Skip to content

Conversation

@iProzd
Copy link
Collaborator

@iProzd iProzd commented May 30, 2025

Summary by CodeRabbit

  • New Features

    • Introduced a new dynamic configuration option for model training, offering greater flexibility in hyperparameter and training setup customization.
  • Enhancements

    • Updated existing configuration parameters to provide more control over model behavior and feature selection.
  • Tests

    • Expanded test coverage to include the new dynamic configuration file, ensuring validation of its setup and arguments.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented May 30, 2025

📝 Walkthrough

Walkthrough

A new dynamic training configuration file for the DPA3 model was added, specifying detailed model, fitting, loss, and training parameters. The existing static configuration was updated with modified descriptor parameters. The test suite was updated to include the new dynamic configuration file for validation.

Changes

File(s) Change Summary
examples/water/dpa3/input_torch.json Updated "repflow" descriptor: reduced feature dimensions, increased smoothing cutoffs, replaced skip_stat with fix_stat_std, and added new boolean flags.
examples/water/dpa3/input_torch_dynamic.json Added new JSON configuration for dynamic PyTorch model training, detailing model, fitting, loss, and training parameters.
source/tests/common/test_examples.py Added the new dynamic configuration file to the list of tested input files.

Sequence Diagram(s)

sequenceDiagram
    participant Tester as TestExamples
    participant ConfigStatic as input_torch.json
    participant ConfigDynamic as input_torch_dynamic.json

    Tester->>ConfigStatic: Validate arguments
    Tester->>ConfigDynamic: Validate arguments
Loading

Suggested reviewers

  • njzjz
  • wanghan-iapcm
  • iProzd
✨ 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)
examples/water/dpa3/input_torch.json (1)

27-29: Document and validate new descriptor flags

Three new boolean parameters (smooth_edge_update, edge_init_use_dist, use_exp_switch) were added. Please ensure:

  • The codebase recognizes and applies these flags in the descriptor update routines.
  • Documentation (e.g., README, config schema) is updated to explain their effects.
📜 Review details

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

📥 Commits

Reviewing files that changed from the base of the PR and between 9c17b96 and e313bea.

📒 Files selected for processing (3)
  • examples/water/dpa3/input_torch.json (1 hunks)
  • examples/water/dpa3/input_torch_dynamic.json (1 hunks)
  • source/tests/common/test_examples.py (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (29)
  • 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: Build C++ (rocm, rocm)
  • GitHub Check: Build C++ (clang, clang)
  • GitHub Check: Build C++ (cuda120, cuda)
  • GitHub Check: Build C++ (cuda, cuda)
  • GitHub Check: Build C++ (cpu, cpu)
  • GitHub Check: Test C++ (true)
  • GitHub Check: Test C++ (false)
  • GitHub Check: Build wheels for cp311-win_amd64
  • GitHub Check: Build wheels for cp310-manylinux_aarch64
  • 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-manylinux_x86_64
  • 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 (5, 3.9)
  • GitHub Check: Test Python (3, 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.9)
  • GitHub Check: Test Python (2, 3.9)
  • GitHub Check: Test Python (4, 3.9)
  • GitHub Check: Test Python (1, 3.12)
  • GitHub Check: Analyze (python)
  • GitHub Check: Analyze (c-cpp)
🔇 Additional comments (9)
examples/water/dpa3/input_torch.json (3)

11-12: Verify reduced feature dimensions

The node (n_dim) and edge (e_dim) feature dimensions have been halved. This affects model capacity, weight shapes, and memory usage. Please confirm that:

  • All architecture definitions and weight initializers have been updated to match these new dimensions.
  • Any downstream code or pre-trained checkpoints expecting the old sizes have been adapted accordingly.

16-19: Validate updated smoothing cutoff distances

The smoothing cutoff radii (e_rcut_smth from 3.0→5.3 and a_rcut_smth from 2.0→3.5) can significantly change neighbor inclusion and computational cost. Ensure that:

  • The new cutoff distances align with the desired physical interaction ranges.
  • Upstream code calculating neighbor lists or edge weights correctly uses these updated values.

22-22: Confirm replacement of skip_stat with fix_stat_std

The boolean skip_stat flag was removed and replaced by fix_stat_std: 0.3. Verify that:

  • Configuration parsing logic no longer references skip_stat.
  • fix_stat_std is documented and handled in the model builder with appropriate defaults.
examples/water/dpa3/input_torch_dynamic.json (5)

11-35: Review dynamic repflow descriptor parameters

The dynamic configuration extends the static descriptor with:

  • Selection sizes (e_sel: 1200, a_sel: 300)
  • Dynamic selection controls (use_dynamic_sel, sel_reduce_factor)
  • Other hyperparameters inherited from the static config

Please verify that:

  1. The model initialization code fully supports these new dynamic parameters.
  2. Reasonable defaults or fallbacks exist if any key is omitted.
  3. The expanded e_sel/a_sel values are compatible with memory constraints.

41-52: Approve fitting network configuration

The three-layer fitting network (neuron: [240,240,240]), residual connections (resnet_dt: true), and float32 precision mirror the static config. Everything looks consistent.


55-61: Approve learning rate schedule

The exponential decay schedule (start_lr: 0.001stop_lr: 3e-5 over decay_steps: 5000) aligns with existing conventions.


62-71: Approve loss function parameters

The energy‐based loss with start/limit prefactors for energy, forces, and virial terms is correctly specified.


72-99: Approve training data and hyperparameters

The training settings—including data paths, batch sizes, step counts, gradient clipping, and output frequencies—are consistent with project standards.

source/tests/common/test_examples.py (1)

61-63: Include dynamic config in example tests

Adding input_torch_dynamic.json to input_files ensures the new dynamic DPA3 example is validated by the argument checker.

@codecov
Copy link

codecov bot commented May 30, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 84.78%. Comparing base (9c17b96) to head (e313bea).
⚠️ Report is 88 commits behind head on devel.

Additional details and impacted files
@@           Coverage Diff           @@
##            devel    #4778   +/-   ##
=======================================
  Coverage   84.78%   84.78%           
=======================================
  Files         698      698           
  Lines       67755    67755           
  Branches     3542     3544    +2     
=======================================
+ Hits        57448    57449    +1     
+ Misses       9174     9173    -1     
  Partials     1133     1133           

☔ 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 May 30, 2025
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to no response for status checks May 30, 2025
@njzjz njzjz added this pull request to the merge queue May 31, 2025
Merged via the queue into deepmodeling:devel with commit 265d094 May 31, 2025
60 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants