Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This change adds a new multi-object tracker called ConfTrack to supervision. It is based on the existing ByteTrack implementation and the ConfTrack paper by Hyeonchul Jung, Seokjun Kang, Takgen Kim, and HyeongKi Kim.
This tracker uses a Noise-scale Adaptive Kalman Filter for predicting the motion of objects and a matching algorithm that uses the BoT-SORT first stage and the ByteTrack second stage, with an additional third stage to match un-initialized tracks.
The original paper used person Re-ID, but I found that the tracker still works well without it. (Don't want to add heavy dependencies like TensorFlow or PyTorch).
I validated the implementation locally on MOT20 with TrackEval and I got these results:
ConfTrack as you can see, performs better than ByteTrack in both the MOTA and the HOTA metrics, and provides people with other options for object trackers that may be better for their application. (ConfTrack seems to perform better with good quality detections, and ByteTrack performs better with lower quality detections.)
Type of change
How has this change been tested, please provide a testcase or example of how you tested the change?
I have tested this change in this colab notebook.
I will share my TrackEval code if you want it.
Any specific deployment considerations
If this gets approved I can help write documentation on how to use ConfTrack (basically the same as ByteTrack).
Docs