Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(pt): fix ValueError when array byte order is not native #4100

Merged

Conversation

njzjz
Copy link
Member

@njzjz njzjz commented Sep 3, 2024

Fix #4099.

Summary by CodeRabbit

  • New Features

    • Enhanced tensor data type handling for improved numerical stability and performance in deep learning computations.
    • Introduced a precision dictionary to ensure input data is processed with the correct precision.
  • Bug Fixes

    • Improved clarity and robustness in the handling of data types within the model evaluation process.

@njzjz njzjz linked an issue Sep 3, 2024 that may be closed by this pull request
Copy link
Contributor

coderabbitai bot commented Sep 3, 2024

Walkthrough

Walkthrough

The changes involve modifications to the _eval_model function in deepmd/pt/infer/deep_eval.py, focusing on the handling of tensor data types. A new precision dictionary, NP_PRECISION_DICT, is introduced to convert input tensor data types based on a reserved precision mapping. The reshaping process for arrays includes casting to the appropriate precision type before conversion to PyTorch tensors, enhancing data type handling for improved numerical stability.

Changes

Files Change Summary
deepmd/pt/infer/deep_eval.py Enhanced _eval_model to utilize NP_PRECISION_DICT for tensor data type conversion and casting.

Assessment against linked issues

Objective Addressed Explanation
Passing >f4 array to DeepPot should not trigger ValueError (#4099)

Tip

We have updated our review workflow to use the Anthropic's Claude family of models. Please share any feedback in the discussion post on our Discord.


Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 1abb89b and cbc6bcf.

Files selected for processing (1)
  • deepmd/pt/infer/deep_eval.py (3 hunks)
Additional comments not posted (4)
deepmd/pt/infer/deep_eval.py (4)

58-58: LGTM!

The additional import RESERVED_PRECISON_DICT is approved.


385-387: LGTM!

The changes to cast the coords array to the appropriate precision type before converting it to a PyTorch tensor are approved.


391-395: LGTM!

The changes to cast the atom_types array to the appropriate precision type before converting it to a PyTorch tensor are approved.


398-400: LGTM!

The changes to cast the cells array to the appropriate precision type before converting it to a PyTorch tensor are approved.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the Python label Sep 3, 2024
Copy link

codecov bot commented Sep 3, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.01%. Comparing base (1abb89b) to head (cbc6bcf).
Report is 203 commits behind head on devel.

Additional details and impacted files
@@            Coverage Diff             @@
##            devel    #4100      +/-   ##
==========================================
- Coverage   83.02%   83.01%   -0.01%     
==========================================
  Files         524      524              
  Lines       51641    51642       +1     
  Branches     3030     3030              
==========================================
- Hits        42873    42870       -3     
- Misses       7823     7825       +2     
- Partials      945      947       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@wanghan-iapcm wanghan-iapcm added this pull request to the merge queue Sep 4, 2024
Merged via the queue into deepmodeling:devel with commit 46632f9 Sep 4, 2024
60 checks passed
mtaillefumier pushed a commit to mtaillefumier/deepmd-kit that referenced this pull request Sep 18, 2024
…ling#4100)

Fix deepmodeling#4099.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **New Features**
- Enhanced tensor data type handling for improved numerical stability
and performance in deep learning computations.
- Introduced a precision dictionary to ensure input data is processed
with the correct precision.

- **Bug Fixes**
- Improved clarity and robustness in the handling of data types within
the model evaluation process.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Jinzhe Zeng <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[BUG] PT: passing >f4 array to DeepPot triggers ValueError
2 participants