Jiwen Lu, Jie Zhou, Wenzhao Zheng, Yunpeng Zhang, Yuanhui Huang
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 1 has no contract verdict; 2 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/2302.07817.json · badge: /api/ran/2302.07817.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 |
|---|---|---|
| wzzheng/tpvformer | canonical (classifier label) classifier basis not recorded on the link |
4 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| get_nuScenes_label_name | Ran ran on a synthesized input |
wzzheng/tpvformer/dataloader/dataset.py code served (permissive licence) · get_code("6272d886536cd43e") 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.
|
| iou | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
wzzheng/tpvformer/utils/lovasz_losses.py code served (permissive licence) · get_code("d94639b28b2134ff") 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.
|
| iou_binary | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
wzzheng/tpvformer/utils/lovasz_losses.py code served (permissive licence) · get_code("1211530cd527bd0b") 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 float, ndim 0, dtype family float, shape () 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.
|
| lovasz_grad | Ran ran, violated the contract we drafted |
wzzheng/tpvformer/utils/lovasz_losses.py code served (permissive licence) · get_code("e85b5d21dc5b8382") 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 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.
|
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, 3 are also present in other papers whose code we hold (3 with at least one paper dated earlier, 3 the same month, 3 later) and 1 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 |
|---|---|---|---|
| lovasz_grad | 40 other papers 16 dated earlier, 1 the same month, 23 later · 1 only as an assembly brick |
1505.04597 (2015-05) U-Net: Convolutional Networks for Biomedical Image Segmentation |
1807.10165 (2018-07) UNet++: A Nested U-Net Architecture for Medical Image Segmentation 1811.11721 (2018-11) CCNet: Criss-Cross Attention for Semantic Segmentation and 37 more not named here |
| iou | 24 other papers 9 dated earlier, 1 the same month, 14 later |
1807.10165 (2018-07) UNet++: A Nested U-Net Architecture for Medical Image Segmentation |
1811.11721 (2018-11) CCNet: Criss-Cross Attention for Semantic Segmentation 2003.10778 (2020-03) PanNuke Dataset Extension, Insights and Baselines and 21 more not named here |
| iou_binary | 24 other papers 9 dated earlier, 1 the same month, 14 later |
1807.10165 (2018-07) UNet++: A Nested U-Net Architecture for Medical Image Segmentation |
1811.11721 (2018-11) CCNet: Criss-Cross Attention for Semantic Segmentation 2003.10778 (2020-03) PanNuke Dataset Extension, Insights and Baselines and 21 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.
Vision-based Occupancy Prediction Ground Truth TPVFormer FRONT_LEFT FRONT FRONT_RIGHT Semantic Occupancy Prediction (Ours) LiDAR Seg. (Ours) LiDAR Seg. (Cylinder3D) LiDAR Seg. (Ground Truth) BACK_LEFT BACK BACK_RIGHT barrier construction vehicle motorcycle traffic cone trailer bicycle bus car pedestrian truck driveable surface other flat sidewalk terrain manmade vegetation Camera As Input: Camera As Input: LiDAR As Input: Figure 1. Given only surround-camera RGB images as inputs, our model (trained using only sparse LiDAR point supervision) can predict the semantic occupancy for all volumes in the 3D space. This task is challenging as it requires both geometric and semantic understandings of the 3D scene. We observe that our model can produce even more comprehensive and consistent volume occupancy than the groundtruth on the validation set (not seen during training) of nuScenes [4]. Despite the lack of geometric inputs like LiDAR, our model can accurately identify the 3D positions and sizes of close and distant objects. Particularly, our model even successfully identifies the partially occluded bicycle captured only by two LiDAR points, demonstrating the potential advantage of vision-based 3D semantic occupancy prediction.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2302.07817")
get_code_for_paper("2302.07817")
have("2302.07817")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2302.07817.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2302.07817)
Connect an agent — have() is free.