model restarts logged for Wed 21/May/2014
2014_05_21 12:44 h1fw1
unexpected restart of h1fw1
Greg/David/Thomas HWS - continued with alignment, position detectors were aligned using retro-reflected 532nm beam. TCSX - had been running since Monday am, turned off for a couple of hours this afternoon to re-route some water lines to allow the FLIR camera, screen and enclosure to protect the camera to be positioned on table. - FLIR camera connected up using laptop and the camera side of the screen was imaged. - Monitoring beam alignment was adjusted to centre the beam on this screen. Images taken and CO2 power onto this screen was slowly increased using rotation stage. Up to ~0.5W was projected onto this screen. Attached images show zero incident power (beam dumped but laser on), and ~500mW of incident power.
I've again redlined D1001132 and added this to the DCC Record. Again, balanced, floating(unlocked or off the 'stops') with C3 covers pulled back from OT for TFs. HEPI remains locked.
9:45 Jason HAM6 picking up IAS gear done 10:45 10 Corey in LVEA looking for IO stuff 10:15 DaveH to HWS HAM4 10:15 JeffB to HAM5 11:15 Travis to LVEA Test area 12:00JeffB out of LVEA, OFI installed 12:00 DaveH out of LVEA 12:45 LVEA transitioned to laser hazard 12:45 Karen to EY, back 14:30 13:15 MikeL to LVEA with small tour 13:15 DaveH to LVEA TCS tables 13:30 Travis to LVEA working on ACB 13:30 Mitch and Scott to LVEA looking for 3IFO parts 13:30 TVO Hugh to HAM4 and HAM5 to install oplev parts out at 16:00 13:30 JeffB and Andres to HAM6 to clean up out at 15:30 13:45 JustinB and DanH to LVEA and optics lab 14:45 TVo to LVEA TCS table
Just to compare what was posted at LLO yesterday https://alog.ligo-la.caltech.edu/aLOG/index.php?callRep=12702. I ran 128k 3Hz sinewave to each quadrant with -125k bias on the DC and looked at the responses. The good news is it actually responds. The bad new it trying to make it respond to sensible signals like a pitch or a yaw does not yield much in a way a results. I am sure Keita will have more to say. But attached are our results of a 3Hz injection
Hugh, Thomas The in-chamber optics are installed but not aligned yet, when the optical lever components on the outside of the chamber and the viewports are installed we will do the alignment portion.
Dave and I fixed up the method by which the sitemap is opened today, fixing the problems we've been having with openning guardmedm guardian controls screens. sitemap is now a script that should be in the path of all users (currently stored at /ligo/apps/linux-x86_64/utils/bin/sitemap). It works from the command line, and menu bar launchers. All other references to any other method of openning sitemap should be purged.
All sitemap calls should now also reuse ("-attach" to) the same MEDM session. If a sitemap is already running, it should raise the already running session.
Andres R., Gerardo M., and Jeff B. The OFI suspension was installed into HAM5. No problems were encountered during the installation.
This morning I restarted the suspension guardian nodes to bring them up to date with the changes Arnaud and I made yesterday (alog 11982). Almost immediately the BS started oscillating in yaw. I tracked the issue down to the BS optical lever loops (H1:SUS-BS_M2_OLDAMP_Y in particular). I believe cycling GRD:SUS_BS through it's graph, which shuts off the damping loops and alignments offsets, is what set it off. Even after re-enabling the damping and alignment offsets did not fix the issues, as the OPDAMP filters were rung up (the outputs continued to oscillate even after the inputs were shut off). After shutting off the OLDAMP loops the oscillations damped down, and once I cleared history and re-enabled the OLDAMP loops things came back to normal.
Clearly one problem is that the SUS_BS guardian is not handling the optical lever loop in the BS. It looks like only BS has OLDAMP engaged at the moment (excetly ITMX, which I'll mention in a minute). The SUS guardian probably should be making sure the OLDAMP controllers are shut off when the optics are not aligned. I'll work with the SUS team to get this fixed.
I'm not sure why ITMY has OLDAMP engaged where as the rest of the main suspensions do not. I'll look into that as well.
Guardian was modified and now TURNS OFF the oplev feedback when going to the MISALIGNED / DAMPED or SAFE state, so this kind of situation shouldn't happen anymore.
I reloaded guardian on suspensions with optical lever : BS ETMX ETMY ITMX ITMY PR3
SUS.py was commited under version #8042 of the svn
Measurements on lower stages (M2-M2 and M3-M3) of SRM succesfully completed yesterday night. The transfer functions are showing a good match with the model (plots pending).
Attached are the in chamber (HAM5 locked), in air, transfer functions and spectra plots for the three stages of SRM.
Betsy's adjustments to center the osem on M2 UR flag has alleviated any osem readout/actuation issues (cf M2 spectra and TF)
Attachments are in the following order :
model restarts logged for Tue 20/May/2014
2014_05_20 12:14 h1sussr2
Chris, Kiwamu, Lisa, Stefan After the 45MHz 12.6dB boost this morning we recommissioned the interferometer: - We realigned the whole interferometer. - We added ND0.4 filter on REFLAIR_A to avoid saturation. - We adjusted gains and phases to match REFLAIR_A_RF45, REFLAIR_B_RF27 and REFLAIR_B_RF135. - First we tried approaching the fringe from the left side. We were hampered by weird demod phases in RF45, as well as the appearance of a resonance in transmission of the y-arm. This probably is the 20 mode of the 45MHz. - We then decided to approach from the right side of the fringe. There REFLAIR_A_RF45 had the same demod phase as PRMI only. - We acquired 700 red Hz off resonance. - We decided to use both its I and Q for PRCL and MICH, because they looked cleaner at low frequency. - We transitioned at 700 red Hz to RF135. - We needed the following settings: REFLAIR_A_RF45 147deg (same for PRMI, and with arms) MICH GAIN 1.2 (UGF 6Hz), PRCL GAIN 0.8 (UGF 25Hz) - Next we started walking in. We needed to update the REFLAIR_B_RF135: 73deg (PRMI), 58deg (1kHz offset), 51deg (and MICH GAIN from 1.2 to 1.0)(450Hz CARM offset) 42deg (250Hz CARM offset) unlocked at 75Hz (up to 1 in ETMY transmission) - Next attempt identical, but no unlock 40deg (160Hz CARM offset) At 125Hz CARM offset we noticed that only the y-arm was building up, so we fine-tuned the DARM offset until the arms were symmetrical. 37deg (60Hz CARM offset) - Then we marched across the river. Some observations: - We had ad least a factor of 10 buildup. We should get more, but we were still moving across the fringe rapidly. - We looked at REFLAIR_A_RF9 but it was puzzling: only a large offset in I. - We then tried a pure DARM fringe offset, but this made the 3f signals flaky. - The 3f signals were fine across the resonance.
Resonant arms and words of wisdom.
It seems that some of the length degrees of freedom had an offset. It is not clear at this point which DOF was off from the operating point. The POP DC basically did not show a buildup at all when the arm was at a high value. The REFL DC did not become a smaller value. Plus, the demodulated signals at 1fs had an offset without any PDH-looking waveform during the arm was flashing. The attached shows the moment of the lock loss. You can see how they behaved odd.
After the people left, I made a few more attempts of this locking procedure last night. It worked robustly. The funny REFL9I offset was also seen consistently.
After the CARM offset was completely removed, I then got rid of the 135I and 135Q offsets to see if this helps the power buildup in the arm cavities. This actually made them worse --- the buildup in the arm cavities decreased by a factor 2 or so. Since the interferometer dropped the lock afterwards, I did not explore a bigger offset in the 135 signals.
Thomas, Greg, David HWS - X-end of table continued to be aligned. TCSX - - managed to get the FLIR camera to be connected up to a laptop. Will look to mount on-table tomorrow. - measurements made to calibrate the on-table output power meter. Maximum power of 2.36W for a rotation angle of 82.5degrees. - maximum measured power after the two polarizers was 40.85W. - maximum measured power after the mask was 10.1W --> this would indicate that a maximum power of ~5W could be incident on the CP. Will investigate further. TCSX laser will be left operating overnight.
The low transmission through the central mask is because - that mask was designed for use in the central heating path - the beam size in the annular heating beam path is ~2.5x larger than in the central heating path.
On friday night, the wind was high(~25mph), and the arm was hard to lock. Although the angular motion of the test masses was not particularly different than on a quiet night. First attachement shows the oplev spectra from friday night, when the wind was ~25mph. second attachement shows spectra from yesterday night with a 5mph wind.
To note :
We tracked down the problems we had in the past windy nights to be related with the ALS tidal tuning , but it is still good to make these plots with the OpLEv signals.
However, I think your plots didn't turn out the way you wanted to. There is only YAW in the second attachment.
Also, it would be easier to make a comparison if you put windy/quiet curves for each DOF in the same plot. Thanks!
thanks for noticing!
Attached are some other plots :
1. wind at corner and endy stations between may 17th/may 20th. High winds references are marked in orange, low winds is in green
2. Spectra comparison of ground sensors (HEPI STS) at end and corner stations with different winds. Blue and pink curves are during high winds (blue = may 17th, pink = may 18th). Red is during low winds (may 19th). From top to bottom rows : ETMX ETMY and ITMY. From left to right : X Y Z degrees of freedom.
3. Spectra comparison of oplevs during high winds (may 18th blue curve) and low winds (may 19th red curve) for ETMx ETMy and ITMy top to bottom. Left column is pitch, right column is yaw.