18:39 Lockloss due to EQ which we received Verbal for rolled in.  Was not able to attempt to ride through it due to BRSx issue (known issue from Fri).  Will need some time to ride through this.....

Attached are trends for oplevs.

NOTE:

• ITMx PIt continues its trend above +10urad  and needs to be centered.

The BS in yaw has an interesting pattern of wandering during a lock.  This typically starts out with a increase seen on the optical lever of about 0.5urad, then a decrease on the optical lever of about -1.5urad, and the an increase of about 1urad, which brings the signal back to about where it started, and the entire process takes about 10 hours, so it's slow.

This pattern repeats in multiple long locks, and there are number of lockes where the patern starts, but never finishes, because H1 loses lock.

The first two plots attached, each show 10 days (plot 1: Aug 8 to Aug 18, plot2: July 30 to Aug 8), and the pattern is visible in both plots. 

In the next 5 plots I've put t0 at each pattern, and saved the plot with a name that reflects if the pattern was complete or ended in Lock Loss.  In the most recent 10 days, there are 2 BS yaw wandering patterns that complete, and 3 that don't because H1 lost lock.

The last plot is of the wander on 10 Aug, 23:19:22UTC, which starts at around 9 Aug, 17:00:00UTC, and finishes around 10 Aug 05:30:00UTC, about 10 hours.

Only notable here is the EX_PS_PRESS1_PSI channel changes from -225 to about +90 on around Aug 6, 2019.

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

    PMC:
    It has been locked 1 days, 18 hr 22 minutes (should be days/weeks)
    Reflected power = 10.4Watts
    Transmitted power = 53.45Watts
    PowerSum = 63.85Watts.

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

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

TITLE: 08/18 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 106Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:  locked all shift, some periods of less glitching, range holding above 100Mpc
LOG:

• 09:09:46 - DCPD
• 14:53:30 - EX

TITLE: 08/18 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 106Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s

All looks quiet from the Control Room.
QUICK SUMMARY:

H1 has been locked/observing for almost 11hrs (& L1 literally just went down [& V1 looks to have went down 2.5hrs ago]).

H1 is still in lock, range is 110Mpc.

TITLE: 08/18 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 102Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 8mph Gusts, 7mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY: locked, range trending downwards but still above 100Mpc

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

My alignment job while recovering the green arms wasn't the best as can be seen in the previous log's screen shots but I was able to re-align ITMX in situ by turning off DOF3 controls and slowly bring the pitch in. It took a couple of IA runs to let the WFS do all the heavy lifting. The beam splitter got pretty misaligned in the process as well (me again). MICH Bright didn't work so I "manueled" past it and handled that alignment during PRMI. The script to re-align SR2 was pretty nice to have and worked well. After PRMI ASC was done, she went right up. Handing of to Cheryl
LOG:

1st Attempt:

• X arm alignment for ALS bad before attempting
• Y arm is just trash right now.
  • gonna try for a bit but it looks like IA may be in order....yep

1:12 IA

2:20 HA! I WIN! (green arms) Both arms were hosed. I got NO love from trending/resetting witness sensors or sliders. I used oplevs for limit references and aligned by visual and very zoomed in ndscope.

2:30 then X did this (see below) :/ - not winning.....yet

2:58 Green Arms finally done!

3:15 IMC unlocked after input align - having trouble re-locking itself - it seems the laser power is still at 9.5W

3:18 Decreased LP to 2W - Cycled IMC guardian - locked

3:30 IA complete - sort of (Mich Bright didn't work)

I re-ran IA Guardian a couple of times just to e sure I didn't interrupt anything

2nd Attempt

3:31 gonna take a swing at re-locking.

3:54 re-locking going ok - at ENGAGE_SOFT_LOOPS

4:12 H1 Observing!

TITLE: 08/17 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 107Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    Wind: 14mph Gusts, 10mph 5min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY:

23:11UTC GRB Stand Down Expired

TITLE: 08/17 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 103Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

H1 continues to run the SEI_CONF guardian in the following state:  WINDY_NO_BRSX.

Has been locked/observing almost 24.5hrs.
LOG:

• 16:29 Cyclists drive down the LIGO driveway (have a snack) and leave.  :)
• 21:16 Visitors approach LSB door (take selfies at entrance).
• 22:52 GRB was received & will Stand Down (INJ_TRANS was already in the INJECT_KILL state).

