9 of 11 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 1 honoured the contract we drafted, 1 violated it and 5 have no contract verdict; 2 failures of our instrument; 2 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2212.03038.json · badge: /api/ran/2212.03038.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| dvl-tum/SUSHI | canonical (classifier label) classifier basis not recorded on the link |
9 ran · 2 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| ccwh2tlbr | Ran ran on a synthesized input |
dvl-tum/SUSHI/src/utils/motion_utils.py code served (permissive licence) · get_code("59cda074baa8557a") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| compute_iou | Ran ran on a synthesized input |
dvl-tum/SUSHI/src/utils/motion_utils.py code served (permissive licence) · get_code("470ebe50cdb0b817") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned tuple, ndim 2, dtype family float; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| create_experiment_path | Ran ran on a synthesized input |
dvl-tum/SUSHI/configs/config.py code served (permissive licence) · get_code("a7ec3c8bfa38a511") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned ConfigStandIn. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| geometric_mean | Ran ran, violated the contract we drafted |
dvl-tum/SUSHI/TrackEval/trackeval/plotting.py code served (permissive licence) · get_code("06d2be4ac9d0e95b") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned ndarray, ndim 1, dtype family float, shape (4,) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| jaccard | Ran ran, honoured the contract we drafted |
dvl-tum/SUSHI/TrackEval/trackeval/plotting.py code served (permissive licence) · get_code("00c662d6d9709fe4") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (2, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| load_multiple_tracker_summaries | Ran ran; our contract draft was wrong, not the code |
dvl-tum/SUSHI/TrackEval/trackeval/plotting.py code served (permissive licence) · get_code("e9f7b2829ca9731b") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned dict. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| masked2original | Ran ran on a synthesized input |
dvl-tum/SUSHI/src/utils/motion_utils.py code served (permissive licence) · get_code("7dad15ff6e85ee33") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Tensor, ndim 2, dtype family float, shape (5, 4) as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| post_config | Ran ran on a synthesized input |
dvl-tum/SUSHI/configs/config.py code served (permissive licence) · get_code("e66624d1da3d8c41") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Config. The image it ran in was not recorded. The code mentions cuda, and the harness aliases cuda to the CPU for every sample; whether this run needed that is not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| time | Ran ran; our contract draft was wrong, not the code |
dvl-tum/SUSHI/TrackEval/trackeval/_timing.py code served (permissive licence) · get_code("df1bd31f4da1bed6") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned function. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| find_graph_time_valid_edges | Not yet run unverified (harvested, no recorded run) |
dvl-tum/SUSHI/src/utils/graph_utils.py code served (permissive licence) · get_code("c2c1aafcffd63e68") How it ranno invocation recorded. |
| get_arguments | Not yet run unverified (harvested, no recorded run) |
dvl-tum/SUSHI/configs/config.py code served (permissive licence) · get_code("a03bcbfa3e6634c3") How it ranno invocation recorded. |
Of 11 samples lifted from this paper's linked repositories, 11 carry a function identity and 0 do not. Of the 11 distinct functions with an identity, 4 are also present in other papers whose code we hold (4 with at least one paper dated earlier, 0 the same month, 4 later) and 7 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| geometric_mean | 6 other papers 4 dated earlier, 2 later |
1905.04804 (2019-05) Video Instance Segmentation |
1912.07515 (2019-12) Learning a Neural Solver for Multiple Object Tracking 2009.07736 (2020-09) HOTA: A Higher Order Metric for Evaluating Multi-Object Tracking and 3 more not named here |
| jaccard | 6 other papers 4 dated earlier, 2 later |
1905.04804 (2019-05) Video Instance Segmentation |
1912.07515 (2019-12) Learning a Neural Solver for Multiple Object Tracking 2009.07736 (2020-09) HOTA: A Higher Order Metric for Evaluating Multi-Object Tracking and 3 more not named here |
| load_multiple_tracker_summaries | 6 other papers 4 dated earlier, 2 later |
1905.04804 (2019-05) Video Instance Segmentation |
1912.07515 (2019-12) Learning a Neural Solver for Multiple Object Tracking 2009.07736 (2020-09) HOTA: A Higher Order Metric for Evaluating Multi-Object Tracking and 3 more not named here |
| time | 6 other papers 4 dated earlier, 2 later |
1905.04804 (2019-05) Video Instance Segmentation |
1912.07515 (2019-12) Learning a Neural Solver for Multiple Object Tracking 2009.07736 (2020-09) HOTA: A Higher Order Metric for Evaluating Multi-Object Tracking and 3 more not named here |
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
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.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2212.03038")
get_code_for_paper("2212.03038")
have("2212.03038")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2212.03038.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2212.03038)
Connect an agent — have() is free.