TITLE: 12/20 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: None
SHIFT SUMMARY:
Rough day with big earthquake which kept us down for first half of the day. Then we had an EX timing crash which has kept us down for a good chunk of the afternoon.
LOG:
Handing off to Niko for last hour (have an appt in town).
After disconnecting some extension cords that were not being used, the unit was powered off at 22:00 UTC.
WP8022
Danni and Dave:
h1tcscs epics parts recording the inputs and outputs of the ring heater inverse filters had name issues which were fixed. After the model and DAQ were restarted, the data concentrator would not start reporting a name duplication for the EpicsOut part which was named <filtername>_OUT. My check_daq_channels_validity script reported no duplicated channels.
Turns out daqd was correct and my script was in error because we had chosen an EPICS channel name which coincided with a test point channel name. My script was just checking for duplications within the INI and PAR file groups separately, I'll fix it to check the full channel list.
The DAQ frame gap due to the extended down time is:
-rw-r--r-- 1 controls controls 1.6G Dec 20 12:39 H-H1_R-1229373312-64.gwf
-rw-r--r-- 1 controls controls 1.6G Dec 20 12:54 H-H1_R-1229374208-64.gwf
Following Robert's post about fan lines in the Darm spectrum from EX Fil and I went down and investigated cabling. I did not like the grounding scheme on the new +-18/48VDC power supplies so we changed the connection. The supplies are now hard wired together through the returns and grounded. Other supplies are done this way but they only supply 2 voltages not 4. Will look for improvement or not.
EY grounding scheme was also changed.
While poking around looking at PR SUS channels this morning, I see that the M3 stage of PR2 needs it's Sat amp "rebooted" (aka cable unplugged and replugged back in has sometimes worked). (See blue and green UL and LR which have gone noisy at high frequencies since May sometime.) We suspect that if we look around we will find more of these which do not pose a threat until it is determined that they are a problem. No action for now, maybe add it to a Tues morning task to try the power cycle.
Using Rana's excitations last night, we measured the REFL port ASC sensing matrix for YAW at three different times (each measurement last 512 sec ~ 10 mins):
1). gps start: 1229337258; input power: 20 W; POP18: ~62 ct
2). gps start: 1229338980; input power: 23 W; POP18: 56 -> 55 ct (approaching thermal steady state)
3). gps start: 1229316688; input power: 23 W; POP18: ~54 ct (reached thermal steady state)
The response matrix corresponding to the three times are (in order listed above):
| PRC1 | PRC2 | CHARD | CSOFT | |
| RF9_A | 7.5e-2 | 1.6e-1 | 1.2e-1 | 1.5e-1 | 4.2e-1 | 2.2e-1 | 3.6e-1 | 3.5e-1 | 3.6e-1 | 1.3e-1 | 1.8e-1 | 1.9e-1 |
| RF45_A | -1.1e-2 | 4.3e-2 | 3.1e-3 | 2.0e-2 | 2.1e-1 | 1.0e-1 | 2.7e-1 | 3.0e-1 | 3.2e-1 | 1.8e-2 | 6.8e-2 | 6.6e-2 |
| RF9_B | 1.7e-1 | 2.7e-1 | 2.1e-1 | 2.5e-1 | 5.9e-1 | 3.2e-1 | 4.6e-1 | 4.7e-1 | 4.5e-1 | 2.2e-1 | 2.9e-1 | 2.9e-1 |
| RF45_B | 1.8e-1 | 6.2e-1 | 5.9e-1 | 4.6e-1 | 1.7e+0 | 1.1e+0 | 3.2e-1 | 5.4e-1 | 6.5e-1 | 5.4e-2 | 3.7e-1 | 4.9e-1 |
The response matrix can be inverted to get an input matrix. For the two interferometric DOFs PRC2 and CHARD, the input sensing matrix:
| RF9_A | RF45_A | RF9_B | RF45_B | |
| 1.00 | 1.00 | 1.00 | -0.45 | -0.33 | -0.24 | -0.59 | -0.55 | -0.69 | 0.12 | 0.01 | 0.04 | PRC2 |
| -0.94 | -1.00 | -1.00 | 1.00 | 0.61 | 0.39 | 0.49 | 0.45 | 0.60 | 0.00 | 0.02 | -0.01 | CHARD |
The input matrices for both PRC2 and CHARD have some large cancelation between the signal in RF9_A and (RF45_A+RF9_B), and use the residual as the input signal. This indicates a high condition number for the original response matrix. Not sure we could use those matrices as its variation might make the residual signal changes sign...
We also looked at the dithering lines' responses in the TR QPDs.
Here we just focus on two times:
1). gps: 1229337258; input power: 20 W; POP 18: ~ 62 ct
2). gps:1229316688; input power: 23 W; POP 18: ~ 54 ct
The response matrix for the two times:
| CHARD | CSOFT | |
| TRX_A | -1.3 | -1.3 | -0.23 | -0.40 |
| TRX_B | -0.77 | -0.79 | -0.35 | -0.44 |
| TRY_A | 1.5 | 1.5 | 0.17 | 0.36 |
| TRY_B | 0.40 | 0.43 | 0.24 | 0.29 |
which can be inverted to the following input matrix:
| TRX_A | TRX_B | TRY_A | TRY_B | |
| -0.51 | -0.40 | 0.48 | 0.74 | 1.00 | 1.00 | -0.50 | -0.66 | CHARD |
| 0.10 | 0.08 | -1.00 | -1.00 | -0.67 | -0.67 | 0.86 | 0.81 | CSOFT |
Such a matrix can be used as the AC part of the HARD/SOFT sensing.
Because the CHARD response was essentially stationary, the combo for CSOFT sensing that decouples CHARD stays also stationary. The soft response changes, yet in neither of the cases we would run into the situation that HARD and SOFT being almost degenerate (i.e., no large signal - large signal in the sensing matrix), thus we could just choose one combo of CHARD input, and even if its decoupling of SOFT would degrade as we went to another power level, the CHARD signal would not accidentally vanish.
0.7.2 is a bug fix release for ndscope. It had been rolled out successfully at LLO, and control room users report that it fixes some bugs. I rolled it out to the CDS workstations this morning under WP 8020.
Heard Verbal Alarm (thought it was from "Japan"). I went to Jim and we took it to the EARTHQUAKE state in thought it was from Japan; in hindsight, now that we see it's closer and from Russia, might have been preferred to use the "Very Large EQ" Red button for a big & close EQ such as this.
TITLE: 12/20 Day Shift: 16:00-00:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
Wind: 3mph Gusts, 2mph 5min avg
Primary useism: 0.04 μm/s
Secondary useism: 0.94 μm/s
QUICK SUMMARY:
Commissioners left just before shift. Have been trying to acquire DRMI for last 25min, so switching to acquire PRMI. Microseism looked like it had been trending down slightly, but has been picking back up the last few hours (still above the 90th Percentile).
No luck with PRMI, so was going to do an Initial Alignment, but going to let Jim squeeze in some HAM2&3 ISI transfer functions. (Taking ISC_LOCK & IMC_LOCK to DOWN during these measurements).
I had the CO2 guardians paused on the 20W setting for several locks tonight. During this time we had several lock losses and were back up again without any issues - DRMI was locking within 2 minutes. Given that it didn't seem to make a difference I have remove the 2W CO2 powers and now it's just set for 20W to make things simpler (CO2X=0.6W and CO2Y=0.3W).
We tried common ITM ring heater changes this evening, 0.25W on each segment. RF18 leveled off around 58, down from 61, so we stopped and dropped the RH levels back down.
Currently ITMY ring heater is set to 1.8W, turning it down did not help, eventually lost lock to a 0.45 Hz instability, DHARD, CHARD, DSOFT, PRC1 pitch were oscillating a lot. As soon as we start approaching RF18 ~ 50 again the ASC starts becoming more unstable. At this point PRCL gain had dropped to about 60% of its value on power up to 20W. Increasing CO2X also didn't help. This time the 3.5Hz oscillation in the SOFT loops. DRMI is now currently struggling to lock, some big bullseye modes can be seen. Hopefully the CO2 and RH changes will settle down soon for the day shift...
Plotted the REFL_A_9_I and REFL_B_9_I analog outputs. Units are uncalibrated RF9 I monitor Volts/rtHz. REFL_A is still being used for CARM control, REFL_B is just an out of loop sensor. For reference, here's the last calibrated CARM noisebudget I made. Looks like sensing noise dominates at 1kHz and below, and the seismic/scatter noise rises much faster below 10 Hz. What could this excess low frequency noise imposed on the laser mean for the rest of our control loops? According to the digital LF readouts, there's 5.2 mW on REFL A, and 4.8 mW on REFL B at the time of these measurements.
I phased LSC REFL B using an excitation at 1234.3 Hz into the Common Mode Board EXC1 and reading out the REFL_B_RF9 I/Q demod monitor and an SR785. Initially, the LO delay was set to Internal, using the physical switches for delaying (JPG 3). All switches were on, giving 32ns of delay, or 105 degs of phase. I switched the LO delay to External, and found a minimum response in Q at phase of 3 degs. I am guessing that the change from Internal and External gave us ~100 degrees of extra phase. I am only now appreciating Keita's previous work on this, where it's possible that REFL B has some frequency dependent demod phase. I'll take some transfer function of Q/I and make sure that I didn't mess up Keita's phasing at low frequency. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ In the meantime, I am tracking down the CARM analog/digital signal chain. One highlight are Pic 4, where I found a TNC splitter connected to the output of the 2 channel demod board I-output. The one end of the splitter goes to the common mode board, while the other goes to an 8 channel whitening chassis. This trackdown is to think about whether our I and Q responses are balanced, and what can our Q phases tell us about the IFO thermal state, sideband imbalance, etc. Useful DCC of the PSL electronics: D1200666 ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ We are wondering if the REFL_A_9_{I,Q} digital readouts can tell us about the CARM loop, because the digital channel REFL_A_9_I_ERR goes to 27.2 counts when the IFO is locked at 20 W, and not zero, even though the REFL A 9 digital phase is zero. It's clear REFL_A_9_Q_ERR is responding to thermal changes of the IFO (like the differential lensing Dan tuned last night). However, REFL_A_9_I_ERR behaves like a suppressed error signal with a bias that increases with input power and CARM loop gain, and does not change with IFO temperature (see pic 7). I checked the dark offsets, they are not responsible for the bias we see. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ I phased from H1:LSC-REFL_A_RF9_PHASE_PHASEDEG = 84.80 degs to 70.01 degs. I did this using the digital REFL_A channels, so this may not be perfect. EDIT: I rephased REFL_A_9 to 94.67 degrees during the last lock using the analog demod board monitors (pics 9 and 10), the phasing was significantly different than the digital phasing. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ I also tried an failed to see PCAL in the REFL_A and REFL_B spectra. Naively, if we believe this plot and the calibrated PcalY spectrum response at 8 Hz being ~1e-14 m/rtHz, we should see equivalent compensation by CARM amounting to 0.7 mHz/rtHz, meaning the 8 Hz line ought to be visible.The super massive CARM loop gain crushes the line at 8 Hz of course, but the displacement signal should be there at REFL.I forgot about the massive additional loop gain of MC2 at 8 Hz, there will be nothing at 8 Hz to see. And things don't look great at higher frequencies because the PCAL strength falls as 1/f^2 and the CARM optical gain falls like 1/f.
This loop uses the POP WFS as a sensor and feeds back to PR2 angle. The PRC1 ASC loop uses POP QPD as a sensor and feedsback to PRM.
as you can see, this loop has multiple unity gain crossings. Hang previously has a -3dB notch for the 3 Hz part, but I think that's only a band-aid.
Best off to either lower the gain more or to put in a good compensation for the PR2-M3 TF. There was a compensation filter in that filter bank but its not quite right and its also not turned on by default.
On one lock we turned the loop gain down by 2 and things looked stable for awhile, but then we had a 3.5 Hz instability in cHard yaw, so unclear if this is a problem.
The second attachment shows the old/new filter. It is now more unconditionally stable. Checked yaw - it seems OK.
Georgia, Craig, Dan, Rana
Georgia noticed that there were ~3.5 Hz yaw oscillations in arm common mode ASC. Using the continuously running ASC sine waves, we looked at the CHARD/soft matrix and it was nearly bad: the CSOFT sensor was seeing almost purely cHard, whereas the cHard sensor had a mixture of both.
The Matrix initially had 3 RF sensors for cHard and only Transmons for cSoft. (no blending going on for yaw, although there was some pitch blend).
WE then added the CHARD_A input matrix elements to cSoft_B and ramped it in so as to cancel the cHard contribution to the cSoft loop. This worked well and as you can see in the attachment, the CSOFT spectrum no longer shows the 23 Hz cHARD line.
Next we will do the real 4x4 inversion to clean up PRC1 and PRC2 from the other loops.
Dan, Craig Tonight Dan has been touching ring heaters while I have been messing around measuring REFL PDs. At one point we went to NOMINAL_LOW_NOISE. To get there I commented out two lines in LOWNOISE_ASC, one which lowed CHARD_Y_GAIN from 2.8 to 0.75 which caused an instability to ring up, and one which turned on CHARD_Y FM3 (a low pass) which caused a lockloss. The noise at NLN was terrible, which is to be expected with high CHARD gain.
We measured the PR2 M3 P2P sus TF. To do so we misaligned PRM, SRM, and ITMY, and then used AS_A_DC_PIT/YAW to measure the response to PR2 PIT motion. During the process we also engaged the DC centering loops to keep the beam onto the PD, yet we turned the DC gains of the centering loops down by a factor of 100 so that they should not affect the responses around sus resonances.
The measured response is shown in the first figure. From it we can also see that the PR2 P2Y coupling is actually quite small, indicating a good coil balancing.
We also fit the P2P response (up to a DC gain ) into zpk format. The fitting result is shown in the second plot and in the last .txt file we gave the zpk representation in the foton format (s-domain). This can be used for better plant inversion.
The yaw loop seemed fine and thus we did not measure them this time.
If you want to monitor the PRCL and SRCL optical gain, you may runorpython /ligo/home/craig.cahillane/Git/IFO/LSC/scripts/PRCL_132HzLine_and_OscillatorMon.pypython /ligo/home/craig.cahillane/Git/IFO/LSC/scripts/PRCL_152HzLine_and_OscillatorMon.pypython /ligo/home/craig.cahillane/Git/IFO/LSC/scripts/SRCL_138HzLine_and_OscillatorMon.pyto start lines in the LSC oscillator matrices 1 and 2 respectively. The lines are demodulated at the correct phases for 20 watts, and the script sets the filter modules with 10 Hz bandpasses about the exc frequency, and a 0.1 lowpass on the I and Q signals. An example PRCL optical gain monitor is shown below. The POP 9 I signal is sent to H1:LSC-LOCKIN_1_DEMOD_1_SIG, demodulated by the excitation, and the results lowpassed and reported in H1:LSC-LOCKIN_1_DEMOD_1_{I,Q}_OUTPUT. EDIT: I made a MICH equivalent script in the same directory, and a bash script which launches all the OSCs:bash /opt/rtcds/userapps/release/lsc/h1/scripts/set_up_LSC_dither_lines.shand a code which shuts down the dither lines:bash /opt/rtcds/userapps/release/lsc/h1/scripts/take_down_LSC_dither_lines.sh
Several times during the power ups tonight, we ran 4 lines in yaw to measure the changes in the ASC yaw sensing matrix:
PRC1 H1:ASC-ADS_YAW1_OSC_FREQ 16.131
PRC2 H1:ASC-ADS_YAW2_OSC_FREQ 18.37
CHARD H1:ASC-ADS_YAW8_OSC_FREQ 23.25
CSOFT H1:ASC-ADS_YAW9_OSC_FREQ 21.111
analysis in progress...
According to our last lock this evening our POP9I/PRCL optical gain fell by a factor of 5 during the entire thermalization. Dan was playing around with ring heaters, which caused the drop at end, but overall this is pretty dire. POP45I/SRCL fell by ~15% in the same time. POP45Q/MICH did not move much, with only about a 5% drop.
Nutsinee, Sheila
Summary: We went back through the data from last night's squeezing injection. We see that the noise added to DARM doesn't depend directly on the CLF power, but it is suppressed by the LO locking loop (which is feeding back to the OPO length). This suggests that OPO length noise is coupling to DARM but not through the CLF or seeding; back scatter is one possibility.
Details:
Our goal last night was to change the CLF power to see how it impacts the noise added to DARM by the squeezer. We did not change the demod phase at all to try to adjust the squeezing angle. Since the locks were short last night, we were only able to get one or two injections in each lock, and our alignment was changing from lock to lock. We looked back at the data to find the CLF fiber launch power, which we use to estimate how much CLF was injected into the interferometer, the RF3 demod power, and a few other things. Since squeezing injections were done over a couple of locks, and the squeezer alignment was adjusted after the first lock, the alignment of the squeezer to the OMC was different for different times. The number in parenthesis in the legends of the attached plots are an estimate how well aligned the squeezer was. We took the ratio ((10^(RF3/10)/sqrt(CLF launch power)))^2, and normalized by the best alignment from last night to make this estimate.
The first observation (second attachment) is that when the squeezer is badly misaligned, we add less noise to DARM (which is what you would expect). The second attachment shows that we have more noise introduced into DARM with better alignment, the same injected CLF power, and the same analog gain in the LO loop. This means that we had lower optical gain in the LO loop, but also that we have less light from the squeezer reaching the DCPDs.
The next more interesting observation from is that increasing the analog gain for the LO locking loop reduced the noise added to DARM for a similar CLF power and alignment efficiency (first attachment).
One explanation could be that increasing the LO loop gain (which is currently feeding back to the OPO PZT) decreased the OPO length noise. Nutsinee and Daniel today found that we were causing a lot of OPO length noise (46058), which is not suppressed by our OPO locking loop since it feeds back to the laser. Since the OPO length noise was the dominant noise in the LO error signal at the time of these injections, the OPO length noise could be decreased by increasing the LO gain.
The OPO length noise could directly couple to DARM through intensity noise on the CLF. Since the CLF is off resonance in the OPO, the OPO length fluctuations cause intensity noise on the CLF, which is attenuated by the OMC but could still add noise if large enough. We also have the comparison in the third attachment (below), where the analog gain stayed the same, the CLF was increased and the alignment was improved, but the noise in DARM improved. The DCPD 3MHz demod shows that there is 3dB more 3MHz signal at the time of the yellow trace (3:46:59 Dec 18th), which means the LO loop gain was increased by sqrt(2), so the OPO length noise and the CLF RIN could have been decreased by a factor of sqrt(2). The CLF power reaching the DCPDs was a factor of 4 higher, so if the CLF RIN was the coupling mechanism we would expect the noise to be larger by 4/sqrt(2) ~3 in the yellow trace, but the noise is actually lower, suggesting that the coupling isn't through the CLF RIN. We are planning to revisit 45858, since that projection of CLF RIN to DCPDs was based on a RIN measurement made on ISCT6, before the OPO length noise would have been imposed on the CLF intensity. '
This comparison also suggests that the noise isn't due to seeding that comes through the AOMs in the CLF path, since there would be more seeding when we inject more CLF into the OPO, and when it is better aligned.
The fourth attachment is perhaps a more convincing comparison to see that CLF intensity noise and seeding aren't the cause of noise in DARM. At the time of the mint colored reference (4:33:40 UTC) there was 6dBm more 3MHz signal than at the time of the black reference (4:30:26 UTC), but the LO loop gain would have been kept the same since Nutsinne increased the analog gain by 6dB for the lower CLF power. (The shelf at around 100 Hz is a transient, we were having these kinds of transients which could be fringe wrapping during all of our locks last night).
Here are the times that we used. Some of these were very short measurements.
| Dec 18 2018 UTC | CLF fiber launch power (mW) | DCPD 3MHz power dBm |
| 2:19:13 | reference no squeezing | |
| 2:35:21 | 0.7 mW | -24 |
| 3:46:59 | 0.7 | -16 |
| 3:50:35 | 0.38 | -19 |
| 4:33:40 | 1.018 | -14 |
| 4:30:26 | 0.295 | -20 |
Increasing the CLF power will increase the optical gain in the LO, which will decrease the noise as seen in the first plot. Potentially, this could mask an increase in the noise due to the CLF power.
Daniel agreed with the conclusion of this alog (that the noise is independent of CLF power) after looking again at the 3rd and 4th attachments.
Here is some information that we can use to make some estimates about noise added due to backscatter:
We had 20mA on the DCPD sum at the time of this measurement, the DCPD responsivity is 0.858A/W (45736), so there was about 23.3 mW of carrier heading toward the AS port (I'm not taking into account OMC losses and mode matching)
While in chamber, we measured 620 ppm of the light heading towards the OMC is sent towards the squeezer by the OFI (41229). (about 14.4 uW arriving at the beam diverter or the VIP)
In the optics lab we measured the isolation of the squeezer faraday to be -27.8dB (39897), so we expect about 23 nW of carrier from the interferometer to reach the OPO.
We are planning to work on getting a calibration of the LO error signal into meters of OPO length, so that we can estimate the amount of backscatter from the OPO we would need to explain the noise in DARM. If we get another chance to inject squeezing into the interferometer we plan to try a fringe wrapping measurement and to check how the noise measured on the DCPDs depends on the local oscillator power (by changing the DARM offset).
M. Wade
There was an issue at LHO where the OBSERVATION_READY bit of the ODC-MASTER channel was not reporting properly. Since this is the channel used by the GDS calibration code to determine h(t)-OK in the GDS-CALIB_STATE_VECTOR, in consultation with Keita I made a configuration change so that h(t)-OK is now determined based on OBSERVATION_INTENT instead of OBSERVATION_READY. This change was made and the pipeline was restarted on the DMT machines at GPS time 1228956497.
Thank you very much Maddie.
I also masked out all INJ ODC bits because it was receiving nothing (all zero, meaning all bad, or maybe something else, see top row of the attached) and low latency pipelines were seeing bogus injection flags.
Operators: When H1 unlocks, DOWN state in ISC_LOCK should set H1:ODC-OPERATOR_OBSERVATION_READY back to zero. But pay attention to see if this really happened, and if it doesn't, manually press "commissioning" button in guardian overview.
Also see this LLO alog about their workaround.
https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=42394
Just to facilitate further discussion, I attach screenshots of the guardian overview screen, and the super-manager guardian node called simply "IFO."
This node looks at the "OK" bit of all subordinate nodes (there is an "exclude" list for nodes that we know are bad / non-functional / unimportant / underconstruction), and generates its own bit, called
H1:GRD-IFO_OK
the subordinate nodes include
- a check that all of the automated interferometer control system nodes are in their pre-programmed nominal state (save those that have been excluded),
- a check by DIAG_SDF against *every* switchable EPICs setting (save those intentionally not monitored because they're switched by an above mentioned automated node),
- a check by DIAG_EXC whether there are any unwanted excitations on,
- a check by DIAG_CRIT which checks critical guardian functionality, and
- a check by DIAG_MAIN several other automated checks of observatory conditions.
The other (and only) human-determined bit is the above mention H1:ODC-OPERATOR_OBSERVATION_READY, which is to what we refer to as the "intent" bit, which is set by cognizent operators, engineers, and scientists when they ackowledge that no one is intending to modify or measure the instruement, and thus they believe it is ready for astrophysical consumption to the best of their knowledge.
FYI, before injection bits were masked out, ODC MASTER screen looked identical to this (except the intent bit, which is masked out in the screen shot for some test, but it wasn't masked out in ER13).
23:08 (15:08) Spelling Corey for his last hour
23:30 (15:30) Dave, Richard, Marc back from EX. Problem fixed.
00:00 (16:00) End of shift. Working on initial alignment