Working With Models

In order to understand how to properly prepare a model for use in a pipeline, let’s first go over the main configuration elements responsible for the model inference. Some parameters have been omitted for simplicity, but you will learn about specific and necessary parameters for specific types of models in dedicated sections.

The listing below represents a typical Savant inference node:

- element: nvinfer@detector
  name: DetectionModel
  model:
    format: etlt
    remote:
      url: "https://127.0.0.1/models/detection_model.zip"
    local_path: /opt/aispp/models/detection_model
    model_file: resnet18_dashcamnet_pruned.etlt
    engine_file: resnet18.etlt_b1_gpu0_int8.engine
    batch_size: 1
    precision: int8
    int8_calib_file: dashcamnet_int8.txt
    mean_file: mean.ppm
    input:
      layer_name: input_1
      shape: [3, 544, 960]
      scale_factor: 0.00392156862745098
    output:
      layer_names: [output_cov/Sigmoid, output_bbox/BiasAdd]

The element section specifies the type of a pipeline unit. There are 4 types of units for defining models: detector, classifier, attribute_model, instance_segmentation, and complex_model.

The name parameter defines the name of the unit. The name is used by the downstream pipeline units to refer to the objects that the unit produces. This parameter is also used to construct the path to the model files, see the local_path parameter.

The format parameter specifies the format in which the model is provided. The supported formats and the peculiarities of specifying certain parameters depending on the model format are described below.

The model_file parameter defines the name of the file with the model. The name is specified as a base name, not a full path.

The engine_file parameter defines the name for the TensorRT-generated engine file. If this parameter is set, then when the pipeline is launched, the presence of this file is checked first, and if it is present, the model will be loaded from it.

If the prepared model file does not exist, then the pipeline will generate the engine for the model with the name. If you are not using a specially generated, pre-created TensorRT engine file, it is recommended not to set this field: the name will be generated automatically.

The remote section specifies a URL and credentials for accessing a remote model storage. Full description below. Savant supports downloading the models from remote locations so you can easily update them without rebuilding docker images.

The local_path parameter specifies the path to the model files. It can be omitted, then the path will be automatically generated according to the following rule <model_path>/<name>, where <model_path> is a global parameter specifying the location of all model files, set in the parameters section (description), and <name> is the name of the element.

The batch_size parameter defines a batch size dimension for processing frames by the model (by default 1).

The precision parameter defines a precision of the model weights. Possible values are fp32, fp16, int8. This parameter is set according to the precision chosen when creating the model.

The int8_calib_file defines the name of the calibration file in case the model has int8 precision.

The mean_file parameter defines the name of the file with the mean values for data preprocessing. The file must be in PPM format. It makes sense to use this file if you already have it, in general, it is easier to specify the necessary mean values and scaling factor for preprocessing in the input section.

The input section describes the model input: names of input layers, dimensionality, etc. The mandatory or optional nature of the parameters in this section depends on the model format, as well as on the type of model. This section will be covered in more detail later, when describing model formats or types of models.

The output section describes the model output: names of output layers, converters, selectors, etc. The mandatory or optional nature of the parameters in this section depends on the model format, as well as on the type of model. This section will be covered in more detail later, when describing model formats.

To accelerate inference in the framework, Nvidia TensorRT is used. To use a model in a pipeline, it must be presented in one of the formats supported by TensorRT:

ONNX

ONNX is an open format built to represent machine learning models. ONNX defines a common set of operators - the building blocks of machine learning and deep learning models - and a common file format to enable AI developers to use models with a variety of frameworks, tools, runtimes, and compilers. This format is recommended as the to-go format for models.

To export a model from one of the most popular frameworks, you can refer to the instructions or examples provided below:

• PyTorch;

• TensorFlow;

• MXNet.

Usage example:

- element: nvinfer@detector
  name: DetectionModel
  model:
    format: onnx
    model_file: detection_model.onnx

If the model has non-standard outputs (outputs that cannot be automatically converted by DeepStream into meta information), then it is also necessary to specify the name or names of the output layers in the output section.

- element: nvinfer@detector
  name: DetectionModel
  model:
    format: onnx
    model_file: detection_model.onnx
    output:
      layer_names: [output]

