search

NVIDIA / TensorRT

NVIDIA® TensorRT™ is an SDK for high-performance deep learning inference on NVIDIA GPUs. This repository contains the open source components of TensorRT.
https://developer.nvidia.com/tensorrt
Apache License 2.0
10.81k stars 2.13k forks source link

The yolov5 model has an error in the detection result of tensorrt7.1 #3968

Open Monlter opened 4 months ago

Monlter commented 4 months ago

Description

I am using the official yolov5 model to export onnx, and converting it to engine using trtexec on two devices. The outputs from the two devices are quite different. The output of tensorrt7.1 will output multiple detection boxes for the same target (and the shape of the detection box is similar to the preset anchor, as if no WH adjustment has been made. Surprisingly, their confidence is very high), while the output of tensorrt8.5 is normal. It should be noted that onnx is the same file, and the command to convert it to engine on two devices is: /usr/src/tensorrt/bin/trtexec --onnx=./.onnx --saveEngine=./.engine --workspace=10240 --fp16. In addition, the inference images and codes are the same.

Environment

machine_1: arm JetPack:4.4 TensorRT Version: 7.1.3.0 NVIDIA GPU: Xavier[16GB] CUDA Version: 10.2.89 CUDNN Version: 8.0.0.180

machine_2: x64 TensorRT Version: 8.5.1.7 NVIDIA GPU: A30 CUDA Version: 11.6 CUDNN Version: ***

Operating System: Python Version:3.8 PyTorch Version:1.8.0 onnx Version:1.16.1 This is the detection result on the tensor7.1 device tensorrt7 1

This is the detection result on the tensor8.5 device tensorrt8 5

lix19937 commented 4 months ago

tensorrt7.1 is too old version.

Monlter commented 4 months ago

tensorrt7.1 is too old version. Yes, but machine 1 can only use tensorrt7.1

lix19937 commented 4 months ago

This is the detection result on the tensor7.1 device maybe need nms process. @Monlter

Monlter commented 4 months ago

This is the detection result on the tensor7.1 device maybe need nms process. @Monlter The above results are all post-processed, and the nms threshold is set to 0.4. If the nms threshold is set too small, some boxes can be filtered out, but the boxes with the highest confidence are not in line with actual expectations because they cannot fit the edge of the object. The above results look more like the WH predicted by the model did not work, causing the shape of the result to tend to the shape of the anchor setting.

lix19937 commented 4 months ago

You can check the result with fp32 precision by trt7.1 

/usr/src/tensorrt/bin/trtexec --onnx=./onnx --saveEngine=./.engine --workspace=10240

and mark the result v71-fp32

If v71-fp32 similar with fp16 by trt7.1, maybe trt7.1 has some issue.
If v71-fp32 similar with fp16 by trt8.5, maybe you need compare the each layer output. And you can use polygraphy. @Monlter

Monlter commented 4 months ago

You can check the result with fp32 precision by trt7.1

/usr/src/tensorrt/bin/trtexec --onnx=./onnx --saveEngine=./.engine --workspace=10240

and mark the result v71-fp32

If v71-fp32 similar with fp16 by trt7.1, maybe trt7.1 has some issue. If v71-fp32 similar with fp16 by trt8.5, maybe you need compare the each layer output. And you can use polygraphy. @Monlter

I tried the fp32 conversion method, but the result of tensorrt7.1 remained unchanged.

lix19937 commented 4 months ago

Use follow 

polygraphy run debug.onnx --trt --onnxrt --atol 0.001 --rtol 0.001