Browse › Computer Vision › Object Tracking › QuadTrack
QuadTrack Benchmark (Object Tracking)
Object tracking is the task of taking an initial set of object detections, creating a unique ID for each of the initial detections, and then tracking each of the objects as they move around frames in a video, maintaining the ID assignment. State-of-the-art methods involve fusing data from RGB and event-based cameras to produce more reliable object tracking. CNN-based models using only RGB images as input are also effective. The most popular benchmark is OTB. There are several evaluation metrics specific to object tracking, including HOTA, MOTA, IDF1, and Track-mAP.
The archive carries no text for this table; the description above is the archive's text for the task Object Tracking. archive 2025-07-28
Over time archive 2025-07-28
The chart needs JavaScript; the table below carries every value.
Not inferred: HOTA. Points are placed at the row's paper date; 8 of 8 rows carry one.
Results archive 2025-07-28
Archive rows end at the archive snapshot, 2025-07-28: no result published after that date is in this table. Rank is the archive's row order at that snapshot; not re-ranked here. Metric values are the archive's strings. Column headers sort the table in your browser; each row keeps its archive rank.
| Paper | Code | Ran Syntology | Report | |||||
|---|---|---|---|---|---|---|---|---|
| 1 | OmniTrack | 23.45 | – | Paper | Code | 2025 | linked, not harvested | report |
| 2 | DeepSORT | 21.16 | – | Paper | Code | 2017 | 12 of 40 ran · 28 unverified | report |
| 3 | OC-SORT | 20.83 | – | Paper | Code | 2022 | 15 of 31 ran · 16 unverified | report |
| 4 | ByteTrack | 20.66 | – | Paper | Code | 2021 | 1 of 12 ran · 11 unverified | report |
| 5 | TrackFormer | 19.62 | – | Paper | Code | 2021 | linked, not harvested | report |
| 6 | HybridSORT | 16.64 | – | Paper | Code | 2023 | linked, not harvested | report |
| 7 | DiffMOT | 16.4 | – | Paper | – | 2024 | no code linked | report |
| 8 | Bot-SORT | 15.77 | – | Paper | Code | 2022 | 4 of 10 ran · 6 unverified | report |
All 8 rows shown. 8 link to a paper page on this site; 0 are marked as using additional training data in the archive. No GitHub stars are tracked; "Code" is the first repository the archive lists for the row. The archive carries no row tags, review links or community-submitted rows for this table; none are shown. archive 2025-07-28
Syntology Ran reads "N of M ran · U unverified": of the M code samples Syntology harvested from repositories linked to that row's paper (joined by arXiv id), N executed on a synthesized input and the other U = M−N are unverified (harvested, no recorded run). It counts code from repositories linked to that row's paper, not this result: the row's number was not reproduced and nothing here is a correctness claim. The other cell texts mean no graph line for the row: "linked, not harvested" (the archive links code, Syntology has not harvested it), "no code linked" (no code link in the archive), "not matched" (the row's paper URL matched no paper on this site). 4 rows have a graph line, from 4 distinct papers; 4 rows (4 papers) have at least one sample that ran. Counting each paper once: Syntology ran 32 of 93 samples; 61 unverified. Separately, 10 of those 93 are pointer-only (licence): the site points at that code rather than redistributing it, a licence property recorded for ran and unverified samples alike; each cell's tooltip carries the row's own pointer-only count. Read from the graph 2026-09-24. Per-sample status is on the paper page.
Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections