TITLE: 01/03 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: Jeff
CURRENT ENVIRONMENT:
    SEI_CONF state: EARTH_QUAKE
    Wind: 20mph Gusts, 15mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.37 μm/s
QUICK SUMMARY: locked in Observe, SEI in EQ, wind, tumbleweed work on the X arm

   At the half way point in this Owl shift there is nothing unusual to report. The wind has piped up a bit with a couple of gusts in the mid 30s. Microseism is ticking up a bit as well.  Range remains up around 118 to 120Mpc.

   All well so far.   

TITLE: 01/03 Eve Shift: 0:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 119Mpc
INCOMING OPERATOR: Jeff B.
SHIFT SUMMARY:

H1's been running optimally with a range just under (or at) 120Mpc!  Thanks for the SQZ temperature adustment Sheila & Daniel!  Oh, and we had one data point hit 123.5+ Mpc!

EX continues to have an Ion Pump red box on the VAC overview; this is known and will be addressed when we have access to EX.

L1 Note:  They officially have the longest lock of O3 (136+ hrs!); previous record was 133hrs by Virgo in May '19.  If they make it through the end of Jeff B's graveyard they'll break 144hrs & beat Virgo's #LIGOVirgo record of 143hrs waaaay back in 2009!  Keep on rockin'!

LOG:

• 0:01 H1 to OBSERVING
• 0:19 Optics lab work complete (Vlad)
• 1:04 MY work complete (Kyle)
• 3:00 EQ alert (while I was making lunch).  This was a small one up in AK/Canada, and no action taken.

There is roughly 1-lane access 3km down the X-arm from the Corner Station (but still exercise caution because that lane already had tumbleweeds creeping back to reclaim what was theirs!).

