MétaCan
Menu
Back to cohort
Record W4284965629 · doi:10.1088/1361-6382/aca238

Subtracting glitches from gravitational-wave detector data during the third LIGO-Virgo observing run

2022· article· en· W4284965629 on OpenAlex
D. Davis, T. B. Littenberg, I. M. Romero-Shaw, M. Millhouse, J. McIver, F. Di Renzo, G. Ashton

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueClassical and Quantum Gravity · 2022
Typearticle
Languageen
FieldPhysics and Astronomy
TopicPulsars and Gravitational Waves Research
Canadian institutionsUniversity of British Columbia
FundersScience and Technology Facilities CouncilNational Science Foundation
KeywordsLIGOPhysicsGravitational waveDetectorGravitational-wave observatoryAstronomyAstrophysicsOptics

Abstract

fetched live from OpenAlex

Abstract Data from ground-based gravitational-wave detectors contains numerous short-duration instrumental artifacts, called ‘glitches’. The high rate of these artifacts in turn results in a significant fraction of gravitational-wave signals from compact binary coalescences overlapping glitches. In LIGO-Virgo’s third observing run, ≈20% of gravitational-wave source candidates required some form of mitigation due to glitches. This was the first observing run where glitch subtraction was included as a part of LIGO-Virgo-KAGRA data analysis methods for a large fraction of detected gravitational-wave events. This work describes the methods to identify glitches, the decision process for deciding if mitigation was necessary, and the two algorithms, BayesWave and gwsubtract , that were used to model and subtract glitches. Through case studies of two events, GW190424_180648 and GW200129_065458, we evaluate the effectiveness of the glitch subtraction, compare the statistical uncertainties in the relevant glitch models, and identify potential limitations in these glitch subtraction methods. We finally outline the lessons learned from this first-of-its-kind effort for future observing runs.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.349
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0020.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.052
GPT teacher head0.316
Teacher spread0.263 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it