5 of 5 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; 0 honoured the contract we drafted, 0 violated it and 4 have no contract verdict; 1 failure of our instrument; 0 no recorded run), measured 2026-11-21; 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/2106.03089.json · badge: /api/ran/2106.03089.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 |
|---|---|---|
| ubc-vision/RefTR | canonical (classifier label) classifier basis: census |
5 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| convert_examples_to_features | Ran ran; our contract draft was wrong, not the code |
ubc-vision/RefTR/datasets/lang_utils.py code served (permissive licence) · get_code("db595e458994d7d0") 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 list, ndim 1, 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.
|
| mlp_mapping | Ran ran on a synthesized input |
ubc-vision/RefTR/models/reftr_transformer.py code served (permissive licence) · get_code("7a5bae282fd6c7e4") 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 Sequential. 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.
|
| read_examples | Ran ran on a synthesized input |
ubc-vision/RefTR/datasets/lang_utils.py code served (permissive licence) · get_code("cec54f25f6a14bf4") 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 list, ndim 1, 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.
|
| to_cuda | Ran ran on a synthesized input |
ubc-vision/RefTR/engine_vg.py code served (permissive licence) · get_code("b46073da47f49206") 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. 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.
|
| to_cuda | Ran ran on a synthesized input |
ubc-vision/RefTR/datasets/data_prefetcher.py code served (permissive licence) · get_code("6b447c14f1b53ea9") 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. 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.
|
Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 3 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 0 the same month, 2 later) and 2 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 |
|---|---|---|---|
| read_examples | 7 other papers 3 dated earlier, 4 later |
1908.06354 (2019-08) A Fast and Accurate One-Stage Approach to Visual Grounding |
2008.01059 (2020-08) Improving One-stage Visual Grounding by Recursive Sub-query Construction 2104.08541 (2021-04) TransVG: End-to-End Visual Grounding with Transformers and 4 more not named here |
| convert_examples_to_features | 6 other papers 3 dated earlier, 3 later |
1908.06354 (2019-08) A Fast and Accurate One-Stage Approach to Visual Grounding |
2008.01059 (2020-08) Improving One-stage Visual Grounding by Recursive Sub-query Construction 2104.08541 (2021-04) TransVG: End-to-End Visual Grounding with Transformers and 3 more not named here |
| to_cuda | 1 other paper 1 dated earlier |
2010.04159 (2020-10) Deformable DETR: Deformable Transformers for End-to-End Object Detection |
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-21.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
As an important step towards visual reasoning, visual grounding (e.g., phrase localization, referring expression comprehension/segmentation) has been widely explored Previous approaches to referring expression comprehension (REC) or segmentation (RES) either suffer from limited performance, due to a two-stage setup, or require the designing of complex task-specific one-stage architectures. In this paper, we propose a simple one-stage multi-task framework for visual grounding tasks. Specifically, we leverage a transformer architecture, where two modalities are fused in a visual-lingual encoder. In the decoder, the model learns to generate contextualized lingual queries which are then decoded and used to directly regress the bounding box and produce a segmentation mask for the corresponding referred regions. With this simple but highly contextualized model, we outperform state-of-the-arts methods by a large margin on both REC and RES tasks. We also show that a simple pre-training schedule (on an external dataset) further improves the performance. Extensive experiments and ablations illustrate that our model benefits greatly from contextualized information and multi-task training.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2106.03089")
get_code_for_paper("2106.03089")
have("2106.03089")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2106.03089.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2106.03089)
Connect an agent — have() is free.