Cause unknown. Seemed to be fast, no signs of a struggle or anything ringing up.
TITLE: 11/10 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 112Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.38 μm/s
QUICK SUMMARY: useism is creeping back up, but other than that it is calm and steady with a 6hr lock.
TITLE: 11/10 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Calibration Pipeline was restarted by Aaron at beginning of shift. So operators no longer have to be mindful of this.
LOG:
H1's been in OBSERVING for about 1.75hrs. Calibration Pipeline was restarted at beginning of the shift, and we just rode through an EQ from Japan region.
There is a Timing Error light for Port 8 of Corner A. I clicked on the "red 8", thinking a window would open up giving me more info, but this caused an SDF change, so from 12:05:56 - 12:06:05 we were out of OBSERVING. Sorry!
Reminder that the top button sets whether the port should be active or not, the bottom widget opens the related display, the row descriptions are shown on the left.
Unitil the 35.5MHz unit is replaced, this system is still going into error states now and then.
Summary: Manual Intervention for: 1st two locks (i.e. Green Arms for Lock #2), and Initial Alignment after Lock #4.
Somewhat similar to last night, H1 had a lockloss close to the shift change at midnight! With the 6 Locks, & an Initial Alignment, it took just about 3hrs to get H1 back up to OBSERVING, following the new Operator Intervention protocl (DCC#T1900725).
Notes On Operator Intervention & Locking:
[C. Gray, A. Viets]
The primary and redundant calibration pipelines were restarted around GPS time 1257408393. The purpose of the restart was to reduce the latency, which had climbed up to 15-20 seconds in the past several days. In the mean time, the latency now looks normal, around 3 seconds. The cause of the original problem is still uncertain.
TITLE: 11/10 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: mostly in Observe, two lock losses, for the second lockloss I handed off to Corey with both arms locked in green
LOG:
TITLE: 11/10 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 3mph Gusts, 2mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.27 μm/s
useism reached a low about 12hrs ago, but has been slightyly increasing since. Winds are nonexistent.
QUICK SUMMARY:
Once again, H1 is down close to the shift change time! Cheryl is handing off to me. We just contacted Aaron/Maddy regarding restarting calibration pipeline.
Lockloss as the last tour was in the CR, relocking took 96 minutes, range is 119Mpc.
Chandra and guest took advantage of this lock loss and entered the LVEA for about 10 minutes. We entered by PSL area and exited through LEAA to avoid HAM6/east bay. Then we drove down X arm and entered MX VEA.
TITLE: 11/10 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 5mph Gusts, 4mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.23 μm/s
QUICK SUMMARY: locked 15 hours, in Observe, it's Saturday Tour day, last tour coming through the CR now
TITLE: 11/09 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 119Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Second Saturday tours flowing through this afternoon. 14hour lock with a calm environment. Corning timing is still flickering in error from time to time, as it was on Thursday. H1ASC has a CFC warning as well.
11 hour lock. There was a brief dip in the range recently but it seems to have recovered. We also had a M4.1 earthquake from British Colombia roll through earlier without an issue. We even got a Seismon warning just about the same time it arrived. This is impressive considering how close it was.
Sheila, Daniel, Nutsinee
Looking at the data taken on Nov 6 with the full interferometer, we have less than 2dB of squeezing (at high freq) with an inferred phase noise of 200 mrad.
I didn't write down the OPO transmission, but looking at the reflection (~input power) to the OPO the nonlinear gain produced continues to degrade. Lee was suggesting that if we plot nlg in terms of green transsmitted power we could determine if the escape efficiency is degrading as well. Those number would required some digging.
The error bar here derived from the (+-) differences nlg measured using the IR PD MON channel vs. fast channel Sheila put on the ndscope. The past measurements have been done with the IR PD channel.
Could bad phase noise be due to CLF? Homodyne says so. In the past I've made a high CLF sqz/asqz measurement with the Homodyne but we thought that worsen squeezing was due to homodyne saturation. Seeing that asqz was not effected that doesn't seem to be the case.
If we were to compared the orange and the purple data at their highest and lowest error bar, the phase noise is about a factor of 1.5 different. 120uW CLF refl was used for the high power measurement and 40uW refl was used for the low CLF power measurement. The phase noise difference between the two is expected to be sqrt ratio of the sideband power, sqrt(120/40) = 1.5.
For the IFO, we have 25mW hitting the OMC PDs (correct me here if I'm wrong). 5uW CLF transmission at 120uW input, a factor of 100 attenuation by the OMC at 3MHz, we have ~1/sqrt(2500/(5/100)) = 4mrad expected.
To check if the source of this 200 mrad phase noise in the interferometer actually comes from CLF (or to see if it is at least partially responsible), one probably should take another set of sqz/asqz measurement now that we have lowered the CLF power input to the IFO by a factor of 2 (alog53107). If CLF was some how responsible, we should see about a factor of sqrt(2) decrease in the inferred phase noise.
TITLE: 11/09 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
A few earthquakes rumbled through, but we made it through them OK. H1's range is looking decent as it is just under 120Mpc...it's been a bit glitchy the last 5hrs though.
Operator Note: Calibration Pipeline still needs to be restarted (I"m assuming when H1 is not locked....Aaron & Maddy were sleeping during the lockloss during my shift).
LOG:
TITLE: 11/09 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 116Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 3mph Gusts, 1mph 5min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.26 μm/s
QUICK SUMMARY: 6.5 hour lock, useism is elevated.
Been locked close to the last 2.5hrs. Have received some recent EQ notifications. Recently switched to EARTHQUAKE, and waiting to see if it gets any worse for wear. It's close to lunch time, so I might leave it in this state for a while, but will keep watching tidal, ASC, & LSC signals to see if I should first switch back to WINDY (because I'm not seeing much for this earthquake on the seismometers).
Summary: H1 was out from 7:58 - 9:45. Not totally clear when to Intervene due to repeating locklosses.
A minute before my shift started H1 lost lock. I immediately got set up to lock H1 with our new operator protocol (T1900725) of allowing H1 to lock as much as it can WITHOUT operator intervention. Still think there are some states/steps where we might want to change intervention thresholds.
To Intervene, Or Not Intervene
For example, there were several locklosses in a row which happened in odd states (several in a row while waiting for DRMI to acquire & one during FIND_IR)...I was fearing I was in a loop of locklosses at this point! And so, to prevent waisting time, on the 9th (!) lock, I threatened to run an alignment by opening up all the nodes needed to do that, and (wouldn't ya know it!) H1 then locked all the way up!! Ha!
As for actual intervention, it only happened on the very first lock (tweaking ETMy for y-arm green locking) & after that, I sat on my hands and noted where it dropped out.
H1:LSC-PRCLFF FM4 is OFF
Looks like Guardian is taking us to the standard state of keeping PRCLFF's FM4 OFF, but with tests last night, there was an SDF diff for wanting it ON. I went back to Accepting FM4 OFF. Attached is a screenshot of the SDF diffs I observed and then ACCEPTED to get us back to OBSERVING.
Notes On Operator Intervention & Locking:
I had not put the PRCLFF FM4 into the guardian (I think I'm getting too used to these very long lock stretches that last for many days!), so it makes sense that it wasn't on. With Craig's plots showing that it maybe didn't really help things, and the range is quite good right now, I think leaving it off was the right call.
TITLE: 11/09 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
SEI_CONF state: WINDY
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.32 μm/s
QUICK SUMMARY:
We literally just lost lock 2min before my shift! So working on bringing H1 back (nothing looks crazy btw).
NOTE regarding Calibration Lines: Operators were asked to send an email to Aaron V./Maddy W. whenever H1 drops lock so they can restart Cal lines. Email was sent a few minutes ago.
Lock loss 1257321505
This looks like a very similar situation to the lock loss on Thursday (alog53069). The squeezer lost lock just before we see the LSC-POP_A_LF_OUT signal drop. This time though, the LO servo channel does not go as unstable. Instead, it drastically drops in power.
Attempt 1:
Attempt 2:
Attempt 3:
This fast lock loss seems exactly the same as one of the ones from yesterday (alog53122), which we have seen recently. Again, I'm not sure if the squeezer is actually causing the lock loss, but it is one of the only channels I can find doing anything before the lock loss.