Relocked after largish earthquake (Mag 6.0 in the Solomon Islands), high winds (gusts into the 30s), and completion of the today's commissioning activities. Wind and microseism continue to be high. 

   While checking into why range appears a bit low found Squeezer SHG Conversion Efficiency Low message. Have posted screen shots in the aLOG #49325, and have a call into Squeezer support.  

   The range has been a bit low since relock. Thought it might be due to high winds and series of EQs during the shift. In checking the Squeezer, found Squeezer SHG Conversion Efficiency Low status. Posted screen shots of the various related MEMD screens.   

   Accepted the following SDF differences after relocked at NLN. 

After we lost lock aligning the reference cavity, 49305, we had had two relocking attempts so far.  

Because Georgia and Niko had moved the ADS phase around last night, and Georgia looked at the HWS and saw that the beam was moved veritcally on ITMY, I stopped in DC readout to check all the ADS phases.  After ADS converged, I opened the loops, and moved the A2L gains to see if the response was in the I phase.  This was the case for P4, P5 and Y3 (ETMX P, ETMY P, and ITMY Y) but I changed the phases for the other loops.  After changing the phases, I checked that the old A2L gain setting still corresponded to a zero crossing, for two of the loops it did not so I found an A2L gain that gave us a zero crossing for the current alignment.  

We tried to power up this way, but there radiation pressure soft instability showed up at lower power, and in the X arm only (screenshot).  Since tuesday it has been a common soft instability.  As the 0.5Hz was ringing up, I tried to increase the CSOFT gain, which is normally 15, first to 30 then to 60.  It's not clear if this helped.  

We looked at the TMS QPDs, and saw that for TMSX we are nearly falling off the QPDs.  While sitting at DC readout, we moved TMSX pitch down by 8.6 urad to center the positions on the QPDs.  (We also turned off the offsets in the QPDs, which are no longer used at DC and therefore don't need offsets).  Then we lost lock because of the earthquake.  

We have replaced the TMSX test offset which is used by the dither alignment script to point the green beam to the baffle PDs (-34.1) with our offset of -8.6 urad.  Keita, Georgia and Jeff B will try engaging this in the next lock before powering up to see if this helps the QPD loops do a better job of suppressing the instability.  

We need to spend some time moving pico motors on TMS, because we are also nearly falling off the green QPDs which are used as our initial alignment reference.  That is a longer project though so we will leave it for another time.

TITLE: 05/17 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 111Mpc
INCOMING OPERATOR: Jeff
SHIFT SUMMARY:

Observing for the first ~3.5hrs of shift.  Went out to address the high-freq intensity noise by touching up refcav alignment.  Relocking was not trivial (with ALS issues, then ran an alignment, then worked on Dither Line Phasing).  Have tried to record notes of locking in other alogs or below.

Reckon we will have SDF diffs to deal with the next time we are ready for Observing (for possibly ADS/Dither Lines, ASC, SQZ, ALS).

Amber Note:  Ballet group will be walking the site (around 3:45pm) scoping out locations for upcoming event.  May or may not need to visit the Control Room.
LOG:

• 17:55-18:04 Out of Observing to lower a value (for H1:SQZ-FIBR_TRANS_DC_LOW) to allow us to be able to turn the SQZ laser autolocker back on.
• 18:28 Out of ObsesAddressing refcav alignment which is probably related to the high freq Intensity noise observed since last night
  • 18:28-18:57 Refcav touch-up
  • 18:58-21:41 Locking
    • Had various issues with ALSy & ALSx (alogged)
    • Still had locking issues & couldn't get to OFFLOAD_DRMI_ASC
  • 21:41-21:13 Alignment
  • 21:10 Back to locking
    • Had OM1 & OM2 saturations ("OMC" on Verbal) before finishing DRMI lock.  Jenne is currently updating guardian to address this (but for my notes below is what she did to clear these "OMC" saturations):
      • sitemap / ASC overview / DC Centering:  Turn off the INPUT for DC3_P [&Y] and DC4_P [&Y]
      • sitemap / SUS AS / OM1 [& OM2] / LOCK FILTERS:  Pitch [& Yaw] gains from 1 to 0.
      • sitemap / SUS AS / OM1 [& OM2] / LOCK FILTERS:  Pitch [& Yaw] CLEAR HISTORY
      • sitemap / SUS AS / OM1 [& OM2] / LOCK FILTERS:  Pitch [& Yaw] gains from 0 to 1.
      • sitemap / ASC overview / DC Centering:  Turn on the INPUT for DC3_P [&Y] and DC4_P [&Y]
      • Jenne hopes we don't have to do the above with her Guardian script update!
      • So please read her alog if you have any saturation issues!
    • 21:40 Dither Line Phasing work (while at ENGAGE_DC_VIOLINS by Sheila)
• 21:35 New HAM3 & 4 SEI ISI blend filters, and they were accepted in SDF (Jim, & see alog).
• 21:45 Backed out some Squeezer changes from the week (see summary in alog 49301).
• 22:30 Handing off to Patrick because I need to sneak out early.

A long time ago I came up with some blend filters to try to improve the 1-10 hz HAM RX/RY motion, to try to reduce SRCL. We ran the filter for about a week last October, but I've been having trouble trying to find good data to compare to the current configuration. Sam Cooper has a document comparing the differences and some of the motivation for finding a better filter at https://dcc.ligo.org/DocDB/0159/T1900107/001/main.pdf. I've switched HAMs 4&5 RX&RY blends to this filter to get some data overnight (or weekend). I made the transition while Corey was locking the IFO, and it's running fine for now. I've accepted the differences in SDF, so this shouldn't prevent us from going to OBSERVE.

The new blends are called "between_350" on the HAM ISI blend screens. If there is some issue where SRCL motion is bad, the old filters are called "notch_rolloff". If there are any questions or anyone needs help reverting over the weekend, give me a call.

We've found several times over the last few weeks that the OMs rail as we are trying to engage the AS DC centering loops, in preparation for engaging DRMI ASC.  I'm not sure why this has only started being a problem in the last few weeks and didn't bug us for the last few months.  I think it is happening if we try to turn on the DC centering servos a little too early.  

There is a checker for those loops to check for saturations because we've had this type of problem with the DC centering loops coming on too early in the distant past, but it was looking at the outputs of the DC servo filter banks.  This was the right thing to look at in the past, when we kept integrators in those filter banks.  However in the O2-O3 break we moved the integrators to the suspensions themselves, so now the servo filter bank outputs will always be near zero, and so will always pass the (old version of the) checker.  

I have added a few lines to also check the outputs of the OMs and RMs to see if the MASTER_OUTs are railed. If they are, then the engage_dc_centering states should clear the optics' histories and try again.  When doing this kind of clear history by hand, I've never had to do it more than once, so I'm fairly confident that this will be sufficient and we shouldn't have to worry about this again.  I've left in the old checking functionality too (although right now it'll always pass as okay) in case we ever decide to move the integrators back to the DC filter banks we won't get caught by this.

