-
Notifications
You must be signed in to change notification settings - Fork 240
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
[Good First Issue][NNCF]: [TorchFX] Test PTQ MinMax parameters #2873
Comments
.take |
Thank you for looking into this issue! Please let us know if you have any questions or require any help. |
Hi, @rk119 , do you still plan to contribute? |
Yes. I do. |
@rk119 do you need any help with task? do not hesitate to ask :) |
if you want to continue we can wait for you, thanks :) |
Oh alright, thank you so much! |
Hi @daniil-lyakhov, I am facing an issue trying to implement test_unified_scales_command_creation . I am unable to verify and access the quantizer parameters in check_unified_scale_layout, since the create_unified_scales_quantizers_insertion_commands in Torch FX backend returns transformations with only params |
Hi @rk119, please use the |
Ah yes! Thank you. :) |
Hi @daniil-lyakhov, I noticed that in the example reference test for this issue, the test_range_estimator_per_channel parameter in the |
Hi @rk119, please just skip this key in the FX tests implementation and keep other tests as it is |
Hi @daniil-lyakhov, I opened a PR #2989 for this issue. |
### Changes New test file added in tests/torch/fx. Implemented TemplateTestPTQParams for PTQ MinMax for TorchFX backend. ### Related tickets #2873
@rk119, thanks for the contribution! |
Greetings🐱! As a part of #2766 TorchFX PTQ backend support, we are gladly presenting to you following issue:
Implement TemplateTestPTQParams, TemplateTestQuantizerConfig as it done for other backends(example: https://github.com/openvinotoolkit/nncf/blob/develop/tests/torch/ptq/test_ptq_params.py)
Example Pull Requests
#2856
Resources
Contact points
@daniil-lyakhov
Ticket
#2766
The text was updated successfully, but these errors were encountered: