chore: bump LAMMPS to stable_29Aug2024_update2

[njzjz]

Summary by CodeRabbit

• Chores
  • Updated all references to the LAMMPS version from stable_29Aug2024_update1 to stable_29Aug2024_update2 across installation scripts, documentation, and dependency specifications.

[coderabbitai[bot]]

📝 Walkthrough

Walkthrough

The changes update all references to the LAMMPS version from stable_29Aug2024_update1 to stable_29Aug2024_update2 across build scripts, documentation, and dependency specifications. No other modifications to logic, control flow, or installation procedures are introduced.

Changes

Files/Paths	Summary of Changes
.devcontainer/build_cxx.sh, source/install/build_cc.sh,	Updated LAMMPS version in CMake configuration from stable_29Aug2024_update1 to stable_29Aug2024_update2.
source/install/build_from_c.sh, source/install/test_cc.sh,
source/install/test_cc_local.sh
source/install/build_lammps.sh	Updated LAMMPS version variable to stable_29Aug2024_update2 for download and build steps.
doc/install/install-lammps.md	Updated all documentation references of LAMMPS version to stable_29Aug2024_update2.
pyproject.toml	Updated lammps dependency version and environment variable to reference stable_29Aug2024_update2.

Possibly related PRs

• deepmodeling/deepmd-kit#4179: Previously updated LAMMPS version from stable_29Aug2024 to stable_29Aug2024_update1 in the same scripts and documentation.

Suggested labels

LAMMPS, Docs

Suggested reviewers

• wanghan-iapcm

✨ 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

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

[codecov[bot]]

Codecov Report

:white_check_mark: All modified and coverable lines are covered by tests. :white_check_mark: Project coverage is 84.57%. Comparing base (3bd950f) to head (7c2c5c9). :warning: Report is 91 commits behind head on devel.

Additional details and impacted files

@@            Coverage Diff             @@
##            devel    #4815      +/-   ##
==========================================
- Coverage   84.57%   84.57%   -0.01%     
==========================================
  Files         699      699              
  Lines       68034    68033       -1     
  Branches     3541     3540       -1     
==========================================
- Hits        57540    57539       -1     
+ Misses       9360     9359       -1     
- Partials     1134     1135       +1     

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

:rocket: New features to boost your workflow:

• :snowflake: Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• :package: JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.