Papers › Rethinking the competition between detection and ReID in Multi-Object Tracking

Rethinking the competition between detection and ReID in Multi-Object Tracking

23 Oct 2020arXiv:2010.12138archive 2025-07-28

Chao Liang, Zhipeng Zhang, Xue Zhou, Bing Li, Shuyuan Zhu, Weiming Hu

Due to balanced accuracy and speed, one-shot models which jointly learn detection and identification embeddings, have drawn great attention in multi-object tracking (MOT). However, the inherent differences and relations between detection and re-identification (ReID) are unconsciously overlooked because of treating them as two isolated tasks in the one-shot tracking paradigm. This leads to inferior performance compared with existing two-stage methods. In this paper, we first dissect the reasoning process for these two tasks, which reveals that the competition between them inevitably would destroy task-dependent representations learning. To tackle this problem, we propose a novel reciprocal network (REN) with a self-relation and cross-relation design so that to impel each branch to better learn task-dependent representations. The proposed model aims to alleviate the deleterious tasks competition, meanwhile improve the cooperation between detection and ReID. Furthermore, we introduce a scale-aware attention network (SAAN) that prevents semantic level misalignment to improve the association capability of ID embeddings. By integrating the two delicately designed networks into a one-shot online MOT system, we construct a strong MOT tracker, namely CSTrack. Our tracker achieves the state-of-the-art performance on MOT16, MOT17 and MOT20 datasets, without other bells and whistles. Moreover, CSTrack is efficient and runs at 16.4 FPS on a single modern GPU, and its lightweight version even runs at 34.6 FPS. The complete code has been released at https://github.com/JudasDie/SOTS.

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

The archive's official repository (JudasDie/SOTS) was not harvested; the 15 samples below come from 2 community repositories.

Syntology 15 code samples harvested from 2 repositories linked to this paper: 12 ran (of which 0 constructed an object rather than computing a result; 10 with no instrument failure: 0 honoured, 0 violated, 10 with no contract checked; 2 where Syntology's instrument failed) · 3 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 15 samples from 2 repositories, 12 ran (10 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

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.

JudasDie/SOTS officialmentioned in papermentioned on GitHubpytorchSyntology: not harvested report
ZhangwenguangHikvision/YoloV5_JDE_TensorRT_for_Track mentioned on GitHubMITSyntology: not harvested report
Zhongdao/Towards-Realtime-MOT mentioned on GitHubpytorchMITSyntology: 14 samples, 12 ran (2 instrument-failed) · 2 unverified report
nemonameless/jde mentioned on GitHubpytorchMITSyntology: 1 sample, 0 ran · 1 unverified 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.

Code Syntology ran Syntology

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

2ran · our draft was wrong
10ran
3unverified

Licence: 0 of the 15 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

Zhongdao/Towards-Realtime-MOT community (archive-listed) 14 samples, 12 ran (2 instrument-failed) · 2 unverified
collate_fn in 500 papers utils/datasets.py ran MIT (permissive) · 7ca75b6abf5efc06 · report fixture: signature batch:list/1/tuple · returned tuple · level recorded 2026-09-25
joint_stracks in 8 papers tracker/multitracker.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
letterbox in 14 papers utils/datasets.py ran MIT (permissive) · 90caac012650cd20 · report fixture: signature img:ndarray/3/int, height:int/0/int, width:int/0/int, color:tuple/1/float · returned tuple · level recorded 2026-09-25
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
parse_data_cfg in 5 papers utils/parse_config.py ran MIT (permissive) · 5f1e6bf7cfe64409 · report fixture: signature path:str/0/str · returned dict · level recorded 2026-09-25
parse_model_cfg in 5 papers utils/parse_config.py ran MIT (permissive) · 3931670f65ad9328 · report fixture: signature path:str/0/str · returned list · level recorded 2026-09-25
random_affine in 7 papers utils/datasets.py ran MIT (permissive) · 5e616815ca4cc1ed · report fixture: signature img:ndarray/3/int, targets:ndarray/2/float, degrees:tuple/1/int, translate:tuple/1/float, scale:tuple/1/float, shear:tuple/1/int, borderValue:tuple/1/float · returned tuple · level recorded 2026-09-25
read_mot_results in 6 papers utils/io.py ran MIT (permissive) · 9eb3b334fd02b5d3 · report fixture: signature filename:str/0/str, is_gt:bool/0/bool, is_ignore:bool/0/bool · returned dict · level recorded 2026-09-25
read_results in 19 papers utils/io.py ran MIT (permissive) · 1958a4fce355d7a6 · report fixture: signature filename:str/0/str, data_type:str/0/str, is_gt:bool/0/bool, is_ignore:bool/0/bool · returned dict · level recorded 2026-09-25
sub_stracks in 8 papers tracker/multitracker.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
unzip_objs in 5 papers utils/io.py ran MIT (permissive) · 261a9c5fae0c1b9f · report fixture: signature objs:list/1/tuple · returned tuple · level recorded 2026-09-25
create_modules in 5 papers models.py unverified MIT (permissive) · 1d0ed55a31730d4a · report
shift_tensor_vertically models.py unverified MIT (permissive) · 9eb6a59860b08148 · report
nemonameless/jde community (archive-listed) 1 sample, 0 ran · 1 unverified
create_modules in 5 papers models.py unverified MIT (permissive) · afc666065e74d2cf · report

Tasks

Multi-Object TrackingObject Tracking

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Multi-Object Tracking HiEve CSTrack IDF1 51.4 #1 of 4 Archive leaderboard report
Multi-Object Tracking HiEve CSTrack MOTA 48.6 #1 of 4 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.

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