Feature/sg 1144 new export in quantization #1511
Merged
Conversation
This file contains 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
BloodAxe
requested review from
shaydeci,
ofrimasad and
Louis-Dupont
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds support to export YoloNAS/PPYoloE/YoloX models (That implements ExportableObjectDetectionModel) while using PTQ/QAT models.
Tested both on YoloNAS-S
Side note:
Currently we export model with
preprocessing=False(Because we calibrated model using validation dataloader that already performed normalization) andpostprocessing=Truebecause users interested in end-to-end model.However, maybe it make sense to introduce
export_paramssection to give users mode control on export process (Choose max number of detections, batch/flat format, TRT or ONNX nms)