NVIDIA / NVIDIA/TensorRT

How to interpret output of TensortRT engine inspector?

Open
#4,535 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Module:Quantization triaged
Dominant language
C++
Stars
13.4k
Forks
2.4k
Avg merge
5d 3h
Merged PRs (30d)
2

Description

I have applied post-training quantization to my pretty complex neural network architecture. Now I am using a TRT engine inspector to retrieve information about each individual layer to see if it was quantized or not, as not all layer types and operations are supported for conversion to INT8 by TensorRT.

After collecting layer information and discarding some columns which I do not need I am left with something that I cannot really parse or understand honestly.

I know for a fact the very first layers of my architecture are the very first 3 layers of a ResNet34, so a Convolution, ReLU and MaxPool, followed by another custom convolutional bloc. Why do the first 4 layers in my quantized model show up as having LayerType Constant, Reformat, Constant and Reformat respectively? With names like onnx::Conv_1063, Identity_76, onnx::Conv_1062 and Identity_77?

I have been so far unable to find a guide on how to interpret these LayerTypes unfortunately.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked TensorRT EngineInspector API reference and compare its documented output with the four reported LayerType values: Constant, Reformat, Constant, and Reformat. Review how the inspector represents the first ResNet34 layers and define what a guide must explain so users can identify quantized layers; done means a clear interpretation guide with a reproducible example.

Written by the indexing model from the issue text.

Assessment

Domain
machine-learning
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.