A second round of testing on the all-metal 3IFO QUAD unit Q7 is attached. After we saw a few cross coupling terms and struggled with coherence in the prior measurement set, we made a few adjustments to the QUAD mechanics. However, readjusting the lacing cabling and retuning the sensor mounting tablecloth seemed to not help much. There is still L and R bleeding into P on the reaction chain. We were able to improve the coherence by building a fort around the test stand however. The main chain looks to be in pretty good shape though.
The first attachement below is of Q7 with damping on and off.
The attachment below is of the Q7 (pink traces) undamped TFs compared to the 3IFO Q6 and Q8 units.
Screenshots of damping filters for DC offset diagnosis.
Spectra for all stages of Q7 attached. Note that the L1 and L2 stage OSEMs are not aligned and centered.
(Keita, Alexa)
We moved IM2 in pitch to correct for the 60urad deviation that Kiwamu and Keita saw on Friday (alog 15081). Originally, IM2 P, Y = 17000, 5154 with M1_DAMP P, Y = 580, -51. This was adjusted to IM2 P, Y = 19200, 5154 with M1_DAMP_ P,Y = 637, -45.
We then repeated an IM4 scan on PR2. The new good alignment values are: IM4 P, Y = 6670.5, -2735.0
The scan procedure:
We moved IM4 in pitch until we saw the beam on the PR2 baffle. This allowed us to center the beam in yaw; we found that the good center position in yaw was -881.8 -- this was consistent for both top and bottom of the baffle. Then we found the pitch values for which the beam was just barely clipping the baffle:
IM4 Pitch | IM4 Yaw | |
Barely Top of PR2 Baffle | -24329.5 ± 2000 | -881.8 |
Barely Bottom of PR2 Baffle | 37670.5 ± 1000 | -881.8 |
This average gave us the pitch position of 6670.5.
It turned out that yaw was bit more tricky. For whatever reason, the "barely clipping" procedure in yaw did not work; it gave us a center value of -3881. So instead we looked at the PR3 camera (with ITMs very misaligned), and determined when the beam disppeared in yaw:
IM4 Pitch | IM4 Yaw | |
Left on PR2 baffle, No beam on PR3 | 6670.5 | 6418.2 ± 100 |
Right on PR2 baffle, No beam on PR3 | 6670.5 | -11681.8 ± 500 |
This difference amounted to 18,100 counts. We then looked at the PR2 baffle lower left and lower right beam positions, and found that this yaw seperation for the PR2 baffle diameter made sense.
As noted in Keita's alog 15063, the diameter of the baffle is 65.4mm, and the beam must be aligned to 26mm from the right edge (or equivalently 6.7mm from the center). So we used
yaw = center + radius in counts/ radius in mm * distance from center
yaw = -881.8 + (6.7 mm / 32.7 mm) * (-9050) = -2735.0
Keita pointed out to me that as we move the beam in yaw to clip on the left side of the PR2 baffle we will actually first see a back reflected beam from PR2. This probably explains why our yaw measurements for the "barely clipping" scheme was incorrect; we were probably measuring the back reflected beam from PR2 and not the beam from IM4.
The calibrations on PR3 angles are wrong. In the attachecd screen shot you can see that someone moved the alignment slider -72 urad in yaw, the OSEMs sees a shift of -62 urad, and the optical lever records a shift of -26 urad
This morning the power on IM4 was about half of what it should be, even though all other readings of IMC ower were good. It turned out that the IM4 whitening gain was reduced by 6 db on Saturday night at about 9.15 LT (2014-11-16 05.15 UTC). We don't know why that happenened and if something else was also changed at the same time. For the moment being, I changed the gain back to the previous value.
This was my fault - apologies for not putting in the log. The IM4_trans quadrants were saturating on Saturday evening, during the time when the CARM offset was being scanned to lock the arms; when I saw this I reduced the gain on IM4_trans by 6dB to bring the signals away from the rails. (The IMC WFS were saturating too, but since they are in-loop I didn't adjust them.)
[Sheila, Gabriele]
As suggested by Keita during the morning meeting, we checked the IM4 transmitted beam coming from the PRM reflection, on the in-air table. We dumped both beams on the table, and this improved a lot the situation. When the PRM is aligned, the noise on the ISS diodes doesn't increase much anymore. However, there is still a small worsening at 18 Hz, so maybe in the future we might want to better dump the beam at the level of the upper mirror into the enclosure.
SEI - plans to do some upgrading/standardiing on Tuesday (maintenence day). Otherwise, standing by to assist with commsissioners.
SUS - plans to work in W bay in the mornings for the entire week
PSL - working on issues with ISS second loop. Also, issues with an apparent 30% power fluctuation that may have something to do with an errant reflection??
3IFO - gearing up for SUS baffle build. Working in VPW to clean up for Contractors
CDS - X-end work - power up and checks
Y-end work - cabling
Facilities - bring palette jack from MX to staging building. Working to maintain temperatures everywhere. Apolllo may be here this week. Their work will include sawing asphalt which will be conidered invasive. operators should be kept informed as to all activities of this nature.
Op Lev - re-alignment work of SR3 (work permit #4946). This will neccessitate transitioning to full LASER SAFE at some point.
Commissioning schedule to remain the same; 12:00 cutoff for noisy work in VEAs unless otherwise granted
grouting in the LVEA discussed as imminent in the not-so-distant future.
Laser Status: SysStat is good Output power is 33.3 W (should be around 30 W) FRONTEND WATCH is RED HPO WATCH is RED PMC: It has been locked 3 day, 23hr 40minutes (should be days/weeks) Reflected power= 2.5W and PowerSum =25.7W (Reflected Power should be <= 10% of PowerSum) FSS: It has been locked for 0h and 4 min (should be days/weeks) Threshold on transmitted photo-detector PD = 0.74V (should be 0.9V) ISS: The diffracted power is around 8% (should be 5-15%) Last saturation event was 1d 16h and 38 minutes ago (should be days/weeks)
model restarts logged for Sun 16/Nov/2014
2014_11_16 08:27 h1fw1
unexpected restart
Sheila, Dan, Evan
Yesterday and today we have tried to get the interferometer into a state where we can lock ALS with a CARM offset, lock DRMI on 3f, and then reduce the offset while staying locked. The lesson learned this weekend is that it is taking too long to get DRMI and ALS locked so that offset reduction can begin.
On the ALS side:
On the DRMI side:
ALS+DRMI, other:
For the record, upon further query Evan says "[The ALS DIFF used during the efforts documented by this entry] was with ETMX only. DARM feedback to ETMY was off." (I'd asked because I wasn't sure whether my new H1 ETMY UIM L2P decoupling filter from LHO aLOG 15049 had been tried / tested.)
Patrick, Dave
We have been scouring the houly conlog reports of EPICS PVs which change more than 500 times an hour for a reoccurrence of the rapid (many times a second) setting of the LSC ramped mux matrix which was observed last weekend. Unfortunately we have not seen anything yet, we will continue our vigilance.
FYI: here is the report from the last hour. (Remember that a 16Hz front end slow channel, if constanly changing, will give 16*3600 = 57,600 changes per hour.)
Process variables in conlog that have changed more than 500 time(s) in the last 3600 second(s):
H1:SUS-ETMY_L1_LOCK_L_RSET 57541
H1:SUS-ETMX_L1_LOCK_L_RSET 57541
H1:ALS-Y_CAM_ITM_SUM 2361
H1:ALS-Y_CAM_ITM_YAW_POS 2361
H1:ALS-Y_CAM_ITM_PIT_POS 2361
The L1 RSET frequency seems bad to me. I would interperet this to mean that the Guardian is resetting the filter history on that filter bank 16 times a second. Even if this filter bank is unused it indicates some rogue/bad Guardian script.
Rana is correct. Sheila, Alexa and Nic found the DOWN state of the ALS_DIFF guardian node was rapidly clearing the history of the ETM[X,Y]_L1_LOCK_L filters. This started at 8pm last Tuesday (11/11) and was ongoing until it was fixed a couple of hours ago. This highlighted a guardian logging issue with this node which Jamie is looking into.
model restarts logged for Sat 15/Nov/2014
2014_11_15 21:27 h1fw1
unexpected restart.
Keita, Kiwamu,
This is a follow up of the previous investigation for the input pointing issue (alog 15028). We are concluding that the IM2 is the one which messed up the input pointing the other day before the temperate issue hit us.
According to a back-of-envelop calculation, this well explains why we had to move IM4 by 88 urad in pitch to get back to good alignment (alog 15063). Also, from the OSEM spectra, there is no obvious indication of the mirror sticking to the cage or something. Therefore we don't think this is an issue.
Here are summary:
The attached is trend of various relevant signals:
Here is the spectra of the OSEMS before and after the slip. The bold curves are the ones taken on Nov 10 and the thin curves are the ones from today. All the spectra from today are consistenly lower at low frequencies supposedly due to different seismic level. Also we are having a small bump at around 2 Hz today for some unknown reason. In any case, we don't see an obivous indication of the mirror touching the cage or OSEMs. Therefore we are concluding that IM2 is still healthy.
Hugh, Sheila
This doesn't seem to be the result of either Hugh's work last tuesday or stray light reflected off of PRM.
This slip in IM2 happened about 5 and a half hours after hugh's work, and about 5 hours before PRM was realinged.
K. Venkateswara, J. Warner
The BRS damper (see 14388) has been malfunctioning since yesterday afternoon. It's controller is an open loop system that assumes it is in the centered position when it is first started. Occasionally it can get restarted accidentally when the insulation box is bumped (probably due to a short somewhere, but I'm not sure where). It looks like this happened yesterday around noon.
This requires a manual re-centering of the turn-table for the feedback system to work as designed. I've attached the directions to do this. Jim will do this later today or tomorrow.
I checked on the BRS this morning, and found the code frozen. I followed Krishna's fairly straightforward document up to the point of opening the box and found the masses 90 degrees out of position (NW/SE instead of SW/NE), I was unsure of what to do, so I closed up, restarted the code and called Krishna to consult.
Afterwards, I went back to EX this afternoon, and re-aligned the masses on the damper. I did this by first modifying the code as described in Krishna's document, then opening the large insulating panel on the west side of the BRS enclosure, and just turned the turn table until the masses were approximately SW/NE. The turn table moved quite easily, I was expecting more resistance.It was dark down there, so it was hard to get a good picture, but I've attached an image taken from the west side of the BRS enclosure, showing how I left the masses. I then went back to the rack, re-commenting the appropriate code and restarting. Haven't had a chance to check on the BRS since then, but it looked okay from what I could see on the laptop readouts.
Looking back at the data, it seems that the changes made in the morning, resulted in a positive feedabck loop leading to large amplitude oscillations in the BRS. The changes made in the afternoon reversed it but it took ~5-6 hours to damp. However, the software appears to have crashed again later. Tomorrow, I'll investigate for intermittent shorts or other grounding issues.