The LSC model has been edited to accommodate a normalized REFLAIR9I signal (LSC-TR_REFLAIR9
) alongisde normalized REFL9I (LSC-TR_REFL9
). A switch determines which of these is signals is fed into LSC-REFLBIAS
.
Correspondingly, I have switched back the cabling on the ISC rack so that the demodulated REFL_A_RF9 signals feed into the REFL_A_RF9 whitening chassis, and likewise for REFLAIR_A_RF9.
The guardian scripts, whitening settings, and demod phases are now corrected back to their settings prior to the cable swap.
Wanted to confirm the long runs to the amplified BSC2 Pressure Sensors weren't the main ground noise culprit. Richard plans to add following resistors to the satellite amplifier before the long runs.
Anyway, it does not look like these are making the Pump Station Pressure signals noisy.
Attached is 30 minutes where we disconnected these channels from the servo inputs: Ch3 goes away as the return and supply pressures from BSC2 (Chs7 & 8) are disconnected. The Main Supply pressure, Ch9, shows that the noise level doesn't change during this period. The servo is in free running manual mode.
model restarts logged for Sun 01/Feb/2015
2015_02_01 14:40 h1fw0
2015_02_01 20:06 h1fw0
both unexpected restarts. Conlog frequently changing channels report attached.
Evan, Sheila
We did a little bit of cleaning up today. First edited the IMC guardian to adjust the input gain for different input powers. We though we had implemented this before, but what we had actually wasn't working. I added an if statement in the BOOST step that sets the input gain for 1W, 4W, or 10W. We could have something better which adjusts it for any input power.
We also changed the ISC_CONFIGs guardian to accoun for the cable swap we did on friday night, PRX locked is not using reflAIR in the input matrix, which is really REFL 9.
Evan and I then locked DRMI just to make sure everything is OK with the TCS back on, it locked with no problem, now we are checking demod phases.
Demod phases are as follows. We have not made any changes.
For 9 MHz and 45 MHz, DRMI was locked on 1f, and for 27 MHz and 135 MHz, DRMI was locked on 3f. We drove a 132 Hz line into PRM (and then later SRM) to gauge the suitability of these demod phases.
For the 3f locking, tuning the 135 MHz demod phase to 25° is sufficient to minimize the appearance of PRCL and SRCL in the 135Q phase. However, for the 1f locking, tuning the 45 MHz demod phase to 142° minimizes only the appearance of SRCL in 45Q; for PRCL, the demodulated 45Q signal is about 15% of the demodulated 45I signal. The demod phase required to minimize the apperance of PRCL in 45Q is instead 150° (but this leaves the SRCL 45Q signal at about 15% of the SRCL 45I signal).
Sheila, Evan
We have been changing the PSL power up and down during CARM offset reduction. Among other things, this changes the optical gain of the IMC PDH loop. So far, we've been compensating for this gain using the IMC servo board as follows:
Just to make sure that the IMC loop is still OK in the latter configuration, we took an OLTF by driving a 20 mV swept sine into EXC A and monitoring the test points before and after. The result is attached.
model restarts logged for Sat 31/Jan/2015
2015_01_31 06:40 h1fw0
2015_01_31 08:08 h1fw0
2015_01_31 18:39 h1fw0
2015_01_31 19:04 h1fw0
all unexpected restarts. Conlog frequently changing channels report attached.
Dan, Elli
Today we did a few non-locking things:
As part of this work we changed a few whitening gains. The gain for IM4 TRANS had been turned down to zero because it was saturating from the aux laser for the Schnupp and PRCL measurements. We turned this gain back to 36dB.
Also we increased the whitening gain on the OMC QPDs, they are now 30dB (were 18dB).
Turned on at 1Feb 2:55:22 UTC. .3W requested power, 0.21W registered at the power meter.
I requested central heating, although the H1:TCS-ITMX_CO2_FLIP2MON and H1:TCS-ITMX_CO2_FLIP1MON mon channels are jumping all over the place, we need to fix this. ITMx HWS was runningand shows an increase in the spherical power, which is consistent with central heating.
model restarts logged for Fri 30/Jan/2015
2015_01_30 04:45 h1fw0
2015_01_30 08:03 h1fw0
2015_01_30 11:02 h1fw0
2015_01_30 17:27 h1fw1
C1PLC1 7:54 1/30 2015
C1PLC2 7:54 1/30 2015
C1PLC3 7:54 1/30 2015
unexpected daq restarts. Beckhoff corner station restart for fast shutter install. Conlog frequently changing channels report attached.
Alexa, Elli, Sheila, Kiwamu, Rana, Evan
With CARM controlled by a combination of sqrt(TRX+TRY) and TR_REFL9 (i.e., REFL9I normalized by TRY), we've achieved a power buildup in each arm that is 800× the single-arm buildup. We believe this corresponds to a CARM detuning of 5 pm.
At this point, REFL_A_LF is at about 2.3 mW, compared to 40 mW when the arms are anti-resonant. If this is truly an indication of the power reflected back from the PRM, this means that the visibility of the interferometer is in excess of 90 %. We do not have TCS on today.
One major roadblock to further progress seems to be angular instability that is seen at the AS port. We have ASC feedback from AS_B_45_Q to ETMX and ETMY, but the bandwidth is too low to suppress the 1 Hz motions that we see. We may need to spend some time increasing the WFS bandwidth, or resort to more aggressive oplev damping.
A laundry list of things we've done today to troubleshoot the transition:
Based on the measured losses in the arms (an average of 110 ppm), we expect an interferometer recycling gain of 32 W/W and a coupled cavity pole of 0.6 Hz (i.e., 9 pm) [using eqs. 6 and 8 from Fritschel et al. 2001]. Therefore, we believe that the arm buildup should be about 1000× the single-arm power with CARM at 0 pm. This is consistent with earlier estimates made by others (LHO#15390, T1000294).
A list of transition steps not yet implemented in the guardian:
Our last three attempts are 11:24:48 UTC, 11:00:27 and 10:37:35 Jan 31.
On oplev damping:
* I turned on the usual f^1 velocity damping, but since it measures the mirror angle and feeds back to the PUM, this is not a very good loop. Turning up the gain excites the 2nd pitch mode.
* In some of these suspensions, there are bad, high-Q filters called 'invP2P' or 'invY2Y'. These kind of invert the plant, but cause us much trouble since they ring for so long. These are not appropriate for the kind of system we have where the plant Q changes (due to damping loop changes) and frequency shifts (due to radiation pressure). With a little sloppy plant inversion we could have a higher BW and squash all of this excess pitch motion during the lock acquisition. Probably much easier than getting high BW WFS at this point.
On the third attachment above, you can see the unfortunate wire heating issue: the SR3 drifts by ~0.5 urad in 4 minutes after the lock loss. It also exponentially drifts up once we ramp up the power in the IFO.
The dark port is not very dark here, but still this seems strange. Some related info on this from LLO by searching for the phrase 'PR3 drift'. Hopefully we can combat this with some 'cage servo' or WFS rather than make an SR3 wire baffle.
New models have been prepared for the splitting the end station isc model:
The old h1iscex and h1iscey are still the default. To activate the new split models, h1iscex_new and h1iscey_new need to be renamed, the IPC file copied over chans/H1.ipc, and then everything recompiled. All in svn.
J. Kissel, R. Adhikari, S. Dwyer, By happenstance calling for another reason (see LHO aLOG 16390), Rana and Sheila informed me of woes at ETMX: a sudden trip, some further trip, followed by more trips of the watchdog. Unsure of what was going on, they had mashed a bunch of buttons in attempt to fix the problem. After some remote MEDM'ing, I could tell that the BRS-rotation-corrected, GND X STS signal had gone bonkers, which was being used as the X -direction Sensor Correction signal since Krishna had resurrected the BRS earlier this afternoon (see LHO aLOG 16380). I've since switched the STS2CART input matrix to use the normal X-direction STS signal for sensor correction (changed the STS2CART matrix to use STS B for X input to sensor correction instead of STS C). I'm not sure what's gone wrong with the BRS (too difficult to diagnose remotely), we'll figure that out later. Further, Sheila and I used the SDF system to restore all of the button mashing they'd done. Now only the expected differences from "nominal" remain -- my switch of the STS2CART input matrix, and Krishna's turning on the outputs of the Rotation and Torque correction paths for the STS. Again, the latter no longer has any impact because this GND super sensor output is no longer being used. I second Hugh's love of the new SDF system!
this is the first trip
I've attached the BRS output trend for the last ~day and the problem is clearly visible at ~4:00 UTC. As I'd mentioned in the previous alog, BRS was outside of its nominal range. When the BRS gets close to the edge of it's range, the subtraction between the reference and the main pattern doesn't work right and produces spikes in the output, which is what seems to have happened. It was a mistake to leave it running in the sensor correction loop in this state and I apologize for it.
On Tuesday, during maintenance, I will change the set-point of the balance physically to bring it in range.
Kiwamu, Sheila, Rich, Daniel, Rana
We are close to saturating REFL_A_RF9 during our hand-off attempts from sqrt(TRX+TRY) to REFL9I.
For the time being, we are switching to REFLAIR_A_RF9 for the handoff. Sheila and Rana have done some rewiring on the ISC rack so that the I&Q demodulated outputs of REFL_A_RF9 are replaced by REFLAIR_A_RF9.
The attachment shows the 9 MHz rms monitors for REFL_A and REFLAIR_A during a lock acquisition attempt. After some discussion, Rich and Daniel have concluded that the RF monitor channels are calibrated into dBm, as measured at the output of each PD with a 50 Ω load. REFLAIR_A is sitting comfortably below −10 dBm. REFL_A, however, peaks as high as +15 dBm. The amplifier in the RFPD is an LMH6624, for which the minimum output swing is reported as ±4.4 V into 100 Ω. Since the amplifier has a 50 Ω series resistor on its output, that's 20 dBm of power delivered into a 50 Ω load. If we want to keep distortion to a minimum, we should stay well below this limit.
we swapped the the I&Q cables at the demod board side, so the REFL_VAC I&Q now go into the AA inputs for REFLAIR and vice versa. This seemed more sensible than doing the RF, since that would introduce weird phase shifts. We then swapped the digital demod phase numbers between the REFLAIR and REFL_A screens so that the demod phase follows the cables.
I'm confused as to why you needed to move cables. Wasn't the REFLAIR signal already going to the CM Summing Module, so you could have used that path? How about a diagram of the setup?
Rightly so. We forgot to mention why we did this...
The LSC model wasn't wired to permit normalization of REFLAIR with sqrt(TR), so we swapped cables rather than rebuild the model and risk that kind of fallout. We should change the model to allow this and swap the cables back eventually.
I updated the GUARD_OVERVIEW and the IM/TT medm screens to contain micro/mini Guardians for IM1, IM2, IM3, IM4, RM1, RM2, OM1, OM2, OM3. The scripts were already made available by Stuart Aston and Jameson Rollins at LLO see https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=15772 and also https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=15585. The Guardian Nodes were not yet created though so I had to create those and figure out that they also had to be started.
Currently RM1, RM2, OM1, OM2, OM3 do not have any offset.snap files saved to them in userapps/sus/h1/burtfiles/ (hence the red border on the Guardian Minis in the overview screen shot).
Attached are the before and after of the GUARD_OVERVIEW.adl screens along with the new HAUX and one of the new HSSS IM screens.
The red boarder actually indicates an ERROR with the node. If there's not actualy ERROR conditions in those nodes, then there might be a version incompatibility between the version of guardian in use and the indicator screen.
I'll help resovle this issue when I'm on site tomorrow.