Compliance checker: epoch number for evaluations should be validated against reference schedule
@shangw-nvidia is already working on this.
Since Aug 3, 2021.
Assessment
This issue has not been assessed yet.
Description
This issue has no description.
- 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 3 days 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
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
huggingface/smolagents#2976 ·
Maintainers usually reply within 1 day
-
bug Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
FuRongJun-1999/dsh-memory#170 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
pgvector/pgvector-python#163 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
521xueweihan/HelloGitHub#3940 ·