J. Driggers, S. Dwyer, J. Kissel, R. Kumar, J. Warner [all remotely]

After this morning's lock loss (known to be caused by an innocent attempt at an excitation on the HAM ISIs), we held the IFO in the "DOWN" / "READY" state, and did the following in preparation for the early end of O3B:
    - run through the entire SDF system, 
    - brought all systems to their designated "safe" configuration (including ISI / HPI systems), 
    - flipped all comparison snaps to the respective "safe.snap" files, 
    - turned off the "unmonitored channels" mask, and reconciled each system 

Major outliers were:
    - R0 damping configurations in ETMs (good catch! had not been captured)
    - Spot position move differences (controlled by guardian, but reflects recent methodology changes)
    - The latest violin mode damping configuration
    - Monitored much more ASC channels than had been before 
    - All SUS alignment offsets were captured
    - TCS lasers had some fake EPICs readback channel values that were accepted, they're now unmonitored (because they're really readbacks) 
    - (masked, b/c guardian controlled) CPS DIFF configuration was left an unaccepted, because it's on now, but we want it to come up off as it is in the safe.snap.
    - (masked, b/c guardian controlled) PCALX high frequency line frequency was left as unaccepted, because it's 3001.3 now, but we want it to come up 4001.3 as it is in the safe.snap
    - (masked, because TINJ controled) calinj channels that are readbacks of injection properties were left as unaccepted (cause they're changed during every injection) 

All other systems were either already captured nicely, or uninteresting (eg the random TRAMP here or there, or some small digitally negligible difference).
 

J. Kissel [remotely]

I've gathered the standard, full, suite of calibration measurements today. The full suite will be useful for building up the new reference model that we'll likely need after the OMC whitening chassis configuration change last week. Other than the new OMC whitening chassis configuration, the IFO was otherwise operating normally for O3B. ~38W input to the IMC, 50 ct SRCL offset, usual configurations of the actuator.

Raw data files have been committed to the following directories:
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
        2020-03-23_H1_DARM_OLGTF_LF_SS_5to1100Hz_15min.xml
        2020-03-23_H1_PCALY2DARMTF_LF_SS_5t1100Hz_10min.xml
        2020-03-23_H1_PCALY2DARMTF_BB_3min.xml             << injection started at 2020-03-23 18:01:20 UTC

    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOActuationTFs/
        2020-03-23_H1SUSETMX_L1_PCAL2DARM_5min.xml
        2020-03-23_H1SUSETMX_L1_iEXC2DARM_8min.xml
        2020-03-23_H1SUSETMX_L2_PCAL2DARM_6min.xml
        2020-03-23_H1SUSETMX_L2_iEXC2DARM_12min.xml
        2020-03-23_H1SUSETMX_L3_PCAL2DARM_6min.xml
        2020-03-23_H1SUSETMX_L3_iEXC2DARM_12min.xml


Data analysis to come.

TITLE: 03/24 Day Shift: 15:00-23:00 UTC (8:00-16:00 PST), all times posted in UTC
STATE of H1: CALIBRATION
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 29mph Gusts, 13mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.23 μm/s
QUICK SUMMARY:

Getting ready for Maintenance Day. 

Currently running the weekly PEM Magnetic Injection.

TITLE: 03/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: Ed
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 11mph Gusts, 6mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.25 μm/s
QUICK SUMMARY:

• 12:02 UTC - H1 lockloss from NLN - H1 out of Observe
• 12:49 UTC - H1 lockloss from MOVE SPOTS
• 13:25 UTC - H1 back in Observe, range is 19.8Mpc
• all locking was automated

TITLE: 03/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: Cheryl
SHIFT SUMMARY:
LOG:

Shift ran un-eventful

• handingoff to Cheryl
• Initiating transition to remote Owl shift

• Everything running smoothly
  • There's been some glitches but no saturations
• Winds have been moderate and causing a slight dips in rane but overall it's been nominally ok.

TITLE: 03/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
INCOMING OPERATOR: Ed
SHIFT SUMMARY: Quiet shift with a couple of breaks for commissioning and calibration. Wind has picked up this afternoon.
LOG:

• 18:03 Out of observing for Calibration Measurements
• 19:29 Back to Observing 
• 21:49 Out of observing for Commissioning Injections
• 21:51 Back to Observing 

TITLE: 03/23 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 114Mpc
OUTGOING OPERATOR: Camilla
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 29mph Gusts, 21mph 5min avg
    Primary useism: 0.07 μm/s
    Secondary useism: 0.24 μm/s
QUICK SUMMARY:

Katie Rink, Jess McIver

Summary: Brian Lantz wondered if leap day was a new record. We looked into the duration of coincident H-L observing mode stretches before and after the October commissioning break. Leap day was a new O3 (and likely all-time) H-L coincident observing mode record by more than 16 hours.

• Figure 1 shows a histogram of continuous observing mode segments for LHO using bin widths of 1 hour, with O3a and O3b plotted on top of one another. Note that the y-axis is log scale.
• Figure 2 shows the same but for LLO.
• Figure 3 shows the same but for the LLO and LHO coincident times, calculated using the GWpy segment intersection function.

In O3a, the longest coincident observing mode stretch was 32.4 hours. In O3b, the longest coincident observing mode stretch was 48.8 hours.

Our main findings are summarized in the table below.

I queried observing mode segments using DMT-ANALYSIS_READY:1 flag for L1 and H1, and the intersection between L1 and H1 in the time span of O3a and O3b independently. O3a was defined as Apr 01 2019 00:00:00 UTC - Oct 01 2019 14:00:00 UTC, O3b was defined as Nov 01 2019 18:00:00 UTC - Mar 23 2020 00:00:00 UTC.

The code I used can be found here.

I just took 5 minutes of commisoning time to redo the CHARD P noise budget injection.  I ran this on Thursday but a large glitch interfered with the measurement. 

Some weird spikey temp plots and the downward stepping of the DCHILFLOW plot.

DQ Shift Summary: 16 March 2020 (1268352018) - 22 March 2020 (1268956817)

• Mean Duty Cycle = 87.22 %
• Mean BNS Inspiral range = 118.14 Mpc
• PCAL X lines shown level variations at Higher Frequencies greater than 1 KHz
• Spectra lines shown level variations.
• Top Channels: Hveto Round 1 winners
  • H1:LSC-POP_A_LF_OUT_DQ
  • H1:ASC-Y_TR_A_NSUM_OUT_DQ
  • H1:LSC-REFL_A_LF_OUT_DQ
  • H1:PEM-EX_ADC_0_19_OUT_DQ

• Locklosses:
  • 5 locklosses due to Earthquakes
  • 9 locklosses due to Commissioning/Hardware Injection/Instrument saturation
  • Causes for 4 locklosses in a week are unknown

• Violin modes were rang up at begining of lock state
• Glitches
  • ~36 Hz shown up on Monday, Tuesday and Friday
  • ~11 Hz - Friday: From 12 UTC to 13 UTC
  • ~29 Hz - Wednesday, Thursday and Sunday
  • ~860 Hz - shown up many times in a week

DQ Shift Summary Page: https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20200316

FAMIS 11057   

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

    PMC:
    It has been locked 12 days, 23 hr 41 minutes (should be days/weeks)
    Reflected power = 11.95Watts
    Transmitted power = 51.75Watts
    PowerSum = 63.7Watts.

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

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

    Possible Issues: NONE

TITLE: 03/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 119Mpc
OUTGOING OPERATOR: Cheryl
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 6mph Gusts, 5mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.24 μm/s 
QUICK SUMMARY: Locked 13 hours. Microseism is coming down but there has been some win spikes overnight.

TITLE: 03/22 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 118Mpc
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: One lock loss from observing, likely from an earthquake. Ran initial alignment after guardian failed to lock PRMI a number of times. Back to observing after. No issues since.
LOG:

23:07 UTC Lock loss from Observing. Likely from earthquake.
23:25 UTC Lock loss from ACQUIRE_PRMI.
Found IR by hand
00:09 UTC GRB-Short. Not locked.
00:13 UTC Guardian has gone to CHECK_MICH_FRINGES three times. Starting initial alignment.
00:38 UTC Initial alignment complete.
01:08 UTC Lock loss from PREP_DC_READOUT_TRANSITION.
01:49 UTC Observing. No SDF differences.

Lost and reacquired lock. Had trouble with DRMI and ended up running an initial alignment. No issues since.

[Robert, Jenne]

This morning we locked DRMI and moved various optics around while Robert took video to see if the beam on the HAM5 side of the septum moves at all.  Robert reported as we were working that he didn't see any obvious movement of that beam, but I'm sure he'll have more details after he's had a chance to review the movies.

We moved SR3 by 28 urad, we moved PR3 by several urad, we moved both ITMs by a few urad each, and I put an offset of 0.7 in the DC3 loop to move OM1 just in case the beam was somehow coming back through that septum viewport.  We also put 1.4 Hz excitations into each of the 3 dofs of the OFI to make it move rail-to-rail on its (weak) actuators.  Last week we had moved the OFI to the edge of its range in yaw, and had also moved ZM2 to the edge of its range, as well as put offsets into the AS_C SRC loop.  So far, nothing seems to move the beam. 

Robert will have more details later, but the beam is quite weak when we have the PRMI locked, even if I bring the power up to 20W injected.  But as soon as the SRM comes into alignment, the beam shows up clearly with DRMI flashes. (The fast shutter was closed when we did that test last week).

The work this week and last Tuesday was all done DRMI-only, with the ETMs misaligned, and DRMI ASC on.  I am running low on ideas of where this beam could be coming from, if I can't move it even the slightest bit with these optic moves.