I think I had seen a paper listing a sources (of non astrophysical origin) of noise for O3a run’s auxiliary channels but cannot seem to find it.
To be specific, there was a mention of one of the air compressors I think and one of the PEM table receiving variable input power as far as I can remember.
I’d suggest looking at this paper [2101.11673] LIGO Detector Characterization in the Second and Third Observing Runs and the list of data quality veto types in LIGO-T2100045-v2: Data Quality Vetoes Applied to the Analysis of LIGO Data from the Third Observing Run.
Thank you for the suggestions! The papers you mentioned describe the classes and categories of noise, but they don’t provide specific events from the O3a run where particular sources caused noise.
For example, in a similar study on the O2 run, researchers identified two specific causes of noise transients: an air compressor and a magnetometer. These sources contributed to spikes in noise transients until the issue was resolved by replacing the compressor.
I don’t think there exists a definitive list of glitch events and their causes, so you’d have to do some work to match things up. You could query the GravitySpy glitch database for certain types of glitch (see Querying Gravity Spy data — GravitySpy 0.1.0+27.g952f923.dirty documentation), get the auxiliary channel information (https://gwosc.org/O3/auxiliary/) for a given data quality veto channel described in LIGO-T2100045-v2: Data Quality Vetoes Applied to the Analysis of LIGO Data from the Third Observing Run, and then correlate the times manually yourself to find glitches that appear when that data quality veto channel is active. You may also want to look at and ask questions on the GravitySpy chat Zooniverse. There’s a long discussion there of the O2 air compressor glitches Zooniverse.
1 Like