Displaying reports 66761-66780 of 77184.Go to page Start 3335 3336 3337 3338 3339 3340 3341 3342 3343 End
Reports until 11:33, Thursday 13 March 2014
H1 CDS (DAQ)
david.barker@LIGO.ORG - posted 11:33, Thursday 13 March 2014 (10739)
CDS model and DAQ restart report, Wed 12th March 2014

model restarts logged for Wed 12/Mar/2014
2014_03_12 16:09 h1ioppemmy
2014_03_12 16:28 h1ioppemmy
2014_03_12 16:28 h1pemmy
2014_03_12 21:02 h1fw1

All expected except for the h1fw1 restart.

H1 SUS
arnaud.pele@LIGO.ORG - posted 11:04, Thursday 13 March 2014 (10734)
ETMY transfer functions

Yesterday, we found that the reaction chain of ETMY quad was rubbing, so Betsy and Travis made some adjustements and a round of TF was ran overnight. The results are now clean, meaning the suspension is free of rubbing for both chains. This will be our official phase 3a set of transfer functions.

The first attachement shows the transfer functions for the 6 DOF of the main chain and the second attachement for the reaction chain. TF have their peaks matching very well with the model, except T DOF of the reaction that has an extra resonance at 0.86Hz which is a roll mode. (and as usual the reaction chain pitch which differs because of added stiffnes from cables which couples into the L DOF).

I added to the plots the phase as well as the ratio between model and measurement.

Non-image files attached to this report
H1 SEI (INS, ISC)
hugh.radkins@LIGO.ORG - posted 10:56, Thursday 13 March 2014 (10738)
WBSC10 ETMY HEPI Alignment Changes w/ Excitations

I attach here three plots showing the Local and Cartesian positions for the ETMY HEPI for the last 72 hours.  I conclude that, at least in this instance, the high frequency excitations (100-1000Hz) which ran this morning, destresses the platform and exhibits strains of significant magnitude.

The first plot is the four vertical Inductive Position Sensors showing the zeroing of the IPS after Alignment approval Tuesday afternoon. When Mitchell pulls ACB elements Wednesday Morning, there is vertical shift of 100s of nm; as we expected, not too much to worry about.  Toward the end of the plot, the start of TFs beginning at 500 to 1000Hz and then continuing with 100to 500Hz as well shows small steps.

The second plot however shows the four horizontal IPS and much larger steps in the IPS readouts at the start of the TFs.  The third plot are the trends of the Cartesian channels.  The Wednesday AM Matrix changes I made are very insignificant but not so the horizontal shifts from the TFs.  The 0.3mm translations of X & Y are ignorable but the Rz of -15urads may not be. With Jason's alignment of ETMY indicating a 20urad CCW error, and if we've all got our signs correct, the -15urads should actually put us closer to zero error.

Notice that the H2 IPS had the largest shift.  I attempt to push it back and was successful with a 1000ct local offset but it went back as soon as I removed the offset.  In the last plot attached you can see all the position senors responding to the stopping of the excitations this morning and then to  the offset and all pretty much returning to their previous values when the offset is removed.

So I would suggest that a destressing exercize of the HEPI may be a valuable step in the alignment process and of course an explicit zeroing (or at least a logging) of the IPS value are in order right after alignment, something we haven't always done.  This also stresses the importance of getting the posirtion loops turned on.

Images attached to this report
H1 AOS (INS, SEI, SUS)
jason.oberling@LIGO.ORG - posted 10:13, Thursday 13 March 2014 (10737)
WBSC10 ETMy Final Alignment Numbers
IAS: D. Cook, J. Oberling
SUS: B. Weaver, T. Sadecki
SEI: H. Radkins, J. Warner, M. Robinson, G. Grabeel
 
Over the last week we have been aligning the ETMy in WBSC10.  Now that the last round of SUS transfer functions have cleared the quad suspension of rubbing issues, I'm posting the final alignment numbers.
 
ETMy

ERMy (set parallel with respect to the ETMy AR surface.  Error numbers are reported from this desired parallelism)

ACB

All IAS equipment has been removed from the spool area and the spool is being installed this morning.

H1 General
corey.gray@LIGO.ORG - posted 09:24, Thursday 13 March 2014 - last comment - 09:48, Thursday 13 March 2014(10735)
Spool Work At EY

Cranework is beginning at EY for Spool Work (involves moving IAS table out of way, inserting spool, etc.).  Bubba noted the Dust Monitor was inoperative & Jeff B. will be heading out there to get their Dust Monitor back online.

Comments related to this report
betsy.weaver@LIGO.ORG - 09:48, Thursday 13 March 2014 (10736)

It was working yesterday and the day before because it beeped at us and showed reasonable counts.

H1 SEI
kiwamu.izumi@LIGO.ORG - posted 06:24, Thursday 13 March 2014 (10732)
BS ISI untripped

We found that the BS ISI had been tripped. We untripped it with stage 1 isolated at level with the Tcrappy blend filter.

H1 ISC
robert.schofield@LIGO.ORG - posted 20:25, Wednesday 12 March 2014 (10730)
70 Hz peak

I tap tested ISCT1 while the arm was locked. The broad peak at about 71 Hz was associated with the red/green periscope, but the sharp peak at 67.9 Hz did not appear to originate on ISCT1. The tall supports used to dress some cables had similar Qs but slightly different frequencies. The tight ones should probably be unscrewed slightly to damp the flag pole resonance and lower their Qs, but they were not the source.

H1 SEI
sebastien.biscans@LIGO.ORG - posted 18:26, Wednesday 12 March 2014 (10728)
SEI status

I am summarizing here recent progress on BSC-ISI units

 

Blend Filters for the BSC-ISI

We have standardized the blend configurations. All the BSC-ISIs are equipped with 3 different blends filters: 'Start', 'T750mHz', 'Tcrappy'

 

BSC-ISI Controllers

All the BSC-ISIs are equipped with a working lvl3 controller for all the DOFs, Stage 1 and Stage 2

BSC-ISI config

The most robust configuration providing good performance on all BSCs is the following:

- control lvl3 on ST1 & ST2

- Tcrappy blend filters on ST1 & ST2

 

To properly turn this config on, see here.

 

Sensor correction Stage 1 to Stage 2 has been installed on all the BSCs but ITMY.

Tilt decoupling ST1 has been installed on all the units

Tilt decoupling ST2 has been installed on BS and ITMY. I started to do X tilt decoupling on ITMX but didn't have the time to do Y.

 

Matrices

After the reboot of the system on February 25th, old input and output matrices have been restored on BS and ETMX. This is not a big deal, we just have to find a quiet time to restore the new ones. This process might disturn the currnt alignment though.

 

Performance

Find attached BS performance plot. The behavior of the beamsplitter is very representative of the behavior on the other chambers. I took BS as an example because it was available at the time, but I expect to have the same kind of results on all the chambers.

Thre configuration are tested here:

- the robust Tcrappy on ST1 and ST2

- Tcrappy on ST1, Start on ST2 with sensor correction #1 (filter 'BandPass2')

- Tcrappy on ST1, Start on ST2 with sensor correction #2 (filter 'BandPass4') > more aggressive sens corr

 

It is interesting to notice the different compromise between Tcrappy and sensor correction. Also, we want to be careful with sensor correction and not reinjecting very low frequency noise.

This shows that there is still some room to tweek our blends/feedforward.

 

I haven't had the time to try your blend Rich (next time!), and the windy configuration.

Images attached to this report
H1 AOS (COC, ISC)
david.ottaway@LIGO.ORG - posted 18:21, Wednesday 12 March 2014 - last comment - 14:33, Tuesday 18 March 2014(10729)
Preliminary Measurement of PRC Gouy Phase
Dave O and Stefan B

We measured the round trip gouy phase of the PRC using the same phase-locked sub-carrier that we used to measure the PRC length.

We scanned the sub-carrier offset frequency over a full spectral range of the PRC (2.6 MHz) from 68.4 MHz - 72.4 MHz. We then monitored the amplitude and phase of the beat- note as measured by Refl-Air-B diode. Two plots are shown. 

The first shows the full sweep. Three tracs are shown. The blue trace is the transfer function for the full beat-note signal scanned over a full PRC FSR. The other two show the traces, when half the photo-diode is blocked and the sub-carrier is locked on either side of the main carrier. Unfortunately the interferometer lost lock half-way through both of these scans. The broader bumps show the resonance of the TEM01 modes.

The second plot is the same trace zoomed in around this area. From this plot we can determnine that TEM01 modes resonate at 375kHz +/- 10 kHz off the main resonance and hence the round trip guoy phase for the PRC is 52 +/- 3 degrees.
Non-image files attached to this report
Comments related to this report
paul.fulda@LIGO.ORG - 14:33, Tuesday 18 March 2014 (10834)

