[Jenne, Hang, Gabriele]
We noticed that when we switch the DRMI length loops from 3F to POP_1F, the recycling gain gets lower and less stable, like we had a longitudinal offset. Indeed before we switch the POP_RF9 and POP_RF45 signals have large offsets, in the 100-1000 counts range.
We tried to switch back to 3F after all ASC loops were on and the alignment was good, and we saw a similar behavior.
We checked the dark offsets and they are small. We also checked POP_9 phase and tuned it from -22 to -19.5.
For the moment being we don't feel like leaving those large offsets. More investigations needed.
I thought that we had fixed this, but AS_B_RF45 seems to have a difference between the request and readback of the whitening filters or gain. We're not currently using AS_B for anything, so not urgent, and can likely wait until next week.
TITLE: 09/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY:
LOG:
Gabriele and Jenne working on locking
15:00 PSL meeting via TeamSpeak
15:46 Nutsinee driving down Y-Arm to have a look at the burned area of the desert
16:11 Nutsinee back and going out to ISCT6
16:16 Guest for Chandra on site
16:38 Mark, Tyler, and Chris to MY to install grease lines for fans and to seal up areas where bats may be getting in
17:00 Safety Commission tour into LVEA for tour.
17:24 Vanessa to MX
17:45 Chandra and guest to mid-stations
18:00 Kyle out to LVEA to recover light equipment. He'll be entering through man door at Lg equipment entry
18:40 Tour out of LVEA
18:51 Karen back to corner
19:04 Mark, Tyler , and Chris back for lunch and are setup at MX for same work.
19:40 Karen to EY
20:00 Mark, Tyler, and Chris to EY
20:32 Karen leaving EY
20:32 Tour group leaving EY
20:41 TVo out to LVEA to turn on CO2X LASER
22:00 Site meeting
After Gerardo regenerated three corner station NEGs yesterday, the isolated pressures in their housings continues to drop. The drastic slope change you see in attached is a gauge thing - these full range hot cathode ion gauges change emission current at 5.6e-6 Torr and can be deceiving when running an experiment like this.
After today's commissioning meeting I was asked to look into the FSS oscillation threshold setting and why the FSS guardian was not detecting when the FSS was oscillating (thus necessitating by-hand adjustment of the FSS common gain every time the IMC loses lock and throws the FSS into oscillation). Looking at the FSS model (1st attachment, middle of the picture), H1:PSL-FSS_OSCILLATION is set when H1:PSL-FSS_MIXER_PP is greater than H1:PSL-FSS_OSCILLATION_THRES.
Knowing this, I trended back a couple hours, looking for times when H1:PSL-FSS_FAST_MON_OUTPUT was oscillating, and compared them with the value in H1:PSL-FSS_MIXER_PP; see 2nd attachment. This makes it clear why an oscillation threshold of 3 was not working to set H1:PSL-FSS-OSCILLATION; the mixer peak-to-peak voltage never exceeded 2.5V during times of oscillation, therefore the threshold was never crossed. From talking with Jenne, apparently a value of 0.6 doesn't always catch an oscillation, so for now I recommend a value of 0.5 for H1:PSL-FSS_OSCILLATION_THRES. This change has been made and accepted in SDF.
[Jenne, Hang, Gabriele]
This morning, when we were locked at 2W, we saw that a line at 28.45 Hz was ringing up, and visible mostly in MICH / PRCL and SRCL, and a bit less in DARM. After checking all loops for possible instabilities, we decided it was a mode of some suspension. We added band-stop filters at 28.4 Hz in all angular degrees of freedom of all suspensions, and this solved the problem, letting the mode ring down. We haven't identified which suspension is responsible.
The mode (actually it looks like a doublet) was also visible in the two ITMs optical levers, but at that time we saw the same excitation in the hard angular loops.
model restarts logged for Tue 11/Sep/2018
2018_09_11 10:22 h1iopiscey
2018_09_11 10:24 h1pemey
2018_09_11 10:26 h1iscey
2018_09_11 10:28 h1caley
2018_09_11 10:30 h1alsey
2018_09_11 10:58 h1iopiscey
2018_09_11 10:58 h1pemey
2018_09_11 10:59 h1iopiscey
2018_09_11 10:59 h1pemey
2018_09_11 11:00 h1alsey
2018_09_11 11:00 h1caley
2018_09_11 11:00 h1iscey
Restart to recover h1iscey from a timing glitch. First unsuccessful restart was done remotely, second at EY itself.
model restarts logged for Wed 05/Sep/2018 - Mon 10/Sep/2018 No restarts reported
J. Kissel Noticed the calibration line spectrum on the main sensitivity wall FOM (nuc3) showed no calibration lines. Opened PCAL Y overview screen and found the OFS railed at ~7.5V (as quickly seen by the trend on the MEDM overview screen; see attached). Trended the OFS PD channel (H1:CAL-PCALY_OFS_PD_OUT16), and found that it railed at Sep 11 2018 @ ~18:00 UTC or at ~11a PDT. This is likely a result of the timing glitch at EY (referenced in LHO aLOGs 43932, 43928). In order to fix, I merely needed to toggle the Loop Enable Switch, H1:CAL-PCALY_OPTICALFOLLOWERSERVOENABLE. Also -- we (Travis and I) didn't store the new amplitude settings for the calibration lines in the SDF system. Upon restart I found calibration line heights at their O2 values. I've also re-changed the line heights to their temporarily higher values while we measure the optical gain with our current, not-yet-amazing, sensitivity. For the record, Former New Change 36.7 OSC1 500 1000 x2 331.9 OSC2 5000 20000 x4 1083.7 OSC3 15000 5000 /3 7.93 OSC4 5000 5000 no change See 2nd and 3rd attached files confirming the change and the capture into SDF.
All BSC spectra looks to be nominal except for a slightly elevated offset in the BS_ST1_CPSINF_H1_I channel. All HAM spectra appears to be nominally sound.
It was not necessary to add water at this time.
TITLE: 09/12 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
Wind: 5mph Gusts, 3mph 5min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.10 μm/s
QUICK SUMMARY: Safety committee meeting today
Hang Sheila Georgia
Attached are 3 ASC measurements:
1) CHARD Y with the gain set to 0.3, which is the same gain as in the reference. You can see that the phase delay at 1.8 Hz is gone.
2) CHARD Y with the gain set to 1, we increased the gain to 2 before powering up but didn't remeasure.
3) CHARD P with the 46dB of additional gain
[Nutsinee, Haocun]
After putting ND filters before the OPO REFL due to the saturation issue, the OPO can be locked without problems, and the I and Q phases look good. (Nutsinee can give more details on this.)
Later on we took more squeezing measurements under this good locking condition, and I plot the data with some fitting curves as attached.
Homodyne Visibility: 97% and 96.87% (We had to do this, and before any adjusting it was ~86.7% with ~2mW unbalancing.)
So the estimated optical efficiency is 65% and 50mrad phase noise.
According to our budget here, our optical efficiency should be around 85%, which means we need to find out where are these ~20% loss from.
Next step:
- Swap PD or tweak electronics to have proper set-up for the saturation problem, instead of using ND filters.
- We'd better to adjust the crystal position again with OPO locking properly.
- Measure the optical loss on SQZT6, and dig out other potential losses.
Just re-checked the quantum efficiency of both diodes, which are pretty good. Very close to 1. The back reflection are ~10uW out of 1mW input.
However, found out that we were using 1mW on each diode instead of 0.5mW for those measurements, which could give some effects on the squeezing measurements.
[Sheila, Hang, Gabriele]
In brief, the L1 LOCK gain in ITMX was 10 instead of 1 (as it used to be during O2). Therefore the reallocation of pitch and yaw to M0 was ten times stronger, and it modified the suspension angular response as seen by the ASC at the lower stages. This created a crossover at about 1 Hz that produced the right-half-plane zero we measured in CHARD and DHARD. This wrong gain was there only in ITMX. We reverted it to 1 as it was during O2. The gain was changed from 1 to 10 on Saturday June 2nd 2018 at about 21:55 UTC. Nothing relevant written anywhere in the elog.
The plot below shows the yaw to yaw response of ITMX, measured with the optical lever, in a few different configurations.
The expectation is that this will fix the DHARD/CHARD plants (43844)
We implemented the low pass filters in all test mass M0 stages, since it gives us some more phase and gain margin at about 1.8 Hz, where there is still a zero.
The story of how we found this problem is long and convoluted. A brief summary below:
As part of this story, Jenne Hang and I checked the calibration of the test mass oplevs using the baffle PDs.
ITMY pit oplev is about 4% larger than what I got from the baffle PD, yaw is 3.5% lower, ETMY pit oplev is 13% high and yaw is 2% high. Jenne did a similar check for the Y arm optics, and I think that she also found that the optical lever calibrations are OK. (for locations of baffle PDs see D1200657)
The check that there wasn't a cross coupling between pitch and yaw on the ITM optical levers, Jenne and Hang steered the green beams to PD2 +PD4 on the ETM baffles, and in both cases the optical lever response in yaw was about 2% of the pitch response.
It would be great if someone could follow up on the ITM pitch to yaw cross coupling during some down time (without the confusion about top mass offloading).
For the yaw to pitch coupling, we already have good measurements of all test mass actuation responses. We only have to repeat the ITMX measurements since they were taken with the wrong M0 offloading. This will take about (10+10)*100 s = 2000 s of interferometer offline.
I will post more details with the measurements tomorrow, and hopefully there will be time to repeat the ITMX measurement.
Commenting on Sheila's log about oplevs checks:
To check the calibration:
To check that true pitch motion is reported by the oplev as pitch-only, and not a combination of pitch and yaw:
TITLE: 09/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PDT), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: None
SHIFT SUMMARY:
Maintenance from 8am - 1:30pm PDT this morning.
LOG:
Thanks for a thorough summary Corey.
While trying to relock today, we had much worse recycling gain after doing initial alignment than what we had on Monday. Hang found that at around 18:06 UTC (11 am local time) the stored values for the ITMY camera were changed. He restored them and Geogria accepted them in SDF, but we don't see any logs about model restarts. It sounds like there was an unintentional restart of that model (43932)
SDF is really not in good shape right now, and it will be challenging for commissioners to keep up with it while we are in this state. It would be great if operators/ other people can help us catch these things by being on the lookout for model restarts and being on top of either checking checking conlog when there are unintentional restarts or checking SDF before planned restarts.
At 19:10TUC, I'd restored the ISS and FSS to locking. At 19:22UTC, unlocked, Mark and Keita are out making measurements.
On 9/3/18, P. King tweaked the mode matching into the 70W amplifier. As Cheryl says, yesterday I took a beam propagation measurement for mode matching into the PMC. To give an idea what the beam now looks like, I've attached a picture of the beam profile taken ~695mm from the 70W amplifier.
As there is a power drop somewhere between the 70W amplifier and the PMC, we did a quick a power budget using the water-cooled power meter; all measurements were done with the ISS OFF:
The largest power loss is at the ISS AOM, where we lose 3.4W. We had suspected clipping at this AOM, and it looks like that is the case. We will have to re-think our PMC mode matching scheme to get the beam smaller at the ISS AOM.
With the 70W beam looking better, I wanted to get an idea of where we are now in regards to PMC mode matching. Without changing the mode matching scheme for the PMC, I took a quick measurement of the PMC visibility using the locked and unlocked voltage from the PMC locking PD. This was also done with the ISS OFF:
Simply by cleaning up the 70W beam (via Peter's 70W amp mode matching tweak), we are at >80% visibility. This is, however, somewhat disconcerting. Looking at the above power budget, we are only transmitting ~73% of the power incident on the PMC, so something isn't quite adding up here. Something to think about before next Tuesday.
[Hang, Craig, Gabriele]
We moved PR3, PRM and the soft degrees of freedom to improve the beam centering on all four test masses and increase the recycling gain.
We started with a recycling gain of about 38.2 and finished with a recycling gain of 47.4 [+24%]
A lock loss terminated our work, so there is still some re-alignment to do to get the test masses centered. And there might be more recycling gain.
We added dithering lines in yaw to all four test masses, and we could improve the centering significantly. At the end all Y2L coefficients are zero, and the dithering signals are quite close to zero. The two ITMs are reasonably centered, as is ETMX. Instead ETMY seems to have a larger mis-centering.
If we need to put back the Y2L coefficients, we probably only need to set ETMY to about 4.
We finally lost lock after more than 6h continuous lock.
Wow, very impressive. Hiro's simulations (G1700140) gave a PRG of only 39, though that was including an ad-hoc loss per arm of 50 ppm.
This is awesome!
Our PR gain is POP_A_LF / IM4_TRANS_SUM with calibrations to take into account reflectivity branching ratios, but we're quite close to the edge of IM4 trans. I think our normalized yaw number is more than 0.8. (We haven't pico'ed yet, to keep an alignment reference, but I think it might be about time to pico and say that this is better than O2.) I'm suspicious that our PR numbers that we've been reporting might be systematically high, if the number we're dividing by is smaller than the total actual amount of power in transmission of IM4.
That said, this has been true since our vent recovery (and also to a lesser extent during O2), so the +24% is certainly real, but the absolute values we've been reporting for PR gain might be high. We should pico and check the calibrations to be sure.
Looking at TR_X_NORM and TR_Y_NORM (which are normalized so that the single arm build ups are 1, at the time of the best recycling gain the build ups were 1646 and 1732 relative to the single arm, which would indicate a recycling gain of 45. Gabriele pointed out that the reflectivity of PRM is 3.1% according to galaxy, which means that this gives a recycling gain of 53.0
Another option for estimating the circulating power would be to try this method which has been done at LLO: 36745
WOW! Amazing!! Congratulations!!
Here's a quick computation of the power recycling gain as a function of the round trip losses in the arm (in ppm, sorry I forgot the units in the plot), assuming Tprm = 3.1%.
The two marked points correspond to the values of recycling gain estimated with POP_LF and with the arm transmission.
Dark offsets for TR_X and TR_Y are not very well set. The table below shows the TR values in different configurations, and the corresponding estimated recycling gain. Taking into account the dark offsets now the X and Y arm transmission give consistent recycling gains.
| Dark | Single arm | Full IFO | Recycling gain | |
|---|---|---|---|---|
| X | 0.045 | 1.00 | 1648 | 53.5 |
| Y | -0.007 | 0.98 | 1736 | 54.5 |
The REFL_A_LF also goes up by about 5% (relative to unlocked so it measures the ifo reflectivity) as expected. Great job!
From the level of reflected power (w.r.t. the off resonance state) we can estimate again the round trip losses.
The plot below shows that the REFL level we measured after re-aligning (8.3%) corresponds to about 61 ppm round trip losses, and a recycling gain of 53.4, which is very close to the recycling gain we can estimate from the arm power buildup.
The recycling gain improvement is seen in the CARM offset reduction sequence too. I ran the script that Sheila and Gabriele posted in alog-43344 on data from yesterday (starting at t = 1220674303).
This plots the reflected power (normalised) vs the arm build up (transmission normalised to a single arm). As we step through the CARM offset reduction, the TR_X increases and the REFL_DC decreases. The slope is an indication of the power recycling gain.
As of yesterday we're going better than the previous measurements, including compared to O1.
In addition to Georgia's analysis, here is a similar plot, with also some fit lines. The new curve is again consistent with no losses in the PRC and arm round-trip losses of about 66 ppm.
(In this post I mean "railing" as "parked at the maximum actuation range", where "oscillation" means "PZT is fighting the EOM") The FSS Fast Path has been railing recently, preventing the FSS from locking. (Pic 1) It seems as though FSS_OSCILLATION does not in fact monitor the FSS RMS, but triggers on a threshold. When the FSS voltage would pass a certain value, the PSL_FSS guardian would send it to state FSS_OSCILLATING. This state brings the common gain down to -10 dB, then slowly back up to wherever it started. This works great for stopping oscillations, but not for permanent rails. I modified the PSL_FSS code to increase the oscillation threshold from 0.6 to 3 V for five seconds whenever the fast voltage is railed at greater than 10 volts with extremely low RMS. This should allow the FSS loop to close and bring the temperature within range. Railing hasn't happened again, so I haven't had a chance to test the state, but it does still suppress actual oscillations.
[Hang Gabriele]
There might be some problem with the logic of the FSS_OSCILLATION state. This morning the guardian was continuously reducing the gain to -10 db, and then ramping it up to more than +100 db. Our guess is that the self.high_gain variable which is set in the main() function got a wrong, large value. Maybe we should hard code a gain of 20 db there?
We fix the problem by stopping the guardian, setting the FSS common gain to 20 db and restarting the guardian.
For now we hacked the PSL_FSS guardian the FSS_OSCILLATING state so that the FSS_COMMON_GAIN could not exceed 20 dB. We could thus lock the IMC without needing to manually pause the PSL every time.
Specifically, we modified the original
if not ezca['FSS_OSCILLATION'] or not ezca['FSS_RESONANT']
into:
if (not ezca['FSS_OSCILLATION'] or not ezca['FSS_RESONANT']) and (ezca['FSS_COMMON_GAIN']<20.)
H1:PSL-FSS_OSCILLATION is set whenever H1:PSL-FSS_PC_PP exceeds the threshold.
More info in alog 43970.
Above comment of mine, "H1:PSL-FSS_OSCILLATION is set whenever H1:PSL-FSS_PC_PP exceeds the threshold.", is totally false, see Jason's alog.
J. Kissel, M. Pirello
Applied the following ECR's to the primary chassis (S1101627) and the spare (S1101603).
The existing Whitening Amplifier (D1002559) needs modification to accommodate the violin modes of the main LIGO optics in the vicinity of 500Hz that have a tendency to saturate the existing whitening chain’s pole-zero filters. (E1600252-v2)
Implement separate higher bandwidth readbacks for the OMC DCPDs to support PI damping. (E1600192-v2)
Both ECR's implemented to both chassis, the primary chassis testing is complete and the data is attached to this report.
Here's a Bode Plot of the different response for ST2 of the chassis as a result of this change / ECR completion.
The data has been downloaded and committed to:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Common/Electronics/H1/Data/OMCWhiteningChassis/2018-06-04/
The script that plots the results is:
/ligo/svncommon/CalSVN/aligocalibration/trunk/Common/Electronics/H1/Scripts/plot_omcdcpdwhiteningmods_20180604.m
The digital compensation for this filter has been *roughly* installed, with the design string
zpk([50],[504],-1,"n")
and I've changed the name of the filter to be called "AntiLP" instead of "AntiWh" so as to help alleviate confusion.
Note, we (the calibration group) still needs to make to fit this data more precisely, compensate it precisely, and with an uncertainty estimate on the poles and zeros.