[JeffK, Sheila, Jenne]
The bounce mode has been giving us extra trouble today. In the end, we used a very fine bandwidth spectrum to confirm that it really was ITMY's bounce mode (as the monitor bar graph was telling us). We tried out some different phases, and ended up with some settings that are now working. When I went to put the new settings into the guardian, I found that these exact filters had once been used for ITMY, but had been commented out and changed. I'm not sure how long ago this happened, but it was at least before Sheila made the gain=-1 filters, so that the numerical gain is positive for all test masses, since that filter wasn't included in the commented-out settings.
So. Why did the damping phase change some time ago, and why did it change back? Unknown.
15:43 Cleaning crew headed to mid stations
15:47 Keita doing ISS measurements
16:31 Karen leaving MY
16:43 Jim headed to EX to tame the BRS beast
16:48 Kiwamu to LVEA to check TF of ISS loops
16:50 Christina left MX
17:01 Jim back. Report is damping was turned off last night to allow ring down(didn't happen). At this point no correcive action has been taken.
17:08 Kyle to MY
17:33 Chandra and John to head to MY
17:34 Kiwamu out of LVEA. We can return to locking
17:45 Jeff K restarting CAL_CS model
18:18 John and Chandra are back
18:25 Kyle back from MY
21:03 Kyle Gerardo and Chandra going to MY
21:49 Kyle Gerardo and Chandra back from MY
22:30 Tour group into control room
Nothing here looks out of the ordinary.
Here is some of the data from Saturday's jitter injections (29780), plotted differently. The main point is that we should be able to reduce the yaw jitter coupling by at least a factor of a few, and this should help the DARM spectrum, but not enough to get the noise a factor of 10 belpw the quantum noise with the current level of jitter.
I have taken open loop transfer functions of the 1st loop in this morning to see where the UGF currently is.
Based on the measurements, I set the gain slider in the medm to 9 dB which gives us a UGF of 50-60 kHz.
Also, the raw data is attached as a zipped file.
Apart from these measurements, I confirmed two features as follows.
During the measurements, I kept the suspiciously high offset value of 20 for the 1st loop. The second loop was off.
I added 125 mL to the crystal chiller. I noted that the fill port water is very turbulent, swirling and full of air bubbles. I recall that it is usually calm.
FAMIS 6489.
Dave, Darkhan, Jeff:
A code bug in the file cds/common/src/BUFFER_AND_AVERAGE.c was fixed and h1calcs was restarted. No DAQ restart was required. This is the only model which uses this file.
Dan, Jim W, Sebastien, Dave:
While Sebastien was visiting LHO during the past week, we performed a test install of the MIT (Sebastien and Michael C.) earthquake arrival predictor code (seismon). Here is a summary of the install work so far:
We are using the spare CW injection computer, Dan M. upgraded this system from SL6.7 to SL7.2 last week.
The software install is in two parts: the USGS client system which periodically downloads seismic data from USGS, and the python code which analyses this data and issues local alters.
The USGS client code (based on java) was installed last Friday and have been running continuously since then. The connection between CDS and USGS is initiated internally for security reasons.
Today we got the seismon_traveltimes python code running, which for earthquakes with magnitude > 5.0 provides predicted arrival times (for each of; p-wave, s-wave, 3XRayleigh waves), predicted maximum velocity and surface distance from eq-source to LHO.
I'm working on scripts to run this continuously with a time resolution of about a minute, and to export these data as EPICS channels.
After a period of testing, we will decide how this system will be installed permanently on site (e.g. dedicated computer, integrated EPICS IOC)
John, Chandra Overfilled CP4 today while monitoring exhaust pressure and flow (from control room). -Manually set LLCV to 66% open (double nominal value) -Took 17 min. to fill to 100% (started at 90%) -Took another 60 min. to see a drastic change in flow and pressure beyond 100% full (i.e. cooling exhaust line) *constant 66% open -When exhaust pressure spiked to ~6 psi (flow meter spiked to ~480 slpm) we terminated the experiment and lowered LLCV to 20%, then 10% -Kyle reported the new plastic flex line froze and all exhaust pipe was cold to the touch. Flow meter read -5decC. -John and I measured uninsulated exhaust line temp afterward: -8degF where pipe exits building (lots of frost build up) and ~26degF several feet downstream We will repeat experiment tomorrow morning after exhaust line warms up but this time run until LN2 flows out end of exhaust line. We will install one or a few thermocouples along exhaust line.
SudarshanK, TravisS, RickS
Yesterday, we went to Xend to assess and optimize the Pcal beam locations on the ETM surface.
Since O1, we have known that the beams were clipping somewhere on the receiving side.
Unsing an updated method of assessing the beam locations that is based on the work that Miranda Chen (REU student from UTRGV) did this summer (basically using the ESD electrode pattern rather than the edge of the ETM) we found that the Pcal beams were quite far from their optimum locaitons (see first image attached below). The offests from the optimal locations (111.6 mm above and below the center of the face of the optic) were U [ 1.71, 12.27], L[10.02, -7.27] where U and L denote the upper and lower Pcal beams and the coordinates are [x offset, y offset] in millimeters with the usual conventions, positive x to the right, positive y up. Because we use 2" diameter optics in the Pcal periscope structure and because the receiveing-side mirrors are twice the distantance from the ETM, an offset of 12 mm at the ETM would correspond to an offset of ~24 mm at the periscope, likely the cause of the clipping we have observed. The reflected power measured by the power sensor in the receiver module increased by about 50% from about 4 V to 6.2 V.
We adjusted the beam locations using the steering mirrors in the Pcal transmitter module and ended up with positions that are within a mm of the optimal locations (see second image attached below): U [ 0.15, 0.43], L[-0.18, 0.05].
The third image below shows the Pcal spots on the ETM surface (inside green circles), visible when the chamber illuminator is off.
We are in the process of modeling the expected calibration errors resulting from bulk elastic deformation induced by the Pcal forces being so far from the optimal locations, but we expect errors as large as 20-40% at frequencies above 4 kHz for offsets as large as what we had before correcting the positions yesterday.
Attached is a plot that shows the expected calibration error at higher frequencies due to the effect of bulk elastic deformation of the test mass. The estimated error is calculated using the COMSOL modeling (worked on by Nicola and Shivaraj this summer) for the pcal beam configuration prior to moving the beam (LHOX_ER9). This is the same configuration in which we were running the the high frequency calibration lines during ER9 and even during O1 (there is no reason to believe the beam positions have changed appreciably since O1). The measurement data plotted alongside are the high frequency calibration lines run during the end of O1 and described in LHO alog 26275. The data is normalized to the model at 1 KHz and agrees closely to the model at frequencies above it. The beams are now moved to their optimal position as described above. The model shows smaller error (plotted in cyan) due to bulk elastic deformation for this optimal configuration (LHOX_ER10). Similar measurement will be done during and before ER10 in order to confirm the model.

Note that the movement of the beam on the ETM, per quarter turn on the adjustment knobs of the mirror mounts in the tramsmitter module, is about 10 mm (judging by what we experienced yesterday).
If one works out the numbers using the 100 TPI actuators in the mount and the 1.5" between the actuator and the pivot point, the result is about 12 mm per quarter turn, assuming the mirror is about 7 m from the mount. It might be closer to 8 meters given the distance from the mirror mount to the periscope and the path in the periscope (larter for the lower - outside - beam).
11am local 28 sec. to overfill CP3 with 1/2 turn open on bypass LLCV (bypass exhaust valve remains open) Next fill due Fri.
It looks like the code restarts yesterday made BRSX upset. Right now, the DRIFTMON channel is swinging about 10k counts, p2p. Krishna suggests "several thousand" is too high for the damper to be useable. It sounds like I'll need to re-center the table, after the BRS has settled down some. We'll keep monitoring, but for now the SEI_CONF manager needs to be left in a state that doesn't use BRSX, currently in WINDY_NOBRSX, though VERY_WINDY and some of the earthquake states will work as well. TJ has confirmed that with the BRSX_STAT node in error, SEI_CONF will not complete a transition to a state that uses the BRSX, but a code restart or INITing SEI_CONF could get around that.
Attached trend shows that trouble started around 18:30 UTC yesterday, which I think is about the time we did several restarts of the BRSX Beckhoff.
Attached is the OLTF in two configurations with 7dB VGA gain.
50W (actually 48W), AC coupling OFF, and boost ON (solid line)
50W (actually 48W), AC coupling ON, boost OFF (dashed).
UGF is about 9kHz with phase margin of 40 deg or so (boost ON) or 50 (boost OFF).
Boost buys us about 9dB more gain at 1kHz.
I asked Kiwamu to do an analog measurement up to higher frequency on the floor.
Here is a transfer fucntion with SR785 to check the high frequency portion.
Also, the attached zip contains the data, plot script, and figure.
Taking this data I looked at modifications to the ISS board to increase its bandwidth. The attached plot shows:
Adding the 20kHz zero is a no brainer, since it only requires to limit the dominant pole in the circuit. It improves the phase margin over the measured curve and allows the ugf up to move to 20kHz. This will increase the ISS gain by 2 at 1kHz. The increased ugf and phase margin will in turn allow us to move the knee of the boost higher with the option to add a second boost. The later two solutions will add another gain of 2 at 1kHz.
We engage the ISS boost twice today in low noise, and did not see any impact on the DARM noise. We expected an improvement at 1 kHz at least. Attached are before and after spectra of the in and out of loop diodes (at least that's what I think the new cahnnel names mean). If it is correct that INNER means in loop and outer means out of loop, we are sensor noise limited at 100 Hz with the boost on.
J. Kissel, K. Izumi Kiwamu and I sat down again this morning to review the suspected sign error in the L3 / TST / ESD path in the calibrated output (see LHO aLOG 29860). He's convinced me -- just like what had happened in July (LHO aLOG 28396) -- after the most recent flip of the ETMY L3 ESD bias sign (LHO aLOG 29397), although I had accounted for all of the digital changes in the L3 path, I did not change the replica of the actual to reflect the real actuation strength sign flip. Several decisions have been made so as to prevent this problem in the future: (1) We've decided against changing anything in the CAL-CS front-end calibration for future ESD bias sign flips. In the real ETMY L3 path, when the ESD bias sign is flipped, it changes the sign of the real-world ESD actuation. As such we compensate that change by changing the sign of the gain in the L3_DRIVEALIGN_L filter bank. In doing so, that means there's no change in the overall LSC super-actuator transfer function. Because there is no change in the overall transfer function, we therefore do not need to change the replica of the path in CAL-CS. In the past, we've changed the CAL-CS replica to save our sanity aesthetically -- such that, for example, we can look at the DRIVEALIGN matrix gain in both the actual ETMY SUS and in CAL-CS and they match. But if one does so, one MUST change the sign of the real ESD (H1:CAL-CS_DARM_ANALOG_ETMY_L3_GAIN). This is what was not done in July, nor was it done in late August, because there's no digital equivalent in the control system to remind me. In light of us (well, me) failing to keep this replica path correct, forgetting to code up a setting change here or there every time, we find the cons of keeping things aesthetically the same out-weighing the pros. We will no longer touch the CAL-CS calibration settings when we flip the bias sign in the future. (2) We've removed all CAL-CS changes from the ISC_LOCK guardian. While assessment and control system compensation for the bias flip still live in the ISC_LOCK and SUS_PI guardians, we've removed all modification to CAL-CS settings from the ISC_LOCK guardian. We've remove execution of these steps by commenting out the relevant lines in the ISC_LOCK guardian: # Check for BIAS flip on ETMY # Note that SUS_PI guardian also is affected by ETMX Bias Flipping. # There are checks and appropriate actions in there too. -Kissel, Hardwick 08/31/2016 if ezca['SUS-ETMY_L3_LOCK_INBIAS'] < 0: # ezca['SUS-ETMY_L3_ESDOUTF_UL_GAIN'] = +1 # Commented out after finding that compensating for the # ezca['SUS-ETMY_L3_ESDOUTF_LL_GAIN'] = +1 # Bias flip down stream of the linearization just does # ezca['SUS-ETMY_L3_ESDOUTF_UR_GAIN'] = +1 # not work. # ezca['SUS-ETMY_L3_ESDOUTF_LR_GAIN'] = +1 ezca['SUS-ETMY_L3_DRIVEALIGN_L2L_GAIN'] = -30.0 ezca['SUS-ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = -124518.4 # ezca['CAL-CS_DARM_FE_ETMY_L3_DRIVEALIGN_L2L_GAIN'] = -30.0 # Commented out after second occurrence # ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_UL_GAIN'] = +1 # of overall sign error in L3 path of # ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = -124518.4 # CAL-CS. LHO aLOG 29868. # ezca['CAL-CS_DARM_ANALOG_ETMY_L3_GAIN']= -1 else: # flip everything. # ezca['SUS-ETMY_L3_ESDOUTF_UL_GAIN'] = +1 # Commented out after finding that compensating for the # ezca['SUS-ETMY_L3_ESDOUTF_LL_GAIN'] = +1 # Bias flip down stream of the linearization just does # ezca['SUS-ETMY_L3_ESDOUTF_UR_GAIN'] = +1 # not work. LHO aLOG 29397. # ezca['SUS-ETMY_L3_ESDOUTF_LR_GAIN'] = +1 ezca['SUS-ETMY_L3_DRIVEALIGN_L2L_GAIN'] = +30.0 ezca['SUS-ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = +124518.4 # ezca['CAL-CS_DARM_FE_ETMY_L3_DRIVEALIGN_L2L_GAIN'] = +30.0 # Commented out after second occurrence # ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_UL_GAIN'] = +1 # of overall sign error in L3 path of # ezca['CAL-CS_DARM_FE_ETMY_L3_ESDOUTF_LIN_FORCE_COEFF'] = +124518.4 # CAL-CS. LHO aLOG 29868. # ezca['CAL-CS_DARM_ANALOG_ETMY_L3_GAIN']= +1 ezca['SUS-ETMY_L3_LOCK_BIAS_GAIN'] = 1 Attached is a screen shot of the relevant MEDM screens to aide discussion.
I took a quick look at six hours of 30-minute SFTs automatically created by FScans this morning (thanks for setting the intent bit!), to see if recent line mitigation attempts have reduced the amplitude of the 1-Hz and other combs at low frequencies. Unfortunately, the low-frequency noise floor is too elevated to say much yet about that mitigation success, but in the band 28-32 Hz, where last night's noise is lower, there do seem to be fewer and lower-level lines, including reduced amplitudes for the 1-Hz comb with a ~0.25-Hz offset. Please note that the 56.84-Hz comb reported in the ER9 data (present but weaker in O1 data) remains quite strong. There are other strong lines present, too, but I gather noise-hunting is just getting started. The 56.84-Hz comb suggests a DAQ problem somewhere, as noted before. The attached plots show different bands of O1 data (narrow black curves) superposed on last night's data (broad red swath). In each case, an inverse-noise weighting is used, to suppress periods of elevated noise. Figure 1 - 10-2000 Hz Figure 2 - 10-28 Hz Figure 3 - 28-32 Hz Figure 4 - 32-50 Hz Figure 5 - 50-100 Hz Figure 6 - 100-200 Hz Figure 7 - 200-1000 Hz Figure 8 - 1000-2000 Hz
Ansel just brought to my attention this alog entry by Robert identifying a 56.8-Hz line with the EX HWS. In that entry Robert suggests isolating the HWS power supply at EX as was done at EY (if I understand correctly) or shutting off the HWS during O2. Is there any reason to leave either HWS on during O2? The 56.84-Hz comb was visible at a low level in O1 data.
Update after looking at this + subsequent lock stretches (through last night):
These results are pretty consistent across the recent locks. Attached: a representative plot of these combs in the 30-50Hz region in 2 hours of the most recent lock stretch.
J. Kissel, S. Dwyer First attachment -- a screen cap the currently functional Bounce and Roll mode damping settings that work as Jenne describes above. One potential cause Shiela and I explored: we're using DARM_CTRL as our error signal for the bounce mode damping. We've always assumed that the DARM open loop gain is large enough that the open loop gain of the bounce mode damping loop is unaffected by changes in the DARM filter, D, or the DARM plant, or sensing function, C. Given recent, uncompensated issues with SRC cavity detuning cause optical spring changes in the plant, the DARM open loop gain near 10 [Hz] has been questionably low. We've been struggling with interferometric SRC alignment signal, and therefore leaving SRC angular control essentially off recently. This implies the SRC detuning can be changing from lock-stretch to lock-stretch, which means the DARM optical plant is changing from lock-stretch to lock-stretch. And if the overall DARM open loop gain is low enough, then the phase impacts of this change in optical plant will change the phase necessary to damp the bounce modes. The second attachment compares Kiwamu's DARM OLG TFs taken on 2016-09-16 vs 2016-09-21, and indeed, the open loop gain magnitude is only ~4 to 5 at 10 [Hz], and once can clearly see substantial phase differences between the two measurements. The third attachment shows the loop math to aide the following proof of how the two loops are coupled: C = DARM IFO plant, or sensing function D = DARM filter bank A = ISC L to TST L DARM super-actuator TF V = Bounce mode damping filter alpha = TOP V to TST L actuation function xi = coupling from TST L to DARM Delta L_{res} = Delta L_{V} + Delta L_{ctrl} = Delta L_{V} + A D C Delta L_{res} d_{ctrl} = D C Delta L_{res} --> Delta L_{res} = d_{ctrl} / (D C) d_{ctrl} / (D C) = Delta L_{V} + A D C d_{ctrl} / (D C) d_{ctrl} = D C Delta L_{V} + A D C d_{ctrl} G_{darm} = - A D C (1 + G_{darm}) d_{ctrl} = D C Delta L_{V} d_{ctrl} / Delta L_{V} = D C / (1 + G_{darm}) --> G_{V} = alpha xi beta D C / (1 + G_{darm}) --> IF G_{darm} << 1, then G_{V} ~ alpha xi beta D C and we have dependence on the changes in the optical plant of DARM. --> IF G_{darm} >> 1, then G_{V} ~ alpha xi beta D C / G = alpha xi beta / A and we have the scenario we have always assumed was happening. Now that Jenne's just restored old damping, this is less of a suspicion, but I wanted to write it down so that we keep this sort of loop inter-dependence in mind.