Chang-Su Kim, Jae-Han Lee, Jinyoung Jun
2 of 2 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, 0 violated it and 0 have no contract verdict; 1 failure 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/2404.19294.json · badge: /api/ran/2404.19294.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 |
|---|---|---|
| jyjunmcl/MSPN_SDR | canonical (classifier label) classifier basis not recorded on the link |
2 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| convert_str_to_num | Ran ran, honoured the contract we drafted |
jyjunmcl/MSPN_SDR/lib/utility.py code served (permissive licence) · get_code("f8ca3cb40c015a0b") 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 int; 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.
|
| make_optimizer_scheduler | Ran ran; our contract draft was wrong, not the code |
jyjunmcl/MSPN_SDR/lib/utility.py code served (permissive licence) · get_code("86a8a5c1d3fbec13") 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.
|
Of 2 samples lifted from this paper's linked repositories, 2 carry a function identity and 0 do not. Of the 2 distinct functions with an identity, 2 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 0 the same month, 2 later) and 0 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 |
|---|---|---|---|
| convert_str_to_num | 3 other papers 2 dated earlier, 1 later |
2007.10042 (2020-07) Non-Local Spatial Propagation Network for Depth Completion |
2303.05021 (2023-03) DiffusionDepth: Diffusion Denoising Approach for Monocular Depth Estimation 2406.11711 (2024-06) OGNI-DC: Robust Depth Completion with Optimization-Guided Neural Iterations |
| make_optimizer_scheduler | 1 other paper 1 later |
2406.11711 (2024-06) OGNI-DC: Robust Depth Completion with Optimization-Guided Neural Iterations |
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.
The main function of depth completion is to compensate for an insufficient and unpredictable number of sparse depth measurements of hardware sensors. However, existing research on depth completion assumes that the sparsity -the number of points or LiDAR lines -is fixed for training and testing. Hence, the completion performance drops severely when the number of sparse depths changes significantly. To address this issue, we propose the sparsityadaptive depth refinement (SDR) framework, which refines monocular depth estimates using sparse depth points. For SDR, we propose the masked spatial propagation network (MSPN) to perform SDR with a varying number of sparse depths effectively by gradually propagating sparse depth information throughout the entire depth map. Experimental results demonstrate that MPSN achieves state-of-the-art performance on both SDR and conventional depth completion scenarios. Codes are available at https:// github.com/jyjunmcl/MSPN_SDR
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2404.19294")
get_code_for_paper("2404.19294")
have("2404.19294")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2404.19294.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2404.19294)
Connect an agent — have() is free.