Skip to content

Conversation

@anyangml
Copy link
Collaborator

@anyangml anyangml commented Jun 24, 2025

Summary by CodeRabbit

  • New Features
    • Enhanced support for optional fitting and atomic parameters during calculations.
  • Tests
    • Added tests to verify correct handling of models with multiple fitting and atomic parameters, ensuring consistent results under atom permutation.

@anyangml anyangml changed the base branch from master to devel June 24, 2025 08:22
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jun 24, 2025

📝 Walkthrough

Walkthrough

The DP calculator's calculate method was updated to support optional fparam and aparam parameters from the atoms.info dictionary, passing them to the underlying model evaluation. A new test class was added to verify correct handling of these parameters and the invariance of computed results under atom permutation.

Changes

File(s) Change Summary
deepmd/calculator.py Modified DP.calculate to extract and forward fparam and aparam from atoms.info to self.dp.eval.
source/tests/pt/test_calculator.py Added TestCalculatorWithFparamAparam class to test calculator with models requiring fparam and aparam, including permutation invariance checks.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant ASE_Atoms
    participant DP_Calculator
    participant DP_Model

    User->>ASE_Atoms: Set up Atoms (with fparam, aparam in info)
    User->>DP_Calculator: Request calculation (energy, forces, stress)
    DP_Calculator->>ASE_Atoms: Access info['fparam'], info['aparam']
    DP_Calculator->>DP_Model: eval(coords, cells, atom_types, fparam, aparam)
    DP_Model-->>DP_Calculator: Return energy, forces, virial, etc.
    DP_Calculator-->>User: Return results
Loading
sequenceDiagram
    participant TestCase
    participant DP_Calculator
    participant ASE_Atoms

    TestCase->>DP_Calculator: Initialize with model (with fparam/aparam)
    TestCase->>ASE_Atoms: Create Atoms (with fparam, aparam)
    TestCase->>DP_Calculator: Calculate properties
    TestCase->>ASE_Atoms: Permute atoms and parameters
    TestCase->>DP_Calculator: Recalculate properties
    TestCase->>TestCase: Assert invariance and correct shapes
Loading

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 Pylint (3.3.7)
deepmd/calculator.py

No files to lint: exiting.


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7652a49 and da9bb00.

📒 Files selected for processing (1)
  • deepmd/calculator.py (1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • deepmd/calculator.py
⏰ Context from checks skipped due to timeout of 90000ms (29)
  • GitHub Check: Build wheels for cp310-manylinux_aarch64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build wheels for cp311-macosx_arm64
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Build C library (2.14, >=2.5.0rc0,<2.15, libdeepmd_c_cu11.tar.gz)
  • GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
  • GitHub Check: Test Python (5, 3.9)
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Test Python (6, 3.12)
  • GitHub Check: Test Python (5, 3.12)
  • GitHub Check: Test Python (6, 3.9)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Test Python (1, 3.9)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Build C++ (cpu, cpu)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Build C++ (rocm, rocm)
  • GitHub Check: Build C++ (cuda, cuda)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Test C++ (false)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (c-cpp)
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this 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.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
deepmd/calculator.py (1)

135-137: Good implementation of parameter passing.

The modification correctly passes the optional fparam and aparam parameters to the model evaluation. Using keyword arguments and None defaults is appropriate.

Consider updating the method docstring to document the new fparam and aparam support for better API documentation:

 def calculate(
     self,
     atoms: Optional["Atoms"] = None,
     properties: list[str] = ["energy", "forces", "virial"],
     system_changes: list[str] = all_changes,
 ) -> None:
     """Run calculation with deepmd model.

     Parameters
     ----------
     atoms : Optional[Atoms], optional
         atoms object to run the calculation on, by default None
+        atoms.info may contain 'fparam' and 'aparam' for additional model parameters
     properties : list[str], optional
         unused, only for function signature compatibility,
         by default ["energy", "forces", "stress"]
     system_changes : list[str], optional
         unused, only for function signature compatibility, by default all_changes
     """
source/tests/pt/test_calculator.py (1)

144-145: Verify parameter data types for testing.

The test uses IntTensor for fparam and aparam, but these typically represent physical parameters which are usually floating-point values. This might be intentional for testing to avoid floating-point precision issues.

Consider using floating-point tensors for more realistic testing:

-        fparam = torch.IntTensor([1, 2])
-        aparam = torch.IntTensor([[1], [0], [2], [1], [0]])
+        fparam = torch.tensor([1.0, 2.0], dtype=dtype)
+        aparam = torch.tensor([[1.0], [0.0], [2.0], [1.0], [0.0]], dtype=dtype)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 04da98f and 7652a49.

📒 Files selected for processing (2)
  • deepmd/calculator.py (1 hunks)
  • source/tests/pt/test_calculator.py (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (29)
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Test Python (6, 3.12)
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Test Python (5, 3.12)
  • GitHub Check: Test Python (5, 3.9)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Test Python (6, 3.9)
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Test Python (1, 3.9)
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build wheels for cp311-macosx_arm64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Build wheels for cp310-manylinux_aarch64
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (c-cpp)
  • GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
  • GitHub Check: Build C library (2.14, >=2.5.0rc0,<2.15, libdeepmd_c_cu11.tar.gz)
  • GitHub Check: Test C++ (false)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Build C++ (rocm, rocm)
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Build C++ (cpu, cpu)
  • GitHub Check: Build C++ (cuda, cuda)
🔇 Additional comments (3)
source/tests/pt/test_calculator.py (3)

113-114: Good test configuration for fparam/aparam support.

The model configuration correctly sets up fitting and atomic parameters for testing the new functionality.


160-160: Excellent handling of parameter assignment and permutation.

The test correctly assigns parameters to atoms.info and properly handles the fact that fparam is system-wide while aparam is per-atom (correctly permuted with aparam[idx_perm, :]).

Also applies to: 175-175


182-188: Comprehensive test assertions validate the implementation.

The test properly verifies data types, shapes, and most importantly, the invariance of computed properties under atom permutation. This ensures the fparam/aparam functionality doesn't break physical symmetries.

@anyangml anyangml requested a review from iProzd June 24, 2025 08:45
@codecov
Copy link

codecov bot commented Jun 24, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.57%. Comparing base (04da98f) to head (da9bb00).
⚠️ Report is 80 commits behind head on devel.

Additional details and impacted files
@@           Coverage Diff           @@
##            devel    #4819   +/-   ##
=======================================
  Coverage   84.57%   84.57%           
=======================================
  Files         699      699           
  Lines       68035    68036    +1     
  Branches     3540     3540           
=======================================
+ Hits        57539    57544    +5     
+ Misses       9361     9358    -3     
+ Partials     1135     1134    -1     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@anyangml anyangml added this pull request to the merge queue Jun 24, 2025
Merged via the queue into deepmodeling:devel with commit e1e433c Jun 24, 2025
60 checks passed
@anyangml anyangml deleted the feat/support-fparam-dp-calculator branch June 24, 2025 16:25
ChiahsinChu pushed a commit to ChiahsinChu/deepmd-kit that referenced this pull request Dec 17, 2025
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **New Features**
- Enhanced support for optional fitting and atomic parameters during
calculations.
- **Tests**
- Added tests to verify correct handling of models with multiple fitting
and atomic parameters, ensuring consistent results under atom
permutation.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
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.

2 participants