Skip to content

Conversation

@njzjz
Copy link
Member

@njzjz njzjz commented Sep 2, 2025

As documented in https://docs.lammps.org/pair_hybrid.html, "In the pair_coeff commands, the name of a pair style must be added after the I,J type specification".

Summary by CodeRabbit

  • Documentation
    • Updated the hybrid/overlay example for D3 dispersion to use model-specific pair_coeff entries instead of placeholders.
    • Clarifies how to declare coefficients for multiple models in one configuration (e.g., Deep Potential and D3), improving accuracy and reducing setup confusion.
    • Example now better reflects real-world usage without altering existing commands.
    • No functional changes to the software; updates are limited to documentation examples.

As documented in https://docs.lammps.org/pair_hybrid.html, "In the pair_coeff commands, the name of a pair style must be added after the I,J type specification".

Signed-off-by: Jinzhe Zeng <jinzhe.zeng@ustc.edu.cn>
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Sep 2, 2025

📝 Walkthrough

Walkthrough

A documentation update modifies the LAMMPS D3 dispersion example in doc/third-party/lammps-command.md. The pair_coeff placeholders are replaced with model-specific entries for deepmd and dispersion/d3 within a pair_style hybrid/overlay setup. No code or API changes.

Changes

Cohort / File(s) Summary of Changes
Docs: LAMMPS D3 example
doc/third-party/lammps-command.md
Updated pair_coeff lines in the hybrid/overlay example to explicitly reference deepmd and dispersion/d3 models instead of placeholder duplicates.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested labels

Docs

Suggested reviewers

  • wanghan-iapcm
✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

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.
    • 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.
  • 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 the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

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

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

  • Add @coderabbitai ignore or @coderabbit 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

Status, Documentation and Community

  • Visit our Status Page to check the current availability of CodeRabbit.
  • 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: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
doc/third-party/lammps-command.md (1)

313-321: Version note is too lax for the ‘original’ damping keyword.

The example uses dispersion/d3 original ..., but “original” replaced the former “zero” keyword on 2Apr2025. If a user runs exactly 4Feb2025, this example will fail unless they use zero. Please either raise the minimum version to 2Apr2025 or add a parenthetical for 4Feb2025 users.

Suggested edit:

- Requires LAMMPS version 4Feb2025 or newer.
+ Requires LAMMPS version 2Apr2025 or newer.
+ (For LAMMPS 4Feb2025 specifically, use `zero` instead of `original`.)

Refs: “Added in version 4Feb2025” and “Changed in version 2Apr2025: renamed zero keyword to original”. (docs.lammps.org)

🧹 Nitpick comments (1)
doc/third-party/lammps-command.md (1)

322-324: Optional: remind users about units for dispersion/d3.

LAMMPS’ dispersion/d3 parameters require metal units; a one-line note under this example would prevent confusion if readers chose a different unit style earlier.

Source: “The compiled in parameters require the use of metal units.” (docs.lammps.org)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

  • MCP integration is disabled by default for public repositories
  • Jira integration is disabled by default for public repositories
  • Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between ea7f828 and 416e043.

📒 Files selected for processing (1)
  • doc/third-party/lammps-command.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (29)
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Build wheels for cp310-manylinux_aarch64
  • GitHub Check: Build wheels for cp311-macosx_arm64
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Build C++ (cuda, cuda)
  • GitHub Check: Build C++ (rocm, rocm)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Build C++ (cpu, cpu)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (c-cpp)
  • GitHub Check: Build C library (2.14, >=2.5.0,<2.15, libdeepmd_c_cu11.tar.gz)
  • GitHub Check: Build C library (2.18, libdeepmd_c.tar.gz)
  • GitHub Check: Test Python (5, 3.12)
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Test Python (6, 3.12)
  • GitHub Check: Test Python (6, 3.9)
  • GitHub Check: Test Python (5, 3.9)
  • GitHub Check: Test Python (1, 3.9)
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Test C++ (false)
🔇 Additional comments (1)
doc/third-party/lammps-command.md (1)

322-324: Correct hybrid/overlay pair_coeff syntax — looks good.

Including the sub-style name after the I,J types is required for hybrid/overlay; your example now follows the LAMMPS rule.
See: “In the pair_coeff commands, the name of a pair style must be added after the I,J type specification…”. (docs.lammps.org)

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR fixes the documentation for LAMMPS pair_style hybrid/overlay usage by correcting the pair_coeff command syntax. The fix ensures that the pair style name is properly specified after the atom type specification, as required by LAMMPS documentation.

  • Corrects pair_coeff commands to include the pair style names (deepmd and dispersion/d3)
  • Aligns the documentation with official LAMMPS requirements for hybrid pair styles

@codecov
Copy link

codecov bot commented Sep 2, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.28%. Comparing base (ea7f828) to head (3b32380).
⚠️ Report is 66 commits behind head on devel.

Additional details and impacted files
@@           Coverage Diff           @@
##            devel    #4951   +/-   ##
=======================================
  Coverage   84.28%   84.28%           
=======================================
  Files         705      705           
  Lines       69085    69084    -1     
  Branches     3573     3572    -1     
=======================================
+ Hits        58229    58230    +1     
+ Misses       9715     9714    -1     
+ Partials     1141     1140    -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.

@wanghan-iapcm wanghan-iapcm added this pull request to the merge queue Sep 3, 2025
Merged via the queue into deepmodeling:devel with commit 68ea2aa Sep 3, 2025
60 checks passed
ChiahsinChu pushed a commit to ChiahsinChu/deepmd-kit that referenced this pull request Dec 17, 2025
…odeling#4951)

As documented in https://docs.lammps.org/pair_hybrid.html, "In the
pair_coeff commands, the name of a pair style must be added after the
I,J type specification".

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

## Summary by CodeRabbit

- Documentation
- Updated the hybrid/overlay example for D3 dispersion to use
model-specific pair_coeff entries instead of placeholders.
- Clarifies how to declare coefficients for multiple models in one
configuration (e.g., Deep Potential and D3), improving accuracy and
reducing setup confusion.
- Example now better reflects real-world usage without altering existing
commands.
- No functional changes to the software; updates are limited to
documentation examples.

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

Signed-off-by: Jinzhe Zeng <jinzhe.zeng@ustc.edu.cn>
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