Papers › Unifying Short and Long-Term Tracking with Graph Hierarchies

Unifying Short and Long-Term Tracking with Graph Hierarchies

6 Dec 2022CVPR 2023 1arXiv:2212.03038archive 2025-07-28

Orcun Cetintas, Guillem Brasó, Laura Leal-Taixé

Tracking objects over long videos effectively means solving a spectrum of problems, from short-term association for un-occluded objects to long-term association for objects that are occluded and then reappear in the scene. Methods tackling these two tasks are often disjoint and crafted for specific scenarios, and top-performing approaches are often a mix of techniques, which yields engineering-heavy solutions that lack generality. In this work, we question the need for hybrid approaches and introduce SUSHI, a unified and scalable multi-object tracker. Our approach processes long clips by splitting them into a hierarchy of subclips, which enables high scalability. We leverage graph neural networks to process all levels of the hierarchy, which makes our model unified across temporal scales and highly general. As a result, we obtain significant improvements over state-of-the-art on four diverse datasets. Our code and models are available at bit.ly/sushi-mot.

PaperPDFConference PDFCodeCode 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 11 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 1 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 11 samples from 1 repository, 9 ran (7 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-25 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

dvl-tum/SUSHI officialmentioned on GitHubpytorchMITSyntology: 11 samples, 9 ran (2 instrument-failed) · 2 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

11 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 1 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 2 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
1ran · violated contract
2ran · our draft was wrong
5ran
2unverified

Licence: 0 of the 11 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 dvl-tum/SUSHI. “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.

dvl-tum/SUSHI official repository 11 samples, 9 ran (2 instrument-failed) · 2 unverified
ccwh2tlbr src/utils/motion_utils.py ran fingerprinted MIT (permissive) · 59cda074baa8557a · report fixture: signature boxes:Tensor/2/float · returned Tensor · level recorded 2026-09-25
compute_iou in 68 papers src/utils/motion_utils.py ran MIT (permissive) · 470ebe50cdb0b817 · report fixture: signature output:Tensor/2/float, target:Tensor/2/float · returned tuple · level recorded 2026-09-25
create_experiment_path configs/config.py ran MIT (permissive) · a7ec3c8bfa38a511 · report fixture: signature config:ConfigStandIn/0/? · returned ConfigStandIn · level recorded 2026-09-25
geometric_mean in 8 papers TrackEval/trackeval/plotting.py ran · violated contract fingerprinted MIT (permissive) · 06d2be4ac9d0e95b · report fixture: signature x:ndarray/1/float, y:ndarray/1/float · returned ndarray · level recorded 2026-09-26
jaccard in 33 papers TrackEval/trackeval/plotting.py ran · honoured contract fingerprinted MIT (permissive) · 00c662d6d9709fe4 · report fixture: signature x:Tensor/2/float, y:Tensor/2/float · returned Tensor · level recorded 2026-09-26
load_multiple_tracker_summaries in 7 papers TrackEval/trackeval/plotting.py ran · our draft was wrong MIT (permissive) · e9f7b2829ca9731b · report fixture: signature tracker_folder:str/0/str, tracker_list:list/1/str, cls:str/0/str · returned dict · level recorded 2026-09-26
masked2original src/utils/motion_utils.py ran MIT (permissive) · 7dad15ff6e85ee33 · report fixture: signature tensor:Tensor/2/float, num_nodes:int/0/int, nodes_mask:Tensor/1/bool, fill_value:int/0/int · returned Tensor · level recorded 2026-09-25
post_config configs/config.py ran MIT (permissive) · e66624d1da3d8c41 · report fixture: signature config:Config/0/? · returned Config · level recorded 2026-09-25
time in 9 papers TrackEval/trackeval/_timing.py ran · our draft was wrong MIT (permissive) · df1bd31f4da1bed6 · report fixture: signature f:callable/0/? · returned function · level recorded 2026-09-26
find_graph_time_valid_edges src/utils/graph_utils.py unverified MIT (permissive) · c2c1aafcffd63e68 · report
get_arguments in 15 papers configs/config.py unverified MIT (permissive) · a03bcbfa3e6634c3 · report

Tasks

Multiple Object Tracking

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Multiple Object Tracking BDD100K test SUSHI mHOTA 48.2 #2 of 5 Archive leaderboard report
Multiple Object Tracking BDD100K test SUSHI mIDF1 60.0 #2 of 5 Archive leaderboard report
Multiple Object Tracking BDD100K test SUSHI mMOTA 40.2 #2 of 5 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