I was prepping to run the H1 Calibration Sensor Measurements, and sure enough, received an EQ alert (5.8 or 6.4 off Chilean coast) minutes before I was going to begin the measurements!  Saw shaking effects on IMC & other signals, so went to EARTHQUAKE state fairly fast, but still we dropped out of lock surprisingly fast before the seismic peaks approached.  (L1 & Virgo are still UP).

For the last lock, noticed glitches on H1 around 25Hz beginning to pick up over the last few hours (paralleling increase in microseism over the same time span).  So I have taken the new SEI_DIFF node to DOWN.

TITLE: 12/25 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Niko
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 3mph Gusts, 1mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.51 μm/s

Microseism is at a high-ish level, but not seeing tons of glitches on DARM's "microseism shelf" (which are glitches hovering around 15-30Hz).  Will continue to watch DARM to see if we want to take SEI_DIFF to the DOWN state (Jenne was swaying away from us needing to go DOWN if microseism BLRMS is above 0.04um/s (which we're currently at).
QUICK SUMMARY:

H1's been locked for almost 8hrs on this Christmas holiday.  Our range is a little lower than we were at a few days ago, but the Earth's been a rumblin'.

And on this holiday, looks like Richard has set up the Access System to keep all of our exterior doors buttoned up (I even tried swiping in to multiple doors after 8am & they remained locked after entering (but one should continue to check the doors via the Access System for one's own piece of mind.)

TITLE: 12/25 Owl Shift 08:00 – 16:00 (00:00-08:00), all times posted in UTC

STATE of H1: Observing

INCOMING OPERATOR: Corey

SHIFT SUMMARY: Uneventful shift once lock was reacquired. Locked and Observing for 7.5 hours.

LOG:

08:37 (00:37) At NLN, accepting SDF diffs to go to Observing

    Laser Status:
    Front End Power is 32.31W (should be around 30 W)
    70W Output Power is 69.36W
    Front End Watch is GREEN
    70W Watch is GREEN

    PMC:
    It has been locked 7 days, 17 hr 24 minutes (should be days/weeks)
    Reflected power = 11.59Watts
    Transmitted power = 51.95Watts
    PowerSum = 63.55Watts.

    FSS:
    It has been locked for 0 days 5 hr and 52 min (should be days/weeks)
    TPD[V] = 5.517V (min 0.9V)

    ISS:
    The diffracted power is around 2.5%
    Last saturation event was 0 days 5 hours and 52 minutes ago (should be days/weeks)

    Possible Issues:

At Cheryl's request, I've plotted the alignment of IM 1-3 OSEMs and IM4 transmission to look for alignment changes after our 6.3 EQ near Vancouver. The first plot shows the ISC_LOCK state, and the timespan covers two locklosses, the first being due to maintenance and the second due to the EQ. There are two vertical lines denoting spots where the IFO is unlocked but the optics should be damped.

It seems there were some large shifts in the IM alignment values, which may have contributed to our noisy re-locking process and our slightly decreased range (though microseism is also up a bit).

Accepting the following sdf diffs to go into Observing. SUS_ETMY test points have been changed, and the BS, ITMY, ITMX, ETMX, and ETMY ISI's have had their ST1_L4CINF F4 gains turned on.

Ops Shift Transition: 12/25/2019, Owl Shift 08:00–16:00 (00:00-08: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: Jeff

Quick Summary: Continuing Jeff’s re-locking attempts after 6.3 mag EQ near Vancouver. Currently sitting at a noisy ENGAGE_ASC_FOR_FULL_IFO.

   Lost lock due to a mag 6.2 earthquake near Port Hardy, CA. There was no warning from any of the EQ systems until after the quake hit. All ISI and several HEPI platforms tripped. Primary microseism is off the top of the chart. 

  Will try resetting the platforms, but do not hold out much hope for relocking anytime soon.    

TITLE: 12/24 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:

Today was a light Maintenance Day.  Had lockloss just before noon, but back to NLN in under 3hrs.

SEI_DIFF:  Instead of looking at seismic levels over 0.4um/s, Jenne said to take this node to DOWN if we see glitches on DARM spectrum (generally we get increased glitches due to useism in the 15-30Hz neighborhood.  See Jenne's alogs for specifics.
LOG:

• 15:45-15:58 PEM Injection (Out of Observing)
• 15:58 On Maintenance Day Light, went back to OBSERVING!
• 16:48 Desert Green observed entering via Gate camera.  Driving down X-arm & Y-arm (16:50-17:20).
• 16:51 EQ Alert:  6.0 Argentina w/ it square in the "earthquake" regime for us (R-wave arrival est was 17:31)
  • Surprisingly, ended up not seeing much from this EQ (maybe a small bump on the EQ band).
• 16:52-18:38 Turbo pump measurements at MY & EY (Gerardo, Kyle)
  • 17:07-17:35 MY entry
  • 17:41-18:35 EY entry
• 17:35 SEI_CONF transitioned to WINDY_NO_BRSY  (Ops NOTE:  This did not bump us out of OBSERVING.)
  • Happened to notice more glitches starting around this time on DMT Omega (see attached snapshot); tagging DetChar.
  • 18:38 SEI_CONF transitioned back to WINDY
• 17:40-17:44 OSB Optics Lab work (Travis)
• 17:41 Out of Observing; Observatory Mode:  PREVENTATIVE MAINTENANCE (for EY VEA incursion).  NOTE:  Managed about 102min of OBSERVING this morning up to this point!
• 18:18 SEI_DIFF transitioned to CORNER_DIFF_CPS (Jenne)
  • 18:47 transitioned back to FULL_DIFF_CPS (Jenne)
• 18:22 LN2 Norco truck arrives for CP6 at MX---Correction:  Swore he told me tank #79, but he went to CP2 (#76) at the corner (remained locked as they drove around corner station, but caused a big glitch/drop in BNS range)
• 19:10 EQ Alert:  5.9 Colombia.  It's in "earthquake" regime, so will monitor (R-wave arrival est. is around 19:34)
  • 19:22 Transitioned to EARTHQUAKE (since IMC signals bumped up a little)
• 19:26 Unifirst swipes through gate
• 19:19 Another (!) EQ Alert:  5.7 Colombia. 
• 19:43 VAC checks on the floor in the LVEA (Gerardo, Kyle)
• 19:48(11:48am) LOCKLOSS (after 18.5hrs of lock):  Either caused by VAC LVEA incursion or EQ (but the largest seismic signals had passed several minutes before the lockloss).
• 19:56 LVEA transitioned to HAZARD (Cherl)
• 19:56-22:03 IO Camera adjustment (Cheryl)
• 20:40-21:26 Initial Alignment (Had a look at PRMI, even with CHECK MICH FRINGES check, and PRMI was very misaligned)
  • MICH BRIGHT went to DOWN 6+ times
    • Contacted Jenne for help!
    • Heard mention of changes related to recent INCREASE FLASHES work (and ETM alignment settings)
  • SRC required a few cycles
• 21:14 ISCLOCK reloaded (Cheryl, Rahul)
• 21:27 Relocking Begins Post-Alignment-from-Maintenance
  • 21:42-22:02 Paused at OFFLOAD DRMI for IO Camera adjustment
• 22:03 LVEA Transitioned back to laser SAFE (Cheryl)
• 22:15 In all the hub bub (lockloss at end of Maintenance, locking, alignment, IO camera work & locking again) I forgot to transition SEI_CONF back.
  • SEI_CONF transitioned back to WINDY (this was during the MOVE SPOTS - INCREASE POWER steps of ISC_LOCK).
• 22:28 Back to NLN
• 22:32 Back to OBSERVING!

I transitioned the LVEA to Laser Hazard after lockloss, and when H1 was relocked and in OFFLOAD_DRMI_ASC, I refocused the HAM2 East door analog camera, with Corey's help in the CR, and transitioned the LVEA back to Laser Safe.  The current lens on the camera has exactly the right field of view, but a very tight focus, and there was very little light to work with at 2W, so the result is that focus moved away from the aperture of the AOE2, which is the aperture I wish to have in focus.   Next Maintenance that where it's possible to have Laser Hazard, I'll swap the lens.

Relocking was paused in OFFLOAD_DRMI_ASC for a total of 25 minutes, which was camera time and time to transition the LVEA back to Laser Safe.

ITMX violin mode 8 damping at relock at the new game of -20 and was successful, and reduced the mode 8 peak faster than -4, without ringing up mode 7 which is nearby.   Plots of relocking at gain = -20 and gain = -4 are attached, both show about 40 minutes, and show ISC_LOCK guardian lock state.

Almost made it all the way through Maintenance with a locked H1, but had a lockloss 12min before noon!  We had literally just made it through the peak of an Earthquake, and at that time Kyle & Gerardo were gently walking around the LVEA, BUT....Keita made a point about the still-rumbling earth post-earthquakes + people walking around in the LVEA + a nearby LN2 truck all cumatively added up to be to much for H1 to handle (& ended our 18.5hr lock).  In hindsight, I probably should have waived off the LVEA incursion until after the earth calmed down from the post-EQ noise (i.e. delaying incursion about 45-60min, or until a later opportunity).  Oh well, that's on me.

• Since we went DOWN, Cheryl transitioned LVEA to HAZARD to do IO camera work at HAM2 which Keita OK-ed (if H1 lost lock). 
• For relocking, DRMI/PRMI were badly misaligned (even after optimizing BS pointing at CHECK MICH FRINGES), so went through an Initial Alignment (haven't run one of these in soooo long!).
• And in 1st lock after the alignment, H1 made it to NOMINAL LOW NOISE.  (The only SDF diffs were probably related to INCREASE FLASHES work....screenshot of diffs are in subcomment to Jenne's alog.)

For this Maintenance Day Light:  Although it wasn't locked the whole Maintenance Day, H1 was down from:  19:48 - 22:28utc (only ~2hrs 40min!)

[Corey, Jenne]

Corey was struggling with the MICH_BRIGHT step of initial alignment.  He let me know that the guardian kept looping through that set of states, and that MICH wouldn't lock.

Things in general looked fine (as in, the past things that have been struggles with this state), so I started looking at the MICH error signal.  It didn't look fine, even though the beam was reasonably well centered on the AS_A WFS diode.  There were PDH-looking jumps in the error signal, when we expect a MICH-only error signal to be a nice smooth signal.  That pointed me toward looking at the misalignment of various optics (PRM, SRM, ETMs), at which point I noticed that the OFFSET values for the TEST filter banks on the ETMs were zero rather than the ~10urad we normally have (one of the 4 was 0.5, but that's essentially zero for the purposes of intentional misalignment).  I realized afterward that this is why we were seeing IR flashes in the arm cavities according to the front wall TV - we shouldn't see those during MICH-only time, so we'll try to remember that that is a clue as to what is wrong.

These OFFSET values are also used by the new INCREASE_POWER INCREASE_FLASHES states that are helping to get the green arms locked when the optics are quite misaligned (this new state is probably related to why we haven't had to do very many initial alignments lately, which is awesome!).  Perhaps these OFFSET values weren't reverted after the testing work done yesterday with this state or they were left over from some other work or losing lock part way through the new state, so when the ALIGN_IFO guardian tried to misalign the ETMs it correctly turned on the OFFSET, but nothing really happened since the offsets were zero.

I reverted the values via SDF (SDF knew that the values were wrong, but it's hard to know which things that SDF says are differences are the things that are actually causing the problem...), and the initial alignment continued forward as normal.

Since this (incorrect offset values) is something that has caused us trouble a few times lately, TJ has been in contact with StuartA at LLO about modifying the suspension guardian to ensure that the offset values are set correctly every time we request the misaligned state.  We had decided to push this modification to January, but this is a good reminder that we should pick it up soon after the holidays, just in case this happens again.

EDIT: Corrected state name - thank you Corey!

Jim suggested this a while ago, and it looks like he and TJ prepared a guardian state for it, but I've just set the nominal for the SEI_DIFF guardian to be CORNER_CPS_DIFF.  This state has all of the vertex CPS DIFF turned on (HAM2-HAM3, HAM4-HAM5, and ITMX-BS-ITMY), but no CPS diff down the long arms. 

The microseism isn't quite high enough right now to see lots of low frequency glitches when the system is on including the arms, so I don't have a good on/off plot to show.  The microseism is increasing though, so hopefully we'll see throughout the day that the low frequency glitches don't increase.

Offline, we'll continue trying to understand how we can use the CPS diff up at higher frequencies to cover the microseism, as well as how we can have it on the arms without causing extra noise.

H1 was in OBSERVING for about 40min this afternoon (until a smaller aftershock knocked us out yet again!).  But when we were at NLN, had a couple of SDF Diffs (see attached for channels) for: 

1. ISI ITMx TRamp (chose to NOT MONITOR)
2. SEI PROC (ISI_DIFF was in ON state.  This basically means we have the new CPS Diff in the ON state (I phoned Jim and he walked me through this new system).  He suggested we NOT MONITOR this channel, but I think in a rush to get back to OBSERVING, I ACCEPTED instead.)

Note On CPS Diff

This had been OFF, but for some reason it was ON for my most recent lock.  I called Jim and so he could help me out---this is a new system from Jenne, Chiari, & Jim.  I mentioned that with all the EQs, I had tried to transition the SEI_CONF to EARTHQUAKE & Large EARTHQUAKE a few times.  Thinking possibly this is how CPS Diff was turned ON, but that's a guess on my part.  Anyway, it was ON according to SDF & Jim explained it to me.

For better performance in the wind/earthquake bands, we run with CPS DIFF--->  ON (see alog).  Jim suggested to leave CPS Diff ON.  It is good to leave ON as long as the microseism is below 0.4um/s (we are currently at about 0.15um/s).  

If microseism gets above 0.4um/s (and it looks like we are getting glitches in DARM), then we should transition CPS Diff to OFF.  Jim suggested one can do this by going to the SEI_DIFF Guardian Node and taking it from FULL_DIFF_CPS state to the DOWN state.  Alternatively, one can also turn the CPS Diff bit to the OFF state on the Output Limiters medm.  The attached screenshot shows ISI_CONFIG, the SEI_DIFF guardian node, and the LSC Output Limiters medm  (the ways to turn CPS Diff OFF are circled in green & have arrow pointing to them.).