[Jenne, Gabriele]

We might be limited by intensity noise that we can't sense with the ISS first loop diodes. Now that we got your attention, see the details below. The most interesting plot is the last one.

This morning we checked whether the ISS second loop was open. The output switch of the second loop board (H1:PSL-ISS_SECONDLOOP_OUTPUT_SWITCH_MON) was indeed open, but the input switch on the first loop board was closed (H1:PSL-ISS_SECONDLOOP_CLOSED). So we decided to open it.

We were surprised to see that the sensitivity got significantly worse when the switch was open. See below (H1:PSL-ISS_SECONDLOOP_CLOSED = 1 means switch closed, first loop closed but second loop still open at the output of the second loop board, H1:PSL-ISS_SECONDLOOP_CLOSED = 0 means switch open at the input of the first loop board, but the first loop is still closed)

At the same time we see that the first loop signals (PDA is out-of-loop and PDB is in-loop) also changed. The in-loop signal did not show any difference, while the out-of-loop signal noise floor increased by about a factor of ten. See below (top panel is again DARM, bottom panel is the in-loop signal (dashed) and the out-of-loop signal (solid).

So it looks like the noise in DARM increased at almost all frequencies by about the same factor as the noise seen by the ISS first loop (out-of-loop) PDA sensor.

However, coherence is very poor between DARM and PDA/PDB, even when the noise is high.

It's however clear that the noise increase in DARM is related to toggling the ISS input switch (we tried many times).

Spectrograms of DARM and PDA (out-of-loop signal) in the quiet and noisy periods show that the noise is highly non stationary, so maybe this is enough to explain the lack of coherence.

So the next question is how close is the intensity noise (as measured by the ISS first loop out-of-loop signal) to limiting us in normal condition?

To answer, we computed the ratio of the DARM spectrum over the PDA spectrum while in the noisy state, and use this ratio to project the quiet state PDA spectrum into DARM. We restricted the projection to only those points where the DARM noise got higher by more than a factor of two when in the noisy state. The result, shown below, seems to indicate that we are likely limited by "intensity" noise measured by the ISS first loop sensor, which couples in a non-stationary or non-linear way, so we don't see coherence.

Next steps:

• understand why the noise in the first loop signals got worse with that switch open (maybe a dangling connection?)
• understand if the noise at that input is limiting the ISS first loop performance even when the ISS second loop switch is closed
• check if other PSL signals got worse (frequency noise?)
• do some intensity noise injections, to make sure we see the same with "real" intensity noise

In breif, I measured, fitted and retuned the MICH and SRCL feedforward. The results are good, but the first SRCL FF filter I tries showed the same instability reported in 44740, probably due to the "large" gain below 10 Hz that's neede to have a good fit down to 10 Hz. So I restricted the fit above 30 Hz, and got a new filter, which should have good performance in the 30 to 100 Hz region. I haven't tested it yet, since the IFO unlocked.

Measurement templates are attached, since I don't have permissions to copy them in /opt/rtcds/userapps/release/lsc/h1

The plot below shows the DARM spectrum without any feedforward (red), with MICH only (blue) and woth MICH+SRCL (black).

The configuration that gives the good MICH filter and the (tentative) good SRCL filter ois shown in the last attached screenshot.

The h1seih23 and h1seih45 computers had their dackill glitches again.  This is what killed the several hour lock at 22W that was left overnight.  I requested the HAM 2,3,4,5 HEPI and ISI guardians to "ready", then ssh'ed to the computers and ran the startWorld script, as in alog 44672 and alog 44695.

Also, just in case some settings get missed, I took the SEI_CONF guardian to WINDY_NOBRSXY and then back to WINDY_NOBRSX, to force any sensor correction settings to be put back.  The SEI_CONF medm screen made it look like everything was in its expected state, and all of the lights (except end X due to BRSX issues) were green, but since this was a problem last week, hopefully this ensures all sensor correction is properly turned on.

Rana, Craig

Today we calibrated the CARM servo board spectrum into Hz.

First, we drove a strong line in the MC2 suspensions at 71.1 Hz, and measured the transfer function from REFL_SERVO_ERR_OUT_DQ (we assume counts from the common mode servo board error signal) to IMC_F_OUT_DQ (calibrated into kHz).
We got 3.1e-7 kHz/cts, or 0.5 Hz/V, at 71.1 Hz, assuming an ADC of 2^16 cts / 40 V. 
Assuming a CARM pole of 0.5 Hz, this gives a CARM optical gain at DC = 284 V/Hz.

We've also measured the CARM OLG, giving a UGF of 10 kHz.  
By extrapolating the CARM OLG with a 1/f^2 line, we can approximately calibrate CARM into Hz of frequency noise incident on the interferometer:


where 
 is the CARM OLG, 
 is the common mode boost (z=4kHz,p=40Hz), 
 is the REFL9 sensing chain,
 is the CARM plant, and 
 is the common mode board test1 point.

The calibrated spectrum is pretty flat, quickly reaching an RMS of 2 Hz at high frequencies.  This RMS frequency noise seems too high to me, and the spectrum doesn't have the shape I expected.

Sheila, Georgia, Craig, Hang, Rana

We have a calibrated DARM spectrum that we can compare to the noise during O2, and it looks like our noise from 40-100 Hz is very similar to the noise floor after the Montana earthquake last July (ignore the large injection just above 70 Hz).  The first attached screenshot shows the noise before and after the earthquake and now for a comparison. The second screenshot shows the coherence of DARM with ASC and LSC signals, none of which are high above 35 Hz.  

Done tonight:

• We removed the changes to the ITMX ESD filtering from the guardian (that doesn't matter for feedforward). 
• We changed the guardian to engage the new MICH FF which Gabriele made earlier (44767), and the SRCL FF that Craig designed last night (44744).  We haven't tried Gabriele's SRCL FF yet.  
• We also removed the ISS second loop from the guardian because it was causing locklosses. 
• Started noise budget injections: IMC PZT P+Y, CHARD P+Y, DHARD P+Y, MICH P +Y (very small compared to O2), LSC MICH +SRCL
• Started a SRCL excitation for Hang at midnight (7 UTC) exactly, we turned it off at 7:19 UTC.
• At 7:20 UTC we are leaving the interferometer undisturbed.  

Craig, Rana

We checked the RF levels at the REFL9 demod board RF MON (-23 dB coupled output) with 50 Ohm terminated oscope.

So to convert this trace back into the input of the demod board we multiply by ~14.

From the scope trace, we can see that the fastest slew is ~140 mV / 10 ns (10 V/us). This is not a problem for the FET mixers on the board.

The slew rate limit of the RFPD output amp is 450 V/us, so we are from hitting the hard slew rate limit. The question that remains is how close can we be before there is some non-negligible downconversion.

Thinking back to the iLIGO days, we used to have trouble with the MAX4107 (450 V/us slew rate) when it was putting out ~150 mV-pk at 2*25 MHz (~30 V/us).

So I think if the LMH6642 distorts at the same fraction of slew rate as the 4107, we are close to seeing this excess noise. To be sure, we'll need to do a more careful and systematic test with some spare RFPD and demod electronics. Tricky.

[Georgia, Patrick]

We ran the usual charge measurements today - the quadrant-by-quadrant effective bias voltage measurements on both ETMX and ETMY, and the additional measurements of combinations of the four parameters on ETMX (measured by driving combinations of the signal and bias electrodes).

The ETMY effective bias trend remains consistent with ~50 V offsets on the UL quadrant (coupling to pitch), the UR quadrant (coupling to yaw), and the LL quadrant (both pitch and yaw). The first attachment shows this over the last few months.

The ETMX effective bias is trending back towards zero after the bias was switched on September 11. The second screen shot shows the quadrant-by-quadrant measurement for ETMX.

This trend is also seen in the four-parameter measurement which makes sense. The third attachment shows the alpha and gamma parameters in the first column, these are associated with the ESD actuation strength and should not change over time. The second column is the beta+beta2 parameters, as measured by driving the bias and measuring the response on the op lev, and by driving the signal electrodes and measuring the response on the op lev. This measurement should be immune to space-charge polarisation which we assume is symmetric. The bias-driven beta+beta2 seems to have taken a jump recently (though I don't want to jump to conclusions based on two data points), while the longitudinal signal drive did not. This is strange. The third column shows beta-beta2 and the Veff, which are sensitive to space charge polarisation and consistent with the quadrant-by-quadrant measurements.

Note when running these measurements - it can be hard to tell if the HV is on or off. Even with the HV off a small signal is seen in the ESDAMON channels whin driving the quadrants. These channels are calibrated into volts and should see a large excitation from the charge measurements (100s of volts, exact numbers depend on the measurement). Up until today the ETMY L3 ESDAMON and LVESDAMON filters were turned off, leaving those channels in counts, not volts. I have switched those filters on now.

J. Kissel, S. Dwyer, E. Goetz, L. Sun

Lilli Shiela and I were able to successfully update the calibration of DELTAL_EXTERNAL today. The residual systematic error is no worse that 15 % and 7 degrees (likely due to a slightly wrong coupled cavity pole, and slightly wrong actuator strengths, and slightly wrong sensing vs actuation relative delay). Recall that this calibration is informed by quick, limited frequency band, measurements, so I'm happy that the results are even this good.

The big gotcha that took us so long: the MEDM screens (recently upgraded by Jeff) do not correctly reflect what's happening in the front-end in each actuator replica's ESD path. Namely, with the replica ESD linearization bypassed, the replica BIAS bank has no influence on the ESD path (this was not Jeff's impression of how it should be, thus he didn't update the MEDM screen that way). Thus, when we had installed the correct replica bias -- and it just happened to be negative -- it did not affect the replica signal path. Thus -- unless we change the model in the future to be more reflective of real life -- we need to apply the bias voltage *sign* and only the sign somewhere in the replica control path. Combined with several other sign flips between the O2 configuration of interferometer control and the current interferometer control (a different arm, a different output matrix, a different bias sign), this was very difficult to find (which is why we needed Sheila's new set of eyes to help figure out the problem).

I've accepted all of the settings in the CAL-CS model as they stand now, so we should have this good(ish) calibration permanently.

I've confirmed the updated calibration and it's systematic error with a PCAL to DARM sweep and an DARM Open Loop Gain, which can be found here:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/O3/H1/Measurements/FullIFOSensingTFs/
    2018-10-23_H1DARM_OLGTF_23to800Hz_10min.xml
    2018-10-23_H1_PCAL2DARM_TF_23to800Hz_2min.xml
they've been exported for future processing by Evan and Lilli. These measurements and their exports have been committed to the above location in the repo.

The attached 2 screenshots show two things:
 - The PCAL to DELTAL_EXTERNAL transfer function (left two panels of first attachment), which quantifies the residual systematic error in the calibration
 - A calibrated (to the accuracy quantified above) amplitude spectral density of DELTAL EXTERNAL.

There are plenty of qualifiers on the noise of this ASD -- it's in the middle of tonight's round of commissioning. The biggest know problem is that they're actively working on tuning the LSC feed-forward, so there is no MICH, PRCL or SRCL feed-forward on during this ASD. Please focus on the fact that the PCAL lines (in green X's) at 35 and 330 Hz are matching the LIVE DELTAL_EXTERNAL (in red).

I determined that something was amis after having replaced BSC10's AIP pump body this morning and, so, swapped the controller out as well.  Something still isn't working - I don't believe the pump current data even though the absolute value is plausible.  I'll continue to investigate at the next opportunity.  Until then, I am leaving the AIP energized but have shut down the pump cart and local turbo.   

Terry Daniel

Added a Thorlabs FLH1064-8, a FLH532-4 and a FLH532-4 in front of the DCPDs which monitor the IR laser light, the SHG green light and the green light launched into the fiber, respectively. This blocks the ambient light and makes us insensitive to the table lights.

TITLE: 10/23 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: None
SHIFT SUMMARY:  Maintenance until ~2pm local time due to extended PSL work. 
LOG:  See attached .txt file.

FYI -
per ongoing work in SEI, I've started committing the changes for the BSC-ISI improved sensor correction to userapps.
It is OK to svn up your userapps. Don't be alarmed if you'll see a bunch of new screens, c-code, and models and some new library parts models in the ISI part of the userapps.

I'm updating the various instructions now on how to install all this stuff. (T1800414)
An SVN up should not have any impact on what is running at the sites,
but,
the overview screen for the BSC-ISI now contains 2 links to the sensor correction, the original one, which should still work in exactly the same way,
and
a new one, which is mostly non-functional until you replace the isi2stagemaster.mdl in the various models with the new isi2stagemaster_SC_2018.mdl library part.
Detailed instruction on making real changes are in progress.
-Brian

Krishna drove over from UW today, and with Gerardo's help, we vented the can and replaced the adjuster for BRSX. We were done with that and closed up by about 1 pm, when we started pumping with a turbo cart. Krishna then rebalanced to where we think is a good spot, but won't know until the pumping is done and the box is closed up. About an hour ago we started the ion pump, still waiting for the current on that to get low enough to turn off the turbo. Once that is done, we'll need to keep an eye on where the beam drifts to see if I need to go back in and rebalance.

Attached is an image of the adjuster and flange we removed. The new one has a 1/4-20 thread with more engagement, a lock washer and a lock nut to hold it together.

Sheila, Hang, Craig, Georgia, Danny, Thomas

• Hang lowered the gain in MICH P to avoid the possibility that it was unstable at 1.1Hz 44739.  We later realized that the locklosses we've been having where MICH P rings up at 1.1 Hz were actually caused by the SRCLFF, not by ASC
• We left the SRC ASC on as we increased the power, and this seems fine so it is now in the guardian.  
• We also added the ISS second loop back into the guardian. 
• In the low noise length control state there were some gain changes that didn't make sense when we looked at the OLG measurements, so we have commented them out.  This leaves us with a SRCL ugf of 35 Hz, PRCL at 60 Hz ,and MICH at 9.5 Hz. 
• We engaged the MICH FF and it still seems to be doing a good job of reducing the coherence.  
• We found that the SRCL FF we have is unstable, we made the measurements to redo the fitting.  We saved templates in userapps/lsc/h1/templates  Craig is working on fitting and has a filter that is ready to try
• We ran Gabriele's A2L script, it worked and reduced the coherence with ASC. 
• We lost lock for an unknown (fast) reason at 3:07 UTC, 4:15 UTC, 5:36 UTC (may have been a small EQ) and 6:09 UTC
• ETMY mode1 gets rung up in about 1 out of every 5 locklosses.  I am not sure why this mode in particular should be rung up, it is not at the edge of any of our notches.  The filter used for damping is narrower, so it might ring longer on locklosses than the wider filters do. 

Related to WP 7881, modified and recompiled the PSL ISS model, to change the name of a filter bank from PSL-ISS_SECONDLOOP_REFERENCE_DIFFRACTION_CAL to PSL-ISS_SECONDLOOP_REFERENCE_DFR_CAL

Modified accordingly the MEDM screen in /opt/rtcds/userapps/trunk/psl/common/medm/ISS/PSL_CUST_SECONDLOOP_SLOWOFFSET.adl

It should now be possible to engage the ISS second loop by requesting the state ISS_ON of the IMC guardian. This state engages an AC coupled ISS loop.

The you can request the state ISS_DC_COUPLED. This state for now just switches off the digital AC coupling. It used to have the engagement of two boosts: for now I left them out, since we need to be at high power to ensure that the ISS second loop has enough gain to be stable with the boosts.

I tested the switching on and off at 2 W. The third plot shows both the first loop (PDA and PDB) and second loop (INNER and OUTER) signals in the three different configurations: ISS 2nd loop off, ISS 2nd loop AC coupled, ISS 2nd loop DC coupled (no boosts)

To be tested at high power (including the boosts)

Some details

• The AC coupling integrator was in a wrong configuration, basically completely off. The right configuration is shown in the first attachment
• Adjusted the diffracted power reference servo offset (second figure)
• Adjusted the reference servo filter banks and gain so that the two servos are working: one is active when the ISS second loop of off and should maintain the board output close to zero; the other is active when the ISS second loop is on, and keeps the refracted power close to the set offset (which is  H1:PSL-ISS_SECONDLOOP_REFERENCE_DIFFRACTION_CAL_OFFSET)