I did some comparison of these results with some predictions from a Finesse model of the PRMI, and also compared with the results of the beam size measurements reported here

I attach plots with the predicted PRX Gouy phases over ITMX substrate lens power and PR2-PR3 distance offset.

The left-most solid diagonal line is the line that comes from the beam size measurements, and the right-most solid diagonal line is the one coming from the Gouy phase measurements (with two dashed lines representing the error bars there). The blue line is the expected ITMX substrate lens power (f=230km, 1/f~4.35uD).

It would help to know if the PD was covered left-right or top-bottom to know if you measured Gouy phase in x or y direction, but for now I just considered both possibilities.

One possible explanation for the larger measured Gouy phase than expected from the beam size measurements is if PRX and PRY were not ideally matched when the measurement was made. If ITMY was not heated enough to match ITMX, the PRC has a kind of "average" Gouy phase that is larger than the PRX Gouy phase on its own.

The contours of equal Gouy phase over the two varied parameters is the same as the contours of equal beam size, so there is still no chance to distinguish between ITMX substrate lens and PR2-PR3 offset (or PR3 Rc).

Non-image files attached to this comment
H1 SEI
hugh.radkins@LIGO.ORG - posted 17:16, Wednesday 12 March 2014 (10726)
Delayed TFs waiting til 0100pdt on ETMy HEPI

Delaying until 1am.  Since SUS will not be done until midnightish and ISI is locked.  These matlabs are running on opsws0.

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 17:07, Wednesday 12 March 2014 - last comment - 06:54, Thursday 13 March 2014(10725)
Red locking in this morning: sensing matrix measured in the sideband locked PRMI

Stefan, Yuta, Kiwamu

We have measured the length sensing matrix in the sideband locked PRMI. The data is now under analysis and will be posted later.

Also since we now know that the in-vac REFL is functional (see alog 10661), we switched the PRMI sensors from the in-air one to the in-vac one. This is a permanent change and in fact, it is already reflected in the guardian.

 

Preparations (adjustment of PD gains and demod phases):

After we locked the PRMI with the sidebands resonant, we re-adjusted the demod phases such that the PRCL signal is maximized in all the in-phase paths. This was done by inserting a new notch at 100 Hz both in MICH and PRCL filters and exciting PRM with an amplitude of 30000 cnts at the output side of the LSC. We used dtt to check the demod phases. The new settings are now:

We didn't phase the POP detectors this time as we were focusing on the REFL detectors. Also, we changed the PD gain in the digital system to make all of them identical to REFLAIR_45. This was meant to make the calibration easier. The new gain settings are now:

At this point, we could see all the I-phase signals beautifully overlaid on each other in the spectrum.

The measurement:

We then moved on to the measurement of the LSC sensing matrix. We continued shaking PRM with the same amplitude of 30000 cnts. We left the notches in at 100Hz to avoid surpression from the LSC control loops. Since we wanted to quickly get a result, we decided to use dtt instead of the online lockins. Monitoring the DAC of BS, PRM and PR2 suspensions we didn't observe a saturation during the measurement. Good. All the 1f detectors had a whitening gain of 0 dB while REFL_RF27 and REFL_RF135 had a whitening gain of 27 dB and 21 dB respectively. We set the bandwidth of the FFT to be 0.1 Hz and averaged it by 10 times. Note that the PRCL loops should have a UGF of about 35-ish Hz and the MICH loop should have a UGF of about 10-ish Hz. So the excitation is above the UGFs.

As for the MICH sensing matrix measurement, we tried three different excitations -- (1) excitation on the diagonalized combination of PRM and BS at 100 Hz, (2) excitation on only BS at 100 Hz, and (3) excitation on ITMs at 18 Hz. The third configuration was not really successful in a sense that we didn't see a big excitation. Also we didn't spend a long time to study the optimum excitation on ITMs this time.

In the first and second excitation configurations, we injected an excitation with an amplitude of 300 cnts above of which the BS saturated at its DAC. Since the excitation was puny, we narrowed dtt's bandwidth down to 0.01 Hz this made the coherence somewhat better.

 

A permanent change -- in-vac locking:

