It seems that since the last power glitches, the DBB is back to operational status... hmmmm. That is to say, before the power glitches it was unusable due to the mysterious tripping of the (dbb) interlock when trying to open the beam path into the box. In the past week I've been trying to get good measurements. This was a abit daunting due to the ISS 3rd loop work that was breaking the IMC lock consistently and yanking on the LASER frequency. Below is what I could muster over the course of a couple of days. ISS_RPN will come later as Peter is currently in the enclosure and working on it.

Comments:

RPN - 35W path looks suspiciously good accross the spectrum by a factor af a few...hmmm?   200W path looks tyo be below requirement from 2Hz to ~25Hz and then above to about a factor of a few through high(er) frequencies.

FRQ -  35W path is quite noisy at low freq (below 15Hz). Other than that the rest looks good save for the usual resonances. 200W path looks ok across the spectrum except for the usual resonances.

PNT - 35W path pointing looks pretty good. 200W path shows seperation  of the 1x/y and 2x/y  by a factor of a couple.

MSC - 35W path shows TEM 20 +02 an order of magnitude higer than reference. 200W path shows TEM 02+02 mode higher by a factor of a couple.

Morning Meeting:

• SEI - all good
• SUS - Betsy to LVEA for about an hour
• CDS/Electronics - waiting for changes in PSL
• PSL - Peter is putting a ND filter in front of the ISS inner loop
• Commissioners left a alog 
• VAC - Chandra - take visitor to EX around 9:30 for les than an hour
• VAC - visiting CP3 this morning
• VAC - Kyle at EX this morning for about 20
• VAC - JimW - will modify to restart automatically

FRS:  reviewed

Currently:  no locking with Peter in the PSL modifying the ISS beam path

Sheila, Kiwamu, Evan, Matt, Lisa, Jenne, Corey

Tonight the locking has been stable enough that we were able to try several low noise steps.  We ended up with a range of about 20 Mpc, and were locked for 3.5 hours.

• Earlier this afternoon Matt, Evan, Kiwamu, and reduced the ISS loop gain by 4dB, to reduce the gain peaking visible in Peter King's plots (29725)
• We've used the guardian states LOW_NOISE_ASC (for reducing arm loop bandwidths, which Jenne checked out earlier), COIL DRIVERS (after a few additional bug fixes), LOWNOISE_ESD_ETMY, and ran the A2L script for the test masses.
• Kiwamu noticed that the AS WFS DC have been close to saturation at 50 Watts.  This might have been part of the reason the OMC alignment was railing in some locks.  To help with this he reduced the modulation depth for 45 MHz by 3dB, and moved the REDUCE_MODULATION_DEPTH state to before the power up. The OMC drives are not large right now.
• Kiwamu reduce the DARM gain by a factor of 2 (in guardian at DC readout) because there was gain peaking.
• We reduced CSOFT PIT back to 0.2 for the digital gain, and CSOFT Y from 3 to 2.
• We have not used the third loop tonight.  We accidentally powered up with it off, and that has been fine.  With the 3rd loop off we don't have the low frequency ISS oscillations that caused us to DC couple the ISS last night.
• I also made a few changes in the IMC LOCK guardian. After talking with Keita, we realized that if the 1st loop saturates and turns off, the second loop would not be turned off.  The guardian is now written to handle this, but I don't think this has happened tonight so we haven't tested it. 
• We measured the SRCL and MICH loops (screenshots and data attached). SRCL still has 6dB of gain peaking, the MICH loop would have been unstable with the boost that gets engages in the state NOISE_TUNNINGS, so we increased the gain by 3dB to a digital gain of 2. 
• When need to move SRM ASC loops off the dither before we reduce the gain of SRCL.  We were sucsesfull for PIT, using 4*ASA36I-ASB36I, and a gain of 3 (FM1 off).  We picked this matrix about 3 hours into a lock, after the thermal state had stabilized.  The next lock we tried it shortly after powering up, and it seemed fine.  We haven't added this to the guardian but probably could.  We tried a similar procedure for YAW, but about 2 hours into the second lock we opened the loop because SRM was slowly becoming misalinged. 
• We tried MICH and SRCL FF, MICH worked fine with the old settings, and improved the noise around 100Hz, we are now limited by SRCL at 50 Hz and below.  We tried SRCL FF, but it made things unstable so we need to check on it tomorow.
• Evan updated the calibration. It was off by 20%. 
• For our last lock, the violin mode damping was somehow off the whoel 3 hours.  Rung up violin modes ended up breaking the lock.  If tomorow's operator has a chance to lock at 2Watts and damp violins using the instructions on the wiki, that would be great.

