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
 

After talking with Rana and Evan during the NSF review, I made some independent estimates of the thermal noise that
could come from the composite SRM which had a measured resonance frequency of 3.34KHz with a Q of 150. I get the same
thermal noise displacement spectra of the mirror surface as Evan in log 27488,27490,and 27490. Tend to favor the viscous case
as Peek is a thermoplastic as is Nylon which was measured to have a viscous spectrum. The model is a shear motion of Peek 8-32 screws 
clamping the 2 inch diameter 1 inch thick mirror into the metal carrier. The motion is a displacement of the mirror allowed by shearing
the 8-32 bolts in and out of the plane of the carrier - longitudinal modulation of the light beam. Thermo elastic damping is much too small
to explain the low Q. The time constant for thermal diffusion in the Peek screws is about 10 seconds. The thermo elastic delta is about 10^-2,
so that loss tangent phi varies as 1/f with a value of 5x 10^-8 at 3.4kHz and about 2 x 10-6 at 100Hz. My guess unfortunately is the
SRM is not responsible for the excess low frequency noise we are seeing. I think Evan and Rana had come to the same conclusion. 

The OMC would not lock as we entered DC_READOUT_TRANSITION, and the DARM spectrum had risen around 100Hz. Sheila tracked it down to H1:LSC-ARM_INPUT_MTRX_RAMPING_1_3 having a gain of 20 and not 8. She investigated further and realized that the matrix was not being loaded beore the actual value was in place, something that a sleep of 0.1s can cure. With her help. I added in these short sleeps or just loaded later.

J. Kissel

Several lock losses were caused by DC coupled ISS loops today, so in my desperation to make things better, I modified the PSL ISS 2ND Loop MEDM screen to include all the relevant PSL AOM Diffracted Power information on the same screen (formerly only available on the 1st loop ISS screen). Also, to facilitate the turn on dance, I've decreased the default increment on the slider used to tune the analog reference signal (H1:PSL-ISS_SECONDLOOP_REF_SIGNAL_ANA) and increased the precision which the reference signal value is displayed.

The updated screen has been committed to the user apps repo here:
/opt/rtcds/userapps/release/psl/common/medm/ISS/PSL_CUST_SECONDLOOP.adl

Sheila, Haocun

We designed some new filters for the low bandwith CHARD Yaw at 40W.

We plan to lower the gain for about 6dB, which will give us a UGF at 3.5Hz and use the new filters 6 ('40W') and 7 ('ctrlHBW') to stablize the loop (blue curve in the 2nd Figure). The new cutoff filter for 40W is filter 9 ('cutoff40W') (Figure 1). The pink curve in the second curve is what we expect from the simulation.

yesterday fw0 was more stable than fw1. In the evening the new QFS-NFS server was serving fw0's files to both nds0 and nds1. I also stopped fw1 from writing science frames to see if this would improve its stability. Overnight fw0 restarted several times, meaning that fw1 needs to write its science frames again (it had not become more stable). Again we are seeing both framewriters sometimes restart around the same time, a synchronisation we had not previous seen.

The configuration for fw1 was changed to write science frames again and I waited until 4pm for it to restart itself, but fw1 went into a period of stability. At 4pm I restarted fw1 and it became very unstable. After power cycling both h1fw1 and h1ldasgw1 it is now stable.

During the day Stefan needed nds1 to link to fw1's frames to see data for a time fw0 was not running, nds1 was reconfigured and restarted.

Support: Jeff K., Jenne, Kiwamu, Peter K., Sheila

At the beginning off the shift I changed the power_sepoint in lsc_params.py from 20 to 40 and loaded it.

After a lock loss from 40 W we started having FSS and ISS issues similar to what TJ (alog 28034) and Sheila (alog 28045) had reported last night. Kiwamu was able to find and address the problem (alog 28058).

A couple of times the guardian did not appear to recognize a lock loss and thus did not take the IFO to down. I had to do so manually.

There were occasional notifications that the POP X PZT had railed and that the IMC WFS were not centered. There were also notifications that the TCSX and TCSY CO2 power was off by more that 0.05 W.

Stefan fixed a bug in the DRMI down state (alog 28053).

I ended the shift having trouble locking DRMI and handed it over to TJ to run an initial alignment.

