Attempted to bring the interferometer back to 40W in an attempt to leave it at 40W over night.
- Slightly tweaked the yaw offsets of the QPDs to improve the PR gain, but ran out of patiance at a recycling gain of 28 - I think there is more to be had with better alignment..
(The offsets I used were in the control filter modules: H1:ASC-DSOFT_Y_OFFSET=0.08, H1:ASC-CSOFT_Y_OFFSET=0.04)
- Then the OMC DCPDs started saturating - for now I just turned off the PD whitening.
- Added the input matrix from alog to Guardian - but Guardian still does not turn the SRC1 loop on when it gets there.:
for SRC1_P:
AS_A_RF36_I : -0.5
AS_B_RF36_I : +1.0
for SRC1_Y:
AS_A_RF36_I : -1.5
AS_B_RF36_I : +0.34
However, the soft loops ran away several times during powerup - not sure what changed.
SUMMARY: Had the Control Room to myself in the evening. Unfortunately, H1 was a bit finicky (see Locking & Initial Alignment notes below) & drove me crazy for an hour or two, but eventually it went to 20W. Will probably leave it here for the night. Violin modes (& harmonics) are rung up.
Config Changes noted for EY on the CDS Overview:
ISI: If we want to address this with reboot, take ISI to a non-sensor correction state first. Then load new filters. But can leave until the morning for Jim to take care of this.
Commissioning:
Soft Loop investigations at the beginning of the shift. (Jenne, Sheila)
Locking Notes:
Switched the input matrix values back for the TMS Soft Loops which Sheila alogged about earlier. Tried locking, but DRMI did not look good.
Initial Alignment Notes:
Went through a couple of alignments and both times had issues with INPUT_ALIGN. For the first time, the MC would not hold lock (so I skipped it). For the second time, the Xarm flashes were good, but it would not lock. I doubled the XARM gain, but I couldn't drop it back down without the Xarm breaking lock (aligned while keeping the gain at the doubled value of ~0.15). Then moved on.
After the first Initial Alignment, could not make it past LOCKING_ALS. Eventually went for the 2nd Initial Alignment (& had INPUT_ALIGN issue noted above, but atleast made it through the step). Went for locking and this time had none of the LOCKING_ALS issues!
[Puzzled about what the deal is with INPUT_ALIGN! Atleast in my attempts, it seemed to definitely affect whether I could get past LOCKING_ALS.]
Leaving H1 at the INCREASE_POWER (@20W) Guardian state for the night.
We measured the ASC PIT Sensing matrix in the REFL sensors.
We drove cHard, cSoft, Inp1, PRC1, & PRC2 loops at around 8 Hz and then took data of the CHARD and REFL WFS signals. We started at 1150766030 and stopped at 1150766330. Coherence was > 0.98 for all elements of the matrix. But why? What's the point of all this? Well, we are trying to make a clean CHARD signal by mixing the REFL WFS signals. However, we have 5 DOFs that show up in REFL, but only 4 sensors.
Therefore this problem is not a pure matrix inverse. Moreover, we would like to maximize the SNR of CHARD in the CHARD_IN1 so as to reduce the CHARD controls noise injected into DARM. IF the REFL signals all had the same noise performance or if they were uncorrelated with each other, this would not be a problem.
The first attached image shows the spectra and coherence during the sensing matrix drive time.
The second image shows the co-Herence during the ~20 Mpc stretch from around 1 PM today. Of course, the ASC noise was really bad then, but its sort of always is, so...
A more complete alog is coming later, but we have an expirimental ASC input matrix for the soft loops in the guardian right now, which is insenstitve to the hard loops. We need to work on decoupling common and differential for this matrix to work. You can revert to the old matrix by on lines 1950 in the ISC_LOCK guardian if necessary.
Conor, Jeff, Jim, Krishna After generating a model that can do offline sensor correction, I played around with the plant inversion, unit conversion, and high-pass filtering in the BRS sensor correction path. Two major points became apparent: 1) The BRS plan inversion is effectively providing some noise gain below 8mHz. By moving the poles in this filter close to the high-Q zero, a free 10dB can be won at low (f<5mHz) frequencies. 2) To improve correction at 10mHz, the STS2 needs some plant inversion. Instead, we can AC-couple the BRS at the same frequency and Q as the STS2. This means moving the poles in the filter 'GND_SENSCOR_ETMY_STS_Y_ROTVEL' FM3 until they match the STS2. The manual says 8.33mHz, Q = 0.707, but I found better subtraction performance with 7mHz, Q = 0.7. I had to push the pole in FM1 'acc_to_vel' from 2mHz to 1mHz to avoid phase loss. Additionally, FM2 'match', is now -0.774, about 15% lower than before. These changes make some small gains at low frequencies, for a total of about 4x RMS improvement at 1mHz. The offline sensor correction goes from the Blue to the Red traces in attachment 1 (BRS_sensor_correction.png). The coherence tells a nice story: Nearly all coherence is subtracted from 0.1Hz down to ~30mHz (where BRS sensor noise becomes significant). At higher frequencies, they remain as coherent as before since the wind drives translation as well as tilt, and we're only subtracting tilt. At low-f, the GND sensor is dominated by BRS noise and they become coherent again. Sensor correction was trained using 5 hours of consistent wind (attachment 3) GPS time: 1150459291 -- 20 June 2016 ~17:01 UTC
Stefan, Kiwamu,
With Keita's instruction in hand (27931), we have closed the 2nd and 3rd ISS loops at the same time. We confirmed that the 3rd loop still suppresses the arm transmission signals.
A next challenge will be to power up the PSL power with both loops closed.
The first attachment is a measured transfer function of the 3rd loop when the 2nd loop was closed. The PSL was set to 20 W. Note that we accidentally had a wrong sign for the control gain in this measurement, so the phase should be read with an extra 180 deg added. As expected the transfer function looks identical to what Keita measured before without the 2nd loop (27898). The second attachment shows the setting we used to close the 3rd loop. As suggested by Keita, we took out FM9. A good gain was found to be 60 dB larger than it was for the 3rd-loop-only configuration. The sign of the gain needed to be negative. We tried closing the 2nd and 3rd loops twice today, one time without an issue, the other time we unlocked the interferometer seemingly due to DAC saturation for the 3rd loop. Once the loop is closed the DAC counts for the 3rd loop is roughly 1000 cnts level -- no problem at all from the range perspective so far.
We then did one quick test where we stepped up the PSL power just by 1 W (i.e. 20 -> 21 W) to see how the ISS system reacts against it. This unlocked the interferometer; seemingly the second loop unlocked first by hitting the trigger upper threshold which subsequently unlocked the first loop whose diffraction power went up to 40 % on a time scale of a couple of seconds.
In alog 27931 I forgot to take into account the 2nd board DC gain of 350 when injecting into 1st loop board. With this correction, the gain at 25W should be 1750 (not 5) with -80dB on, so it's understandable that we need to turn -80dB off and set the gain to 0.1.
I don't understand the sign, maybe the polarity of the PD+whitening of the second loop array is different from that of the first loop PD.
Nutsinee, Jim, Dave:
The HWS code crashed at 07:50 PDT this morning, Nutsinee tried to restart at 11:46 PDT, but it failed. We found that the 1TB raid is 100% full (has data back to December 2014). We are contacting Aidan to see how to proceed.
BTW: the /data file system on h1hwsmsr is NFS mounted at the end stations, so no HWS camera information is being recorded at the moment.
We deleted December 2014 ITMX and ITMY data to free up 21GB of disk space on /data. The code now runs.
We need a long term plan on how to keep these data if they need permanent archiving.
I have restarted both X and Y HWS codes this evening.
The disk was full again today. I deleted Jan-Feb 2015 data from ITMX folder. Freed up 194GB. HWS code now runs again.
[Jenne, Sheila]
We spent much of the evening trying to find a better combination of QPDs to use for the SOFT error signals, since SOFT is what is moving, and pulling down our recycling gain.
In the past, we have chosen combinations that are insensitive to TransMon pitch and yaw, so that we don't put TransMon motion back into our arms.
One of the things we tried tonight was to instead chose a combination for SOFT that was insensitive to HARD. Unfortunately, our HARD and SOFT modes are very nearly degenerate in the QPDs, so that turns out to have been a poor idea. We were able to close the loops around this combination (before we realized that it wasn't going to be great), and I moved the SOFT offsets around to recover our power recycling gain. In the screenshot, you can see that when we increased the PSL power, we lost recycling gain. Then, it comes back. (Also shown is my stray click on the PSL guardian screen where I accidentally requested more than 50W. We kept lock during that adventure).
We tried once to create a combination that is maximally sensitive to SOFT (which will also be very sensitive to HARD). We engaged the pitch loops with this combo, and lost recycling gain, and then lost lock. So, more work to be done here.
We're still not sure what is the best combo to use - there are more things in this department to try out.
Quiet shift environmentally, and the entire shift was devoted to Commissioning work. Here are a few notes:
Untimately we need to engate the 2nd and the 3rd ISS loop at the same time. Toward this goal, I first tried to engage the 2nd loop but without the 3rd loop, and measure the 3rd loop open loop transfer function while the 3rd loop was open, but the IFO didn't cooperate at 20W today.
I instead measured the 1st loop and the second loop sensing by injecting into the 1st loop error point via the second loop board while the input side of the 2nd and the 3rd loop were both open. I measured between 6Hz and 0.4Hz, and it was mostly flat as it should be. At 2W, the ratio of the second loop sensing to that of the 1st loop sensing was:
Sens2(2W)/Sens1 = -0.4.
At P Watts, this will become -0.2*P.
Let's say that the 2nd loop works at 25 Watts with the same setting as in O1. And we already know that the 3rd loop (without 2nd loop) works with the 3rd loop filter gain of -1. A good starting point would be to engage the 2nd loop at 25 Watts without the 3rd loop, disable FM9 (boardComp) of the 3rd loop filter, set the gain to -1*(-0.2*25) = 5 and engage the 3rd loop.
The 3rd loop digital gain needs to be changed as the power goes up because the sensing for the second loop is not normalized by power. The analog gain control slider is downstream of the 3rd loop summation point and cannot be used as a poor man's power scaling for the sensing.
Strictly speaking, Sens2/Sens1 is not flat at very low frequency beucase of the analog "whitening" difference. If this causes problem at the lower UGF, try adding zpk([7mHz], [71mHz], 1) in the 3rd loop digital filter.
PSL ISS PDs all have some built-in whitening. The "error point" we're talking about is downstream of the whitening, and therefore both Sens2 and Sens1 include the whitening. It's confusing to explain this in words, so just look at the simplified diagram attached. Except that each of the 2nd loop pds have its own whitening in reality (rather than whitened after added together), this is a reasonable diagram.
Anyway, the whitening for 2nd loop array is
z, p = [7e-3; 71e-3], [3.1; 3.2; 117; 2.46k]
according to D1300639, while the whitening for the 1st loop is
z, p = [72e-3; 72e-3; 2.6k], [3.4; 3.4; 130; 2.3k]
or something like that (see D1001998).
(This also means that the TF from injection point to the intensity noise is inversely proportional to the whitening.)
I forgot to take into account the board DC gain of 350 when injecting into the 1st loop.
This means that, with 25W, the gain should be 5*350=1750 instead of 5.
While locking this evening, Sheila noticed that while H1 was locked in DRMI & after it went through PREP_TR_CARM, the Arm Offsets were put at wrong values (which would have prevented us from FINDING IR for later locks).
In Guardian, we basically take an average of 1sec of data of the IN1 signals & then this avg is entered as the offset (with a "-" sign).
[From the ISC_LOCK.py script]
This sounds like it makes sense, but for our lockloss, Guardian took BOTH offsets to 0.0 (and the IN1 signals were clearly not 0.0). So this looks rather dubious. Attached is 6-seconds of data for both X&Y arms.
After the OAF model wiring fix, the Suspoint -> IFO-basis appears to work fine, except for the (already mentioned) limited subtraction. I compared the GS13 (Suspoint) DARM with H1:CAL-DELTAL_EXTERNAL_DQ. To do this, I had to de-whiten the DELTA-L signal with 6 zeroes at 30 Hz and 6 poles at 0.3Hz (10^12 dewhitening). In principle, this should be calibrated down to 10mHz (the calibration model has a pole at 10mHz instead of DC). The two spectra (attachment 1, 'DARM_suspoint_vs_IFO.png') somewhat agree. There seems to be some residual error in the calibration of Delta L at low frequencies (it should cross 10^-6m/rt(Hz) at some point). Kiwamu found that the gain field of H1CAL-CS_DARM_FE_ETMY_L1_LOCK_L was a factor of 3 different from its equivalent suspension model, and corrected it, but this cannot explain the difference we see. The coherence (attachment 2) is quite good from ~0.03-0.3Hz. Note that the GS13s are calibrated only to 30mHz, but this is also where they begin to rapidly lose coherence anyway. GS13 noise floor (for a single device) is added to show that there is some significant SNR at nearly all frequencies shown.
The ITMX PI path was measured during maintenance day driving from CDS and measuriung the quadrant outputs to the ESD. WP#5931
Specifically driving H1:SUS-ITMX_PI_OMC_DAMP_MODE1_DAMP_EXC with 80k counts, and measuring P2-P5 of D1600122 directly with an SR785.
In this case a splitter was created and used to allow the cable and ESD load to be included in the measurement. This configuration resulted in a 1.6% drop in drive amplitude of the LL quadrant fairly uniformly across all frequencies.
There is some confusion with the channel naming, on the chassis front panel left and right are switched relative to the model naming. The model names appear consistent with wiring diagram D1500464.
Otherwise these channels behave well.
There was a left -> right switch in the naming of the inputs and outputs of the PI ITM_DRIVER block used in h1susitmpi. ITMX and ITMY channels for linearisation, PWD and OUT and OUT_MON were incorrect.
This will be fixed next model restart.
Since the calibration for the rotation stage doesnt seem to last too long, I added a bootstrapping method from rs_power_control.py (that I think Jamie made?)
At the end of the RS move, the bootstrap will move (requested_power^2) / (current power) further. This assumes that it is already close.
We tried it once going from 9.2W to a request of 20W and it went to 20.0W. Very nice.
This was introduced by David Feldbaum at LLO and I am assuming that is where the code comes from (see LLO alog 13223)
Nergis, Peter, Stefan,
Currently, as we transition from 10W to 57W input power, our recycling gain drops from about 34 to 27. It seems like we need to tune the common TCS:
Attached are 3 plots:
Plot 1: DC signals:
PR_GAIN and normalized arm power (both blue)
AS_DC A and B (green and red)
POP_DC A and B (cyan and purple)
REFL_DC A and B (yellow and black)
Note the interesting behaviour of the REFL DC, all while AS_DC is linear in power.
Plot 2:
Arm and power recycling cavity powers, as well as test mass pitch control signals. The test masses have to compensate for radiation pressure, making the pitch control signal proportional to the arm cavity power.
Plot 3: RF signals:
Power and signal recycling cavity sideband buildups.
[Jenne, Stefan, Peter]
We sent a lot of CO2 power to the ITMs today for a short period of time, once at 20W PSL power and once at 40W PSL power. The idea was that if the recycling gain drop was due to central heating from the intracavity power, we should be able to mimic that by heating with the CO2 lasers and see a drop in recycling gain. However, we don't see a drop in recycling gain, so it's not a heating / mode matching problem. The drop in recycling gain really is due to misalignment effects, mostly SOFT yaw.
We set the Yarm TCS to 2.4W, and the Xarm TCS to 4.0W for the durations of these tests. See attached that we didn't see any effect in any buildups or recycling gain.
Here are some plots that show that the X arm is getting misalinged in yaw durring the lock that Stefan was invesitagting power recycling gain loss for. The first plot shows the transmitted green power, which is dropping for the X arm but not the Y arm. We don't use any ASC control for the green light while in full ock, but by leaving it injected we can tell when the alignment of an indivdual arm is changing. The second plot shows the Transmon QPDs for both pit and yaw, showing that X yaw has the largest change durring this lock.
This is a quick summary of today's TCS joy. I ran another differential lensing test today. I went to the other side of the differential lensing (CO2X goes higher power).
The highest cavity pole was 352 Hz in this test.
This time, I also took many measurements of the intensity and frequency noise couplings periodically throughout the test using Evan's automated measurement script (20470). I will analyze and post them later. The second attachment is trend of some relevant channels.
This is a report on the intensity noise coupling measurement to DARM during the same TCS testing period.
The below is an animated plot showing how the intensity noise coupling evolved as a function of time during the test. The transfer function was measured from ISS-SECONDLOOP_SUM14_REL to CAL-DELTAL_EXTERNAL. DELTAL_EXTERNAL is unwhitened.
As shown in the above animated plot, the intensity noise increased at the beginning and then went back down to where it was. The overall spectral shape almost did not change, but the scaling factor has changed roughly by a factor of two comparing the minimum and maximum. The magnitude of the coupling rises in proportion to frequency -- if I plotted them for a coupling to DCPDs, they would be almost flat due to the cavity pole correction taken out.
Here is another plot showing the evolution of coupling as a function of time.
The upper plot shows the transfer coefficient at 2500 Hz (in arbitrary unit) as a function of time. The bottom plot shows the CO2 lensing from the same period. The transfer coefficient shows a clear correlation with the defocus of ITMs. I can not say for sure if the differential was a dominant cause of this effect because I had a few uD defocus as well in the same fashion.
Here is the same analysis for the frequency noise coupling to DARM. The variation in the coupling is more drastic than that of intensity noise.
The below is a same type of animated plot. The transfer function was measured from REFLA_RF9_I_ERR to CAL-DELTAL_EXTERNAL. Note that DELTAL_EXTERNAL is properly unwhitend.
It seems that the coupling has two different mechanisms, one for the coupling below 300 Hz and the other for the above. As the CO2 setting changed, the high frequency part increased at the beginning and decreased later while keeping the same spectral shape. On the other hand the low frequency part varied in an opposite fashion; it decreased as the high frequency part increased. The slope of the high frequency coupling seems to be almost proportional to f. If we convert it into [OMC DCPDs [A] / laser frequency [Hz]], it will be more like 1/f due to the cavity pole and REFL's transfer functinon against the laser frequency.
Here is another plot showing the evolution of the transfer coefficient at 2500 Hz. The coupling coefficient changed by a factor of 15 at this frequency. This is much more drastic than that of the intensity noise coupling which varied by a factor of two or so.
A preliminary conclusion:
With the 2 W PSL, the DARM cavity pole prefers a high CO2 differential lensing while the laser noise couplings prefer a low differential lensing.
This is a belated analysis on the intensity noise coupling. The punch lines are:
[Noise coupling v.s. differential lensing]
As seen in the plot above, the coupling coefficient shows a linear relation to the differentianl lensing. This likely indicates that the differential lensing is not optimized to minimize the intensity noise coupling. I should note that this measurement had used the badly clipped COY beam (27433) which was later fixed in May 2016; a smaller differential lensing means less power in CO2Y than CO2X.
[Intensity noise coupling]
Here is a plot showing the intensity noise coupling of the various TCS settings. This time the coupling coefficient is converted to OMC power [W] / input RIN. The dashed line in the magnitude represents the expected value calculated by
(coupling) = 2 * J1^2 * Pin * Tomc * Tifo [W/RIN] = 5.5e-6 [W/RIN],
where Pin = 2 W is the PSL input power, Tomc = 61.4 ppm is the OMC transmission for the 45 MHz RF sidebands, and Tifo is the transmission of the intereferometer for the 45 MHz RF sidebands which I have assumed to be 1 for quick calculation. As seen in the plot, the expected noise level (limited by the 45 MHz RF sidebands) is lower then the measurement by roughly a factor of 10. These two plots support the hypothesis that we are far from the optimum point.
Here are the beamsplitter angles as a function of differential lensing. (There are some data dropouts in the trends).
This seems to indicate that a differential lens change of a few tens of microdiopters causes the beamsplitter yaw to change by a few hundreds of nanoradians, presumably via changes in the 36 MHz angular plant. In pitch it is less clear whether we are seeing angular control effects or simply drift over time.