Evan, Keita, Kiwamu, Alexa
It had appeared that the temperature in the LVEA had stablized (alog 15054) so we went about realigning in the IFO. Here is the original alignement we started with:
PR3 | IM4 | PR2 | |
Pitch | -246.0 | 13350 | 1057.2 |
Yaw | 88.0 | -5056 | 2971.3 |
Here are the initial steps we took:
At this point, we noticed that the WFS had brought IM4 to a bad alignment. Keita has measured the PR2 baffle clearance (alog 15063); and IM4 was not within range in YAW. So we basically started from scratch, and did the following:
Now we have the following:
PR3 | IM4 | PR2 | |
Pitch | -243.5 | 12694.7 | 926.2 |
Yaw | 13.9 | -5052.5 | 2312.2 |
ALS X Camera | ALS Y Camera | |
X pos | 393.1 | 267.8 |
Y pos | 250 | 289 |
COMM beatnote: 6dBm, DIFF beanote: -1.6dBm. When I get a chance again I will take a snap shot of the ALS camera images, but for reference these image is a bit clipped for both beams; however the transmission is good and the beatnotes are good so it's just the image.
Apparently, the end station temperatures are still drifting. This will affect the DIFF beatnote. Unfortunatly if EX drifts a lot we will need to re-do this input alignment again ...
08:22 Ken to end X to move AC receptacles (WP 4945) 08:45 Jeff B. and Andres to end stations to pack up tooling 08:52 Karen to end Y to clean 09:00 Chris done cleaning in LVEA 09:01 Aaron and Filiberto to end Y to pull PEM cables 12:05 Karen done 12:06 Jeff and Andres done 12:13 Aaron and Filiberto done 13:07 Bubba to inspect end station mechanical rooms 15:01 Cyrus to mid X to test phone 15:03 Suresh to adjust optical lever by HAM3 16:02 Suresh done
Alexa, Nic, Jim, Dave
Alexa reported strange LSC-PD_DOF_MTRX input ramped mux matrix behavior last weekend. Symptoms were: new element values were taken immediately without loading, ramping continued indefinitely. The current theory is that a rogue script is setting H1:LSC-PD_DOF_MTRX_LOAD_MATRIX to 1 frequently. On monday this channel was added to conlog, and conlog reported that during monday afternoon and early evening this EPICS channel was being set to 1 several times a second. We also discovered that the DAQ trends were not showing this high frequency activity, this underreporting is under investigation (only seen in the LOAD channel, all other matrix channels trend correctly).
At 11/10 20:19PST monday evening the rogue loader stopped running and has not restarted since. Initial scans of guardian and home account directories have not found any script which would be loading the matrix frequently. Guardian logs its PV settings and these are seen at very low rates (max 100 per day). We may have to wait for the problem to reappear in order to track it down further. Investigation is continuing.
This reeks of bad guardian programming to me. I would put money on one of the ISC nodes writing a one to that LOAD_MATRIX channel every cycle. Look for that channel name in whatever guardian node is actuating on that matrix, or just grep for it in all ISC nodes.
Jamie, we had seen this behavior with all the ISC guardians set to "DOWN" and/or paused. I don't see any guardian that loads the matrix in the "DOWN" state.
As noted over the last few days, the temperature at LHO has dropped significantly over the last few days and the HVAC temp control of Ey and the LVEA have wandered more than normal. For the record, attached is an 8 day trend showing the temperature drop at End-Y versus the ETMy main and reaction chain vertical, pitch, and yaw positions.
In order to check model calibrations and to compare with LLO's temperature drift measuremenst from Aug (alog 14008), I looked closer at a smaller band of temperature change in the above plot. I chose a quieter time when ETMy was not being manipulated by commisioning but during a 1.5 degC temperature change in the End Y VEA on 11/08.
During our -1.5 degC temp change the ETMy suspension shows the following drift in Pitch and Yaw:
ETMy M0 PIT | * ETMy R0 PIT | ETMy M0 YAW | ETMy R0 YAW |
35 urad | 21 mrad + 7 mrad | 2 urad | 3 urad |
With Vertical showing the following drift magnitude:
ETMy M0 V | ETMy R0 V |
18 um | 16 um |
Note, the ETMy R0 (reaction chain) seems to show some stepping which we are looking into, so the drift trend has a step in between the 21 um drift and a 7 um drift.
New IM4 nominal bias sliders: [13350, -5056].
Good range for IM4 bias after the initial alignment procedure is [13350 +- 2400, -5056 +- 330] assuming that the MC is behaving well.
The "good range" gives you +-2 mm displacement on the PR2 baffle, which is a non issue for clipping, or +-60urad in IM4 rotation.
IM4 slider calibration was remeasured, it's: 0.025 rad/bogorad for PIT, 0.182 rad/bogorad for YAW.
The slider change from yesterday, i.e. [3364.4, -118] slider counts (micro bogorad), corresponds to [88.3, -21.5] urad physical rotation.
What was done:
After the LVEA temperature settled, IM4 was scanned while the PR2 baffle and the SRM baffle was monitored. Before I started IM4 [P,Y] was [9985.6, -4938].
For IM4 YAW, I was able to see when the beam barely touched the PR2 baffle edge, and when the straight shot beam on SRM baffle disapperaed. I made the average to determine when the beam is 50% blocked.
For PIT the driver railed before I was able to completely block anything, I only recorded when the beam barely touches the PR2 baffle edge.
barely touches | Completely blocked | Average | |
Left, Y bias | 800+-100 | 1800+-100 | 1300+-70 |
Right, Y bias | -6300+-200 | -12200+-200 | -9250+-140 |
Top, P bias | -25300+-1000 | NA | NA |
Bottom, P bias | 52000+-1000 | NA | NA |
Since baffle hole appears to be a 65.4mm diameter circle, and since the beam is supposed to be 26mm from the right edge, the new position is
P = (52000-25300+-1400)/2 = 13350+-700.
Y =26/65.4*(1300+-70) + 39.4/65.4 * (-9250+-140) = -5056+-90.
Slider calibration is the angle over the baffle diameter 65.4mm/17m divided by two divided by the slider difference, i.e.
calibration for P = 65.4e-3m/17m/2/(52000E-6+25300E-6+-1400E-6 bogorad) = 0.0249(1+-0.02) rad/bogorad
for Y = 65.4e-3/17/2/(1300E-6+9250E-6+-160E-6) = 0.182(1+-0.015) rad/bogorad
JeffK says may be a leftover from unexplained ISI trips. I'll study.
Here are TFs from the Ground STSs to the ISIs GS13 in low gain. I'll switch to high gain and compare when that transition won't potentially disturb the commissioners.
In low gain, there is good coherence bewteen 2 and ~10 hz. Cross couple channels, shown for HAM2, are all pretty small.
See plot...I don't know what this is.
So this ISI sat tripped for some 20 minutes until I was scanning the SEIs. I will implement an alarm system so these do not languish.
It tripped at Nov 14 2014 03:48:32 UTC, which is 19:48:32 local time yesterday.
Probably it was me shaking the HAM2 ISI for checking the PR3 performance. Good catch !
I noticed while walking by that air currents (from my passing) caused the curtains to swing free and then thump on the box. This doesn't seem good. The curtains could likely be tied back, easy. Or maybe the cleanroom should be moved, a bit harder.
Seems like the temperature was already good-ish as of 18:00 or so yesterday.
Doug will rezero SR3 optical lever around 10am The beam balance is misbehaving, Krishna will be here Tuesday to investigate PEM cabling at end Y Ken moving AC outlets at end X Jeff and Andres packing and removing tooling at end X and end Y
Looks like an unwarranted glitch on the actuator. The CPS aren't moving before the trip. The GS13 respond quickly (hard to tell if this is cause or effect) but again there is no preamble.
J. Kissel, A. Staley, K. Izumi, K. Kawabe Continuing investigations of why ETMY behaves poorly when attempting ALS DIFF (see LHO aLOG 15037) -- I've looked at two more things: (1) Pitch-only optical lever Damping: This had been turned on only *after* it had been decided that ETMY was "fragile," i.e. any impulses would shake the SUS quite a bit -- but I checked it anyways. First attachment is comparing spectra with the PUM (L2) stage actuated, optical lever Pitch damping loop ON vs. OFF. It's damping pitch, as expected, and not injecting anything terrible. This of course is assessing the stationary noise, and we're worried about non-stationary problems ... but ruling things OUT with quantitative data, I feel, is just as important along the investigatory route. (2) DRIVEALIGN Matrices: I attach comparisons between everything in the ETMs UIM (L1) DRIVEALIGN matrices (Only the P2P, Y2Y, and L2P have anything in them, so those are what's compared in the attachment). I believe the original design intent for P2P and Y2Y filters was to have global WFS transfer function be similar to the test-mass transfer functions -- hence the high-Q, plant inversion-y type stuff. They are slightly different between the two test masses, but, in-fact, they don't matter matter at all because we don't feed any angular signals to the UIM stage. However, I've found that the ETMY UIM L2P frequency-dependent decoupling filter in the UIM bank is significantly different than ETMX's -- and the filter has a much larger step response. I compare three different sets of filters on pgs 1 and 2: ETMX -- FM1 & FM2, "L2P" & "L2P2" ETMY, Current -- FM1, FM2, & FM4 "L2P", "L2P2", and "BetterRolloff" ETM, Legacy -- FM6 & FM7, "L2Plegacy" & "L2P2legacy" It looks like the initial story here is laid out in LHO aLOG 11832, but there're several more aLOGs referencing UIM / L1 L2P Filters, and how they've been bad, they've been good, they've been turned off, they've been turned on... The foton calculation of the step response disagrees with the measured step response LHO aLOG 14832 -- but recall that the filter step response is not the only thing measured in that 14832 measurement -- it's measuring both the filter AND mechanical step response. We now have local damping filters from LLO which has reduced the mechanical impulse response time by a factor of a few. This, coupled with a smaller impulse response filter should help, but we'll remeasure once a new filter is designed. I'll move on to chasing this down -- re-measure the step response, and also remeasure the plant upon which these filters were designed. Of course, an immediate, band-aid fix could be just to copy ETMX's L2P filter over to ETMY, but while we wait for the temperature in the VEAs to settle down, I've been given the green light to measure some TFs.
CORRECTION:
The first attached plot in alog 14832 shows the impulse reponse of ETMY L1 stage with:
The trace the was *not* plotted was the ETMY, Legacy -- FM6, FM7. We had taken an impulse response of this configuration, but it was so bad that we did not leave it in the plot. Clearly this disagreed with Jeff's response.
In preparation for tomorrow's maintenance on HAM2 and HAM3, I have set the following gains and whitening stages on HAM2 and HAM3 OPLEVs.
Whitening and Gain settings of | Gain (dB) | Whitening stages |
HAM2 | 18 | 2 |
HAM3 | 6 | 2 |
I added the dewhitening filters in the input flter banks of the oplevs and switched on two stages to mirror the analog state. The analog switch states are shown in the attached pics. The label on the cable tells us the name of the oplev that is addressed by the dip-switch board.
The oplevs are, as yet, not calibrated. The HAM3 shows an uncompensated whitening though I have switched on the dewhitening filters stages. Will investigate further.
Ed writes such nice alogs about oplevs and whitening filters and diode lasers and stuff!!
Imagine how nice it would be if I knew what i was talking about!
Jason, Sheila
There have been some glitches on the ETMX oplev, which don't seem to correspond to motion of the optic, the attached screen shot shows an example. I think that I have seen glitches like this that were much larger in amplitude, but am not sure.
One question for detchar is if they have a tool that can search for glitches like these, and give us some information about how often they are happening, how large they are, and maybe monitor to see if they are happening on other op levs.
Another issue is that sometimes the lasers fail, which is often foretold by a several seconds oscillation in the oplev sum. Can detchar set up some kind of monitoring for that?
Of course the real question is how can we fix it......
Hi Jason and Sheila, here at LLO Olmo Cerri, a summer student from UMISS, looked at the possible causes of glitches in OPLEVs. He worked with Suresh. Suresh earlier found that the the temperature variation could cause changes in the cavities of OPLEV laser and thereby changing the laser intensity which would look like glitches. Olmo looked at week long strecthes of data from a few OPELVs and charactersized how many glicthes we see (he wrote a matlab script to find the such gltiches). They also implemetned a simple temperature stabilization method (LLO a-log) to reduce the gltiches. It seemed to work well. Here is a presentation by Olmo on this work which shows data before and after the temperature stabilization setup. He is now looking into implemneting an online version of the code.
I set Olmo's code to run on a cron job with the results here: https://ldas-jobs.ligo-wa.caltech.edu/~codyca/MHoF_results/ We still need to put together a better way to present the results. The code is set to remove glitches caused by human interaction by looking at the OPTICALIGN offsets. Also, the results for LLO can be found here: https://ldas-jobs.ligo-la.caltech.edu/~codyca/MHoF_results/
We this alighment we achieved a build up of around 210 for PRMI after we ran the inital alignment procedure. We are pretty content with this for now. As Evan aloged we couldn't keep going because of an earthquake.
As a reminder, Nic was in the middle of aligning POPAIR on ISCT1 when the earthquake hit, so we need to finish this next time we lock PRMI.
Also, as a note, we have left SR3 in the old configuration and Kiwamu has aligned ASAIR and the camera on ISCT6 for this old configuration.
In regard to the work on ISCT1: I touched up the beat note power onto the COMM diode; it was relatively straightforward. I also did DIFF, but it was much more touchy. Also, the mount for the DIFF interference BS is not oriented correctly; when the beams are passing through the clear aperture of the optic, the TRY beam is clipping on one of the mount knobs. The BS mount needs to be rotated to resolve this.
With PRMI locked, I have gone onto ISCT1 and realigned the beam onto POPAIR_B.