Software Version
DRIVE OS 6.0.8.1
Target Operating System
Linux
I am experiencing an issue when converting an ONNX model to a TensorRT engine using trtexec. The conversion fails when the input resolution is large.
Issue Description
I attempted to convert an ONNX model with an input resolution of width 1600 and height 800 using trtexec. The conversion failed with the following error message:
Could not find any implementation for node /AveragePool_1.
[optimizer.cpp::computeCosts::3897] Error Code 10: Internal Error (Could not find any implementation for node /AveragePool_1.)
Engine could not be created from network
Building engine failed
■Relevant Logs Around /AveragePool_1 Layer
=============== Computing costs for /AveragePool_1
*************** Autotuning format combination: Float(400,400,400,1) → Float(200,200,200,1) ***************
Skipping CudnnPooling: No valid tactics for /AveragePool_1
--------------- Timing Runner: /AveragePool_1 (CaskPooling[0x8000002f])
Skipping tactic 0x933eceba7b866d59 due to exception Cask Pooling Runner Execute Failure
Skipping tactic 0xba33c80addb15739 due to exception Cask Pooling Runner Execute Failure
/AveragePool_1 (CaskPooling[0x8000002f]) profiling completed in 0.118985 seconds. Fastest Tactic: 0xd15ea5edd15ea5ed Time: inf
*************** Autotuning format combination: Float(400,1:4,400,1) → Float(200,1:4,200,1) ***************
--------------- Timing Runner: /AveragePool_1 (CaskPooling[0x8000002f])
Skipping tactic 0xfab3e2ee1c085a9a due to exception Cask Pooling Runner Execute Failure
/AveragePool_1 (CaskPooling[0x8000002f]) profiling completed in 0.229153 seconds. Fastest Tactic: 0xd15ea5edd15ea5ed Time: inf
■Questions
1.The logs show multiple occurrences of the message “Cask Pooling Runner Execute Failure” related to the /AveragePool_1 layer. Is this the direct cause of the conversion failure?
2.When I reduce the input resolution to width 1600 and height 384, the conversion succeeds. Can I conclude that the large input resolution is the cause of the failure?
If so, are there any known limitations on input resolution size when converting models using trtexec?