Full report

Brief Summary

• Total duty cycle of 85.1% 
• PI modes were an issue throughout the four days. They caused a few locklosses and the operators seemed to be damping them and worrying about them fairly often.
• In general the data was pretty good and the duty cycle was great.

Day-to-Day Summary

• Day 1, Thursday the 9th, had a great duty cycle of 91.6%. The was significant PI mode activity and they were blamed for the one lockloss, but upon further analysis the Detchar people and the people on site decided it was probably because of PSL FSS PZT oscillations. aLog
• Day 2, Friday the 10th, had two locklosses assumed to be because of environmental disturbances that were later ruled to be due to PI modes. 7:43 lockloss seemed to be due to the ~50 mph wind at EY. Another lockoss after ~14:30 when an EQ from the Phillipines came through. aLog Later it was suggested that both of these locklosses may have been due to PI modes between 28 - 32 kHz. aLog
• Day 2 also had 2 GraceDB? triggers. One was a glitch at H1 coincident with some random noise at L1. The other had a latency of about 6 million seconds and had an event time of Dec. 2nd 2016. I'm not sure what happened there.
• Day 3, Saturday the 11th, had a couple of early locklosses that were initially mysterious but later determined to be PI mode related as well. After the initial difficulties the rest of the day went smoothly and the IFO remained locked.
• Day 4, Sunday the 12th, had a 1 hour standown time early in the day because of a GRB. At approximately 4:00 a Canadian EQ knocked us out. We entered observing mode again and the operator worked to damp some PI modes. Lost lock at about 14:30 and an official reason for the lockloss was never concluded. After lock was regained again PI modes remained a bit of a challenge.