2 of 3 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 2 have no contract verdict; 0 failures of our instrument; 1 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/2305.03533.json · badge: /api/ran/2305.03533.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 |
|---|---|---|
| tarano/ml-based_source_localization_from_uv-plane | canonical (classifier label) classifier basis: census |
2 ran · 1 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| add_colorbar | Ran ran on a synthesized input |
tarano/ml-based_source_localization_from_uv-plane/src/libs/utils.py code served (permissive licence) · get_code("08c26315474793da") 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 Colorbar. 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.
|
| makeDir | Ran ran on a synthesized input |
tarano/ml-based_source_localization_from_uv-plane/src/libs/utils.py code served (permissive licence) · get_code("4939c5a483a5724b") 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 str. 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.
|
| none_or_str | Not yet run unverified (harvested, no recorded run) |
tarano/ml-based_source_localization_from_uv-plane/src/libs/utils.py code served (permissive licence) · get_code("2fc6fdb85f13dc41") How it ranno invocation recorded. |
Of 3 samples lifted from this paper's linked repositories, 3 carry a function identity and 0 do not. Of the 3 distinct functions with an identity, 1 are also present in other papers whose code we hold (1 with at least one paper dated earlier, 1 the same month, 1 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 |
|---|---|---|---|
| none_or_str | 16 other papers 3 dated earlier, 1 the same month, 12 later |
1810.01845 (2018-10) Task-Oriented Hand Motion Retargeting for Dexterous Manipulation Imitation |
1909.10893 (2019-09) Recurrent Independent Mechanisms 2109.11251 (2021-09) Trust Region Policy Optimisation in Multi-Agent Reinforcement Learning and 13 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.
In our work, we examine, for the first time, the possibility of fast and efficient source localization directly from the uvobservations, omitting the recovering of the dirty or clean images. We propose a deep neural network-based framework that takes as its input a low-dimensional vector of sampled uvdata and outputs source positions on the sky. We investigated a representation of the complex-valued input uv-data via the real and imaginary and the magnitude and phase components. We provided a comparison of the efficiency of the proposed framework with the traditional source localization pipeline based on the state-of-the-art Python Blob Detection and Source Finder (PyBDSF) method. The investigation was performed on a data set of 9164 sky models simulated using the Common Astronomy Software Applications (CASA) tool for the Atacama Large Millimeter Array (ALMA) Cycle 5.3 antenna configuration. We investigated two scenarios: (i) noise-free as an ideal case and (ii) sky simulations including noise representative of typical extra-galactic millimeter observations. In the noise-free case, the proposed localization framework demonstrates the same high performance as the state-of-the-art PyBDSF method. For noisy data, however, our new method demonstrates significantly better performance, achieving a completeness level that is three times higher for sources with uniform signal-to-noise (S/N) ratios between 1 and 10, and a high increase in completeness in the low S/N regime. Furthermore, the execution time of the proposed framework is significantly reduced (by factors about 30) as compared to traditional methods that include image reconstructions from the uv-plane and subsequent source detections.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2305.03533")
get_code_for_paper("2305.03533")
have("2305.03533")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2305.03533.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2305.03533)
Connect an agent — have() is free.