Tracker FAQ
This topic is a conclusion for Tracker related problems, following problems is a summary from DS 4.0 to latest DS version(5.0.1).
Standalone tracker sample:
We don’t have an official standalone sample, refer forum topic KLT NvMOT usage
NvDCF tracker:
We suggest to use latest DS version since we had fixed many tracker related issues to make the tracker more stable and robustness on latest DS version.
-
Show 64-bit long Unique ID
- Set
useUniqueID: 1
in tracker config
- Set
-
Make tracker ID continues and reset ID
- Currently we don’t support the feature and user can do it by installing a probe and implementing it
- Related topic Track id not continuous
-
Assign tracker ID per stream
- Disable batch processing mode
- Related topic Dcf tracker use same tracker to increase objectID in mutil stream
-
Shadow tracking
- a per-object tracker is in inactive mode is called the shadow tracking, refer tracker plugin manual for more details Gst-nvtracker — DeepStream 6.1.1 Release documentation
- Related topics Tracking info
-
Track per class ID
- Use the per-class configuration in PGIE config and set threshold to be an infeasible high number like 100
- Related topics Track on the specified class-id - #5
-
Frequent ID switch w/o nearby objects
- Refer NvDCF tuning Doc for more details Troubleshooting — DeepStream 6.1.1 Release documentation
- Related topics NVDCF Tracking Parameters Detailed Info
-
Ghost bbox
- Refer NvDCF tuning Doc for more details Troubleshooting — DeepStream 6.1.1 Release documentation
- How to smooth the bbox detections with the DCF tracking in DS5.0 GA? - #20 by jasonpgf2a
-
Tracker update frequency(related to motion dynamic)
- Try to tune the Moving-Average Estimator or Kalman Filter (based on the value of stateEstimatorType in your config)
- Related topics NvDCF tracker update frequency