Papers › Understanding spectral artefacts in SKA-LOW 21-cm cosmology experiments: the impact of...

Understanding spectral artefacts in SKA-LOW 21-cm cosmology experiments: the impact of cable reflections

6 Feb 2024arXiv:2402.04008links table onlyarchive 2025-07-28

Oscar Sage David O'Hara, Fred Dulwich, Eloy de Lera Acedo, Jiten Dhandha, Thomas Gessey-Jones, Dominic Anstey, Anastasia Fialkov

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.

The Cosmic Dawn was marked by the formation of the first stars, and preceded the Epoch of Reionization (EoR), when the Universe underwent a fundamental transformation caused by the radiation from these first stars and galaxies. Interferometric 21-cm experiments aim to probe redshifted neutral hydrogen signals from these periods, constraining the conditions of the early Universe. The SKA-Low instrument of the Square Kilometre Array (SKA) is envisaged to be the largest and most sensitive radio telescope at metre and centimetre wavelengths. The latest Aperture Array Verification Systems feature 7-m coaxial transmission lines connecting the low noise amplifiers to optical transmitters at the front of the analogue-receiving chain. An impedance mismatch between these components results in a partially reflected electromagnetic signal, introducing chromatic aberrations into the instrument bandpass. This causes power from the foreground signals to appear at higher delays, potentially contaminating the 'EoR window', a region in which the 21-cm signal should be detectable. We present an end-to-end simulation pipeline for SKA-Low using a composite sky model combining radio foregrounds from the Galactic and Extragalactic All-Sky MWA (GLEAM) Survey, Haslam $408\,$MHz, and a 1.5-cGpc 21-cm brightness temperature cube generated with the 21cmSPACE simulator. We derive a model for the scattering parameters of a coaxial transmission line in terms of its specifications and bulk material properties. Assuming identical cables of length $\leq 15.0\,$m with impedance mismatch $\leq 10\, \Omega$, the reflection is confined below the EoR window. However, we demonstrate that even a 0.1 per cent length tolerance introduces contamination with an absolute fractional difference of ∼10 per cent across all accessible k-modes.

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="2402.04008")

Code

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

By repository: community (archive-listed): 2 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

2 samples harvested; 0 ran; 0 honoured the contract we drafted; 2 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.

2unverified

Licence: 0 of the 2 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 ycliu23/Cambridge-SKA-SDC3-Foregrounds. “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.

error_prop ycliu23/Cambridge-SKA-SDC3-Foregrounds/pipeline/cal_ps.py community (archive-listed) unverified MIT (permissive) · 6862744dc265a80b · report
ratio ycliu23/Cambridge-SKA-SDC3-Foregrounds/pipeline/cal_ps.py community (archive-listed) unverified MIT (permissive) · 9a9729fbe4891041 · 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