Dan, Kiwamu, Sheila
Today we made several gaurdian changes:
I looked for a signal from the QPDs which was insensitive to TMS angle. For the X arm pitch I used TRX A - 0.5 TRB and for Y arm pitch 1TRY_A-0.65 TRY_B seemed good. I closed a verry low bandwidth loop to ITMX using this signal, screen shot is attached.
We found that we could increase the recycling gain from ~27 to ~33 by moving the ITMs with ASC lops closed on IM4, PR2, BS, common ETMs, and differential ETMs. We had to move ITMX by as much as 5 urad to do this, and we found that we would loose the lock soon after getting a good recycling gain. Kiwamu calcualted that by moving ITMX 5 urad, we are moving the spot on the test masses by 1 cm assuming that the ETM is controlled. This may be due to a problem with the DHARD loop.
We also spent some time looking for a Transmon QPD signal that would be insensitive to motion of the transmon. We closed a loop to ITMX pitch using TRX_A - 0.5 TRX_B, the attached screenshot shows the settings. This loop was verry low bandwidth.
We had a second incident of a permanently ramping slider today, earlier we saw this with SR2 Yaw and just now (3:56:20 UTC) we saw it again with SR2 pitch. The offset had ramped to the correct value (probably in the 10 second ramp time), but the ramping indicator stayed on. This wouldn't be a problem except that we are using .is_ramping in the guardians, and they get confused by this situation.
Again I changed the ramp time, and Dan moved the slider one click and moved it back again, and the ramping indicator went off.
Dave investigated this earlier in the day when we saw it with yaw.
Scott L. Ed P. Chris S. The crew relocated lights and equipment this morning. We will be starting at the single door between X-1-5 and X-1-6 double doors and working toward the Mid station. We started vacuuming beam tube supports this afternoon and took dirty samples on the tube. Results posted on this entry. These are some of the dirtiest areas we have seen so far. A new generator was purchased Friday, however it still needs to be shipped here. A rental generator was picked up this morning to get us by until the new unit arrives.
This is a reminder that the RF phase of the REFL_A_RF9 and REFLAIR_A_RF9 signals should always be adjusted using the delay line phase shifter. The analog phase shift is applied to the LO signal and therefore effects both analog and digital feedback paths. On the other hand, the phase rotation in the real-time system only changes the digital path. It should always be set to 0°, if the error signal of the REFL servo uses the I output of the demodulator, and to ±90°, if it uses the Q output. One other caveat is that the delay line phase shifter may be in local mode, meaning one has to use the physical toggle switches at the chassis. In local mode the digital settings are getting completely ignored and there is no readback.
Jamie, Dave, Jim:
Jamie reported that the location of the MEDM Print selection, being at the top of the right-mouse pull-down menu, has resulted in many accidental printer jobs. This explains the printouts of things like the sitemap screen with no data content and no one picking the print-outs up.
Jim modified the LHO CDS MEDM this afternoon to move the print section from the top to second from the bottom of the pull down menu. Please see the attached before and after images.
During tomorrow's maintenance we will stop all old MEDMs in the control room so the new feature will be picked up. This is only a linux change, it was not applied to Mac OS.
Awesome. Thanks, Jim and Dave. The forests thank you.
LVEA: Laser Hazard Observation Bit: Commissioning 07:00 Karen & Cris – Cleaning in the LVEA 07:45 Bubba – Chiller delivery from LLO, Bubba unloading truck at Mid-X 08:15 HFD – On site with Richard at Mid-X 08:25 Adjust ISS diffracted power from 5.5% to 8.2% 08:43 Corey – Going into Squeezer bay for 3IFO work 08:50 Filiberto – IN LVEA making a survey of racks 09:00 Corey – Out of squeezer bay 10:00 Corey – Going into squeezer bay for 3IFO work 10:10 Bubba – Finished unloading truck at Mid-X – Big Red has been parked 10:30 Corey – Out of squeezer bay 11:15 Ken – Working on CER 12:47 HFD on site for fire alarm maintenance 14:20 Richard – Going to Mid-X 14:35 HFD finished testing the OSB fire alarms
Even though the threshold is set to 32k, the Stage2 tripped when the Actuators only hit 30k. Is this just from the 512k downsampled data?
The attached trend plots shows the full data and although it gets close, it doesn't appear to reach the threshold. Shame we get shut down for such a short transient.
Hugh means 512 [Hz], because the _DQ channel he's posted is down sampled from the native user model rate of 16384 [Hz] to 512 [Hz] before it sent out for frame storage. No way to confirm your suspicion Hugh, with the data that's currently stored. Brian says "We should store that stuff faster." I agree, especially if we add "if we *actually* want to know for these super-high-frequency glitch-type trips," because most people probably don't, they just want it not to happen. #TriggerECR Have y'all reduced the high-frequency roll-off of these loops yet? That's the real solution...
These are the 24 hour OpLev trends. Will look into the drops in PR3 and the BS.
PSL Status: SysStat: All Green, except VB program offline Output power: 31.9w Frontend Watch: Green HPO Watch: Red PMC: Locked: 13 days, 2 hours, 34 minutes Reflected power: 2.1w Transmitted power: 22.5w Total Power: 24.6w ISS: Diffracted power: 9.2% Last saturation event: 0 days, 0 hours, 28 minutes FSS: Locked: 0 days, 0 hours, 5 minutes Trans PD: 1.347v
Sheila, Nutsinee
Attached below are the plots of PEM/ALS and PEM/ISI correlations. Using data from March 14 (we had high wind up to 45 MPH). The x-axes are wind speed in mph, the y-axes are either ALS-X(Y)_REFL_SCTRL_OUT_DQ (rms) or ISI-ETMY_ST1_FFB_BLRMS_(DOF)_(100M or 300M)_(300M or 1) (mean). The correlation (r) is calculated and printed in the parentheses. Since PEM-EX and ALS-Y seems to correlate the most (r=0.7783) I only plot the correlation between PEM-EX and ISI-ETMY for the PEM/ISI correlation. PEM-EX and ISI-ETMY-RY (100-300 mHz) appears to have the highest correlation (r = 0.7469).
A Matlab script also attached.
My apology for the lack of axes labels earlier. I have attached better plots below....
Also, note that PEMEX, PEMEY, and PEMCS is in X, Y, Z direction (not locations). Also, the "ISI-ETMY_ST1_FFB_BLRMS_(DOF)_
Seismic: Hugh will be doing HEPI maintenance in the LVEA during the Tuesday maintenance window. Jim will be running transfer functions as opportunity allows. CDS: Need to work on shutter interface at End-Y. 3IFO work in the H2 Electronics building. VAC: Kyle will swap the ion pumps at HAM1 and HAM2 during the maintenance window. 3IFO: Work continues on IO inventory & storage tasks. The temp/dew point sensors are ready; connecting the 3IFO storage containers to N2 can start.
See the attached for trends of the BRS for health assessment. It has been down since ~22 Feb.
The first plot is the minute trend of H1:ISI-GND_BRS_ETMX_RY_INMON. This is 100 days of just the mean and the flat lined sections are BRS in trouble areas. The 2nd attachment is a 60 minute second trend. This shows the healthy 9mhz signal of the BRS.
Thanks Hugh. Some comments: The BRS was turned off around Dec. 18th for the ETMX vent and restored after things normalized again in EX VEA. The 'spikes' in the BRS data are mostly the disturbances from people in it's vicinity, which is damped quickly (in ~10 mins). Therefore in the normal/good state BRS_RY_INMON shows between 5-50 count amplitude and 9 mHz oscillations, as Hugh showed. When the BRS software crashes, the output remains flat and shows <2 count variation.
Currently the software crashes once in 2-3 weeks. A preventive restart (which takes <10-15 minutes) once in two weeks would be useful till a better solution can be found.
After a bit of a struggle getting the pre-modecleaner out of its tank, we managed to
examine the mirrors of the pre-modecleaner. Visually most looked okay, except one which
showed some evidence of a film. It was not easy to see, nor photograph but certainly the
impression is that something is there.
This is most likely the reason of the pre-modecleaner's demise, which may have been
the result of it having been stored with its tank lid on.
Ed, Peter
More details on the scattering Dan mentioned on Friday, with some new and re-interpreted details (the responsible motion is horizontal) that became clear after further investigation.
This last Monday, DARM spectra showed a double scattering shelf occasionally reaching 60 Hz and 120 Hz (Figure 1) and even higher. I searched for the source of the scattering path length variation by looking for motion sensors that detected maximum motion at the times that the higher frequency scattering shelf reached its highest frequency. The top trace of Figure 2 is a 700s time series of DARM, band passed between 90 and 145 Hz. Each of the spikes in the time series was produced when the scattering shelf reached into this band. The lower plot shows that the maxima in one of the OMC OSEM signals coincides with the spikes in the DARM plot above it. All OMC OSEMs show this correlation except the side sensor (on the short side). I found no other GS13 or OSEM channels that showed this correlation; most importantly, it was not in the GS13 signals from HAM6. Figure 3 is a zoom in to one of the clusters of scattering spikes, showing that the scattering spikes appear to occur at the steepest part of the OSEM signals (when velocity would be highest), and that the time spacing between DARM spikes agreed with the resonant frequencies of the OMCS. Beating between 2 of the suspension modes seems to cause the variation in motion.
Using the 1 um/count calibration of the OSEM OUT channels, I obtained average velocity spetra that, for some OSEMs, reached 10 um/s (Figure 4).
In order to produce a shelf out to 60 Hz, the rate of path length change for a single bounce would have to reach about 30 um/s. The OSEMs measure displacement of the top mass, M1, and the OMC hangs below it. At the resonant frequencies of this suspension, the motion of the OMC, while damped, would still be greater than the top mass. Also, the 10 um/s figure is only an average rms. Thus the OMC motion can account for the 60Hz shelf with a single reflection.
There are two shelves in Figure 1 spaced by a factor of 2 in frequency. The spectrogram in Figure 5 shows that the frequency spacing of the two shelves is always a factor of 2. The shelf at 120 Hz in figure 1 is about an order of magnitude below the shelf at 60 Hz. If this represents a scattered beam that reflects twice instead of once, then the reflectivities at each of the two extra surfaces would have to be very high. While there may be other mechanisms to generate the double shelf, it is probably worth looking for bright beam spots on highly reflective surfaces in HAM6.
Finally, it would be nice to reduce the motion of the OMC by a factor of ten, particularly, the side to side and rolling motion perpendicular to and about the line connecting the two suspension points of M1, motion detected by the LF, RT, T2 and T3 OSEMs.
It's likely the OMC ASC control (Kiwamu, Daniel, Keita)
Summary:
OMC BOSEMs are usually very quiet, but they show extremely big motion that Robert showed only when the IFO is in lock with DC. In-lock VS out-of-lock ratio is huge at about 3 orders of magnitude.
It turns out that this comes from OMC ASC control actuating on the OMC suspension.
OMC YAW has a large coupling to the distance between the OMC and the IFO because the rotation axis is fairly distant from the first steering mirror on the OMC breadboard, probably 18cm or so, and therefore is likely this is the main motion coupling to the scattering path modulation.
Apart from identifying the scattering source, there could be some mitigation tasks that we could do.
We will test the two TT mitigation tomorrow.
Details:
Attached shows the same OMC BOSEM velocity signals that Robert used (the only difference is that this is calibrated in um/sec, not m/sec).
Solid lines are now, broken lines are when Robert took his measurement. At around big peaks, there's 3 orders of magnitude difference. It turns out that they're mostly like solid lines show, and becomes excited only when in DC-lock.
Kiwamu will fill in more details.
I attatch a 24-hrs trend of some relevant channels from Mar-10-2015. As shown in the trend, it seems that every time the OMC-ASC loops are in action actuating on the OMC suspension, the OMC OSEMs read high fluctuation as weel as a big shift in the DC values. When the OMC ASC loops are not in action, the OSEM readouts are quiet.
On Friday we reduced this scattering noise below the usual noise floor by reducing the OMC ASC gain by ~10x. This reduced the UGF of the QPD loops down to 0.1Hz. This is around the UGF of the dither loops, which explains why we only saw this noise recently, when the QPD loops were used in low-noise. See the attached plot of the OMC SUS longitudinal signal: the blue traces are the QPD loops in a high-gain state, red is low-gain. The purple traces are from March 4 when the OMC was aligned with the dither loops 9 (the dither signals are rolled off above 2Hz since the signal-to-noise above that frequency is not good). The black traces are the quiescent OMC SUS noise without ASC feedback. For the current noise floor between 10-100Hz, the motion of the red and purple traces are low enough to keep the scattering from being the limiting noise source.
That said, this scattering knowledge means that the experiment of feeding back alignment signals to the OMC SUS should end. I've added OM3 to the ASC model, so we can feed back the DC centering signal from AS_B to OM1-3, along with the two degrees of freedom from the OMC. This will give us a 3x3 control matrix for the HAM6 alignment, similar to what's being done at L1. It ignores the centering on AS_A, but centering on AS_B should be sufficient.
Btw the dither loops need to be re-commissioned because I moved the dither lines up to ~1.7kHz. This changed the sensing matrix, it needs to be remeasured and inverted for a new control matrix. Tomorrow we will 1) switch the control topology to use the OMs rather than the OMC SUS, and 2) switch the sensing topology back to the dither for low-noise operations.
Today we have high winds again. At 22:24 UTC I've switched the ALS arm requests to LOCKED_NO_SLOW_NO_WFS. This means H1:ALS-REFL_CNTRL_OUT_DQ will be a measure of the arm length fluctuations (in um), contaminated by the coupling of angle to the length sensor which is due to the high transmission of the ETMs. The locks are only lasting at most 30 seconds. We've have both end station ISIs with 45 mHz blends along the beam direction.
Blends along the beam direction were switched to 90 mHz at 22:37 UTC.
At 23:23 UTC I switched the end X sensor correction to use the BRS, and turned off beam direction sensor correction in End Y.