aLIGO LHO Logbook

H1 General

nutsinee.kijbunchoo@LIGO.ORG - posted 08:02, Monday 21 November 2016 - last comment - 21:03, Monday 21 November 2016(31678)

Ops Owl Shift Summary

TITLE: 11/21 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC

STATE of H1: Observing

INCOMING OPERATOR: Jim

SHIFT SUMMARY: One lockloss during the shift. There was a small earthquake in CA showed up on the seismic FOM around the same time (read 0.1 um/s). This amplitude of earthquake doesn't usually break the lock so I wonder if something else might have caused it. Had no issue relocking.

LOG:

9:28 Out of Observe to run a2l

9:36 a2l done. Back to Observe.

09:42 Lockloss

10:16 Arrived at NLN. Took time to damp bounce modes and ran a2l.

10:31 Observe

13:07 Out of Observe to run a2l

13:12 Observe

15:13 Out of Observe, ran a2l

15:18 back to Observe.

Dust alarm and Vacuum alarm (CP4) continues to beep. If your system is using the alarm handler please make sure the threshold is set right and only make it beeps when things are critical. Otherwise operators are just going to keep ignoring these alarms, including the ones that might actually be critical.

Comments related to this report

jeffrey.bartlett@LIGO.ORG - 13:16, Monday 21 November 2016 (31692)

Link

  Checked the alarm level settings for all site dust monitors, and all are set correctly.
  Dust monitor alarms should be investigated and documented in the aLOG. Use some common sense when aLOGing an event, e.g. if you know Karen is cleaning at End-? and the alarm goes off no need to log. All unknown alarms should be logged.