Papers › BoT-SORT: Robust Associations Multi-Pedestrian Tracking

BoT-SORT: Robust Associations Multi-Pedestrian Tracking

29 Jun 2022arXiv:2206.14651archive 2025-07-28

Nir Aharon, Roy Orfaig, Ben-Zion Bobrovsky

The goal of multi-object tracking (MOT) is detecting and tracking all the objects in a scene, while keeping a unique identifier for each object. In this paper, we present a new robust state-of-the-art tracker, which can combine the advantages of motion and appearance information, along with camera-motion compensation, and a more accurate Kalman filter state vector. Our new trackers BoT-SORT, and BoT-SORT-ReID rank first in the datasets of MOTChallenge [29, 11] on both MOT17 and MOT20 test sets, in terms of all the main MOT metrics: MOTA, IDF1, and HOTA. For MOT17: 80.5 MOTA, 80.2 IDF1, and 65.0 HOTA are achieved. The source code and the pre-trained models are available at https://github.com/NirAharon/BOT-SORT

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 10 code samples: 9 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 10: 10 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 0 violated, 4 with no contract checked; 5 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 5 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 9 ran (5 with no instrument failure; 4 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

niraharon/bot-sort officialmentioned in papermentioned on GitHubpytorchMITSyntology: 9 samples, 9 ran (4 instrument-failed) · 0 unverified report
Robotmurlock/Motrack mentioned on GitHubMITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Revisiting Multi-Object Tracking Baselines: Hyperparameter Optimization with... (arXiv:2609.12261; that paper's own run record: 4 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 0 violated, 1 with no contract checked; 2 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. report
airotau/pointpillarshailoinnoviz mentioned on GitHubpytorchSyntology: not harvested report
mikel-brostrom/boxmot mentioned on GitHubpytorchAGPL-3.0Syntology: not harvested report
viplix3/BoTSORT-cpp mentioned on GitHubMITSyntology: not harvested report
PaddlePaddle/PaddleDetection paddleSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to PP-YOLOE: An evolved version of YOLO (arXiv:2203.16250; that paper's own run record: 22 ran (of which 0 constructed an object rather than computing a result; 19 with no instrument failure: 2 honoured, 0 violated, 17 with no contract checked; 3 where Syntology's instrument failed) · 5 unverified); nothing checks that they implement this paper's method. report
tensorworksio/mot.cpp Syntology: not harvested report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

10 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 1 honoured, 0 violated, 4 with no contract checked; 5 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
5ran · our draft was wrong
4ran

Licence: 4 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from niraharon/bot-sort. 1 sample is listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

niraharon/bot-sort official repository 9 samples, 9 ran (4 instrument-failed) · 0 unverified
DWConv in 14 papers yolov7/models/common.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · b9a38c519e71eeba · report fixture: signature c1:int/0/int, c2:int/0/int, k:int/0/int, s:int/0/int, act:bool/0/bool · returned Conv · level recorded 2026-09-25
autopad in 36 papers yolov7/models/common.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 988a3c854b1b13d0 · report fixture: signature k:int/0/int, p:NoneType/0/? · returned int · level recorded 2026-09-22
joint_stracks in 8 papers tracker/bot_sort.py ran · our draft was wrong MIT (permissive) · 557de671825f7887 · report fixture: signature tlista:list/1/Track, tlistb:list/1/Track · returned list · level recorded 2026-09-22
linear_assignment in 7 papers tracker/matching.py ran fingerprinted MIT (permissive) · fa0376e6b3c39f1b · report fixture: signature cost_matrix:ndarray/2/float, thresh:float/0/float · returned tuple · level recorded 2026-09-25
merge_matches in 5 papers tracker/matching.py ran MIT (permissive) · de19615aab6efe36 · report fixture: signature m1:ndarray/2/int, m2:ndarray/2/int, shape:tuple/1/int · returned tuple · level recorded 2026-09-25
postprocess in 70 papers
census: 5 implementations from 5 papers, 5 distinct outputs across 2 buckets, one shared input per bucket
fast_reid/fast_reid_interfece.py ran MIT (permissive) · 967fd53d2da42e11 · report fixture: signature features:Tensor/2/float · returned ndarray · level recorded 2026-09-25
preprocess in 284 papers
census: 11 implementations from 13 papers, 10 distinct outputs across 5 buckets, one shared input per bucket
fast_reid/fast_reid_interfece.py ran MIT (permissive) · c23eced4a7405ac6 · report fixture: signature image:ndarray/3/int, input_size:tuple/1/int · returned tuple · level recorded 2026-09-25
sub_stracks in 8 papers tracker/bot_sort.py ran · our draft was wrong MIT (permissive) · 322ac55b144012cf · report fixture: signature tlista:list/1/Track, tlistb:list/1/Track · returned list · level recorded 2026-09-22
transI_fusebn in 8 papers yolov7/models/common.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 079d0a85a0bfbb47 · report fixture: signature kernel:Tensor/4/float, bn:callable/0/? · returned tuple · level recorded 2026-09-25
Repository not located 1 sample, 1 ran (1 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
get_image_list in 15 papers repository not located ran · our draft was wrong fingerprinted licence of this copy not recorded · 6874177200d9a346 · report fixture: signature path:str/0/str · returned list · level recorded 2026-09-22

Tasks

Multi-Object TrackingObjectObject Tracking

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Multi-Object Tracking MOT17 BoT-SORT HOTA 65.0 #10 of 48 Archive leaderboard report
Multi-Object Tracking MOT17 BoT-SORT IDF1 80.2 #10 of 48 Archive leaderboard report
Multi-Object Tracking MOT17 BoT-SORT MOTA 80.5 #10 of 48 Archive leaderboard report
Multi-Object Tracking MOT20 BoT-SORT HOTA 63.3 #9 of 27 Archive leaderboard report
Multi-Object Tracking MOT20 BoT-SORT IDF1 77.5 #9 of 27 Archive leaderboard report
Multi-Object Tracking MOT20 BoT-SORT MOTA 77.8 #9 of 27 Archive leaderboard report
Object Tracking QuadTrack Bot-SORT HOTA 15.77 #8 of 8 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Methods

Test

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