I have measured the transfer functions of the newly installed whitening chassis (alog 28010, ECR:E1600192, SN:S1101627) for the OMC DCPDs. I used LISO for fitting the data.

[1st stage for DCPD A]

Best parameter estimates:
pole0:f =  18.6776675365k +- 10.45 (0.0559%)
pole1:f =  14.3409807014k +- 6.292 (0.0439%)
pole2:f =  98.9444053052k +- 32.86 (0.0332%)
pole3:f =  10.3243596197 +- 359.4u (0.00348%)
zero0:f =  985.3423393170m +- 79.51u (0.00807%)
factor =  998.8350760502m +- 67.01u (0.00671%)

Final chi^2=0.00252952

[2nd stage for DCPD B]

Best parameter estimates:
pole0:f =  18.5698573085k +- 14.71 (0.0792%)
pole1:f =  14.6043378758k +- 9.31 (0.0637%)
pole2:f =  100.4496012696k +- 43.14 (0.0429%) > MAX
pole3:f =  10.0731025960 +- 470.5u (0.00467%)
zero0:f =  961.4535554217m +- 104.7u (0.0109%)
factor =  997.7425128879m +- 90.38u (0.00906%)

Final chi^2=0.00454374

[Small notes]

I have also measured the same transfer functions with a 4 times smaller excitation signal in order to check some sort of saturation-induced measurement error. I did not quantitatively look at these data, but plotting them on top of the above data showed excellent agreement (to my eyes).

[SVN info]

All the data, scripts and figures are checked into SVN at:

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Scripts/OMCDCPDs

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Measurements/OMCDCPDs/2016-06-30

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O2/H1/Results/OMCDCPDs

Attached are the past 7 day pitch, yaw and sum trends for all active H1 Optical Levers

TITLE: 06/30 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Lock Aquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY: First half of the day was dedicated to maintenance and measurments by several parties.  Afterwards, locking has been fairly successful up to INCREASE_POWER several times, and we made it to NLN finally.
LOG:

15:33 Kiwamu and Evan G. to HAM6 OMC chassis measurements

16:00 Fil to LVEA getting serial #'s for vacuum racks and chassis

16:02 King Soft on site

16:18 Patrick updating MX vacuum Beckhoff

16:22 Richard to reinstall OMC AA chassis

16:25 Hugh to EX

16:36 Richard done

17:06 Fil done

17:08 Patrick done

17:09 Cheryl to IOT2L taking pics of beam dump

17:23 Kiwamu done, Cheryl done, Hugh done

17:39 Kyle back

17:59 DAQ restart

19:19 Richard to EX, EY, and MY

20:08 Richard back

20:37 reset ALS Y VCO

Between yesterday and today, Gerardo and I successfully bonded the ears to core optic mass ETM15, destined for LLO for post-O1 eventual replacement. 

Ear s/n 195 bonded to S3 flat of mass June 29, 2016

Ear s/n 196 bonded to S4 flat of mass June 30, 2016

The first ear (s/n 195) has a series of bubbles along it's edge, but the surface area of these do not add up to more than the allowed amount as per E1000277, so it passes, see pix attached.

The second ear (s/n 196) has no bubbles and is nice full bond. 

The CP5 level control differential pressure signal from the pump is noisy so I have set the "Smoothing" to 0.999

I would like to leave it this way overnight but if problems arise the smoothing can be reset to 0.0

C. Cahillane

After taking a close look at the Hanford actuation measurements, with the addition of the January 7th measurements, it became very obvious that the actuation measurements were never compensated for time dependence.
I am not sure if the same is true at Livingston.  I will be investigating shortly.  If so, it could be a major reason why LLO actuation uncertainty is so large... Previously, I used only calibration-week actuation measurements for LHO, meaning the kappas could not have varied too crazily in that period.  But LLO had measurements more spread throughout the run.

This is obviously quite important for our uncertainty budget... The systematic errors will be affected on the order of the kappas that were never applied, so about 3% for TST and 2% for PUM and UIM.  The uncertainties will be smaller since removing time-dependence will cluster our measurements better.

I have posted a plot similar to the one from aLOG 27290 showing the actuation magnitude variances and covariances between each day's measurements.  
Blue is the measurements without the kappas applied.  Red is with the kappas applied.

