Validate number of logging entries
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the existing verifiers and package checker to see where submission node and accelerator counts are available. Compare their current rules with the MLPerf Training Logging Spec v0.7, then define how expected log counts should be represented and validated; done means the checker reports missing or extra required entries consistently.
Written by the indexing model from the issue text.
Description
The MLPerf v7.0 logging was described by a MLPerf Training Logging Spec v0.7 document, which includes a definition of the number of expected logs.
The committee decided to drop support for this document, and the checkers should be the only source of logging rules.
With this decision, we lost the definition of required logs, and submitters don't know, what is expected.
I propose to update verifiers to add support for log entries count validation. This test should be a part of the tool, that has knowledge about a number of nodes/accelerators in the submission. The package checker may be the right choice.
- Dominant language
- Python
- Stars
- 43
- Forks
- 60
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mlcommons/logging
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
results summarizer is broken since 4.1.45Possibly taken @pgmpablo157321 claimed this 1 day ago. Open
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in mlcommons/logging
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
enhancement good first issue Stellar Wave trivial
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
StellarCanary/ProtocolCanary-Fixtures#258 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
IBM/ai-atlas-nexus#295 ·
Maintainers usually reply within 6 days
-
github_actions
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Hochfrequenz/aibap.mcp#578 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
mishraprafful/multihull#150 ·
Maintainers usually reply within 1 day