Final alignment numbers for last weeks SR2 alignment (now that we have good TFs):
Sheila, Arnaud, Stefan Based on the model (both the sophisticated official, as well as a simple 4-mass, length only one) the transfer function ratio (TOP_L-to-TST_L)/(UIM_L-to-TST_L) is given by a simple pendulum resonance, namely the resonance of the top mass, assuming ass other masses are locked down (divided by the spring constant strength between TOP and UIM). Since we had a very good measurement of the TOP_L-to-TST_L transfer function below 1Hz, we trusted those poles and zeros, and simply updated the UIM inverse plant filter with the corresponding <1Hz poles and zeros of the TOP inverse plant. Next I copied the top mass blendLP to the UIM LOCK bank, and added a gain of -1. this allowed my to drive the nominally same signal through TOP and UIM, with opposite sign. Then I fine-tweaked the relative gain (and additional factor of 1.255 for the UIM drive), getting a drive signal cancellation of -39dB at 0.31Hz. THe same gain setting still gave me a cancellation of -26dB at 0.91Hz. I now trust the TOP/UIM blended actuator - onwards to the ESD! Attached are snap shots for the LOCK filter banks. (The UIM - the one with the gain of 1.255 - has the wrong title - the MEDM needs to be updated.)
Sheila noticed that some of the labels for the ISC lock filters linked to SUS_CUST_QUAD_OVERVIEW for ETMy/ETMx were incorrect. Specifically, L1 and L2 were both labelled as M0. We replaced with the correct title and committed to svn.
We also verified these errors were not present for the HSTS/HLTS/BS medms.
After the alignment of SR2 on friday, a set of transfer functions of the top mass has been ran over the week end. Measurements are agreeing with the model.
Only things to note : First pitch mode is slightly shifted down (from 1.00Hz to 0.96Hz), and second roll mode is slightly shifted up (from 2.19Hz to 2.27Hz).
The osem open light values and serial numbers for the osems of this suspension can be found under the excel spreadsheet E1200343.
Here is the list of commissioning task for the next 7-14 days:
Green team (XY-arm):
Blue team (Y-arm):
Blue team (X-arm):
Red team:
SEI/SUS team:
J. Kissel We're most of the way through turning H1 SUS ETMX into a super actuator of TOP, UIM, and TST actuation stages, so I've installed an over all controller into FM1 of the LSC_DARM filter bank in the H1LSC.txt filter file, called simply "ALSDIFF" (this replaced a "p0.01" integrator). The filter design string is zpk([5;5],[0.5;80;80],1,"n") i.e. two real zeros at 5 [Hz], balanced with two poles at 80 [Hz] to provide a phase boost around 15-20 [Hz], and a boost pole at 0.5 [Hz], which was the controller used for a design with a 15 [Hz] UGF (see plots from LHO aLOG 11676). Noteably, the DC gain of the filter is unity. We haven't yet installed any of the overall gains, so those will need to be installed and tuned before we *actually* get a UGF of 15 [Hz]. Remember, the design uses both ETMs, and over-estimates the TST drive strength by a factor of 4. But, as long as we install the *measured* gain ratios (again, see LHO aLOG 11676), and are consistent with our overall super-actuator gain, we should be alright. At this point, our plan is to have what is sent to the suspensions be in units of [um] of desired DARM correction, and we'll have the overall gain of the super actuator be [ct_{TST} / um_{DARMCTRL}], or DAC counts of test mass motion per micron. From LHO aLOG 11676, TST: 1.760e-13 [m / ct_{TST}] = 1.76e-7 [um / ct_{TST}] ==> 5.68e+6 [ct_{TST} / um]
model restarts logged for Sun 04/May/2014
2014_05_04 17:02 h1fw0
unexpected restart of h1fw0
LVEA going to laser Hazard as soon as possible
SR2 alignment mostly done...some TF's from Arnaud ongoing
HAM Arm install @HAM5, may involve cranining and forking (Bubba)
TCS - alignment on TCSX, req laser hazard...prep for in vacuum alignment Tuesday
Integration---working on ESD drivers
Richard - inspection of EY ESD
Stefan, Arnaud, Jeff, Alexa, Sheila
Yesterday we tried to test our plant inversion for each stage of the ETMX quad. The good news is that we get the same results if we make out measurement with optical levers on or off, so we can use the same plant inversion in either case. We had thought there was a difference based on the earlier measurements, but that was mostly due to one point with lower coherence.
The first screenshot shows a measurement we made with the slow feedback going to the top mass, made by injecting into the top mass and measuring the ALS REFL control signal. Stefan calibrated this so that it would be flat if the plant inversion is perfect.
The blue trace has is the original plant inversion, the green trace is just a better resolution measurement of the resonance similar to the blue.
Stefan installed a patch filter to cancel this resonance (second screenshot attached), and we repeated the measurement (show by the red trace). Now it is flat.
We then switched the slow feedback to the UIMand repeated the same measurement, using the plant inversion L2L, the gain uim/tst, and the low pass blend but no high pass blend. We again found a resonance at 0.44 Hz, but need a better resolution measurement to correct it.
2014_05_03 19:36 h1fw0
this is an unexpected restart of h1fw0. We will schedule a reboot of its solaris QFS writer 06may
I left a measurement running on the suspension overnight, but that should have been finished before this trip, so I'm not sure what caused this.
The measurement was done by 10am this morning; it has been saved.
No restarts reported.
Gradual pressure increase seen by PT246B over past few weeks represents an unpumped accumulation -> I will turn this off on Monday as the CC gauge pump effect is decaying and is now insufficient to match the outgassing-> Configuration will be restored to normal after the adjacent RGA volume (temporary) is finished baking out
The beam diverter moves TMS pitch by a bit more than 9urad. This seems like a potential problem if we are planning to use any of the sensors on TMS when we flip it to go to science mode.
In the attached screenshot, I opened the beam diverter and misalinged the arm cavity, closed the beam div again, and the cavity was aligned again. I opened it again, and moved TMS +9.1 urad in pitch to realign the cavity.
J. Kissel, K. Izumi, S. Ballmer Inspired by the presentation Suresh gave today on the ISC / Integration Call, (see T1400311, which includes data originally taken from LLO aLOG 11518), I looked at the spot positions on the IMC WFS using a 1 hour trend over the past 30 days (Suresh used 20 days). See first attachment. While LLO's spot position oscillates roughly +/- 0.5 [fractional beam diameters] (though it's tough to quantify without y-axis labels or gridlines), LHO's WFS DC signals fluctuate about an order-of-magnitude less over these time-scales. Though we haven't cross-referenced in detail, we believe the discrete jumps seen correspond to the MCWFS alignment mystery starting and te subsequent recovery (see LHO aLOG 11481). I also attach the amplitude spectra of MC2 Trans, calibrated* into [W/rtHz] at of intra-cavity power noise, as Suresh has done on pg 7 of T1400311. One can see that the (equivalent) transmitted power noise floor is higher at LHO, (which we guess it QPD electronics noise), so at this point we're not able to resolve noise features at the same level, so it's unclear if we have similar problems with WFS centering creating intensity noise. * Calibration of H1:IMC-MC2_TRANS_SUM_IN1_DQ into intra-cavity power: The SUM is already calibrated into [uW] at the MC2 TRANS QPD as per LHO aLOG 9716. From T1300386 and E1300756, the two non-suspended optics between the QPD and MC2 are AROM RHS (a high-reflector), and ROM RH13 (a R=90% beam splitter). From the galaxy optics page and E1200463, our MC2 is IMCC02, with a transmission of 5.1 ppm. So, the extinction ratio between the HR surface of MC2 and MC2 trans is 5.1e-6 [MC2 AR / MC2 HR] * 0.1 [ROM RH13 AR / MC2 AR] = 5.1e-7 [ROM RH13 AR / MC2 HR] (where I've ignored the loss from MC2 AR surface, since it's small w.r.t. the 10% loss from the ROM RH13). Therefore 1 [uW] at MC2 TRANS QPD is (1 / 5.1e-7) = 1.96e6 [uW] = 1.96 [W] of intra-cavity power. Currently, the calibrated MC2 TRANS reports 433 [uW] at DC, i.e. 848 [W] of intra-cavity power. This is roughly consistent with the 5.7 [W] measured at the input at PSL periscope * Finesse/pi = 936 [W] of intra-cavity power (with IMC Finesse as 516).
Days activities
To solve build problems with the 'nds' DAQ executable, I have installed the ldas-tools-1.19.32 build (which includes framecpp) on /opt/rtapps on the LHO DAQ test stand. I have also made it the default framecpp, replacing framecpp-1.19.24p1. This has long been the version at L1 and LLO test stand. After this change and using 'source /opt/cdscfg/rtsetup.sh', I was able to build the 'nds' executable. I also fixed the install on the /opt/cdscfg configuration scripts (specifically rtsetup.sh) to match current practice. I have also created H1, L1 versions (/opt/cdscfg-h1/rtsetup.sh, /opt/cdscfg-l1/rtsetup.sh) to simplify building L1, H1 models on this test stand. The new rtsetup.sh also supports the use of 'private' userapps, rcg checkouts (PRIVATE_USERAPPS, PRIVATE_RCG) to simplify automated testing with Jenkins. Please see Jenkins scripts on the LLO DAQ test stand for examples.
Have noticed odd behavior with the HAM4 Dust Monitor (listed as #1). Have gotten MAJOR alarms for 0.3um particles (several hundred up to a few thousand counts!). Conversely, 0.5um particles has been virtually 0 for days. Mentioned high counts to Betsy before she went out to HAM4 today, and she mentioned that she only saw small counts out there on the floor. So there seems to be a discrepency some where.
Attached is a trend of the last 5-days. Will send an email to Jeff B.
This dust monitor looks to have fishy readings. Why are there lots of particle counts of 0.3um size but 0 counts on the 0.5um size? When I looked at the physical monitor a few times throughout the morning Friday, 0.3um always was reading ~10-30 counts, while 0.5um was reading 0. There must be some calibration diff between what reads on the actual monitor screen and what reads out in the control room trend data. Never-the-less, it's hard to think of how we could be dirty at 0.3 but not at 0.5.