TITLE: 11/18 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 6mph Gusts, 4mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.35 μm/s
QUICK SUMMARY: locked 33+ hourrs
TITLE: 11/17 Eve Shift 00:00 – 08:00 (16:00-00:00), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Quiet shift, small EQ in the first hour. Locked and Observing ~33.5 hours.
LOG:
00:36 (16:36) Going to EQ seismic configuration for 5.6 magnitude EQ in Guam
00:46 (16:46) Back to WINDY seismic configuration
Looks like ITMX Pitch and ITMY yaw are both on/close to the 10 urad line
Noticed an increase in 10-20 Hz noise between two glitches. The first glitch didn't elicit any Alarm Handler notifications, the second had an EX saturation.
Ops Shift Transition: 11/17/2019, Eve Shift 00:00–08:00 (16:00-00:00) - UTC (PT)
State of H1: Locked
Intent Bit: Observing
Weather: 0-5 mph wind
Primary 0.03 – 0.1Hz: 0.01 um/s
Secondary 0.1 – 0.3Hz: 0.4 um/s
Outgoing Operator: Camilla
Quick Summary: Locked and Observing for ~26 hours.
TITLE: 11/18 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 113Mpc
INCOMING OPERATOR: Niko
SHIFT SUMMARY: Quiet shift with 10 minutes of Commissioning at the end due to SQZ
LOG:
FAMIS 12874. Posted below are the plots from the weekly ISI CPS noise spectra. No reported elevated noise. The plots look OK.
I noticed when we had a drop in range at 19:49UTC that the BRSX_STAT was in DAMPER_ON and taking itself back to READY. It seems that the wind fence work has been effecting both the BRS's. See plot from last 5 days of BRS states (40=nominal state READY; 30=DAMPER_ON) alongside movement at EX and EY. It's intersting that BRSX kept going on and off Friday evening when there wasn't anything obvious happening.
These shots are from Friday during the concrete delivery.
1) Concrete trucks filling the hopper of the pump truck
2) The pump truck reaching to the far end of the EndX line
3) Filling the Line End guy tie blocks
4) Checking the Pole plumb before
5) Filling the collar forms
Wire stringing continues today.
TITLE: 11/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 109Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.35 μm/s
QUICK SUMMARY: Have been locked for 17h40. Wind fence crew may be on site later to finish putting up wires.
TITLE: 11/17 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 111Mpc
INCOMING OPERATOR: Camilla
SHIFT SUMMARY: Quiet shift
LOG:
Not much happened this time around.
TITLE: 11/16 Eve Shift 00:00 – 08:00 (16:00-00:00), all times posted in UTC
STATE of H1: Observing
INCOMING OPERATOR: Jim
SHIFT SUMMARY: Quiet shift. Locked and Observing 9.5 hours
LOG:
00:03 (16:03) Wind fence crew leaving site
Lots I probably don't kow about but a little less than half the wire is up. Given the preliminaries, maybe they'll get all that up tomorrow... A photo attached.
Ops Shift Transition: 11/16/2019, Eve Shift 00:00–08:00 (16:00-00:00) - UTC (PT)
State of H1: Locked
Intent Bit: Observing
Weather: 0-5 mph wind
Primary 0.03 – 0.1Hz: 0.01 um/s
Secondary 0.1 – 0.3Hz: 0.4 um/s
Outgoing Operator: Camilla
Quick Summary: Locked and Observing for just under two hours. Wind fence crew starting to leave the site.
TITLE: 11/17 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 105Mpc
INCOMING OPERATOR: Niko
SHIFT SUMMARY: Work still continuing at the wind fence, mainly EY, where wires are being strung up between posts
LOG:
One of Camilla's locklosses in this recovery (from Low noise ASC) looks pretty similar to one that's we've been having frequently where there is a sudden burst of high frequency noise in DHARD that saturates many supensions. This one is interesting because there are several ADC saturatoins at the time of the DHARD problem, as the lockloss website shows: 1257975934. There seems to be something wrong with the subplots that would help us narrow down which channel was saturating though.
It also looks like inthe seconds before that lockloss we are having the problem with the PSL rotation stage where it jumps back, see 53068
Camilla, Sheila (remotely)
Still trying to get locked after Niko left, but being stopped by some weird issues. First was an OM1 trip at during I think DRMI asc offload, IFO stayed locked for a bit while I tried to figure out where to clear histories because all of the OMs were railed.
After that, I couldn't move past DRMI at all. The buildups were gradually degrading through several attempts to get DRMI, and each time ISC_LOCK would get stuck after DRMI or PRMI initial acquisition, then refuse to move on simply reporting "IMC_LOCK has notification". When I looked at IMC_LOCK, it didn't seem to have any such notification.
After multiple rounds of that, I'm trying to run initial alignment, but that is starting to look equally fruitless. The input alignment state seems to be hanging, saying ALIGN_IFO has notification. But ALIGN_IFO seems to be waiting for the input to a DC YAW loop to come on. This has continued through a number of steps in initial alignment, and the only way I've been able to move on is by manually selecting the the next offload state. This is probably all wrong.
Initial alignment is "done", so back to locking. With an incoming earthquake. Oy.
ISC_LOCK continues to move on from DRMI acquisition. The only clue I have are some alogs ending with Jeff's comment here, some related alogs it points to and FRS 5109. It's called alternately a red herring and occasional issue, but other than some wfs system that doesn't seem to be implemented, I don't see a solution. Seems like the IMC WFS need to be better centered, but I can't figure out how. Can't proceed past DRMI and can't seem to find a solution.
The IMC WFS message is a red herring, the gaurdian is just giving that as a warning occasionally that we are off center, but it doesn't wait for the IMC WFS. It looks like in a couple of the cases, ISC_LOCK was waiting in ACQUIRE_DRMI_1F for the DRMI guardian, ISC_DRMI was stuck in the DC centering state. This is trying to center the AS + REFL WFS before turning on the DRMI ASC, which it couldn't do because the outputs of those filters were off. With those off center the DRMI ASC won't work, which would cause locklosses if we moved on to DRMI_ASC. So the guardian was doing the right thing, the problem was that the outputs were off.
