Fix duplicated input node issue in TensorRT 8.6 ONNX export #4137
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Fix duplicated input node issue in TensorRT 8.6 ONNX export.
This PR addresses a problem where exporting ONNX models using TensorRT 8.6 results in two input nodes being generated. The root cause of the issue is that unused graph inputs are not being removed during the export process. By adding the parameter
remove_unused_graph_inputs=True
in thegraph.cleanup()
method, this PR ensures that only the necessary input nodes are preserved in the final ONNX model.Changes
cleanup
method in the ONNX export process to includeremove_unused_graph_inputs=True
to remove unnecessary input nodes.Testing
This fix was tested in the TensorRT 8.6 environment. After applying the changes, ONNX models that previously exhibited the issue of duplicated input nodes were tested and now produce the correct number of input nodes.
Documentation
No changes to documentation are needed as this is a bug fix to the existing ONNX export functionality.
Signed-off-by: Phoenix [email protected]