14:58 UTC Peter to LVEA PSL racks to reset noise eater
16:08 UTC Bubba and Nicole to mid X
16:57 UTC Karen and Christina to mid X and mid Y to clean
17:02 UTC Ed to CER to reset DBB AA/AI chassis (alog 28049)
17:52 UTC Karen leaving mid Y
18:07 UTC Christina leaving mid X
18:19 UTC Ryan patching alog
21:44 UTC Kyle refilling CP3 (alog 28062)
22:03 UTC Kyle back

biggest = prm pitch changing by 2.5urad

close second = im4 pitch changing by 1,15urad

plot and chart of top 16 optics/DOFs attached

1450 - 1505 hrs. local -> To and from Y-mid 

Opened exhaust check-valve bypass, opened LLCV bypass valve 1/2 turn -> LN2 at exhaust in 50 seconds -> Restored valves to as found state.  

Next CP3 over-fill to be Friday, July 1st.  

Kiwamu, Stefan

We were trying to nail down what is responsible for the Power Recycling Gain change during power-up, so we went through the whole sequence slowly, and gave the system time to settle in each state:

All times UTC of 20160629:

- 18:54:37 / Green dot: Power-up starts from 2Watt to 10Watt
- 19:00:32 / Red dot: Power-up restarts from 10Watt to 40Watt
- 19:06:10 / Black dot: : Power-up to 40W finishes, but additional SOFT offsets remain left off.
- 19:10:15 / Blue dot: Soft offsets in yaw start ramping on over 2 minutes
- 19:12:17: Soft offsets ramp in yaw is done
- 19:15:17: Soft offsets in pit start ramping on over 3 minutes
- 19:18:19: Soft offsets ramp in yaw is done
- 19:21:20: End of undisturbed period - guardian continued
 

In particular, we now there is a significan power recycling gain improvement with a soft yaw adjustment of the x-arm. Additionally, the beam splitter cannot affect the relative alignment of x-arm and power recycling cavity. SO attached are only yaw signals from x-arm and power recycling cavity.

Conclusions:

- During the very first step in power up (green dot) there is a momentary shift in PRM yaw and IM4 yaw, but it does not continue during the additional power increase.
- During the main power increase (between red dot and black dot). There is a consiostent signature in the ETMX control, oplev and IR camera signal, sggesting that we are slightly moving the x-arm with the ASC system. THe ITMX doesn't see much of this in control signal and oplev signal (its camera is broken and not plotted). However no significant motion is visible in any of the power recycling cavity mirrors (this includes PR2, which is not plotted).
- Once we start moving the soft loops with soft offsets, ETMX, ITMX, PR3 and BS clearly respond. Interestingly, the ETMX moves to the same direction as during the power increase.

• I have defined an earthquake state in the SEI_CONF guardian. This state currently just turns off all sensor correction to the the HAM ISIs (X,Y&Z) BSC-ISIs (X&Y), BSC HEPIs (Z) and HAM1 HEPI (X,Y&Z). Following the IFO surviving a small earthquake last night, I could believe that it might work as intended, at least during an otherwise quiet ground environment (low wind, low microseism).
• The dream would be to add automation or operator notifications. Terramon being down makes this harder. When are we getting an epics variable? Otherwise, TJ and I have talked about an environment guardian.
• Chris Buchanan has a study of O1 earthquake statistics (G1600348), it would be nice to get more detail about what IFO signals were impacted by earthquakes during O1, so we know what signals to look at. IMC-F and LSC-X/Y_TIDAL_MON seem like good starting points. Chris's DCC doc includes a link to an earthquake wiki with a lot of information.

Last night at about 23:30 UTC last night, we had an earthquake arrive at LHO. I don't know where it was or how big, because Terramon has been down for a while. The peak BLRMS displacement seen by the ITMY STS in the .03-.1hz region was .28 microns. The first thing I noticed was the IMC F and LSC Y TIDAL on the Tidal StripTool were showing large ~20 second oscillations. When Sheila switched to  the "Earthquake" SEI_CONF state, these oscilations went away, even though the earthquake band ground motion continued going up. My first plot shows the SEI_CONF state ( 40 is the windy state (SC on everywhere), 17 is the earthquake state) ITMY Z .03-.1hz BLRMS displacement in nm, IMC-F and LSC-Y_TIDAL_MON. You can see that at about the time the ground motion BLRMS gets to about 100nm, the IMC and LSC TIdal starts ringing up. As soon as the sensor correction is turned off, the IMC and Tidal settle down. This lock lasted in this configuration past the earthquake, until the commissioners tried to move to a higher guardian state.

