Papers › Simulation-based inference for stochastic gravitational wave background data analysis

Simulation-based inference for stochastic gravitational wave background data analysis

14 Sep 2023arXiv:2309.07954links table onlyarchive 2025-07-28

James Alvey, Uddipta Bhardwaj, Valerie Domcke, Mauro Pieroni, Christoph Weniger

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 next generation of space- and ground-based facilities promise to reveal an entirely new picture of the gravitational wave sky: thousands of galactic and extragalactic binary signals, as well as stochastic gravitational wave backgrounds (SGWBs) of unresolved astrophysical and possibly cosmological signals. These will need to be disentangled to achieve the scientific goals of experiments such as LISA, Einstein Telescope, or Cosmic Explorer. We focus on one particular aspect of this challenge: reconstructing an SGWB from (mock) LISA data. We demonstrate that simulation-based inference (SBI) - specifically truncated marginal neural ratio estimation (TMNRE) - is a promising avenue to overcome some of the technical difficulties and compromises necessary when applying more traditional methods such as Monte Carlo Markov Chains (MCMC). To highlight this, we show that we can reproduce results from traditional methods both for a template-based and agnostic search for an SGWB. Moreover, as a demonstration of the rich potential of SBI, we consider the injection of a population of low signal-to-noise ratio supermassive black hole transient signals into the data. TMNRE can implicitly marginalize over this complicated parameter space, enabling us to directly and accurately reconstruct the stochastic (and instrumental noise) contributions. We publicly release our TMNRE implementation in the form of the code saqqara.

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

Code

Syntology Ran 3 of 4 code samples harvested from 1 repository linked to this paper; 1 has no recorded run. Of those that ran: 3 ran with no contract checked.

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

peregrine-gw/saqqara officialmentioned in papermentioned on GitHubjaxMIT 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

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

3ran
1unverified

Licence: 0 of the 4 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 peregrine-gw/saqqara. “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.

load_settings peregrine-gw/saqqara/saqqara/config.py official repository ran MIT (permissive) · 2bf10f5b8a8a59c7 · report
setup_logger peregrine-gw/saqqara/saqqara/training.py official repository ran MIT (permissive) · 73de8659377256a1 · report
setup_scheduler peregrine-gw/saqqara/saqqara/training.py official repository ran MIT (permissive) · 2c5e398f81d02fef · report
get_settings peregrine-gw/saqqara/saqqara/config.py official repository unverified MIT (permissive) · f6235727b33ac148 · 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