Here is the list of commissioning task for the next 7-14 days:
Green team:
Red team:
Blue team (ALS WFS):
Blue team (ISCTEY):
TMS:
SEI/SUS team:
Yesterday on Sunday, Mitchell and I got 6 of the 8 HEPI Actuators attached. The remaining corner (NE#4) should fall by late morning Monday along with any alignment adjustment obvious from the Dial Indicators. So far the DIs are looking pretty good as to alignment. If IAS has its instruments at the ready, we should be complete by mid-day with post actuator install check/adjustments.
The ISI has a C3 cover on it so is not fit for TFs. SUS and TMS should however feel free to do evaluate their systems.
I found that the most of the ISIs had been tripped. Probably it was due to the earthquake as logged by Jeff (alog 10638).
I untripped the following systems:
Currently I am having a trouble in engaging the Tcrappy blend filter on stage 2 of ITMX. I am leaving it with the simplest filter, i.e. "Start", for now.
Assuming the frequency calibration of the network analyzer is accurate, we can compare the measured PRC length with the measured mode cleaner length. This was measured in alog 9679.
Parameter | Value | Unit |
---|---|---|
FSRPRC | 2.600075 | MHz |
LPRC | 57.6508 | m |
FSRMC | 9.099173 | MHz |
LMC | 16.473612 | m |
FSRMC / 3.5 - FSRPRC | -306 | Hz |
(1 - FSRMC / 3.5 FSRPRC) LPRC | 6.8 | mm |
Compared with the modeclaner, the power recycling cavity is about 7 mm too short. The other way around, the modecleaner is about 2 mm too long.
We hooked up the network analyzer to the timing comparator/frequency counter and set it to 40 MHz sharp at 0 dBm. The readback value was dead on, occasionally we would read 1 Hz higher. Conclusion: the frequency of the sweep is no more than 1 Hz off, even at 100 MHz.
I've redone the fits using both the magnitude and the phase. The fitting function is now the usual Fabry–Pérot reflectance function, with a complex magnitude to allow for global amplitude rescaling and global phase offset.
Nominal FSR | Frequency (Hz) |
−39.5 | −102 701 040 ± 200 |
−39.5 | −102 700 900 ± 220 |
−26.5 | −68 900 600 ± 180 |
−12.5 | −32 500 080 ± 100 |
12.5 | 32 501 720 ± 110 |
26.5 | 68 903 940 ± 200 |
39.5 | 102 704 700 ± 200 |
The linear fit now gives an FSR of (2 600 073 ± 9) Hz. This is consistent with the previous fit, and anyway the total error is still dominated by some systematic, as seen by the fact that the residuals are excessively large.
Taking a systematic 400 Hz uncertainty on the residual for the 12.5 FSR measurement gives a systematic uncertainty of 32 Hz on the PRC FSR. Propagating foward gives (57.6508 ± 0.0007) m.
J. Kissel As of 2014-03-10 03:00 UTC (08:00p PT), I've left the functional BSC-ISIs in the following state: ITMY BS ITMX ETMX Iso Blend | Iso Blend | Iso Blend | Iso Blend | HPI Lvl 1 "Pos" | Lvl 1 "Pos" | Lvl 1 "Pos" | Lvl 1 "Pos" | ST1 Lvl 3 "TCrappy" | Lvl 2* "TCrappy" | Lvl 3 "TCrappy" | Lvl 3 "TCrappy" | ST2 OFF | OFF | OFF | OFF I left ST2 OFF, because I want to get a measure for the differences between chamber performance is as related to the differing input motion at low frequency. Unfortunately, the ISI BS's level 3 controller appears to be unstable, so I had to stick with Level 2, but this shouldn't matter for the regions I'm looking to study. I've also made sure all optical levers are aligned.
J. Kissel I've grabbed spectra from all possible degrees of freedom of the ground, HEPI pier, and ISI ST1 for the four operational ground sensors and the four operational BSC-ISIs during a very windy and noisy afternoon this past Thursday, Mar 6 2014 at 22:15 UTC. This will hopefully assist modelling efforts to design blend filters that might be able to withstand such input noise. Unfortunately, because Sebastien was commissioning a few chambers, and we had to reboot ETMX to get his GND T240 stored in the right place, there wasn't any long stretch of time during that day in which all platforms were at comparable performance (hence the differences in the ISI ST1 performance). Also, I'm not sure I believe what the rotational HEPI L4Cs are saying at the microseism. The spectra are attached, but they were created by the following DTT templates, /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/ 2014-03-06_2215UTC_GroundMotion_ASDs.xml 2014-03-06_2215UTC_HEPIPierMotion_ASDs.xml 2014-03-06_2215UTC_ISIST1Motion_ASDs.xml and they were also exported to the following files /ligo/svncommon/SeiSVN/seismic/BSC-ISI/H1/Common/Data/ 2014-03-06_2215UTC_Windy_GroundMotion_ASDs_ITMY-XYZ_HAM2-XYZ_HAM5-XYZ_ETMX-XYZ.txt 2014-03-06_2215UTC_Windy_ISIST1Motion_ASDs_BS-XYZRXRYRZ.txt 2014-03-06_2215UTC_Windy_ISIST1Motion_ASDs_ETMX-XYZRXRYRZ.txt 2014-03-06_2215UTC_Windy_ISIST1Motion_ASDs_ITMX-XYZRXRYRZ.txt 2014-03-06_2215UTC_Windy_ISIST1Motion_ASDs_ITMY-XYZRXRYRZ.txt 2014-03-06_2215UTC_Windy_PierMotion_ASDs_BS-XYZRXRYRZ.txt 2014-03-06_2215UTC_Windy_PierMotion_ASDs_ETMX-XYZRXRYRZ.txt 2014-03-06_2215UTC_Windy_PierMotion_ASDs_ITMX-XYZRXRYRZ.txt 2014-03-06_2215UTC_Windy_PierMotion_ASDs_ITMY-XYZRXRYRZ.txt where the last part of the file name indicates the order in which the channels have been exported.
Alexa, Sheila
We tried engaging the refl DC bias path with the 1.6Hz pole :40Hz zero engaged. We were able to measure a tranfer function using 0dB on the CM in1 gain, and -80 in REfl DC bias, which has coherence to about 2Hz. (the UGF is around 3.5Hz). We tried to push the gain up and engage the boost to get a better measurement, but now we seem to have an earthquake from Mexico tripping our ISIs, so we are done for the day.
All ISIs except for the BS tripped Mar 10th 2014 ~00:58 UTC, most likely from 6.3 Mag Mexican Earthquake (see USGS Page), which happened at Mar 10th 00:38:20 UTC. *sigh* Well, THAT's annoying. Delightfully however, once untripped, the guardian brought the HAM2 and HAM3 ISIs back up to full isolation.
Yuta, Sheila, Alexa
Today we found an alignment that should be acceptable to both PRMI and the Xarm, in the hopes that the green team and red team will not each have to change PR2 significantly each day.
First Yuta aligned PRX, then we aligned the Xarm, locked the IR to the X arm, and moved PR2 and IM4 to point the beam down the xarm. After this the alignment of PRX was way off and unlockable. We checked that the beam was centered on POPAir B, then restored PR2 to the intial PRX alignment. Then Yuta aligned PRM by hand, and walked PR2 back to the arm alignment. Finally Yuta realinged PRY. A screenshot of the final positions is attached.
Yuta has changed the dither guardian script for PRX so that the PR2 dither is now fed back to PRM instead of PR2.
Hopefully this means that the PRMI and arm alignments will stay compatable and both the red team and green team don't have to spend as much time aligning each day.
Just an observation from this morning:
I wanted to see how much power build up the PRC can achieve without touching the alignment. I reverted PRM, BS and ITMY to the values that Sheila had in her screen shot because their alignment wasn't saved and they had come back to some past values by the guardian. The highest build up I saw was about 12 uW in POPAIR_B_RF18 which is about 6-7 times smaller than the highest in the past. Not bad.
Note that ITMX, ETMX and TMXS had different alignment biases than that in the screen shot. I assumed that there had been a fine touch by the green team and I didn't revert them to the screen shot values. The green light mostly stays on a 01 mode and occasionally on a 00 mode.
J. Kissel While gathering data of the ground motion from Thursday's windy afternoon, I found that the calibration filter used to turn the ground inertial sensor into (asymptoting to) 1 [nm/s] (at high-frequency) for the new, temporary, T240 at End X (see LHO aLOGs 10594, 9758, and D1400077) was incorrect. The "Cal" filters in FM1 of the H1:ISI-ETMX_ST1_GNDSTSINF_[A,B,C]_[X,Y,Z] banks were ON and still calibrating for an STS2 read-out chain, i.e. 1 / (1500 [V / (m/s)] * 40 [V/V] * 2^16/40 [ct/V] * 1e-9 [(m/s) / (nm/s)]) = 10.1725 [(m/s) / ct] These filters were most likely installed and turned on by some script that was preparing for the permanent solution; not surprising. I've installed a new filter in FM2 of all nine banks, called "T240Cal" with the following gain: 1 / (1200 [V / (m/s)] * 2 [V/V] * 2^16/40 [ct/V] * 1e-9 [(m/s) / (nm/s)]) = 254.3132 [(m/s) / ct] where I've assumed that the Trillium Interface Chassis is configured in its low-gain mode, with a gain of 2.0. I attach a spectra of data in the past, comparing all four ground inertial sensors, with the ETMX GND sensor corrected for the factor of (254.3132 [T240] / 10.1725 [STS]) = 25.0 [T240/STS] difference in gain between the STS and T240 calibration. Where we expect the ground motion to be coherent, namely between 0.1 and 0.5 [Hz], the ETMX sensor matches all three corner station's sensors exquisitely, and the micro seismic peak is roughly 1e-6 (m/s)/rtHz as expected. As of now, until the T240 is replaced with an STS2 as designed, the ETMX_ST1_GNDSTSINF_[A,B,C]_[X,Y,Z] filter banks should have FM2 ON and FM1 OFF. Once the T240 is replaced by an STS2, we can switch back to using FM1, and "T240Cal" should be removed from FM2 to avoid confusion. All calibration values were obtained from D1001575.
As of this entry (roughly 2014 March 9th 22:15 UTC) the channels H1:ISI-GND_STS_ETMX_X_DQ H1:ISI-GND_STS_ETMX_Y_DQ H1:ISI-GND_STS_ETMX_Z_DQ are therefore correctly calibrated version of the end stations ground inertial sensor, i.e. 1 [(nm/s) / ct] (above ~[4 mHz]). As with any STS / T240, the signal is trustworthy up to ~30 [Hz], where the instrument's response is rolled off internally. Also, I've committed the current filter file with the correct gains into the userapps repo, /opt/rtcds/userapps/release/isi/h1/filterfiles/H1ISIETMX.txt, removed the local copy in the chans directory, and made it a soft link to the repository version, controls@opsws2:chans 0$ ls -l H1ISIETMX.txt lrwxrwxrwx 1 controls controls 60 Mar 9 15:16 H1ISIETMX.txt -> /opt/rtcds/userapps/release/isi/h1/filterfiles/H1ISIETMX.txt controls@opsws2:chans 0$ (So far this is the *only* ISI to have it's filter file soft-linked.)
Just finished up the March Public Tour. I took the group up on the roof around 2:50-3:00pm.
Engaged DOF1P, DOF1Y and DOF2Y, dithered ITM and ETM, and measured the sensing matrix based on OL (assuming that OL calibration is now correct).
WFSA | WFSB | |
ITMP | 82.8 cts/urad | 901.8 |
ETMP | -430.8 | -1247.8 |
ITMY | -587 | 671 |
ETMY | -504 | 292 |
The sign follows the SUS convention that positive PIT = mirror points down, positive YAW = counter clockwise viewed from the top.
As was observed before, WFSA is a good YAW hard mode sensor, WFSB is a good PIT hard mode sensor.
Since neither of the WFSs is good soft mode sensor, I made these:
DOF2P = -4.19 WFSAP + WFSBP
DOF2Y = WFSAY + 1.1 WFSBY
After making these, all four DOF loops were closed and it worked, with one caveat: It seems like DOF2P wants a large offset in order for the green transmission to be maximized. I tried +2500 cts offset and it was good (transmission touches 850 cts). Without this, the transmission stays between 650 and 750.
Unfortunately I cannot give DOF2P an offset before the master switch, and I put this offset in the feedback filter itself. When IFO unlocks the integrator will keep integrating, destroying the IFO alignment.
So I disabled DOF2P input AND offset, and left other three DOFs, for tonight.
It's still slow.
Daniel, Alexa, Keita, Arnaud, Sheila
Tonight we measured the same noise spectrum of the normalized arm PDH spectrum that we measured tuesday night, with the WFS on at low gain. The noise was not improved, it even seemed worse.
We then tried feeding the normalized PDH back to the CM board though input 2. With a gain of 18 in -500 in REFL_DC_BIAS and 0 in the CM board Input 2 and positive polarity.
We saw that the error signal was supressed. The transfer function we measured for this loop didn't make sense, we measured a ugf of 500Hz and 180 degrees phase. We weren't able to calibrate the nosie spectrum we then measured, not trusting the measurement of the loop gain.
The transmitted power fluctations were reduced by adding the feedback from the IR, but still fluctuated from 1 to 0.5, at around half a hertz.
The IR was locked to the cavity starting at around 6:30 UTC, most of the time until the ITMX ISI tripped at around 7:30 UTC. I reset the target offsets before bringing it back up, after which Alexa realinged the cavity by moving ITMX 2.5urad in pitch. Trying to bring it up I tripped it twice more trying to reengage the Tcrappys (even though everything was green, it seems we need to wait until the number are around a few hundred.) Arnaud brought it back by switching to Tcrappy one DOF at a time on stage 2, and sensor correction is now left off.
Turns out we forgot to take into account that we turn the boost gain on in the path from the PLL. This would have made the two paths flat in respect to each other from 1.6Hz to 80Hz, rather than the desired 1/f.
Yesterday night and this morning some diagonalization measurements were taken with pum drive on etmx and itmx. The low coherence for the pitch drive described on the previous alog was due to the optic not centered enough on the oplev, so both ETMX p2p and y2y were remeasured. Those measurements can actually be really fast (15/20min each).
ITMX measurement has some calibration factor of 1.56 for Yaw and 1.83 in Pitch. T1100378 was the reference for calibrating the drive from cts to N.
Attached are the plots comparing the measurement and the model (wirerehang for itmx, fiber for etmx). Note that there is a sign error in ETMX Yaw, so we should double check if that comes from the Oplev sign convention.
ITMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Results/quad_{p2p/y2y}.mat
ETMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL2/Results/quad_{p2p/y2y.mat
ITMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Data/2014-03-06_H1SUSITMX_{P2PY/Y2PY}_WhiteNoise.xml
ETMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Data/2014-03-04_H1SUSETMX_{P2PY/Y2PY}_WhiteNoise.xml
ITMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ITMX/SAGL2/Scripts/itmx_L2_diag.m
ETMX : /ligo/svncommon/SusSVN/sus/trunk/QUAD/H1/ETMX/SAGL2/Scripts/etmx_L2_diag.m
PUM drivealign P2P and Y2Y filters were installed.
In each of the attached, foton screen shot to the left shows the actual filter installed, matlab plot to the right shows the P2P or Y2Y measurement, fit, model, and the expected TF from PUM to the test mass after the new filter takes effect.
As you see I made the filters such that ITM and ETM looks as if they share the same low Q (Q=3) resonance at 0.51 Hz for PIT and 0.6Hz for YAW. There's also a roll of at 30Hz, which is not that aggressive. If necessary you can easily add more.
I ignored the DC calibration of the measurement. I'll handle them in the gain.
The filters relevant are FM1 of H1:SUS-ETMX_L2_DRIVEALIGN_P2P, Y2Y and corresponding ITMX filters.
Scripts used for the fit and inversion as well as the filter definition files generated by the scripts are:
~controls/keita.kawabe/fit/[EI]XPUM_[PY]2[PY]fit.m
~controls/keita.kawabe/fit/[EI]XPUM_[PY]2[PY]inversion_soscoeffs.txt
[Yuta Keita Arnaud]
ETMX ITMY ITMX top mass P2P drivealign filters installed
On friday, filters were designed the same way as Keita, in order to get a single pendulum transfer function from the top mass drive to the test mass displacement in pitch. The filters were installed in the top drivealign matrix in FM1 of the P2P bank filter. ITMX filter is a copy paste from ITMY, assuming they have the same P2P transfer function (both are wires). Attached are the plots showing the design of the filters and the foton version. The transfer function after filtering has its cut off frequency at 0.45Hz for ETMX and 0.55Hz for ITMY/ITMX.
ETMX Length to pitch decoupling was also designed and installed in L2P drivealign matrix. Plots of design pending.
And also IM3.