Summary of the DQ shift from Thursday 2nd February 00:00 - Sunday 5th February 23:59 (UTC), click here for full report

• "All is well in H1 land." Light snow. Low winds. Low u-seism... high duty cycle, LONG locks ... everyone should have such a peaceful DQ shift.
• BNS ranges between 65 - 70 Mpc, throughout.
• Rather quiet on the glitch front. Omicron glitch rate SNR>5 stable at 0.5 Hz, throughout. SNR>8 glitch rate mostly below 0.01 Hz, throughout.
• Locklosses due to PI, TCS, unknown causes; see full report.
• PI caused multiple lock losses on Feb 2; PI damping frequencies tweaked, per PI damping wiki, fixed the problem (alog 33833).
• Rode through 5.6mag Martinique quake (LLO lost lock). No other significant quakes.
• Wind up to 5 m/s on 2/2, 2/3. More like 2-3 m/s on 2/4, 2/5. Rising towards the end of 2/5 UTC.
• Microseism from 0.4-0.6 um/s on 2/2, 2/3, falling to 0.2-0.3 um/s on 2/4, 2/5. Rising towards the end of 2/5 UTC.
• GRB Alert Standown on 2/5, 18:07:12 UTC. Both LHO and LLO did the manual Injections pause (INJ_TRANS Guardian node manually brought to INJECT_KILL, then back to INJECT_SUCCESS an hour later). Keita posted GRB alert instructions in alog 33903.
• pycbcLive: between 1 and 3 triggers per day above newSNR of 9. Loudest per day: 10.7, 11.2, 13.8, 11.9; these are always from the shortest templates, with durations ~ 0.1s.
• Three GraceDB alerts; all Burst, all rejected: two for DQ reasons, one due to an apparent bug in cWB FAR computation.

Laser Status:
SysStat is good
Front End Power is 34.05W (should be around 30 W)
HPO Output Power is 164.3W
Front End Watch is GREEN
HPO Watch is GREEN

PMC:
It has been locked 7 days, 21 hr 17 minutes (should be days/weeks)
Reflected power = 14.81Watts
Transmitted power = 65.69Watts
PowerSum = 80.5Watts.

FSS:
It has been locked for 0 days 14 hr and 11 min (should be days/weeks)
TPD[V] = 1.753V (min 0.9V)

ISS:
The diffracted power is around 2.0% (should be 3-5%)
Last saturation event was 0 days 14 hours and 12 minutes ago (should be days/weeks)

Possible Issues:
ISS diffracted power is Low
 

I've looked at two images of the IO beam dump steering mirror from Oct 2012 and Nov 2016.  Comparing the two images suggests the beam may have moved enough to be clipping on the edge of the steering mirror, which would cause significant scattering.  The image from Nov 2016 does not show the entire steering mirror, so there is some non-trivial potential for error in identifying the location of the beam on the mirror.  My estimate for that error is around 25%, so if the beam is 25% closer to location of Oct 2012 the risk of clipping is small, but if the beam is 25% farther away from the location of Oct 2012, the risk of clipping is high.  Attached: image of beam dump and sterring mirror from Nov 2016, analysis of images (2.4MB)

Joe is using the machine on the sidewalks East of the OSB. Low freq noise is audible in the control room.

TITLE: 02/06 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 63Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Locked the whole shift, I had nothing to do.
LOG:

• 08:31 Out of Observing to run a2l while LLO is down.
• 08:50 Observing
• 10:52 GRB

Observing at 62Mpc for 9hrs. Range still seems to be going down very slowly, and now a bit more from Hanford traffic. Still not sure of the cause.

Site is a bit slippery, but the rest of the roads seemed good when I came in.

Out at 08:31UTC while LLO is down to run a2l.

TITLE: 02/06 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 65Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 7mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.30 μm/s
QUICK SUMMARY: The range seems to be trending down in the last 24hr, you could maybe say that it is from the wind and/or useism but I've been fooled before. 4hr lock so far.

TITLE: 02/06 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: One lock loss. New longest O2 lock stretch of 41:53:43. No major issues relocking. Damped PI modes 26 and 27. Wind has come back down.
LOG:

03:19 UTC TCSY chiller flow is low verbal alarm. MEDM shows it to be around 3.1, which appears normal. Must have been a glitch.
03:47 UTC Lock loss. Verbal alarms crashed.
04:28 UTC Observing. Damped PI modes 26 and 27 beforehand.

04:28 UTC Observing. No major issues relocking. Damped PI modes 26 and 27.

Reacquiring after lock loss at 03:47 UTC. Cause not clear.

TITLE: 02/06 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 69Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 15mph Gusts, 14mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.41 μm/s 
QUICK SUMMARY:

No issues to report.

All is well in H1 land. There was one GRB alert. The lock is just past 34 hours. It has started snowing lightly. 

Event time: 18:07:12

Verbal Alert Time: 18:08:02

Tom Evans at LLO contacted me via TeamSpeak to verify the alarm was recieved by me as well.

After a dazzingly confusing narrative of what to do with the INJ_TRANS Guardian node in aLogs and E-mails, I selected to manually take the node to INJECT_KILL. I shall return the state to INJECT_SUCCESS after the requisite 1hr stand-down time. After speaking to Keita he assured me that this is ok to do and it won't harm or change anything but It is no longer neccesary to do manually. I spoke with Tom at LLO and he told me that they are still doind the manual Injections pause as well. I infer that they don't utilize the same method for handling this type of event that we do? I hope it isn't just me that is confused about this and why it isn't being handled identically by the entire project.