UFF

UFF is an intermediate format for representing a model between TensorFlow and TensorRT. Users who use the TensorFlow framework can convert their models to the UFF format using the UFF converter. If you are using a model in the UFF format, you must specify the name of the input layer (layer_name) and the input dimensionality of the model (shape) in the input section, as well as the name(s) of the resulting layer(s) (layer_names) in the output section.

- element: nvinfer@detector
  name: DetectionModel
  model:
    format: uff
    model_file: detection_model.uff
    input:
      layer_name: input_1
      shape: [3, 544, 960]
    output:
      layer_names: [output_cov/Sigmoid, output_bbox/BiasAdd]

This format will no longer be supported by future releases of TensorRT (Tensor RT release notes).

Caffe

If you have a model trained using the Caffe framework, then you can save your model in the caffemodel format.

- element: nvinfer@detector
  name: DetectionModel
  model:
    format: caffe
    model_file: detection_model.caffemodel
    proto_file: resnet.prototxt
    output:
      layer_names: [output_cov/Sigmoid, output_bbox/BiasAdd]

This format will no longer be supported by future releases of TensorRT (Tensor RT release notes).

Nvidia TAO Toolkit

The NVIDIA TAO Toolkit is a set of training tools that requires minimal effort to create computer vision neural models based on user’s own data. Using the TAO toolkit, users can perform transfer learning from pre-trained NVIDIA models to create their own model.

After training the model, you can download it in the etlt format and use this file for model inference in the Savant framework. If you are using a model in the etlt format, you must specify the name of the input layer (layer_name) and the input dimensionality of the model (shape) in the input section, as well as the name(s) of the resulting layer(s) (layer_names) in the output section.

- element: nvinfer@detector
  name: DetectionModel
  model:
    format: etlt
    model_file: detection_model.etlt
    input:
      layer_name: input_1
      shape: [3, 544, 960]
    output:
      layer_names: [output_cov/Sigmoid, output_bbox/BiasAdd]

Custom CUDA Engine

For all the above-mentioned variants of specifying the model, during the first launch, an engine file will be generated using TensorRT with automatic parsing of the model. When the model is very complex or requires some custom plugins or layers, you can generate the engine file yourself using the TensorRT API and specifying the library and the name of the function that generates the engine (Using custom model with deepstream).

- element: nvinfer@detector
  name: DetectionModel
  model:
    format: custom
    custom_config_file: yolov2-tiny.cfg
    custom_lib_path: libnvdsinfer_custom_impl_Yolo.so
    engine_create_func_name: NvDsInferYoloCudaEngineGet

Working With Remote Models

Currently, there are three data transfer protocols supported: S3, HTTP(S), and FTP. By specifying the URL of the archive file, you can use models that are stored remotely.

- element: nvinfer@detector
  name: Primary_Detector
  model:
    format: caffe
    config_file:  ${oc.env:APP_PATH}/samples/nvidia_car_classification/dstest2_pgie_config.txt
    remote:
      url: s3://savant-data/models/Primary_Detector/Primary_Detector.zip
      checksum_url: s3://savant-data/models/Primary_Detector/Primary_Detector.md5
      parameters:
        endpoint: https://eu-central-1.linodeobjects.com

In this example, in the remote section, we specify:

• url - specifies where to download the archive file from;

• checksum_url - specifies the file that stores the md5 checksum for the archive; if the archive has not been updated, it will not be downloaded during the next module launch;

• parameters - a section that allows you to specify additional parameters for the S3, HTTP(S), or FTP protocols:

  • S3 protocol parameters: access_key, secret_key, endpoint, region;

  • HTTP(S) protocol parameters: username, password;

  • FTP protocol parameters: username, password.

All necessary files (model file in one of the formats described above, configuration, calibration, and other files that you specify when configuring the model) must be archived using one of the archivers (gzip, bzip2, xz, zip). The must should contain all required model files.

The archive should contain a set of files. You can download an example model archive used in the Nvidia car classification example with the following command:

aws --endpoint-url=https://eu-central-1.linodeobjects.com s3 cp s3://savant-data/models/Primary_Detector/Primary_Detector.zip .

You can find an example of using this model archive at the following link.