Virgo Detector Characterization and Data Quality: tools

TL;DR

This paper reviews the tools developed for Virgo detector characterization and data quality during the third LIGO-Virgo observation run, highlighting their roles in ensuring data integrity and supporting gravitational-wave detection.

Contribution

It provides a comprehensive overview of the data quality tools used by the Virgo DetChar group during O3, detailing their functionalities and applications.

Findings

Tools enabled effective noise identification and monitoring.

Improved data quality assessment during the O3 run.

Facilitated rapid analysis and public alert processing.

Abstract

Detector characterization and data quality studies -- collectively referred to as {\em DetChar} activities in this article -- are paramount to the scientific exploitation of the joint dataset collected by the LIGO-Virgo-KAGRA global network of ground-based gravitational-wave (GW) detectors. They take place during each phase of the operation of the instruments (upgrade, tuning and optimization, data taking), are required at all steps of the dataflow (from data acquisition to the final list of GW events) and operate at various latencies (from near real-time to vet the public alerts to offline analyses). This work requires a wide set of tools which have been developed over the years to fulfill the requirements of the various DetChar studies: data access and bookkeeping; global monitoring of the instruments and of the different steps of the data processing; studies of the global properties of the noise at the detector outputs; identification and follow-up of noise peculiar features (whether they be transient or continuously present in the data); quick processing of the public alerts. The present article reviews all the tools used by the Virgo DetChar group during the third LIGO-Virgo Observation Run (O3, from April 2019 to March 2020), mainly to analyse the Virgo data acquired at EGO. Concurrently, a companion article focuses on the results achieved by the DetChar group during the O3 run using these tools.