YOLOv4 ====== .. _yolo_v4: YOLOv4 is an object detection model that is included in the Transfer Learning Toolkit. YOLOv4 supports the following tasks: * kmeans * train * evaluate * inference * prune * export These tasks can be invoked from the TLT launcher using the following convention on the command line: .. code:: tlt yolo_v4 where :code:`args_per_subtask` are the command line arguments required for a given subtask. Each subtask is explained in detail below. Creating a Configuration File ----------------------------- .. _creating_a_configuration_file_yolo_v4: Below is a sample for the YOLOv4 spec file. It has 6 major components: :code:`yolov4_config`, :code:`training_config`, :code:`eval_config`, :code:`nms_config`, :code:`augmentation_config`, and :code:`dataset_config`. The format of the spec file is a protobuf text (prototxt) message, and each of its fields can be either a basic data type or a nested message. The top-level structure of the spec file is summarized in the table below. .. code:: random_seed: 42 yolov4_config { big_anchor_shape: "[(114.94, 60.67), (159.06, 114.59), (297.59, 176.38)]" mid_anchor_shape: "[(42.99, 31.91), (79.57, 31.75), (56.80, 56.93)]" small_anchor_shape: "[(15.60, 13.88), (30.25, 20.25), (20.67, 49.63)]" box_matching_iou: 0.25 arch: "resnet" nlayers: 18 arch_conv_blocks: 2 loss_loc_weight: 0.8 loss_neg_obj_weights: 100.0 loss_class_weights: 0.5 label_smoothing: 0.0 big_grid_xy_extend: 0.05 mid_grid_xy_extend: 0.1 small_grid_xy_extend: 0.2 freeze_bn: false freeze_blocks: 0 force_relu: false } training_config { batch_size_per_gpu: 8 num_epochs: 80 enable_qat: false checkpoint_interval: 10 learning_rate { soft_start_cosine_annealing_schedule { min_learning_rate: 1e-7 max_learning_rate: 1e-4 soft_start: 0.3 } } regularizer { type: L1 weight: 3e-5 } optimizer { adam { epsilon: 1e-7 beta1: 0.9 beta2: 0.999 amsgrad: false } } pretrain_model_path: "EXPERIMENT_DIR/pretrained_resnet18/tlt_pretrained_object_detection_vresnet18/resnet_18.hdf5" } eval_config { average_precision_mode: SAMPLE batch_size: 8 matching_iou_threshold: 0.5 } nms_config { confidence_threshold: 0.001 clustering_iou_threshold: 0.5 top_k: 200 } augmentation_config { hue: 0.1 saturation: 1.5 exposure:1.5 vertical_flip:0 horizontal_flip: 0.5 jitter: 0.3 output_width: 1248 output_height: 384 output_channel: 3 randomize_input_shape_period: 0 mosaic_prob: 0.5 mosaic_min_ratio:0.2 image_mean { key: 'b' value: 103.9 } image_mean { key: 'g' value: 116.8 } image_mean { key: 'r' value: 123.7 } } dataset_config { data_sources: { label_directory_path: "/workspace/tlt-experiments/data/training/label_2" image_directory_path: "/workspace/tlt-experiments/data/training/image_2" } include_difficult_in_training: true target_class_mapping { key: "car" value: "car" } target_class_mapping { key: "pedestrian" value: "pedestrian" } target_class_mapping { key: "cyclist" value: "cyclist" } target_class_mapping { key: "van" value: "car" } target_class_mapping { key: "person_sitting" value: "pedestrian" } validation_data_sources: { label_directory_path: "/workspace/tlt-experiments/data/val/label" image_directory_path: "/workspace/tlt-experiments/data/val/image" } } Training Config ^^^^^^^^^^^^^^^ .. _training_config_yolo_v4: The training configuration (:code:`training_config`) defines the parameters needed for training, evaluation, and inference. Details are summarized in the table below. +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | **Field** | **Description** | **Data Type and Constraints** | **Recommended/Typical Value** | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | batch_size_per_gpu | The batch size for each GPU; the effective batch size is | Unsigned int, positive | -- | | | batch_size_per_gpu * num_gpus | | | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | checkpoint_interval | The number of training epochs per one model checkpoint/validation | Unsigned int, positive | 10 | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | num_epochs | The number of epochs to train the network | Unsigned int, positive. | -- | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | enable_qat | Whether to use quantization-aware training | Boolean | **Note**: YOLOv4 does not support loading a pruned QAT model and retraining | | | | | it with QAT disabled, or vice versa. For example, to get a pruned QAT model, | | | | | perform the initial training with QAT enabled or :code:`enable_qat=True`. | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | learning_rate | One soft_start_annealing_schedule and soft_start_cosine_annealing_schedule with | Message type | -- | | | the following nested parameters are supported: | | | | | | | | | | 1. min_learning_rate: The minimum learning late during the entire experiment | | | | | 2. max_learning_rate: The maximum learning rate during the entire experiment | | | | | 3. soft_start: The time to lapse before warm up (expressed as a percentage of | | | | | progress between 0 and 1) | | | | | 4. annealing: (**only for soft_start_annealing_schedule**) The time to start | | | | | annealing the learning rate | | | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | regularizer | This parameter configures the regularizer to use while training and contains | Message type | L1 (Note: NVIDIA suggests using the L1 regularizer when training a network | | | the following nested parameters: | | before pruning, as L1 regularization makes the network weights more | | | | | prunable.) | | | 1. type: The type of regularizer to use. NVIDIA supports NO_REG, L1, or L2. | | | | | 2. weight: The floating point value for regularizer weight | | | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | optimizer | The optimizer can be one of adam, sgd, and rmsprop. Each type has the | Message type | -- | | | following parameters: | | | | | | | | | | 1. adam: epsilon, beta1, beta2, amsgrad | | | | | 2. sgd: momentum, nesterov | | | | | 3. rmsprop: rho, momentum, epsilon, centered | | | | | | | | | | The meanings of above parameters are same as those in Keras_. | | | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | pretrain_model_path | The path to the pretrained model, if any | String | -- | | | | | | | | At most, one pretrain_model_path, resume_model_path, and pruned_model_path may be | | | | | present. | | | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | resume_model_path | The path to the TLT checkpoint model to resume training, if any | String | -- | | | | | | | | At most, one pretrain_model_path, resume_model_path, and pruned_model_path may be | | | | | present. | | | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | pruned_model_path | The path to the TLT pruned model for re-training, if any | String | -- | | | | | | | | At most, one pretrain_model_path, resume_model_path, and pruned_model_path may be | | | | | present. | | | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | max_queue_size | The number of prefetch batches in data loading | Unsigned int, positive | -- | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | n_workers | The number of workers for data loading per GPU | Unsigned int, positive | -- | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ | use_multiprocessing | Whether to use multiprocessing mode of keras sequence data loader | Boolean | true (in case of deadlock, restart training and use False) | +---------------------+---------------------------------------------------------------------------------------+-------------------------------+-------------------------------------------------------------------------------+ .. Note:: The learning rate is automatically scaled with the number of GPUs used during training, or the effective learning rate is :code:`learning_rate * n_gpu`. .. _Keras: keras.io/api/optimizers Evaluation Config ^^^^^^^^^^^^^^^^^ The evaluation configuration (:code:`eval_config`) defines the parameters needed for the evaluation either during training or standalone evaluation. Details are summarized in the table below. +-----------------------------------+-----------------------------------------------------------------------------+----------------------------------+-------------------------------+ | **Field** | **Description** | **Data Type and Constraints** | **Recommended/Typical Value** | +-----------------------------------+-----------------------------------------------------------------------------+----------------------------------+-------------------------------+ | average_precision_mode | Average Precision (AP) calculation mode can be either SAMPLE or INTEGRATE. | ENUM type ( SAMPLE or INTEGRATE) | SAMPLE | | | SAMPLE is used as VOC metrics for VOC 2009 or before. INTEGRATE is used for | | | | | VOC 2010 or after. | | | +-----------------------------------+-----------------------------------------------------------------------------+----------------------------------+-------------------------------+ | matching_iou_threshold | The lowest IoU of the predicted box and ground truth box that can be | float | 0.5 | | | considered a match | | | +-----------------------------------+-----------------------------------------------------------------------------+----------------------------------+-------------------------------+ NMS Config ^^^^^^^^^^ The NMS configuration (:code:`nms_config`) defines the parameters needed for the NMS postprocessing. NMS config applies to the NMS layer of the model in training, validation, evaluation, inference, and export. Details are summarized in the table below. +------------------------------------------+------------------------------------------------------------------------------------------------+-------------------------------+-------------------------------+ | **Field** | **Description** | **Data Type and Constraints** | **Recommended/Typical Value** | +------------------------------------------+------------------------------------------------------------------------------------------------+-------------------------------+-------------------------------+ | confidence_threshold | Boxes with a confidence score less than confidence_threshold are discarded before applying NMS.| float | 0.01 | +------------------------------------------+------------------------------------------------------------------------------------------------+-------------------------------+-------------------------------+ | cluster_iou_threshold | The IoU threshold below which boxes will go through the NMS process. | float | 0.6 | +------------------------------------------+------------------------------------------------------------------------------------------------+-------------------------------+-------------------------------+ | top_k | top_k boxes will be output after the NMS keras layer. If the number of valid boxes is less | Unsigned int | 200 | | | than k, the returned array will be padded with boxes whose confidence score is 0. | | | +------------------------------------------+------------------------------------------------------------------------------------------------+-------------------------------+-------------------------------+ | infer_nms_score_bits | The number of bits to represent the score values in NMS plugin in TensorRT OSS. The valid range| int. In the interval [1, 10]. | 0 | | | is integers in [1, 10]. Setting it to any other values will make it fall back to ordinary NMS. | | | | | Currently this optimized NMS plugin is only avaible in FP16 but it should also be selected by | | | | | INT8 data type as there is no INT8 NMS in TensorRT OSS and hence this fastest implementation in| | | | | FP16 will be selected. If falling back to ordinary NMS, the actual data type when building the | | | | | engine will decide the exact precision(FP16 or FP32) to run at. | | | +------------------------------------------+------------------------------------------------------------------------------------------------+-------------------------------+-------------------------------+ Augmentation Config ^^^^^^^^^^^^^^^^^^^ The augmentation configuration (:code:`augmentation_config`) defines the parameters needed for online data augmentation. Details are summarized in the table below. +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | **Field** | **Description** | **Data Type and Constraints** | **Recommended/Typical Value** | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | hue | Image hue to be changed within [-hue, hue] * 180.0 | float of [0, 1] | 0.1 | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | saturation | Image saturation to be changed within [1.0 / saturation, saturation] | float >= 1.0 | 1.5 | | | times | | | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | exposure | Image exposure to be changed within [1.0 / exposure, exposure] times | float >= 1.0 | 1.5 | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | vertical_flip | The probability of images to be vertically flipped | float of [0, 1] | 0 | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | horizontal_flip | The probability of images to be horizontally flipped | float of [0, 1] | 0.5 | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | jitter | The maximum jitter allowed in augmentation; "jitter" here refers | float of [0, 1] | 0.3 | | | to jitter augmentation in YOLO networks | | | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | output_width | The base output image width of augmentation pipeline | integer, multiple of 32 | -- | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | output_height | The base output image height of augmentation pipeline | integer, multiple of 32 | -- | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | output_channel | The number of output channels of augmentation pipeline | 1 or 3 | -- | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | randomize_input_shape_period | The batch interval to randomly change the output width and height. | non-negative integer | 10 | | | For value K, the augmentation pipeline will adjust output shape | | | | | per K batches, and the adjusted output width/height will be within | | | | | 0.6 to 1.5 times of the base width/height. | | | | | | | | | | Note: If K=0, the output width/height will always be the exact | | | | | base width/height as configured, and training will be much faster. | | | | | But the accuracy of the trained network might not be as good. | | | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | mosaic_prob | The probability of mosaic augmentation to be applied on one image | float of [0, 1] | 0.5 | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | mosaic_min_ratio | The minimum ratio of width/height one sub-image should occupy | float of (0, 0.5) | 0.2 | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ | image_mean | A key/value pair to specify image mean values. | dict | -- | | | If omitted, ImageNet mean will be used for image preprocessing. | | | | | If set, depending on `output_channel`, either 'r/g/b' or 'l' | | | | | key/value pair must be configured. | | | +------------------------------+----------------------------------------------------------------------+-------------------------------+-------------------------------+ Dataset Config ^^^^^^^^^^^^^^ The following is an example :code:`dataset_config` element: .. code:: dataset_config { data_sources: { label_directory_path: "/workspace/tlt-experiments/data/training/label_2" image_directory_path: "/workspace/tlt-experiments/data/training/image_2" } data_sources: { label_directory_path: "/workspace/tlt-experiments/data/training/label_3" image_directory_path: "/workspace/tlt-experiments/data/training/image_3" } include_difficult_in_training: true target_class_mapping { key: "car" value: "car" } target_class_mapping { key: "pedestrian" value: "pedestrian" } target_class_mapping { key: "cyclist" value: "cyclist" } target_class_mapping { key: "van" value: "car" } target_class_mapping { key: "person_sitting" value: "pedestrian" } validation_data_sources: { label_directory_path: "/workspace/tlt-experiments/data/val/label_1" image_directory_path: "/workspace/tlt-experiments/data/val/image_1" } } The YOLOv4 dataloader assumes the training/validation split is already done and the data is prepared in KITTI format: images and labels are in two separate folders, where each image in the image folder has a :code:`.txt` label file with the same filename in the label folder, and the label file content follows KITTI format. The parameters in :code:`dataset_config` are defined as follows: * :code:`data_sources`: The path to datasets to train on. If you have multiple data sources for training, you may use multiple :code:`data_sources`. This field contains 2 parameters: * :code:`label_directory_path`: The path to the data source label folder. * :code:`image_directory_path`: The path to the data source image folder. * :code:`include_difficult_in_training`: A flag specifying whether to include difficult boxes in training. If set to :code:`false`, difficult boxes will be ignored. Difficult boxes are those with occlusion level 2 in KITTI labels. * :code:`target_class_mapping`: This parameter maps the class names in the labels to the target class to be trained in the network. An element is defined for every source class to target class mapping. This field was included with the intention of grouping similar class objects under one umbrella. For example, "car", "van", "heavy_truck", etc. may be grouped under "automobile". The “key” field is the value of the class name in the tfrecords file, and the “value” field corresponds to the value that the network is expected to learn. * :code:`validation_data_sources`: Captures the path to datasets to validate on. If you have multiple data sources for validation, you may use multiple :code:`validation_data_sources`. Like :code:`data_sources`, this field contains two parameters. .. Note:: The class names key in the :code:`target_class_mapping` must be identical to the one shown in the KITTI labels so that the correct classes are picked up for training. YOLO4 Config ^^^^^^^^^^^^ The YOLOv4 configuration (:code:`yolov4_config`) defines the parameters needed for building the YOLOv4 model. Details are summarized in the table below. +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | **Field** | **Description** | **Data Type and Constraints** | **Recommended/Typical Value** | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | big_anchor_shape, mid_anchor_shape, and small_anchor_shape | These settings should be 1-d arrays inside quotation marks. The elements of those arrays | string | Use the `tlt yolo_v4 kmeans` command to generate | | | are tuples representing the pre-defined anchor shape in the order of "width, height". | | those shapes | | | | | | | | The default YOLOv4 configuration has nine predefined anchor shapes. They are divided into three groups | | | | | corresponding to big, medium, and small objects. The detection output corresponding to | | | | | different groups are from different depths in the network. You should run the :code:`kmeans` | | | | | command (:code:`tlt yolo_v4 kmeans`) to determine the best anchor shapes for your | | | | | dataset and put those anchor shapes in the spec file. It is worth noting that the number of | | | | | anchor shapes for any field is not limited to three; you only need to specify one anchor | | | | | shape in each of those three fields. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | box_matching_iou | This field should be a float number between 0 and 1. Any anchor with at least this IoU to any | float | 0.5 | | | ground truth boxes will be matched to the ground truth box it has the largest IoU with. In contrast with | | | | | YOLOv3, one ground truth box might match to multiple anchors in YOLOv4. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | arch_conv_blocks | Supported values are 0, 1, and 2. This value controls how many convolutional blocks are present | 0, 1 or 2 | 2 | | | among detection output layers. Set this value to 2 if you want to reproduce the meta | | | | | architecture of the original YOLOv4 model paired with DarkNet 53. Note that this config setting | | | | | only controls the size of the YOLO meta-architecture--the size of the feature extractor has | | | | | nothing to do with this config field. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | loss_loc_weight, loss_neg_obj_weights, and loss_class_weights | These loss weights can be configured as float numbers. | float | loss_loc_weight: 5.0 | | | | | loss_neg_obj_weights: 50.0 | | | The YOLOv4 loss is a summation of localization loss, negative objectiveness loss, positive | | loss_class_weights: 1.0 | | | objectiveness loss, and classification loss. The weight of positive objectiveness loss is set to | | | | | 1, while the weights of other losses are read from the config file. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | label_smoothing | Label smoothing applied to classification loss. | float of [0, 0.3] | 0, 0.1, 0.2 | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | big_grid_xy_extend, mid_grid_xy_extend, and small_grid_xy_extend | These settings should be small positive floats. The calculated box center relative to the anchor box | float of [0, 0.3] | 0.05, 0.1, 0.2 | | | will be re-calibrated according to following: | | | | | | | | | | center_xy = calculated_xy * (grid_xy_extend + 1.0) - grid_xy_extend / 2.0 | | | | | | | | | | The default YOLOv4 has nine predefined anchor shapes. They are divided into three groups | | | | | corresponding to big, medium, and small objects. The detection output corresponding to | | | | | different groups are from different depths in the network. The three different grid_xy_extend configs | | | | | allow users to define different grid_xy_extend values for different anchor-shape groups. | | | | | | | | | | The grid_xy_extend settings make it easier for the network to propose an inferenced box with a | | | | | center that is close to or on the anchor border. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | arch | The backbone for feature extraction. Currently, “resnet”, “vgg”, “darknet”, “googlenet”, “mobilenet_v1”, | string | resnet | | | “mobilenet_v2”, "cspdarknet", and “squeezenet” are supported. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | nlayers | The number of conv layers in a specific architecture. For “resnet”, 10, 18, 34, 50 and 101 are | Unsigned int | -- | | | supported. For “vgg”, 16 and 19 are supported. For “darknet” or "cspdarknet", 19 and 53 are supported. | | | | | All other networks don’t have this configuration, in which case you should just delete this config from | | | | | the config file. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | freeze_bn | A flag specifying whether to freeze all batch normalization layers during training. | Boolean | False | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | freeze_blocks | The list of block IDs to be frozen in the model during training. You can choose to freeze some of the | list(repeated integers) | -- | | | CNN blocks in the model to make the training more stable and/or easier to converge. The definition of | | | | | a block is heuristic for a specific architecture (for example, by stride or by logical blocks in the | • ResNet series. For the ResNet series, the block IDs valid for | | | | model). However, the block ID numbers identify the blocks in the model in a sequential order so you | freezing is any subset of [0, 1, 2, 3] (inclusive) | | | | don't have to know the exact locations of the blocks when you do training. A general principle to keep | • VGG series. For the VGG series, the block IDs valid for freezing | | | | in mind is that the smaller the block ID, the closer it is to the model input; the larger the block ID, | is any subset of[1, 2, 3, 4, 5] (inclusive) | | | | the closer it is to the model output. | • GoogLeNet. For the GoogLeNet, the block IDs valid for freezing | | | | | is any subset of[0, 1, 2, 3, 4, 5, 6, 7] (inclusive) | | | | You can divide the whole model into several blocks and optionally freeze a subset of it. Note that for | • MobileNet V1. For the MobileNet V1, the block IDs valid for freezing | | | | FasterRCNN, you can only freeze the blocks that are before the ROI pooling layer. Any layer after the ROI | is any subset of [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11] (inclusive) | | | | pooling layer will not be frozen anyway. For different backbones, the number of blocks and the block ID | • MobileNet V2. For the MobileNet V2, the block IDs valid for freezing | | | | for each block are different. It deserves some detailed explanations on how to specify the block IDs for | is any subset of [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13] (inclusive)| | | | each backbone. | • DarkNet. For the DarkNet 19 and DarkNet 53, the block IDs valid for | | | | | freezing is any subset of [0, 1, 2, 3, 4, 5] (inclusive) | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ | force_relu | A flag specifying whether to replace all activation functions with ReLU. This is useful for training | Boolean | False | | | models for NVDLA. | | | +------------------------------------------------------------------+-----------------------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+-------------------------------------------------------+ Generate anchor shape --------------------- The anchor shape should match most ground truth boxes in the dataset to help the network learn bounding boxes. The YOLOv4 paper proposes using the kmeans algorithm to get the anchor shapes, and the :code:`tlt yolo_v4 kmeans` command is implemented in the TLT algorithm. You should use the output as your anchor shape in the :code:`yolov4_config` spec file. .. code:: tlt yolo_v4 kmeans [-h] -l -i -x -y [-n ] [--max_steps ] [--min_x ] [--min_y ] Required Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-l`: Paths to the training label folders. Multiple folder paths should be separated with spaces. * :code:`-i`: Paths to corresponding training image folders. Folder counts and orders must match label folders. * :code:`-x`: The base network input width. This should be the :code:`output_width` in the augmentation config part of your spec file. * :code:`-y`: The base network input height. This should be the :code:`output_height` in the augmentation config part of your spec file. Optional Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-n`: The number of shape clusters. This defines how many shape centers the command will output. The default is 9 (3 per group and 3 groups). * :code:`--max_steps`: The max number of steps the kmeans algorithm should run. If the algorithm does not converge at this step, a suboptimal result will be returned. The default value is 10000. * :code:`--min_x`: Ignore ground truth boxes with width less than this value in a reshaped image (images are first reshaped to network base shape as `-x`, `-y`). * :code:`--min_y`: Ignore ground truth boxes with height less than this value in a reshaped image (images are first reshaped to network base shape as `-x`, `-y`). * :code:`-h, --help`: Show this help message and exit. Training the Model ------------------ .. _training_the_model_yolo_v4: Train the YOLOv4 model using this command: .. code:: tlt yolo_v4 train [-h] -e -r -k [--gpus ] [--gpu_index ] [--use_amp] [--log_file ] Required Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-r, --results_dir`: The path to the folder where the experiment output is written. * :code:`-k, --key`: The encryption key to decrypt the model. * :code:`-e, --experiment_spec_file`: The experiment specification file to set up the evaluation experiment. This should be the same as the training-specification file. Optional Arguments ^^^^^^^^^^^^^^^^^^ * :code:`--gpus`: The number of GPUs to use for training in a multi-GPU scenario (default: 1). * :code:`--gpu_index`: The GPU indices used to run the training. You can specify the indices of GPUs to use for training when the machine has multiple GPUs installed. * :code:`--use_amp`: A flag to enable AMP training. * :code:`--log_file`: THe path to the log file. The default path is :code:`stdout`. * :code:`-h, --help`: Show this help message and exit. Input Requirement ^^^^^^^^^^^^^^^^^ * **Input size**: C * W * H (where C = 1 or 3, W >= 128, H >= 128, W, H are multiples of 32) * **Image format**: JPG, JPEG, PNG * **Label format**: KITTI detection Sample Usage ^^^^^^^^^^^^ Here's an example of using the train command on a YOLOv4 model: .. code:: tlt yolo_v4 train --gpus 2 -e /path/to/spec.txt -r /path/to/result -k $KEY Evaluating the Model -------------------- To run evaluation on a YOLOv4 model, use this command: .. code:: tlt yolo_v4 evaluate [-h] -e -m -k [--gpu_index ] [--log_file ] Required Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-e, --experiment_spec_file`: The experiment spec file to set up the evaluation experiment. This should be the same as the training-specification file. * :code:`-m, --model`: The path to the model file to use for evaluation. The model can be either a :code:`.tlt` model file or TensorRT engine. * :code:`-k, --key`: The key to load the model (not needed if the model is a TensorRT engine). Optional Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-h, --help`: Show this help message and exit. * :code:`--gpu_index`: The GPU index used to run the evaluation. You can specify the index of a GPU to run evaluation when the machine has multiple GPUs installed. Note that evaluation can only run on a single GPU. * :code:`--log_file`: The path to the log file. The default path is :code:`stdout`. Running Inference on a YOLOv4 Model ----------------------------------- .. _running_inference_on_a_yolo_v4_model: The inference tool for YOLOv4 networks, which may be used to visualize bboxes or generate frame-by-frame KITTI format labels on a single image or a directory of images. An example of the command for this tool is shown here: .. code:: tlt yolo_v4 inference [-h] -i -o -e -m -k [-l ] [-t ] [--gpu_index ] [--log_file ] Required Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-m, --model`: The path to the trained model (TLT model) or TensorRT engine. * :code:`-i, --in_image_dir`: The directory of input images for inference. * :code:`-o, --out_image_dir`: The directory path to output annotated images. * :code:`-k, --key`: The key to load model (not needed if model is a TensorRT engine). * :code:`-e, --config_path`: Path to an experiment spec file for training. Optional Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-t, --draw_conf_thres`: Threshold for drawing a bbox. default: 0.3. * :code:`-h, --help`: Show this help message and exit. * :code:`-l, --out_label_dir`: The directory to output KITTI labels. * :code:`--gpu_index`: The GPU index used to run the inference. We can specify the GPU index used to run evaluation when the machine has multiple GPUs installed. Note that evaluation can only run on a single GPU. * :code:`--log_file`: The path to the log file. The default path is :code:`stdout`. Pruning the Model ----------------- .. _pruning_the_model_yolo_v4: Pruning removes parameters from the model to reduce the model size without compromising the integrity of the model itself using the :code:`tlt yolo_v4 prune` command. The :code:`tlt yolo_v4 prune` command includes these parameters: .. code:: tlt yolo_v4 prune [-h] -m -o -k [-n ] [-eq ] [-pg ] [-pth ] [-nf ] [-el [] Required Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-m, --model`: The path to pretrained YOLOv4 model * :code:`-o, --output_file`: The path to the output checkpoints * :code:`-k, --key`: The key to load a .tlt model Optional Arguments ^^^^^^^^^^^^^^^^^^ * :code:`-h, --help`: Show this help message and exit. * :code:`-n, –normalizer`: Use ``max`` to normalize by dividing each norm by the maximum norm within a layer; use ``L2`` to normalize by dividing by the L2 norm of the vector comprising all kernel norms. The default value is ``max``. * :code:`-eq, --equalization_criterion`: Criteria to equalize the stats of inputs to an element-wise op layer or depth-wise convolutional layer. This parameter is useful for ResNets and MoblieNets. Options are :code:`arithmetic_mean`,:code:`geometric_mean`, :code:`union`, and :code:`intersection`. The default value is :code:`union`. * :code:`-pg, -pruning_granularity`: The number of filters to remove at a time (default: 8) * :code:`-pth`: The threshold to compare a normalized norm against (default: 0.1) .. Note: NVIDIA recommends changing the threshold to keep the number of parameters in the model to within 10-20% of the original unpruned model. * :code:`-nf, --min_num_filters`: The minimum number of filters to keep per layer (default: 16) * :code:`-el, --excluded_layers`: A list of excluded_layers. Examples: -i item1 item2 (default: []) After pruning, the model needs to be retrained. See :ref:`Re-training the Pruned Model ` for more details. Using the Prune Command ^^^^^^^^^^^^^^^^^^^^^^^ Here's an example of using the :code:`tlt yolo_v4 prune` command: .. code:: tlt yolo_v4 prune -m /workspace/output/weights/resnet_003.tlt \ -o /workspace/output/weights/resnet_003_pruned.tlt \ -eq union \ -pth 0.7 -k $KEY Re-training the Pruned Model ---------------------------- .. _re-training_the_pruned_model_yolo_v4: Once the model has been pruned, there might be a slight decrease in accuracy because some previously useful weights may have been removed. To regain accuracy, we recommend retraining the pruned model over the same dataset. To do this, use the :code:`tlt yolo_v4 train` command as documented in :ref:`Training the model `, with an updated spec file that points to the newly pruned model as the :code:`pruned_model_path`. We recommend turning off the regularizer in the :code:`training_config` for detectnet to recover the accuracy when retraining a pruned model. You may do this by setting the regularizer type to NO_REG as mentioned in the :ref:`Training Config ` section. All other parameters in the spec file can be carried over from the previous training. Exporting the Model ------------------- .. _exporting_the_model_yolo_v4: Exporting the model decouples the training process from inference and allows conversion to TensorRT engines outside the TLT environment. TensorRT engines are specific to each hardware configuration and should be generated for each unique inference environment. The exported model may be used universally across training and deployment hardware. The exported model format is referred to as :code:`.etlt`. Like :code:`.tlt`, the :code:`.etlt` model format is also an encrypted model format with the same key of the :code:`.tlt` model that it is exported from. This key is required when deploying this model. INT8 Mode Overview ^^^^^^^^^^^^^^^^^^ TensorRT engines can be generated in INT8 mode to improve performance, but require a calibration cache at engine creation-time. If :code:`tlt yolo_v4 export` is run with the :code:`--data_type` flag set to :code:`int8`, the calibration cache is generated using a calibration tensor file. Pre-generating the calibration information and caching it removes the need for calibrating the model on the inference machine. Moving the calibration cache is usually much more convenient than moving the calibration tensorfile since it is a much smaller file and can be moved with the exported model. Using the calibration cache also speeds up engine creation, as building the cache can take several minutes depending on the size of the Tensorfile and the model itself. The export tool can generate an INT8 calibration cache by ingesting training data using either of these options: * **Option 1**: Using the training data loader to load the training images for INT8 calibration. This option is now the recommended approach to support multiple image directories by leveraging the training dataset loader. This also ensures two important aspects of data during calibration: * Data pre-processing in the INT8 calibration step is the same as in the training process. * The data batches are sampled randomly across the entire training dataset, thereby improving the accuracy of the INT8 model. * **Option 2**: Pointing the tool to a directory of images that you want to use to calibrate the model. For this option, make sure to create a sub-sampled directory of random images that best represent your training dataset. FP16/FP32 Model ^^^^^^^^^^^^^^^ The :code:`calibration.bin` is only required if you need to run inference at INT8 precision. For FP16/FP32 based inference, the export step is much simpler. All that is required is to provide a :code:`.tlt` model from the training/retraining step to be converted into :code:`.etlt`. Exporting the Model ^^^^^^^^^^^^^^^^^^^ Here's an example of the command line arguments of the :code:`tlt yolo_v4 export` command: .. code:: tlt yolo_v4 export [-h] -m -k [-o ] [--cal_data_file ] [--cal_image_dir ] [--data_type ] [--batches ] [--max_batch_size ] [--max_workspace_size ] [--experiment_spec ] [--engine_file ] [--gen_ds_config] [--verbose] [--strict_type_constraints] [--force_ptq] [--gpu_index ] [--log_file ] Required Arguments ****************** * :code:`-m, --model`: The path to the :code:`.tlt model` file to be exported. * :code:`-k, --key`: The key used to save the :code:`.tlt` model file. * :code:`-e, --experiment_spec`: The path to the spec file. Optional Arguments ****************** * :code:`-h, --help`: Show this help message and exit. * :code:`-o, --output_file`: The path to save the exported model to. The default path is :code:`./.etlt`. * :code:`--data_type`: The desired engine data type. The options are {:code:`fp32`, :code:`fp16`, :code:`int8`} The default value is :code:`fp32`. A calibration cache is generated in INT8 mode. If using INT8 mode, the following INT8 arguments are required. * :code:`--gen_ds_config`: A Boolean flag indicating whether to generate the template DeepStream related configuration ("nvinfer_config.txt") as well as a label file ("labels.txt") in the same directory as the :code:`output_file`. Note that the config file is NOT a complete configuration file and requires the user to update the sample config files in DeepStream with the parameters generated. * :code:`-s, --strict_type_constraints`: A Boolean flag indicating whether to apply the TensorRT strict type constraints when building the TensorRT engine. * :code:`--gpu_index`: The index of the (descrete) GPU for exporting the model if the machine has multiple GPUs installed. Note that export can only run on a single GPU. * :code:`--log_file`: The path to the log file. The default path is :code:`stdout`. INT8 Export Mode Required Arguments ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * :code:`--cal_data_file`: The tensorfile generated for calibrating the engine. This can also be an output file if used with :code:`--cal_image_dir`. * :code:`--cal_image_dir`: A directory of images to use for calibration. .. Note:: The :code:`--cal_image_dir` parameter for images applies the necessary preprocessing to generate a tensorfile at the path mentioned in the :code:`--cal_data_file` parameter, which is in turn used for calibration. The number of generated batches in the tensorfile is obtained from the :code:`--batches` parameter value, and the :code:`batch_size` is obtained from the :code:`--batch_size` parameter value. Ensure that the directory mentioned in :code:`--cal_image_dir` has at least :code:`batch_size * batches` number of images in it. The valid image extensions are :code:`.jpg`, :code:`.jpeg`, and :code:`.png`. In this case, the :code:`input_dimensions` of the calibration tensors are derived from the input layer of the :code:`.tlt` model. INT8 Export Optional Arguments ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ * :code:`--cal_cache_file`: The path to save the calibration cache file to. The default value is :code:`./cal.bin`. * :code:`--batches`: The number of batches to use for calibration and inference testing. The default value is 10. * :code:`--batch_size`: The batch size to use for calibration. The default value is 8. * :code:`--max_batch_size`: The maximum batch size of the TensorRT engine. The default value is 16. * :code:`--max_workspace_size`: The maximum workspace size of TensorRT engine. The default value is :code:`1073741824 = 1<<30` * :code:`--engine_file`: The path to the serialized TensorRT engine file. Note that this file is hardware specific, and cannot be generalized across GPUs. It is useful to quickly test your model accuracy using TensorRT on the host. As TensorRT engine file is hardware specific, you cannot use this engine file for deployment unless the deployment GPU is identical to the training GPU. * :code:`--force_ptq`: A boolean flag to force post training quantization on the exported etlt model. .. Note:: When exporting a model trained with QAT enabled, the tensor scale factors to calibrate the activations are peeled out of the model and serialized to a TensorRT readable cache file defined by the :code:`cal_cache_file` argument. However, note that the current version of QAT doesn’t natively support DLA INT8 deployment on Jetson. To deploy this model on a Jetson with DLA :code:`int8`, use the :code:`--force_ptq` flag for TensorRT post-training quantization to generate the calibration cache file. Sample usage ^^^^^^^^^^^^ The following is a sample command to export a YOLOv4 model in INT8 mode: .. code:: tlt yolo_v4 export -m /workspace/yolov4_resnet18_epoch_100.tlt \ -o /workspace/yolov4_resnet18_epoch_100_int8.etlt \ -e /workspace/yolov4_retrain_resnet18_kitti.txt \ -k $KEY \ --cal_image_dir /workspace/data/training/image_2 \ --data_type int8 \ --batch_size 8 \ --batches 10 \ --cal_cache_file /export/cal.bin \ --cal_data_file /export/cal.tensorfile Deploying to DeepStream ----------------------- .. _deploying_to_deepstream_yolov4: .. include:: ../excerpts/deploying_to_deepstream.rst TensorRT Open Source Software (OSS) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The TensorRT OSS build is required for YOLOv4 models. This is required because several TensorRT plugins that are required by these models are only available in TensorRT open source repo and not in the general TensorRT release. Specifically, for YOLOv4, we need the :code:`batchTilePlugin` and :code:`batchedNMSPlugin`. If the deployment platform is x86 with an NVIDIA GPU, follow the **TensorRT OSS on x86** instructions; if your deployment is on an NVIDIA Jetson platform, follow the **TensorRT OSS on Jetson (ARM64)** instructions. TensorRT OSS on x86 ******************* .. include:: ../excerpts/tensorrt_oss_on_x86.rst TensorRT OSS on Jetson (ARM64) ****************************** .. include:: ../excerpts/tensorrt_oss_on_jetson_arm64.rst Generating an Engine Using tlt-converter ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ .. _generating_an_engine_using_tlt-converter_yolo_v4: .. include:: ../excerpts/generating_an_engine_using_tlt-converter.rst Instructions for x86 ******************** .. include:: ../excerpts/instructions_for_x86_with_OSS.rst Instructions for Jetson *********************** .. include:: ../excerpts/instructions_for_jetson_with_OSS.rst Using the tlt-converter *********************** .. code:: tlt-converter [-h] -k -d -o [-c ] [-e ] [-b ] [-m ] [-t ] [-w ] [-i ] [-p ] [-s] [-u ] input_file Required Arguments ~~~~~~~~~~~~~~~~~~ * :code:`input_file`: The path to the :code:`.etlt` model exported using :code:`tlt yolo_v4 export`. * :code:`-k`: The key used to encode the :code:`.tlt` model when training. * :code:`-d`: A comma-separated list of input dimensions that should match the dimensions used for :code:`tlt yolo_v4 export`. * :code:`-o`: A comma-separated list of output blob names that should match the output configuration used for :code:`tlt yolo_v4 export`. For YOLOv4, set this argument to :code:`BatchedNMS`. * :code:`-p`: Optimization profiles for :code:`.etlt` models with dynamic shape. Use a comma-separated list of optimization profile shapes in the format :code:`,,,`, where each shape has the format: :code:`xxx`. The input name for YOLOv4 is :code:`Input` Optional Arguments ~~~~~~~~~~~~~~~~~~ * :code:`-e`: The path to save the engine to. The default path is :code:`./saved.engine`. * :code:`-t`: The desired engine data type. The options are {:code:`fp32`, :code:`fp16`, :code:`int8`}. The default value is :code:`fp32`. A calibration cache is generated in INT8 mode. * :code:`-w`: The maximum workspace size for the TensorRT engine. The default value is :code:`1073741824(1<<30)`. * :code:`-i`: The input dimension ordering; all other TLT commands use NCHW. The options are {:code:`nchw`, :code:`nhwc`, :code:`nc`}.The default value is :code:`nchw`, so you can omit this argument for YOLOv4. * :code:`-s`: TensorRT strict type constraints. A Boolean to apply TensorRT strict type constraints when building the TensorRT engine. * :code:`-u`: Specifies the DLA core index when building the TensorRT engine on Jetson devices (only needed if using DLA core). INT8 Mode Arguments ~~~~~~~~~~~~~~~~~~~ * :code:`-c`: The path to the calibration cache file (only used in INT8 mode). The default value is :code:`./cal.bin`. * :code:`-b`: The batch size used during the export step for INT8-calibration cache generation (default: :code:`8`). * :code:`-m`: The maximum batch size for the TensorRT engine (default: :code:`16`). If you encounter an out-of-memory issue, decrease the batch size accordingly. This parameter is not required for :code:`.etlt` models generated with dynamic shape (which is only possible for new models introduced in TLT 3.0). Sample Output Log ~~~~~~~~~~~~~~~~~ Here is a sample log for exporting a YOLOv4 model: .. code:: tlt-converter -k $KEY \ -d 3,384,1248 \ -o BatchedNMS \ -e /export/trt.fp16.engine \ -t fp16 \ -i nchw \ -m 8 \ /ws/yolov4_resnet18_epoch_100.etlt Integrating the model with DeepStream ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ To integrate a model trained by TLT with DeepStream, you shoud generate a device-specific optimized TensorRT engine using :code:`tlt-converter`. The generated TensorRT engine file can then be ingested by DeepStream (Currently, YOLOv4 etlt files are not supported by DeepStream). For YOLOv4, you will need to build the TensorRT open-source plugins and custom bounding-box parser. The instructions to build TensorRT open-source plugins are provided in the **TensorRT Open Source Software (OSS)** section above. The instructions to build a custom bounding-box parser are provided in the **Prerequisites for YOLOv4 Model** section below, and the required code can be found in this `GitHub repo`_. .. _GitHub repo: https://github.com/NVIDIA-AI-IOT/deepstream_tlt_apps To integrate the models with DeepStream, you need the following: 1. Download_ and install DeepStream SDK. The installation instructions for DeepStream are provided in the `DeepStream Development Guide`_. 2. An exported :code:`.etlt` model file and optional calibration cache for INT8 precision. 3. `TensorRT 7+ OSS Plugins`_ . 4. A :code:`labels.txt` file containing the labels for classes in the order in which the networks produces outputs. 5. A sample :code:`config_infer_*.txt` file to configure the nvinfer element in DeepStream. The nvinfer element handles everything related to TensorRT optimization and engine creation in DeepStream. .. _Download: https://developer.nvidia.com/deepstream-download .. _DeepStream Development Guide: https://docs.nvidia.com/metropolis/deepstream/dev-guide/index.html .. _TensorRT 7+ OSS Plugins : https://github.com/NVIDIA/TensorRT/tree/release/7.0 DeepStream SDK ships with an end-to-end reference application which is fully configurable. Users can configure input sources, inference model, and output sinks. The app requires a primary object detection model, followed by an optional secondary classification model. The reference application is installed as :code:`deepstream-app`. The graphic below shows the architecture of the reference application. .. image:: ../../content/arch_ref_appl.png There are typically 2 or more configuration files that are used with this app. In the install directory, the config files are located in :code:`samples/configs/deepstream-app` or :code:`sample/configs/tlt_pretrained_models`. The main config file configures all the high level parameters in the pipeline above. This would set input source and resolution, number of inferences, tracker and output sinks. The other supporting config files are for each individual inference engine. The inference specific config files are used to specify models, inference resolution, batch size, number of classes and other customization. The main config file will call all the supporting config files. Here are some config files in :code:`samples/configs/deepstream-app` for your reference. * :code:`source4_1080p_dec_infer-resnet_tracker_sgie_tiled_display_int8.txt`: Main config file * :code:`config_infer_primary.txt`: Supporting config file for primary detector in the pipeline above * :code:`config_infer_secondary_*.txt`: Supporting config file for secondary classifier in the pipeline above The :code:`deepstream-app` will only work with the main config file. This file will most likely remain the same for all models and can be used directly from the DeepStream SDK will little to no change. User will only have to modify or create :code:`config_infer_primary.txt` and :code:`config_infer_secondary_*.txt`. Integrating a YOLOv4 Model ****************************** To run a YOLOv4 model in DeepStream, you need a label file and a DeepStream configuration file. In addition, you need to compile the TensorRT 7+ Open source software and YOLOv4 bounding box parser for DeepStream. A DeepStream sample with documentation on how to run inference using the trained YOLOv4 models from TLT is provided on `GitHub repo`_.. Prerequisites for YOLOv4 Model ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 1. YOLOv4 requires batchTilePlugin, resizeNearestPlugin, and batchedNMSPlugin. These plugins are available in the TensorRT open source repo, but not in TensorRT 7.0. Detailed instructions to build TensorRT OSS can be found in `TensorRT Open Source Software (OSS)`. 2. YOLOv4 requires YOLOv3 custom bounding box parsers that are not built-in inside the DeepStream SDK. The source code to build YOLOv3 custom bounding box parsers is available in `GitHub repo`_. The following instructions can be used to build bounding box parser: **Step1**: Install git-lfs_ (git >= 1.8.2) .. _git-lfs: https://github.com/git-lfs/git-lfs/wiki/Installation .. code:: curl -s https://packagecloud.io/install/repositories/github/git-lfs/ script.deb.sh | sudo bash sudo apt-get install git-lfs git lfs install **Step 2**: Download Source Code with SSH or HTTPS .. code:: git clone -b release/tlt3.0 https://github.com/NVIDIA-AI-IOT/deepstream_tlt_apps Step 3: Build .. code:: // or Path for DS installation export CUDA_VER=10.2 // CUDA version, e.g. 10.2 make This generates :code:`libnvds_infercustomparser_tlt.so` in the directory :code:`post_processor`. Label File ^^^^^^^^^^ The label file is a text file containing the names of the classes that the YOLOv4 model is trained to detect. The order in which the classes are listed here must match the order in which the model predicts the output. During the training, TLT YOLOv4 will specify all class names in lower case and sort them in alphabetical order. For example, if the `dataset_config` is: .. code:: dataset_config { data_sources: { label_directory_path: "/workspace/tlt-experiments/data/training/label_2" image_directory_path: "/workspace/tlt-experiments/data/training/image_2" } target_class_mapping { key: "car" value: "car" } target_class_mapping { key: "person" value: "person" } target_class_mapping { key: "bicycle" value: "bicycle" } validation_data_sources: { label_directory_path: "/workspace/tlt-experiments/data/val/label" image_directory_path: "/workspace/tlt-experiments/data/val/image" } } Then the corresponding `yolov4_labels.txt` file would be: .. code:: bicycle car person DeepStream Configuration File ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ The detection model is typically used as a primary inference engine. It can also be used as a secondary inference engine. To run this model in the sample :code:`deepstream-app`, you must modify the existing :code:`config_infer_primary.txt` file to point to this model. .. image:: ../../content/dstream_deploy_options2.png **Integrate the TensorRT engine file with the DeepStream app** **Step 1**: Generate TensorRT engine using tlt-converter. Detail instructions are provided in the :ref:`Generating an engine using tlt-converter ` section above. **Step 2**: Once the engine file is generated successfully, modify the following parameters to use this engine with DeepStream. .. code:: model-engine-file= All other parameters are common between the two approaches. To use the custom bounding box parser instead of the default parsers in DeepStream, modify the following parameters in [property] section of primary infer configuration file: .. code:: parse-bbox-func-name=NvDsInferParseCustomBatchedNMSTLT custom-lib-path= Add the label file generated above using: .. code:: labelfile-path= For all the options, see the configuration file below. To learn about what all the parameters are used for, refer to the `DeepStream Development Guide`_. .. _DeepStream Development Guide: https://docs.nvidia.com/metropolis/deepstream/dev-guide/index.html Here’s a sample config file, `pgie_yolov4_config.txt`: .. code:: [property] gpu-id=0 net-scale-factor=1.0 offsets=103.939;116.779;123.68 model-color-format=1 labelfile-path= model-engine-file= tlt-model-key= infer-dims=3;384;1248 maintain-aspect-ratio=1 uff-input-order=0 uff-input-blob-name=Input batch-size=1 ## 0=FP32, 1=INT8, 2=FP16 mode network-mode=0 num-detected-classes=3 interval=0 gie-unique-id=1 is-classifier=0 #network-type=0 #no cluster cluster-mode=3 output-blob-names=BatchedNMS parse-bbox-func-name=NvDsInferParseCustomBatchedNMSTLT custom-lib-path= [class-attrs-all] pre-cluster-threshold=0.3 roi-top-offset=0 roi-bottom-offset=0 detected-min-w=0 detected-min-h=0 detected-max-w=0 detected-max-h=0