mlcommons / mlcommons/algorithmic-efficiency
Add step_hint_batch_size property to workloads to allow submissions to know the batch size the baseline defining the step hint used
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 425
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
The step_hint is meaningless without knowing the batch size the baseline used. We should just provide that information for each workload so submissions that use batch sizes that non-uniformly vary relative to the baseline can properly adjust the step hints, if they desire.
Contributor 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.
Research direction
The issue names workloads and the existing step_hint value but gives no file or test entry point. Start by locating workload definitions and how submissions read step hints; done means each workload exposes the baseline batch size used for its step hint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100