Skip to content

chore: bump LAMMPS to stable_29Aug2024_update2 #4815

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

Draft
wants to merge 1 commit into
base: devel
Choose a base branch
from

Conversation

njzjz
Copy link
Member

@njzjz njzjz commented Jun 21, 2025

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.

@github-actions github-actions bot added the Docs label Jun 21, 2025
Copy link
Contributor

coderabbitai bot commented Jun 21, 2025

📝 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

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
🪧 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: 0

🧹 Nitpick comments (1)
source/install/build_from_c.sh (1)

1-23: Consider centralizing the LAMMPS version string
Having to update the version literal across multiple scripts increases the risk of drift. You could define LAMMPS_VERSION once (e.g., in an env file or top-level config) and source it in each build/test script.

📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 3bd950f and 7c2c5c9.

📒 Files selected for processing (8)
  • .devcontainer/build_cxx.sh (1 hunks)
  • doc/install/install-lammps.md (4 hunks)
  • pyproject.toml (3 hunks)
  • source/install/build_cc.sh (1 hunks)
  • source/install/build_from_c.sh (1 hunks)
  • source/install/build_lammps.sh (1 hunks)
  • source/install/test_cc.sh (1 hunks)
  • source/install/test_cc_local.sh (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (30)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Test C++ (false)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Build C++ (cuda, cuda)
  • GitHub Check: Build C++ (rocm, rocm)
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Build C++ (cpu, cpu)
  • 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 wheels for cp311-manylinux_x86_64
  • GitHub Check: Analyze (python)
  • GitHub Check: Build wheels for cp311-macosx_x86_64
  • GitHub Check: Build wheels for cp311-manylinux_x86_64
  • GitHub Check: Analyze (c-cpp)
  • GitHub Check: Analyze (javascript-typescript)
  • 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 Python (4, 3.9)
  • 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 (5, 3.12)
  • GitHub Check: Test Python (4, 3.12)
  • GitHub Check: Test Python (3, 3.9)
  • GitHub Check: Test Python (2, 3.12)
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Test Python (3, 3.12)
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Test Python (1, 3.9)
🔇 Additional comments (16)
source/install/build_from_c.sh (1)

16-16: Approve version bump in build_from_c.sh
The -DLAMMPS_VERSION flag is correctly updated to stable_29Aug2024_update2.

.devcontainer/build_cxx.sh (1)

16-16: Approve version bump in build_cxx.sh
The CMake -D LAMMPS_VERSION argument has been updated to stable_29Aug2024_update2 as expected.

source/install/build_cc.sh (1)

29-29: Approve version bump in build_cc.sh
Updated -D LAMMPS_VERSION to stable_29Aug2024_update2 to stay consistent with other build scripts.

source/install/test_cc_local.sh (1)

31-31: Approve version bump in test_cc_local.sh
The local C++ test script now references stable_29Aug2024_update2 correctly.

source/install/test_cc.sh (1)

20-20: Approve version bump in test_cc.sh
The -DLAMMPS_VERSION flag is updated to stable_29Aug2024_update2, aligning with other test scripts.

source/install/build_lammps.sh (1)

17-17: Verify new LAMMPS version tag exists on GitHub.

The version was bumped to stable_29Aug2024_update2. Please confirm that the corresponding Git tag and tarball URL are available before merging:

#!/usr/bin/env bash
curl -I -f https://github.com/lammps/lammps/archive/refs/tags/stable_29Aug2024_update2.tar.gz
pyproject.toml (3)

248-248: Sync DP_LAMMPS_VERSION for macOS build.

The DP_LAMMPS_VERSION environment variable for macOS cibuildwheel is updated to "stable_29Aug2024_update2", matching the new release.


285-285: Sync DP_LAMMPS_VERSION for Linux build.

The DP_LAMMPS_VERSION environment variable for Linux cibuildwheel is updated to "stable_29Aug2024_update2", ensuring consistency across platforms.


111-111: Verify PyPI release for LAMMPS 2024.8.29.2.0.

The optional lmp extras group now specifies "lammps~=2024.8.29.2.0". Confirm this version is published on PyPI or your chosen index:

#!/usr/bin/env bash
curl -sf https://pypi.org/pypi/lammps/json | jq -e '.releases["2024.8.29.2.0"]'
doc/install/install-lammps.md (7)

20-21: Update built-in mode download commands.

The wget URL and tar xf command now fetch stable_29Aug2024_update2, aligning docs with build scripts.


24-24: Update directory name reference for built-in mode.

The directory name is updated to lammps-stable_29Aug2024_update2, consistent with the downloaded tarball.


33-33: Update source directory navigation.

The cd command now targets lammps-stable_29Aug2024_update2/src/, reflecting the new version.


63-64: Update build directory creation for built-in mode.

The mkdir and cd commands reference lammps-stable_29Aug2024_update2/build/, matching the version bump.


97-98: Update plugin mode download commands.

Plugin mode’s wget and tar xf now use stable_29Aug2024_update2.


101-101: Update plugin mode directory reference.

The plugin mode directory name is updated to lammps-stable_29Aug2024_update2.


104-105: Update plugin mode build directory creation.

The commands to create and enter the build directory now point to lammps-stable_29Aug2024_update2/build/.

Copy link

codecov bot commented Jun 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 84.57%. Comparing base (3bd950f) to head (7c2c5c9).

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     

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

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.

1 participant