Robert has started his work, should last around 30min.

Edit: title had wrong time

At 1613 UTC I transitioned SEI_CONF to the EARHTQUAKE state for the 6.4mag earthquake in Guam.

TITLE: 06/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: Jeff
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.04 μm/s
QUICK SUMMARY: 9.5 hour lock, calm environment.

   Good first half of the shift. 

   Other than a couple of glitches, it has been smooth sailing. Locked and Observing for past 4.75 hours. Wind and microseism are low. The range is hovering around 118.5Mpc. All green and clear at this time.  

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

Life in ASC land was a little fuzzy/noisy for locking at the beginning and 2nd half of shift.  An alignment appears to have helped get through.  

There was a PRM Diff for its M2 coils which were ACCEPTED.  Will want to watch this for next time we get to NOMINAL_LOW_NOISE.  (see earlier alog)
LOG:

• 23:13 Lockloss at DARM to DC.....preceded by ramp up of PR_GAIN & POP18
• 23:16 MY visit (Kyle)
• 0:08-0:18 Back to OBSERVING.
• ~0:50 utc Range begins to trend down.  38-60Hz band begins to increase & looks like it's our infamous ~48Hz line.  :-/
• 3:14 - 6:15 Down for locking & alignment (see alog)

Two Types of Symptoms For Locking Locklosses During This Shift Before Alignment:

1. PR Gain noisy from CARM_OFFSET_REDUCTION all the way to ENGAGE_ASC_FOR_FULL_IFO (example Attachment #1)
2. Ringing up of PR GAIN & POP18 from ENGAGE_ASC_FOR_FULL_IFO to DARM_TO_DC_READOUT (example Attachment #2)

Something was not happy in ASC land!

LOCKING NOTES:

3:14 Lockloss

• Attempt#1:
  • DRMI didn't lock after 10min so moved to PRMI
  • Got up to CARM_OFFSET_REDUCTION (where it looks like PR Gain was really noisy/ringing up) and then = LOCKLOSS
• Attempt #2:
  • Got up to RESONANCE, but PR gain still looked ugly = LOCKLOSS
• Attempt #3:
  • Hung out at OFFLOAD DRMI ASC a few minutes
  • Got up to PREP_DC_READOUT_TRANSITION and the PR GAIN & POP18 started to ring up like what happened for the lockloss from TJ's lock he handed off == LOCKLOSS
• 4:38 Initial Alignment 
  • INIT_ALIGN took over, but needed me manual tweaks for ALSx alignment
  • This time MICH BRIGHT OFFLOADED worked for me & INIT_ALIGN finished off the alignment on its own.
• 5:10 Attempt #4 (post alignment)
  • After the alignment, PR_GAIN (& POP18) looked much better...they have their noisy spots, but they weren't as bad as those earlier attempts.  
  • 5:54 Made it all the way to NLN!  (w/ no pauses or issues)

New SDF Diff for PRM:  This had to do with Binary IO (BIO) State Request (for Acquire & Low Pass) for PRM.

These were a new set of DIFFS which I had not seen before.  I called Keita first (but I woke him up!), and then talked with Georgia.  She was familiar with the issue.  She mentioned since these were on the M2 stage they are not an issue for us at NOMINAL LOW NOISE since we do not have signals for the M2 coils.  So in the interest of returning to OBSERVING & since this won't affect NLN/Observing, screenshot the channels/diffs, and all windows related to this (See Attachment #3, which shows channels with diffs, and all PRM medm windows involved). 

Will need to trend these channels and/or go through guardian scripts to see what State Request we normally have for PRM, but I'll leave this for others.  Will want to see what happens for the next lock!

6:15 Back to OBSERVING!

3:14 (8:13pm):  Lockloss (did not see anything obvious for the lockloss).  Relocking so far (no alignment yet).

Starting at around 0:50utc, noticed H1 range drop.  Drop looks correlated with DARM's 38-60Hz band.  And sure enough we see the infamous ~48Hz line getting bigger. Will keep monitoring.

Attachement #1:  38-60Hz line

Here you see this band slowly growing during an hour long stretch where we had no glitches. 

Attachement #2:  48Hz line on DARM spectra

Here is a random screenshot when the line was large.  (and also a glimps of the range drop over the last 40min.

H1 DOWN from 22:10 - 0:08utc

For the locking-H1 TJ handed off, there was a lockloss around the DARM_TO_DCREADOUT state.

• Note on Lockloss:  PR_GAIN & POP18 both rung up!  (no idea what the reason was for this).
• However, made it to OBSERVING on next attempt with no issues....I might have lingered on a few steps before ENGAGE_DC_VIOLINS.
  • Touched up alignment for ALSx via ETMx & TMSx
  • Locked PRMI

SDF Diffs While at NLN (see this alog on specifics for these recurring Diffs):

Continue to have the PSL ISS Diff:   ACCEPTED (per Jason)

Continue to have the ASC RF36 Diff:  ACCEPTED (per Keita)

Yesterday I re-ran Craig's SRCL to DARM transfer function and his analysis code which calculates the circulating arm power from the RIN to DARM transfer function. This measurement was done ~10 hours into the lock.

Results: 

Arm QPD      Gain [DARM m/RIN]    Arm Power Inferred [kW]
------------------------------------------------------------------
XA           1.55e-6              183
XB           1.58e-6              188
YA           1.65e-6              195
YB           1.72e-6              204

X arm power = 185 kW
Y arm power = 200 kW

Average arm power = 192.4 +/- 7.9 kW

The fit of arm power RIN to DARM is shown in the attached figure. If we remove the two lowest frequency points we will probably improve the uncertainty on the arm power.

TITLE: 06/27 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    Wind: 19mph Gusts, 14mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

Walked in to TJ locking up H1.  Unfortunately, it dropped out shortly after while moving up ISC_LOCK.  Going to try to lock one more time (& try alignment next).

TITLE: 06/27 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Just lock at the end of my shift, most likely due to a large gust at the CS. Relocking has been easy, ALS dropped lock as few times as the WFS kicked in though.
LOG:

• 1600 GRB notification with latency ~17000 seconds, ignoring.
• 1636 Ken to MY then MX to install emergency lights
• 1647 Bubba filling a nitrogen bottle from tank 375 (next to corner station along y-arm)
• 1701 Niko to Optics Lab
• 1800 Kyle to MY then MX
• 1827 Rick to Optics Lab
• 1829 Ken back
• 1910 Kyle back
• 1915 Niko out
• 2210 Lockloss
• 2220 Robert, Adrian, Matt to LVEA to check on vibrometer
• 2255 Robert and crew out.

The cause is currently unknown. There was a large gust of wind at the corner station, but I haven't had the chance to confirm that was it.

After the storm and ALSx issue, ran an alignment, went for locking & finally back to Observing.

NOTES: 

• 4:29 During locking (of course) there was an incoming earthquake.  Took SEI_CONF to EARTHQUAKE state while waiting for DRMI.
• 4:57 LSC tidal X&Y Errors received via Verbal (could see ETMy Drive Align hitting rails on the Tidal strip tool...see 1st attachment)
• Made it to NLN, but had the same DIFFS we've been having since Tues Maintenance.

Commissioners & Jason:  Should We UNMONITOR these? (see 2nd attachment)

• ASC changes during locking every time (not sure what is different here...did we start monitoring this all of a sudden?
• PSL ISS diff is a 10^-14 difference Jason mentioned we'd get after Maintenance.
• Have been ACCEPTING these since Tuesday

Went to Observing

• 5:51  LSC tidal X&Y Errors received via Verbal again.  Once again ETMy Drive Align was flat-lining at a rail.  This caused the lockloss.  
  • Before lockloss, I was watching Jim's new signals for transitioning SEI_CONF from EARTHQUAKE to WINDY, but they remained in the red the whole time, so I worried we'd lose lock.  We did lose lock before I could transition.  
  • NOTE:  LSC-CPSFF_INMON was showing a large oscillation while in the EARTHQUAKE state.  As soon as I transitioned to WINDY, this signal became small. (see 3rd attachment).

[Georgia, Jenne]

• In prep for the measurement, at around 11:50am local we turned on the ETMY bias with 9 V (a little less than the 9.5 V value that ETMX uses).  There is a lot of low frequency noise added, so we're sat here for ~7 min in case the data is useful, but then we're trying the other sign of the bias.  We don't think that we need lower noise for our measurement (exciting the mode with various ESD patterns on different optics) though, so it should be fine either way. 
  • Keita points out that maybe we should think about grounding the ETMY bias input, since we aren't using it at all for lock acquisition.
• We were working on exciting the mode (not succesful yet), but lost lock.  I suspect the lockloss is unrelated to our work, since none of the PI modes were any higher than they had been the whole lock, our excitation hadn't changed in a long time, and Robert had said that he was planning to do some laser vibrometer work requiring contact with some HEPI piers.  So, I suspect that the lockloss was a combo of Robert's work and the fact that we're in EQ mode. Robert and crew were still in the H2 part of the LVEA, hadn't gotten near HEPI piers yet.
• Acquisition guardian change: PRMI_ASC_OFFLOADED now turns off the PRMI ASC filter banks that were in use, prior to our trying to acquire DRMI lock. It looked like we were still sending signals out to the optics after we had lost PRMI when the SRM came back into alignment, which probably didn't help DRMI acquisition (although it did catch by itself).
• We are going to excite this time in the damping filter for PI mode 24, since then our RMS monitor won't be directly contaminated by our excitation, and will just monitor the actual peak height.  New channel: H1:SUS-PI_PROC_COMPUTE_MODE24_DAMP_EXC, with a narrow bandpass in the awggui. 
  • Previous channel: H1:SUS-PI_PROC_COMPUTE_MODE24_BP_EXC.
  • Had also tried exciting using the OMC deacon infrastructure, but that's not really what we want to be using for this identification measurement.  We'll re-look at that when we're ready to implement deacon alignment for the OMC.
• To be continued in a comment by Georgia....