The next two images are two times later in the evening, one when the SEI_CONF was still in the earthquake mode (6/29/2016 1:10 UTC), the other after the later lockloss when the commissioners had changed back to the "Windy" SEI_CONF state (6/29/2016 2:13 UTC). IMC and Tidal don't seem to be bothered by either state. The newt four images are various spectra comparing IFO control signals at these two times. Unfortunately it looks like there was maybe another small earthquake and higher winds when the SEI_CONF was still in "earthquake". All "REF" traces are with the earthquake configuration, the live traces are with the windy configuration. I think these spectra show that for now we can be in either state, but some of the suspension length signals show lower drives with the "windy" config. Additionally, the earthquake config will probably not be okay with higher microseism, we have been sitting at about 10th percentile levels for a while now. The last plot just shows the effect of turning of the (BRS subtracted, STS based) sensor correction on the ETMY ST1 T240s. The Y blend is the same for both blue and pink traces. The subtraction at the microseism doesn't look good right now, but I think that is because of the low microseism.

DBB:

.001 files= Lo Power

,002 files = Hi Power

As expected beam pointing and mode matching in the Hi Power path remain to be addressed. 

ISS_RPN:

It looks like AOM diffraction noise is high consistent with the higher-than-usual measured diffracted power.

PDB is "in-loop" and noise is ≈ 1 oreder of magnitude higher than reference.

Pointing noise in X-axis seems to be elevated in the regions between 12Hz & 80Hz. Also, there is some Y-Axis noise between 100Hz & 850Hz.

Lisa asked me to run a BruCo scan on data from this elog entry: 27990 (June 28, 6:00 - 6:10 UTC)

The report is available at the following address:

https://ldas-jobs.ligo.caltech.edu/~gabriele.vajente/bruco_1151128817/

Instead of CAl_DELTAL I used directly the OMC_DCPD_SUM signal. The reason is that the usual calibration of CAL_DELTAL does not seem to be correct anymore.

In summary:

• All noise below ~70 Hz is dominated by alignment signals (CHARD, SRC, PRC2, PRC1, INP2). CHARD seems to be the one with largest coherence. There's also large coherence with ASC-OMC_A/B_SUM. I'm not sure if this is ok (they may be the same DCPD signals) or if those signals are sampling the beam before the OMC. In the latter case, it might indicate that the coupling of angular noise goes through some high order modes or clipping.
• However, coherence is also large with MICH / PRCL / SRCL, so it's hard to say what's going on. Are the auxiliary channels feedforward paths on?
• At higher frequencies I couldn't find much going on, except maybe a larger than usual coupling with IMC jitter, see last plot.

For future reference, to run BruCo you can follow this procedure

1. log in into one of LDAS machines, for example ldas-pcdev1.ligo-wa.caltech.edu
2. download the bruco code from the git repository https://github.com/gabrielevajente/bruco
3. read the first lines of the bruco.py script for instructions. To produce the report above I used the following command:
   ./bruco.py --ifo=H1 --channel=OMC-DCPD_SUM_OUT_DQ --gpsb=1151128817 --length=600 --outfs=4096 --naver=300 --dir=~/bruco_1151128817 --top=100 --webtop=20 --xlim=1:1000 --ylim=1e-10:1

So, I've taken the NPRO "RRO" (which is LASER speak for Resonant Relaxation Oscillation - what is that?? right?) status indicator from the PSL_LASER.adl screen and copied it to the FSS_LASER.adl screen and aptly enhanced the label to include the term "NOISE EATER" which is a term that we would more likely be familiar with. It's located in some prime real estate just South of the "Oscillation Threshold [v]" setting.  I did this at the advice of Peter King in response to the issues that have recently arisen regarding the FSS trying to re-lock after being "kicked" by a lock loss. In the usual tradition, GREEN=Good and RED=Bad. 

Marie, Sheila, Kiwamu, Lisa, Stefan

We tried a few things to improve the recycling gain tonight. We  believe that the problem is with something in our PRC.  We can see that the green power transmitted through the X arm stays stable as we power up, we think this means the optics are stable.  When we move the soft offsets to improve the recycling gain we change the X arm alignment to follow something in the vertex.

• We started with dithering IM1+IM3.  The IM1 dither was meant to test is we were clipping into the Faraday, we don't think that is happeneing because we could clearly see our dither in IM4 trans PIT and Yaw, but not in the sum. 
• We tried moving IM3 and PR2 offsets.  We saw taht IM4 trans pit moves as we power up, so we started by trying to correct this by moving IM3. We were repeatably able to improve the reycyling gain from 28 to 29 by moving IM3 by 3000 in pitch counts (we think this is calibrated in urad! Our inital starting point was 58495 on the IM3 pit slider, our best recycling gain was at 55515 urad).  This seems like too big of a move to be the real drift that we are trying to correct, and is much larger than the move needed to correct the position on IM4 trans. 
• We tried moving loop offsets in PRC2 (POPX-> PR3 loop) In pit we went +- 400 counts without seeing any real change, in yaw we saw a repeatable imprvement with a offset of +400 counts. 
• We switched off the loop, moved optics, and broke the lock. 

As TJ noted, since the computer problems earlier we are having trouble relocking the PSL after locklosses, with noise eater, PMC and FSS and ISS problems.  It seems like trying to lock the FSS causes the noise eater to oscillate again after it has been reset. 

The OMC DCPDs have proven to be useful for monitoring the test mass acoustic modes around 15 kHz, but there is a lot of low-pass filtering in the readout chain that render them less useful for monitoring higher frequency acoustic modes. This is now being changed with modifications to the electronics that will provide separate, faster channels for PI monitoring:

• In-vacuum pre-amp: this has 2 poles at 16 kHz (these will remain, since in HAM6)
• Whitening board: 1 pole at 14 kHz; 1 pole at 18 kHz. These will be eliminated in the new chain.
• Anti-alias filter: 3rd order Butterworth low-pass at 10 kHz. These will be eliminated in the new chain.

The attached plot shows the magnitude response of the low-pass filtering in the previous case, and with the poles removed from the whitening and AA channels. It is no wonder that no PI modes have been seen above the 15-16 kHz grouping, as there is 40 dB of relative attenuation already at 25 kHz.

I also attach a 1kHz - 10 MHz transfer function of the in-vacuum DCPD readout that Koji measured at Caltech:

https://nodus.ligo.caltech.edu:8081/OMC_Lab/235

Jenne, Lisa, Stefan,

Still running at 40W, for 2h.

Tried to damp some PIs and go to low-noise.

- We successfully damped 15009Hz (ETMY) and 15542Hz (ETMY) (damp settings picture attached.)

- 15541Hz (ETMX) was ringing up.So we tried switching to ETMY and transition the ETMX coil driver to low noise.

- We successfully switch the coil drivers, but...

- We switched to ETMY, low noise, held lock for a while, but saturated the ETMY ESD with 20Hz noise from the ASC, as well as a 532.77Hz line, that we don't know the origin off. (PI?) (picture)

===================================

Also, we realized that DTT is a bit too smart: The 64kHz channel H1:OMC-PI_DCPD_64KHZ_A_DQ can in principle look at PIs above the Nyquest through aliasing. However, since DTT only alows you to select a freqency about 10% below the Nyquist frequency, there is an effecive dead band where DTT cannot see PIs between ~29500Hz and ~36036Hz. The MATLAB script below produces a spectrum up to the Nyquist. Indeed, we found an elevated mode at 30018.3Hz, although it was not quite saturating.

MATLAB code to get spectrum up to Nyquist frequency:

addpath /ligo/svncommon/NbSVN/aligonoisebudget/trunk/Externals/SimulinkNb/Utils/
gwd = GWData();
gwd.make_kerberos_ready;
gwd.site_info(2).port = 31200;
gwd.site_info(2).server = 'nds.ligo-wa.caltech.edu';
H1.channels = {'H1:OMC-PI_DCPD_64KHZ_A_DQ'};
time_fetch = tconvert('26 Jun 2016 01:15:00');
[data, t, ~] = gwd.fetch(time_fetch, 1000, H1.channels);
Fs=4*16384;
pwelch(data,[],[],[],Fs)