Repository navigation
Tracking Outputs vs Detection Outputs #14
Description
While using ByteTrack as a tracker, the visualized bounding boxes sometimes do not precisely match the detection results. Are there any methods to assign tracking IDs to detections without altering the bounding box coordinates? I am asking this question because the tracking bounding boxes are sometimes too wide for my specific case.
Activity
derpda commentedon Mar 7, 2024
I believe ByteTrack ends up using the predicted bounding box for the next step instead of the current bounding box. See below
ByteTrack-cpp/src/STrack.cpp
Line 110 in d43805d
I have changed that in my own fork, but also made a lot of changes specific to my use case, which may or may not be appropriate for you. Tests are also currently not passing since I changed (in my opinion fixed) the IoU calculation. I'm looking into that at the moment.
Have a look for yourself: https://github.com/derpda/ByteTrack-cpp