Related logs, 31303, 31371, 31403
Jeff, Kiwamu,
We have copied the actuator function plotting script from LLO and adopted for LHO. The code seems to run fine. It resides at
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/Scripts/FullIFOActuatorTFs/actuatorCoefficients.m
The attached are the resulting pdf showing the three sets of measurements that Jeff took in the past few days. I did not do fittin yet. Below are several notes
/ligo/svncommon/CalSVN/aligocalibration/trunk/Runs/ER10/H1/params/H1params.confquadmodelproduction-rev7995_ssmake4pv2eMB5f_fiber-rev3601_h1etmy-rev7915_released-2016-06-15.matquadmodelproduction-rev7995_ssmake4pv2eMB5f_fiber-rev3601_h1etmy-rev7915_released-2016-03-01.matJeff K, Darkhan T,
Modified Kiwamu's script to save the measured actuation transfer functions - which will be used to fit the actuation function parameters (currently written in Python). The results include TFs from Nov 07, 08, 10 and 12. The Nov 12 measurements were added to the previously reported three sets (see LHO alog 31433).
The script also saves the [N/ct] actuation coefficients into a separate set of *.txt files (frequency independent), this can simplify fitting a single parameter - actuation strength for each of the stages.
The clean transfer function *.txt files were uploaded to CalSVN at (files with postscript N2ct have [N/ct] gain values):
${CalSVN}/Runs/ER10/H1/Measurements/FullIFOActuatorTFs/${date}_coefs/*Actuation_measurement.txt
${CalSVN}/Runs/ER10/H1/Measurements/FullIFOActuatorTFs/${date}_coefs/*Actuation_measurement_Npct.txt
The script that generated the txt files was placed here:
${CalSVN}/Runs/ER10/H1/Scripts/FullIFOActuatorTFs/actuatorCoefficients_Npct.m
Operator task request
Now that we're at lower power, we'd like to double check what PI's actually need to be damped. We still have damping settings set up on all the modes that rang up while at 50 W, but it looks like most of them are no longer actually needed. I trended the past several days of locks and only Modes 26, 27, 28, (and maybe 3) rang up enough to engage their damping loops. We'd like to turn off the damping for the other modes and watch and make sure that they really don't need it.
To check:
1. Once you've passed DC READOUT, guardian has turned on all the usual PI gains. Write the gains down (or I've put them in the comment below) so that you can quickly put these values back in if needed.
2. Set the gains of Modes 1 - 25 (edited to now include keeping Mode 3 on) 1, 2 , 4 - 25 to zero. Do Not zero Modes 3, 26, 27, 28 as we are definitely actively damping those. Just do this directly on the main PI medm screen under the 'gain' column.
3. Watch the modes throughout the lock. The StripTool will still give the same ring up info as always and the DTT screen is a good way to keep an eye on if something is growing.
4. If a mode starts to clearly ring up, put back in the original noted gain value and damp as usual. Make a note in the log.
I've chosen not to just auto set the gains to zero already in case the operator is busy for now. Let's get a few longer locks that are more closely watched and confirm we really dont need damping on.
| Mode | Gain |
| 2 | 5000 |
| 3 | -3000 |
| 9 | -1000 |
| 10 | -1000 |
| 17 | 1000 |
| 18 | -5000 |
| 25 | -1000 |
| 26 | -3000 |
| 27 | 5000 |
| 28 | 3000 |
Fil, Jim We replaced the ADC0 card, ribbon cable, and interface card in the h1oaf0 I/O chassis after the last failure of the ADC/DAC. We also moved the h1oaf0 timing fiber and SFP on the timing fanout from port 1 to port 13. (This causes an error status on the Beckhoff timing MEDM screen, which shouldn't cause problems.) After startup, we noted that the timing status on the IOP model flashed several times, this can be observed in a raw data plot of the H1:FEC-23_STATE_WORD channel for 10 minutes ending at GPS 1162946454. See attached plot. We have not seen this behaviour previously. Present status: h1oaf0 I/O chassis replaced with x1psl0 DTS I/O chassis, but using all ADC/DAC/BIO and interface cards with the exception of ADC0 and interface card, which were replaced with a set from the x1psl0 I/O chassis.
State of H1: locking well, OAF issues
Activities:
Currently:
Cheryl's idea was very clever; we now have ~1 min PI damping downtime which is no problem and have made it through several restarts without PI being a problem.
In an effort to get the h1oaf0 to run reliably, Fil and I replaced the I/O chassis with the x1psl0 chassis from the DAQ test stand, which has been the most reliable. We used the same ADC/DAC/BIO cards as were in the original h1oaf0 I/O chassis. The ADC/DAC failed within 5 minutes. Next we will try swapping ADC0 and it's interface card.
2:44pm local Filled CP3 from control room today! Took 26 min. Set LLCV to 50% open (from 20%) and monitored the two thermocouple readings on MEDM. Since it took so long I increased nominal to 21%. CP3 Dewar is scheduled for fill on Tuesday.
T240:
Averaging Mass Centering channels for 10 [sec] ...
2016-11-11 12:46:08.555164
There are 4 T240 proof masses out of range ( > 0.3 [V] )!
ETMY T240 3 DOF Z/W = 0.328 [V]
ITMX T240 1 DOF X/U = -0.47 [V]
ITMX T240 3 DOF X/U = -0.46 [V]
ITMY T240 3 DOF Z/W = -0.743 [V]
All other proof masses are within range ( < 0.3 [V] ):
ETMX T240 1 DOF X/U = 0.093 [V]
ETMX T240 1 DOF Y/V = 0.075 [V]
ETMX T240 1 DOF Z/W = 0.105 [V]
ETMX T240 2 DOF X/U = 0.088 [V]
ETMX T240 2 DOF Y/V = 0.054 [V]
ETMX T240 2 DOF Z/W = 0.111 [V]
ETMX T240 3 DOF X/U = 0.051 [V]
ETMX T240 3 DOF Y/V = 0.022 [V]
ETMX T240 3 DOF Z/W = 0.061 [V]
ETMY T240 1 DOF X/U = -0.03 [V]
ETMY T240 1 DOF Y/V = -0.014 [V]
ETMY T240 1 DOF Z/W = -0.2 [V]
ETMY T240 2 DOF X/U = 0.204 [V]
ETMY T240 2 DOF Y/V = -0.201 [V]
ETMY T240 2 DOF Z/W = 0.011 [V]
ETMY T240 3 DOF X/U = -0.221 [V]
ETMY T240 3 DOF Y/V = -0.04 [V]
ITMX T240 1 DOF Y/V = 0.237 [V]
ITMX T240 1 DOF Z/W = 0.179 [V]
ITMX T240 2 DOF X/U = 0.245 [V]
ITMX T240 2 DOF Y/V = 0.204 [V]
ITMX T240 2 DOF Z/W = 0.232 [V]
ITMX T240 3 DOF Y/V = 0.177 [V]
ITMX T240 3 DOF Z/W = 0.212 [V]
ITMY T240 1 DOF X/U = 0.135 [V]
ITMY T240 1 DOF Y/V = 0.036 [V]
ITMY T240 1 DOF Z/W = 0.036 [V]
ITMY T240 2 DOF X/U = 0.071 [V]
ITMY T240 2 DOF Y/V = 0.172 [V]
ITMY T240 2 DOF Z/W = 0.163 [V]
ITMY T240 3 DOF X/U = -0.195 [V]
ITMY T240 3 DOF Y/V = 0.171 [V]
BS T240 1 DOF X/U = 0.028 [V]
BS T240 1 DOF Y/V = 0.053 [V]
BS T240 1 DOF Z/W = 0.202 [V]
BS T240 2 DOF X/U = 0.135 [V]
BS T240 2 DOF Y/V = 0.184 [V]
BS T240 2 DOF Z/W = 0.174 [V]
BS T240 3 DOF X/U = 0.031 [V]
BS T240 3 DOF Y/V = 0.082 [V]
BS T240 3 DOF Z/W = -0.014 [V]
Assessment complete.
---------
STS:
Averaging Mass Centering channels for 10 [sec] ...
2016-11-11 12:47:53.351902
All STSs prrof masses that within healthy range (< 2.0 [V]). Great!
Here's a list of how they're doing just in case you care:
STS A DOF X/U = -0.537 [V]
STS A DOF Y/V = -0.053 [V]
STS A DOF Z/W = -0.503 [V]
STS B DOF X/U = 0.098 [V]
STS B DOF Y/V = -1.23 [V]
STS B DOF Z/W = -0.064 [V]
STS C DOF X/U = -0.0 [V]
STS C DOF Y/V = -0.0 [V]
STS C DOF Z/W = -0.0 [V]
STS EX DOF X/U = -0.21 [V]
STS EX DOF Y/V = 0.553 [V]
STS EX DOF Z/W = 0.086 [V]
STS EY DOF X/U = 0.027 [V]
STS EY DOF Y/V = 0.315 [V]
STS EY DOF Z/W = 0.298 [V]
Assessment complete.
WP 6314 Fil, Jim In an attempt to stabilize the h1oaf0 ADC/DAC issue, Fil and Jim replaced the DC power supply in the h1oaf0 I/O chassis, and reseated all ADC, DAC, BIO, and interface cards in the chassis. Start time 9:31, power up of I/O chassis at 9:55. The first attempt at starting the models resulted in ADC and DAC errors like we've seen, and the IRIG-B time going negative. The models were killed, then restarted manually to watch for issues. The models started OK on the second attempt. Note that the TCS AI chassis was powered down during this work, and was powered back up once the h1tcscs model was running. We avoided tripping the TCS laser chillers.
H1 was in NLN, but the OAF issues is pressing, so I killed the H1 lock and Jim and Fil are reseating the OAF card in hopes that this will return OAF to it previously stable running.
TITLE: 11/11 Owl Shift: 08:00-16:00 UTC (00:00-08:00 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Cheryl
SHIFT SUMMARY: Locking has been very straight forward tonight, two lockloss from unknown reasons, but other than that I have been in observing. Sheila suggested that I wait at NOISE_TUNINGS for 10-15 before moving on, you can run a2l while waiting. ITMY is still swinging, but not as much as I saw last weekend.
LOG:
The other night I ran Stefan's spot move script, which tracks the alignment of all optics based on the combination of ASC control signals and sliders. Tnight I tried to imitate that move of the interferometer alignemt by moving IMs, by moving IM1 I was able to see a small improvement in recycling gain, (from about 30.7 to 30.8) but no improvement in the 260Hz jitter peak. I started trying to move IM2, but moved too quickly and broke the lock.
When I moved the IMC DOF1P offset to 120 counts this is how the other optics moved:
PIT: SUS-IM1_M1_ 0.0
SHIFT SUMMARY: Commissioning all evening. Oaf computer crashed at least twice this evening. Dave created a script to kill and restart the model that can be un anywhere from ops computer. Just do ./restart_h1oaf0_models.bsh. Be mindful that when the models are being restarted PI won't be damped. So be ready to damp PI after every oaf restart because some of the modes will come back high every time.
We measured the pitch refl sensing matrix for PR3, IM4 and CHARD again, and adjusted the input matrix for PR3 a little. This helped to keep our sideband build ups much mroe stable after we transitioned to it and the interferometer seems stable like this so far.
The old matrix for PR3 was 0.08 REFL B 9I -0.08 REFL B45 I. THe new matrix is 0.1 REFL B 9 I -0.0768 REFL B 45I
It seems like we are on the edge of the recycling gains where the REFL WFS have a decent signal for PR3, so that the matrix we need to use changes with the recycing gain. We've had a couple more locklosses when switching to the new matrix, but it seems to work if we wait ~15 minutes after powering up to try the switch, but it works if we . I"ve moved the switch from POPX WFS to a new state called PR3_REFL_WFS, so that operators can easily skip it and beam diverters if they need to. For now I will leave it in the guardian with the advice to operators to wait a while before trying it. If you are having locklosses quickly after this state, then skip it and skip the beam divereters as well.
To speed up the restart we have created an SSH key-pair between the operator station and h1oaf0, and written a script to kill and restart the models in the correct sequence.
1. log into operator0 as user ops (password in shared secrets)
ssh ops@operator0
2. run script
./restart_h1oaf0_models.bsh
When the models are running again, at the bottom of the CDS Overview MEDM press the buttons "!Press All Diag Reset Buttons" and "!DAQ Clear Accumulated CRC" to green up the board.
If problem persists, we will do more hardware investigations tomorrow
[Terra, Jenne, Cheryl, Nutsinee]
When the OAF model requires a restart during a full 25W lock, the parametric instabilities lose their damping during the reboot (since the damping stuff lives on that computer). Unfortunately, the PIs ring up badly enough during the short time it takes to boot that we lose lock shortly after the computer goes down for a restart. This is the 2nd time today that we've seen this. Despite Cheryl's efforts when this happened during the daytime, and Nutsinee's efforts just now, the modes are just too high for the damping to work.
So. Obviously the CDS team is already working on figuring out why the oaf computer is so unhappy, but I just wanted to highlight that even if we reboot before the TCS trips, we still lose lock due to this hardware problem.
Previously the PI gain SDF setpoints were set to zero since guardian turns on gains at DC READOUT. Both model restarts today happened at NLN, so when the PI model restarted it was setting the damping gains to zero (since we weren't moving through DC READOUT), so I've changed the setpoints to the final gain settings. Correct PI gains should now turn on even with a restart in NLN. Note that Jenne's comment above still stands; this past restart Nutsinee and I immediately set gain settings back upon restart but the modes were still too rung up as Jenne said.
We measured the REFL signals at 2W with the ISS second loop engaged and off (REF traces). The RF signals measure residual RF modulation (RAM), whereas LF measured the RIN. The REFL PD sees about a factor of 10 more light than the ISS second loop PDs when unlocked.
There seems to be a wide scatter peak at ~16.5 Hz. The 9 MHz demodulated signal shows some strange smooth excess noise below 100 Hz, whereas the 45 MHz seems to see more of the jitter peaks. The 9 MHz signal has been scaled to give the same digital and electronics gain as the 45 MHz. The transimpedance gains are very similar to start with.
The 16.5 Hz peak appears to be the same one reported about two years ago in 15223. That peak is caused by scatter of the REFL beam that is transmitted by IM4, goes out the viewport and onto IOT2R. It might be worth checking if the beam dumping on IOT2R is as good as it can be. Longer term, this beam should be dumped in vacuum, on HAM2 (this was done at LLO in the post-O1 vent).
We measured 12.9 mW with 2.0 W input, when the PRM is aligned, but the interferometer is not locked. This scales to Punlock ~ 160 mW at 25 W.
When locked and after the modulation index reduction for the 9 MHz RF, we have about Plock ~ 2.2 mW of light, which is carrier dominated.
To calibrate the REFL_LF in RIN we need to divide the signal by √ Punlock x Plock ~ 18.8 mW.
The shot noise in units of RIN is then √ 2 h ν Plock / √ Punlock x Plock = √ 2 h ν / Plock .
When we are locked at 25 W, the second loop ISS diodes are exposed to 15 mW and 16.5 mW for inner and outer, respectively.
This makes REFL_LF a better sensor for relative intensity noise measurements by about a factor of 3.
Here is a measurement of the REFL signals when locked at 25 W. The reference traces are measured with 2 W and unlocked (no second loop ISS).
The red horizontal cursor corresponds to the ISS second loop shot noise. It is well reproduced by REFL_LF between 200 Hz and 3 kHz. One striking feature is the 260 Hz periscope peak that is suppressed by the ISS near shot noise level, but shows up again much stronger in REFL_LF. This peak is most likely regenerated in the interferometer from the jitter and an rms common misalignment. The situation is a little different for the set of peaks around 4 kHz. It looks like they appear weaker in REFL_LF, as if they get regenerated but with a negative sign, so that their amplitudes subtract.