Attached is a photo of what we have on the white board.

Addressed TCS Chillers (5:08pm local):

• TCSx Chiller:  Had level of 30.0 cm.  No water added.
• TCSy Chiller:  Had level of 9.3 cm.  Added 50mL for 10.2cm.

To set an operator's lock-loss alert configuration prior to their shift type the following command:

owl_op operator.name

Where operator.name is the operator's ligo.org name. These settings rely on the Guardian IFO_NOTIFY node to alert for both lock-loss and out-of-observation events. GraceDB events are disabled, and alerting times restricted to the shift times.

I've added the IFO_NOTIFY node status and link to the LOCKLOSS ALERT Overview page. Anyone with voice-call option selected is shown with an ORANGE phone indicator.

TITLE: 02/24 Eve Shift: 00:00-08:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 120Mpc
OUTGOING OPERATOR: Patrick
CURRENT ENVIRONMENT:
    SEI_CONF state: WINDY
    Wind: 9mph Gusts, 7mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.31 μm/s 
QUICK SUMMARY:

H1's been locked 21.5+hrs.  Microseism has been trending down the last 14hrs (currently between 90th-50th percentile).

DIAG_MAIN has:  "PCAL X OFS servo malfunction", but this was noted earlier.

TITLE: 02/24 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:

Remained locked the entire shift.

Out of observing for Jim to address SEI_DIFF issues, calibration, and ASC sensing matrix measurement.

Received alert for S200224ca.

LOG:

16:14 UTC Tyler and Chris tumbleweed chipping on X arm
16:21 UTC Tyler and Chris tumbleweed chipping on Y arm, instead of X arm
17:03 UTC Out of observing. Jim addressing SEI_DIFF issues (alog 55258)
17:07 UTC Jim done. Back to observing.
17:10 UTC Dripta to optics lab
17:28 UTC Dripta back
19:00 UTC Out of observing for Jeff K. to run calibration measurements
19:31 UTC Sheila investigating increase in H1:SQZ-OPO_REFL_DC_POWER.
20:32 UTC Jeff K. done. Back to observing.
20:34 UTC Received Hanford monthly alert test phone call
21:51 UTC Tyler getting close to end station with tumbleweed chipping at end X
22:23 UTC S200224ca alert
22:29 UTC Called Bubba to have tumbleweed chipping stand down
22:31 UTC Tumbleweed chipping machine shutdown about a quarter of the way from mid to end station
22:32 UTC Set INJ_TRANS to INJECT_KILL
22:57 UTC Set INJ_TRANS to INJECT_SUCCESS
23:57 UTC Gerardo to mid Y

Took ASC sensing matrix measurement with 'userapps/asc/h1/scripts/sensingMatrix/run_sensmat.py', using updated injection amplitudes. DHARD & CHARD yaw were too low to get a coherent measurement, I've left a note for next time.

ASC Sensing Matrix (Pitch), [W/rad]

ASC Sensing Matrix (Yaw), [W/rad]

FAMIS 11258

All appear in range.

J. Kissel

I've gathered all standard measurements for putting together estimates of the current sensing and actuation functions, in order to continue to beat down the statistical uncertainty in the unknown systematic error (especially in the actuator stages; see LHO aLOG 55055). 

The data sets live and have been committed here:
Sensing Function:
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
        Swept sine excitation:
        2020-02-24_H1_DARM_OLGTF_LF_SS_5to1100Hz_15min.xml
        2020-02-24_H1_PCALY2DARMTF_LF_SS_5t1100Hz_10min.xml

        Broadband excitation
        2020-02-24_H1_PCALY2DARMTF_BB_3min.xml                << start time 2020-02-24 19:00:39 UTC, for later GDS / DCS processing

Actuation Function:
    /ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOActuationTFs/
        2020-02-24_H1SUSETMX_L1_iEXC2DARM_8min.xml
        2020-02-24_H1SUSETMX_L1_PCAL2DARM_5min.xml

        2020-02-24_H1SUSETMX_L2_iEXC2DARM_12min.xml
        2020-02-24_H1SUSETMX_L2_PCAL2DARM_6min.xml

        2020-02-24_H1SUSETMX_L3_iEXC2DARM_12min.xml
        2020-02-24_H1SUSETMX_L3_PCAL2DARM_6min.xml

These data sets will be added to the uncertainty budget in due time.

Evan and Yanyan noted that PCALX was malfunctioning since Wednesday (LHO alog 43959 and 55257). Jeff has added an alert that will notify operators if this happens in the future (LHO alog 55257). 

Since, simply switching on and off the OFS control loop, didnot bring PCAL back, I looked at the PD singals and saw all PD signals were reading zero values. I tried switching on and off the laser remotely but still no signals on any of the photodiodes. Further investigations (on AOM status and/or the laser itself) will require  going down to the endstation. Stay tuned!

DQ Shifter: Yanyan Zheng

Email:zytfc@umsystem.edu

Fellow(s): Sudarshan

Mentor:NA

