Skip to content

Incorrect detector state report?

I was looking at this PyCBC Live event, for which the detector state report lists H1 and L1 as bad (GPS time 1238702182). Being a little surprised that PyCBC Live uploaded an event in bad data, I went to the summary pages and found that

  • H1 was observing stably at the time of the trigger.
  • L1 left observing mode 25 s after the trigger (the relevant L1:DMT-OBS_INTENT:1 segment is listed as 2 1238699661 1238702207 2546.0).

Could someone explain why the detector state report thinks H1 and L1 were in bad state at GPS 1238702182?

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information