NVIDIA-NeMo / NVIDIA-NeMo/Megatron-Bridge
Feature Request: Support for multiple validation sets + separate loss validation reporting
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 921
- Forks
- 506
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 236
Description
Currently, Megatron-Bridge supports evaluating on a single validation set. For many workflows (e.g., multi-domain SFT, benchmarking across datasets), it is useful to:
- Define multiple validation datasets in the config.
- Report losses separately for each validation set (instead of aggregating).
This would allow fine-grained monitoring of model performance across domains or tasks without maintaining separate training runs.
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 does not name files or tests. Start by locating the configuration for validation datasets and the evaluation and loss-reporting entry points, then trace how the current single validation set is defined and evaluated. Done means multiple validation datasets can be configured and losses are reported separately for each set, with coverage for both behaviors.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100