We did nothing special to switch the sensor from the in-air to in-vac. We simply set the LSC gains right. Currently REFL_A_RF45_I is for PRCL and REFL_A_RF45_Q. for MICH. We then confirmed that the in-vac detector grabbed the PRMI fringe without a problem. Also we noticed that the in-vac Q-signal contained less noise by a factor of 5-ish (actually I forgot the exact number, sorry) above 30 Hz and therefore the BS DAC should be happier now.

Additionally, we confirmed that we could still transition to the 3f diodes smoothly by the guardian.

Comments related to this report
yuta.michimura@LIGO.ORG - 17:25, Wednesday 12 March 2014 (10727)

PRMI sensing matrix elements measured are as follows;

===PRM actuation===
== Raw data
REFL_A_RF9_I      1.57e-03 +/- 2.27e-05 counts/counts (err: 1.4 %)
REFL_A_RF9_Q      -2.21e-06 +/- 4.34e-07 counts/counts (err: 19.7 %)
REFL_A_RF45_I      1.58e-03 +/- 2.14e-05 counts/counts (err: 1.3 %)
REFL_A_RF45_Q      7.43e-06 +/- 1.98e-06 counts/counts (err: 26.7 %)
REFLAIR_A_RF9_I      1.60e-03 +/- 2.22e-05 counts/counts (err: 1.4 %)
REFLAIR_A_RF9_Q      2.95e-06 +/- 4.30e-07 counts/counts (err: 14.6 %)
REFLAIR_A_RF45_I      1.60e-03 +/- 2.09e-05 counts/counts (err: 1.3 %)
REFLAIR_A_RF45_Q      1.30e-05 +/- 1.80e-06 counts/counts (err: 13.9 %)
REFLAIR_B_RF27_I      1.58e-03 +/- 2.22e-05 counts/counts (err: 1.4 %)
REFLAIR_B_RF27_Q      -4.41e-06 +/- 5.33e-07 counts/counts (err: 12.1 %)
REFLAIR_B_RF135_I      1.02e-03 +/- 2.57e-05 counts/counts (err: 2.5 %)
REFLAIR_B_RF135_Q      -6.73e-06 +/- 1.05e-05 counts/counts (err: 155.7 %)
== Calibrated data (calibration error is not included in the error shown below)
REFL_A_RF9_I      1.51e+06 +/- 2.18e+04 W/m (err: 1.4 %)
REFL_A_RF9_Q      -2.12e+03 +/- 4.17e+02 W/m (err: 19.7 %)
REFL_A_RF45_I      5.44e+05 +/- 7.34e+03 W/m (err: 1.3 %)
REFL_A_RF45_Q      2.55e+03 +/- 6.81e+02 W/m (err: 26.7 %)
REFLAIR_A_RF9_I      1.41e+06 +/- 1.97e+04 W/m (err: 1.4 %)
REFLAIR_A_RF9_Q      2.61e+03 +/- 3.81e+02 W/m (err: 14.6 %)
REFLAIR_A_RF45_I      4.75e+05 +/- 6.22e+03 W/m (err: 1.3 %)
REFLAIR_A_RF45_Q      3.86e+03 +/- 5.37e+02 W/m (err: 13.9 %)
REFLAIR_B_RF27_I      7.72e+03 +/- 1.09e+02 W/m (err: 1.4 %)
REFLAIR_B_RF27_Q      -2.15e+01 +/- 2.60e+00 W/m (err: 12.1 %)
REFLAIR_B_RF135_I      1.78e+02 +/- 4.47e+00 W/m (err: 2.5 %)
REFLAIR_B_RF135_Q      -1.17e+00 +/- 1.82e+00 W/m (err: 155.7 %)


