REVIEW 1 cited by
Towards a multi-tracer neutrino mass measurement with line-intensity mapping
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
abstract
Accurately determining neutrino masses is a main objective of contemporary cosmology. Since massive neutrinos affect structure formation and evolution, probes of large scale structure are sensitive to the sum of their masses. In this work, we explore future constraints on $\sum m_\nu$ utilizing line-intensity mapping (LIM) as a promising emerging probe of the density of our Universe, focusing on the fine-structure [CII] line as an example, and compare these constraints with those derived from traditional galaxy surveys. Additionally, we perform a multi-tracer analysis using velocity tomography via the kinetic Sunyaev-Zeldovich and moving lens effects to reconstruct the three-dimensional velocity field. Our forecasts indicate that the next-generation AtLAST detector by itself can achieve $\sigma_{\Sigma m_\nu} \sim 50$ meV sensitivity. Velocity tomography will further improve these constraints by 4%. Incorporating forecasts for CMB-S4 and DESI-BAO in a comprehensive multi-tracer analysis, while setting a prior on the optical depth to reionization $\tau$ derived using 21-cm forecasted observations, to break degeneracies, we find that a $\gtrsim5\sigma$ detection of $\sum m_\nu\!\sim\! 60$ meV, under the normal hierarchy, is within reach with LIM. Even without a $\tau$ prior, our combined forecast reaches $\sigma_{\Sigma m_\nu} \!\sim\! 18$ meV.
Forward citations
Cited by 1 Pith paper
-
Neutrino Mass Constraints from kSZ Tomography
kSZ tomography will add little to neutrino mass constraints from Stage IV surveys unless the kSZ optical depth degeneracy is broken.
Discussion (0). Continue with ORCID to comment.