h1 continues with lock/observing approaching 20.5hrs with a BNS range hovering between 102-113Mpc.  All is quiet otherwise.

TITLE: 08/17 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 108Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

Not much to pass on.  Locked/Observing for almost 16.5hrs (with the noticeably-varying range [see Cheryl's plot in her summary]).

TITLE: 08/17 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 105Mpc
INCOMING OPERATOR: Corey
SHIFT SUMMARY: locked all shift, range plot for 16 hours attached to this alog
LOG:

• 23:51:00 - DCPD glitch
• 06:07:57 - DCPD and EX glitch
• 06:39:36 - DCPD and EX glitch
• 08:00:10 - DCPD and EX glitch
• 09:03:03 - DCPD glitch
• 09:32:24 - EX glitch
• 10:34:23 - EX glitch
• 10:57:43 - DCPD glitch
• 11:41 - EQ1, off coast of Oregon
• 12:47 - EQ2, North of us by about 100 miles, an M2.3, changed Latest EQ website to real All Magnitudes (alog 51349)

Figures Of Merit:  We're in the process of replacing our monitor that displayed wind, so I put a NEW_WIND striptool on Video4

The USGS site has options for what EQs are displayed, and tonight I had one seismic events, seen in H1 and on our seismometors,  that I didn't see on their site, until I switched from the default of M2.5+, to ALL Magnitudes for the US. 

• First EQ: M3.3 off the Oregon Coast, 11:41:53UTC Aug 17th - seen with the default setting
• Second EQ M2.3 roughly 100 miles North of LIGO, 12:47:50UTC Aug 17th - not seen with the default setting of M2.5+
• plots attached for both events

We've had a few other small seismic events where we could not identify the source, so we might want to adopt this setting change for the FOM display.

The setting of All Magnitudes for the US, doesn't alter the display of World EQs, it just fills in the 0-2.5M EQs for the US.  Nuc1 Latest EQs is currently set for All Magnitudes, US.

TITLE: 08/17 Owl Shift: 07:00-15:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 108Mpc
OUTGOING OPERATOR: Ed
CURRENT ENVIRONMENT:
    Wind: 21mph Gusts, 16mph 5min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.09 μm/s
QUICK SUMMARY: range is more variable tha usual, still, locked in Observe

• The OUT Gate was 1/2 way open when I arrived.
  • Ed took a picture with my headlights on the gate (will add)
  • I've noticed this before, and emailed Bubba, and this is the first time I've seen this happen again, so the frequency has gone down
  • What it means for the previous shift is that we can't guarentee that no vehicles were on site / driving down the arms

I am unable to phone the site either via land line or Verizon Wireless.  Regardless, we need to have the Vacuum Site Overview available for remote viewing.  Someone has replaced our screen with one showing the wind speed. 

At 13:03 PDT all h1psl0 models stopped running. I found that one of the 16bit DAC cards was not seen on the pci bus.

We power cycled both CPU and IO Chassis, the missing card reappeared. The IOP model did not run due to the IX Dolphin card in the CPU, but not configured on the fabric *.

Powered down CPU and removed IX611 card. IOP still wont run, its configured to use the card.

Removed pciRfm=1 directive from h1ioppsl0 and installed new IOP model. It started but we had a negative IRIG-B excursion which took about 15 minutes to clear.

Started user models, all is running and Peter verified correct DAC drives on all models.

* a description of how we got here. During the 18 Sept 2018 upgrade of Dolphin from DX to IX, h1psl0 was upgraded along with all the other IPC'ed systems. We then entered the series of Dolphin crashes, which took the PSL down each time, we quickly took the PSL out of the Dolphin fabric(%)by simply disconnecting its IX cable and taking h1psl0 out of the Dolphin manager's configuration. This kept h1psl0 stable and no reboot was necessary at that time. Fast forward to today, and h1psl0 had not been rebooted for 332 days, which is why we are seeing these startup problems today.

(%) In consultation with Keita, Daniel and Peter, the Dolphin IPC was used for ISS third loop PD readout from the end stations, and DBB Jitter transmission to LSC. Neither were needed for O3.