Since the sun sets fast around 4pm, wanted to snap a few photos of the arms for historical purposes, so I used our Building Cameras (and since I don't know how to get those images off the computer, I snapped photos with my phone).  Here's (attached) how we look for:

1. Corner Station to MX (and EX in distance)
2. MX to EX (note the tumbleweed chipper around the midpoint)
3. Looking back from EX to MX

Many Thanks to Chris & Tyler for tacking this #tumblegeddon on site!!

Smooth sailing for H1  being locked 4+hrs and a range around 119Mpc (and a couple data points above 122Mpc!).  

TITLE: 01/03 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: Corey
SHIFT SUMMARY: locked most of the shift, CR covered by me, Camilla, and Jim
LOG:

• 02-01-20 18:04 UTC Kyle to Y-mid
• 02-01-20 18:27 UTC Niko and Vlad to optics lab
• 02-01-20 18:54 SEICONF to EQ - M5.6 from Japan
• 02-01-20 19:13 Niko out of optics lab
• 02-01-20 19:15 SEICONF to WINDY
• 02-01-20 20:00 Kyle back from Mid-Y
• 02-01-20 21:00 Tyler and crew heading back to X arm to handle tumbleweeds
• 02-01-20 21:43 currently about 2 doors from the Mid-Station, and about 8 doors until the X End-Station, and he will call when 2 doors from the X end building to see if H1 can see any increased noise, before getting closer to the X end building
• 02-01-20 22:45 crew on X arm tumbleweed cleanup is done for the day, will continue on the X arm tomorrow
• 02-01-20 22:47 all tumbleweed crews done for today
  • X arm, between Mid-X and End-X is heavily covered in tumbleweeds, so not accessable, and crew will continue there tomorrow

Attached are the TRAMP changes I accepted in SDF yesterday.  Before accepting these, I ran a matlab script to look for the values 7 days prior and 14 days prior, and when those agreed with the current values, I then accepted them in SDF.   These include TRAMP SEI values for ITMX, ITMY, BS, HAM1, HAM2, HAM3, HAM4, HAM5, and HAM6.   Attached screenshots show most, but not all SEI HEPI and ISI TRAMP values that were restored. The overall list is:

• ITMX/Y BSC ISI ST1/ST2 DAMP
• ITMX/Y BSC ISI ST1/ST2 ISO
• HAM ISI DAMP
• HAM ISI ISO
• ITMX/Y BSC HPI IPS
• ITMX/Y BSC HPI ISO
• HAM HPI IPS
• HAM HPI ISO

These are a result of an unusual event, at an inopertune time, and now, experienced gained.

TITLE: 01/03 EVE Shift: 0:00-08:00 UTC (16:00-0:00 PST), all times posted in UTC
STATE of H1: Observing at 118Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 3mph Gusts, 1mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.54 μm/s

Microseism around the 90th percentile & raining out with low winds.
QUICK SUMMARY:

• Walked in to seeing H1 almost at NLN as Sheila & Keita were performing some final measurements.  Shortly after Cheryl/Camilla took H1 to OBSERVING.
• H1's range has been above 120Mpc a few times (just hit 120.95!)!  (Sheila said this is due to the OPO Crystal Temperature adjustment, alog.)
• On the tumbleweed front, Chris/Tyler made the heroic effort of getting a single-lane to the ~3km point of the Xarm from the corner (currently no access to EX on our main road yet).
• Speaking of EX there is an Ion Pump issue there, but we'll have to wait until x-arm access is restored.

Camilla was having a few locklosses at TURN_ON_BS_STAGE2, so she asked me to check. The only issue that I found was that the ST1-2 sensor correction was on, which I had changed the SEI_CONF nominal state to have off a couple of months ago, as part of this alog, where I also made some tweaks to the ISO filters. This probably got turned on by accident with the cornerstation crash a couple days ago, and for some reason wasn't recovered properly. This was probably caused by a the gains for the sensor correction being set on in the safe.snap. Because this is controlled by a guardian, it isn't monitored in SDF, and the guardians don't raise an alert. I've fixed the safe.snap to have the senscor off, so this shouldn't happen in the future, but several issues with the seismic configuration have come up over the last several days because there isn't a clear procedure for making sure these systems are fully recovered after ISI restarts. This control path is kind of obscure, so wouldn't be easy to find.

The attached plot shows the BS ST2 drives, BS guardian state number and POPAIR from the end of the last lock (with the st1-2 senscor on) until now (with this senscor off). The blue and orange are the ISI ST2 drives and the drives are definitely larger with the sensor correction on, which is probably fine for steady state, but seems to be a problem for trying to turn the loops on with MICH locked. Probably we could turn this sensor correction on after the loops were on and settled, but getting all of the necesary guardians wrangled would be complicated, and the difference probably isn't worth it.

I've talked to Niko about adding a flag to the lock loss page for lock losses that coincide with this ISC_LOCK state, and SEI_BS being in transition. Should help us track these kinds of locklosses over time.

Sheila, Jeff K, Cheryl, Camilla 

After our most recent lockloss, we watched the increase flashes states in both arms.  The first time it ran it did manage to improve the arm flashes, so the arms would lock afterwards, but the alignment wasn't good enough for the WFS.  I increased the threshold for sucsess from 0.85 for the Y arm and 0.8 for the X arm to 0.9 for both arms.  

We tried this once and it worked.  If increase flashes doesn't meet the threshold, it will set the offsets to the best postiion that it finds, so I don't think there should be a drawback to increasing the thresholds except that it may take longer. 

The annulus ion pump (a.k.a. AIP) went offline high a little while ago -> Though bailing has been ongoing on the X-arm since 0700 hrs. local time this morning, access to the EX is still blocked.  As the IFO is out of lock at this time, we would otherwise have replaced the controller for this AIP but, as is, will have to wait. 

Over New Year's we had to reduce the trigger threshold on POP for SRY to get the cavity locked.  (54210 and 54208)  In October Jenne had changed these triggers to avoid a problem where the trigger was on continuously (and the suspension was driven) although the cavity was unlocked,  5283.  When Corey was manually aligning the SRM, after having the run the servo that points SR2 to AS_C, he couldn't make the flashes large enough for a 0.5 trigger.  As a compromise I have for now left the off threshold at 0.3 and set the on threshold to be 0.4, we will see how this goes.  ALIGN_IFO needs to be reloaded for this change to happen.  

I also made the changes to the power up described in 54219.  For the last few months we have engaged ASC, turned on the soft loops and ADS with the A2L gains set to cetner the beam on the optics, then servoed TMS and moved the A2L gains to their high power values (MOVE spots),  transitioned to DC readout, then powered up to 20W input power.  Now I have changed the guardian so that we servo TMS when we engage the soft loops at the centered position, then go to DC readout and power up to 10W, then move the spots and run the TMS servo again before we power up to 20W and proceed as usual.  

To do this I also did some cleaning up of the way we were doing convergence checking in ENGAGE_SOFT_LOOPS, and did a lot of renumbering states after DC readout because there were not enough numbers free to make these changes.  I have not reloaded these changes but would like to soon.  

Edit:  We have now relocked with these changes, fixed a few typos but there were no real problems.

All spectra look good.

The initial degradation seems to have slowed down. Initially we needed 5.3mW at launch, but within the first 4 days this increased to ~7.5mW. Currently we need ~8.5mW of green pump light to mainatain the OPO intra-cavity power.

TITLE: 01/02 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: Ed
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 11mph Gusts, 9mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.59 μm/s
QUICK SUMMARY: locked in Observe