Displaying reports 66241-66260 of 85883.Go to page Start 3309 3310 3311 3312 3313 3314 3315 3316 3317 End
Reports until 12:52, Monday 03 August 2015
H1 CDS (SUS)
david.barker@LIGO.ORG - posted 12:52, Monday 03 August 2015 (20165)
18bit DAC autocal results from last Tuesday's restarts

Late entry from last Tuesday's SUS front end restarts, here are the results of the 18bit DAC AUTOCALs performed by the IOP model. One card fails autocal, two take an addtional 1.2S to complete.

h1susb123

[6026421.925705] h1iopsusb123: DAC AUTOCAL FAILED in 5344 milliseconds 
[6026427.286059] h1iopsusb123: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[6026433.073912] h1iopsusb123: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[6026438.434332] h1iopsusb123: DAC AUTOCAL SUCCESS in 5345 milliseconds 
[6026445.457686] h1iopsusb123: DAC AUTOCAL SUCCESS in 6576 milliseconds 
[6026450.818041] h1iopsusb123: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[6026456.178303] h1iopsusb123: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[6026461.537803] h1iopsusb123: DAC AUTOCAL SUCCESS in 5344 milliseconds 
 
h1sush2a
 
[5885314.201965] h1iopsush2a: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[5885319.562309] h1iopsush2a: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[5885326.585739] h1iopsush2a: DAC AUTOCAL SUCCESS in 6572 milliseconds 
[5885331.946076] h1iopsush2a: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[5885337.733940] h1iopsush2a: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[5885343.094372] h1iopsush2a: DAC AUTOCAL SUCCESS in 5341 milliseconds 
[5885348.454724] h1iopsush2a: DAC AUTOCAL SUCCESS in 5344 milliseconds 
 
h1sush2b
 
[2422259.598387] h1iopsush2b: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[2422264.958836] h1iopsush2b: DAC AUTOCAL SUCCESS in 5345 milliseconds 
 
h1sush34
 
[5962934.903750] h1iopsush34: DAC AUTOCAL SUCCESS in 5341 milliseconds 
[5962940.264027] h1iopsush34: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[5962946.051914] h1iopsush34: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[5962951.412329] h1iopsush34: DAC AUTOCAL SUCCESS in 5345 milliseconds 
[5962957.200212] h1iopsush34: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[5962962.559720] h1iopsush34: DAC AUTOCAL SUCCESS in 5340 milliseconds 
 
h1sush56
 
[2418700.148743] h1iopsush56: DAC AUTOCAL SUCCESS in 5345 milliseconds 
[2418705.509074] h1iopsush56: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[2418711.296963] h1iopsush56: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[2418716.657324] h1iopsush56: DAC AUTOCAL SUCCESS in 5344 milliseconds 
[2418722.445270] h1iopsush56: DAC AUTOCAL SUCCESS in 5344 milliseconds 
 
h1susex
 
[613223.518484] h1iopsusex: DAC AUTOCAL SUCCESS in 5346 milliseconds 
[613228.876736] h1iopsusex: DAC AUTOCAL SUCCESS in 5383 milliseconds 
[613234.662541] h1iopsusex: DAC AUTOCAL SUCCESS in 5345 milliseconds 
[613240.020587] h1iopsusex: DAC AUTOCAL SUCCESS in 5346 milliseconds 
[613245.378585] h1iopsusex: DAC AUTOCAL SUCCESS in 5318 milliseconds 
 
h1susey
 
[  130.787835] h1iopsusey: DAC AUTOCAL SUCCESS in 5346 milliseconds 
[  136.148897] h1iopsusey: DAC AUTOCAL SUCCESS in 5346 milliseconds 
[  141.941127] h1iopsusey: DAC AUTOCAL SUCCESS in 5346 milliseconds 
[  147.302189] h1iopsusey: DAC AUTOCAL SUCCESS in 5346 milliseconds 
[  152.663846] h1iopsusey: DAC AUTOCAL SUCCESS in 5346 milliseconds 
 
 
 
 
 
H1 General
thomas.shaffer@LIGO.ORG - posted 12:21, Monday 03 August 2015 (20163)
Morning Locking Summery

H1 was locked when I got in, so I brought ISC_LOCK to DOWN to get some locking practice.

It went up to CARM_ON_TR before stopping and notifying  of "No IR in arms".

Sheila mentioned in a log a few weeks back to go to manual and then go back to the state PREP_TR_CARM, but that did not solve the issue and broke lock when I went back to CARM_ON_TR.

Brought it back up and got the same notification, and then I did exactly what I did last time.

While it was going up and down the last few times I was investigating some of the work the commissioners did last night, and I ended up using SDF to switch back some of the changes from alog20146

At this point I got Jenne involved and she worked hard trying to figure it out while I went to a training.

When Evan came in he admitted that he had forgotten to turn back on the Input to the H1ALS-C_REFL_DC_BIAS filter module.

This seemed to have solved the issue.

This filter module is not being monitored, so I added it to the SDF monitor and Jenne added it to the Guardian.

All seems to be good now, made it to COIL_DRIVERS before a commissioner accidentally lost lock.

H1 General
jeffrey.bartlett@LIGO.ORG - posted 11:24, Monday 03 August 2015 (20162)
08:30 Meeting Minutes
Log Times – The time stamp on the headers of aLOG entries are in Local Time. After much discussion, the times in body of the log entries should be entered in UTC time, with a note to that effect. Example: “restarted XYZ at 15:45 UTC”.

Betsy is giving operator training on the SDF system at 10:00 in the control room.

The New LIGO Web page has launched.
 
Prep work for the Tuesday maintenance window: 
   Sub Systems are coordinating planned updates
   CDS: will swap a switch on the End-Y UIM Coil Driver
   VAC: will be regenerating the NEG pump at End-X
   FAC: will be moving several crates to Mid-X    
LHO VE
kyle.ryan@LIGO.ORG - posted 11:17, Monday 03 August 2015 (20161)
1050 - 1100 hrs. local -> In and out of X-end VEA (stopped RGA heating)


			
			
H1 ISC
peter.fritschel@LIGO.ORG - posted 11:08, Monday 03 August 2015 - last comment - 12:30, Monday 03 August 2015(20160)
Suggestions for high frequency 'mystery' noise

Matt E and I were talking about the broadband noise that is showing up coherently in the OMC DC readout, increasing the noise by 15% or something above shot noise, at frequencies above ~80 Hz. The observation is that this noise increases as the input power is increased (i.e., the watts/rtHz on the OMC DC PDs goes up with higher input power). Amplitude noise on one or more RF sidebands is a plausible source of this noise (not a new idea), and we wanted to suggest specific tests be done to look for RF sideband noise. For example:

Comments related to this report
evan.hall@LIGO.ORG - 12:30, Monday 03 August 2015 (20164)

The OMC refl shutter is normally kept closed, but I have just opened it.

H1 TCS
eleanor.king@LIGO.ORG - posted 10:02, Monday 03 August 2015 - last comment - 15:36, Tuesday 04 August 2015(20158)
Using the corner station HWS

There have been some questions about how to run the HWS code.

The HWS code runs on one of three HWS computers, we have one at each end station and one at the corner station.  I have set up a tmux session to run the HWS code constantly at the corner station.  If the code is running, the heartbeat will flash on the TCS HWS ITMX/Y medm screens, and the seidel aberrations will update once a second on the HWS ITMX/Y CODE screen.  To take a measurement using the HWS, in addition to having thr HWS code running, you also need to turn on the RCX link framegrabber power, the Dalsa 1M60 Camera power, and the Superluminescent diode (SLED) power switched on the HWS medm screen.  To increase the lifetime of the SLED and to avoid injecting 1Hz noise into the PEM channels (we are working on filters on the camera power supply to fix this one), we are leaving the HWS hardware off if we are not using it.

 

If you want to stop or restart the corner station code for some reason, you can ssh into the cornerstation hws computer:

>>    ssh -X controls@h1hwsmsr

and attach to the tmux session

>>    tmux attach

This webpage (http://www.dayid.org/os/notes/tm.html) has a list of tmux commands.  We are running two sessions, one for ITMX and one for ITMY.  Go to the relevant session, go to the folder ~/temp, and run the HWS code with the command

>>    Run_HWS_H1ITMX  (or ITMY....)

Comments related to this report
eleanor.king@LIGO.ORG - 15:36, Tuesday 04 August 2015 (20216)

Jim and Dave have installed tmux on the end station HWS computers (thanks guys), so the code is running at these computers now too. It is intialized with the command  >> Run_HWS_H1ETMX  or  >>Run_HWS_H1ETMY in ~/temp, after you log into controls@h1hwsey (or h1hwsex).

H1 CDS (ISC)
jameson.rollins@LIGO.ORG - posted 09:58, Monday 03 August 2015 - last comment - 16:48, Monday 03 August 2015(20157)
h1lsc test points cleared to clear up errant excitation in

There was a persistent excitation in:

H1:ALS-C_REFL_DC_BIAS_EXC

on h1lsc.  This was presumably from an awg process left running by Evan on operator1 workstation.

I killed ALL testpoints on h1lsc (dcuid 10):

jameson.rollins@operator1:~ 0$ diag -l -z
supported capabilities: testing  testpoints  awg 
diag> tp clear 10 *
test point cleared
diag>

Comments related to this report
james.batch@LIGO.ORG - 16:48, Monday 03 August 2015 (20175)
Actually, you should clear the awg, then clear the test point. As it is now, there is still an awg slot with a sine excitation, but no test point.
H1 General
thomas.shaffer@LIGO.ORG - posted 07:21, Monday 03 August 2015 (20156)
Unlocked H1 for Operator taining

I took down the IFO at 717 PST for locking training. The insiral range shows that it was locked for over 12 hours. Awesome!

H1 ISC (CAL)
evan.hall@LIGO.ORG - posted 21:50, Sunday 02 August 2015 - last comment - 09:42, Monday 10 August 2015(20143)
Thoughts on the EY ESD actuation coefficient

Based on measurements of the DARM OLTF and the EY PUM/test crossover that Jeff and I took last week, we can estimate the current value of the EY ESD actuation coefficient. It is 1.45×10−10 N/V2, with a 20 % uncertainty. This is an 80 % increase compared to the previous value (0.8×10−10 N/V2) which was measured at the end of May.

This number mostly relies on the crossover measurement, since above 10 Hz, the effect in the OLTF of changing the actuation coefficient is largely the same as changing the optical gain. Additionally, this number requires us to assume a number for the PUM actuation coefficient. Here I assume that it has not changed since the May calibration (i.e., I use 7.0×10−13 m/ct at dc).

Note that the modeled crossover doesn't really agree well with the measurement above 80 Hz. More investigation is required, particularly since during ER7 we already knew there was an issue with the DARM model around 10 Hz. (This discrepancy is why I say the uncertainty in the coefficient is no better than 20 %.)

To generate this number, I took Jeff's ER7 calibration script and made a version (H1DARMXO.m) that models the crossover. Both scripts (and the parameters file for the July 25 measurement) live in the CalSVN under Runs/PreER8/H1/Scripts/DARMOLGTFs. All parameters were left the same as their ER7 values except for the optical gain (I use 1.0×106 ct/m), the DARM pole (I use 330 Hz), and the EY L3 drive strength (I use 11×10−15 m/ct at dc). By tuning the L3 drive strength to match the measured crossover, we can extract the ESD actuation coefficient, assuming the rest of the L3 signal chain has been well-characterized. This is how I get the number quoted above.

The 80 % increase is sort of consistent with the 70 % increase that we saw when retuning the L3 digital gain post-vent. Strictly speaking, that was a measurement of the relative strengths of EX and EY. However, the DARM OLTF (with the retuned EY L3 gain) stayed roughly the constant before and after the vent, indicating that this 70% increase really is a change in EY.

Non-image files attached to this report
Comments related to this report
evan.hall@LIGO.ORG - 09:42, Monday 10 August 2015 (20374)CAL

I would like to clarify the relationship between the above entry and Sudarshan's entry.

The above entry is making a statement about a number (in N/V2) which characterizes the force applied to the test mass given a certain amount of voltage applied to the ESD (both its bias and its quadrants).

Sudarshan's entry is making a statement about a number (in m/ct) which characterizes the test mass displament given a certan number of counts in the DARM control signal. Therefore, it includes not only the above ESD strength (in N/V2), but also the mechanical response of the test mass, the electronic driver transfer function, the DAC, and the digital control filters for EY. In particular, it includes the digital EY L3 drivealign gain, which was changed from 50 ct/ct to 30 ct/ct after the vent in order to compensate for an unknown* increase in some other part of the EY actuation chain. Therefore, we expect Sudarshan's number to be small; if the compensation had been done perfectly, we would expect 0% change.

 

*Although it is unknown, I hypothesize that it is due to the discharging of EY resulting in an increase in the ESD actuation coefficient (in N/V2).

H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 21:26, Sunday 02 August 2015 (20153)
Frequency noise transfer function near coupling null
Evan, Stefan

Using a line at 6409.7Hz we found a null in the frequency noise coupling. Thus we took the REFL_9 to OMC_DCPD_A transfer function (plot 1).
This is a nice modelling challenge - thus we spend some time calibrating it in meaningful units.

Calibration:
 - OMC_DCPD_9 (H1:IOP-LSC0_MADC0_TP_CH12):
   - This is just a copy of the filters in the PDA filter module, plus the 13.7kHz 17.8kHz poles from preamp (alog 17647). We did not take into account the AA board, but it should be the same for both channels:
   - G=8.63151e-07
   - P=0.87, 7.689, 7.689
   - Z=10.07, 78.912, 90.642, 13700, 17800
 - REFL9 (H1:IOP-LSC0_MADC1_TP_CH28):
   - The gain is 2900V/WattsRF (see alog 10661) x (12dB whitening) x 1638.4cts/V, plus a z=1,p=10Hz whitening filter (again, no AA board compensation)
   - G=5.2867e-08 = 1/(2900*3.9811*1683.4)
   - P=1
   - Z=10

Plot 2 shows the 9 OMC_DCPD traces during heating, calibrated in A/rtHz

The xml template is in LIGO-T1500414
https://dcc.ligo.org/T1500414

Images attached to this report
H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 20:44, Sunday 02 August 2015 (20152)
Broadband coherence noise at close to the null of frequency coupling
The broadband level below 8kHz didn't change, but the structure around 15kHz disappeared... (Compare to alog 19856)
Images attached to this report
H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 20:39, Sunday 02 August 2015 (20151)
Broadband frequency noise injection during thermal tuning (sneak preview)
Attached is a plot of the frequency noise in OMC_PDC_A at six different times during the thermal tuning. There is a significant drop in frequency noise coupling. However the feature that changes most drastically is the carrier 10-mode resonance at 5.1kHz. Thus some of this might be alignment induced effects.

Plot 2 has three more traces with even more heating.

Images attached to this report
H1 PSL
kiwamu.izumi@LIGO.ORG - posted 19:35, Sunday 02 August 2015 (20148)
ISS 2nd loop brief update

This is a brief update of the current situation of the ISS 2nd loop.

 

[Contribution to DARM]

Here are estimation of the contribution of intensity noise to DARM with and without closing the 2nd loop:

The left plot is an estimation without the 2nd loop closed, and the right plot with the 2nd loop closed. The estimation was done by measuring the coupling transfer function from the ISS 2nd loop PD array to the DARM error point and propagating the measured spectra of the ISS array via the measured transfer function to DARM displacement. As you can see, when the 2nd loop is open, it pollutes the DARM spectrum in 100- 400 Hz. Though it looks like I am missing a factor of two or so for some reason in order for the intensity noise to be dominant in the DARM spectrum as observed.

As shown in the right plot, the loop suppresses intensity noise and pushes it to a point more than a factor of 10 apart from the DARM noise floor. This is good. One thing I noticed is that the spectral shape of intensity noise changed depending on whether the 2nd loop was closed or not. For example, the left plot clearly shows structure in 100 - 400 Hz band in the estimated contribution of intensity noise while the right plot does not show the structure. I am still studying what is going on, but it seems like it is from some kind of readout noise of the PD array which covered the real spectral shape.

Also, I attach a measured coupling from the PD arrays to DARM displacement [meters/RIN].

As shown, it is on the order of 3-4 x 10-14 [meters/cnts]. By the way, meters, I refer here is unsuppressed DARM displacement. The measurement was done by injecting swept sine at  H1:PSL-ISS_TRANSFER1_INJ with the 2nd loop intentionally disabled in order to get high coherence. The interferometer was locked fully in low noise and a PSL power was at 24 W at around 8:40 PT of July 31st.

 

[Suppression]

As mentioned above, the suppressed noise does not make sense. They look as if they are covered by some kind of readout noise.  Nevertheless, it is evident that the suppression at 300 Hz is approxiamtely a factor of 60 as expected. Good. Later, Stefan and I undid the anti-whitening in the measured spectra in order to check whether the signals were above ADC noise or not -- they were above ADC noise by a factor of 10 or so. Also, I believe that the structure in 10-20 Hz is some scattering induced noise which Gabriele reported before (for example, alog 15198).

[Next to do]

* Modeling of the measured intensity noise coupling. 

* Figure out the read out noise.

Images attached to this report
H1 ISC (INJ, ISC)
stefan.ballmer@LIGO.ORG - posted 18:40, Sunday 02 August 2015 - last comment - 18:50, Sunday 02 August 2015(20147)
Broadband frequency noise injection
Evan, Stefan,

We set up a function generator to get a 3kHz-30kHz broadband frequency noise injection. Details:

 - Function generator, set on 'noise'
 - Followed by an SR560 (AC, band-passed between 3kHz and 30kHz, gain 1)
 - This drives drive a noise floor of about 22uVrms/rtHz at 10kHz.
 - We hooked this up the the CM board input 2 (note to self - need to reconnect SUM_B for the IFO to re-lock).

 - Next we turned on the CM board input 2 with -20dB gain: this should add about 2.2uVrms/rtHz at 10kHz.

Attached is a plot of REFL_9 and OMC_DCPD_A, with annotated features at the carrier 10 and carrier 20 modes.

We left this excitation on for the thermal run tonight.
Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 18:50, Sunday 02 August 2015 (20149)ISC
Here are updated numbers for higher order arm resonances:

f1=9100230Hz (verified)
f2=5*f1
Arm length: L=3994.47 (same used for x and y)
RoC:
ETMX: 2241.54m
ITMX: 1939.3m
ETMY: 2238.9m
ITMY: 1939.39m

XARM:
Resonance condition: fres = FSR * (q  + (l+m+1)*fTM/FSR)
Free Spectral Range (FSR)    : 37.5259 kHz
Transverse Mode Spacing (fTM): 32.4296 kHz
f1 sideband:
q=243	l+m=0	 Freq. diff. = 18.5727 kHz
q=242	l+m=0				 Freq. from antiresonant = 0.190312 kHz
q=242	l+m=1	 Freq. diff. = 13.4763 kHz
q=241	l+m=1				 Freq. from antiresonant = 5.28668 kHz
q=241	l+m=2	 Freq. diff. = 8.37992 kHz
q=-243	l+m=0	 Freq. diff. = 18.5727 kHz
q=-243	l+m=0				 Freq. from antiresonant = 0.190312 kHz
q=-243	l+m=1	 Freq. diff. = 13.8569 kHz
q=-244	l+m=1				 Freq. from antiresonant = 4.90605 kHz
q=-244	l+m=2	 Freq. diff. = 8.76055 kHz
f2 sideband:
q=1213	l+m=0	 Freq. diff. = 17.8114 kHz
q=1212	l+m=0				 Freq. from antiresonant = 0.95156 kHz
q=1212	l+m=1	 Freq. diff. = 12.715 kHz
q=1211	l+m=1				 Freq. from antiresonant = 6.04793 kHz
q=1211	l+m=2	 Freq. diff. = 7.61868 kHz
q=-1213	l+m=0	 Freq. diff. = 17.8114 kHz
q=-1213	l+m=0				 Freq. from antiresonant = 0.95156 kHz
q=-1213	l+m=1	 Freq. diff. = 14.6182 kHz
q=-1214	l+m=1				 Freq. from antiresonant = 4.14481 kHz
q=-1214	l+m=2	 Freq. diff. = 9.5218 kHz

Carrier:
l+m=1            Freq. diff. =  5096.3661 Hz
l+m=2            Freq. diff. = 10192.7323 Hz

YARM:
Checking accidental sideband resonances in the arm cavities:
Resonance condition: fres = FSR * (q  + (l+m+1)*fTM/FSR)
Free Spectral Range (FSR)    : 37.5259 kHz
Transverse Mode Spacing (fTM): 32.4638 kHz
f1 sideband:
q=243	l+m=0	 Freq. diff. = 18.5727 kHz
q=242	l+m=0				 Freq. from antiresonant = 0.190312 kHz
q=242	l+m=1	 Freq. diff. = 13.5105 kHz
q=241	l+m=1				 Freq. from antiresonant = 5.25248 kHz
q=241	l+m=2	 Freq. diff. = 8.44832 kHz
q=-243	l+m=0	 Freq. diff. = 18.5727 kHz
q=-243	l+m=0				 Freq. from antiresonant = 0.190312 kHz
q=-243	l+m=1	 Freq. diff. = 13.8911 kHz
q=-244	l+m=1				 Freq. from antiresonant = 4.87185 kHz
q=-244	l+m=2	 Freq. diff. = 8.82895 kHz
f2 sideband:
q=1213	l+m=0	 Freq. diff. = 17.8114 kHz
q=1212	l+m=0				 Freq. from antiresonant = 0.95156 kHz
q=1212	l+m=1	 Freq. diff. = 12.7492 kHz
q=1211	l+m=1				 Freq. from antiresonant = 6.01373 kHz
q=1211	l+m=2	 Freq. diff. = 7.68708 kHz
q=-1213	l+m=0	 Freq. diff. = 17.8114 kHz
q=-1213	l+m=0				 Freq. from antiresonant = 0.95156 kHz
q=-1213	l+m=1	 Freq. diff. = 14.6524 kHz
q=-1214	l+m=1				 Freq. from antiresonant = 4.11061 kHz
q=-1214	l+m=2	 Freq. diff. = 9.5902 kHz

Carrier:
l+m=1            Freq. diff. =  5062.1663Hz
l+m=2            Freq. diff. = 10124.3327Hz
H1 TCS (ISC)
evan.hall@LIGO.ORG - posted 18:37, Sunday 02 August 2015 - last comment - 10:09, Monday 03 August 2015(20146)
TCS test in progress

Kiwamu, Stefan, Evan

We are trying to minimize the coupling of frequency and intensity noise into DARM by tuning the central heating on the IX CP.

The following excitations have been set up:

The amplitudes were chosen so that each line has an SNR of 50 or so in OMC DCPD sum with a 10 s FFT. Each demodulator demodulates OMC DCPD sum at the appropriate frequency, and then lowpasses I and Q with a 100 mHz, 4th-order butterworth.

At 2015-08-03 01:19:45 Z we changed the IX CP heating power from 0.23 W to 0.36 W.

At 2015-08-03 02:57:25 Z we changed the IX CP heating power from 0.36 W to 0.53 W.

At 2015-08-03 04:26:20 Z we changed the IX CP heating power from 0.53 W to 0.41 W.


Additionally:

Comments related to this report
evan.hall@LIGO.ORG - 21:59, Sunday 02 August 2015 (20154)

Stefan has reverted the rewiring on the CARM board.

We are leaving the injected frequency line on so we can watch it as the interferometer settles into its new thermal state.

stefan.ballmer@LIGO.ORG - 22:42, Sunday 02 August 2015 (20155)
Also, we further increased the ISS gains: the first loop went up by 10dB, the second loop by 6dB. No immediate noise improvement was visible in DARM.
lisa.barsotti@LIGO.ORG - 10:09, Monday 03 August 2015 (20159)ISC
I looked at OMC SUM/NULL during the long lock last night, after the frequency noise injection was turned off.
There is no significant difference between the beginning and the end of the lock. The excess of noise was of the order of 10% shot noise level, similarly to the night before. The highest excess of noise I have seen is ~15%, corresponding to  a few days ago , July 31st.
Images attached to this comment
H1 ISC (ISC)
stefan.ballmer@LIGO.ORG - posted 02:41, Thursday 23 July 2015 - last comment - 14:53, Monday 24 August 2015(19856)
Coherent broadband noise in OMC_DC_SUM
We observed broadband coherence of OMC_DC_SUM with ASC_AS_C_LF_SUM and ASC_A_RF36_PIT. We made some numbers and plots, using the 64kHz version of the channels.

First the measurements we made on OCXO oscillator:
- ASC_AS_C sees a RIN of about 5e-7/rtHz above 100Hz (either from H1:ASC-AS_C_SUM_OUT_DQ or from H1:IOP-ASC0_MADC6_TP_CH11). The same is true for its segment 1.
- The calculated shot noise RIN at 20mA (quantum efficiency 0.87) detected is 4.0e-9/rtHz.
- The 4.0e-9/rtHz agrees with DCPD_NULL_OUT_DQ's prediction (8.0e-8 mA/rtHz/20mA).
- DCPD_SUM_OUT_DQ sees a slightly elevated RIN of 4.6e-9/rtHz (9.2e-8 mA/rtHz/20mA).

- The RIN in DCPDA (H1:IOP-LSC0_MADC0_TP_CH12, corrected for the whitening) is about 5.9e-8 mA/rtHz, or RIN = 5.9e-9/rtHz at 20mA/2diodes (~15pm DARM offset)...
- ...or about 3.3e-8 mA/rtHz or 1.2e-8/rtHz at 5.7mA/2diodes (~8pm DARM offset).

- ASC-AS_C_SEG1 (H1:IOP-ASC0_MADC6_TP_CH11) and OMC-DCPD_A (H1:IOP-LSC0_MADC0_TP_CH12) shows a coherence of 0.053 at 20mA, suggesting a white noise floor a factor of 0.23 below shot noise.
- At 5.7mA the same coherence is about 0.13, i.e. the white noise floor is a factor of 0.39 below shot noise.
- These two measurements are in plot 1.

- Taking the last two statements together, we predict a coherent noise of
  - 5.9e-8 mA/rtHz *0.23 = 1.4e-8 mA/rtHz at 20mA/2diodes (~15pm DARM offset)  (RIN of coherent noise = 1.4e-9/rtHz) - The pure shot noise part is thus 5.7e-8 mA/rtHz
  - 3.3e-8 mA/rtHz *0.39 = 1.3e-8 mA/rtHz at 5.7mA/2diodes (~8pm DARM offset)  (RIN of coherent noise = 4.5e-9/rtHz) - The pure shot noise part is thus 3.0e-8 mA/rtHz.

- AS_C calibration:
 - 200V/W (see alog 15431)
 - quantum efficiency 0.8 (see alog 15431)
 - 0.25% of the HAM 6 light (see alog 15431)
 - We have 39200cts in the AS_C_SUM. Thus we have
   - 39200cts / (1638.4cts/V) * 10^(-36/40) (whitening) / (200V/W) = 1.89mW and AS_C. (shot noi
   - 1.89mW/0.025 = 76mW entering HAM6. I.e. we have slightly more sideband power than carrier power (Carrier: 27mW in OMC transmission).
   - Shot noise level on AS_C_SUM is at 2.0e-8 mA/rtHz, corresponding to a RIN of 1.6e-8/rtHz. I.e. the coherent noise seen at 5e-7/rtHz is high above the shot noise. Dark noise TBD.
   - The light entering HAM 6 has a white noise of 5e-7/rtHz*76mW = 3.8e-5 mW/rtHz 
    

Bottom line:
 -We have ~1.4e-8mA/rtHz, or 1.9e-8mW/rtHz of coherent white noise on each DCPD.
 -It corresponds to 3.8e-5mW/rtHz before the OMC, i.e. the the OMC seems to attenuate this component by 2000.
 -This noise stays at the same level (in mW/rtHz) for different DCPD offsets.


Next, we switched back to the IFR for testing. plot 2 shows the same coherences (all at 5.7mA / 8pm DARM offset), but on the IFR. Interestingly now AS_C and AS_A_RF36 start seeing different noise below 2kHz. We convinced our selfs that the higher excess noise seen in AS_A_RF36 is indeed oscillator phase noise from the IFR - so that is clearly out of the picture once of the OCXO. (Evan will shortly log the oscillator phase noise predictions.)


64k Channel list:
H1:IOP-LSC0_MADC0_TP_CH12:     OMC-DCPD_A  (used in plot)
H1:IOP-LSC0_MADC0_TP_CH13:     OMC-DCPD_B
H1:IOP-LSC0_MADC1_TP_CH20:     REFLAIR_A_RF9_Q
H1:IOP-LSC0_MADC1_TP_CH21:     REFLAIR_A_RF9_I
H1:IOP-LSC0_MADC1_TP_CH22:     REFLAIR_A_RF45_Q
H1:IOP-LSC0_MADC1_TP_CH23:     REFLAIR_A_RF45_I
H1:IOP-LSC0_MADC1_TP_CH28:     REFL_A_RF9_Q
H1:IOP-LSC0_MADC1_TP_CH29:     REFL_A_RF9_I
H1:IOP-LSC0_MADC1_TP_CH30:     REFL_A_RF45_Q
H1:IOP-LSC0_MADC1_TP_CH31:     REFL_A_RF45_I


H1:IOP-ASC0_MADC4_TP_CH8:      ASC-AS_A_RF36_I1
H1:IOP-ASC0_MADC4_TP_CH9:      ASC-AS_A_RF36_Q1
H1:IOP-ASC0_MADC4_TP_CH10:     ASC-AS_A_RF36_I2
H1:IOP-ASC0_MADC4_TP_CH11:     ASC-AS_A_RF36_Q2
H1:IOP-ASC0_MADC4_TP_CH12:     ASC-AS_A_RF36_I3
H1:IOP-ASC0_MADC4_TP_CH13:     ASC-AS_A_RF36_Q3   (used in plot)
H1:IOP-ASC0_MADC4_TP_CH14:     ASC-AS_A_RF36_I4
H1:IOP-ASC0_MADC4_TP_CH15:     ASC-AS_A_RF36_Q4

H1:IOP-ASC0_MADC6_TP_CH11:     ASC-AS_C_SEG1  (used in plot)
H1:IOP-ASC0_MADC6_TP_CH10:     ASC-AS_C_SEG2
H1:IOP-ASC0_MADC6_TP_CH9:      ASC-AS_C_SEG3
H1:IOP-ASC0_MADC6_TP_CH8:      ASC-AS_C_SEG4





Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 17:01, Thursday 23 July 2015 (19882)
Some more estimation - this time for frequency noise:

- Shot noise on the refl diodes is given by Pshot=sqrt(2*h*nu*Pr_lock)
- The cavity sensing function is P_9_pk = 4*Gam9*P0 * dNu(f)/(f_p + i*f), where P0 would be the carrier power incident on the PD without the IFO.
- from this we can estimate a frequency (phase) noise of about 8e-11 rad/rtHz.

Gam9=0.219; %alog15874
PSL_low=2; %W
Pr_nolock_low=13.7e-3; %W
PSL_lock=24;
Pr_lock=3.5e-3; %W
IMCt=0.88; 
att=Pr_nolock_low/(PSL_low*IMCt);
P0=PSL_lock*IMCt*att;
inlockdrop=Pr_lock/(P0);

Pshot=sqrt(2*h*nu*Pr_lock);
dphi=Pshot/P0/4/pi/Gam9;
stefan.ballmer@LIGO.ORG - 12:28, Monday 27 July 2015 (19963)
For reference, I ran the numbers on where we would expect the sidebands to show a resonance feature.

I used the following values:
RITM=1939.3m
RETM=2241.54m
L=3994.485m

Checking accidental sideband resonances in the arm cavities:
Resonance condition: fres = FSR * (q  + (l+m+1)*fTM/FSR)
Free Spectral Range (FSR)    : 37.5258 kHz
Transverse Mode Spacing (fTM): 32.4297 kHz
Checking f1 sideband:
q=242	l+m=0	 Freq. diff. = 18.2284 kHz
q=242	l+m=0				 Freq. from antiresonant = 0.534516 kHz
q=242	l+m=1	 Freq. diff. = 14.2013 kHz
q=241	l+m=1				 Freq. from antiresonant = 4.56162 kHz
q=241	l+m=2	 Freq. diff. = 9.10514 kHz
q=-242	l+m=0	 Freq. diff. = 18.2284 kHz
q=-243	l+m=0				 Freq. from antiresonant = 0.534516 kHz
q=-243	l+m=1	 Freq. diff. = 13.1322 kHz
q=-244	l+m=1				 Freq. from antiresonant = 5.63065 kHz
q=-244	l+m=2	 Freq. diff. = 8.0361 kHz
Checking f2 sideband:
q=1212	l+m=0	 Freq. diff. = 16.0903 kHz
q=1212	l+m=0				 Freq. from antiresonant = 2.67258 kHz
q=1212	l+m=1	 Freq. diff. = 16.3393 kHz
q=1211	l+m=1				 Freq. from antiresonant = 2.42356 kHz
q=1211	l+m=2	 Freq. diff. = 11.2432 kHz
q=-1212	l+m=0	 Freq. diff. = 16.0903 kHz
q=-1213	l+m=0				 Freq. from antiresonant = 2.67258 kHz
q=-1213	l+m=1	 Freq. diff. = 10.9942 kHz
q=-1214	l+m=1				 Freq. from antiresonant = 7.76872 kHz
q=-1214	l+m=2	 Freq. diff. = 5.89804 kHz

stefan.ballmer@LIGO.ORG - 00:19, Wednesday 29 July 2015 (20014)ISC
Evan, Matt, Lisa

We did one more test for the broadband coherence noise: Common mode gain +3dB vs -3dB

We see no chnge in the broadband level of the noise below 10000Hz.
However, we do see an FSS gain oscillation at 7320Hz showing up in the OMC_DCPD_SUM - but not in AS_C_LF or AS_A_RF36 - in fact that coherence has adip where we get the frequency noise oscillation.
This strongly suggests that our broadband noise is NOT frequency noise.

Evan also took the frequency noise transfer function - a preliminary analysis here also confirms: the frequency noise should be significantly below the O(1e-8mA/rtHz) noise level we see.
Images attached to this comment
stefan.ballmer@LIGO.ORG - 18:53, Sunday 02 August 2015 (20150)
Note that the higher order mode estimates above were made using a slightly wrong modulation frequency. Updated estimates for the correct modulation frequency are attached to alog 20147
stefan.ballmer@LIGO.ORG - 14:20, Monday 24 August 2015 (20826)
 - ASC-AS_C GETS 2.5% of the HAM 6 light (see alog 15431) (NOT 0.25%)
daniel.hoak@LIGO.ORG - 14:53, Monday 24 August 2015 (20828)

Actually AS_C gets 400ppm of the light entering HAM6 -- the OM1 mirror was swapped from 5% transmission to 800ppm transmission in early April.  See alog:17738.

Displaying reports 66241-66260 of 85883.Go to page Start 3309 3310 3311 3312 3313 3314 3315 3316 3317 End