-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Error creating tensorrt engine for Single class #7
Comments
@Hidayat722 Did you adapt the |
Yeah i did it but still having problems. Anyhow when i use yolov3-spp.cfg it works which is fine i can use this configuration for training. Anyhow my main concern is that i want to use this engine file with deepstream but i am unable to use it. Since the infer function is different with nvdsparsecustomyolov3 custom function in deepstream, Any solution or suggestion would be appreciated. |
@Hidayat722 I never used deepstream, so not able to help you with it. For yolov3-spp-1cls, you should adapt several layers, including conv88, conv100 and conv112, change their output channels to 18. Can you try it? |
Well i have instead used the yolov3-spp.cfg for training since it converts to engine file but i am struggline with deepstream thanks for your help |
Hi @wang-xinyu i tried for the single class as you mentioned above but i am getting error with concatenation len 1024 Thanks |
Hi @wang-xinyu I also tried the new version where the outputs have been changed to 3 * (Yolo::CLASS_NUM + 5) but still i am getting the same error for yolov3-spp-1cls.cfg. Any help would be appreciated. Thanks. |
@Hidayat722 What's the input shape are you using? the input H and W should be divisible by 32. |
@wang-xinyu Thanks alot the trick worked for me |
Hi,
I am unable to create tensorrt engine using the default parameters for single class config "yolov3-spp-1cls.cfg. i have also tried different height and width but still not able to produce engine it fails at the serialization step. any help would be appreciated.
Thanks in Advance
The text was updated successfully, but these errors were encountered: