REVIEW 1 cited by
Is the Radio Source Dipole from NVSS Consistent with the CMB and $\Lambda$CDM?
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
The dipole moment in the angular distribution of the cosmic microwave background (CMB) is thought to originate from the Doppler effect and our motion relative to the CMB frame. Observations of large-scale structure (LSS) should show a related ``kinematic dipole'' and help test the kinematic origin of the CMB dipole. Intriguingly, many previous LSS dipole studies suggest discrepancies with the expectations from the CMB. Here we reassess the apparent inconsistency between the CMB measurements and dipole estimates from the NVSS catalog of radio sources. We find that it is important to account for the shot noise and clustering of the NVSS sources, as well as kinematic contributions, in determining the expected dipole signal. We use the clustering redshift method and a cross-matching technique to refine estimates of the clustering term. We then derive a probability distribution for the expected NVSS dipole in a standard $\Lambda$CDM cosmological model including all (i.e., kinematic, shot-noise and clustering) dipole components. Our model agrees with most of the previous NVSS dipole measurements in the literature at better than $\lesssim 2\sigma$. We conclude that the NVSS dipole is consistent with a kinematic origin for the CMB dipole within $\Lambda$CDM.
Forward citations
Cited by 1 Pith paper
-
Measuring our peculiar velocity from spectroscopic redshift surveys
The B-FOTO method, based on artificial Doppler shifts of galaxy redshifts, recovers the observer's peculiar velocity to about 10% and the matter density parameter to about 3% in full-sky mock surveys.
Discussion (0). Continue with ORCID to comment.