nutsinee.kijbunchoo@LIGO.ORG - posted 00:35, Thursday 09 March 2017 - last comment - 10:14, Thursday 09 March 2017(34690)
Ops Owl Shift Transition
TITLE: 03/09 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 61Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT: Wind: 5mph Gusts, 4mph 5min avg Primary useism: 0.01 μm/s Secondary useism: 0.18 μm/s
QUICK SUMMARY: Spotted a bunch of EY CDS overview went red. The status reverted before I can identify which column it was complaining.
I attached a plot of H1IOPSUSEY status over the past 30 mins. I saw two columns went red on this one. The number read 6 and 512.
Note to operators: remember that h1susex and h1susey are running the newer, faster computers to keep processing time to within the 60uS limit. This system has a feature, occassionally the IOP runs long for a single cycle resulting in a latched TIM, ADC error on the IOP, and sometimes an IPC error which propagates to the SUS models, SEI models and ISC models at the end station. A cronjob running every minute at the zero second mark clears these latched errors.
As an example of the frequency of these glitches, over the past 7 days, EX has glitched 61 times and EY 38 times (once every 2 and 4 hours respectively).
We should only report problems if the error bits are not being cleared after a minute has elapsed.