The following guardians will need to be reloaded: ISC_LOCK, ISC_DRMI, and ALIGN_IFO because they all use the ISC_library code that is now modified.  If there is a problem, one can comment out lines 170-174 in ISC_library.py and reload.

Also, I have added some clear histories and a short wait in ISC_DRMI's prep_for_drmi_asc state for INP1, since sometimes INP1 is sending out a kick and killing the DRMI lock.  I'd seen it several times, but Georgia put together the pattern that it only happens after we've done an initial alignment.  After she pointed that out, I think the problem is that since ISC_DRMI is already sitting in its down state, it doesn't go through down again as we get ready for main lock acquisition, so it doesn't redo the resets of INP1.  Sheila had already moved the gain setting to zero up in the prep_asc state, but because there wasn't a wait and the filters had some history in them, we were sending a short kick out before the gain gets all the way to zero.  Hopefully this will fix this problem, and we won't lose any more DRMI locks due to this.  

Sharan, Robert. 

There was heavy rain yesterday (16th May 2019) for about 10 minutes yesterday,  which we used as an adhoc pem injection. The noise from the rain seem to have caused a range drop of at least 2-3 Mpc (see figure 2 below), and coupled with DARM at ~ 48 Hz, 80 - 100 Hz and at ~ 380 Hz (see figure 2). Using the HAM6VAC SEPTUM accelerometer was a witness, the noise below 100 Hz in DARM seems consistent with the coupling estimate from 48912. It is not clear where the 380 Hz line is from, but it can be seen from spectrograms to be present for the duration of the rain (figure 3).

While locking ALSx arm looked glitchy and we kept breaking lock when Locking ALS.  So toggled the Noise Eater Off/On (on the ALS-X Laser Head medm screen).  Did this twice where I did a quick toggle, but Jenne mentioned leaving it off for 30sec then turned it back ON.

When locking after the PSL RefCav alignment touch-up, Needed to tweak both green arms, but the oddity this time is ALSy's WFS would not stay engaged. 

From ALS_Overview screen, opened the PLL & PDH screens and they both had issues.  Able to track down issue (by watching the flashing RED status which said "Laser Error".  So opened the ALS Laser medm (attached), and here Sheila noticed a message flash which said something related to "Diode 2".  The Laser Diode 2 Monitor is hovering around 1.6.  This value was out of range for our settings.  [Nominal was 1.4 with a tolerance of 0.2....so we were currently right around the limit of 1.6]. 

So nominal channel (H1:ALS-Y_LASER_HEAD_LASERDIODEPOWERNOMINAL) was changed from: 1.4 to 1.5 to allow for the ALSy Diode 2 Power drift up.

Summary:  18:28utc:  Out of OBSERVING (CORRECTIVE_MAINTENANCE) for PSL refcav alignment

Sheila checked on the high freq Intensity noise reported by Georgia last night, and has traced this down to PSL Ref Cav transmission (talked with Jason & heard him mention he has noticed this transmission dropping when humidity in the H1 PSL room rises).  Consulted with Keita & we decided to take H1 out of OBSERVING & mark this time as CORRECTIVE_MAINTEANCE (FRS forthcoming).  Keita contacting Brian & I notified other observatory operators via TeamSpeak.

RefCav alignment touch up is being done by Jason here in the control room via picomotors on the table.  This touch up caused a lockloss.  Once Jason is complete, I will take H1 to DC Readout and then we will take this opportunity to check H1's ability to acquire (I assume this will involve alignment stuff---i.e. ASC & Dither line systems).

After being locked for ~1.5 hours, ASC yaw oscillations started to build up. I re-phased PIT3 in the ADS overview to 110 via Georgia's original re-phasing alog (49298). This is reducing the oscillations, so I am accepting sdf changes for this phase setting.

Additionally, before this we were getting taken out of Observing sporadically with changes to H1:SQZ-FIBR_SERVO_COMGAIN, H1:SQZ-FIBR_SERVO_FASTGAIN, and H1:SQZ-FIBR_LOCK_TEMPERATURECONTROLS_ON. On the SQZ medm screen it looks like the SHG Power is to blame, as it is railing to -9000. There is an alog about this that Nutsinee posted (48760), but I don't think I can recreate what she did to mitigate the problem. We still get an extra 15 Mpc with squeezing on, so I'm un-monitoring these channels for now and going back to Observing.