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 408MHz, 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 ≤15.0m with impedance mismatch ≤10 Ω, 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 View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

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

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 2 code samples harvested from 1 repository linked to this paper: 0 ran · 2 unverified.

By repository: community (archive-listed): 2 samples from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

ycliu23/Cambridge-SKA-SDC3-Foregrounds mentioned on GitHubMITSyntology: 2 samples, 0 ran · 2 unverified report

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 · 2 unverified. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is 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 “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (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 are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. 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 six 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; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. 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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

ycliu23/Cambridge-SKA-SDC3-Foregrounds community (archive-listed) 2 samples, 0 ran · 2 unverified
error_prop pipeline/cal_ps.py unverified MIT (permissive) · 6862744dc265a80b · report
ratio in 6 papers pipeline/cal_ps.py 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