NVIDIA-NeMo / NVIDIA-NeMo/Curator
RL-Trained LLM for End-to-End Data Recipe Generation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.8k
- Forks
- 328
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 30
Description
What:
Add integration with DataChef (arXiv:2602.11089, Feb 2026) — a 32B LLM trained via RL to generate complete end-to-end NeMo Curator pipeline specifications (synthesis strategy, filter chain, mixing ratios) given a target benchmark and base model. Exposes a DataChefRecipeGenerator that outputs a valid NeMo Curator config YAML.
Why:
DataChef achieves 66.7 on AIME'25 for a Qwen3-1.7B math-adapted model — surpassing the official Qwen3 post-training checkpoint for the same base model. It matches human expert curation across 6 held-out tasks. The RL-trained recipe generator eliminates the manual trial-and-error of pipeline design, which is the primary bottleneck in practice.
Definition of Done:
- DataChefRecipeGenerator under nemo_curator/recipe/
- Interface: accepts target_benchmark: str, base_model_id: str, available_data_sources: List[str], compute_budget_tokens: int
- Calls DataChef API (hosted or local) with structured prompt encoding the above
- Parses DataChef output into a valid NeMo Curator pipeline config YAML
- Config validation: runs a dry-run of the generated pipeline on 1M token sample before full execution
- Proxy reward integration: evaluates generated recipe quality on a fast proxy before committing to full run
- Fallback: if DataChef unavailable, outputs a best-practice template config for the domain
- Tutorial: generate and execute a math-specialization recipe using DataChef → NeMo Curator pipeline
- Integration test: generated YAML is parseable and passes NeMo Curator config validation
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
Start by examining the existing structure under nemo_curator/recipe/ and the repository's configuration validation and integration-test entry points. Define the DataChef API boundary, generated YAML validation, dry-run and proxy-reward flow, fallback behavior, and the tutorial. Done means the generator, validation and fallback paths work, the generated YAML passes config validation, and the math-specialization tutorial and integration test are included.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data-engineering, machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100