Remove quantization_config in config.json from original deepseek models #753
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Zhiyu Cheng <zhiyuc@nvidia.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #753 +/- ##
=======================================
Coverage 74.66% 74.66%
=======================================
Files 192 192
Lines 18975 18975
=======================================
Hits 14167 14167
Misses 4808 4808 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
cjluo-nv
approved these changes
Jan 13, 2026
kevalmorabia97
pushed a commit
that referenced
this pull request
Jan 15, 2026
…ls (#753) ## What does this PR do? **Type of change:** Bug fix **Overview:** DeepSeek original checkpoints may include a `quantization_config` field in `config.json` (describing the source checkpoint's quantization). When we export ModelOpt quantization configs to `hf_quant_config.json`, leaving the original `quantization_config` in place can be confusing. Add a function to remove it. ## Usage <!-- You can potentially add a usage example below. --> ```python # Add a code snippet demonstrating how to use this ``` ## Testing <!-- Mention how have you tested your change if applicable. --> ## Before your PR is "*Ready for review*" <!-- If you haven't finished some of the above items you can still open `Draft` PR. --> - **Make sure you read and follow [Contributor guidelines](https://github.com/NVIDIA/Model-Optimizer/blob/main/CONTRIBUTING.md)** and your commits are signed. - **Is this change backward compatible?**: Yes <!--- If No, explain why. --> - **Did you write any new necessary tests?**: Yes/No - **Did you add or update any necessary documentation?**: Yes/No - **Did you update [Changelog](https://github.com/NVIDIA/Model-Optimizer/blob/main/CHANGELOG.rst)?**: Yes/No <!--- Only for new features, API changes, critical bug fixes or bw breaking changes. --> ## Additional Information Resolve nvbug https://nvbugspro.nvidia.com/bug/5736665 --------- Signed-off-by: Zhiyu Cheng <zhiyuc@nvidia.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
Type of change: Bug fix
Overview: DeepSeek original checkpoints may include a
quantization_configfield inconfig.json(describing the source checkpoint's quantization). When we export ModelOpt quantization
configs to
hf_quant_config.json, leaving the originalquantization_configin place canbe confusing. Add a function to remove it.
Usage
# Add a code snippet demonstrating how to use thisTesting
Before your PR is "Ready for review"
Additional Information
Resolve nvbug https://nvbugspro.nvidia.com/bug/5736665