LIGO Document T2600242-v1

Constraining astrophysical parameter bias due to glitches in future ground-based gravitational-wave detectors

Document #:
LIGO-T2600242-v1
Document type:
T - Technical notes
Other Versions:
Abstract:
Transient detector noise artifacts, or glitches, that coincide in time and frequency with gravitational-wave signals can bias the inferred astrophysical parameters of compact binary coalescences, particularly the black hole spins. We investigate how this bias evolves as detector sensitivity increases by simulating binary black hole signals based on GW200129 and GW191109, contaminated by glitches, under projected sensitivities for LIGO A# and Cosmic Explorer (CE). We consider two limiting scenarios in which either the glitch amplitude or the glitch signal-to-noise ratio (SNR) is held fixed relative to present-day detectors, and perform Bayesian parameter estimation on each simulated data set. We find that glitches injected with fixed SNR produce progressively smaller absolute biases in the effective spin parameters as the signal SNR increases, whereas glitches injected with fixed amplitude continue to induce biases of comparable magnitude despite substantially narrower posterior distributions. Lowering the minimum analysis frequency from 20 to 14 Hz further reduces the fixed-SNR glitch bias to a negligible level. Adopting a signal SNR of 150 as the threshold above which bias from a fixed-SNR glitch (with glitch SNR 6-8) becomes negligible, we simulate a population of binary black hole mergers and find that only 0.03% of detections in an A# network and 2-5% in a CE network exceed it, suggesting that most future detections would still require mitigation if they overlapped a comparable glitch. These results show that the impact of glitches in future detectors depends critically on how glitch populations scale with detector sensitivity, and provide insight into when computationally expensive glitch-mitigation methods remain necessary.
Files in Document:
Other Files:
Keywords:
SURF26
Referenced by:

DCC Version 3.6.0, contact DCC Help