AlexaS, TravisS, RickS Yesterday (Friday) afternoon, we re-focused the Y-end Pcal beam localization camera for green light in preparation for next week's efforts to clean the ETM surface. The attached image was taken after re-focusing the camera, with the green light resonating in the Y-arm.
Dan, Evan
Some housekeeping for DRMI locking:
We wanted to reimplement the SRC WFS loops, but so far we are unable to get DRMI locks that are long enough to do anything useful with.
[Mackenzie, Evan, Paul]
Today we improved the alignment of the aux laser into HAM2, and after some searching around with the aux laser temperature control were able to observe the beat signal on the RFPD. The beat signal amplitude was around -45dBm at best, when we had 1.5V DC on the PD. I didn't check the difference between DC and AC gains for that pd, but we expect we should be able to get a significantly larger beat signal. We adjusted the aux laser alignment trying to improve the beat signal amplitude, but weren't able to get a big improvement. At this point we think that we are limited by the mode matching of the two beams: it's clear just looking at the card that there's at least a factor 2 in beam sizes at the IM4 forward trans beam path. Next step will be to make some quick mode measurements on the table and either adjust the lens currently in place or add some more to the path to get a better overlap.
Evan, Daniel, Stefan We duplicated the full WFS + camera auto-alignment scheme on the y-arm. In particular we - Restarted h1iscey.mdl to include the CAM.mdl change (SVN revision 9393) - Set the Y Green WFS autocentering UGF's to 10Hz. - Re-phased Y Green WFS using a 55Hz length dither. - Closed all loops with the same scheme as the x-arm (WFSA-->ITMY, WFSB-->TMSY, ITMY camera-->ETMY). The camera loop relies on gain hierarchy through the WFS loops. - The overall gain is slightly lower on the y-arm, but all seems to work. - Did a from-scratch baffle-PD alignment of TMSY, aligned the y-arm to it, updated the camera config file and took a camera reference. - All this again seemed to work fairly reliably. - All medm setting are shown in the attached snapshot (the PIT and YAW output matrices are identical). Still TBD: Same tweaking as for the x-arm: - Fine-tune the output matrix - in particular the DoF3 (camera path) should be set to move all 3 optic in the right way - this would avoid having to go through a gain hierarchy. - Increase the loop UGF: main pendulum notches are needed to avoid a 2nd unity gain crossing.
08:50 Start of 2nd cleaning at BSC10 08:52 Bubba to end Y to turn on purge air 08:53 Filiberto to beer garden to pull cables, may bump piers on BSC3 09:08 Jeff and Andres putting together contamination control kits in the LVEA 09:20 Bubba turning on purge air compressor at end Y 09:51 Cleaning crew leaving end station 10:16 Corey to squeezer bay 11:38 Jeff and Andres back 12:04 Filiberto and Aaron done 12:05 Krishna to end Y to check on BRS 12:34 Krishna back 12:53 Jeff to end Y, setup for vent 12:58 Travis and Rick to end Y for PCAL checkout 13:21 Jeff back 13:45 Corey done 14:25 Rick and Travis back
I though I would try sensor correction again on HAM3 and I've figured out from whence comes the .6hz peak on that chamber. I don't know why, but turning on the Z sensor correction causes it. X&Y sensor correction still don't perform well on this chamber either, so I'll leave both HAM2 and HAM3 with sensor correction off and in a state that my script (previous post) won't turn on. Attached plot shows Z CPS, correction on(blue) and off(red), .6hz peak is pretty obvious. This contaminates other dofs, too.
I've written another python script to turn on seismic sensor correction. The plan is to eventually put this under Guardian control, but I wanted to make a simple 1 button turn on tool for the commissioners. It lives in the same location as the other scripts: /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Misc/Test_Configuration_Scripts. Just cd into the fold run: ./Senscor_On.py or ./Senscor_Off.py as appropriate. This script turns on all the sensor correction on all of the chambers (ISI on HAM, HEPI and ISI on BSC), so it's more of a sledge hammer, not a scalpel.
Alexa, Daniel, Sheila, Stefan
From yesterday:
- We re-entered and re-focused the ITMX Green camera (#22). The picture is now good enough for feed-back use.
- Updated the camera config file (attached).
Today:
- Updated the CAM.mdl library in isc/common/models/ - it had normalized and non-normalized inputs switched.
- SVN Committed revision 9393
- Dave's script now copies the camera values into the H1:ALS-X_CAM_ITM_PIT_POS and H1:ALS-X_CAM_ITM_YAW_POS fields (see alog 15587)
- With the X Green WFS running (feed-back to ITMX and TMSX, auto-centering running) we engaged the feed-back loop to ETMX, relying on gain hierarchy through the WFS loops.
- All this seemed to work fairly reliably, although the WFS and camera gain are extremely low - it takes about 3 minutes for pulling in the alignment.
- With that in place, we did a from-scratch baffle-PD alignment of the whole X-arm, and noted the Green ITMX camera position: PIT: 236.78, Yaw: 354.8. For this we used the following script:
asc/h1/scripts/ditherAlign.py TMSX
- All medm setting are shown in the attached snapshot (the PIT and YAW output matrices are identical).
Tweaking that could still be done:
- Fine-tune the output matrix - in particular the DoF3 (camera path) should be set to move all 3 optic in the right way - this would avoid having to go through a gain hieararchy.
- Increase the loop UGF: main pendulum notches are needed to avoid a 2nd unity gain crossing.
I've tried turning on ISI sensor correction at HAM 4 and 5, it seems to be working. At first I thought HAM5 was not working as well, but there must have been somebody out on the floor near the chamber, because now both chambers are performing similarly. Attached plots show only the CPS_X side of things, but the GS-13 plots weren't as clear and I'm not sure how to calibrate their signals so they line up with the STS, but GS-13's seem to agree in spirit. Correction also is working similarly in all degrees of freedom. I did this a while ago at HAM6 as well, but I don't think I saved the data. HAM's all use the same configuration with the Hua filters in X&Y and Mittleman's Z filter.
J. Kissel I've solved the loose wires in the software problem indicated a bit ago in in LHO aLOG 15571, with the sledge hammer solution of restarting all of the front end processes. Unfortunately this is now quite an arduous process. Details of exactly what I did are below, but the problem is now solved. This is another data point on Integration Issue 931, which remains open, because these errors happen only once every month or so -- enough time for other CDS fires to overwhelm this one. Curiously, it took two starts of the IOP process in order to get the AWG light to behave. Another mystery. -------- Restart process (1) Turn off all sensor correction, because this is not yet under guardian control. Set H1:ISI-*_ST1_SENSCOR_GND_STS_?_MATCH_GAINs to 0, and turn off OUTPUT switch for good measure (2) Request Manager SEI GUARDIANs to take the chambers to OFFLINE (noting the state from whence they came. Beam Splitter is ISOLATED_DAMPED, ITMs are FULLY ISOLATED) (3) Save any alignment offsets on the SUS for the current state they're in, if GUARDIAN is warning you they're not saved (4) Request the SUS GUARDIANs to take the SUS to SAFE (noting the state from whence they came AND the EPICs values of the alignment offsets) (5) Take the opportunity to grab a updated safe.snap file, and commit to userapps repo. jeffrey.kissel@operator1 ]$ makeSafeBackup sus h1susbs (6) Log into the h1susb123 front end as controls (7) Kill all USER front-end processes controls@h1susb123 / 0$ killh1susitmx controls@h1susb123 / 0$ killh1susitmy controls@h1susb123 / 0$ killh1susbs (8) Restart IOP front process, make sure to have GDS_TP screen open, to hit the BURT button once EPICs comes back controls@h1susb123 / 0$ starth1iopsusb123 h1iopsusb123epics H1 IOC Server started Burt restored /opt/rtcds/lho/h1/target/h1iopsusb123/h1iopsusb123epics/burt/safe.snap Old : H1:FEC-28_BURT_RESTORE 1 New : H1:FEC-28_BURT_RESTORE 1 * WARNING: awgtpman_iop has already been started. controls@h1susb123 / 0$ (9) Restart USER front-end processes, make sure to have GDS_TP screen open, to hit the BURT button once EPICs comes back controls@h1susb123 / 0$ starth1susitmx h1susitmxepics: no process found h1susitmxepics H1 IOC Server started Burt restored /opt/rtcds/lho/h1/target/h1susitmx/h1susitmxepics/burt/safe.snap Old : H1:FEC-29_BURT_RESTORE 1 New : H1:FEC-29_BURT_RESTORE 1 * Starting h1susitmx awgtpman ... [ !! ] controls@h1susb123 / 0$ (rinse and repeat for the other two SUS) (10) Reset all watchdogs on SEI, SUS, and IOP (there's about 30). << --- It's only at this step d'you know if you've actually fixed the problem (11) Request SUS GUARDIANs to return to original state (whether it be aligned or misaligned, make sure alignment offsets have been restored properly) (12) Request SEI Manager GUARDIANs to return to original state (13) Go through CDS OVERVIEW Screens and hit "DIAG RESET" in the upper left corner of any GDS_TP screens which show an IPC Error in the CDS STATE WORD. The IPCs glitch on start up, and the error latches, so it just needs to be cleared. If it goes red again after a few seconds, then there's *actually* a problem. (14) Turn sensor correction back ON by first turning ON the MATCH OUTPUT, and then ramping up the gain back to 1.0, with a ramp time of something like 10 to 15 seconds. I've turned on the following sensor correction configuration configuration for all three BSC chambers: - Ryan's IIR filters, SC-rdr, FM2 for X & Y with a gain of 1.0. Only the BS has a "MATCH" filter (just a gain of 1.03), which I've left ON as I'd found it. - Rich's IIR filters, Mitt_SC, FM6 for Z with a gain of 1.0. For the record, both the ISI and HEPI Sensor Correction Screens still suck: - The filters that we actually use in the GND sensor correction are not visible on the sensor correction overview - The links to sub-screens are ambiguous locations on the SC overview. Thus, one can pull up different screens -- that don't look different at first glance -- depending on where you click - In the HEPI sensor correction overview, there's no link for the full MATCH filter bank, so you have no control over / knowledge of important things like the ramp time - Remove ST0 to ST1 HEPI L4C Feed forward path, it's currently not used and there's scientific motivation (pending) that it should never be used.
Looking at the sensor readbacks they seem to work.
At Daniel's request I extended my cameracopy.py script to also copy the ITMX green digital video data (centroid position and sum) to the ALS-X front end.
I have documented this system on the CDS wiki https://lhocds.ligo-wa.caltech.edu/wiki/CameraCopy
I have created an MEDM, accessible from the sitemap SYS pull down (screen shot attached).
Dave O, Greg, Elli
Yesterday we tried to realign the Hartmann sensors in the corner station. This is because 14-11-12 17:15:00 the SR3 mirror changed alignment which threw out the HWS alignment. We found the alignment is now so bad the periscopes will have to be moved. I still need to do this. If the alignment of the SRC, BS, or ITms changes again we will have to realign the HWS again.
Are there any photos of the current positions of the green beams at the HWS periscopes?
Vent prep: While the commissioners were at a stopping point, I made a new h1susetmy_safe.snap file and committed it to the svn. The ETM was restored to their working configuration afterwards.
K. Venkateswara,
As reported yesterday, winds were gusting at 60 mph, at the corner station and roughly 40 mph at EX. They were mostly blowing across, ~ along Y direction for EX. I've attached ASD plots showing the tilt-subtraction during the period with higher wind speeds (GPS time 1102388000 - 1102403000), and the low-wind period (1102408000 - 1102413000).
The residual after tilt-subtraction is much higher during the windy period than without. But it is possible that the floor is being displaced that much more by the wind. The high-wind period drove up the resonance of the BRS, which is why the harmonics of the beam-balance are visible in the low-wind period. But otherwise the residual is as low as during other quiet periods.
Vent of BSC10 scheduled for Monday morning, door removal on Tuesday Request for laser safe at end Y before Monday morning 2nd cleaning of BSC10 this morning Purge air needs to be turned on this morning Request to align end Y PCAL sometime during vent CDS Cabling in beer garden Putting v6 AA boards back in chassis Repair of ESD connectors next week SEI BRZ subraction on BSCs 3IFO Corey and Suresh working on ISC kits in squeezer bay
model restarts logged for Thu 11/Dec/2014
2014_12_11 20:16 h1iopsusb123
2014_12_11 20:17 h1iopsusb123
2014_12_11 20:17 h1susitmx
2014_12_11 20:19 h1susbs
2014_12_11 20:19 h1susitmy
No unexpected restarts. Restart of h1susb123 to clear DAC problem. Conlog frequently changing channels list attached.
The last couple of days Krishna and I have been working on sensor correction everywhere, but have been having troubles on HAM3. This is not exactly related to that effort, but we noticed that there is a very Q-y feature in the HAM3 ISI and SUS spectra. Jeff helped me dig into this and we are pretty sure this is not due to the suspensions, but it's been there the last couple of days, with and without sensor correction. It doesn't show in HEPI or the ground spectra, so I'm not sure where this comes from. When the IMC isn't being used I will try turning isolation loops off to see if the ISI is causing it. Attached spectra is of the MC2 suspension point(ISI GS-13's), but PR2, MC2 OSEMS and ISI CPS's see this, as well.
And by "pretty sure" it's not the SUS, Jim means "it's definitely not." The first HSTS modes are at 0.67 [Hz], and the recent design study (see G1401291) have revealed that even with crappy legacy damping filters and gains that are still in place, the Qs of all the modes are reduced well below what's seen here. Also of note -- The 0.6 [Hz], and 1.5, and 2.9 [Hz] features are seen in IMCL, PRCL, and the HAM Optical lever, so it's definitely the ISI, because it's common to both SUS in the chamber and their moving mass doesn't couple well enough to the ISI to move the thing in all DOFs like is shown here.
And now you don't!
I started looking for the .6hz whatsits and it's gone now. The local sensors didn't see it when I looked this morning, but looking back in time it disappeared some time between 16:00 (first plot) and 16:30 (second) yesterday. We are also seeing something similar on the ITMs' oplevs (third plot, you can see it in Krishna's post about Xarm sensor correction, too) now as well, so whoever fixed HAM3 should keep going.
