[6008361][ONNX][Quantization] Clarify autotune guidance#1989
Conversation
Signed-off-by: Gwenaelle Cunha Sergio <gcunhasergio@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1989 +/- ##
==========================================
- Coverage 77.40% 76.41% -1.00%
==========================================
Files 524 524
Lines 59267 59649 +382
==========================================
- Hits 45873 45578 -295
- Misses 13394 14071 +677
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Signed-off-by: Gwenaelle Cunha Sergio <gcunhasergio@nvidia.com>
Signed-off-by: Gwenaelle Cunha Sergio <gcunhasergio@nvidia.com>
Signed-off-by: Gwenaelle Cunha Sergio <gcunhasergio@nvidia.com>
Signed-off-by: Gwenaelle Cunha Sergio <gcunhasergio@nvidia.com>
Signed-off-by: Gwenaelle Cunha Sergio <gcunhasergio@nvidia.com>
What does this PR do?
Type of change: documentation
This PR clarifies when users should use ONNX quantization with Autotune enabled versus the direct Autotune entry point.
autotune=Truein the Python API and explain that it uses default Autotune settings.python -m modelopt.onnx.quantization ... --autotune=<mode>for accuracy-sensitive PTQ from an unquantized model.Usage
Testing
python -m py_compile modelopt/onnx/quantization/autotune/__main__.py.python -m sphinx -b html docs/source docs/build/html; build succeeded. Remaining warnings are from optional documentation imports and existing cross-reference labels.Before your PR is "Ready for review"
Make sure you read and follow Contributor guidelines and your commits are signed (
git commit -s -S).Make sure you read and follow the Security Best Practices (e.g. avoiding hardcoded
trust_remote_code=True,torch.load(..., weights_only=False),pickle, etc.).CONTRIBUTING.md: N/A