Summary:

Lock/Range

• Duty cycle in observing is (91.7%+60.6%+79.5%+77.2%+95.0%+88.7%+79.2%)/7=81.7%.
• Earthquake from Arctic, Russia and Japan on Tuesday, Thursday and Friday caused the lockloss.
• The average BNS range is ~118Mpc.
• On Wednesday, the range dropped to 108Mpc from 10:00-12:00 maybe because of out of observe to relock squeezer(alog55175)

Noise/Strain

• Violin modes at 500Hz and 1000Hz can be seen most time of the week.
• And on Thursday, violin modes at 1300Hz presented from 16:00-18:00
• ~33Hz excess noise can be seen most time in the week.(For example, 8am on Wednesday)
• On Sunday, loud noise presented at 17:30-18:30. It may come from the high speed wind.

Dechar:

• On Sunday, H1:LSC-POP_A_RF45_Q_ERR_DQ and :ASC-DHARD_P_OUT_DQ vetoed the loud noise at 18:00.
• H1:ASC-Y_TR_A_NSUM_OUT_DQ vetoed the low frequency noise on Monday, Wednesday,Thursday,Friday and Saturday.

Pcal:

• Pcal X : There is a small peak at ~18Hz on Monday and Tuesday but disappear on Wednesday until Sunday. And the line became smooth on high frequency after Wednesday. It looks like the optical follower servo saturated and so the PCAL is not able to inject lines for normal operations(alog55257).
• Pcal Y: nothing unusual.

Spectra: Nothing unusual.

Full report can be seen here:https://wiki.ligo.org/DetChar/DataQuality/DQShiftLHO20200217

Still trying to figure out full story, but last night when SEI_DIFF was transitioned to the corner only state, this engaged some filters (for the arm cps diff, which was being disengaged, so nothing weird was actually used) and created some sdf differences, which were accepted. I've fixed the filter settings and made some changes to the SEI_DIFF guardian that should keep this from being an issue in the future. I've also turned the full cps diff back on, I don't think this has an adverse affect on our ability to lock during high microseism any more, and it should be beneficial in high winds like we had over the weekend.

Out of Observe at 17:03 utc, back to Observing at 17:07 utc.

Yanyan noted in the DQ shift for LHO that the x-arm PCAL lines--both high frequency lines and CW hardware injections--disappeared on Wednesday Feb 19 2020 (see summary page plot). It looks like the optical follower servo saturated on this day. The loop should be opened and closed again to regain normal operations as soon as is possible. Likely this will cause a glitch so perhaps it should be done out of observing.

This plot covers 11 Feb to 19 Feb, 2020, a more recent stretch of time, showing H1 locking and Initial Alignment, and the ASC_A Pitch and Yaw Offsets.  My original post, for 29 Jan to 5 Feb, is alog 55194.  Color scheme for the previus plot and this plto are the same.  There are a coule places where there are multiple Initial Alignments, and I can tell that in at least one case, these repeat Initial Alignments are a result of going back to recheck one state, and not a full Inital Alignment.  Gathering further info on these situations, to incorporate in future plots.

TITLE: 02/24 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Observing at 120Mpc
INCOMING OPERATOR: Patrick
SHIFT SUMMARY: locked all shift in Observe
LOG:

• 10:00:06 - GRB, standdown is complete
• 14:23:57 - DCPD glitch
• 14:51 - Tyler driving down X arm to assess the Tumbleweed situation
• 15:32 - Tyler back from the X arm

H1 SEI Configuration:

• last night Ed changed SEI config for CDIFF, see alog 55249
• Ed accepted changes related to this in SDF
• when H1 breaks lock, if this is reverted, there will be SDFs

[Sheila, Jenne, Keita]

Since we thought that increasing our DARM offset would improve our sensitivity slightly (alog 55105) we wanted to do one more on/off test using online SRCL FF with the new filter (alog 55189).  We took 2 sets of on/off, and then determined that although very slight, there did seem to be a consistent improvement with the higher DARM offset and so put into guardian to relock with the higher DARM offset.  However it has been reverted since it seems that we can't hold lock through glitches.

After noting that I couldn't change the SRCL LSC loop's cutoff filter (alog 55207) we moved the DARM offset such that we had 40mA sum on the OMC DCPDs and turned on the iterative SRCL FF filter.  Sheila did a brief scan of squeezing angle to see if there was any change to the squeezing angle from the DARM offset change (not that we expect that their should be).  We left the squeezing angle 5 degrees different from how it had been, but determined that this was a pretty small change and didn't change it again when going back to check the 20mA DARM offset.

We took 2 sets of on/off spectra to (try to) convince ourselves that it was a real effect that we were seeing, and determined that we could also continue to look at more new configuration spectra after going to Observing.  The difference is much more subtle than we were expecting, although it seems to be repeatable. 

