Papers › Cosmology with the Galaxy Bispectrum Multipoles: Optimal Estimation and Application to...
Cosmology with the Galaxy Bispectrum Multipoles: Optimal Estimation and Application to BOSS Data
Mikhail M. Ivanov, Oliver H. E. Philcox, Giovanni Cabass, Takahiro Nishimichi, Marko Simonović, Matias Zaldarriaga
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.
We present a framework for self-consistent cosmological analyses of the full-shape anisotropic bispectrum, including the quadrupole (ℓ=2) and hexadecapole (ℓ=4) moments. This features a novel window-free algorithm for extracting the latter quantities from data, derived using a maximum-likelihood prescription. Furthermore, we introduce a theoretical model for the bispectrum multipoles (which does not introduce new free parameters), and test both aspects of the pipeline on several high-fidelity mocks, including the PT Challenge suite of gigantic cumulative volume. This establishes that the systematic error is significantly below the statistical threshold, both for the measurement and modeling. As a realistic example, we extract the large-scale bispectrum multipoles from BOSS DR12 and analyze them in combination with the power spectrum data. Assuming a minimal ΛCDM model, with a BBN prior on the baryon density and a \textit{Planck} prior on nₛ, we can extract the remaining cosmological parameters directly from the clustering data. The inclusion of the unwindowed higher-order (ℓ>0) large-scale bispectrum multipoles is found to moderately improve one-dimensional cosmological parameter posteriors (at the 5%-10% level), though these multipoles are detected only in three out of four BOSS data segments at ≈5σ. Combining information from the power spectrum and bispectrum multipoles, the real space power spectrum, and the post-reconstructed BAO data, we find H₀ = 68.2±0.8 km s⁻¹Mpc⁻¹, Ωₘ =0.33±0.01 and σ₈ = 0.736±0.033 (the tightest yet found in perturbative full-shape analyses). Our estimate of the growth parameter S₈=0.77±0.04 agrees with both weak lensing and CMB results.
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="2302.04414")
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.
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 oliverphilcox/spectra-without-windows. “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.
c0ba8424527608d8 · report
ee3a321b25d47e0d · report
8a079b39cbc218ef · 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