Please provide complete information as applicable to your setup.
General information: python3.6, deepstream6, tx2
let’s say we have a video stream that has a driving car in it. the car was detected by the infir plugin and labeled as “Vehicle” and the pipeline has a tracker plugin which gave to the object the id #1.
Will the object that being tracked ( vehicle #1) continue to be tracked even if the “infir” plugin is unable to identify it ?
Which tracker are you using? You can fine-tune some parameters in the tracker to tolerate some missing of detetion, you can refer page Gst-nvtracker — DeepStream 6.1 Release documentation (nvidia.com)
Im using the basic tracker from the test-2 python code example (the NvDCF).
where can I find python’s code example using the Deepsort version?
Can you check your configure file as below to change to different tracker?
[tracker]
enable=1
tracker-width=640
tracker-height=384
ll-lib-file=/opt/nvidia/deepstream/deepstream/lib/libnvds_nvmultiobjecttracker.so
ll-config-file=…/deepstream-app/config_tracker_NvDCF_perf.yml
gpu-id=0
enable-batch-process=1
enable-past-frame=1
display-tracking-id=1
Im receiving the follow exception when running with the ‘DeepSort’ yml file:
environment : TX2 , CUDA 10.2 , tensorRT 8.0.1.6 , cuDNN8.2
!![ERROR] UFF file does not exist
[NvMultiObjectTracker] De-initialized
An exception occurred. UFF file does not exist
gstnvtracker: Failed to initialize tracker context!
gstnvtracker:: Failed to create batch context. Shutting down processing.
gstnvtracker: Loading low-level lib at /opt/nvidia/deepstream/deepstream/lib/libnvds_nvmultiobjecttracker.so
gstnvtracker: Batch processing is ON
gstnvtracker: Past frame output is ON
~~ CLOG[/dvs/git/dirty/git-master_linux/deepstream/sdk/src/utils/nvmultiobjecttracker/src/modules/ReID/ReID.cpp, loadTRTEngine() @line 344]: Engine file does not exist
[NvMultiObjectTracker] Load engine failed. Create engine again.
!![ERROR] UFF file does not exist
[NvMultiObjectTracker] De-initialized
An exception occurred. UFF file does not exist
gstnvtracker: Failed to initialize tracker context!
gstnvtracker:: Failed to create batch context. Shutting down processing.
INFO: [Implicit Engine Info]: layers num: 5
0 INPUT kFLOAT Input 3x480x640
1 OUTPUT kINT32 BatchedNMS 1
2 OUTPUT kFLOAT BatchedNMS_1 200x4
3 OUTPUT kFLOAT BatchedNMS_2 200
4 OUTPUT kFLOAT BatchedNMS_3 200
Decodebin child added: source
Decodebin child added: decodebin0
0:00:03.916814623 14691 0x3ad57370 INFO nvinfer gstnvinfer.cpp:638:gst_nvinfer_logger:<primary-inference> NvDsInferContext[UID 1]: Info from NvDsInferContextImpl::deserializeEngineAndBackend() <nvdsinfer_context_impl.cpp:1900> [UID = 1]: deserialized trt engine from :/home/nvidia/deepstream_python_apps/apps/CVIS/export/yolov4_cspdarknet_tiny_epoch_1000.etlt_b1_gpu0_fp16.engine
0:00:03.916926014 14691 0x3ad57370 INFO nvinfer gstnvinfer.cpp:638:gst_nvinfer_logger:<primary-inference> NvDsInferContext[UID 1]: Info from NvDsInferContextImpl::generateBackendContext() <nvdsinfer_context_impl.cpp:2004> [UID = 1]: Use deserialized engine model: /home/nvidia/deepstream_python_apps/apps/CVIS/export/yolov4_cspdarknet_tiny_epoch_1000.etlt_b1_gpu0_fp16.engine
0:00:03.930154184 14691 0x3ad57370 INFO nvinfer gstnvinfer_impl.cpp:313:notifyLoadModelStatus:<primary-inference> [UID 1]: Load new model:/home/nvidia/deepstream_python_apps/apps/deepstream-test3/pgie_yolov4_tiny_tao_config.txt sucessfully
Decodebin child added: qtdemux0
Decodebin child added: multiqueue0
Decodebin child added: h264parse0
Decodebin child added: capsfilter0
Decodebin child added: nvv4l2decoder0
NvMMLiteOpen : Block : BlockType = 261
NVMEDIA: Reading vendor.tegra.display-size : status: 6
NvMMLiteBlockCreate : Block : BlockType = 261
Opening in BLOCKING MODE
In cb_newpad
gstname= video/x-raw
features= <Gst.CapsFeatures object at 0x7fa5673d68 (GstCapsFeatures at 0x7f08003ac0)>
Do you have model or engine in you setup which listed in the configure file?
There is no update from you for a period, assuming this is not an issue anymore.
Hence we are closing this topic. If need further support, please open a new one.
Thanks
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.