-
Notifications
You must be signed in to change notification settings - Fork 517
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug/sg 861 decouple qat from train from config #1001
Bug/sg 861 decouple qat from train from config #1001
Conversation
…in_from_config' into bug/SG-861_decouple_qat_from_train_from_config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great!
I wrote a small note about naming (non-blocking)
Other than that I think we should also add this as a "quickstart" section in the ptq/qat tutorial: https://github.com/Deci-AI/super-gradients/blob/master/documentation/source/ptq_qat.md
…in_from_config' into bug/SG-861_decouple_qat_from_train_from_config
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great like that
I think there might be one bug though, see below, and the rest is just minor comments
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
* adde unit tests * changed local * switch to ema model before quantization if exists * midifying method complete * midifying method cal in pre launch callback * removed option to get the defaults from previous training * added unit tests passing * updated docs and test names * moved logger init * comments resolved
This PR decouples QAT/PTQ from train_from_config.
The goal is to let users launch PTQ/QAT using Python instead of CLI + configs, while using as much defaults as possible.
Note that automatic adaptation of the parameters using the best practices is the users responsibilty when they choose to launch this way, since the new "quantize" method I added can expect objects rather then parameters.