===BS-0.5*PRM actuation===
== Raw data
REFL_A_RF9_I      4.69e-05 +/- 9.95e-07 counts/counts (err: 2.1 %)
REFL_A_RF9_Q      -1.62e-05 +/- 2.12e-07 counts/counts (err: 1.3 %)
REFL_A_RF45_I      4.68e-05 +/- 1.08e-06 counts/counts (err: 2.3 %)
REFL_A_RF45_Q      -8.04e-05 +/- 5.47e-07 counts/counts (err: 0.7 %)
REFLAIR_A_RF9_I      4.73e-05 +/- 1.40e-06 counts/counts (err: 3.0 %)
REFLAIR_A_RF9_Q      -1.60e-05 +/- 6.25e-07 counts/counts (err: 3.9 %)
REFLAIR_A_RF45_I      4.66e-05 +/- 1.57e-06 counts/counts (err: 3.4 %)
REFLAIR_A_RF45_Q      -8.04e-05 +/- 9.60e-07 counts/counts (err: 1.2 %)
REFLAIR_B_RF27_I      3.10e-05 +/- 6.23e-06 counts/counts (err: 20.1 %)
REFLAIR_B_RF27_Q      -3.30e-05 +/- 9.95e-06 counts/counts (err: 30.2 %)
REFLAIR_B_RF135_I      -3.56e-04 +/- 4.16e-04 counts/counts (err: 116.6 %)
REFLAIR_B_RF135_Q      1.16e-03 +/- 2.22e-04 counts/counts (err: 19.1 %)
== Calibrated data (calibration error is not included in the error shown below)
REFL_A_RF9_I      4.87e+04 +/- 1.03e+03 W/m (err: 2.1 %)
REFL_A_RF9_Q      -1.68e+04 +/- 2.20e+02 W/m (err: 1.3 %)
REFL_A_RF45_I      1.74e+04 +/- 4.02e+02 W/m (err: 2.3 %)
REFL_A_RF45_Q      -2.99e+04 +/- 2.03e+02 W/m (err: 0.7 %)
REFLAIR_A_RF9_I      4.53e+04 +/- 1.34e+03 W/m (err: 3.0 %)
REFLAIR_A_RF9_Q      -1.53e+04 +/- 5.98e+02 W/m (err: 3.9 %)
REFLAIR_A_RF45_I      1.50e+04 +/- 5.05e+02 W/m (err: 3.4 %)
REFLAIR_A_RF45_Q      -2.59e+04 +/- 3.09e+02 W/m (err: 1.2 %)
REFLAIR_B_RF27_I      1.64e+02 +/- 3.29e+01 W/m (err: 20.1 %)
REFLAIR_B_RF27_Q      -1.74e+02 +/- 5.25e+01 W/m (err: 30.2 %)
REFLAIR_B_RF135_I      -6.69e+01 +/- 7.80e+01 W/m (err: 116.6 %)
REFLAIR_B_RF135_Q      2.18e+02 +/- 4.16e+01 W/m (err: 19.1 %)


===BS only actuation===
== Raw data
REFL_A_RF9_I      8.01e-04 +/- 5.85e-06 counts/counts (err: 0.7 %)
REFL_A_RF9_Q      -1.54e-05 +/- 2.82e-07 counts/counts (err: 1.8 %)
REFL_A_RF45_I      8.05e-04 +/- 5.85e-06 counts/counts (err: 0.7 %)
REFL_A_RF45_Q      -6.80e-05 +/- 1.06e-06 counts/counts (err: 1.6 %)
REFLAIR_A_RF9_I      8.12e-04 +/- 6.26e-06 counts/counts (err: 0.8 %)
REFLAIR_A_RF9_Q      -1.21e-05 +/- 5.48e-07 counts/counts (err: 4.5 %)
REFLAIR_A_RF45_I      8.13e-04 +/- 6.26e-06 counts/counts (err: 0.8 %)
REFLAIR_A_RF45_Q      -6.52e-05 +/- 1.24e-06 counts/counts (err: 1.9 %)
REFLAIR_B_RF27_I      8.09e-04 +/- 1.04e-05 counts/counts (err: 1.3 %)
REFLAIR_B_RF27_Q      -1.63e-05 +/- 6.16e-06 counts/counts (err: 37.7 %)
REFLAIR_B_RF135_I      4.21e-04 +/- 2.67e-04 counts/counts (err: 63.3 %)
REFLAIR_B_RF135_Q      -5.33e-04 +/- 2.51e-04 counts/counts (err: 47.2 %)
== Calibrated data (calibration error is not included in the error shown below)
REFL_A_RF9_I      1.18e+06 +/- 8.60e+03 W/m (err: 0.7 %)
REFL_A_RF9_Q      -2.26e+04 +/- 4.14e+02 W/m (err: 1.8 %)
REFL_A_RF45_I      4.23e+05 +/- 3.08e+03 W/m (err: 0.7 %)
REFL_A_RF45_Q      -3.57e+04 +/- 5.54e+02 W/m (err: 1.6 %)
REFLAIR_A_RF9_I      1.10e+06 +/- 8.48e+03 W/m (err: 0.8 %)
REFLAIR_A_RF9_Q      -1.64e+04 +/- 7.42e+02 W/m (err: 4.5 %)
REFLAIR_A_RF45_I      3.70e+05 +/- 2.85e+03 W/m (err: 0.8 %)
REFLAIR_A_RF45_Q      -2.96e+04 +/- 5.64e+02 W/m (err: 1.9 %)
REFLAIR_B_RF27_I      6.04e+03 +/- 7.79e+01 W/m (err: 1.3 %)
REFLAIR_B_RF27_Q      -1.22e+02 +/- 4.60e+01 W/m (err: 37.7 %)
REFLAIR_B_RF135_I      1.12e+02 +/- 7.09e+01 W/m (err: 63.3 %)
REFLAIR_B_RF135_Q      -1.41e+02 +/- 6.68e+01 W/m (err: 47.2 %)


