Papers › Correcting for interloper contamination in the power spectrum with neural networks

Correcting for interloper contamination in the power spectrum with neural networks

9 Apr 2025arXiv:2504.06919links table onlyarchive 2025-07-28

Marina S. Cagliari, Azadeh Moradinezhad Dizgah, Francisco Villaescusa-Navarro

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.

Modern slitless spectroscopic surveys, such as Euclid and the Roman Space Telescope, collect vast numbers of galaxy spectra but suffer from low signal-to-noise ratios. This often leads to incorrect redshift assignments when relying on a single emission line, due to noise spikes or contamination from non-target emission lines, commonly referred to as redshift interlopers. We propose a machine learning approach to correct the impact of interlopers at the level of measured summary statistics, focusing on the power spectrum monopole and line interlopers as a proof of concept. To model interloper effects, we use halo catalogs from the Quijote simulations as proxies for galaxies, displacing a fraction of halos by the distance corresponding to the redshift offset between target and interloper galaxies. This yields contaminated catalogs with varying interloper fractions across a wide range of cosmologies from the Quijote suite. We train a neural network on the power spectrum monopole, alone or combined with the bispectrum monopole, from contaminated mocks to estimate the interloper fraction and reconstruct the cleaned power spectrum. We evaluate performance in two settings: one with fixed cosmology and another where cosmological parameters vary under broad priors. In the fixed case, the network recovers the interloper fraction and corrects the power spectrum to better than 1% accuracy. When cosmology varies, performance degrades, but adding bispectrum information significantly improves results, reducing the interloper fraction error by 40-60%. We also study the method's performance as a function of the size of the training set and find that optimal strategies depend on the correlation between target and interloper samples: bispectrum information aids performance when target and interloper galaxies are uncorrelated, while tighter priors are more effective when the two are strongly correlated.

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 9 code samples harvested from 1 repository linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 9 samples from 1 repository, 5 ran (5 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.

Levels written on 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

mcagliari/nointernet officialmentioned in papermentioned on GitHubpytorchMITSyntology: 9 samples, 5 ran (0 instrument-failed) · 4 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

9 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. 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.

5ran
4unverified

Licence: 0 of the 9 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 mcagliari/nointernet. “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. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “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.

mcagliari/nointernet official repository 9 samples, 5 ran (0 instrument-failed) · 4 unverified
fraction_type src/catalogs-stats/Bk_displace_all.py ran fingerprinted MIT (permissive) · 5344ecff122e916f · report fixture: signature arg:str/0/str · returned float · level recorded 2026-09-25
normalize_02 src/training/NoInterNet_model.py ran fingerprinted MIT (permissive) · 52519005744904b3 · report fixture: signature Pks:ndarray/2/float, nP:int/0/int · returned tuple · level recorded 2026-09-25
normalize_Pk src/training/NoInterNet_model.py ran fingerprinted MIT (permissive) · 301ad3e3f1cf155b · report fixture: signature Pks:ndarray/2/float · returned tuple · level recorded 2026-09-25
objective in 14 papers src/training/NoInterNet_hyper_optimization.py ran MIT (permissive) · 1a265dffcebeaf86 · report fixture: returned float · level recorded 2026-09-25
objective in 14 papers src/training/NoInterNet_hyper_optimization_PB.py ran MIT (permissive) · 1cae86a8911fca0a · report fixture: returned float · level recorded 2026-09-25
load_PBf src/training/NoInterNet_fraction_model.py unverified MIT (permissive) · e58b823ec81527fc · report
load_Pk src/training/NoInterNet_model.py unverified MIT (permissive) · 941bec4e290a0062 · report
load_Pkf src/training/NoInterNet_fraction_model.py unverified MIT (permissive) · 8c992876dbb3274d · report
load_Pkf_feat src/training/NoInterNet_fraction_model.py unverified MIT (permissive) · feae8ae6a4180723 · 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