aaron.viets@LIGO.ORG - posted 09:39, Sunday 16 April 2017 - last comment - 16:20, Sunday 16 April 2017(35569)
LHO pipeline restarted to correct bad kappas and h(t)
I have just restarted the primary and redundant pipelines at LHO at GPS time 1176395700. Due to an issue with the computed kappas being out of the expected range, h(t) was marked bad by the calib_state_vector. This is due to a bug in the most recent release of the calibration code, gstlal-calibration-1.1.5-v1. For more information on this bug and the proposed fix, see https://bugs.ligo.org/redmine/issues/5494
Is this something Operators should worry about, or is it handled by others offsite? Jim & Cheryl both alogged status and that Aaron was working on/fixed it. Just wondering if this rises to the state of needing an alarm because it affects H1 data, or does it just mean one of our tools is having an issue (i.e. GWI.stat being yellow and the Daily Summary Pages reporting an on BNS range).
Should we be checking the GWI.stat through the shift (I can put it in our Shift Check Sheet), or is this something we leave to off-site staff? For GWI.stat's Help Page it says we should report bugs to Peter Shawhan. I'm not sure of who we report Summary Page bugs to.