support fparam in lmp template

[mingzhong15]

in previous version, if we use template in model deviation process, the generated LAMMPS input file would neglect fparam-dependence in DP model, as

pair_style      deepmd ../graph.000.pb ../graph.001.pb ../graph.002.pb ../graph.003.pb out_freq 10 out_file model_devi.out 
pair_coeff      * *

here we fixed this problem, as

pair_style      deepmd ../graph.000.pb ../graph.001.pb ../graph.002.pb ../graph.003.pb out_freq 10 out_file model_devi.out fparam ${ELE_TEMP}
pair_coeff      * *

Summary by CodeRabbit

• New Features

  • Enhanced the LAMMPS input model to support configurations based on electron temperature settings.
  • Added flexibility in handling different input scenarios with the introduction of a new parameter.

• Bug Fixes

  • Improved compatibility checks for the specified DeepMD version in the input model construction.

• Documentation

  • Updated comments for clarity regarding the new functionality and parameter usage.

[coderabbitai]

📝 Walkthrough

Walkthrough

The changes in this pull request involve modifications to the revise_lmp_input_model function in the dpgen/generator/run.py file. An additional parameter, use_ele_temp, has been introduced to the function signature, influencing how the LAMMPS pair style input is constructed based on electron temperature settings. The logic within the function has been updated to conditionally include a fitting parameter for electron temperature when use_ele_temp is set to 1. Compatibility checks for deepmd_version have also been added, along with minor formatting and comment adjustments.

Changes

File Path	Change Summary
dpgen/generator/run.py	Updated revise_lmp_input_model function signature to include use_ele_temp. Modified logic to construct lmp_lines based on use_ele_temp. Added compatibility check for deepmd_version. Minor adjustments to comments and formatting.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Function
    participant LAMMPS

    User->>Function: Call revise_lmp_input_model(lmp_lines, task_model_list, trj_freq, deepmd_version, use_ele_temp)
    Function->>Function: Check use_ele_temp
    alt use_ele_temp = 1
        Function->>Function: Construct lmp_lines with fparam ${ELE_TEMP}
    else use_ele_temp = 0
        Function->>Function: Construct lmp_lines without changes
    end
    Function->>LAMMPS: Output lmp_lines

Loading

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 47a23b3 and 4f9d0e5.

📒 Files selected for processing (1)

• dpgen/generator/run.py (6 hunks)

🔇 Additional comments (3)

dpgen/generator/run.py (3)

1008-1010: LGTM: Function signature updated correctly.

The addition of use_ele_temp parameter with a default value of 0 maintains backward compatibility while enabling the new fparam functionality.

---

1019-1033: LGTM: Electron temperature handling implemented correctly.

The implementation properly handles electron temperature by:

1. Checking use_ele_temp flag
2. Adding fparam ${ELE_TEMP} to the pair_style command when use_ele_temp=1
3. Maintaining the original behavior when use_ele_temp=0

The code aligns with the PR objectives to support fparam in the LAMMPS template.

---

Line range hint 1008-1033: Verify the impact of the changes.

Let's verify that all callers of this function pass the correct use_ele_temp value.

✅ Verification successful

Let me analyze the callers of revise_lmp_input_model to verify if we need more context.

---

Let me check where use_ele_temp is defined and how it's passed down to these calls.

---

Based on the gathered information, I can now provide the final response:

The use_ele_temp parameter is properly handled throughout the codebase

The parameter is:

• Consistently initialized from configuration with jdata.get("use_ele_temp", 0) defaulting to 0
• Properly passed down to all calls of revise_lmp_input_model
• Used correctly with validation checks in multiple places
• Has clear logic paths for all its possible values (0, 1, 2)

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Search for all calls to revise_lmp_input_model
rg -A 5 "revise_lmp_input_model\(" 

Length of output: 2765

---

Script:

#!/bin/bash
# Let's check the context of the callers in dpgen/generator/run.py to see how use_ele_temp is determined
rg -B 10 -A 2 "lmp_lines = revise_lmp_input_model" dpgen/generator/run.py

Length of output: 1793

---

Script:

#!/bin/bash
# Search for where use_ele_temp is defined and initialized
rg -B 5 "use_ele_temp\s*=" dpgen/generator/run.py

Length of output: 4918

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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.
  • 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 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 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.

[njzjz]

I found this PR is not merged into the devel branch.