The first 4 attachements are all the same spectra (2 old nominal config, 2 candidate high DARM offset config) in 4 different zooms.  The first attachment is over the full GW band, and the other 3 are zoomed from 10-200 Hz.  The second plot is to show a zoom of the small improvement we see, and then the third and fourth plots are just to show that the spectra in each configuration are similar to one another, since they are all overlapped in the second plot.  In all of these plots, the pink/red traces are from the nominal DARM offset, and the blue/cyan traces are with the higher DARM offset. 

Particularly around 90 Hz, there seems to be a repeatable improvement with the higher DARM offset.  There is also an improvement at higher frequencies, perhaps due to smaller influence of any intensity noise or frequency noise on the junk light.

I added a new state to the ISC_LOCK guardian to change the DARM offset just after Lownoise_length_control, and added the new iterative SRCL FF filter to the guardian, and it worked twice to relock.  The 5th attachment shows the range calculated by the summary page (after the effect on calibration is taken into account), showing that we seem to have eked out a small improvement.  Noteable is that with the slightly different optical gain, in the high DARM offset configuration the control room reported range number (which does not track time dependent calibration corrections) becomes a slight underestimate rather than our usual case of a slight overestimate.

The higher DARM offset does put us much closer to the edge of our ADC range when we have 2 stages of whitening on (as is our nominal configuration).  We seem to not be able to survive glitches when running in this state, and have had 2 locklosses after very brief Observing segments with the higher DARM offset, and so have backed out the change by bypassing the new change_darm_offset state and taking out the iterative SRCL FF filter.  The 6th figure shows the OMC DCPD inputs before they are filtered to account for the analog whitening, and you can see that just before we lost lock we came extremely close to hitting the ADC limit, although we didn't actually go over 32000 counts.  Something that we may consider is what the tradeoff would be if we were to operate in the LowZ transimpedance option for the DCPDs, since that would keep us farther away from the edge. 

Sheila, Jenne, Rahul

I went through all the monitor filters for the violin modes to confirm the following,

The band pass filter has a gain of 120db and the bandwidth is 0.02Hz. The bandwidth at 80db is 0.04Hz.

With this boundary condition, I found 4 modes (ETMY 1,6 and ETMY 18,20) which are very close to each other (or are pairs), i.e. within 0.04Hz. The bode plots for all  4 modes are attached below. 

In fact mode 1 and mode 6 and only 0.011 Hz apart and they are sitting on the flat top of the band pass filter (which is not good, since they are creating beating and hence Guardian cannot effectively damp them). Sheila suggested that we can use notch filters to reject signals in this case.

Keita, Sheila

We had another example of the squeezer oscillations that were seen last weekend:  54864  The first screenshot shows the signals related to gree power in the OPO getting very noisy over ~ 6 hours this morning.  We went out of observing earlier than our planned commisioning time to try to address this.  We turned off the green ISS, which brough all the signals back to normal.  Turning that loop back on brought the noise back.  We also tried reducing the gain in that loop, which did reduce the peak to peak noise seen in the ndscope.  Based on loop measurements taken on Tuesday, 54888, the shape of this loop at its nominal 31dB gain setting should be fine. 

Next I went to the floor, while Keita took spectra and changed the gain from the control room.  On the floor I measured a spectrum of IN1 (the error point) on the green ISS, and I saw large lines at 15kHz and 30kHz.  Keita saw that there is an aliased line at 1249Hz in the spectra in the control room, which would correspond to a line at 15135 Hz.  The height of the 15kHz and 30kHz lines didn't change with gain changes, although the overall noise floor did change.  Ketia disabled the loop, and I could no longer see the lines on the error point, and the low frequency intensity noise increased (as you would expect).  

We then unlocked the squeezer by requesting no squeezing, and relocked it.  We saw no evidence of the 15kHz and 30kHz lines on the analyzer, although the red trace in the second attachment shows that the 1kHz line is still present.  We reset the ISS gain to 31Hz, which is nomal, and everything seems fine for the time being. 

Photos attached (after screenshots):

• 1st spectrum of ISS error point with gain change (reference is lower gain, I think this was 20dB and 26dB)
• 2nd same reference as 1st photo, ISS error point with loop open
• 3rd same reference as above, after OPO unlocked and relocked no sign of 15kHz and 30kHz lines.

For operators: 

The first attached screenshot is from the ndscope that is accessible from the upper right corner of the SQZ_OVERVIEW screen, called locking signals.  If you see the range dropping, open this ndscope and see if there is trend similar to what is shown in the attached screenshot that lines up in time with the range drop.  In the left column of the screenshot you can see that the OPO REFL power is changing and the max-min difference gets larger, the max-min difference of OPO_IR_RESONANCE trigger gets larger, and the SQZ_SHG_LAUNCH power max-min difference also gets larger.  If this is happening and corresponds to a range drop, please unlock the squeezer by requesting "NO_SQUEEZING" from SQZ_MANAGER, then once it arrives, request SQZ_READY_IFO.  Once it arrives there hopefully the signals in the ndscope will have returned to normal, if so you can request "SQUEEZING" again.  If not you can try again or call for help.