-
Notifications
You must be signed in to change notification settings - Fork 234
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
Failed to export NNCF QAT model for Ultralytics YOLOv8 #2846
Comments
Hello @quinnZE! I could not run your code because I faced with the error:
Please provide a working reproducer. I also checked the code from the issue #2486 with the last NNCF and did not face the provided error. |
My apologies @alexsu52, I am using a modified repo that forks Ultralytics, causing the import issue. Below I have provided an updated snippet. I will also try to replicate with vanilla Ultralytics on my end and see if the issue appears as it may be due to one of my custom modifications, though I don't believe I have done much to edit the Batch Normalization
|
@alexsu52 I have updated the code and used vanilla Ultralytics and I am still encountering the same error during export with both the previous versions and the update versions from the original issue:
Here is the complete code and traceback for my most recent run. This should run on any machine installed with the proper packages.
Error trace:
|
Hello @quinnZE, After analyzing your code, I found that you are trying to export the model after the final validation. I would note that
|
Ah I completely overlooked that, thank you! Everything works as expected now. Final code snippet of working export setup
|
🐛 Describe the bug
I am currently attempting to train and export an Ultralytics YOLOv8 Large model using NNCF QAT. I used the code referenced in issue 2486 to implement training and exporting.
The training proceeded normally with the exception that the validation scores remained stagnant regardless of loss changes. However, when attempting to export I received the following.
The text was updated successfully, but these errors were encountered: