Displaying reports 74041-74060 of 84476.Go to page Start 3699 3700 3701 3702 3703 3704 3705 3706 3707 End
Reports until 09:25, Friday 14 March 2014
H1 PSL (PSL)
justin.bergman@LIGO.ORG - posted 09:25, Friday 14 March 2014 (10751)
H1 Diode room cleaning

Chris ran the swiffer in the Diode Room this morning for the first time in 8 months. Will try to make cleaning more regular.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 02:34, Friday 14 March 2014 (10750)
Input beam pointing noise doesn't contribute much to ALS COMM noise

Earlier tonight Alexa made some measurements of IMC transfer functions to for matching with her model, and I worked on the slow feedback to the ETM top mass. (alog about that coming in the morning, in short the L2P decoupling has helped)

Now I've made some measurements similar to what ALexa and I did on Monday night (alog 10668) of the linear coupling from the test mass angles to the out of loop frequency noise sensor (the normalized refl PDH).  This time I dithered the PZTs on ISCEX, and measured the spectrum of the normalized PDH and the green QPDs on the input beam on the TMS table.  I haven't calibrated the QPDs, or measured the loop gain, but these are verry slow loops and I dither the PZTs at 5Hz so that should not matter. By dithering each PZT in both pitch and yaw, and finding the peak in the spectrum of both QPDs each time, we get 2 measurements of the coupling from each QPD to frequency noise.

  Hz/ count measured by dithering PZT1 Hz/count measured by dithering PZT2
QPDA PIT 114 126
QPDA YAW 66 154
QPDB PIT 92 44
QPDB YAW 51 69

As you can see the measurements made with different PZTs aren't always consistent.  Using these and measured spectra of the QPDs, we can make the projection of the linearly coupled  noise from input beam pointing to ALS frequency noise, it is not a significant contribution (below 100Hz) based on any of these measurements. At around 100 Hz these projections seem to explain the noise, I believe this is just the noise of the QPDs, but will check in the morning. 

I also checked the linear coupling from the ETM pitch to frequency noise, to see how much it changes with alignment. I measured 424Hz/urad, moved the ETM by 0.1urad, measured 1.12kHz/urad, tried to move it back to the original spot and measured 2.03kHz/urad.  Then I tweaked up both pitch and yaw on the ITM and ETM to try to maximize the green transmission, and got 3.2kHz/urad. So we can change the linear coupling by adjusting the alingment; by hand I only seem to make it worse but hopefully the WFS will do better.

I am leaving the green arm locked, and the guardian running the ALS COMM handoff, so hopefully the IR will be resonanting in the arm some part of the night.

Images attached to this report
H1 CDS
cyrus.reed@LIGO.ORG - posted 17:50, Thursday 13 March 2014 (10746)
h1pemmy Working (Finally)

h1pemmy is finally up and working.  The first problem relatively easily found was a bad ADC card, which was swapped early on after it was seen to generate 'channel hopping' errors to dmesg.  Said card has been marked as bad (it was probably pulled from somewhere else, but not actually labelled as bad which led to it's later unfortunate re-installation).  The second issue was that after replacing the ADC card the duotone signal was not appearing on CH31 (numbered from 0).  This led to a number of time consuming component swaps to eventually find that the cause was a bad cable from the internal 16 channel Contec card to the IO chassis backplane.  I could verify with the IO chassis powered up, but the front end computer off, that the duotone signal was present on the correct pin of the cable feeding the ADC.  After boot/code initialization, the duotone input was switched off by the relay on the adapter board, and the last channel of the AA chassis would then feed the ADC (verified by injecting a signal through the AA chassis).  I could also verify the relay control voltage with the Duotone0_select testpoint on the backplane.  The code is (in it's present form, in theory) hard coded to never activate this relay, so seeing 5V here is not right.  The cable itself is mis-crimped, such that pins 1/20, 2/21, ... , 18/37 are shorted together, with pin 19 not connected at the male/Contec side of the cable, a fact not immediately obvious in the back of a dark rack, but more so once exposed to the light...  The moral of this tale is to double check the internal 37 pin cable that controls the backplane if the duotone signal seems to go missing between the testpoint on the board and the ADC sometime after boot, there may be more of these floating around.

Images attached to this report
H1 SUS
keita.kawabe@LIGO.ORG - posted 17:48, Thursday 13 March 2014 - last comment - 10:21, Friday 14 March 2014(10747)
ETMX PUM Y2P decoupling done

Offending Y2P peak between 1 and 2Hz (pink) was removed after a new decoupling filter was put in place (green).

In the H1:SUS-ETMX_L2_DRIVEALIGN_Y2P filter, I put the same invP2P filter in FM1 as in the P2P path, then added a diagonalization filter ("Y2Pdiag") in FM2, and another filter that is a 3rd order elliptic BP in FM3. I didn't try to remove 0.4-0.5Hz Y2P peak, it's not great but probably good enough.

Images attached to this report
Comments related to this report
keita.kawabe@LIGO.ORG - 17:52, Thursday 13 March 2014 (10748)

ITMX PUM P2Y and Y2P measurement was done, but I need to leave before generating decoupling filter.

Seems like ITMX PUM is somewhat better diagonalized than ETMX PUM, but I'll remove 1.4Hz P2Y peak anyway.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 19:37, Thursday 13 March 2014 (10749)ISC
Remember, the ITM is a wire hang QUAD (the test mass is suspended from the PUM via a wire loop and prisms), and has significantly different dynamics than the ETM fiber welded QUAD. This may be an explanation for the different dynamics.

I also imagine you'll have to do this process all over again with the ITM once it becomes monolithic like the ETM.

 
keita.kawabe@LIGO.ORG - 10:21, Friday 14 March 2014 (10755)

We probably need to re-do everything once it's re-hang.

H1 SYS (SYS)
corey.gray@LIGO.ORG - posted 16:46, Thursday 13 March 2014 (10743)
H1 Ops Overview MEDM

Thomas started work on an Operator Overview screen.  This screen has a graphic of H1 with all of its chambers.  For each chamber, we have buttons to easily & directly open HEPI, SEI, & SUS screens.  The buttons are also colored such that they indicate whether Watchdogs are GREEN or RED.  So for quick glances, this medm can give you an idea of ALL WATCHDOGS.

This is a living screen, and we plan to add more features (Guardian, "Measurement In Progress", etc.).  This medm currently resides at: 

/opt/rtcds/userapps/release/sys/h1/medm

We currently have this medm is now an FOM & currently on our video1 Wall Monitor.  The CDS SUS Overview also shares this FOM, but we may remove that screen since that screen is sort of redundant (or it will be once we get all SUS screens on the Ops Overview screen).

Images attached to this report
H1 INS (SEI)
jim.warner@LIGO.ORG - posted 16:45, Thursday 13 March 2014 (10745)
TF running on ETMY ISI on opsws1

TF is setup on the workstation with a 2.5 hour delay, to allow for PCAL work. Lucky number 3.

LHO General
corey.gray@LIGO.ORG - posted 16:31, Thursday 13 March 2014 (10740)
Ops DAY Summary

.......LVEA:  Laser SAFE..............EY:  Laser SAFE.........EX:  Laser HAZARD.......

A major activity today was the installation of the Spool at EY, installation of viewports on the spool, and then getting PCal pylons staged into position.  Other activities are:

H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:29, Thursday 13 March 2014 (10744)
Dust Monitors
End-Y - The dust monitor in the spool cleanroom (#2) at End-Y failed with a low battery message. Filiberto replaced a blown fuse in the network junction box. The dust monitor appears to be working at this time. The dust monitor for the BSC10 chamber (#1) is charging and will be replaced in the morning. There is a temporary handheld unit in the chamber cleanroom. 

HAM5 Cleanroom – Getting communications errors on the dust monitor in the HAM5 cleanroom. Filiberto found low voltage on this unit. It is shut down for charging overnight. I will bring it back on line in the morning.     
H1 AOS
yuta.michimura@LIGO.ORG - posted 14:48, Thursday 13 March 2014 (10742)
PRMI noise budget model updated for balanced BS/PRM actuator

I updated Simulink noise budget model to incorporate balanced BS/PRM actuator.
Updates made since last alog (#10441) are;


PRMI sensing matrix I used is;
                PRCL    MICH
REFLAIR 45 I    4.8e5   1.5e4
REFLAIR 45 Q    3.9e3   -2.6e4  W/m


Some plots from NB model are attached. Data I used is taken from Mar 12, 12:43:00 UTC for 2048 seconds, when PRMI is sideband locked with REFLAIR45.

OLTF_MICH_1078663396.png: MICH OLTF. The magnitude from the model is higher than the measured by ~40 %. This means that there are some errors in the sensing matrix measurement. We have sensor/actuator calibration error of ~10%. Also, there was a power drop in the cavity build up (POP18) by ~10%. However, these errors don't explain the disagreement between the model and measurement. We need more investigaton on this. (There was is a suspision about the factor of sqrt(2) in BS, but I've checked that)

OLTF_PRCL_1078663396.png: PRCL OLTF. The model and measurement agrees within 10%. Also, phase looks reasonable (compare the OLTF before output matrix diagonalization in alog #10441; we had a dip).

PRCLtoMICH_1078663396.png, MICHtoPRCL_1078663396.png: Measured coupling between MICH loop and PRCL loop (TF from H1:LSC-MICH_EXC to H1:LSC-PRCL_IN1 or vice versa). Compared with the same measurement done before output matrix diagonalization, coupling is at least factor of 2 less (see alog #10481). Model explains some features qualitatively.

NB_MICH_1078663396.png, NB_PRCL_1078663396.png: Noise budget for MICH and PRCL loop. Note that seismic noise is not real (copied from LLO model).

Images attached to this report
H1 PSL (PSL)
corey.gray@LIGO.ORG - posted 13:44, Thursday 13 March 2014 (10741)
H1 PSL Operator Check

LASER

PMC

FSS

ISS

Non-image files attached to this report
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
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?

Displaying reports 74041-74060 of 84476.Go to page Start 3699 3700 3701 3702 3703 3704 3705 3706 3707 End