Comparing to aLOG 27290, we see UIM and PUM variances stay about the same, which makes sense because kappa_pu is not that volatile.
But TST variance goes from 2.5% to 2.0%!

I have added the following scripts to the calibration repository:

analyze_pcal_20150928_kappa_corr
H1PCALparams_20150826_kappa_corr
H1PCALparams_20150828_kappa_corr
H1PCALparams_20150829_kappa_corr
H1PCALparams_20160107_kappa_corr

These allow me to correct the LHO time dependence in our actuation functions.

Added 200ml water to the crystal chiller.

B. Weaver, J. Kissel

Betsy grabbed this week's charge measurements on both end station test masses; the first after the what-will-no-be-regular bias sign flipping that started last week. There is a significant jump in actuation strength in all quadrants to ETMX and ETMY, but this is the first data point of many, and the point is to see how the scatter of actuation strength changes over time. So, though this first point may be confusing, we should ride it out to see if the long term effect is as desired. 

We'll flip the bias back upon the next lock loss.

Attached are the usual trend plots. Thanks to Betsy for running and processing the measurements from today!

Following Tuesday's install of a new Solaris QFS-NFS gateway machine, the DAQ had became more unstable with both frame writers restarting regularly. Today we reverted the system back to its old configuration to see if we can get back to a more stable system for the long weekend and ER9.

h1ldasgw0 NFS was reconfigured to export ldasg-h1-frames to both nds machines

h1ldasgw1 NFS was reconfigured to export cds-h1-frames to both nds machines

h1nds0 processes were stopped, umounted h1ldasgw2 then mounted ldas-h1-frames from h1ldasgw0

h1nds1 processes were stopped, umounted h1ldasgw2 then mounted cds-h1-frames from h1ldasgw1

The new h0vacmx.ini file was incorporated into H0EDCU_VAC.ini.

11:06PDT full DAQ restart.

This was a messy restart, h1psl0 DAQ data was held in a bad state as long as mx_stream was running on h1asc0. This was tracked primarily to monit not running on h1asc0 (it was shutdown while the special asc awgtpman was installed this week). Our /etc/start_streamers.sh file was out of date, it should not attempt to start the mx_stream process itself, rather it should kill the process and allow monit to start it. This file was modified on h1boot accordingly. We are still unsure why we do not see two copies if mx_stream on the FECs that have had start_streamers.sh manually ran. I checked and all FECs now have one, correctly configured mx_stream process. This raised the question of if the data loading is balanced between the two data concentrator ports, as the port allocation is purely on the order of the models in the rtsystab file.

J. Kissel, J. Betzwieser