Kiwamu, Lisa

We monitored the intensity noise coupling to DARM over more than 2 hours during one of the long lock tonight by injecting noise in the ISS outerloop excitation point.

Labels correspond to local times (September 16).

The coupling changes significantly over time. Kiwamu tried to reduce the CO2 ITMX power to see if we could maintain a low coupling, but that didn't really work.

After a couple of hours we could clearly see the coupling getting significantly worse (red trace). 

Tonight there was a flurry of activity with H1.  There were issues with locking at the beginning of the shift, but it got better....we had a range reminiscent of H1 during S6:  19Mpc!  :)  Slowly but surely, we're gettin' there.

Locking Notes:

At the beginning of the shift, had issues locking ALS.  This was traced down to the wrong polarizations.  

• Adjusted polarazitaion for Y-arm PLL.  Also had VCO guardian error message, so it was RESET.
• Also had same issue with X-arm, so did both of above.
• Before getting to DC_READOUT, Guardian had an issue with ENGAGE_SRC_ASC.  Jamie & Jenne troubleshooted the issue and finally got guardian going again.
• While at DC Readout:  Chris & crew(s) ran some measurements.
• Had a nice 2.5hr long high power lock.  Terra chased some PIs.  Kiwamu & Sheila eventually took us to nearly 20Mpc, and then we lost lock.
• While reacquiring, the ETMx was off a bit, but eventually got it back.
• DRMI looked off in yaw & dead.  PRMI looked ugly, too.  So, we misaligned PRM & adjusted the BS (in yaw).  This got us partly there.  Then Sheila had me restore the PRM & then tweak it such that we had decent PRMI flashes.  Eventually locked up and had no issues getting up to 50W.  (Oh, we did need to employ the BS excitation trick that Sheila alogged about on Tues night.
• Kiwamu, Sheila, & Matt will now tinker with a 50W H1....whoops, it just broke lock...time to sneak out!  :)

FOM Note on Nuc5:

Cheryl mentioned this was booted during the day, and then it died & no DMT Viewer/DTT came up on their own.  I rebooted nuc5 and conversely to last night, the DMT seismic trends looked fine & current.

Since the lock was so stable, I could not avoid measuring the DARM open loop for calibration purpose tonight. I have tuned the excitation amplitudes of the 4-1200 Hz DARM OLTF template because some frequency points had too high excitation causing saturation on ETMY DACs. Also for completeness, I have taken a Pcal sweep as well. I will analyze the data later.

The dtt files can be found at:

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/DARMOLGTFs/2016-09-15_H1_DARM_OLGTF_4to1200Hz.xml

/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Measurements/PCAL/2016-09-15_H1_PCAL2DARMTF_4to1200Hz.xml

Matt, Terra

Status of PI after TCS work and ring heater change transient (for at least the first three hours of 50 W lock):

