Monocular Depth with TAO Deploy#
To generate an optimized NVIDIA® TensorRT™ engine for NvDepthAnythingV2, the
gen_trt_engine action takes an ONNX file previously produced by the NvDepthAnythingV2
export action. For more information about training a NvDepthAnythingV2 model, refer to the
section Monocular Depth Estimation.
Converting the NvDepthAnythingV2 .onnx file into TensorRT Engine#
You can reuse the spec from the NvDepthAnythingV2 export action as a starting point.
gen_trt_engine#
The gen_trt_engine parameter defines TensorRT engine generation.
gen_trt_engine:
onnx_file: /path/to/onnx_file
trt_engine: /path/to/trt_engine
tensorrt:
data_type: fp16
workspace_size: 1024
min_batch_size: 1
opt_batch_size: 4
max_batch_size: 8
Field |
value_type |
Description |
default_value |
valid_min |
valid_max |
valid_options |
automl_enabled |
|---|---|---|---|---|---|---|---|
|
string |
Path to where all the assets generated from a task are stored. |
FALSE |
||||
|
int |
Index of the GPU to build the TensorRT engine. |
0 |
FALSE |
|||
|
string |
Path to the ONNX model file. |
??? |
FALSE |
|||
|
string |
Path where the generated TensorRT engine from |
FALSE |
||||
|
int |
Number of channels in the input tensor. |
3 |
3 |
FALSE |
||
|
int |
Operator set version of the ONNX model used to generate the TensorRT engine. |
17 |
1 |
FALSE |
||
|
int |
The batch size of the input tensor for the engine.
A value of |
-1 |
-1 |
FALSE |
||
|
bool |
Flag to enable verbose TensorRT logging. |
False |
FALSE |
|||
|
collection |
Hyperparameters to configure the TensorRT Engine builder. |
FALSE |
tensorrt#
The tensorrt parameter defines the TensorRT engine generation.
Field |
value_type |
Description |
default_value |
valid_min |
valid_max |
valid_options |
automl_enabled |
|---|---|---|---|---|---|---|---|
|
string |
The precision to be set for building the TensorRT engine. |
FP32 |
FP32,FP16 |
FALSE |
||
workspace_size |
int
|
The size in megabytes of the workspace TensorRT has
to run its optimization tactics and generate the
TensorRT engine.
|
1024
|
FALSE
|
|||
min_batch_size |
int
|
The minimum batch size in the optimization profile for
the input tensor of the TensorRT engine.
|
1
|
FALSE
|
|||
opt_batch_size |
int
|
The optimum batch size in the optimization profile for
the input tensor of the TensorRT engine.
|
1
|
FALSE
|
|||
max_batch_size |
int
|
The maximum batch size in the optimization profile for
the input tensor of the TensorRT engine.
|
1
|
FALSE
|
Ask the agent to run the gen_trt_engine action against your spec. For example:
Build an FP16 TensorRT engine for NvDepthAnythingV2 from the exported
ONNX at ``s3://my-bucket/depth/model.onnx`` using ``trt-spec.yaml``.
Write the engine to ``s3://my-bucket/depth/model.engine``. Run on the local Docker daemon.
Running Evaluation through a TensorRT Engine#
You can reuse the TAO evaluation specification file for evaluation through a TensorRT engine. This is a sample specification file:
evaluate:
trt_engine: /path/to/engine/file
input_width: 924
input_height: 518
dataset:
test_dataset:
data_sources:
- dataset_name: RelativeMonoDataset
data_file: /data/depth_net/annotation_test.txt
workers: 4
batch_size: 4
Ask the agent to run the evaluate action against the engine you built. For example:
Evaluate the NvDepthAnythingV2 TensorRT engine at
``s3://my-bucket/depth/model.engine`` against ``eval-spec.yaml``. Run on
local Docker.
Running Inference through a TensorRT Engine#
You can reuse the TAO inference specification file for inference through a TensorRT engine. This is a sample specification file:
inference:
conf_threshold: 0.5
input_width: 960
input_height: 544
trt_engine: /path/to/engine/file
color_map:
"black cat": green
car: red
person: blue
dataset:
infer_dataset:
data_sources:
- dataset_name: RelativeMonoDataset
data_file
workers: 4
batch_size: 4
Ask the agent to run the inference action against the engine you built. For example:
Run NvDepthAnythingV2 inference with the TensorRT engine at
``s3://my-bucket/depth/model.engine`` using ``infer-spec.yaml``. Run on
your chosen backend.
Annotated visualizations are written to images_annotated under the configured results
directory, and predictions are written to labels.