TITLE: 06/25 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 10mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

Steady rollin' for 23:50 hours.

TITLE: 06/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

Much nicer shift tonight with the winds not causing grief as they did my entire shift last night!  Have one EQ incoming, but I'm handing that over to Ed to observe/handle while utilizing Jim's new tool to help us transition to EARTHQUAKE mode without breaking lock.  This one is right on the border of being worrisome.  Virgo has started Maintenance.  
LOG:

• 23:13 Vac Prep Lab had dust alarm
• 23:25 GRB Alert Received
  • 23:27 went to INJECT_KILL
  • 23:34 Completed going thru procedure & determined the Trigger duration was less that 1.024s (it was 0.016 sec).  Talked to Arnaud at LLO on Teamspeak (left a message on chat window for Virgo since I didn't hear from them).
  • Stand down until 23:40
  • 23:40 went to INJECT_SUCCESS, since Stand Down was complete.  (Would be nice to state what state the operator should take this node to "INJECT_SUCCESS".)
• 0:05 - 0:17 Hanford Fire Dept showed up to look at (RAIFAR?) alarms.  Asked them to park (for 5-min) at LSB while I contacted Bubba.  Bubba was not aware of their visit, but said they frequently get alarms, and said they can check alarms in acceptable areas (i.e OSB, Mids, etc.), or wait until Maintenance tomorrow since we are observing.  Talked to them at the gate again and they said the alarm was at the OSB & outside (next to Control Room entrance), so I let them in.
• 3:33 rebooted video0
• 6:22 Verbal for Incoming EQ (5.8 SW of Australia), but it's on the border, and is just under an hour away, so Ed may have to deal with this one.

Smooth running with H1 locked for almost 19.75hrs (last 45 min with no glitches).  Winds are hovering around 10mph.  (I think it's time to make lunch.)

Sheila asked if any of the H1 spectral lines below 100 Hz could be due to motion of HAM6 ISI (see LHO aLOG 50098, and LLO aLOG 46603). It's not enough to ask "are any lines coincident" because they could be just that, coincidence. A better measure is coherence because then one can make a more convincing argument.

I took a recent 17+ hour lock stretch from June 15, 2019, and measured coherence between H1:GDS-CALIB_STRAIN and the channels H1:ISI-HAM6_BLND_GS13X_IN1_DQ, H1:ISI-HAM6_BLND_GS13Y_IN1_DQ, H1:ISI-HAM6_BLND_GS13Z_IN1_DQ, H1:ISI-HAM6_BLND_GS13RX_IN1_DQ, H1:ISI-HAM6_BLND_GS13RY_IN1_DQ, and H1:ISI-HAM6_BLND_GS13RZ_IN1_DQ. The coherence was calculated using GWpy with 1800 s long, 50% overlapping, Hann windowed FFTs. I attach the coherence results below. Long FFTs are used because the spectral artifacts in DARM are weak but clearly exposed with long averaging.

While all figures show coherence at 60 Hz, there are only a few other peaks in each of the degrees of freedom. It's not a convincing argument that a few lines may be caused by HAM6 ISI motion since there are not a lot of other strong peaks aside from 60 Hz. Still, there are some statistically significant peaks worth further investigation and possible mitigation. One caveat: this is just a 17 hour average, so it may be more convincing with increased averaging over many more lock stretches. This is something that should be investigated further.

Figure 1: H1:GDS-CALIB_STRAIN coherence with H1:ISI-HAM6_BLND_GS13X_IN1_DQ
Figure 2: H1:GDS-CALIB_STRAIN coherence with H1:ISI-HAM6_BLND_GS13Y_IN1_DQ
Figure 3: H1:GDS-CALIB_STRAIN coherence with H1:ISI-HAM6_BLND_GS13Z_IN1_DQ
Figure 4: H1:GDS-CALIB_STRAIN coherence with H1:ISI-HAM6_BLND_GS13RX_IN1_DQ
Figure 5: H1:GDS-CALIB_STRAIN coherence with H1:ISI-HAM6_BLND_GS13RY_IN1_DQ
Figure 6: H1:GDS-CALIB_STRAIN coherence with H1:ISI-HAM6_BLND_GS13RZ_IN1_DQ

TITLE: 06/24 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
OUTGOING OPERATOR: Jim
CURRENT ENVIRONMENT:
    Wind: 13mph Gusts, 9mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.12 μm/s

Little windy, but less windy than last night! *knock on wood*  Microseism is low. 
QUICK SUMMARY:

H1 has been locked/OBSERVING 15.75hrs with a range hovering over 116Mpc.

TITLE: 06/24 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 117Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: Nothing much happened
LOG:

Couple small earthquakes at the start of the shift, but no transition required. 

20:45 GRB

Here is the full list of h1seiex DAQ-CRC error events we have seen since 13th June. There are 20 in total, and each one has exactly the same profile, with h1iopseiex CRC incrementing by 7 each time, and the user models (h1hpietmx, h1isietmx) incrementing by 8.

The first column is the date in June. Note that generally the time of the event is randomly distributed throughout the day exept for two event pairs (marked with +) which are three and six minutes apart.

13 03:57:46.000000Z
13 08:26:19.000000Z

14 20:45:14.000000Z

15 07:14:56.000000Z
15 12:08:52.000000Z
15 19:50:32.000000Z

16 18:37:31.000000Z

17 01:07:17.000000Z
17 17:32:49.000000Z
17 22:49:13.000000Z

19 02:14:14.000000Z
19 11:14:04.000000Z

20 03:04:27.000000Z
20 16:01:39.000000Z

21 07:02:05.000000Z+
21 07:05:39.000000Z+
21 09:59:01.000000Z

23 05:06:11.000000Z

24 04:56:32.000000Z+
24 05:02:10.000000Z+

Next to the big red button, there are 4 new red/green lights with 2 readouts that show the outputs of the nominal and earthquake sensor corrections for each test mass. The idea is that if there is an incoming earthquake, the user will look at the lights and if any of them are red, wait for them to go green again before doing the transition to the earthquake mode, or before going back to Windy. 

The transition to the earthquake seismic state has occasionally caused locklosses. I haven't been able to run down the exact cause for this but, it could be from some low frequency offsets in the different sensor correction paths. These offsets are caused by the different filters and sensor configurations used by the nominal and earthquake sensor correction paths. I've added some lights and readouts to hopefully make the transition smoother. These are the red and green boxes in the upper left corner of the attached screen shot.

The boxes for each chamber are green when the differences between the two paths are less than 3 microns and they go red when the differences are greater than 3 microns. I don't know for sure if 3 microns is a good limit or not, but I've watched successful transitions that were about the level. 

In the attached screen shot, the yarm chambers have are red because they have offsets of about 8 microns. The units in readouts are nm, i.e. for the top right box the difference between upper number and lower number is (-309) - (-8196) =7887 > 3000. The bottom two boxes are green, i.e. for the bottom left box the difference is 37-787=750 < 3000.

HAM and BSC IS  CPS sensors look good, no alerts when running the script to look for excess noise.

TITLE: 06/24 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Jim
SHIFT SUMMARY:
LOG:

14:00 GRB alert - latency 19,501 sec - Ignored

11:44 and 11:45 -  Incoming Earthquake from Tonga.
Moving to Earthquake mode in precautionary preparation

ETMY could use some centering, in general. Not sure what happened there, in YAW after last centering. ITMX settles to a ~2.5urad in pit after loops converge but still sits ~ 11urad high in PIT when unlocked and even after DRMI ASC. I'm not sure what's going on there.  I'll continue to watch these and make adjustments on maintenance days when I can.

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

    PMC:
    It has been locked 26 days, 14 hr 47 minutes (should be days/weeks)
    Reflected power = 10.43Watts
    Transmitted power = 54.23Watts
    PowerSum = 64.66Watts.

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

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

    Possible Issues:

TITLE: 06/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 115Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY:

Ugh.  Rough shift.  Started out with a lockloss from the get-go, and H1 had issues relocking.  (Sheila even texted to check on me.)  Noted issues earlier, and I guess I am blaming wind, but I'm not sure (we were plagued by 20+winds most of the shift).  Then during recovery we were hit by a 7.3 EQ which kept us down for another couple of hours.  Just performed a 2nd alignment and handed off to Ed and H1 is getting further than it did at the beginning of the shift.  I'm going to try and sneak out soon in case I am bad luck!
LOG:

• 23:32 Lockloss ( a couple of EX alarms/glitches and then lockloss.)  See earlier alogs.
• 0:50 Large dust counts at EY
• Post Alignment Lock:  
  • 1st attempt:  Locked DRMI directly on first attempt, but dropped out at DRMI_LOCKED_CHECKED_ASC.
• 1:12 Incoming EQ from Papua New Guinea on VERBAL
• 2:58 Incoming 7.3 Large EQ on VERBAL
• 3:43 Transitioned to LARGE_EQ_NOBRSXY (~10min ahead of R-wave arrival)
• 4:30 Transitioning back to WINDY (eq band at 1um/s).
• 4:36 2nd Initial Alignment of shift!  (still see 0.06Hz EQ noise), but....
  • 5:40 ALSx finally completes Initial Alignment (& it was the fast one!  Still waiting for Y-arm...but it keeps dropping out of lock every 10min or so...but we obviously need 10s of minutes to complete Initial Alignment during an EQ.)
    • 5:49 ALSx GREEN_WFS_OFFLOADED done!!!
  • 5:52 ALSy finally completes Initial Alignment!  
    • 5:54 ALSy GREEN_WFS_OFFLOADED done!!
  • 6:13 Initial Alignment COMPLETE!
• 5:58 EQ band at 0.2um/s
• 4:45 Winds finally dip under 20mph for first time in shift!
• 6:20 Returned the ISI CONFIG to the WINDY state.  Winds are also under 20mph.
• First lock attempt post-EQ:  DRMI broke lock at DRMI_LOCKED_CHECK_ASC
• Second Lock (which I'm handing over to Ed) has made it to OFFLOAD_DRMI_ASC!  (But I did do a PRMI tweak, and also saw the PR_GAIN & POP18 glitching observed at the beginning of the shift.)
  • At Engage Soft Loops now....and now I'm sneaking out!

Thanks, Corey

TITLE: 06/24 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 11mph Gusts, 8mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.12 μm/s
QUICK SUMMARY:

H1 locking seems to be going ok at this point...

In addition to 20+ mph steady winds (gusts just under 40mph) for most of the shift, we were hit with a 7.3 EQ from the South Pacific.  I'm trying to run an alignment (because the arms were not locking), but the 0.07Hz eq noise is pretty dominant as the Green WFS try to fight the EQ.  I transitioned to the EARTHQUAKE state to see if that would make it easier for the GREEN WFS, but not sure if it's helped.  Attaching a screenshot of the ALS X&Y guardian nodes.  

One unfortunate feature, I've noticed while waiting for ALS is that when the Y-arm breaks lock, it immediately goes to the UNLOCKED state, despite me selecting INITIAL_ALIGNMENT.  Maybe it's always been like that, but it would be nice if this node would not stay in the UNLOCKED state and return to INITIAL ALIGNMENT & relock (because it drops out quite a bit and I have to keep my eyes on the node to manually select INITIAL ALIGNMENT.  (or maybe I'm just being impatient as I want to move on with this alignment!)

Oh, and the winds had a little lull about 45min ago (445utc), but looks like that was shortlived because they've picked back up!

After the Initial Alignment, the outlook looked better with H1 making it all the way to DRMI on its own (no PRMI tweaks needed).  But it had multiple locklosses before OFFLOAD DRMI ASC.  

Did a small alignment tweak via PRMI & this got me a little further and even through a noisy stretch for the PR Gain & POP16 (see attached).

But overall, have not had much luck.  The winds have steadily been increasing (steady in the 20s & approaching gusts in 40s).  I am marking OBSERVATORY MODE  from Locking to WINDY.  

OH, and we also had some South Pacific quakes roll in, so I'm in the EARTHQUAKE state as well.

I'm going to wait out the EQ a little and then return to locking in a bit.

Had a lockloss at 23:32utc (4:32pm PDT).  Nothing obvious, but it was windy.  Thought I would let H1 relock on its own, but it's been over an hour, and have tried various things, and am now going for an alignment (I've not done an alignment in several weeks!).

NOTES:

• Let H1 relock on its own.
• Green arms locked up OK.
• Lockloss at FIND_IR, LOCKING_ALS, FIND_IR, 
• ALSx polarization was at 28, so took time to reduce it (22.5 was all I could get down to, and it started increasing).  While I was at it, I took ALSy from 2.8 to about 0.5.
  • Marked this briefly as Preventative Maintenance and then Corrective mainteannce
  • Diag Main continues to have warning of ALSx polarization of " > 20% ". 
• Returned to locking and finally able to FIND IR!  Moved on to DRMI locking, but after 3min flashes weren't great, so 
• Went for PRMI....only able to get POP18 to 51.
• DRMI would not lock after 10min, Checked MICH Fringes & moved BS only a little.  Then tried PRMI (AGAIN), but there was a lockloss.  
• Gave up on relocking as-is.
• 0:38 INITIAL ALIGNMENT begins.
• 0:56 IA ends.
• Back to locking!