TITLE: 04/09 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Locked for 33hrs, one large glitch about 15min ago.
LOG: Nothing to note

Locked for 30hrs, environment is calm and a2l looks good.

TITLE: 04/09 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 7mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY: useism is almost back to its usual level, wind is calm, and we have been locked for 25.5hrs

TITLE: 04/09 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 62Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

Nothing to report. Handing off to TJ
LOG:

CP6 and CP8 deliveries scheduled for Tuesday, April 11th.  My recollection from Friday was that CP6 was in the mid 20's - increased consumption or bad memory?

2:42UTC LLO concurred. Guardian acting normally. 1 hr stand-down time in effect.

TITLE: 04/08 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 59Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 20mph Gusts, 18mph 5min avg
    Primary useism: 0.08 μm/s
    Secondary useism: 0.27 μm/s 
QUICK SUMMARY: No issues. Ran a2l after LLO lost lock.

17:03 UTC LLO lost lock. Going out of observing to run a2l.
17:08 UTC Back to observing.
21:07 - 21:40 UTC Chandra leading tour through control room.

Only out of observing to run a2l after LLO lost lock. No issues to report.

TITLE: 04/08 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 62Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 10mph Gusts, 8mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.42 μm/s 
QUICK SUMMARY:

No issues to report.

TITLE: 04/08 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 64Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: Very quite shift, locked for 9.5hr.
LOG: Nothing to note

5.5hrs at 65Mpc. Wind has calmed down adn useism seems to be on its way down as well.

TITLE: 04/08 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 67Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 23mph Gusts, 20mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.53 μm/s
QUICK SUMMARY: Hour and a half at 67Mpc, wind is still a bit elevated and teh useism is a bit high as well.

TITLE: 04/08 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

See previous aLogs
LOG:

• 4:45UTC Lockloss - winds seem to be picking up again, some in excess of 40MPH.
•  First attempt: after some BS/PRMI aligning, locking failed at DRMI_ON_POP. Some camping at LOCKING_ALS and DRMI _LOCKED was done for ASC purposes.
• 4.7K was elevated again and engaging FM6 in th ETMY Mode10 Filter section did the trick again. I will, again, accept this diff in SDF to resume Observing.
• 5:36UTC Intention Bit - Undisturbed

02:25UTC After about 1hr15min of NLN the a2l measurement showed about .7 out of PIT in X arm. Yaw looked nice and coherent. Livingston operator was informed.

02:30 H1 back to Observing

Ed, Miriam

• 4.7K violin mode rung up to e10^-16 hampering things for a while. Thank you,  Corey, for the aLog and thank you Miriam for finding it for me!

TITLE: 04/08 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Wind
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 28mph Gusts, 24mph 5min avg
    Primary useism: 0.12 μm/s
    Secondary useism: 0.57 μm/s
QUICK SUMMARY:

Re-Locking has been a bit daunting: Bad fiber polarization, SRC acting up, locklosses occurring at CARM_ON_TR. the wind is coming back to more reasonable levels so I may try going back to the nominal WINDY state for the ISI configuration. Stay tuned.

Summary: there seems to be a correlation between computer errors (for instance timing or IPC errors) with one or two types of blip glitches in DARM.

Explanation:

With the help of Dave Barker, in the last days I have been looking at several FEC_{}_STATE_WORD channels to find times of computer errors. First I used the minute trends to go back 90 days, and after that I used the second trends to find the times of the errors with an accuracy of a second (going back two weeks). I have been looking for error codes up to 128, where 2=TIM, 4=ADC, 8=DAC, 16=DAQ, 32=IPC, 64=AWG, and 128=DK. Finally, I generated omega scans of GDS-CALIB_STRAIN for the times of errors and found that they often show glitches.

Since there were some times that did not glitch, we are trying to track down how the coupling between the errors and the glitches is happening to see if it can be fixed or if the times can be vetoed. It might not be possible to fix the issue until we go into commissioning time at the end of O2, so DetChar might want to consider creating a flag for these times.

Investigations:

With the times obtained from the second trends, I have created tables of omega scans to see how the errors propagate and where the glitches appear. All those tables can be found here as html files, and the lists of times of errors for the last ~two weeks as txt files. So far, the model with the highest rate of glitches vs non-glitches is the susetm(x/y)pi.

I have been looking at some of these glitches, and the loudest ones coincide with small range drops. Also, the three glitches that had a strong residual in the subtraction of the MASTER signal from the NOISEMON signal (see aLog 34694) appear in the minute trends as times when there were computing errors (I haven't tracked those times down to the second though) in the h1iopsusey model.