Today, I added the BS elliptical baffles (both HR and AR) to the suspension in addition to the remaining lower structure support brackets. As of now, the payload of the SUS is as accurate and complete as it can be without having the optic installed. It should not change much once the optic is installed (probably on the order of 10s of grams difference?). Once a decision has been made with regards to the placement of the structure on the ISI table, SEI can rebalance and begin their testing.
Did the same as was done for h1ecatc1. There are now three gateways running on this machine. I set the affinities for these tasks to all of the CPUs. This had to be done earlier for h1ecatc1 to fix problems with the EPICS update rate.
Mark B. Andres backed out the BOSEMs on PRM and PR3, and the AOSEMs were already out, so we measured the OL counts: prettyOSEMgains(logOLs('H1','PRM'),'PRM') M1T1 24867 1.206 -12434 M1T2 27695 1.083 -13847 M1T3 26803 1.119 -13401 M1LF 27765 1.081 -13882 M1RT 29899 1.003 -14949 M1SD 26998 1.111 -13499 M2UL 24409 1.229 -12204 M2LL 25575 1.173 -12787 M2UR 25475 1.178 -12738 M2LR 26427 1.135 -13214 M3UL 24962 1.202 -12481 M3LL 24710 1.214 -12355 M3UR 26711 1.123 -13356 M3LR 25557 1.174 -12778 prettyOSEMgains(logOLs('H1','PR3'),'PR3') M1T1 25835 1.161 -12917 M1T2 30072 0.998 -15036 M1T3 28666 1.047 -14333 M1LF 25623 1.171 -12812 M1RT 25798 1.163 -12899 M1SD 28238 1.062 -14119 M2UL 17706 1.694 -8853 M2LL 20285 1.479 -10142 M2UR 18746 1.600 -9373 M2LR 17714 1.694 -8857 M3UL 17313 1.733 -8656 M3LL 22891 1.311 -11445 M3UR 24376 1.231 -12188 M3LR 17159 1.748 -8580
Mark B. I entered all the above gains and offsets into the various OSEMINF blocks for PRM and PR3, checked that OSEM2EUL, SENSALIGN, DAMP, DRIVEALIGN, EUL2OSEM and COILOUTF were all correct, and updated the safe.snap files (in the new locations that Jeff K had just moved them to!).
RCG 2.6.1 now authorizes 512 IPC channels (previously limited at 64 channels with RCG 2.5). The communications channels between the BSC-ISIs and the QUADs were added at ITMY (BSC1) and renamed at ETMY (BSC6).
After assessing the location of every subsystem's safe.snaps in the userapps repository, then discussion on the CDS software meeting yesterday, we determined that each subsystem's safe.snap should live here: /opt/rtcds/userapps/release/${subsystem}/${ifo}/burtfiles/${modelname}_safe.snap where ${subsystem} = [isi, sus, psl, etc.] , ${ifo} = [l1, h1, i1] , and ${modelname} = name of simulink model (sans the .mdl extension) . ISI and PSL already obey this convention, but SUS had put the .snaps in subfolders of the burtfiles directory named after the optic motivated by still-under-developement Guardian work at LLO. As of this entry, all SUS (including h1susim, and h1sustmsy) safe.snaps have been moved out of their sub-folder into the "top level" burtfiles folder, and the corresponding soft link in the target directory has been updated: controls@opsws1:target 0$ ls -l h1sus*/h1sus*/burt/safe.snap lrwxrwxrwx 1 controls controls 65 2013-01-17 12:46 h1susbstst/h1susbststepics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susbstst_safe.snap lrwxrwxrwx 1 controls controls 64 2013-01-17 12:46 h1susetmy/h1susetmyepics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susetmy_safe.snap lrwxrwxrwx 1 controls controls 62 2013-01-17 12:46 h1susim/h1susimepics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susim_safe.snap lrwxrwxrwx 1 controls controls 64 2013-01-17 12:46 h1susitmy/h1susitmyepics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susitmy_safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:46 h1susmc1/h1susmc1epics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susmc1_safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:46 h1susmc2/h1susmc2epics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susmc2_safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:47 h1susmc3/h1susmc3epics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susmc3_safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:47 h1suspr2/h1suspr2epics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1suspr2_safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:47 h1suspr3/h1suspr3epics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1suspr3_safe.snap lrwxrwxrwx 1 controls controls 63 2013-01-17 12:47 h1susprm/h1susprmepics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susprm_safe.snap lrwxrwxrwx 1 controls controls 67 2013-01-17 12:47 h1susquadtst/h1susquadtstepics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1susquadtst_safe.snap lrwxrwxrwx 1 controls controls 64 2013-01-17 12:48 h1sustmsy/h1sustmsyepics/burt/safe.snap -> /opt/rtcds/userapps/release/sus/h1/burtfiles/h1sustmsy_safe.snap controls@opsws1:target 0$
[Cheryl V, Giacomo C, Paul F]
Today we tried measuring the OLTF at the IMC 'common mode' servo board. This required locking the IMC of course, which we were able to do at about 1pm without much trouble (as previously). With the settings that we were using for the initial locking, we saw a UGF of about 1.8kHz. To compare with William Korth's LLO alog entry 4182 where a UGF of 14kHz was reported, we increased the common mode gain until we matched the UGF of 14kHz. We required a common mode servo gain of 10dB to reach a UGF of 14kHz, whereas at LLO the corresponding gain was -2dB. The difference in gains required (12dB~ factor 4) was close to what we would expect given the different laser power (200mW here versus 1W at LLO).
However, there was still some work going on around the chamber at that time, so we decided to go for lunch before recording an OLTF to post. After coming back, we then found it very difficult to lock the mode cleaner again. We could get short locks, but nothing more than 15 seconds. As far as we could tell, nothing had changed in terms of gains or offsets inbetween (we had brought the common gain back to our previous locking value of -4dB). We then spent a lot of time trying unsuccessfuly to adjust gains, offsets, and filters to get a stable lock. We did eventually get some longer locks (~30 seconds) after increasing the watchdog limits for MC2 M2 and M3, but then we noticed an oscillation in the length feedback channel after M2 feedback was applied (see attached plot).
Some possible causes for the change in the locking situation are:
We'll keep trying to get the IMC locking up and running again tomorrow so we can look at some WFS signals.
[Paul, Cheyl, Giacomo]
Between Monday and Tuesday we worked at the IOT1 (also very confusingly known as IOT2L = IOT HAM2 Left). We rearranged the IMC refl beam path according to the layout D0902284 (it had previously been layed down temporarily to get an error signal for the IMC locking asap) with the following exceptions and notes:
- the high power beam dump is not there, so we are going on a normal razor-blades beam dump (we will not be using high power though). Also, the other components on that path are not there/in place.
- as per Chris suggestion, we placed that HWP in front of IO_MCR_BS1 instead of in its original location. However, we noticed that it reduced the power at the RFPD by about 50% (independetly from its orientation), so we decided to remove it untill we are confident with IMC locking.
- the shutter is not there
- the GiGe camera is not yet available, so we put an analog camera in its place
- some adjustment has been done to the WFS path, to accomodate for the focal lenses of IO_MCR_L2 and _L3 that are slightly different than the design values. See the following for details.
A few pictures attached.
For the WFS path, we placed IO_MCR_L2 in its nominal position, and performed a beamscan using the Ophir Nanoscan. Beamscan1.pdf shows the fit to the horizontal and vertical beam sizes (w0 is ~50 um for both horizontal and vertical)
Also, we measured the beam at a fixed position for different rotations of the nanoscan head around the beam axis, to look for systematics in the observed ellipticity, but we didn't find a relevant effect.
After putting IO_MCR_L3 in a position (it turned out to be about 2" further downstream wrt nominal) that would give about the same waist size quoted on the layout (300 um) we repeated the beam scan, shown in Beamscan2.pdf (w0 is ~275 um for horizontal and ~250 um for vertical).
We then placed the two 45 deg mirrors, put the beamscan downstream and identified the positions (in front and after the waist) in which the beamsize was sqrt(2)*waist (this corresponds to +-Zr from the beam waist, or +-45 deg Gouy phase). As these positions are different wrt the horizontal or vertical beam profiles, we placed each WFS at an intermediate one.
Note that, because the optic mounts have slotted bases, we used temporary clamps to place the 45 deg mirrors in the ideal position (beam centered on the mirror and reflecting at 90 deg). However, later on it was decided to slightly move the mirrors so that they could be screwed to the closest usable hole on the table, thus modifying the pathlength to the two WFS (wrt the waist) by a few mm each. The position of the WFS was not corrected, so for now it can be sxpected to be off by that much (the error is anyhow comparable to the difference between the ideal position for the horizontal or vertical beam profile).
It's also worth mentioning that after a few hours that the WFS were connected to the electronics, we noticed that the metallic enclosure of WFS_A (and only that) was unusually hot to the touch(about 40 C?). We disconnected it and run a series of electrical tests both Tuesday evening and Wednesday morning, without finding any evidence of malfunction. It has been connected since this morning and the temperature seems equal of that of WFS_B (i.e. slightly warmer than ambient). We'll occasionally re-check the temperature of the WFS during the next days.
Finally, Cheryl routed the IMC transmitted beam down the periscope and into another analog camera.
Gate valve 18 was closed at 11:45AM and then open again at 3:45PM Hydrocarbons were still elevated at the y end and easy to measure without accumulation on a liquid nitrogen trap. Although water has come down as 1/t, it seems that the hydrocarbons are not attenuating as quickly. The analysis of the runs made over the last two days will be available within the next week and posted both in this log and in the DCC.
Input/Output filters: Installed, enabled on both ISIs
Symmetrization filters: Installed, enabled on both ISIs
Damping loops: Installed, running on both ISIs
Blend Filters:
-> We will leave HAM2/3-ISIs in this known configuration for the night.
UGF = Unity Gain Frequency
* Blend filters used:
-X,Y,Z: 100mHz
-RX,RY,RZ: 250mHz
One more corner down. Did Corner 3 (SE) on WHAM2 this afternoon. Was requested to leave the system locked tonight but before locking, maximum local motion was maybe 1 mil so there should be no problem for the Mode Cleaner Crew. WHAM2 ***HEPI Locked***, but if there is time, tomorrow I'll unlock gain and finish the final corner(SW) at HAM2.
Today I added the h1ascimc model to the DAQ. I installed LLO's SVN version of the safe.snap (12dec2012) which gave a few errors but seems to have gotten the WFS signals going. We also installed the latest fiter module file from LLO (modied 15jan2013).
The initial install h1h1ascimc with dcuid=19 caused some testpoint issues today. This was resolved by removing the dcuid=19 from the testpoint.par file, leaving the correct dcuid=20 in that file.
Note that h1asc0 is still not on the Dolphin IPC network, nor are its PIT and YAW control signals being received by MC1,2,3. We should schedule these changes with the IMC group.
Today was split between me, Pablo, and Patrick at the end of the day
John W. had soft-closed this earlier in the day for Apollo's clean-room craning/repositioning over GV20
Indicated He baseline of 4.5 x 10-10 torr*L/sec at start -> 10 second audible blast at each conflat joint and 5 second audible blast in volume between each window and corresponding guard shutter Note: There is still an untested electrical feed-through flange on south side of HAM2 between the support tubes but it is not accessible
(Betsy, Gerardo)
Both sets of prisms have been glued onto the BS.
Prism SN 41 was used for the ARM side, and Prism SN 40 was used for 180ARM side.
ARM side results:
Measurement from S1 to the fiducial side of the prism, 20.08 mm + 9.99 mm (prism Wp/2) = 30.07 mm
The measured distance from the centerline of the primary prism to the S1 surface is 30.07 mm, the target is 30.04 mm, so this gives us a +0.03 mm, away from S1 surface, but well within the +-0.1 mm.
180ARM side results:
Measurement from S1 to the fiducial side of the prism, 40.07 mm - 10.01 mm (prism Wp/2) = 30.06 mm
The measured distance from the centerline of the primary prism to the S1 surface is 30.06 mm, the target once again is 30.04 mm, so this gives us a +0.02 mm, away from S1 surface, but well within the +-0.1 mm.
Replaced the dust monitor labeled 'C' at LVEA location 15 in the clean room over BSC1 with the dust monitor labeled 'P'. The dust monitor labeled 'C' was reporting occasional calibration failure errors.
We ran Phase 1b power spectra on the India HLTS PR3 this morning. The plots are in the attached files. The results are positive. If the results are approved by the testing group, we will put this suspension into storage. I have added these results files to SVN.
Mark B. Travis reports that he found some blade stops touching on the BS, so I'm starting another round of DTT TFs for the BS.
Mark B. TFs were attempted but have been put on hold because F1 OSEM was badly centred (21K raw, 7K normalized), causing the IOP WD to trip after a minute or two of the usual level of excitation. Travis is on his way to make adjustments. Measurement Status light will go back on when TFs are resumed.
Mark B. Success: ^/trunk/BSFM/H1/BSTST/SAGM1/Data/2013-01-15_1200_H1SUSBSTST_M1_*_WhiteNoise.xml All the plots look good. Correction - plots initially posted were from Monday.
Mark B. Comparison plot.