Merged
Conversation
|
MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅ |
mlperf_logging/compliance_checker/training_6.0.0/closed_common.yaml
Outdated
Show resolved
Hide resolved
mlperf_logging/compliance_checker/training_6.0.0/closed_deepseekv3_671b.yaml
Show resolved
Hide resolved
039c2fa to
f3a3dc7
Compare
- Add rcps_deepseek_v3_671b.json stub with BS 16384/18432/20480, learning rates, warmup steps, and gradient accumulation steps - Register deepseek_v3_671b in benchmark_meta.py (result file counts and allowed benchmarks for 6.0) - Add deepseek_v3_671b to submission_runs and eval_accuracy parsing in rcp_checker.py - Add deepseek_v3_671b entry to result_summarizer config.yaml
f3a3dc7 to
c528ecb
Compare
Contributor
Author
|
recheck |
Contributor
|
@denys-fridman - can you please complete the CLA? Also, can you create a PR to training_rules that adds GB300 to the list of acceptable reference hardware (https://github.com/mlcommons/training_policies/blob/master/CONTRIBUTING.md#general)? |
mlperf_logging/compliance_checker/training_6.0.0/closed_deepseekv3_671b.yaml
Show resolved
Hide resolved
mlperf_logging/compliance_checker/training_6.0.0/closed_deepseekv3_671b.yaml
Show resolved
Hide resolved
Contributor
Author
|
recheck |
Contributor
Author
|
recheck |
mlperf_logging/compliance_checker/training_6.0.0/closed_deepseekv3_671b.yaml
Show resolved
Hide resolved
mlperf_logging/compliance_checker/training_6.0.0/closed_deepseekv3_671b.yaml
Show resolved
Hide resolved
mlperf_logging/compliance_checker/training_6.0.0/closed_deepseekv3_671b.yaml
Show resolved
Hide resolved
| - KEY: | ||
| NAME: max_steps | ||
| REQ: EXACTLY_ONE | ||
| CHECK: " v['value'] == 12000 " |
Contributor
There was a problem hiding this comment.
Not needed for the open category. Submitters should be free to modify max_steps and LR
Only the eval dataset, eval frequency and the eval accuracy should be met in the ope category.
| REQ: AT_LEAST_ONE | ||
| CHECK: | ||
| - "'samples_count' in v['metadata']" | ||
| ATLEAST_ONE_CHECK: "(v['value'] <= 4.05) and v['value'] > 0.0" |
| REQ: AT_LEAST_ONE | ||
| CHECK: | ||
| - "'epoch_num' in v['metadata']" | ||
| ATLEAST_ONE_CHECK: "(v['value'] <= 4.05) and v['value'] > 0.0" |
ShriyaRishab
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.