Papers › Challenging interferometric imaging: Machine learning-based source localization from...

Challenging interferometric imaging: Machine learning-based source localization from uv-plane observations

5 May 2023arXiv:2305.03533links table onlyarchive 2025-07-28

O. Taran, O. Bait, M. Dessauges-Zavadsky, T. Holotyak, D. Schaerer, S. Voloshynovskiy

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

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.

PaperPDFCodeCode Syntology ran

In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, Syntology's MCP tool lists every function and class Syntology harvested from this paper and whether it ran (how to connect): get_harvested_code_for_paper(arxiv_id="2305.03533")

Code

Syntology Ran 0 of 3 code samples harvested from 1 repository linked to this paper; 3 have no recorded run.

By repository: official repository: 3 samples from 1 repository, 0 ran. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

3 samples harvested; 0 ran; 0 honoured the contract we drafted; 3 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

3unverified

Licence: 0 of the 3 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from tarano/ml-based_source_localization_from_uv-plane. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples from a repository marked official are listed first. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of four reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

add_colorbar tarano/ml-based_source_localization_from_uv-plane/src/libs/utils.py official repository unverified MIT (permissive) · 08c26315474793da · report
makeDir tarano/ml-based_source_localization_from_uv-plane/src/libs/utils.py official repository unverified MIT (permissive) · 4939c5a483a5724b · report
none_or_str tarano/ml-based_source_localization_from_uv-plane/src/libs/utils.py official repository unverified MIT (permissive) · 2fc6fdb85f13dc41 · report

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections