- Kiwamu, Cheryl I
M1 and IM2 were aligned through the FI using beam clipping on the iput aperture and the beam at the output of the FI (no baffle to see, but other clues used to center).
After burning time on IM3 and IM4 and not making progress, I came up with a plan to use the wall markings and IM4 TRANS QPD to fine tune IM2 and IM3 alignment. The matks on the wall were from October. The two feducials should give a beam from IM3 that is at the same position and angle as the beam from October.
The beam on the PR2 baffle was difficult to see, but did cross the baffle when driving IM3 or IM4. Exact alignment wasn't possible, and when I left Kiwamu was working on getting a good camera view to assist in centering the beam using IM4.
Noticed the drive to ISI actuators gettting larger and JeffK thought it might be that the Boost2 was on with the level3 controllers. It was nearing ACtuator trigger levels and we switched it to boost3. Maybe too late or maybe you must start from scratch but it still tripped the Stage2 WDs. Jeff brought it back up to level3 and still in boost2 rather than 3. We had though it might have been related to me just jumping staight to level3 from level1 earlier. Attempting to run a spectra to see what is happening but my session had died onme twice--I'll take this up later.
Meanwhile--maybe there is a script error engaging level2 boost in the level3 isolation? For the moment I'll leave it in level1.
Been distracted so I'm not sure what the state has been for a few days but attempted to turn on the BSC9 ETMx ISI and it tended to trip due to the T240. RyanD(LLO) reminded me of the steering offsets, I didn't think they'd matter that much for the ISI since HEPI can do so much more but I looked at them anyway. Since before the pump down beginning ~10 Dec, the alignment targets or CPS Offsets had not been reset. This causes too great a drive and saturates theT240s. So I reset both the Offsets and the Targets. I should have just done the offsets first to see what happens but I did both.
Looking at the cartesian positions, the Zs and Rzs saw some very large shifts during the pump down. Stage1 & Stage2 Z both saw 17umeters drops. Much more drawn out over time the Rz of the two stages saw ~10urad shifts. These are possibly attributed to buoyancy and thermal effects. The translational & Rx/Ry changes were more like 1um.
Anyway, bottom line, the CPS offsets and targets were too far from the idle free position and would not stay stable trying to move these large shifts. Now with close offsets and targets, the system turns on quietly.
I started with level1 and then rememebered Hugos status log where he put us at level3 isolation. I bumped it up to that directly.
Attached are some trends of the CPS positions since before the pump down.
LVEA Laser Hazard Apollo Installing TCS plumbing in the LVEA SEI group Running HEPI transfer functions 09:00 Richard remove yellow view port cover on X-Arm spool to check ACB photo diodes 09:10 Andres in LVEA working on H1-SR2 10:22 Corey going to End-Y to recover camera equipment 10:30 Richard open gate due to snow and slick roads 10:37 Kiwamu Working on IOT2L in LVEA 10:51 EE interns pulling cables around HAM2 11:00 Cheryl & Kiwamu Open HAM2 East side view ports, with ALS pipe closed, to look at in chamber optics 11:02 Filiberto working on diodes at the BSC3 SUS rack
Richard, Filiberto, Daniel
We tested the photodiodes and they seem to be all working. There was a problem with the ordering as seen by the slow controls system. This is fixed now, and the order has changed relative to an hour ago. 1 and 3 swapped, and 2 and 4 swapped. This also brings the order as shown by the medm in agreement with the AOS drawings. We also added the hooks for the binary outputs to adjust the gain. However, these won't be activated until we receive the binary EP module. For now the gain adjust on the medm does NOT work and needs to be done with a breakout board directly at the DB37 of the PD amplifier.
J. Kissel Ran transfer functions of H1 SUS RM1 and H1 SUS RM2 after Jamie, Alexa, and Kiwamu adjusted the eddy current damping (see LHO aLOG 9034). Results look virtually the same as before (see LHO aLOG 8725); the transfer H1 transfer functions still look different from LLO's RMs, and there's still an anomalous feature in the Yaw to Yaw TFs for H1 SUS RM2. Things that *have* changed: - H1 SUS RM2 anomolous resonance has *moved* a little - The high-frequency magnitude for the L2L and P2P transfer functions of H1 SUS RM1 has increased by a factor of ~10 (!!) - The frequency at which the high-frequency magnitude turns from f^{-2} to f^{-1} has changed for all DOFs in both SUS. Please note that I'm still using an out-dated, incorrect model for the HTTS that do not include any eddy current damping or local damping. The measurements were taken with the local damping turned off. Mark is close, but not finished with the Matlab model modifications to address eddy current damping appropriately. Next time. I attach three different comparison plots, all with the same data sets, just different traces compared on different plots so you can see them all and compare them in different ways. - allhttss_2013-12-20_Phase3a_H1SUSRM1 ... has the L1 RMs and H1 SUS RM1 measurements before and after the latest adjustment - allhttss_2013-12-20_Phase3a_H1SUSRM2 ... has the L1 RMs and H1 SUS RM2 measurements before and after the latest adjustment - allhttss_2013-12-20_Phase3a_H1SUSRMs ... compares the latest measurements (after the adjustments) against each other, and the L1 RMs.
(Alexa, Sheila)
We adjusted the alignment on ISCTEX and have found a beatnote .
The crystal temperature was around 31.7 degC and the beatnote is -50dBm at 42MHz (see picture below).
After some alignment adjustment the beatnote is more like -40dBm. The pll is not locked yet but now we are ready to do the locking from the control room.
1.5 x 10-3 torr at pirani, 4 micron at TC gauge -> will compare TC reading on Monday
Today, in prep for the holiday downtime, I secured the ETMy installation hardware at Ey. I covered the Class A and B equipment that is parked around the cartridge cleanroom and weld room and I turned off as many lights as I could find switches and plugs for.
J. Kissel, J. Bartlett, A. Ramirez We've measured the open light currents on the newly cabled up H1 SUS SR2 (with a metal dummy mass), calculated and applied the compensating offsets and normalization gains, captured a new safe.snap, and committed it to the userapps repository. Details below! -------------- Using the matlab script /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/prettyOSEMgains.m the captured open light currents and calculated normalization gains and compensating offsets are >> prettyOSEMgains('H1','SR2') OSEM OLC [ct] Gain Offset [ct] M1T1 25985 1.155 -12992 M1T2 26833 1.118 -13417 M1T3 25702 1.167 -12851 M1LF 31475 0.953 -15738 M1RT 25346 1.184 -12673 M1SD 25571 1.173 -12786 M2UL 25576 1.173 -12788 M2LL 27473 1.092 -13736 M2UR 24401 1.229 -12201 M2LR 26282 1.141 -13141 M3UL 26043 1.152 -13021 M3LL 25772 1.164 -12886 M3UR 25342 1.184 -12671 M3LR 24901 1.205 -12451 These were manually installed in the H1:SUS-SR2_${ISOSTAGE}_OSEMINF_${DOF} bank, with ${ISOSTAGE} = [M1, M2, M3] and ${DOF} = [T1, T2, T3, LF, RT, SD] or [UL, LL, UR, LR] for M1 or M2/M3, respectively. Though Mark has written a nice utility for capturing safe.snaps (see LHO aLOG 5202), we needed to get this done fast, I hadn't used it before, neither Mark or Arnaud are here to help us if it breaks, so we captured the files "by hand" (which is quickest for me), hence: (1) Turned OFF the masterswitch. (2) Turned OFF all requested DAC drive (LOCK, TEST, and OPTICALIGN outputs all OFF), other than the damping filter outputs which remain ON. (3) Made sure the band-limiting filters were engaged in the filter banks preceding the watchdog trigger values. (4) Captured each suspension's safe.snap, saving over what is in the userapps repository, e.g. controls@opsws0:burtfiles 0$ pwd /opt/rtcds/userapps/release/sus/h1/burtfiles controls@opsws0:burtfiles 0$ burtrb -f /opt/rtcds/lho/h1/target/${ifo}sus${optic}/${ifo}sus${optic}epics/autoBurt.req > /opt/rtcds/userapps/release/sus/${ifo}/burtfiles/${ifo}sus${optic}_safe.snap (3) Ensured that the link to target directory (which is where the front end *actually* looks during reboot) was in place, e.g. controls@opsws0:burt 0$ pwd /opt/rtcds/lho/${ifo}/target/${ifo}sus${optic}/${ifo}sus${optic}epics/burt/ controls@opsws0:burt 0$ ls -l safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:46 safe.snap -> /opt/rtcds/userapps/release/sus/${ifo}/burtfiles/${ifo}sus${optic}_safe.snap (4) committed the new safe.snap to the userapps repository, controls@opsws0:burtfiles 0$ pwd /opt/rtcds/userapps/release/sus/h1/burtfiles controls@opsws0:burtfiles 0$ svn commit -m "Installed and captured new open light current gains and offsets." ${ifo}sus${optic}_safe.snap
With the H1 and L1 HIFO X runs approaching, I have revisited and updated the H1 HIFO Y line finding report I gave at the Hannover Detchar F2F meeting in September. Attached are slightly updated slides with some additional info (mostly on slides 42-44 with a few clarifications elsewhere) on lines found in the transmitted IR light on half-fringe power. Since I neglected to alog the original report, I am including the full report here for reference (both ppt and pdf, to enable future searches for particular frequencies - I hope).
(Alexa, Sheila)
I measured the fiber power from the PSL into the ALS Distribution Box to be 5.65mW which means we have 78.5% coupling to the fiber, which is what we expect. We also calibrated the internal PD in the box -- the responsivity is .33A/W.
Sheila, Kiwamu
We looked for the POP beam by opening up several viewports on both HAM2 and HAM3. However we couldn't find the POP beam mostly because none of the viewports were in a convenient location to look at the POP path. Also we looked at the swiss cheese baffle with both analog and GigE cameras from the HAM3 spool and jiggled the POP steering picomotor. We didn't see a beam hitting in the vicinity of the POP penetration hole. At this point, we have no idea of where it is stuck.
Sheila and Dave.
Sheila made changes to the following SUS models to add missing IPC channels (the existing models had place-holders for the IPC channels).
h1susbs, h1susetmx, h1susetmy, h1susim, h1susitmx, h1susitmy, h1suspr3, h1sussr2, h1sussr3 and h1sussrm. The model h1susprm had a simple text edit to clean it up.
We discovered an RFM0-RFM1 error on the h1asc and h1susetmy models. RFM0 is the X-Arm and RFM1 is the Y-Arm. I hand edited the H1.ipc file to change ETMY ASC PIT and YAW from RFM0 to RFM1.
All models were compiled and installed, the DAQ was restarted.
IPC data from ASC to SUS-ETMX and SUS-ETMY were tested to verify the RFM0,1 settings were correct.
The latest HPI tools development from Stanford have been installed. They ramp the controls a better way and close the Xterm windows 5s after scripts have successfully completed. I tried it on ITMY, everything worked well.
The LSC demodulator chassis (for ASAIR_A 45MHz, ASAIR_B 18 MHz, ASAIR_B 90 MHz) has been removed from slot 8 in the ISC R3 rack. This is for executing ECR E1300899, which calls for adding low pass filters to the 2f paths, and high pass filters for the 10f paths.
The plan is to actually modify this AS demod board with the needed POPAIR modifications and test, then do swapsy with the installed POPAIR demod and fix that board for reinsertion into the ASAIR slot.
Hard-close to soft-close GV7, Kyle Remove yellow covers on HAM2 and HAM3 to look for POP beam, ISC Look for ETMX ACB PDs through viewports, Richard Add IPC sends/receives in LSC and ASC models, Sheila DAQ restarts, Dave HAM1 POP beam look with IR only glasses (approved), ISC Flying a camera on the crane, Apollo Work on EY TMS, Corey, Jeff, Andres Guardian presentation/training, Jamie
(Andres, Corey, Jeff B, Keita)
Today the TMS Upper Structure was moved from its H2-BSC6 spot to its H1-BSC10 spot. For the most part it was straightforward, but it should be noted that there are issues with the Alignment Templates (i.e. "cookie cutters") and/or the Overall Drawing (D0902168).
Issue #1: When we used the called out alignment templates, it was noted that the counterbored holes were not useful, because to match the drawing, we have to flip the Templates over.
Issue#2: After we lifted the Upper Mass up to the Cookie Cutter and inspected the position of the Upper Mass, it was apparent we were just under an 1" off! This was with using the called-out Templates (#23 & 24) at the correct corners. We ended up switching the template out between corners (i.e. we used a #23 at the location the drawing calls for #24). This got us much closer to where we wanted to be....not perfect though, we were probably a few millimeters off.
At any rate, the Upper Mass is up & torqued down.
Spoke with systems - They confirmed the cookie cutter reference numbers were reversed on the drawing (D0902168 sheet #2). The cookie cutter #23 was the correct one to use in the A21/B51 by A26/B41 position. Systems has redlined the drawing with the correct placements.
TF crashed (watchdog trip) last night at 6pm local. Very weird. The attached plots show the details. First plot shows all the excitation channels for a 3 hour period around the watchdog trip, you can clearly see where we were driving at ~3000cts on each exc channel (this wasn't happening at the exact moment of the trip. The second plot shows the V4 excitation channel and the V4 L4C that tripped over a 100 second window. There is a very low drive, but high frequency excitation that does not look like the other parts of the transfer function being run at the time. But, this excitation is also roughly at the same time as when we were driving on a different (H1) channel.
Fabrice was able to copy the signal from the V4 excitation channel at the time of the trip and send it again with some matlab trickery, but we saw nothing on any of the chamber's (HEPI, ISI, SUS) sensors. So we still don't know what caused the trip. Weird.
The injection log file shows that a Matlab process on opsws1 started an awgstream excitation on channel H1:HPI-ETMX_OUTF_V4_EXC at GPS time 1071453844, for 1011 seconds. The monitoring of H1:HPI-ETMX_OUTF_V4_EXC_DQ was started 7 seconds earlier at 1071453837.