-
Notifications
You must be signed in to change notification settings - Fork 124
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
Compilation failed due to large activation tensors in model #449
Comments
Please try with tensorflow==2.5.0 and let us know if unable to compile the model. |
@hjonnala I quickly reran the process with the suggestion, but the problem still persists. Thanks! |
u should use -a -d flags and wait it should work |
i check it and it works
|
@taloot This is great and the issue is resolved. But one question though, for every step I received the below error. I hope you got a similar one even though the final conversion was successful. Kindly confirm. Thanks! Try to compile segment with 16 ops |
yes sure but what we care most is having working sloution, |
Thanks for your timely response! |
Description
I am trying to edge compile yolov5s with a resolution of 512(only one class), but every time the compilation process results in "Compilation failed due to large activation tensors in model". I was referring to the previous issue #405 and there looks like @taloot and @pirazor were able to execute the models with image sizes 512 & 416 respectively. But I am not sure what I am missing, I used the tf.py from zldrobit to make the conversion. Please let me know why the compilation fails.
Notebook used, custom yaml file, best.pt, int8 tflite are present here - https://drive.google.com/drive/folders/16Q76WeIKSF6FlqUJ86HOWDTC1Hi8pvJt?usp=sharing
Notes: For now I have used the publically dataset from roboflow(due to privacy concerns could not share the actual weight). But the problem is same for both. Thanks
Issue Type
Bug
Operating System
Windows 10
Coral Device
USB Accelerator
Other Devices
Rapsberry Pi 4
Programming Language
Python 3.9
Relevant Log Output
The text was updated successfully, but these errors were encountered: