Displaying reports 57981-58000 of 85647.Go to page Start 2896 2897 2898 2899 2900 2901 2902 2903 2904 End
Reports until 17:09, Friday 15 July 2016
H1 ISC
stefan.ballmer@LIGO.ORG - posted 17:09, Friday 15 July 2016 - last comment - 17:08, Friday 29 July 2016(28442)
Recycling gain does not depend on PR2 spot position

Kiwamu, Stefan

Using the pr2spotmove script (see alog 28420), we moved the spot on PR2 in lock by almost 1 milimeter.

Conclusions:

- The carrier recycling gain desn't care about the PR2 spot positon.
- The POP beam from PR2 to the invacuum POP diode is fairly close to the edge of the visibility aperture. This might be an issue for LSC aux noise.

Details:

- To be able to explore the full range of motion, we had to switch back to the REFL B WFS for PRC2 / PR3 control. We BTW verified that this WFS also works at 40W (and during the power increase).
- With that, the move-limiting aperture is the path from PR2 to POP. We can move until the POP_A loses the beam. The pitch and yaw min/nominal/max values for PR3 alignment angles are
    Pitch value / delta:
     min: -302.95  / -4.6urad
     nom: -298.35 / 0urad
     max: -275.35 /  +23urad
    Yaw value / delta:
     min: 257.45 / -16urad
     nom: 273.45 / 0urad
     max: 281.45 / +8urad
  Notice how close to the edge we are in pitch - this could be a factor for PRCL/SRCL/MICH auxiliary length noise and scatter coupling. We have to revisit this in low-noise.

- The 27.6urad move in pitch (24urad in yaw) peak-to-peak move corresponds to 0.9mm (0.8 mm) for the PR2 spot position. Note though that for the beam in transmission of PR2 that corresponds to several spot sizes of motion. (The virtual beam waist behind PR2 is 114u, i.e. we moved the spot more than 7 beam waists. As a result the beam completly left the POPAIR camera view.)


 


 

Non-image files attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 17:08, Friday 29 July 2016 (28748)

Here is the theoretical matrix for this move (note that signs will vary for pitch and yaw):

    PR2/PR3=-9.041812537326308*t3;

    PRM/PR3=1.824484077268346*t3;

    IM4/PR3=0.964764706304192*t3;

 

This was calculated with the following data (in meters):

RPRM=-11;

RPR2=-4.555;

RPR3=36.0;

RITM=1939;

LPRM=16.6128;

LPR2=16.1551;

LPR3=24.88797;

LARM=3994.5;

LIM4=0.413;

LIM3=1.17;

n=1.45;

f=-RITM/(n-1);  # thin lens approximation

fm=-RPRM/(n-1); # thin lens approximation

 

 

 

H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:13, Friday 15 July 2016 (28440)
Ops Day Shift Summary

Title:  07/15/2016, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT)
State of H1: IFO unlocked. Relocking not successful. Need to do initial alignment.   
Commissioning: IFO locked at DC_READOUT, 2.0W, Wind is a moderate breeze (13 – 18mph) and a corresponding bit of elevated X and Y seismic motion. 
Outgoing Operator:  None
 
Activity Log: All Times in UTC (PT)

15:00 (08:00) Start of shift
15:52 (08:52) Richard – Going to HAM6 to check if HV shutter is on
15:55 (08:55) Lockloss – Richard turned on HV shutter
16:22 (09:22) Keita & Travis – Going to End-Y to reset camera
16:57 (09:57) Kyle – Going to Mid-X to check on moving a vacuum pump
17:06 (10:06) Keita & Travis – Out of Mid-Y
17:10 (10:10) IOF locked at NOMINAL_LOW_NOISE 24.9W
17:15 (10:15) Lockloss – commissioning
17:45 (10:45) Kyle – Back from Mid-X
18:03 (11:03) Richard – Going into LVEA to work on HV shutter near HAM6
18:08 (11:08) Richard – Out of LVEA
18:39 (11:39) IFO locked at DC_READOUT 
18:54 (11:54) Lockloss – commissioning
19:14 (12:14) IFO locked at DC_READOUT
19:25 (12:25) Kyle – Going to Mid-Y to look for rigging
20:00 (13:00) Kyle – Back from Mid-Y
20:15 (13:15) Kyle – Going to Mid-X (WP #6000)
20:24 (13:24) Lockloss – commissioning
20:46 (13:46) IFO locked at DC_READOUT
20:49 (13:49) Betsy – Going to Mid-Y
21:16 (14:16) Lockloss – commissioning
21:36 (14:36) IFO locked at DC_READOUT
21:45 (14:45) Betsy – Back from Mid-Y
21:50 (14:50) Kyle – Back from Mid-Y
23:00 (16:00) Turn over to Nutsinee
 

End of Shift Summary:

Title: 07/15/2016, Day Shift 15:00 – 23:00 (08:00 – 16:00) All times in UTC (PT)
Support: Keita, Stefan, Kiwamu,        
Incoming Operator: Nutsinee 

Shift Detail Summary: IFO locked at DC_READOUT, at 2W. Locking went relative well today. Had the IFO to NOMINAL_LOW_NOISE at 24.9Ws. Commissioners working on system. Rode out a 5.1mag EQ with no problems noted in the IFO operation.  
LHO VE
kyle.ryan@LIGO.ORG - posted 15:04, Friday 15 July 2016 (28439)
Relocated stored vacuum pumps at X-mid
Kyle, Gerardo 

Used overhead crane to move EH2600 vacuum pumps from the elevated BT slab to the VEA floor -> Had rearranged pallets of HEPI actuators yesterday so as to create floor space to position (1) ea. EDP200 and (3) ea. EH2600 vacuum pumps adjacent to each other and near the 480 and 208 power receptacles, chilled water connections and LN2 boil-off vapor line.  Now I will be able to run these pumps periodically which will extend there useful life while in storage.
LHO VE
kyle.ryan@LIGO.ORG - posted 13:02, Friday 15 July 2016 (28436)
Manually over-filled CP3
1235 - 1255 hrs. local -> To and from Y-mid 

Opened exhaust check valve bypass valve, opened LLCV bypass valve 1/2 turn -> LN2 at exhaust in 1 minute -> Restored valve configuration to as found.  

Next CP3 overfill to be Monday, July 18th.  
H1 ISC
stefan.ballmer@LIGO.ORG - posted 11:18, Friday 15 July 2016 (28420)
Script for moving the beam spot on PR2 in lock

While Sheila was exploring the input alignment my moving PR3 and letting the initial alignment follow the beam, I recorded the required drive vector for PR3, PR2 and IM4, in both pitch and yaw.

This combination of alignment sliders keeps the spot positions on PR3 and IM4 the same, but moves the spot on PR2 (and therefore somewhat on PRM).

The matrix to convert PR3 alignment slider counts into corresponding alignment slider counts of PR2 and IM4 is
pitPR3toPR2=-9.2;
yawPR3toPR2=+9.2;
pitPR3toIM4=56;
yawPR3toIM4=11;
 

The attached script continuosly reads PR3 slider values and updates PR2 and IM4 slider values, walking the beam on PR2 only.

The script still doesn't have the PRM matrix elements - we will have to addd this in DRMI or full lock.

=========================================================================

Also updated the script to include PRM. This was done in the PRM align state.

pitPR3toPR2=-9.2;
yawPR3toPR2=+9.2;
pitPR3toIM4=56;
yawPR3toIM4=11;
pitPR3toPRM=1.5;
yawPR3toPRM=2.2;
 

Note that this should work in-lock once the PRC1 pointing loop is off (despite the fact that PR3 is WFS controlled).

Non-image files attached to this report
H1 AOS (AOS, CAL, ISC)
keita.kawabe@LIGO.ORG - posted 10:34, Friday 15 July 2016 (28434)
PCal EY camera error (Travis, Keita)

Last night I took a bunch of pictures using PCal EX and EY camera to check the large angle scattering at 20W.

This morning, while I was taking pictures while IFO was unlocked to capture images without 1064 light, EX worked fine but EY stopped working after 10 or 11 pictures. Camera control software stopped responding, I cannot trigger shutter, see the live view, see the camera settings, really nothing.

Rebooting the camera, the camera interface and h1pcaly multiple times didn't help.

H1 AOS (ISC)
richard.mccarthy@LIGO.ORG - posted 10:33, Friday 15 July 2016 - last comment - 11:26, Friday 15 July 2016(28433)
H1 Fast Shutter Driver Found in off State
The other day when verifying rack layout Filiberto felt like something was wrong.  Upon further reflection he came to me this morning thinking he saw the HV shutter drive off.  No readbacks on the lcd screen.  I went out on the floor this morning and sure enough the +-15VDC switch was in the off position.  I turned it on and knocked the IFO out of lock.  At this time I am not sure how long it has been off (will run Dataviewer on a channel.) or why but will investigate.  When we work on this chamber for vacuum reasons we switch off the High Voltage supply so no one should have shut this unit off.   Investigation will continue to see how long we have been running in this state.
Comments related to this report
richard.mccarthy@LIGO.ORG - 11:26, Friday 15 July 2016 (28435)
Further investigation looks like the unit has been off since early April.  The HV Enable was also in the off position and the Trigger PD was disconnected.  Someone really wanted this off.
H1 SEI
hugh.radkins@LIGO.ORG - posted 10:28, Friday 15 July 2016 (28432)
H1 ITMX survives a M5.4 EQ NE of New Zealand--Same location where only ITMX trips on a M6.3 (Wednesday early morning)

So the ITMX did not break lock on this smaller EQ.  Attached are the ISI T240 local channels--a couple hours around the EQ, for both ITMY & X.  Differences in the responses at these inloop T240s for these minute trends is uninformative so don't bother looking.  It is cool that the onboard vertical T240s shows the EQ shape better than the ground STS; related to the sensor correction?  The two ITMs respond ~the same in the regard.  When I compare the ITMs during the larger EQ Wednesday when the ITMX tripped, the response appears similar before the trip in the local basis from this vantage point.  Again, I attach the trends I've looked at but I think zooming in, the frequency space and cartesian basis is next.

The old geophysicist in me believes the trip is occurring with the earlier arriving s-wave, not the large amplitude surface waves.

Images attached to this report
H1 General
jeffrey.bartlett@LIGO.ORG - posted 09:21, Friday 15 July 2016 (28430)
08:30 Meeting Minutes
Subsystems report all is working as expected, at this time.

Commissioning will be focusing on: 
	- Understanding the recycling gain loss
	- Lowering noise in the system
	- Improving the reliability of the IFO	 
H1 ISC
sheila.dwyer@LIGO.ORG - posted 02:09, Friday 15 July 2016 (28429)
POP 90 has been removed from ADS input matrix for some reason

As Jenne wrote, it does look like POP90 should be a god signal to use for an SRM dither lock, but somehow POP90 is not actually going to the ADS input matrix despite what the medm screens say, and what my old alog says.   I wonder if I frogot to check something into the svn after doing the model restart and someone reverted to the old version for some reason? 

Anyway, it seems worth getting the model with OPO90 in ADS back since a dither using POP90 might be an easy way to get SRM alignment under control now that the PD is no longer saturated.  Tonight it looked like the bounce mode rings up when SRM is misaligned, which makes sense if the SRM alignment causes SRC detuning and changes the DARM gain, as people have suggested. 

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 01:39, Friday 15 July 2016 - last comment - 09:22, Friday 15 July 2016(28428)
We can get back to a high-ish recycling gain at 25 W

Sheila, Kiwamu,

Tonight, we continued working on searching for the missing recycling gain. We opened up PRC1 (which uses POP_A_QPD and feeds it back to PRM) and moved PRM manually to study the effect of the spot position on PR2. This seems to work well and we were able to get back to a high recycling gain of about 34 when PSL was 25 W. The attached shows the time series of us moving PRM in pitch toward the negative side by about 90 urad. The first drop in the power recycling gain is caused by the power-up from 2 to 25 W. We had to move SRM by hand in order not to loose too much sideband build up in SRC. Our alignment action seems to pull the common soft (or something similar) to one direction in which all the test masses goes to negative pitch values (see the second attached). Therefore, as we were in O1, at this power level, the recycling gain can be still found under some alignment land. We did not try this test at a higher PSL power.

Also, we have noticed at some point that some segments of the POP QPDs already used up the half of the ADC range at 25 W. So we decreased the whitening gains to 0 dB (which were 6 dB before). Sheila changed the guardian accordingly so that it maintains the 0 dB gain as a nominal setting. Also when we had a good recycling gain with this alignment, the beams on both POP QPDs were almost falling off of the photodiodes

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 09:22, Friday 15 July 2016 (28431)

Another interesting point to note:

In a different lock stretch with a 25 W PSL, I was allso able to recover the recycling gain back to 32 or so by moving the soft offsets mostly in yaw. As reporeted above, it was surprising to me that for some reason moving PRM in pitch also regained the recycling gain.

H1 PEM (DetChar)
keith.riles@LIGO.ORG - posted 20:44, Thursday 14 July 2016 (28426)
Folded magnetometer channels during ER9
Weigang Liu tried folding DARM and selected magnetometer channels during the three days of ER9 (UTC days)
with results posted here:  https://ldas-jobs.ligo.caltech.edu/~weigang.liu/advancedLIGO_3/ER9/files/ER9_magnetometers_and_strain_list.html,
where DARM folding focused on the 10-50 Hz band, and the magnetometer folding was low-pass
below 50 Hz, choices motivated by O1 experience.

As expected, the magnetometer channels still exhibit a variety of pathologies with 2-second periodicity,
but the elevated low-frequency noise in DARM make it hard to see this 2-second contamination in that channel
with this method. Attached are a few sample magnetometer fold summaries over the three days.
Images attached to this report
H1 General
nutsinee.kijbunchoo@LIGO.ORG - posted 19:54, Thursday 14 July 2016 (28425)
Ops EVE shift summary

Quick Summary: We stay at relatively low power because ITM PI damping modules are not ready.

(All time in UTC)

23:45 SUSPI model restart

00:45 DAQ restart

1:47 Kiwamu to the floor aligning REFL camera

2:35 Kiwamu out

2:45 Kiwamu request for higher power. Going to 30W.

H1 ISC
kiwamu.izumi@LIGO.ORG - posted 15:05, Thursday 14 July 2016 - last comment - 11:46, Friday 05 August 2016(28414)
Quick analysis of shot noise from last night

The shot noise level from last night seems higher (worse) than the O1 level by 6%. Here is the spectrum:

You can see that the red trace (which is the one from the last night) is slightly higher than the (post-) O1 spectrum. The 6% increment was estimated by dividing the two spectra for frequencies above 1200 Hz and taking a median of it.

Images attached to this report
Comments related to this report
kiwamu.izumi@LIGO.ORG - 16:41, Friday 15 July 2016 (28441)

Evan H. suggested looking at the null and sum channels to see if the excess in shot noise is from an addition technical noise or not. The attached shows the spectrum of the null and sum channels at the same duration as the spectrum in the above entry.

From this plot, it is evident that the excess is not due to technical white noise.

Images attached to this comment
kiwamu.izumi@LIGO.ORG - 20:15, Thursday 21 July 2016 (28576)CAL, ISC

It is quite likely that the calibration is wrong -- the true shot noise level can be smaller than what we have measured.

I have checked the calibration of the DARM signal by comparing it against the Pcal excitation signals. I used the same lock stretch as the above entry. The height of the Pcal line at 331.9 Hz in the DARM spectrum was found be too high by 13% relative to the Pcal TR and RX PDs. See the attached. This means that we have overestimated the DARM signal at 331.9 Hz due to a calibration error. If we assume this is all due to an inaccurate optical gain, actual shot noise level should be smaller by the same factor of 13% that what we thought, corresponding to a ~7% smaller shot noise level than that in O1. We need to nail down whether this is an error in the optical gain or cavity pole in order to further evaluate the calibration error.

Note that the Pcal Y uses a fresh set of the calibration factors that was updated a month ago (27983). The ratio of RX PD over TX PD was found to be 1.002 at 331.9 Hz and this makes me think that the Pcal Y calibration is reliable.

Images attached to this comment
shivaraj.kandhasamy@LIGO.ORG - 09:53, Friday 05 August 2016 (28863)CAL

Here I have attached plots of the optical gain during this lock as well a few locks randomly picked during the month of July. I used O1 model as reference (wasn't not quite sure whether there was new time zero reference after O1 with all kappas set to 1). The first plot showing kappa_C over a few locks during July show that kappa_C values were close to 1. However here we note that the gain in the inverse sensing function during July was set to 1.102e-6 compared to 8.834e-7 during O1 (the referene model has changed). At high frequencies, the relation between corrected h(t) and h(t) recorded in front-end is,

corrected h(t) ~ h(t) / kappa_C ~ inv_gain * DARM_ERR / kappa_C

So for same DARM_ERR, kappa_C of 1 during July 2016 corresponds to 0.8 * h(t)  (= 8.834e-7 / 1.102e-6) as that of during O1. This assumes that there wasn't any change in the gain of the electronic chain on the OMC side.  The second plot show trend of kappa_C during the lock Kiwamu was looking at. An interesting thing to note here that there was ~10% change in the optical gain during this lock.  Kiwamu's plot correspond to time of the second peak we see in the plot (a coincidence!). The kappa_C value of 1.15 suggests that the measured h(t) in the above a-log would correspod to 0.70 ( = 8.834e-7/1.102e-6/1.15) times that of h(t) we would be measured during O1. Since the trend plot show that there were times in the same lock during which the kappa_C values were different, I tried to compare the power spectrum between those times. The third plot show that comparison. The mystery is that eventhough the ratio between the 331.9 Hz photon calibrator line and DELTAL_EXTERNAL line is ~10 % different between the times compared (and hence corresponding to ~10% different optical gain), the shot noise level looks same! We couldn't get the exact cavity pole frequencies because at this point I don't have the new LHO DARM model function, but the trend indicated that it didn't change during the lock. For completeness we also added the acutation strength variation during this time. The values are close to what we expect. Since 35.9 Hz ESD line we used during O1 wasn't available, for actuation strength comparison we used 35.3 Hz ESD line.

EDIT: We corrected the earlier estimate of high frequency h(t) level change.

Images attached to this comment
H1 ISC
stefan.ballmer@LIGO.ORG - posted 14:21, Thursday 14 July 2016 - last comment - 14:03, Friday 15 July 2016(28411)
Commissioning goals

*track AAA: PSL
- fix FSS re-locking problem

*track A: missing RG gain:
- PR2 spot position during alignment
- Add digital camera of BS
- arm optics camera defocus & power monitor
- *** fix the 2x omega diodes for SB recycling gain readout
   - check broadband mod of 2w PDs (POB and AS)
   - new lens in front of POB_B

*track B: noise commissioning?
 - shot noise scaling?
  - check calibration
  - try for 50W stable. Serious trouble with PI?
  - pick operating point, then now-noise commissioning
  - reduce RF45
  - Aux length show exess noise - fix it!

Comments related to this report
peter.fritschel@LIGO.ORG - 14:03, Friday 15 July 2016 (28437)

Relevant to noise hunting: all test mass PUM coil drivers should be put in a lower noise state than state 2 (which is the noisiest state). State 4 is the lowest noise, but state 1 should be adequate as well. See 28264.

H1 ISC
sheila.dwyer@LIGO.ORG - posted 23:22, Wednesday 13 July 2016 - last comment - 00:29, Friday 15 July 2016(28398)
POP and REFL cameras not displaying

Nutsinee, Sheila

There is something wrong with the REFL and POP cameras, we see no image from them although we shoudl be seeing something on REFL. 

Comments related to this report
sheila.dwyer@LIGO.ORG - 00:23, Thursday 14 July 2016 (28399)

Actuallythe POP camera is just misaligned (probably has been since we inserted the beamsplitter monday), but there is still nothing on refl which I think there should be.

kiwamu.izumi@LIGO.ORG - 00:29, Friday 15 July 2016 (28427)

The issue with the POP camera was found to be a clipping at the newly installed beamsplitter. This was fixed today. The REFL camera was completely misaligned for some reason, perhaps it was mistakenly moved around. The REFL camera was also realigned. So both are back to functional.

H1 INJ (INJ)
evan.goetz@LIGO.ORG - posted 12:01, Friday 03 June 2016 - last comment - 19:06, Thursday 14 July 2016(27543)
Amplitude of CW injections changed on restart -- why?

The CW injection amptlitude, as measured at the HARDWARE_OUT, appears to have changed on restart May 12. So far, I have not been able to trace down the problem, and conlog is currently down so I cannot see a history of chagnes in the HARDWARE_OUT bank.

Figure 1 observations (10 minute trend of HARDWARE_OUT):

Figure 2 observations (10 minute trend of CW_OUT):

Need conlog to investigate further.

Images attached to this report
Comments related to this report
evan.goetz@LIGO.ORG - 19:04, Thursday 14 July 2016 (28423)

On Jan 20, there was a site-wide power outage (alog 25041), and after everything was restored, one of the filter modules (FM3) was not turned on, but it should have been. This was the 1/AI2 filter with design:

zpk([1.2627e3 - i*2.6133e3;1.2627e3 + i*2.6133e3],[7000;7000],1,"n")

Turning this off flips the phase of the injected signal, but it doesn't really explain the drop in the signal amplitude that I would have expected.

One thing interesting is that there was considerable high frequency noise on the PINJX_HARDWARE_OUT time series that is reduced by turning off the 1/AI2. I plotted the spectrum of the HARDWARE_OUT channel before and after, separated by 24 hours so that the pulsar injections are approximately the same amplitude. Sure enough, with the 1/AI2 filter on, there is a large peak at 7 kHz with an amplitude nearly as large as the highest frequency pulsars. Is this why the pre-power outage time series is about twice as large? It is certainly suspicious...

evan.goetz@LIGO.ORG - 19:06, Thursday 14 July 2016 (28424)

See attached figures for pre- and post-power-outage spectrum.

Images attached to this comment
Displaying reports 57981-58000 of 85647.Go to page Start 2896 2897 2898 2899 2900 2901 2902 2903 2904 End