1. Successfully damping all modes (with some caveats; see #4,5.)
2. Actively damping ITMX 15520, ITMY 14980 and 15515, ETMX 15541 and 15008, ETMY 15542, 15009, 18041 and 18059 Hz. Of these, the 18kHz and 15kHz only ring up during the transient. 
3. All modes are now getting damped using the PLL. One motivation for this is avoiding saturations. I'm fairly certain that the mysterious sign flips and illogical behavior when increasing gain in the past have been due to something saturating along the loop, usually resulting in ringing up the mode. 
4. 15009 Hz (MODE 26) is still a bit confusing: it rings up twice during the transient period and appears to require a sign flip to damp each time. I'm not yet convinced this isn't just a byproduct of the transient though (we flip a gain sign and see a slow downturn on the same timescale as the transient passing, attributing the turn around to the wrong reason?). 
5. After ~2 hours, 15541/2 Hz (MODE 17/25) ring up. While we have the actuation strength to damp these, these modes are ~.5 Hz apart, so the PLL is having trouble staying on the right one and I had to do lots of actively jumping back and forth between controls. We are going to try sending both drive signals to both optics, etc. 

3 hours into the lock and all PI's are stable. Leaving PI control with Matt for the night. 

Kiwamu I, Jeff K, Darkhan T,

Overview

Today we looked at the calibration line coherence values calculated in the front end. We discovered that in the front-end model with the currently used averaging parameters the coherence value is updated once every 10 seconds (first 1.5 minutes in Fig. 1).

We propose modifying the averaging code to improve coherence calculation and avoid potential aliasing (see details).

Details

A front-end model that calculates coherence uses N data points taken every S_cycles computational cycles to calculate cross-spectral density of the signals. S_cycles is controlled by an EPICS record $(IFO):CAL-CS_TDEP_COH_STRIDE (or simply STRIDE): S_cycles = FE_RATE * STRIDE. There are drawbacks associated with this approach:

• New coherence value will appear every STRIDE seconds;
• Skipping data points will produce aliasing.

We can deal with the first problem listed above by reducing STRIDE. On Fig. 1 we show coherence values for N = 10 and STRIDE set to 10, 5, 1, 1/16 and again 1. Notice that this test was done when the IFO was not locked, thus we do not expect a coherence of ~1. When STRIDE is set to 1/16, we can see that the number of averages must be increased in order to include actual fluctuations in the signals (in the last 2.5 minutes N = 120).

Fig. 1

Several minutes later IFO locked (at t = -5 in Fig. 2) and the coherence became ~0.8. After we set the line amplitude to its nominal value we got coherence of ~1.

Fig. 2

Next, to avoid aliasing we should use all data points (equivalent to setting STRIDE = 1/FE_RATE in the current code) and increase N accordingly. Thus to integrate over 10 seconds and avoid aliasing the current code will require O(FE_RATE * 10) = O(160k) operations per cycle and a buffer for 160k values, which is unnecessary expensive.

A following minor modification of the averaging code can solve the issue described above. Instead of adding every S_cycles'th data point into the averaging buffer, we could insert an average of S_cycles values. E.g. buffer_and_average() can be modified as follows:

...

    static int mini_sum = 0;

...

    //Increment cycle count
    mini_sum += data;
    cycle_counter++;
    if (cycle_counter >= cycles_between_data) {
        buffer[current_pointer] = mini_sum / ((double) cycles_between_data);
        current_pointer++;
        cycle_counter = 0;
        mini_sum = 0;
    }

...

With this modification and N = 160, STRIDE = 1/16 (S_cycles = 1024), the coherence will be calculated with 10 second integration and will require O(160) operations per cycle, and the coherence value will be updated every 1/16 of a second.

Neither PIT or YAW trends were near/approaching +/-10urads, so it looks fine.  Nothing obvious on the SUM trend either.

This CLOSES FAMIS #4693.

[Jenne, Sheila, Matt]

On our way to trying for some low noise, we went through the CoilDrivers state.  But, somehow there was some buggy code in there that it was only trying to switch the UL coil of all the optics ('PRM', 'PR2', 'SRM', 'SR2', 'BS', 'ETMY', 'ETMX', 'ITMY', 'ITMX') over and over again, and never going to any other coils.  After a few minutes of this, we lost lock.  I don't know that I can prove that that's why we lost it, but we lost lock on this state yesterday also, and certainly having 3 coils one way, and one coil continually going between states 1 and 3 isn't helping keep us locked. Code fixed, we'll try it again next lock.

Jeff K, Darkhan T,

Overview

CAL-CS synchronized oscillator settings for cal. line coherence calculations were lost after the recent power glitch (LHO alog 29592). The settings were lost because after populating the settings (see LHO alog 28995) on August 10, not all of the channels were monitored by SDF_OVERVIEW.

Today we restored the coherence calculation settings and accepted the changes in SDF_OVERVIEW.

Details

The power glitch did not cause losses of the H1CALCS filters, so running set_coherence_h1.py (that populates filter modules) was not necessary this time (only changes names of the "1/f^2" filters to ":1,1", same as in PCAL models).

However filter module switches needed to be turned on (those previously weren't monitored by SDF_OVERIVEW). Some of the synchronized oscillator settings were also lost during the power glitch, they have been fixed now.

Today we updated coherence calculation settings for the following lines:

•   35.9 Hz - ESD, SUS_LINE1
•   36.7 Hz - PCALY_LINE1
•   37.3 Hz - DARM_LINE1
•  331.9 Hz - PCALY_LINE2
• 1083.7 Hz - PCALY_LINE3

All channels have been added to the list of monitored channels and the values have been accepted in SDF_OVERVIEW tables (safe.snap and OBSERVE.snap).

Note: IFO was not locked when the screenshots were taken.

Terra, Dave:

new h1susprocpi model was installed. This adds 64x2k chans to the science frame. The 'place holder' zeroed data were removed at the same time. DAQ was restarted.

related to 29648,

The output from HWSY doesn't look reasonable. This is something we knew, but this time a surprising thing was that, if I interpret the data as it is, the self heating on ITMY introduced negative lensing rather than positive lensing. This does not make sense. See the second attachment below. The first attachment is the HWS signal for ITMX with its prediction from the TCS simulator for comparison.

Jeff K, Chris Whittle

Following on aLOG 28363 (initial proposal) and 29250 (installation), we measured the open loop gain of the IMC loop (without full CARM) with the AG4395A, both with and without the daughter board 200 kHz pole. The GPIB is still connected to the AG4395A by the Common Mode Board.

TFAG4395A_15-09-2016_140247.txt has the transfer function without the daughter board, TFAG4395A_15-09-2016_140553.txt with the daughter board. The attached plots were generated with daughter_tf_plots.py.

See the attached plots of open loop gain, loop suppression and closed loop gain. Takeaways:

• features around 800 kHz suppressed by 200 kHz pole
• we still have 48° of phase margin compared to our previous 63°
• unity gain frequency has moved from 75kHz to 64kHz
• gain margin has increased from 2.7 dB to 4.6 dB
• maximum gain peaking in the loop suppression has been reduced from 4 to 2.5
• closed loop gain is relatively unchanged below 40 kHz and should not affect CARM loop

Also note some variation in the OLG at about 200 kHz compared to the previous measurement.

Sheila, Matt, Lisa

The ISS has been oscillating a couple of times when reaching 50W in the last two locks. Sheila fixed that by turning off the AC coupling.

We leave the IFO locked at 50W with the ISS AC coupling off, at Sep 15, 9.45UTC. It has been locked for about 20 minutes, powers are stable, no PIs.

Matt updated SDF with the latest PI settings.

We just noted that the PSL NOISE EATER is oscillating -- so please fix that in the morning.

I have spent some time trying to understand the behavior of the CARM loop in full lock.

First, I have reduced the loop to the following block diagram:

P is the IFO, K is the IMC, and G is the FSS. F and M represent the fast and slow common-mode feedback paths, and A represents the IMC PDH board and the VCO. A fuller accounting of these blocks is given in the sections below.

The OLTF of CARM is then given by