Errors shown are statistical errors for this measurement (using coherence, number of averaging and the formula in alog #10506) and calibration errors are not included. The sensor calibration and the actuator calibration has roughly ~10% error (see for example, alog #9630 and #10213).
For the sensor calibration (counts/W),numbers in H1PRMI awiki was used. For the actuator calbiration (m/counts), numbers in alog #10724 (see comments) was used. "m" in these units are either cavity one-way length change, or MIchelson one-way length difference between X and Y. However, "BS only" ones are calibrated in BS motion (since BS changes MICH by sqrt(2) and PRCL by 1/sqrt(2) ). 'W" in these units are the amplitude of modulated laser power (before demodulation).

PRM to I signals in counts/counts look alike since we adjusted the PD filter gains to be that way. PRM to Q signals are significantly smaller than I as a result of demodulation phase adjustment.
BS-0.5*PRM actuation is supposed to be pure MICH actuation, but since it is not true perfectly, both I signals and Q signals show up.


[Data and script]
Raw data and the script to calbirate data lives in /opt/rtcds/userapps/release/lsc/h1/scripts/sensmat.
./sensemat_20140312_PRCL_part3.xml     (dtt of PRM actuation)
./sensemat_20140312_MICH_100Hz_part1.xml     (dtt of BS-0.5*PRM actuation)
./sensemat_20140312_MICH_100Hz_part2.xml     (dtt of BS only actuation)
./sensmat_20140312_PRCL.txt    (magnitude, phase, and coherence data for each PD extracted manually from dtt)
./sensmat_20140312_MICH.txt    (magnitude, phase, and coherence data for each PD extracted manually from dtt)
./calibPRMsensmat.py    (script for calibration, putting signs and errors to the data)

rana.adhikari@LIGO.ORG - 01:44, Thursday 13 March 2014 (10731)SYS

The formula from Bendat is correct for simple cases, but, as you might guess, its not right in the case where you have finite overlap between FFT segments. Otherwise, you could choose a 90% overlap and get much less calculated uncertainty for the same total length of data, than what you get with the DTT default of 50%. (i.e. two overlapping data segments have a finite correlation)

For the usual DTT parameters of 50% overlap + Hann window, the effective number of averages is:

Nave_equiv = 1.89 * (T_total / T_fft)

(cf. Chapter 10 of http://books.google.com/books/about/Noise_and_Vibration_Analysis.html?id=-1DSxrlhL5sC )

yuta.michimura@LIGO.ORG - 06:54, Thursday 13 March 2014 (10733)

I see the point that we have to include the overlap into the formula for error estimation.
But if the overlap is 50%,  (T_total/T_fft) will be (Nave+1)/2. So, Nave_equiv = 1.89 * (T_total / T_fft) = 0.945 * (Nave +1). This means that Nave_equiv will be more than Nave when Nave < 18. This this true?

LHO FMCS (SEI)
mitchell.robinson@LIGO.ORG - posted 16:35, Wednesday 12 March 2014 (10723)
Staging building, 3IFO (unit 2) progress
Mitchell,
CPS racks were put together. Class A probes sorted. CPS sub assemblies started and nearly completed. Probes will be attached to their sub assemblies and staged on the ISI to be attached at a later date.
LHO General (CDS, PEM)
patrick.thomas@LIGO.ORG - posted 16:34, Wednesday 12 March 2014 (10722)
restarted IOC for dust monitors in LVEA
The IOC had apparently stopped running. I telneted into the procServ for it on h0epics and it automatically restarted. I burtrestored it.
H1 SUS
arnaud.pele@LIGO.ORG - posted 15:48, Wednesday 12 March 2014 - last comment - 16:03, Wednesday 12 March 2014(10718)
TMSX TF results

After TMSY work on monday I took some overnight measurements yesterday night to check for rubbing, and compared the results with model and TMSX data.

TF looks suspiciously different in the vertical degrees of freedom (VERT and ROLL) than TMSX and model, which indicates that there is probably still something blocking the table to move freely.

Non-image files attached to this report
Comments related to this report
arnaud.pele@LIGO.ORG - 16:03, Wednesday 12 March 2014 (10720)

Per Keita's request, attached is a comparison between the TMSY last year in April and yesterday night

Non-image files attached to this comment
H1 SUS
betsy.weaver@LIGO.ORG - posted 15:47, Wednesday 12 March 2014 - last comment - 16:35, Wednesday 12 March 2014(10719)
ETMy SUS alignment update

After lunch we went back to EY to find the mechanical grounding in the ETMy reaction chain.  After a while we spotted a top mass MRB block (hanging part) brushing the tablecloth (structure part).  Our pitch alignment earlier in the day caused the top mass to pitch into the structure.  We could not adjust the structure out of the way* so we adjusted pitch to alleviate the brushing.  The reaction chain pitch has a  ~1.47mRad tolerance and we are still within this at ~860uRad.  Quick low-coherence TFs looked promising so we are restarting the night run full suite Matlab TFs.

 

*We could not adjust the table cloth easily since 1) everything is suspended - ISI and HEPI included so it all bounces to the lightest touch, 2) the ACB is now mounted and difficult to maneuver around, and 3) the table cloth serves purpose for both chains simultaneously so adjusting it for one chain somewhat anti-adjusts it for the other chain - too risky at this point.

 

-Betsy, Travis

Comments related to this report
arnaud.pele@LIGO.ORG - 16:35, Wednesday 12 March 2014 (10721)

As a reference, I attached the results from the main and reaction chain transfer functions taken yesterday night, showing how the rubbing due to one of the vertical EQ stops affects the TF (2nd attachement).
 

Non-image files attached to this comment
H1 ISC
yuta.michimura@LIGO.ORG - posted 09:55, Tuesday 11 March 2014 - last comment - 16:54, Wednesday 12 March 2014(10674)
BS and PRM actuation balancing - MICH to PRCL supressed by factor of 4

I re-measured BS and PRM actuation transfer functions in PRY configuration after plant inversion done on Mar 5 (see alog #10559).
It seems like we succeeded in BS and PRM balancing within ~8 % and MICH to PRCL coupling is expected to be supressed by factor of ~4, compared with using only BS as an actuator.
For the sensing matrix measurment, the effect of residual MICH to PRCL coupling gives ~6 % error for MICH to REFL45Q element and ~16000 % error for MICH to REFL45I element.

[Motivation]
Before measuring the PRMI sensing matrix, we wanted to estimate how good output matrix diagonalization is.


[Method]
1. Lock PRY and measure open loop transfer function. Compare it with the model to derive optical gain.

2. Measure actuator transfer function of BS and PRM from ISCINF to REFLAIR_RF45_I_ERR in PRY (using the same template used in alog #10450). Calibrate these TFs into m/counts with the optical gain derived in step 1.

3. Closed loop correct TFs measured in step 2. TFs should look like 1/f^2 at 1-300 Hz (see comments on alog #10450). Since output matrix for MICH in PRMI are set to (BS,PRM)=(1,-0.5), these TFs should be equal (see alog #10559 and table below).

-table of actuation efficiency (optic motion to interferometer length change in m/m)-
      PRY      PRCL      MICH
BS    sqrt(2)  1/sqrt(2) sqrt(2)
PRM   1        1         0


4. Calculate expected actuator TFs for MICH to PRCL coupling using the measured TFs. BS ISCINF to PRC length change will be half as that of PRY. BS-0.5*PRM gives the residual MICH to PRCL coupling.


[Result]
1. OLTF_PRCL_1078572000.png: Openloop transfer function of PRY lock. By comparing with the model, this gives PRY optical gain of 1.8 W/m. So, the calibration factor for REFLAIR_RF45_I_ERR in PRY is 4.7e11 counts/m. Note that this calibration factor includes losses in the PD signal chain (e.g. loss from long cable). Also, note that PRM suspension model was 30 % off from the measurement (see #10482; measurement = 0.77 * SUS model). This correction factor is included in the model to derive the optical gain.

2. BSandPRMact_PRY.png: Measured actuator transfer functions for BS and PRM in PRY. x marks show raw measured TFs and dots show closed loop corrected ones. After closed loop correction, actuator TFs look like they follow 1/f^2. From the fit, BS actuator TF is 1.79e12 Hz^2/f^2 m/counts and PRM actuator TF is 1.93e12 Hz^2/f^2 m/counts for PRY. Considering the error bar from coherence and cavity build up fluctuation during the measurement, this 8% difference between BS and PRM is significant (error bars in TF magnitude are derived using the formula in alog #10506). We have done the balancing with the precision of ~10%, so this difference is reasonable.

3. BSandPRMact_MICH2PRCL.png: Estimated MICH to PRCL coupling from actuator diagonalization. Blue dots show BS ISCINF to PRC length change and red dots show BS and PRM combined actuator to PRC length change. Fitted lines show that MICH to PRCL coupling is expected to be supressed by factor of ~4 by actuator balancing. We can improve this supression ratio a little bit by changing the gain balancing between BS and PRM by 8%, but it's not easy to improve more and prove we did more.


[Is this enough?]
This means that our MICH actuator (BS - 0.5*PRM) changes MICH length by 1.79e12 Hz^2/f^2 m/counts and PRC length by 2.06e11 Hz^2/f^2 m/counts. According to Optickle simulation in LIGO-T1300328, sensing matrix for PRMI sideband is

            PRCL    MICH
REFL 45I    3.4e6   2.5e3
REFL 45Q    6.4e4   1.3e5  W/m


So, the estimated effect of residual MICH to PRCL coupling to the sensing matrix measurement is;

MICH to REFL45Q element:   6 % error (= 6.4e4/1.3e5/(1.79e12/2.06e11) )
MICH to REFL45I element: 16000 % error (= 3.4e6/2.5e3/(1.79e12/2.06e11) )

If we ignore MICH to REFL45I element, which is hard to measure anyway, I think this is acceptable.


[Next]
 - Update gain balancing factor between PRM and BS from 1/16 to 1/14.7 (FM5 in H1:SUS-BS_M3_LOCK_L)
 - Update IQ demod phase in H1:LSC-REFLAIR_A_RF45_PHASE_R to minimize PRCL to MICH coupling
 - Measure sensing matrix in PRMI

Images attached to this report
Comments related to this report
arnaud.pele@LIGO.ORG - 16:15, Tuesday 11 March 2014 (10695)

After talking with Yuta, I took a look at our PRM M3 to M3 transfer functions, measured with the osems as actuators and sensors, and compared it with the model. We see a factor difference of ~20% (model=1.18*measurement). This would mean the calibration error comes from the actuation chain (both of us are using T1000061 as a reference for calibrating actuation).

Images attached to this comment
yuta.michimura@LIGO.ORG - 16:54, Wednesday 12 March 2014 (10724)

I did the calibration of the error signal wrong.  The calibration factor 4.7e11 counts/m was correct, but I multiplied this number to the measured data in the script, instead of dividing.
Correct figures are attached. Actuator calibration from the fitting is as follows

BS to PRY: 8.13e-12 Hz^2/f^2 m/counts  (half of this is BS to PRCL in PRMI)
PRM to PRY: 8.79e-12 Hz^2/f^2 m/counts  (same as PRM to PRCL)
BS-0.5*PRM to MICH: 8.13e-12 Hz^2/f^2 m/counts (same as BS to PRY)
BS-0.5*PRM to PRCL: 9.28e-13 Hz^2/f^2 m/counts

Discussion about MICH to PRCL supression ratio and sensing matrix measurement error from actuation off diagonal element remain unchanged.

Also, note that my definition of MICH is one-way length difference between BS to ITMX and BS to ITMY. PRCL is PRC one-way length.

[Data and script]
Data and script used lives in ~/yutamich/BSPRMact/ folder.
./PRMdrive_complete.xml   (dtt of PRM actuation TF measurement)
./BSdrive_complete.xml   (dtt of BS actuation TF measurement)
./PRYoltf_complete1.xml    (dtt of PRY OLTF measurement)
./BSPRMact.py    (script for plotting and calibrating data)

Images attached to this comment
Displaying reports 66761-66780 of 77184.Go to page Start 3335 3336 3337 3338 3339 3340 3341 3342 3343 End