Wei Zhang, Hang Xu, Jiachen Lu, Li Zhang, Feng Wen, Xinyue Cai, Renyuan Peng
4 of 4 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, 1 violated it and 0 have no contract verdict; 3 failures of our instrument; 0 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/2401.17609.json · badge: /api/ran/2401.17609.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 |
|---|---|---|
| fudan-zvg/RoadNet | canonical (classifier label) classifier basis: census |
4 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| cumsum_trick | Ran ran; our contract draft was wrong, not the code |
fudan-zvg/RoadNet/RoadNetwork-2.0.1/rntr/LiftSplatShoot.py code served (permissive licence) · get_code("8945de8524a23486") 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.
|
| gen_dx_bx | Ran ran, violated the contract we drafted |
fudan-zvg/RoadNet/RoadNetwork-2.0.1/rntr/LiftSplatShoot.py code served (permissive licence) · get_code("bb7f8ca26bf25aec") 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.
|
| node_match | Ran ran; our contract draft was wrong, not the code |
fudan-zvg/RoadNet/RoadNetwork-2.0.1/rntr/transforms/roadnet_reach_dist_eval.py code served (permissive licence) · get_code("d7b613aa78ab0d22") 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 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.
|
| pos2posemb3d | Ran ran; our contract draft was wrong, not the code |
fudan-zvg/RoadNet/RoadNetwork-2.0.1/rntr/ar_lanegraph2seq_head.py pointer only (licence: MIT); the stored copy get_code serves, from HDETR/H-PETR-3D, is pointer only (licence: NOASSERTION) · get_code("718ca707584a0928") How it ranThe body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from HDETR/H-PETR-3D, and GitHub could not classify the licence of that repository (NOASSERTION). The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 2 are also present in other papers whose code we hold (2 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 |
|---|---|---|---|
| pos2posemb3d | 6 other papers 5 dated earlier, 1 later |
2206.01256 (2022-06) PETRv2: A Unified Framework for 3D Perception from Multi-Camera Images |
2207.13080 (2022-07) DETRs with Hybrid Matching 2304.01054 (2023-04) VoxelFormer: Bird's-Eye-View Feature Generation based on Dual-view Attention for Multi-view 3D Object Detection and 3 more not named here |
| cumsum_trick | 4 other papers 3 dated earlier, 1 later |
2210.07729 (2022-10) Model-Based Imitation Learning for Urban Driving |
2304.11379 (2023-04) LiDAR2Map: In Defense of LiDAR-Based Semantic Map Construction Using Online Camera Distillation 2311.11762 (2023-11) MUVO: A Multimodal Generative World Model for Autonomous Driving with Geometric Representations and 1 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.
Understanding road structures is crucial for autonomous driving. Intricate road structures are often depicted using lane graphs, which include centerline curves and connections forming a Directed Acyclic Graph (DAG). Accurate extraction of lane graphs relies on precisely estimating vertex and edge information within the DAG. Recent research highlights Transformer-based language models' impressive sequence prediction abilities, making them effective for learning graph representations when graph data are encoded as sequences. However, existing studies focus mainly on modeling vertices explicitly, leaving edge information simply embedded in the network. Consequently, these approaches fall short in the task of lane graph extraction. To address this, we introduce LaneGraph2Seq, a novel approach for lane graph extraction. It leverages a language model with vertex-edge encoding and connectivity enhancement. Our serialization strategy includes a vertex-centric depth-first traversal and a concise edge-based partition sequence. Additionally, we use classifier-free guidance combined with nucleus sampling to improve lane connectivity. We validate our method on prominent datasets, nuScenes and Argoverse 2, showcasing consistent and compelling results. Our LaneGraph2Seq approach demonstrates superior performance compared to state-of-theart techniques in lane graph extraction. Code is available at https://github.com/fudan-zvg/RoadNet
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2401.17609")
get_code_for_paper("2401.17609")
have("2401.17609")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2401.17609.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2401.17609)
Connect an agent — have() is free.