REVIEW 1 cited by
The Impact of Peculiar Velocities on the Estimation of the Hubble Constant from Gravitational Wave Standard Sirens
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
Signed reviews
abstract
In this work we investigate the systematic uncertainties that arise from the calculation of the peculiar velocity when estimating the Hubble constant ($H_0$) from gravitational wave standard sirens. We study the GW170817 event and the estimation of the peculiar velocity of its host galaxy, NGC 4993, when using Gaussian smoothing over nearby galaxies. NGC 4993 being a relatively nearby galaxy, at $\sim 40 \ {\rm Mpc}$ away, is subject to a significant effect of peculiar velocities. We demonstrate a direct dependence of the estimated peculiar velocity value on the choice of smoothing scale. We show that when not accounting for this systematic, a bias of $\sim 200 \ {\rm km \ s ^{-1}}$ in the peculiar velocity incurs a bias of $\sim 4 \ {\rm km \ s ^{-1} \ Mpc^{-1}}$ on the Hubble constant. We formulate a Bayesian model that accounts for the dependence of the peculiar velocity on the smoothing scale and by marginalising over this parameter we remove the need for a choice of smoothing scale. The proposed model yields $H_0 = 68.6 ^{+14.0}_{-8.5}~{\rm km\ s^{-1}\ Mpc^{-1}}$. We demonstrate that under this model a more robust unbiased estimate of the Hubble constant from nearby GW sources is obtained.
Forward citations
Cited by 1 Pith paper
-
Cosmological Inference using Gravitational Wave Standard Sirens: A Mock Data Challenge
A mock data challenge shows that gravitational wave standard sirens can recover an unbiased Hubble constant with galaxy catalogs as incomplete as 25%, using the gwcosmo Bayesian pipeline.
Discussion (0). Continue with ORCID to comment.