fix(pt): typo in epoch training

[OutisLi]

Summary by CodeRabbit

• Bug Fixes
  • Fixed configuration lookup for the epoch count so training now reads and respects the configured number of epochs.

[Copilot]

Pull request overview

Fixes PyTorch trainer configuration parsing so epoch-based training works when configs are normalized via deepmd.utils.argcheck.normalize().

Changes:

• Read training.numb_epoch (canonical argcheck key) instead of training.num_epoch in the PyTorch Trainer initialization.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 702b5d84-6b1c-4e33-8b6b-ee13e431331f

📥 Commits

Reviewing files that changed from the base of the PR and between 716a15b and 86a93af.

📒 Files selected for processing (1)

• deepmd/pd/train/training.py

---

📝 Walkthrough

Walkthrough

Trainer initialization now reads epoch count from the "numb_epoch" key instead of "num_epoch" in training parameter dictionaries. No other iteration-related fields or control flow were modified.

Changes

Cohort / File(s)	Summary
Configuration Parameter Rename deepmd/pt/train/training.py, deepmd/pd/train/training.py	Replaced lookup of training parameter key from "num_epoch" to "numb_epoch" in Trainer.__init__; no other logic or public interfaces changed.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title refers to a typo fix in epoch training configuration, which aligns with the changes in both pt and pd training modules that correct 'num_epoch' to 'numb_epoch' lookup.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 80.47%. Comparing base (1a1dc59) to head (86a93af).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #5410   +/-   ##
=======================================
  Coverage   80.47%   80.47%           
=======================================
  Files         820      820           
  Lines       86005    86005           
  Branches     4139     4140    +1     
=======================================
+ Hits        69209    69210    +1     
  Misses      15521    15521           
+ Partials     1275     1274    -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.

[njzjz]

I searched num_epoch and found many other places using num_epoch

https://github.com/search?q=repo%3Adeepmodeling%2Fdeepmd-kit%20num_epoch&type=code

[OutisLi]

I searched num_epoch and found many other places using num_epoch

https://github.com/search?q=repo%3Adeepmodeling%2Fdeepmd-kit%20num_epoch&type=code

I searched num_epoch and found many other places using num_epoch

https://github.com/search?q=repo%3Adeepmodeling%2Fdeepmd-kit%20num_epoch&type=code

Thanks for the catch! I went through every num_epoch hit in that search.

The only other occurrence that had the same bug was in the Paddle backend, which I've now fixed in the latest commit:

deepmd/pd/train/training.py: training_params.get("num_epoch") → training_params.get("numb_epoch") (same root cause — the canonical key after normalize() is numb_epoch, while num_epoch is only an alias).
The remaining num_epoch mentions are intentional and not bugs:

deepmd/tf/entrypoints/train.py and change_bias.py: num_epoch is just a local variable name; the .get(...) call already uses the canonical "numb_epoch".
self.num_epoch, num_epoch_dict_config, test_sampler.py::num_epoch = 1.5, etc.: internal attribute/variable/parameter names, unrelated to the config key.
num_epoch_dict is itself the canonical name (not an alias of numb_epoch_dict), so all usages are correct.
num_epoch in docstrings and error messages in argcheck.py / TF entrypoints is user-facing text; since num_epoch is a documented alias, keeping it matches what most users actually write in their input files.
examples/water/se_e2_a/input_torch_num_epoch.json uses "num_epoch": 100, which is a legal alias and still works

[njzjz]

Thanks!