Why changing tracking-method also affects the number of detections?

[davide-bontempelli-zupit]

Search before asking

• I have searched the Yolo Tracking issues and found no similar bug report.

Question

I ran boxmot keeping the same yolo model and only changing tracking method and on the video shown i got a lot less detections.

These are the two command that i used

python tracking/track.py --source "5042_5047.mp4" \ 
  --yolo-model yolov8x-pose.pt \
  --reid-model osnet_x1_0_msmt17.pt \
  --tracking-method botsort \
  --conf 0.1 \
  --iou 0.7 \
  --device 0 \
  --show \       
  --classes 0 \
  --name test \
  --exist-ok \ 
  --show-labels \      
  --show-conf \
  --show-trajectories \
  --save-txt \
  --line-width 3 \
  --verbose

python tracking/track.py --source "5042_5047.mp4" \ 
--yolo-model yolov8x-pose.pt \
--reid-model osnet_x1_0_msmt17.pt \
--tracking-method botsort \
--conf 0.1 \
--iou 0.7 \
--device 0 \
--show \     
--classes 0 \
--name test \
--exist-ok \ 
--show-labels \      
--show-conf \
--show-trajectories \
--save-txt \
--line-width 3 \
--verbose

[mikel-brostrom]

The tracking modules themselves are doing some filtering on the detections in order to figure out wether they are good candidates to be accepted as valid tracks or not. Hence, affecting the number of outputs 😄. For example this line of code is relevant in BoTSORT:

boxmot/boxmot/trackers/botsort/bot_sort.py

Line 278 in b349b67

first_mask = confs > self.track_high_thresh