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

Data quality up to the third observing run of advanced LIGO: Gravity Spy glitch classifications

2023· article· en· W4318015141 on OpenAlex
J Glanzer, S. Banagiri, S B Coughlin, S. Soni, M. Zevin, C. P. L. Berry, O. Patane, S Bahaadini, N Rohani, Kevin Crowston, V. Kalogera, Carsten Østerlund, Laura Trouille, Aggelos K. Katsaggelos

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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueClassical and Quantum Gravity · 2023
Typearticle
Languageen
FieldPhysics and Astronomy
TopicPulsars and Gravitational Waves Research
Canadian institutionsnot available
FundersDivision of Information and Intelligent SystemsDivision of PhysicsCanadian Institute for Advanced ResearchNorthwestern UniversityNational Aeronautics and Space AdministrationScience and Technology Facilities CouncilNational Science Foundation
KeywordsLIGOGlitchGravitational wavePhysicsObservatoryNoise (video)DetectorSkyInterferometryWaveformGravitational-wave observatoryAstronomyComputer scienceOpticsArtificial intelligence

Abstract

fetched live from OpenAlex

Abstract Understanding the noise in gravitational-wave detectors is central to detecting and interpreting gravitational-wave signals. Glitches are transient, non-Gaussian noise features that can have a range of environmental and instrumental origins. The Gravity Spy project uses a machine-learning algorithm to classify glitches based upon their time–frequency morphology. The resulting set of classified glitches can be used as input to detector-characterisation investigations of how to mitigate glitches, or data-analysis studies of how to ameliorate the impact of glitches. Here we present the results of the Gravity Spy analysis of data up to the end of the third observing run of advanced laser interferometric gravitational-wave observatory (LIGO). We classify 233981 glitches from LIGO Hanford and 379805 glitches from LIGO Livingston into morphological classes. We find that the distribution of glitches differs between the two LIGO sites. This highlights the potential need for studies of data quality to be individually tailored to each gravitational-wave observatory.

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 categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.603
Threshold uncertainty score0.548

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.001
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.001
Research integrity0.0000.000
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.110
GPT teacher head0.416
Teacher spread0.306 · 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