All times local PDT.

0728  IFO Dropped Lock

0755 Richard Starts on PRM -- Finished 1044 -- No obvious problem but Chassis changed.

0759 Hugh Installs STS2-A at HAM2 -- Finished 0825

0822 Keita to EndX for QPD checks-- Finished 1043--No obvious problem.

0833 Phil to EndX for UIM -- Upgraded breaker from 1 to 3Amps.  Done 0935

0835 Hugh updates ODC MASTER for Auto Intent_Bit Reset  ECR E1500352

0855 Ellie to TCS HWS Camera Power Supply, removes filter to EE Shop.  No good, revert to no-filter configuration.  Done 1033

0912 Nutsinee to TCSX for Temperature Sensor install--Finished 1158.

0930 Barker completes LSC/ASC/OAF/PEMEX  Model updates for SciFrame changes & others (see Kawabi=LSC)

1031 Kiwamu doing ALS Diff Electronic Measurements.  Done 1245

1000 SysDiag Guardian node down for rebuild finished 1723

1100 Leo starts ETM Charge Measurements.  Complete 1239.

1105 Model Restarts--H1OAF fails from Epics problem.  Halt model restarts.

1115 JimB fixes Epics problem.  Model Restarts resume.

1124 DAQ Restart

1130 Daniel & Sheila at AS WFS Electronic response  & dark noise  Done 1240.

~1100 Phil Terminating PEM Cables in LVEA and CER.  Installing 18bit DAC card.  Done 1244.

Following up on Evan's investigation into the glitches from LL coil on the PRM M3.   I tried to monitor the output with a scope attached.  I was not looking for very big signals as the the noisemon indicated roughly 30mV signal and it has some gain associated with it. So I connected to scope probes to the LL coil drive signal and looked at it on a scope with a trigger set fairly low.(10s of milivolts).  I also looked at UL just for comparison.   I was able to get the signal to trigger on some events  on LL that were not seen at as high a level on UL.  This was with the DAC both connected and disconnected with small offset (20 counts) applied and a large offset (20,000 counts) applied.  After a couple of hours of investigation I decided there were some glitches present and seemed to be from the coil driver not the DAC.  I also looked at the DAC input to the coil driver and did not see the glitches.  In the end I swapped out the coil driver.  I am not 100% certain this will fix the problem as it was difficult to verify the glitches were present at all times.

WP5452: New LSC and ASC models were made and built yesterday, and were installed today. ASC update also include one bug fix for ASC ODC (change one data type from cdsepicsout to cdsepicslong).

As for LSC, as per E1500343, 45MHz AM monitor channels was added to the science frame at 16kHz.

As for ASC, as per E1500348, input side of ASC feedback filters were added to ASC at 256Hz, and as per E1500349, ALS-C_TRX_A_LF_OUT_DQ and ALS-C_TRY_A_LF_OUT_DQ (both 2k) were removed.

After the installation, in chans/daq directory, LSC and ASC science frame channels were checked.

$ grep -B 1 "^acquire=3" H1LSC.ini|grep DQ

[H1:IMC-F_OUT_DQ]
[H1:IMC-I_OUT_DQ]
[H1:IMC-L_OUT_DQ]
[H1:IMC-REFL_DC_OUT_DQ]
[H1:IMC-TRANS_OUT_DQ]
[H1:LSC-ASAIR_B_RF90_I_ERR_DQ]
[H1:LSC-MCL_IN1_DQ]
[H1:LSC-MCL_OUT_DQ]
[H1:LSC-MICH_IN1_DQ]
[H1:LSC-MICH_OUT_DQ]
[H1:LSC-MOD_RF45_AM_AC_OUT_DQ]
[H1:LSC-ODC_CHANNEL_OUT_DQ]
[H1:LSC-POPAIR_B_RF18_I_ERR_DQ]
[H1:LSC-POPAIR_B_RF90_I_ERR_DQ]
[H1:LSC-POP_A_LF_OUT_DQ]
[H1:LSC-POP_A_RF45_I_ERR_DQ]
[H1:LSC-POP_A_RF45_Q_ERR_DQ]
[H1:LSC-POP_A_RF9_I_ERR_DQ]
[H1:LSC-POP_A_RF9_Q_ERR_DQ]
[H1:LSC-PRCL_IN1_DQ]
[H1:LSC-PRCL_OUT_DQ]
[H1:LSC-REFL_A_LF_OUT_DQ]
[H1:LSC-REFL_A_RF45_I_ERR_DQ]
[H1:LSC-REFL_A_RF45_Q_ERR_DQ]
[H1:LSC-REFL_A_RF9_I_ERR_DQ]
[H1:LSC-REFL_A_RF9_Q_ERR_DQ]
[H1:LSC-REFL_SERVO_ERR_OUT_DQ]
[H1:LSC-REFL_SERVO_SLOW_OUT_DQ]
[H1:LSC-SRCL_IN1_DQ]
[H1:LSC-SRCL_OUT_DQ]

$ grep -B 1 "^acquire=3" H1ASC.ini|grep DQ

[H1:ASC-AS_A_DC_PIT_OUT_DQ]
[H1:ASC-AS_A_DC_SUM_OUT_DQ]
[H1:ASC-AS_A_DC_YAW_OUT_DQ]
[H1:ASC-AS_A_RF36_I_PIT_OUT_DQ]
[H1:ASC-AS_A_RF36_I_YAW_OUT_DQ]
[H1:ASC-AS_A_RF36_Q_PIT_OUT_DQ]
[H1:ASC-AS_A_RF36_Q_YAW_OUT_DQ]
[H1:ASC-AS_A_RF45_I_PIT_OUT_DQ]
[H1:ASC-AS_A_RF45_I_YAW_OUT_DQ]
[H1:ASC-AS_A_RF45_Q_PIT_OUT_DQ]
[H1:ASC-AS_A_RF45_Q_YAW_OUT_DQ]
[H1:ASC-AS_B_DC_PIT_OUT_DQ]
[H1:ASC-AS_B_DC_SUM_OUT_DQ]
[H1:ASC-AS_B_DC_YAW_OUT_DQ]
[H1:ASC-AS_B_RF36_I_PIT_OUT_DQ]
[H1:ASC-AS_B_RF36_I_YAW_OUT_DQ]
[H1:ASC-AS_B_RF36_Q_PIT_OUT_DQ]
[H1:ASC-AS_B_RF36_Q_YAW_OUT_DQ]
[H1:ASC-AS_B_RF45_I_PIT_OUT_DQ]
[H1:ASC-AS_B_RF45_I_YAW_OUT_DQ]
[H1:ASC-AS_B_RF45_Q_PIT_OUT_DQ]
[H1:ASC-AS_B_RF45_Q_YAW_OUT_DQ]
[H1:ASC-AS_C_PIT_OUT_DQ]
[H1:ASC-AS_C_SUM_OUT_DQ]
[H1:ASC-AS_C_YAW_OUT_DQ]
[H1:ASC-CHARD_P_IN1_DQ]
[H1:ASC-CHARD_P_OUT_DQ]
[H1:ASC-CHARD_Y_IN1_DQ]
[H1:ASC-CHARD_Y_OUT_DQ]
[H1:ASC-CSOFT_P_IN1_DQ]
[H1:ASC-CSOFT_P_OUT_DQ]
[H1:ASC-CSOFT_Y_IN1_DQ]
[H1:ASC-CSOFT_Y_OUT_DQ]
[H1:ASC-DC1_P_IN1_DQ]
[H1:ASC-DC1_P_OUT_DQ]
[H1:ASC-DC1_Y_IN1_DQ]
[H1:ASC-DC1_Y_OUT_DQ]
[H1:ASC-DC2_P_IN1_DQ]
[H1:ASC-DC2_P_OUT_DQ]
[H1:ASC-DC2_Y_IN1_DQ]
[H1:ASC-DC2_Y_OUT_DQ]
[H1:ASC-DC3_P_IN1_DQ]
[H1:ASC-DC3_P_OUT_DQ]
[H1:ASC-DC3_Y_IN1_DQ]
[H1:ASC-DC3_Y_OUT_DQ]
[H1:ASC-DC4_P_IN1_DQ]
[H1:ASC-DC4_P_OUT_DQ]
[H1:ASC-DC4_Y_IN1_DQ]
[H1:ASC-DC4_Y_OUT_DQ]
[H1:ASC-DC5_P_IN1_DQ]
[H1:ASC-DC5_P_OUT_DQ]
[H1:ASC-DC5_Y_IN1_DQ]
[H1:ASC-DC5_Y_OUT_DQ]
[H1:ASC-DHARD_P_IN1_DQ]
[H1:ASC-DHARD_P_OUT_DQ]
[H1:ASC-DHARD_Y_IN1_DQ]
[H1:ASC-DHARD_Y_OUT_DQ]
[H1:ASC-DSOFT_P_IN1_DQ]
[H1:ASC-DSOFT_P_OUT_DQ]
[H1:ASC-DSOFT_Y_IN1_DQ]
[H1:ASC-DSOFT_Y_OUT_DQ]
[H1:ASC-INP1_P_IN1_DQ]
[H1:ASC-INP1_P_OUT_DQ]
[H1:ASC-INP1_Y_IN1_DQ]
[H1:ASC-INP1_Y_OUT_DQ]
[H1:ASC-INP2_P_IN1_DQ]
[H1:ASC-INP2_P_OUT_DQ]
[H1:ASC-INP2_Y_IN1_DQ]
[H1:ASC-INP2_Y_OUT_DQ]
[H1:ASC-MICH_P_IN1_DQ]
[H1:ASC-MICH_P_OUT_DQ]
[H1:ASC-MICH_Y_IN1_DQ]
[H1:ASC-MICH_Y_OUT_DQ]
[H1:ASC-ODC_CHANNEL_OUT_DQ]
[H1:ASC-OMC_A_PIT_OUT_DQ]
[H1:ASC-OMC_A_SUM_OUT_DQ]
[H1:ASC-OMC_A_YAW_OUT_DQ]
[H1:ASC-OMC_B_PIT_OUT_DQ]
[H1:ASC-OMC_B_SUM_OUT_DQ]
[H1:ASC-OMC_B_YAW_OUT_DQ]
[H1:ASC-POP_A_PIT_OUT_DQ]
[H1:ASC-POP_A_SUM_OUT_DQ]
[H1:ASC-POP_A_YAW_OUT_DQ]
[H1:ASC-POP_B_PIT_OUT_DQ]
[H1:ASC-POP_B_SUM_OUT_DQ]
[H1:ASC-POP_B_YAW_OUT_DQ]
[H1:ASC-POP_X_RF_I_PIT_OUT_DQ]
[H1:ASC-POP_X_RF_I_YAW_OUT_DQ]
[H1:ASC-POP_X_RF_Q_PIT_OUT_DQ]
[H1:ASC-POP_X_RF_Q_YAW_OUT_DQ]
[H1:ASC-PRC1_P_IN1_DQ]
[H1:ASC-PRC1_P_OUT_DQ]
[H1:ASC-PRC1_Y_IN1_DQ]
[H1:ASC-PRC1_Y_OUT_DQ]
[H1:ASC-PRC2_P_IN1_DQ]
[H1:ASC-PRC2_P_OUT_DQ]
[H1:ASC-PRC2_Y_IN1_DQ]
[H1:ASC-PRC2_Y_OUT_DQ]
[H1:ASC-REFL_A_DC_PIT_OUT_DQ]
[H1:ASC-REFL_A_DC_SUM_OUT_DQ]
[H1:ASC-REFL_A_DC_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF45_I_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF45_I_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF45_Q_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF45_Q_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF9_I_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF9_I_YAW_OUT_DQ]
[H1:ASC-REFL_A_RF9_Q_PIT_OUT_DQ]
[H1:ASC-REFL_A_RF9_Q_YAW_OUT_DQ]
[H1:ASC-REFL_B_DC_PIT_OUT_DQ]
[H1:ASC-REFL_B_DC_SUM_OUT_DQ]
[H1:ASC-REFL_B_DC_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF45_I_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF45_I_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF45_Q_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF45_Q_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF9_I_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF9_I_YAW_OUT_DQ]
[H1:ASC-REFL_B_RF9_Q_PIT_OUT_DQ]
[H1:ASC-REFL_B_RF9_Q_YAW_OUT_DQ]
[H1:ASC-SRC1_P_IN1_DQ]
[H1:ASC-SRC1_P_OUT_DQ]
[H1:ASC-SRC1_Y_IN1_DQ]
[H1:ASC-SRC1_Y_OUT_DQ]
[H1:ASC-SRC2_P_IN1_DQ]
[H1:ASC-SRC2_P_OUT_DQ]
[H1:ASC-SRC2_Y_IN1_DQ]
[H1:ASC-SRC2_Y_OUT_DQ]
 

Filiberto, Elli 

The ITM HWS weren't working properly after installing the filter box last week (alog 20626).   Power goes from the HWS breakout box through the filter module to the HWS cameras.  The voltage drop across the filter put the voltage at the cameras below their operating range.  (There is 14V at breakout box output, 10.8V after the filter.  Operating voltage of the camera is 12-15V.  13.3V reaches camera with no filter installed.)  We have taken the filter out and reverted to the previous HWS configuration.  We will rethink the choice of filter.

The new SYS_DIAG infrastructure for the Guardian diagnostic nodes has been installed.  The new infrastructure allows for multiple diagnostic nodes with different names.

The old SYS_DIAG node was re-written to use the new infrastructure, and was renamed as DIAG_MAIN:

$USERAPPS/sys/h1/guardian/DIAG_MAIN.py

The old SYS_DIAG node was destroyed, and DIAG_MAIN was created and started.  DIAG_MAIN is now running and appears to be executing all tests normally.

A DAQ restart is required to pull in the new DIAG_MAIN channels.

Usage of SYS_DIAG for diagnostic guardian nodes

The main infrastructure for SYS_DIAG is encoded in the SYS_DIAG module:

$USERAPPS/sys/common/guardian/SYS_DIAG.py

DO NOT MODIFY THE SYS_DIAG MODULE.  This module defines common infrastructure for loading and running the tests.

To create a new diagnostic node, define a new module: $USERAPPS/sys//guardian/DIAG_.  This module should import everything from SYS_DIAG, and define all diagnostic tests as follows:

from SYS_DIAG import *

@SYSDIAG.register
def TEST_SOMETHING()
    """One-line description of test.

    Other info about test.

    """
   if some_condition():
        yield "message to be reported to operator"

Note the "@SYSDIAG.register" decorator above the TEST_SOMETHING function.  That's what registers the function as a diagnostic test that gets run in the RUN_TESTS state (see below).  The module can define as many functions as you like, but only those registered will be run as diagnostic tests.

Also note that the function "yields" a diagnostic message.  Each test can define as many conditions as you like, and for each failing condition, yield a diagnostic message as show above.  The yielded message will be displayed as a NOTIFICATION by the DIAG guardian node, tagged with the test from whence it came.

The DIAG module only needs to define tests as described above, and should not define any GuardState classes. The states are imported from SYS_DIAG: INIT that just lists the registered tests, and RUN_TESTS which runs all tests tagged with the @SYSDIAG.register decorator.

Tests can be defined in separate modules and imported as needed in the usual way.

(Keita writing)
Nothing changed for green, it's hard to tell if anything happened for IR as there's no light right now.

Analog signal coming out of the interface looked OK in that no high frequency oscillation was observed in green as well as IR. Ditto for Analog signal coming out of whitening.

I didn't pull the QPD interface chassis out, as one of the clean room legs is blocking the front side of the ISC field rack and I couldn't move the clean room on my own.

Here is a quick script to get the svn numbers of the TwinCAT PLCs:

#!/bin/csh
ezcaread ${1}:SYS-ETHERCAT_C1PLC1_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_C1PLC2_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_C1PLC3_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_X1PLC1_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_X1PLC2_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_X1PLC3_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_Y1PLC1_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_Y1PLC2_SVNREVISION
ezcaread ${1}:SYS-ETHERCAT_Y1PLC3_SVNREVISION

and here are the results:

H1:SYS-ETHERCAT_C1PLC1_SVNREVISION = 2406
H1:SYS-ETHERCAT_C1PLC2_SVNREVISION = 2402
H1:SYS-ETHERCAT_C1PLC3_SVNREVISION = 2402
H1:SYS-ETHERCAT_X1PLC1_SVNREVISION = 2357
H1:SYS-ETHERCAT_X1PLC2_SVNREVISION = 2357
H1:SYS-ETHERCAT_X1PLC3_SVNREVISION = 2357
H1:SYS-ETHERCAT_Y1PLC1_SVNREVISION = 2357
H1:SYS-ETHERCAT_Y1PLC2_SVNREVISION = 2325
H1:SYS-ETHERCAT_Y1PLC3_SVNREVISION = 2325

These are the most recent versions for the respective PLCs.

At 0728 pdt the IFO dropped lock.

Prior to that the SDF was green except for the OMC, SUSETMY, and SUSPRM.  Some CALC stuff too but I'll not worry about that.

The PRM diffs are from the LL Coil driver changes and the OMC & SUSETMY diffs are captured below.  These system should not have to be restarted today.

As of 0905,

The STS2-A is installed.

Richard has been and continues to work on the PRM coils.

Keita is working the EndX QPD.

Phil is working the ETMX UIM Breaker and

Ellie is working on the TCS HWS Camera Power Supply.

ALL TIMES IN UTC

Summary:

H1 remained locked for ~6+ hours. LLO went down at 12:39UTC according to Doug Lormand’s aLog. There was ~4hrs coincidental lock with LLO. Wind and Seismic still calm. ETMY glitches at 10:12, 10:24, 11:12, 11:55, 13:19, 13:35, 14:27. Handing off to Jeff B.

LOCK LOG:

• 8:49  Locked @ NOMINAL_LOW_NOISE

  • 9:03 ADD_WHITENING to OMC 66 Mpc

    • clearing some SDF diffs for data taking while LLO is up

    • Evan doing some light commissioning work before data collecting mode

• 9:37  OIB and OOM switched to Undisturbed/Observing

• 14:27 Lockloss- Possibly PRAXXAIR delivery

• Sequence started again but maintenance will eventually take it down at 15:00UTC

ALL TIMES IN UTC

Upon Arrival: IFO not locked. Calibration going on. Wind calm. Seismic calm

Summary:

Wind and seismic remain calm. IFO has been locked and in Undisturbed/Observing Mode since 9:37UTC @ ~66Mpc. A few ETMY glitches, nothing major. Everything looks good so far.

• 7:00 Kissel, Kiwamu, Evan on site doing their thing(s)

• 10:13 ETMY Saturation. Dropped range to 4Mpc

• 10:24 ETMY Saturation. Dropped range to 48Mpc

• 11:12 ETMY Saturation. Dropped range to 48Mpc

Ed, Evan

The OIB and OOM were set to Undisturbed/Observing ,66Mpc, at 9:37UTC. Evan cleared SDF of everything that he knew of. Some remaining SDF diffs are as follows: SUSPRM(known issues), OMC, SUSETMY.

This is just a quick report about one of today's calibration activities.

I made a measurement to help understanding the OMC DCPD response by having intensity modulated light on OMC in a simple configuration. At the beginning I was going to use ISS PD arrays to calibration the intensity noise, but it turned out that they were not accurate enough to get 1 % accuracy due to mismatched dewhitening filters in the digital system. Seeking for alternatives, I finally ended up with ASC AS_C. Data and analysis to come later.

J. Kissel, P. Thomas, E. Hall, K. Izumi, E. Merilh

We had ceased calibration activities around 10p this evening, and have been trying to recover the interometer since. A few things that have bitten us that none of our current systems could have caught:
(1) Kiwamu had turned ON the frequency servo for the ALS DIFF PLL while tuning ALS DIFF actuation function measurements. This was left ON when he was finished, so it took Patrick and Kiwamu a bit off tail chasing witht the VCO frequency slider when the ALS DIFF guardian couldn't find IR. 
(2) Once we got past ALS DIFF onto to DRMI locking, we immediately saw the normalized ASAIR B RF 90 purple trace on the PRMIsb.stp was high. Kiwamu found that this was a result of new large dark offsets on the electornics. We suspect this has to do with the "transparent" work done in the HAM6 Racks today (see LHo aLOG 20838).
(3) An initial alignment was needed (no surprise).
(4) Something went wrong with what Evan suspects to be offloading just before the CARM offset reduction. This reduced the recycling gains by a third, and made the signals very noisey. Somehow the lock acquisition sequence and CARM reduction managed to survive, and eventually the SRC and SRC cavity signals came back to normal. Huh... we'll see it if repeats. 
(5) Power normalization didn't work during power up. Guardian skipped to COIL_DRIVERS without completing INCREASE_POWER.
(6) repeat of (4) ... ifo makes it again though. Kiwamu later identifies it as a problem with SRM alignment
(7) Fail at the ETMY transition. Found it due to ETMY being still in its high-voltage setting, left over from the later work that Kiwamu was doing with ALS DIFF.
(8) Fail at PRM low-noise noise transition (3 coils is less stable to coil driver switching than 4 coils). Hopefully this'll be fixed tomorrow.
(9) This SRM alignment business is getting better, without us doing anything...
(10) repeat of (5), Evan now suspects an ISC_LOCK guardian change he made yesterday...

I'm running out of steam for this. I'll leave it to others to document the rest of the recovery, 'cause this is gunna be just as hard if not harder tomorrow... 
#premaintenanceday

J. Kissel, K. Izumi, C. Cahillane

Evan and Kiwmau wished to get a better answer than my supremely bold claim of being able to ALS DIFF VCO's pole and zero to 1% and 1 [deg] (LHO aLOG 20542). As such, they remeasured the ALS DIFF PLL OLGTF with no boosts, as had been done before, but this time with the PLL Common gain reduced to -32 dB([V/V]) instead of the nominal 26 dB([V/V]). In this way, they reduce the overall loop suppression, in hopes to alleaviate the non-linear distortion we had been plagued by before. The message -- they were right. The new OLGTF, with all other parameters the same, shows that the "nominal" z:p = 40:1.6 [Hz] pair fits the data better than my previously claimed z:p = 40:1.05 [Hz].

However, naturally, there is still confusion. The new *magntiude* residual shows what looks to be a descrepant pole-zero pair around 100 to 500 Hz, but there's no such affect in the phase. Recall that the frequency dependence in the model is simple -- a pole a DC for the phase-frequency descriminator, the z:p pair for the VCO, a time delay, and a single 450 kHz pole. Nothing around 100 - 500 Hz. What do we suspect? More non-linearity. Great. 

More to think on. We'll measure the PLL controller in the -32dB gain setting tomorrow to make sure it's what we hope -- non-linearity at the negative-edge of the gain setting for this box, that we can just measure and divide out.

Calibration work until 05:15 UTC.

UTC (Pacific)
23:00 (16:00) Start of shift. Calibration is ongoing.
00:04 (17:04) Kiwamu and Craig C. to LVEA ISC rack to measure ALS DIFF PLL open loop gain
00:11 (17:11) Corner station main entry proximity reader door forced
00:18 (17:18) end X dust monitor invalid alarm
00:37 (17:37) Daniel to CER to check RF distribution
00:43 (17:43) Daniel back
00:45 (17:45) Sheila and Daniel to LVEA to look at racks, changed ASC-AS_B_RF45 sensor cabling (alog 20838)
01:05 (18:05) Sheila and Daniel back
01:30 (18:30) Kiwamu and Craig C. back
02:50 (19:50) Momentary HEPI EX Pressure alarm

The ETMX L1 UIM coil driver tripped off 3 times. Kiwamu reset it each time.

05:15 (22:15) Kiwamu done calibration work, I started attempting to lock.

Spent about 20 minutes trying to find IR diff by hand. It turned out the frequency servo for the ALS DIFF VCO had been left on and was driving the frequency to H1:ALS-C_DIFF_VCO_FREQUENCY. Kiwamu turned it off.

06:13 (23:13) Evan to CER to check for possible left over issues from the changes Daniel and Sheila made.
06:19 (23:19) Evan back, no issues found

Kiwamu has the IFO and is attempting to bring it back.

J. Kissel, P. Thomas

Given that we've had so many examples of rocker switch death this evening (see LHO aLOG 20839), I was able to identify that my new(ish) warning message about this failure mode on the MEDM overview screen (see LHO aLOG 20281) had a bug. The MEDM logic was watching L2 for all three stages, L2, L1, and M0. I've committed the bug-fix to the SVN such that LLO can receive its benefits.

J. Kissel, S. Dwyer, E. Hall

As I was about to characterizing the ETMY coil drivers (i.e. the UIM and PUM), I noticed that they were in their highest noise state. After conversations with Sheila and Evan, we (re)agreed that the PUMs should be run in their lowest noise state, which is with  LP ON and ACQ OFF, or State 3 from T1100507. As such, we've switched all QUADs to this state, and confirmed that ISC_LOCK guardian will ensure this to be true in the future (again). That guardian has been reloaded.

The reason they had been put back into high range (and taken out of the guardian) was that the range was needed to better damp the QUAD roll modes after they had been severely rung up in the Christmas Episode in early August. 

From a calibration stand point, this will affect the DARM calibration by a small amount, but I had not started characterizing the ETMY PUM drivers before I got started, and I'm now full aware of it, so it's affect will be fully understood and expected. As such, we're OK with this configuration change. Further, we'll all be happy with the little bit extra range we get from it (Evan will post an aLOG making a noise statement later)!

Jim, Evan

We have grown tired of the glitching in the PRM M3 LL OSEM, so here is a script that ramps it off in full lock. It gets rid of the glitching and allows us to recover 60ish Mpc range.

Also included is a screenshot of the usual Euler/OSEM matrix for PRM.