Chenjie LuoandClaude Opus 4.8 9cfd7dd3e8 Align eval skill AA benchmarks to golden NeMo configs + harden skill (#1790)
### What does this PR do?

Type of change: Documentation (agent skill under
`.agents/skills/evaluation/`)

Aligns the `evaluation` agent skill's AA benchmark recipes with NeMo
Evaluator's Nemotron-3-Ultra golden reproducibility configs, and fixes
several robustness gaps surfaced while validating the changes end-to-end
on SLURM (MiniMax-M2.7, FP8 + ModelOpt NVFP4).

**AA benchmark alignment**
- GPQA: simple-evals `gpqa_diamond_aa_v3` → nemo-skills `ns_gpqa`
(`++prompt_config=eval/aai/mcq-4choices`).
- MMLU-Pro: `mmlu_pro_aa_v3` → `ns_mmlu_pro` (`mcq-10choices-boxed`).
- Repeat counts unchanged (GPQA 16, MMLU-Pro 1); score-extraction metric
keys updated to the nemo-skills names
(`gpqa_pass_at_1_avg-of-N_symbolic_correct`,
`mmlu-pro_pass_at_1_symbolic_correct`, verified against MLflow run
data).
- HLE: add golden knobs `hle_strict_judge: true` +
`++server.enable_soft_fail=True`.
- Updated `references/{quantization-benchmarks,parallelism}.md` and the
example config's default task to match.

**Skill robustness fixes**
- Invoke `modelopttools:eval-config` at Step 1 for judge-scored runs;
create/populate `.env` before Step 5 (it was only created at Step 8) —
fixes a fresh-environment ordering gap.
- Secret-safety rule: never open `.env` with file tools (the harness
mirrors later external edits back into context, leaking keys) — interact
via shell only.
- Require fetching `recipes.vllm.ai` for the **exact model variant** and
bumping the image to its minimum vLLM — variant minimums differ (e.g.
MiniMax-M2 ≥0.11.0 vs M2.7 ≥0.20.0), and running below crashes
mid-inference with `CUDA illegal memory access`. Note that `--dry-run`
does not validate the image/version.
- Remove internal cluster names from the public skill docs.
- gitignore the local eval run-config dir.

### Usage

N/A — agent skill docs/recipes; no library/API change.

### Testing

Validated on SLURM with MiniMax-M2.7 (16-sample canaries):
- FP8: GPQA + MMLU-Pro ran through the new nemo-skills harness and
produced valid scores (e.g. MMLU-Pro `symbolic_correct=75.0`),
confirming the harness switch + metric keys.
- NVFP4: confirmed the vLLM-min-version finding — deploy crashed on
0.19.1 (`CUDA illegal memory access` mid-inference) and succeeded on
0.20.2 (the recipe minimum).
- (HLE tokenizer gap was reproduced deterministically; its fix is a
separate follow-up, not in this PR.)

### Before your PR is "*Ready for review*"

Commits are signed (`git commit -s -S`). ✅

- Is this change backward compatible?: N/A — agent skill/recipe docs.
Note: the GPQA/MMLU-Pro harness switch changes the MLflow metric keys,
so new runs are not directly comparable to prior simple-evals baselines
(re-baseline).
- If you copied code from any other sources or added a new PIP
dependency: N/A
- Did you write any new necessary tests?: N/A (docs/recipes only)
- Did you update Changelog?: N/A
- Did you get Claude approval on this PR?: ❌ (run `/claude review`)

### Additional Information

🤖 Generated with [Claude Code](https://claude.com/claude-code)


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Strengthened evaluation setup guidance: `.env` is now required earlier
with safer creation/sourcing rules, and endpoint placeholders are
clarified.
* Updated judge/user-simulator and vLLM deployment instructions,
including exact minimum `recipes.vllm.ai` variant/image requirements,
expected failure symptoms, and a warning about `--dry-run`.
* Refreshed AA benchmark/task recipes to the `nemo-skills` harness
(e.g., `ns_gpqa`, `ns_mmlu_pro`) with updated parameters and
score-metric guidance, plus stricter HLE judging options.
* **Bug Fixes**
* Improved score-reporting guidance for GPQA and MMLU-Pro to match
current outputs.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Signed-off-by: Chenjie Luo <chenjiel@nvidia.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
2026-06-25 02:18:58 +05:30
…
…
…
2026-06-23 21:42:37 +05:30

Banner image

NVIDIA Model Optimizer

Documentation version license

Documentation | Roadmap


NVIDIA Model Optimizer (referred to as Model Optimizer, or ModelOpt) is a library comprising state-of-the-art model optimization techniques including quantization, pruning, Neural Architecture Search (NAS), distillation, speculative decoding and sparsity to accelerate models.

[Input] Model Optimizer currently supports inputs of a Hugging Face, PyTorch or ONNX model.

[Optimize] Model Optimizer provides Python APIs for users to easily compose the above model optimization techniques and export an optimized quantized checkpoint. Model Optimizer is also integrated with NVIDIA Megatron-Bridge, Megatron-LM and Hugging Face Accelerate for training required inference optimization techniques.

[Export for deployment] Seamlessly integrated within the NVIDIA AI software ecosystem, the quantized checkpoint generated from Model Optimizer is ready for deployment in downstream inference frameworks like SGLang, TensorRT-LLM, TensorRT, or vLLM. The unified Hugging Face export API now supports both transformers and diffusers models.

Latest News

Previous News

Install

To install stable release packages for Model Optimizer with pip from PyPI:

pip install -U nvidia-modelopt[all]

Model Optimizer will download and install additional third-party open source software projects. Review the license terms of these open source projects before use.

To install from source in editable mode with all development dependencies or to use the latest features, run:

# Clone the Model Optimizer repository
git clone git@github.com:NVIDIA/Model-Optimizer.git
cd Model-Optimizer

pip install -e .[dev]

You can also directly use NVIDIA container images, which have Model Optimizer pre-installed:

  • nvcr.io/nvidia/pytorch:<version>-py3
  • nvcr.io/nvidia/nemo:<version>
  • nvcr.io/nvidia/tensorrt-llm/release:<version>

Before pulling and using the container images, please review their respective license terms. Make sure to upgrade Model Optimizer to the latest version as described above. Visit our installation guide for more fine-grained control on installed dependencies or for alternative docker images and environment variables to setup.

Techniques

Technique Description Examples Docs
Post Training Quantization Compress model size by 2x-4x, speeding up inference while preserving model quality! [HF LLMs / VLMs] [Megatron-Bridge LLMs / VLMs] [Diffusers] [ONNX] [Windows] [docs]
Quantization Aware Training / Distillation Refine accuracy of quantized models even further with a few training steps! [Hugging Face] [Megatron-Bridge] [docs]
Pruning Reduce your model parameters or memory footprint and accelerate inference by removing unnecessary weights! [General] [Megatron-Bridge]
Distillation Reduce deployment model size by teaching small models to behave like larger models! [Hugging Face] [Megatron-Bridge] [Megatron-LM] [docs]
Speculative Decoding Train draft modules to predict extra tokens during inference! [Hugging Face] [Megatron-LM] [docs]
Sparsity Efficiently compress your model by storing only its non-zero parameter values and their locations [Hugging Face] [docs]

Pre-Quantized Checkpoints

Resources

Model Support Matrix

Model Type Support Matrix
LLM Quantization View Support Matrix
VLM Quantization View Support Matrix
Diffusers Quantization View Support Matrix
ONNX Quantization View Support Matrix
Windows Quantization View Support Matrix
Quantization Aware Training View Support Matrix
Pruning View Support Matrix
Distillation View Support Matrix
Speculative Decoding View Support Matrix

Deprecation Policy

Model Optimizer follows a structured approach to managing deprecated features:

  • Communication: Deprecation notices are documented in the Changelog. Deprecated items include source code statements indicating deprecation timing, with runtime warnings issued upon use.
  • Migration Period: Since Model Optimizer is still pre-1.0, we provide a 1-release (~1-month) migration period after deprecation. During this window, deprecated features continue functioning while issuing warnings.
  • Scope: The policy addresses both complete deprecations (entire APIs removed) and partial ones (specific parameters removed while methods remain).
  • Removal: Following the migration period, deprecated elements are removed in alignment with semantic versioning standards, potentially including breaking changes in minor version updates while Model Optimizer remains in 0.x.

Contributing

Model Optimizer is now open source! We welcome any feedback, feature requests and PRs. Please read our Contributing guidelines for details on how to contribute to this project.

AI Agents

For AI-assisted development setup, see the agent tooling notes.

Top Contributors

Contributors

Happy optimizing!

S
Description
GitHub Trending: NVIDIA/Model-Optimizer
Readme Multiple Licenses
1.2 GiB
Languages
Python 97.3%
Shell 1.3%
Cuda 0.8%
Jinja 0.3%
C++ 0.2%