-
-
Notifications
You must be signed in to change notification settings - Fork 370
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
No detection with int8 #336
Comments
Deepstream 6.2, gst-nvinfer, yolov8, int8 - nearly zero detections after calibration too. 1% of detections available. Calibration was with 1.5k images from the training dataset and batch size 7. Fp32 and fp16 work ok, however even fp32 is a bit worse than just running through pytorch. I dream about high-quality yolov8 int8. P.S. Author, big thanks for the repo! |
It's that I thought my yolov8 programs with TensorRT engine in GPU gives me very better results in Fp16 with an easy display possibility and performance of 10-15 ms / 15-16 fps / 10-15 Watts in processing by Frame |
I found this if it can help someone ,you can use python apps with examples for Deepstream sur le repository de nvidia :https://github.com/NVIDIA-AI-IOT/deepstream_python_apps/tree/master |
For now, the INT8 calibration is a basic implementation. My plan is to optimize it in the future.
The |
Thanks for the answer! We are gradually building the test suit to do educated validation. Can't wait for good int8 |
I did some small adjusts in the INT8 calibration (PTQ) and it is also available for ONNX exported models now. In the future, I'm planing to add the QAT method to get better accuracy. |
Thanks, we will try! |
Hello every one
I allow myself to ask for your help, I followed the tutorial to switch to int8 everything sucked well to create not without difficulty but I do have a model model_b1_gpu0_int8.engine which was created but the problem is that the video is launches but NO DETECTION
PS: on the screen all go well in fp32 I specify, I work on an nvidia 6.2 trion docker
Cordially
The text was updated successfully, but these errors were encountered: