Reports until 02:46, Monday 16 January 2017
H1 AOS
travis.sadecki@LIGO.ORG - posted 02:46, Monday 16 January 2017 - last comment - 10:54, Monday 16 January 2017(33334)
Ops Owl Shift Summary

TITLE: 01/16 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Corrective Maintenance (this is the best fit I could find for this state in the Observatory Mode Wiki)
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Nutsinee stayed to see through the IA that she started at the end of her shift.  As has been the case for the past several shifts, all seemed well until LOWNOISE_ASC when we noticed that the ASC-MICH_Y and ASC-DHARD_Y error signals seemed to make a jump and start oscillating.  The beam spot on ASAIR could also be seen ringing up in yaw until the lock broke.  It seems that this could be indicative of an ASC tuning issue.
LOG:  I am abandoning ship and leaving the IFO in DOWN for the remainder of Owl shift.  Keita has given an email OK (with instructions NOT to call anyone tonight) and  Corey has been CC'ed.  Consider this a Mayday call to Commissioners.

NOTE: According to the Observatory Mode Wiki, the Corrective Maintenance state that I am leaving the IFO in is supposed to be accompanied by an FRS ticket.  Since we won't know the cause of the issue until it is fixed, I am asking that Commissioners working on the problem file and close out an appropriate FRS ticket to account for the downtime.  Please let me know if Operators are simply supposed to enter an FRS ticket saying something vague like "IFO won't lock" and we can do that in the future, but for now that doesn't seem very useful to me.  Correct me if I'm wrong.

Comments related to this report
richard.oram@LIGO.ORG - 10:54, Monday 16 January 2017 (33339)
Link

Since you asked for a steer I will provide one. In the event of deciding to put the IFO status into CM an FRS should be opened. This is correct. My expectation is that the on duty operator opens the FRS with a title and content that best describes the deviation from SOP that is being observed. Making an informed guess of the amount of observing time loss thus far is also helpful. Initiating the FRS is helpful to Det Engs and Scientists that will follow up on the fault. Likely the Det Engs will make edits to the title of the FRS and description of the fault as troubleshooting reveals more of the root cause. So the main take away for operators is open an FRS early with the best description you have in the present moment. Do not be afraid of opening an FRS with an incomplete understanding of the what the root cause, this will come later.