ArchEnemy: Removing scattered-light glitches from gravitational wave data

Data recorded by gravitational wave detectors includes many non-astrophysical transient noise bursts, the most common of which is caused by scattered-light within the detectors. These so-called ``glitches'' in the data impact the ability to both observe and characterize incoming gravitational wave signals. In this work we use a scattered-light glitch waveform model to identify and characterize scattered-light glitches in a representative stretch of gravitational wave data. We identify $2749$ scattered-light glitches in $5.96$ days of LIGO-Hanford data and $1306$ glitches in $5.93$ days of LIGO-Livingston data taken from the third LIGO-Virgo observing run. By subtracting identified scattered-light glitches we demonstrate an increase in the sensitive volume of the gravitational wave search for binary black hole signals by $\sim1\%$.Comment: 30 pages + acknowledgements and references, 13 figure

Unified p astro for gravitational waves: Consistently combining information from multiple search pipelines

Recent gravitational-wave transient catalogs have used p astro, the probability that a gravitational-wave candidate is astrophysical, to select interesting candidates for further analysis. Unlike false alarm rates, which exclusively capture the statistics of the instrumental noise triggers, p astro incorporates the rate at which triggers are generated by both astrophysical signals and instrumental noise in estimating the probability that a candidate is astrophysical. Multiple search pipelines can independently calculate p astro, each employing a specific data reduction. While the range of p astro results can help indicate the range of uncertainties in its calculation, it complicates interpretation and subsequent analyses. We develop a statistical formalism to calculate a unified p astro for gravitational-wave candidates, consistently accounting for triggers from all pipelines, thereby incorporating extra information about a signal that is not available with any one single pipeline. We demonstrate the properties of this method using a toy model and by application to the publicly available list of gravitational-wave candidates from the first half of the third LIGO-Virgo-KAGRA observing run. Adopting a unified p astro for future catalogs would provide a simple and easy-to-interpret selection criterion that incorporates a more complete understanding of the strengths of the different search pipelines

Low-latency gravitational wave alert products and their performance in anticipation of the fourth LIGO-Virgo-KAGRA observing run

Multi-messenger searches for binary neutron star (BNS) and neutron star-black hole (NSBH) mergers are currently one of the most exciting areas of astronomy. The search for joint electromagnetic and neutrino counterparts to gravitational wave (GW)s has resumed with Advanced LIGO (aLIGO)'s, Advanced Virgo (AdVirgo)'s and KAGRA's fourth observing run (O4). To support this effort, public semi-automated data products are sent in near real-time and include localization and source properties to guide complementary observations. Subsequent refinements, as and when available, are also relayed as updates. In preparation for O4, we have conducted a study using a simulated population of compact binaries and a Mock Data Challenge (MDC) in the form of a real-time replay to optimize and profile the software infrastructure and scientific deliverables. End-to-end performance was tested, including data ingestion, running online search pipelines, performing annotations, and issuing alerts to the astrophysics community. In this paper, we present an overview of the low-latency infrastructure as well as an overview of the performance of the data products to be released during O4 based on a MDC. We report on expected median latencies for the preliminary alert of full bandwidth searches (29.5 s) and for the creation of early warning triggers (-3.1 s), and show consistency and accuracy of released data products using the MDC. This paper provides a performance overview for LVK low-latency alert structure and data products using the MDC in anticipation of O4

gwastro/pycbc: v2.2.2 release of PyCBC

This is the v2.2.2 release of PyCBC. Adds a variety of incremental improvements with respect to v2.2.1, including the ability to use the SEOBNRv5 waveform. See the commit history for more details. A Docker container for this release is available from the pycbc/pycbc-el8 repository on Docker Hub and can be downloaded using the command: docker pull pycbc/pycbc-el8:v2.2.2 On a machine with CVMFS installed, a pre-built virtual environment is available for Red Hat 8 compatible operating systems by running the command: source /cvmfs/software.igwn.org//pycbc/x86_64_rhel_8/virtualenv/pycbc-v2.2.2/bin/activate A singularity container is available at /cvmfs/singularity.opensciencegrid.org/pycbc/pycbc-el8:v2.2.1 which can be started with the command: singularity shell --home ${HOME}:/srv --pwd /srv --bind /cvmfs --contain --ipc --pid /cvmfs/singularity.opensciencegrid.org/pycbc/pycbc-el8:v2.2.

Low-latency gravitational wave alert products and their performance in anticipation of the fourth LIGO-Virgo-KAGRA observing run

International audienceMulti-messenger searches for binary neutron star (BNS) and neutron star-black hole (NSBH) mergers are currently one of the most exciting areas of astronomy. The search for joint electromagnetic and neutrino counterparts to gravitational wave (GW)s has resumed with Advanced LIGO (aLIGO)'s, Advanced Virgo (AdVirgo)'s and KAGRA's fourth observing run (O4). To support this effort, public semi-automated data products are sent in near real-time and include localization and source properties to guide complementary observations. Subsequent refinements, as and when available, are also relayed as updates. In preparation for O4, we have conducted a study using a simulated population of compact binaries and a Mock Data Challenge (MDC) in the form of a real-time replay to optimize and profile the software infrastructure and scientific deliverables. End-to-end performance was tested, including data ingestion, running online search pipelines, performing annotations, and issuing alerts to the astrophysics community. In this paper, we present an overview of the low-latency infrastructure as well as an overview of the performance of the data products to be released during O4 based on a MDC. We report on expected median latencies for the preliminary alert of full bandwidth searches (29.5 s) and for the creation of early warning triggers (-3.1 s), and show consistency and accuracy of released data products using the MDC. This paper provides a performance overview for LVK low-latency alert structure and data products using the MDC in anticipation of O4

Low-latency gravitational wave alert products and their performance in anticipation of the fourth LIGO-Virgo-KAGRA observing run

International audienceMulti-messenger searches for binary neutron star (BNS) and neutron star-black hole (NSBH) mergers are currently one of the most exciting areas of astronomy. The search for joint electromagnetic and neutrino counterparts to gravitational wave (GW)s has resumed with Advanced LIGO (aLIGO)'s, Advanced Virgo (AdVirgo)'s and KAGRA's fourth observing run (O4). To support this effort, public semi-automated data products are sent in near real-time and include localization and source properties to guide complementary observations. Subsequent refinements, as and when available, are also relayed as updates. In preparation for O4, we have conducted a study using a simulated population of compact binaries and a Mock Data Challenge (MDC) in the form of a real-time replay to optimize and profile the software infrastructure and scientific deliverables. End-to-end performance was tested, including data ingestion, running online search pipelines, performing annotations, and issuing alerts to the astrophysics community. In this paper, we present an overview of the low-latency infrastructure as well as an overview of the performance of the data products to be released during O4 based on a MDC. We report on expected median latencies for the preliminary alert of full bandwidth searches (29.5 s) and for the creation of early warning triggers (-3.1 s), and show consistency and accuracy of released data products using the MDC. This paper provides a performance overview for LVK low-latency alert structure and data products using the MDC in anticipation of O4