As a part of the DRMI investigation, we checked the laser power of CO2X and found that the power had dropped by a factor of two or so a week ago. However it turned out that this was due to a calibration filter (FM2 of TCS-ITMX_CO2_LSRPWR_MTR) which had turned off at that time for some reason. We switched it back on and also edited safe.snap accordingly. The attached is a 100days trend of relevant channels. As shown, the input of the monitor channel stayed at a constant value approximately in the past month or so while the output suddenly changed a week ago, indicating that the calibration filter was taken out.
I found a small mistake in the HAM_gain_matching_calculation script.
The Q of the GS13 model was wrong by a factor a few, causing a slight phase delay around the frequencies that matter for the sensor correction ([0.1Hz-0.4Hz]). The overall amplitude was thus altered.
This has been fixed and committed into the SVN:
/ligo/svncommon/SeiSVN/seismic/HAM-ISI/Common/Misc/HAM_gain_matching_calculation.m
Here's the correct values that we have so far (I though we had done HAM2 as well, but I can't find a good set of data):
HAM4 | HAM5 | HAM6 | |
X | 0.945 | 1.001 | 1.035 |
Y | 0.929 | 0.991 | 1.027 |
Z | 0.918 | 1.039 | 1.103 |
We still need to do HAM2&3, plus all the BSCs. Don't forget to put the ISI in high blend mode with sensor correction OFF when you want to calculate the gain.
Using the Guardian manager, brought down the entire ETMX SEI after capturing the current held position for HEPI. The Guardian code has been changed to restore all 8 dofs on HEPI to reduce or nearly eliminate alignment changes from lock to lock. Before HEPI only restored the RZ and Pitch at the ETMs.
The Guardian smoothly brought the system down with no trips. Restarted the Guardian code and then went directly to fully isolated first time. No problems with the idea then. I'll step this through all the platforms as commissioners allow.
Of note, none of the DOFs on the BSC-ISI are restored like this (As opposed to the HAM-ISI where all dofs are restored.) So, I attach a plot showing the before and after of this morning's restart. The op-levs are shown and the HEPI RZ. Additionally, all the rotational dofs of the two ETMX ISI stagesare show to reveal at least one lock to lock alignment change on the ISI. All the SEI channels are in nano units, Oplevs are urads I believe. The Stage1pitch is worst at 600nrad tilt, all others are much smaller.
250ml of water added to chiller.
As we found that the beam was too big on the IMC refl camera (alog 16166), I inserted a focusing lens (PLCX-25.4-20.6-UV) in front of it in order to obtain a better and wider view. The belows are pictures before and after the lens insertion.
Before
After
Both pictures were taken with the nominal exposure time of 19444 usec. In the second image, the main 00 mode is seen at the lower right. I am not sure whether if the upper part of the image is explainable by spatial higher order modes. It maybe a ghost beam. Note that this ghost-ish structure was visible with a laser card.
model restarts logged for Tue 20/Jan/2015
2015_01_20 00:05 h1fw0
2015_01_20 04:07 h1fw0
2015_01_20 10:29 h1iopsusex
2015_01_20 10:30 h1iopsusex
2015_01_20 10:31 h1susetmx
2015_01_20 10:31 h1sustmsx
2015_01_20 10:32 h1susetmx
2015_01_20 10:35 h1iopsusex
2015_01_20 10:35 h1susetmx
2015_01_20 10:37 h1sustmsx
2015_01_20 10:44 h1susetmx
2015_01_20 10:51 h1iopsusey
2015_01_20 10:51 h1susetmy
2015_01_20 10:51 h1sustmsy
2015_01_20 11:31 h1hpiham2
2015_01_20 11:31 h1hpiham3
2015_01_20 11:31 h1iopseih23
2015_01_20 11:31 h1isiham2
2015_01_20 11:32 h1hpiham2
2015_01_20 11:32 h1hpiham3
2015_01_20 11:32 h1iopseih23
2015_01_20 11:32 h1isiham2
2015_01_20 11:32 h1isiham3
2015_01_20 11:58 h1fw0
2015_01_20 11:58 h1nds0
2015_01_20 12:49 h1fw1
2015_01_20 12:49 h1nds1
2015_01_20 12:57 h1broadcast0
2015_01_20 12:57 h1dc0
2015_01_20 12:57 h1fw0
2015_01_20 12:57 h1fw1
2015_01_20 12:57 h1nds0
2015_01_20 12:57 h1nds1
maintance day preceded with two unexpected restarts. Restart tests on SUS ETMs. Power cycle of h1seih23 for noise hunting. Power cycle of DAQ solaris boxes, followed by DAQ restart for new slow controls ini files. Conlog frequently changing channels report attached.
Alexa, Evan, Koji, Arnaud, Sheila, Rana
The good news is that ALS is quite stable tonight, staying locked for up to 2 hours.
We have been having trouble transitioning to 3F tonight. We can transition MICH and PRCL fine, but we have seen a lot of noise at 300 Hz when we try to transition SRCL to 3F. When we try to transition we see noise at 23.5Hz.
ALS lock loss times: (all Jan 21st UTC) 0:03:02, 0:34:26
ALS lock loss +HEPI, ISI and sus trips: 7:30:15, 5:15:26
Lockloss and bad misalingment of IMC due to DOF4: 6:35
DRMI + arms off resonance lock loss due to SRCL 3f transition at 01/21/14 08:06:00 UTC
Keita, Sheila, Daniel, Alexa
Here is a screen shot of what happened that caused HEPI and ISI trips on DIFF lockloss last night. First, the arms loose the green lock, at that time the DARM output becomes very large, the gaurdian ramps this down over ten seconds, durring which time the integrator in L1 is still integrating. The guardian eventually clears this integrator. Before the integrator was cleared, the arm cavity flashes, although the suspension was still swinging so this produced a momentary lock. The tidal comes on, with a large output because the integrator in L1 has not been cleared yet.
We have done 4 things to help prevent this in the future:
The last thing that we need to do is add a delay to the logic for the tidal feedback, so that it does not engage prematurely on these momentary locks.
Comparison of the OMC length noise for H1OMC and L1OMC.
Note that floor noise of the L1 measurement was limited by the intensity noise at the time.
Math puzzle: What's wrong with this UGF Servo?
its installed for use in the OMC and LSC at the moment, and could be used in the ASC if we find we want to hold the UGFs constant during TCS tuning.
We want to measure . The algebra tells us that
,
.
When the excitation is sufficiently large that the noise is negligible, we get .
and
are complex quantities, and the real and imaginary parts are the I and Q outputs of the demods, or
,
.
In the version of the UGF servo that Rana posted, the phases would be chosen such that the imaginary (Q) outputs are zero, thus
.
This is OK as long as G only ever changes in magnitude, otherwise .
To get the correct measurement in the case of a changing phase, one must do the following:
This is implemented in the attached simulink model.
(First of all I don't know the answer yet)
I believe G only changes the gain most of the case.
The problem was
a/e = G/(1-G) and b/e = 1/(1-G) change their phase as you change the gain of G.
We usually don't care the phase of G, but only care the magnitude of G as the phase of G is fixed.
Therefore what we need is to take the ratio of the magnitude of a and b
|a| = |G|/|1-G|, |b| = 1/|1-G|
|a|/|b| = |G|, where |a| = sqrt(aI2+aQ2) and |b| = sqrt(bI2+bQ2)
(Ed: I'm suggesting to take SQRT(I^2+Q^2) to eliminate the frequently-omitted-effort of adjusting the demod phase correctly.)
Meh, I say it's overkill. As Nic mentions, this works just fine if the UGF phase is not changing, so long as you set the demod phase correctly. As Koji mentions, the UGF phase should not be expected to change that much. It is already a second-order effect, so what is there now should be fine, unless we really want to accommodate wild loop phase fluctuations at the UGF. Is there a reason that's ever something we want?
Rana, JeffK, Kiwamu,
We did some maintenance items on IMC ASC. The major activities are:
Also, tomorrow or sometime this week, we might insert a lens in the REFL gigE path as the REFL beam now is a bit too big to be able to cover the spatial higher order modes.
Some issues with the current implementation:
Tonight we have twice had MC lock losses where MC1+MC3 got completely misalinged, although they didn't trip. The second one of these was at the same time as a lockloss of the ALS, but we don't know if the IMC caused it or ALS. This was at 6:35 UTC, Jan 21st.
We made the decision not to increase the spot size. This was done at LLO to decrease the jitter coupling into the ISS. The in-vacuum ISS doesn't require this.
The IMC seem to have worked much more reliably, before we added DOF4. Please turn it off for good.
Alexa, Evan, Dan, Sheila
We have been having intermittent problems for the last two or three days. This evening we traced the problems we've been having with ALS COMM (alog 16129 ) to an oscillation of the PSL noise eater. The tell tale symptom was amplitude noise at around 900 kHz on the PSL light. We don't know of a good indicator of this problem from the control room.
We do not know if this was the cause of our mode cleaner lock losses over the last few days (alog 16128 ), or to tripping of MC1+MC3 suspensions and HAM2 ISI.
After I toggled the noise eater switch the ISS first loop was unable to lock. For now we have turned it off.
We had the outputs held on the IMC WFS DOF4 from late last night until 8 pm today. We didn't see any trips of MC1+MC3 today. Now we have turned DOF4 back on.
I turned on the ISS first loop. For the OMC characteization, we needed some kind of ISS.
1. Changed REFSIGNAL (H1:PSL-ISS_REFSIGNAL) from -2.248 to -2.135 to match it with H1:PSL-ISS_PDA_AVG
2. Push "On" of AUTOLOCK
This allowed me to engage the ISS loop. The out of loop "lsd" monitor (H1:PSL-ISS_PDB_LSD) shows 1.2e-8/rtHz.
There was recent check of the Noise Eater mon at LLO (log 13353). Wasn't that useful, but the binary NE mon is supposed to tell us when the NE loop is oscillating.
There were also numerous instances of this during eLIGO; the 'solution' then was to turn the servo OFF and then ON. Maybe if the monitor is now mistuned, we should adjust the resonant circuit to operate at 900 kHz.
Apparently we do have at least two ways to tell this is happenening from the control room, which means we could have some automated error checking for it.
First, this was already done in the PSL ODC, which seems to have degraded at least at LHO. (alog 9674) The PSL ODC screen now looks like the attached screen shot, I don't know what hapened to it but it might be helpfull to restore it.
The second screenshot shows that the RF mon on the COMM PFD was around -1dBm even when the X arm was unlocked while the noise eater was oscillating. We can add an error check for this in the COMM PLL beckhoff code. This is similar to what we did for the end station lasers (alog 10273 )
The attached plots show 2 weeks of the PSL Noise Eater channels as well as the ALS COMM demod mon.
NPRO_NEMON doesn't show any change and I don't know what it is connected to.
NPRO_RRO is the binary indicator of whether the NPRO Relaxation Relaxation Oscillation monitor is indicating a high noise state: around -5800 means OK, around -300 means Oscillating.
COMM DEMOD RFMON shows the non-bandpassed RF noise (in units of dBm):
-35 dBm corresponds to the bare noise on the laser without the arms locked
-1 dBm seems to be what we see with the arms unlocked an the NPRO NE oscillating
+5 dBm corresponds to the X arm locked and there's a good beat note between the green PSL and the green X trans beam
* the RRO indicator on the PSL screen had the threshold set too high; I've changed it to now change from green to red at -2000 counts rather than -200 (which would make it always show GREEN)