Searching for stochastic gravitational waves using data from the two colocated LIGO Hanford detectors

Searches for a stochastic gravitational-wave background (SGWB) using terrestrial detectors typically involve cross-correlating data from pairs of detectors. The sensitivity of such cross-correlation analyses depends, among other things, on the separation between the two detectors: the smaller the separation, the better the sensitivity. Hence, a colocated detector pair is more sensitive to a gravitational-wave background than a noncolocated detector pair. However, colocated detectors are also expected to suffer from correlated noise from instrumental and environmental effects that could contaminate the measurement of the background. Hence, methods to identify and mitigate the effects of correlated noise are necessary to achieve the potential increase in sensitivity of colocated detectors. Here we report on the first SGWB analysis using the two LIGO Hanford detectors and address the complications arising from correlated environmental noise. We apply correlated noise identification and mitigation techniques to data taken by the two LIGO Hanford detectors, H1 and H2, during LIGO's fifth science run. At low frequencies, 40--460 Hz, we are unable to sufficiently mitigate the correlated noise to a level where we may confidently measure or bound the stochastic gravitational-wave signal. However, at high frequencies, 460--1000 Hz, these techniques are sufficient to set a 95% confidence level upper limit on the gravitational-wave energy density of $\mathrm{\ensuremath{\Omega}}(f)<7.7\ifmmode\times\else\texttimes\fi{}1{0}^{\ensuremath{-}4}(f/900\text{ }\text{ }\mathrm{Hz}{)}^{3}$, which improves on the previous upper limit by a factor of $\ensuremath{\sim}180$. In doing so, we demonstrate techniques that will be useful for future searches using advanced detectors, where correlated noise (e.g., from global magnetic fields) may affect even widely separated detectors.

Récupéré en direct depuis OpenAlex et désinversé. Les résumés ne sont pas conservés dans cette base de données : les index inversés représentent 8,6 Go des 9,3 Go de texte de la base, et le serveur dispose de 13 Go libres.