Looking at timeseries graphs for photodiaodes from two separate locks (7-28-15 8:00:00 UTC for two hours AND 8-1-15 10:15:00 UTC for two hours) I've tightened up all the saturation thresholds in the LSC ODC.

The firefox web browser has been updated to version (39.0.3) for security reasons.  If you have a firefox browser open, you should restart it.

The "fast" h1susex computer has been replaced with the original h1susex computer.  This should eliminate the IOP model timing glitches that would occasionally cause IPC errors across other models.

I started this node a month or so ago to test and to see what configuration we might use it in. With the code freeze upon us, it seems as though this will not be used and is just sitting in the background. No need for that. I did the following:

>> guardctrl destroy ISI_ETMX_ST1_CONF

I then double checked that the node was no longer in the node list.

J. Kissel, D. Tuyenbayev

We've installed a few new writeable EPICs records for the following channels, in order to circumvent the issues we've found with EPICs / FE computational precision problems in the new CAL-CS front-end model infrastructure to accommodate tracking of slow, time-dependent parameters in the IFO calibration in the GDS calibration pipeline. See LHO aLOG 20386 for ID of precision bugs.

Attached are screenshots of the changed library parts, which have now been committed to the userapps svn.

In summary, 
(1) the channel names which should be used have not changed, they're now merely EPICs writeable records as opposed to calculated records. The calculated channels still exist (they've not been removed so we can continue to debug ), but have been renamed.

Channels that are now EPICS Writes                       Former Calc Record's New Name                                 Term in T1500377
$(IFO):CAL-CS_TDEP_REF_INVA_CLGRATIO_TST_$(REAL,IMAG)    $(IFO):CAL-CS_TDEP_CALC_INVA_CLGRATIO_TST_$(REAL,IMAG)        - (1 / A_{0}^{tst})|f_tst *  C_{0} / (1 + G_{0})|f_pcal * (1 + G_{0}) / C_{0}|f_tst     
                                                                                                                       This is the constant part of Eq. 9
$(IFO):CAL-CS_TDEP_REF_CLGRATIO_CTRL_$(REAL,IMAG)        $(IFO):CAL-CS_TDEP_CALC_CLGRATIO_CTRL_$(REAL,IMAG)            C_{0} / (1 + G_{0})|f_pcal * (1 + G_{0}) / C_{0} |f_ctrl
                                                                                                                       This is the constant part of Eq. 11
$(IFO):CAL-CS_TDEP_REF_A_USUM_INV_$(REAL,IMAG)           $(IFO):CAL-CS_TDEP_CALC_A_USUM_INV_$(REAL,IMAG)               1 / A_{0}^{pu}
                                                                                                                       This is the constant part of Eq. 12