We've recently installed CDS oscillator parts which have their phase synchronized to GPS time 0, in order to progress with the O2 calibration line scheme of PCAL cancelling suspension lines (see LHO aLOG 27733). However, when I turned the lines on the other day (see LHO aLOG 27981), I'd installed the new oscillator / cal line frequency (a copy of LLO's frequency) in the Pitch Oscillator of the optical lever lockins. These lockins still use the former unsynchronized oscillators. As such, I've swapped the calibration line frequencies such that the old frequency (35.9 Hz) is now run by the Pitch Optical lever lockin, H1:SUS-ETMY_LKIN_P_OSC (so that it's just as unsynchronized as it was during O1) and the new frequency (35.3 Hz) is run by the now synchronized cal line oscillator that *used* to run the O1 test mass calibration line, H1:SUS-ETMY_L3_CAL_LINE.

These settings have been captured in the SAFE and down.snaps of the SDF system.

WP 5972

The Beckhoff vacuum controls code on h0vacmx has been updated to use the same PI controller as h0vacey (alog 27886).

I have put both CP5 and CP6 on PID control.

The channels in the DAQ and autoBurt request snapshots still need to be updated.

A little late, but on Tuesday the BSC-ISI models were updated to the newest version. This was also mentioned in Dave Barkers Tuesday summary. The master parts. several MEDMs, common guardian and chamber specific guardian code was all updated. Seems to work. Changes are described in detail in T1600216.

We also added a science frame channel for the end station BRS/STS super-sensor. This channel is a 256 channel and is called ISI-GND_SENSCOR_ETMX/Y_SUPER_X/Y_OUT_DQ. This channel is the tilt subtracted STS channel for each endstation in the beam line.

Sheila, Carl, Stefen

With the ISS 2nd loop patch (see alog 28076) we successfully reached the "lowish" nosie state again. The spectrum loked the same as in alog 27990.
.

Start: Jun 30 2016 05:01:36 UTC
Loss:Jun 30 2016 05:05:22 UTC

The loss was presumably cause by a 18.04kHz mode ringing up rapidly. Carl will add more details on that.

Jeff, Kiwamu, Stefan

We had trouble engaging the ISS 2nd loop at 40W. The core issue is that the digitized signal (H1:PSL-ISS_SECONDLOOP_SIGNAL_OUTPUT) swings rail to rail without the loop, making it difficult to properly pre-set the offset adjuster (H1:PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA).
As a result, when engaged, the ISS 1st loop tended to swing into saturation.

I patched the Guardian as follows:
- Instead of trying to rely on a calculation for the offset adjuster (H1:PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA), I hard-coded it to 0.987 V, which is where it likes to sit at 40W. (THis is obviously not a long-term solution.)
- As soon as the servo comes on, I ramp H1:PSL-ISS_SECONDLOOP_REF_SIGNAL_SERVO_GAIN to zero, clear the history, and re-engage it on the diffreation power.

This seemed to engage the 2nd loop without excessive transient - back to full locking.

PS: I might have already mentioned this: but the ISS SHOULD BE AC COUPLED!

Code:

In PREPARE_ISS:

        # read current servo signal value. If it is too far from the operating point, correct the offset.
        #second_loop_out = cdu.avg(1, 'PSL-ISS_SECONDLOOP_SIGNAL_OUT16')
        #if abs(second_loop_out) > 1.0:
        #    # measure current input PD value
        #    # Sets the ref. signal value to bring it to close to the operating point
        #    pd_avg = cdu.avg(1, 'PSL-ISS_SECONDLOOP_PD_14_SUM_INMON')
        #    ezca['PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA'] = round(0.5*((pd_avg*2.29*.0006103515625)+0.101), 6)
        #    time.sleep(5)

        # above section commented out - instead command the value that worked  (Stefan Ballmer 20160629 for 40W)
        ezca['PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA']=-0.9826934814453125
 

In CLOSE_ISS, once the loop is closed:

            # the loop is successfully locked, ramp off the loop (Stefan Ballmer 20160629 for 40W)
            ezca['PSL-ISS_SECONDLOOP_REF_SIGNAL_SERVO_GAIN'] = 0

and a little later:

            # clear and ramp on the loop (Stefan Ballmer 20160629 for 40W)
            ezca['PSL-ISS_SECONDLOOP_REF_SIGNAL_SERVO_RSET'] = 2
            time.sleep(0.1)
            ezca['PSL-ISS_SECONDLOOP_REF_SIGNAL_SERVO_GAIN'] = 1
 

biggest = prm pitch changing by 2.5urad

close second = im4 pitch changing by 1,15urad

plot and chart of top 16 optics/DOFs attached

(Richard M, Fil C, Ed M, Daniel S)

ECR E1600192.

Split Whitening Chassis S/N S1101627:

• On the interface chassis remove R7, R8, R9 and R10, R17 and R18 (disconnects in-vac cables and Z-switch).
• On the interface chassis jumper 220 pF capacitors on J3 between pins 1-3, 9-11, 2-4 and 10-12 (adds one pole of high pass at 7.2 kHz).
• On the 2nd whitening board remove C37, C38 and C39 (removes both poles of low pass).

AA Chassis S/N S1102788 & S1202201:

• On channels 15 and 16 remove C1, C6 and C9 (two poles of 10 kHz low pass).
• On channels 15 and 16 remove C7 (one pole of 10 kHz low pass).
• The twin-T notch was left in. It is fairly wide and attenuates ~17 dB at 50 kHz.

The attached plots show the transfer functions of

1. whitening chassis: OMC DCPD_A: same as before
2. whitening chassis: OMC PI DCPD_A: modified
3. whitening chassis: OMC DCPD_B: same as before
4. whitening chassis: OMC PI DCPD_B: modified
5. AA chassis: channel 15
6. AA chassis: channel 16