For the remaining list of channels needed (none of whom's names have changed) see LHO aLOG 20361.

In consequential changes:
(2) I've fixed the mistake in the flags to compute $(IFO):CAL-CS_TDEP_CALC_INVA_CLGRATIO_TST_$(REAL,IMAG), even though we now won't use this channel. (see ID of this bug in LHO aLOG 20365)
(3) I've also added the missing minus sign to the comments.


For LLO to update, one only needs to update the following common library parts:
/opt/rtcds/userapps/release/cal/common/models/
CAL_CS_MASTER.mdl
CAL_GAMMA_CALC_MASTER.mdl
and recompile. MEDM screen updates will come later today.

J. Kissel

Attached is a screenshot of the values installed on Sunday will be lost because of SDF precision issues.

Both HPCL-2231 optoisolators were replaced.

After re-inserting the servo card, I checked that the laser was on and that the NPRO noise eater was still happy.  The laser MEDM screen indicated both.  When I pulled up the ISS screen the power on the photodiodes was zero.  I checked the PMC screen and it indicated that there was no laser power incident on the PMC.  A closer look at the laser screen indicated that the low power shutter in the laser had closed.  Resetting the external shutter request from the laser MEDM screen restored the light.

After locking the ISS servo, everything seems okay as far as the laser goes.

J. Kissel, B. Weaver, C. Vorvick

- ISC_LOCK guardian to DOWN, set in PAUSED
- IMC_LOCK set to OFFLINE
- ALIGN_IFO set to PAUSED

- SEI_ETMY to OFFLINE and SUS_ETMX to SAFE for prepping SUS EX reversion to slow front end computer.

-Cleared ETMX SDF warnings about new violin mode damping configuration, initialized new RMSLP and L3_CAL_LINE channels and set to monitored

- Accepted ETMY BIAS sign flip and corresponding DRIVEALIGN gain sign flip.

- Accepted ALS Y PZT2 YAW MISALIGN BIAS to be 11200 (from 11500)

- Reverted SUS BS LOCK L OFFSET (and TRAMP) to 0 and 10 (respectively) from 10000 and 30 (respectively).

- Accepted SUS ITMY violin mode damping settings, and that the output is OFF for ITMY OLDAMP P.

- Accepted SUS ITMX optical lever Y damping GAIN to be 0.0 (from -111). 

NOTE: ITM Optical Lever P Damping is totally inconsistent. We've found that ITMX P is ON (gain and output switch) yet ITMY Y is on OFF (gain -300 output is OFF).
We tested TJ's modifcations to the SUS guardian by exercising the SAFE state, which turns OFF the outputs. By design, the outputs should be turned back ON in the DAMPED state. Will speak with TJ.

While looking at a few big glitches, I noticed that many have a curious post-glitch feature around 300Hz.  The post-glitch ring seems to match the periscope frequencies we usually see noise at... could this be a hint as to the source of some of our glitches?  Maybe this was fixed last night, maybe not.

Alignment and locking issues aloged earlier.

IFO did make it to low noise about 6 hours ago.

Relocking about 45 minutes had trouble with Guardian that we hadn't had any issues with all night - not sure why.  At JeffK's suggestions I commented out the offending section of code.  Code is attached as a screenshot.

IFO handed off to Mantenance activities.

----------Maintanance Activities ------

7:00 - Richard and Ken, roof

7:37 - Bubba and Chris, LVEA fan maintenance

7:41 - PeterK, ISS

7:42 - Richard and Ken, Electronic's Room

7:59 - Richard/Ken DONE

7:59 - PeterK Done

Cheryl, Evan

The 0.43 Hz pitch instability strikes again. I had to turn up the dHard pitch gain from 10 to 20 in order to prevent a runaway. Back into the guardian it goes!

It takes tens of minutes to ring up, and even after tweaking loops, it never exactly rings down (the fuzz in the attached striptool is almost all from this 0.43 Hz feature).

(Evan, Kiwamu. Daniel)

We installed the 45.5MHz EOM driver in the PSL room. It is located below the PSL table and replaces the RF amplifier at the same location. The drive power has been adjusted to be the same as before at 23.2dBm. This is now controlled remotly through medm.

Calibration:

• For the front panel BNC of Mon1 and Mon2 the calibration is 105V/V relative the output signal. The DAQ readbacks RF45_ERR and RF45_AC have an additional gain of 20.
• The DC output at the fron panels have a gain of 0.578V/V relative to the output signal. The DAQ readback RF45_DC has an additonal gain of 2.
• To caluclate the RF AM in dBc one has to divide the AC/ERR values by the DC value.

The RF phase shift was compensated by cable length to within 1°.

The RF phase has a slightl dependence on the RF level. At 45.5MHz with 23dBm output level the phase advance of the entire chassis is 121°. The relative phase shift at 17dBm is +4.8° (advance), +8° at 13dBm, and 12.8° at 5dBm—or –0.8°/dBm.

The attached plot shows the RF AM RIN in dBc/Hz for both the in-loop and out-of-loop sensor (double-sided). At 100Hz with 23dBm output we are achieving-170dBc/Hz.

• quadmodelproduction-rev7652_ssmake4pv2eMB5f_fiber-rev3601_h1etmx-rev7641_released-2015-08-07.mat
• quadmodelproduction-rev7652_ssmake4pv2eMB5f_fiber-rev3601_h1etmy-rev7640_released-2015-08-07.mat