Displaying reports 69301-69320 of 84537.Go to page Start 3462 3463 3464 3465 3466 3467 3468 3469 3470 End
Reports until 23:37, Tuesday 16 December 2014
H1 ISC
stefan.ballmer@LIGO.ORG - posted 23:37, Tuesday 16 December 2014 - last comment - 23:56, Tuesday 16 December 2014(15662)
High bandwidth BS WFS
Kiwamu, Stefan

Tonight we copied the BS OPLEV filters to the BS M2 LOCK pitch and yaw filters, and modified them slightly to get some moderate DC gain on top of a significant suppression at the optics resonances.
 - The modification we made is
   PIT and YAW: FM1: zpk([0],[100],1,"n") was replaced with zpk([0.1;0.1],[4000;100],0.2,"n") . Together with the WFS filter bank (a simple 1/f integrator) this results in very weak DC feed-back.
   PIT: We added a 1.2Hz resonance peak compensation and a p0.1:z1.5 low frequency boost to FM10:
      zpk([0.02+i*1.2;0.02-i*1.2],[0.200028+i*1.18338;0.200028-i*1.18338],1,"n")* zpk([1.5],[0.1],15,"n")
   The results in a reasonable secondary UGF crossing.

Pitch was tested, and resulted in a unconditionally stable loop.
Yaw wasn't tested yet. A snapshot of the engaged filters is attached.
Images attached to this report
Comments related to this report
stefan.ballmer@LIGO.ORG - 23:56, Tuesday 16 December 2014 (15664)
Also, from this morning's lock, here are some WFS signals that show clearly what is running away.

REFL_B_RF9_I seems to be the prime candidate.

Images attached to this comment
H1 ISC
alexan.staley@LIGO.ORG - posted 22:05, Tuesday 16 December 2014 - last comment - 15:37, Wednesday 17 December 2014(15661)
Sideband Modulation Depth and RFAM
Paul, Sheila, Mackenzie, Alexa
 
We measured the RFAM and the modulation depth for 9 MHz and 45 MHz sidebands. This measurement was previously done by Volker (see alog 3693, 3695).  We followed a similar procedure as explained in our setup alog 15625. During this measurement, the IFR modulation frequency was set to 9.100229 MHz as read from the timing comparator read back.
 

45 MHz RF Input:
12.6dBm out of RF balun on the ISC field racks
3.3dBm into the RF amplifier with -8dB attenuator in the path (with RF power meter).
11.32dBm without the -8dB attenuator (with RF power meter).
21.5 dBm with the -8dB attenuator and with the RF amplifier (with Spectrum analyzer)
3.2dBm into the RF amplifier with -8dB attenuator in the path (with spectrum analyzer).
 
This is consistent with Filiberto's alog 14251 when the RF amplifier was installed.
 
9 MHz RF Input:
17.27dBm measured at the RF balun on the ISC field racks. Based on what we saw for the 45 MHz there might be a 1dBm loss in the cable to the PSL enclosure.
 
Modulation Depth:
With the OSA aligned we found,
 
  RF Input Power Peak Height measured with OSA relative to noise floor Modulation Depth
45 MHz 21.5dBm 79.2mV 0.284
9 MHz 17.27dBm 41.2mV * 0.205
* For the amp of the 9 MHz we had to estimate a bit because the sidebands were laying on the carrier. We estimate that the carrier was about 5.2mV at the peak of the 9 MHz sideband with respect to the noise floor. The 9 MHz sideband peak is then 46.4mV with respect to the noise floor. So the approx 9 MHz sideband is 41.2mV.
 
Meanwhile we measured, the carrier Amp = 3.92 V  with respect to midpoint of noise floor. Similary to alog 8867 we measured the modulation depth using: Gamma = 2*sqrt(V_sideband/V_carrier). The 24 MHz sideband is barely visible. These modulation depths are fairly consistent with what Dan measured using the OMC scan (see alog 14801)

 
RFAM Measurement:
We used an 1811 NewFocus PD (125 MHz Bw) which has a 50 Ohm output impedance for both AC and DC. Our PD is the AC-coupled version the transimpedance gain is 40V/mA (AC) and 1V/mA (DC). So the AC gain is amplified by 40.
DC was connected to a TPS 2024; we measured 28.8mV with high impedance. AC was connected to Agilent 43958 Spectrum Analyzer with a 50 Ohm transimpedance. (Note: this gives another factor of 2 for DC).
Taken from Volker's old alog: the RFAM is then measured via, RFAM = (V_AC/40) / (V_DC/2) where V_AC denotes the Vrms as measured with the spectrum analyzer and V_DC the voltage read from the oscilloscope. The PM value below is the modulation index as measured previously.
 
Spectrum Analyzer peak height for
45.5 MHz = -70.6dBm = 65.99 uVrms, RES BW is 10 Hz, Range is 45.9875 Mhz to 45.50375 MHz (5kHz span)
9.1 MHz = -48.36dBm = 854.05 uVrms, RES BW is 10 Hz, Range is 9.09975 Mhz to 9.1025 MHz (5kHz span)
24 MHz = -98.8dBm = 2.57 uVrms, RES BW is 3 Hz, 24.0784 MHz is the peak which is about center on 5kHz span
 
  RFAM RFAM/PM
45 MHz 1.146e-4 4.0199e-4
9 MHz 1.486e-3 7.233e-3
The RFAM has degrared over time since Volker measured it in 2012 as expected. Kiwamu tells me that these values are still pretty good.
 
Tomorrow we also want to measure the RFAM after the MC. We are all set up to do this on IOT2R, which already has a PD1811 aligned (this just involves blocking the aux beam). Another thing we might consider doing is installing a long cable to the 1811 on the PSL table and send it to a spectrum analyzer outside the enclosure so that we can monitor the RFAM over time. Also, we need an extention for the 1811 PD power cable; at the moment it can't reach the power supply on the floor unless the box is elevated. We did not want to leave the power supply elevated, so at the  moment the 1811 PD is not powered.
 
 
Comments related to this report
daniel.sigg@LIGO.ORG - 10:43, Wednesday 17 December 2014 (15674)

I annotated the scope screenshot from alog 15639 with carrier and sideband frequencies. Just reading off the plot we have

Frequency Amplitude Unit Ratio Γ
Carrier –22.0 dBm 1
–9 MHz sideband –41.0 dBm 0.112 0.226
+9 MHz sideband –41.5 dBm 0.106 0.213
–45 MHz sideband –39.0 dBm 0.141 0.285
+45 MHz sideband –39.5 dBm 0.133 0.269

Taking the average and assuming a 0.5 dB reading error we have Γ = 0.219(12) for the 9 MHz and Γ = 0.277(16) for the 45 MHz sidebands, respectively.

Images attached to this comment
alexan.staley@LIGO.ORG - 14:58, Wednesday 17 December 2014 (15681)

Paul, Mackenzie, Alexa

We measured the RFAM again; this time after the MC (with the PRM misaligned). Paul and Mackenzie had already aligned the beam onto the AC coupled 1811 NewFocus PD on IOT2R (same specs as before). We blocked the auxiliary laser. Again we used a TPS 30324 to measure the DC signal at high impedance, and the Agilent 43958 Spectrum Analyzer to measure the AC signal. We measured 210mV at DC, and

45.5 MHz = -47.5dBm = 942.9 uVrms, RES BW is 10 Hz, 5kHz span
9.1 MHz = -33.4dBm = 4.7086 mVrms, RES BW is 10 Hz, 5kHz span
 
Using the same formula as before RFAM = (V_AC/40)/(V_DC/2), we find:
 
  RFAM RFAM/PM
45 MHz 2.245e-4 6.762e-4
9 MHz 1.121e-3 5.63e-3

The PM represents the modulation depth. We repeated Daniel's calculation but wanted to collect the numbers with the Spectrum Analyzer to reduce the error. So again, we had the aux beam phase locked to the beam on IOT2R. We measured the following:

  Freq Amplitude Ratio Mod Depth
Beat 60 MHz -22.8dBm 1  
+ 45 MHz 105 MHz -37.96dBm 0.174 0.348
+  9 MHz 69 MHz -43.2dBm 0.095 0.19
-9 MHz 51 MHz -42.50dBm 0.104 0.208
-45 MHz 14.5 MHz -38.82dBm 0.158 0.316

Taking the average we find. Gamma_9MHz = 0.199 and Gamma_45MHz = 0.332. This seems a bit high given our previous two measurements. I have used RFAM = 2 * (Vsb/Vcar). There is no sqrt this time because we are measuring the amplitudes; whereas the OSA measured the power. The PD has a BW of 200 MHz, but maybe we are approacing the roll-off. We tried locking the beatnote at a lower frequency so that we would not need to worry about the PD's roll off; however, we had trouble getting a clean lock even at 20 MHz which seemed to be fine yesterday. Paul will attach the raw data.

paul.fulda@LIGO.ORG - 15:37, Wednesday 17 December 2014 (15688)

..and here are the data. It seems like we can even pick out sidebands of sidebands with this measurement technique.

Non-image files attached to this comment
H1 SUS (COC)
betsy.weaver@LIGO.ORG - posted 19:57, Tuesday 16 December 2014 - last comment - 09:53, Wednesday 17 December 2014(15660)
ETMy Test Mass cleaning status

Betsy, Travis, Rick

How today went:

We spent a few hours this morning working on the in-vac side of the new ESD connector termination checkouts. 

At ~2pm we pulled the FC sheet off of the ETMy-HR (painted on last night).  We immediately saw that the 3 larger FC remnants that were causing all of the glint in the cavity arm were removed.  Yay!  However, it was also immediately clear (with the green flashlight) that the 3" ring feature and mottled haze were still there. 

We took a break at 3pm and spoke to a wider SYS+ audience where it was determined we would attempt to do a test drag wipe on the mottling nearer the edge of the optic.  We worked on getting pictures of numerous mottled areas in the haze of the donut shape on the ETMy-HR before doing some test drag wipes.  Then we chose an area toward the top of the optic where there was another relic IAS window circle print near the 12 o'clock position to test drag wiping.  After numerous failed attempts at performing the light-duty friction-only drag wiping technique on this area I resorted to folding the lens wipe a few times and applying pressure during the drag wipe.  This made a smudge where I wiped which I then had to spend another ~5 wipes removing.  We then reevaluated the mottling and found that we might have improved it in one small place, but not the entire area I had been working on.  We then redirected a streaky area at the bottom of the optic to see if I could get a better technique down.  No such luck and I again had to resort to applying pressure numerous times in order to see an improvement.  Since we had better pictures of the 12 o'clock position mottling area that I had been working on earlier, we decided to revisit that area.  I again made an attempt at friction-only drag wiping of this top area.  In the process I must have lightly swiped the optic with my glove because when inspecting the optic after the drag wipe, we found a ~2mmx2mm patch of particulate just outside of the 3" ring near the center of the optic.  Brilliant.  We also found more particulate on the optic from the waving lens tissues.  We tried to blow them off with a few minutes of N2.  This did not seem to work.  One of the particles was quite large and even a light dab with an swab did not move it (in fact, ~5 attempts to snatch it off via dabbing failed).  Rick captured a few pictures of the "new" features.

At this point we aborted the drag wipe testing and carefully repainted FC back on.  I was very careful to not brush across the large particle nor the "patch" area very much.  I applied very thick ~1 inch long strokes which at first were more like dabs near these areas.  (All other saturated sloppy strokes were ~1-2" in length, repeated.)

I do not think we can drag wipe the full surface (or even the central ~8") of the ETMy-HR.  We were not sucessful in ~25 attempts to get a good pull on the optic except for in the localized areas I mentioned above when I used finger pressue.  And after these attempts we added contaminant to the surface by accident.

The optic size obviously makes it hard to work with.  The working area is too small for 2 hands, elbows, flashlights, your head, etc.  Then, the task is too hampered by suspension brackets and braces to get good surface tension with the flat lens tissue.  The wipe wants to continue to pull off the surface and ripples easily.  As well (or worse), we had a hard time getting the wetted wipe to the surface before the acetone dried.

Rick plans to attach some pictures to this alog so check back later or tommorrow.

Comments related to this report
richard.savage@LIGO.ORG - 09:53, Wednesday 17 December 2014 (15668)COC
Some images to supplement Betsy's narrative.  Hopefully the file names are sufficiently descriptive.
For visualizing some of the features, zooming helps a lot.  Look in the elliptical area illuminated by the green flashlight beam.

Filenames, in order, are:

LHOyTopLineBeforeCleaning176.jpg

LHOyTopLineBeforeCleaning185.jpg

LHOyBirdsHeadBrightEdge180.jpg

LHOyDarkBirdsBeak181.jpg

LHOyLongVerticalBrightPatch182.jpg

LHOyGloveTouchPatch186.jpg

LHOyTopLineAfterCleaning190.jpg
Images attached to this comment
H1 AOS (AOS)
douglas.cook@LIGO.ORG - posted 18:01, Tuesday 16 December 2014 (15658)
HAM5 oplvr transceiver mirror misaligned to the point where the return beam is exiting the viewport
 (Doug Jason)
The HAM5 oplvr mirror must have been bumped in situ as we were unable to get the reflected beam out of the viewport to the receiver. It is far enough off that the reflected beam cannot be seen hitting anywhere. We will need to adjust it with the next vent opportunity.
H1 SUS
filiberto.clara@LIGO.ORG - posted 16:34, Tuesday 16 December 2014 - last comment - 07:51, Wednesday 17 December 2014(15656)
ETMY ESD
Betsy, Filiberto, Gerardo, Richard, Travis

1. The old vacuum feedthrough was removed by Gerardo
2. Continuity test were done on each pin to verify each section LR, UR, BIAS, UL, and LL.
3. The in-vacuum cables were re-terminated for installation of the new UHV 5-way coaxial connector.
4. Gerardo installed new feedthru (has not been leaked checked).
5. In-vacuum and in-air cables were connected to feedthru.
6. All pins were HIPOT to 1K and passed (some pins had to be reterminated).
6. Pin layout for ESD is as follow:
   Pin 1 - LR
   Pin 2 - UR
   Pin 3 - BIAS
   Pin 4 - UL
   Pin 5 - LL
Comments related to this report
gerardo.moreno@LIGO.ORG - 07:51, Wednesday 17 December 2014 (15666)
The ESD feedthrough was removed and replaced, flange will need to be leak tested.
Images attached to this comment
LHO VE
kyle.ryan@LIGO.ORG - posted 16:29, Tuesday 16 December 2014 (15655)
1610 hrs. local -> Started purge air compressors at X-end


			
			
H1 SUS (SUS)
peter.king@LIGO.ORG - posted 16:27, Tuesday 16 December 2014 (15654)
ESD Replacement Connector
Fil, Gerardo, Richard, Peter

Attached are 3 photos of the flange that the replacement ESD connectors mate to.  The first image (ESD1.png)
shows some metal shards in the first two pins sockets from the left.  They can be clearly seen in the following
images.

Some of the connections passed the HiPot tester only to sometimes fail when retested.  Some of the connections
that had previously failed, passed.
Images attached to this report
H1 General
jeffrey.bartlett@LIGO.ORG - posted 16:02, Tuesday 16 December 2014 (15653)
Ops Shift Summary
LVEA: Laser Hazard
Observation Bit: Commissioning  

07:00 Karen & Cris – Cleaning in the LVEA
08:01 Kyle – Soft close on GV5 & GV7. Prep work for door removal of HAM1
08:10 Kyle, Gerardo, Bubba – Removing door on HAM1
08:15 Hugh – Working on CS HEPI system
08:20 Hugh – Taking down HEPI pump in LVEA mezzanine to fix leak
08:48 Aaron – Working on PEM power cables in LVEA
08:50 Filiberto – Going to End-Y to prep for ESD cabling 
09:30 Hugh – Finished with HEPI work and out of LVEA 
09:10 Peter – Going into the H2 PSL enclosure to take pictures
09:19 Doug & Jason – Going into the LVEA to prep for HAM5 OpLev check
10:24 Jonathan – Recycling 2F authentication system
10:36 Karen & Cris – Going to End-Y to deliver garb and clean
10:38 Betsy & Travis – Going to End-Y to work on cleaning ETM-Y 
10:40 Filiberto – Going to End-Y
11:00 Add 200ml water to diode room chiller
12:28 Rick – Going to End-Y
13:08 Cris – Going to End-X to restock garb and turn on small cleanrooms
13:08 Karen – Going to End-Y to restock garb
13:30 Betsy, Travis, and Rick – At End-Y cleaning 
13:35 Adjutant on site for repair work for Kyle 
13:48 Sheila, Elli, and Kiwamu – Going into HAM1 to do alignment 
13:54 Dale – Going to HAM1 to take pictures
14:50 Krishna & Fabrice – Going to End-X to work on BRS system
15:23 Travis – Going into the LVEA looking for Acetone
15:30 Rick, Travis, & Betsy – Going back to End-Y for more optics cleaning
15:48 Sheila – Transitioned LVEA to laser safe
   
LHO General
bubba.gateley@LIGO.ORG - posted 15:33, Tuesday 16 December 2014 (15652)
Clean room @ EX
The clean room at EX was turned on at approximately 1400 hrs.
H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 14:27, Tuesday 16 December 2014 (15651)
PSL DBB Scan Results
Ed ran the PSL DBB scans today. The results are posted below.
Non-image files attached to this report
H1 IOO (IOO, ISC, SEI)
sheila.dwyer@LIGO.ORG - posted 12:50, Tuesday 16 December 2014 - last comment - 08:24, Wednesday 17 December 2014(15650)
IMC mystery again

Hugh, Sheila, Stefan, Elli, Kiwamu,

The mysterious IMC misalignment event happened again. We are speculating that there may be a loose optical component in the IMC refl path on the HAM2 in-chamber table.

 


Back in the last February, there was a strange misalignment event in IMC (see alog 10335) where the IMC reflection path seemed to have significantly moved for some reason. This happened again this morning. This time, it was associated with the HAM1 activity of taking the door off from the HAM1 chamber. It tripped the HAM2 ISI and HEPI. After untripping them, we noticed that the IMC reflection was misalgined so much that the beam was almost missing the reflection camera and WFS diodes. However, like the previous event, the IMC power build-up was still reasonably high (it was at 820 counts in MC2 trans which is usually 830 counts or so) when it was locked.  Sheila and Hugh then restored the HEPI back to the previous positions using the IPSs as a reference. At this point we could already see a reasonable DRMI flash at the dark port and also the IM4 trans seemed to have come back to the previous position. Based on these observations, we determined that the misalignment was only in the IMC refl path which is exactly the same conclusion as the previous event. So we realigned the refl path on IOT2L. Now IMC is locking fine and ASC loops were engaged without an issue.

In addition to those recovery activities, we did a brief test where we steered the HEPI by a big amount (~200 urads or so) in each rotational degree of freedom to see if we can reproduce such a big misalignment in the IMC refl, but we could not move the spot on the camera back to the center. Also, we quickly checked the mirrors in the IMC refl path on IOT2L to see if there is a loose component or something easily movable, but we could not find any. The misalignment was mainly in the horizontal direction on the table. The spot position on all three diodes (REFL, WFS_A and WFS_B) had almost the same amount of displacements horizontally, by half a cm toward the East. The attached is 3 hours trend of various sensors. At one point, both the WFSs got misaligned and at the same time the MC1 witness sensors saw a jump in both pitch and yaw (which I think is me untripping the HEPI and ISI).

Images attached to this report
Comments related to this report
hugh.radkins@LIGO.ORG - 08:24, Wednesday 17 December 2014 (15671)SEI

Just to be thorough, I had also taken down the entire corner station HEPI to address a fluid leak.  This took down all HEPIs and most ISIs--maybe the timing here was poor.

Also, "...realigned to the IPS...," we returned the Cartesian positions back to their pre break positions, not the individual IPS values persay.  Still these moves were a few 10s of urads (we ignored the several um of translational shifts.)

Also as a reminder, HEPI only keeps the RZ dof, all others just servo to the free hanging position before the current isolation.  Given the lack of impact of moving the HEPI 100s urads, letting it wander about a few 10s of urads each time it breaks isolation may be reasonable.

H1 PSL
jeffrey.bartlett@LIGO.ORG - posted 11:51, Tuesday 16 December 2014 (15649)
Diode Room Crystal Chiller
Add 200ml water to diode room chiller
H1 ISC (ISC)
paul.fulda@LIGO.ORG - posted 10:48, Tuesday 16 December 2014 (15647)
SRC expected Gouy phases between mirrors

At the request of Stefan, here are the expected Gouy phases accumulated between mirrors in the SRC. I added the results for PRC for good measure. As we expected, almost all the Gouy phase is accumulated between S/PRM and S/PR2. The model these values were calculated from included 34.5km "thermal" lenses in the ITMs, and no ITM substrate non-thermal lenses. The no ITM substrate lenses is probably close to reality, since the CO2 laser was used to match ITMX to ITMY. Probably the +34.5km thermal lens isn't very true right now though. In general if this lens is not present all Gouy phases get smaller, but the relatve fractions accumulated between optics remain pretty similar.

Space Gouy phase x-axis [deg] Gouy phase y-axis [deg]
SRM – SR2

20.53

18.69
SR2 – SR3 

 0.75

0.69

SR3 – BSAR

0.14

0.13

SRC total 

21.42

19.52
PRM – PR2

25.10

23.84

PR2 – PR3

0.97

0.93

PR3 – BSHR

 0.14

0.13

PRC total

26.20

24.91

H1 SEI
jim.warner@LIGO.ORG - posted 10:00, Tuesday 16 December 2014 (15645)
HAM2 & 3 GS-13 coherence with ground seismometer

More sensor correction data. May have posted this before, but I can't find the report. HAM3 shows less coherence with the STS than HAM2. No clue why. If work on the floor stops tripping chambers I'll try to use todays service interruptions for more invasive measurements.

Images attached to this report
H1 ISC
stefan.ballmer@LIGO.ORG - posted 09:38, Tuesday 16 December 2014 - last comment - 09:44, Tuesday 16 December 2014(15643)
9h lock of DRMI
I left the DRMI running last night with the SRC WFS and pointing loop running. We got a 9h lock out of it. But we still have to track down some drift - most likely the recycling cavity, because both 18 and 90 buildups are affected.

Start: 2014/12/16 06:04 UTC
Stop:  2014/12/16 15:41 UTC
Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 09:44, Tuesday 16 December 2014 (15644)

The drift of PR3 yaw OpLev seems to be a likely suspect for the drift in the DRMI build up, the same trend shows up in POP_B_YAW, so this might be a good signal to use to stabilize the PRC axis. 

Images attached to this comment
H1 TCS
eleanor.king@LIGO.ORG - posted 09:31, Tuesday 16 December 2014 (15641)
HWS ITMy beam aligned

HWS ITMy probe beam is reaching the camera.  There is no green beam on the table when this image was taken with the camera.

HWS ITMx beam should be aligned too, I don't have a picture from the ITMx HWS camera yet.

Images attached to this report
H1 ISC
stefan.ballmer@LIGO.ORG - posted 23:25, Monday 15 December 2014 - last comment - 10:24, Tuesday 16 December 2014(15638)
DRMI WFS and alignment work
Alexa, Sheila, Stefan

We made a little bit of progress in DRMI alignment today.

 - First we ran the SRY cavity, and commissioned a pointing loop from the ASC_AS_C quad to SRM and SR2.
 - We used M1 (top mass) actuation because we needed the range, so we switched both SRM and SR2 to MO angular actuation.
 - We then carefully tuned the output matrix such that we don't rely on the WFS to keep SR2 and SRM aligned relative to each other.
 - The output matrix is:
             SRM    SR2
    PIT     -7.08   1.00
    YAW      7.12   1.00
   Note that this matrix will likely change if we switch M2 actuation.
 - Then we successfully used this pointing loop in DRMI, even without any SRC WFS running.
 - The gains were H1:ASC-SRC2_Y_GAIN = 1, H1:ASC-SRC2_P_GAIN = 1, and the input matrix is also 1 (H1:ASC-INMATRIX_P_7_27 and H1:ASC-INMATRIX_Y_7_27).

 - Next we re-phased the AS 36 and AS45 diodes using a freely swinging Michelson. A snapshot of all four diodes is attached.
 - Then we started looking into the SRC WFS again:
 - After many failed trials, we noted that one of the biggest signals for the SRM is AS_A_RF36_Q. But we already used this for the BS.
 - However when driving the BS we found that it has a different demod phase: The BS signal is maximized for the mix
    0.89*I + 0.45*Q (all of AS_A_RF36). The same mix was measured for both PIT and YAW.
   Thus we switched the BS to this mix.
 - Finally, for controlling the SRM, we found two signals: AS_A_RF36_Q from before, and AS_B_RF36_I.
 - Because AS_B_RF36_I is more what I expected, I left the SRM on that one.


Not done yet: 
Adding all this to the Guardian. 


Images attached to this report
Comments related to this report
alexan.staley@LIGO.ORG - 10:24, Tuesday 16 December 2014 (15646)

I added the SRC2 feedback to SRM, SR2 to the "SRM ALIGN" part of the ISC_DOF guardian. These are also in the DRMI guardian now. The SRC1 feedback to SRM is also in the guardian but for now I have left the gain to 0; the old gains are commented out. In the DRMI guardian, "OFFLOAD_DRMI_ASC" now only offloads the PRC, and MICH wfs since its only works for feedback to M2. I have added an "OFFLOAD_SR2_ALIGNMENT" and "OFFLOAD_SRM_ALIGNMENT" which should offload the M1 stages; this was copied over from ISC_DOF guardian and I have not tested it in this configuration.

H1 ISC (IOO)
paul.fulda@LIGO.ORG - posted 23:12, Monday 15 December 2014 - last comment - 11:04, Wednesday 17 December 2014(15639)
Aux laser (re)setup progress

[Mackenzie, Paul]

Yesterday we had trouble getting a large enough beat signal between the aux laser and the main PSL. After discussions with Dave O., Stefan and Daniel, we were convinced that the aux laser was not operating monochromatically. This can apparently occur if the aux laser is close to a "mode hop" region when we bring its frequency close to the PSL frequency using the temperature control. We then end up observing the beat frequency between the PSL and one of the "parasitic" modes of the aux laser, which has a much smaller amplitude than the main mode.

On Daniel's advice, we adjusted the diode input current as well as temperature, in order to give us an additional frequency control option that affected the proximity to the mode hopping region differently to the temperature. After some searching around, we suddenly observed a forest of peaks, with one especially large peak.

This forest appears to have been a combination of a) saturation of the 1811 AC output exciting harmonics of the base beat frequency and b) contributions from RF sidebands of the PSL light. We reduced the power on the 1811 using the filter wheel (we ended up using the OD 2.5 filter), resulting in the spectrum shown in the attached figure. The VCO offset frequency was 20MHz. Interestingly, the beat between aux laser and 9, 45MHz sidebands are quite visible.

The dominant beat frequency now registers a -22dBm signal at the AC PD output on the spectrum analyzer, even with the power on the PD attenuated such that the DC output from the PD produced by the PSL beam is less than 1mV (the PSL beam is the weaker of the two beams at the PD). This may still seem a little weak, but it is much better than yesterday, when we had ~-50dBm AC on a ~100mV DC signal.

After some adjustment of the servo box gains, we were able to achieve stable PLL locks. There is no slow temperature servo path included yet, so the PZT on the aux laser will go out of range rapidly if the temperature dial is not adjusted by hand. By adjusting the temperature dial, it was possible to keep the PLL locked for tens of minutes. 

Next, we switched the frequency reference for the PLL offset from the Marconi VCO to the swept sine output of the network analyzer. This presents a new challenge, because now not only does the aux laser have to phase lock to the PSL, but it also has to track the offset frequency generated by the NA. After playing around with IF BW, sweep ranges, source power etc., we were eventually able to get the aux laser to reliably phase lock to the PSL and track the NA frequency through a ~2MHz frequency range (almost enough for a full PRC sweep). We convinced ourselves that the PLL was locked and tracking the NA frequency by observing the TF from NA drive signal to 1811 AC output. When the PLL is locked, the TF is flat, high, and smooth, since the 1811 AC output is coherent with the NA signal at the same frequency. When the PLL is unlocked, the same TF is many decades smaller.

Each time the NA reaches the end of a sweep and flips back to the start frequency, the lock drops. I'm not sure there's much we can do about that. It would help to have the slow path enabled though, in order to compensate for slow drifts of the aux laser frequency away from the PSL frequency. 

Next we plan to try some PRC sweeps if there is PRMI locked time available. For this, we will take the TF from NA drive signal to one of the REFL AIR broadband detectors, with the PRMI locked and the PLL locked. Depending on how that goes, we may pursue the slow temperature feedback development. 

Images attached to this report
Comments related to this report
daniel.sigg@LIGO.ORG - 16:54, Tuesday 16 December 2014 (15657)

With a subcarrier you can measure the strength of each individual RF sideband---with upper and lower sidebands separated around the VCO frequency. The ratio you see here between RF sideband amplitude and carrier is a direct measurement of the modulation depth.

paul.fulda@LIGO.ORG - 11:04, Wednesday 17 December 2014 (15675)

Great point, what a convenient way to measure the modulation depth! It's also probably a lot more precise that the OSA.

When we get the PLL going again later today I'll save the data from the spectrum analyzer so we can do a more careful analysis.

H1 AOS
suresh.doravari@LIGO.ORG - posted 22:08, Monday 15 December 2014 - last comment - 14:15, Thursday 08 January 2015(15637)
BS Oplev laser replaced: A factor ten improvement in RIN and glitch free operation for over four hours and counting

(Doug C and Suresh D.)

    This afternoon we replaced the glitchy diode laser  (Sl. No. 193) in the BS optical lever with a repaired and thermally stabilised laser (Sl. No. 130-1) which was under observation in HAM3 oplev.     The attached plots show the improved performance due to the repairs and stabilisation.

Things to note:

1) Broadband noise injection into pitch has disappeared after swapping the lasers

2) Constant glitching and consequent broadband injection of noise into yaw signals has disappeared after swapping.

3) The RIN has dropped by an order of magnitude at all frequencies

4) The spectrum is stable and does not oscillate between stable and unstable regimes as the temperature in the LVEA changes due to the airconditioners.

 

Please note that the laser is still approaching a stable operating condition and is under observation for a futher 24 hrs.  However its performance over the past six hours is satisfactory.

Images attached to this report
Comments related to this report
suresh.doravari@LIGO.ORG - 11:04, Tuesday 16 December 2014 (15648)

 

Distinguishing glitch and operator initiated actions in PIT and YAW signals:

 

  We  can distinguish the glitch and operator actions by looking at their spectral signatures.   A glitch would cause a rise in spectral amplitude right across the entire frequency range.  This would then appear as a white line running vertically (across all frequencies) in the spectrogram.  Where as an operator initiated action would have a subsequent suspension damping motion at low frequencies (only). 

   We can see examples of both in the PIT spectrogram.  There are no glitches in the red trace (the spectrogram for that is in bottom panel). This was after about 7PM and folks had already started using the BS oplev for damping.  So their initial alignment efforts show up as small steps with an associated low frequency spectral signature. 


    The blue trace has the classic glitch related signals showing up in pitch.  They can be seen starting at 1.3 hrs and going on till 1.4 hrs.  I dont think anyone was using the IFO at that time.  Since the BS oplev is used for local damping continuously, it is likely that the gliches kicked the optic and caused the activity we see around that time.

  The picture is more messy in the case of YAW as we can see from the blue trace and its associated spectrogram (middle panel).  The yaw signal seems to be continuously affected by the glitching however the event we saw in pitch at 1.3 hrs can also be seen in yaw.  Once again there is no operator related activity in the blue trace while the red trace shows some steps which have an associated low frequency spectral signature (bottom panel).  I concluded that they were associated with the initial alignment activity which was going on at that time.

suresh.doravari@LIGO.ORG - 19:04, Wednesday 17 December 2014 (15699)

I looked at whether the improvement in the laser quality has resulted in an actual improvement in the BS local damping.  There is a tangible improvement in YAW.

 

1) The Spectrogram of YAW motion shows that the injection of broadband noise into the optic motion in YAW due to glitching has disappeared after the swapping of lasers

2) the Coherence between the witness channel and Oplev channel in YAW shows that we can now extend the servo bandwidth to about 10Hz reliably.

3) The spectrum of yaw motion dropped by a factor of two in the range 1 to 20 Hz. This probably has nothing to do with the laser per se.  Probably the pier motion decreased between the two data segments.

Images attached to this comment
suresh.doravari@LIGO.ORG - 17:59, Monday 22 December 2014 (15791)

Performance check after a week of operation

    To see if the laser is still operating safely within the glitch free region, I checked the 1s trend over the past two days.  The laser power has a slow drift of about 1% in a day.  This is probably a LVEA average temperature related effect.   The long term spectrum shows a 1/f shape down to 10^-4 Hz.

And to see the broad band noise I looked at raw signal over the past four hours (256 samples/sec)

The 4hr stretch of raw data spans a period when the oplevs were not used for first 1.4 hour stretch and then were turned on.  We can see the suspension resonances damp in the witness channels.  

The spectrograms show that there is broad band noise in the optic motion, but it is not due to the laser glitching. 

The top panel shows the laser spectrogram and it does not show any broadband noise.

 

Conclusion:

     The laser is performing well, without glitches.   All the action we see in the Pitch and Yaw is associated with either human intervention or lock loss events which have kicked the optic.

Images attached to this comment
evan.hall@LIGO.ORG - 14:15, Thursday 08 January 2015 (15947)

After looking at the oplev spectra with the OL damping loops on and off, I turned down the yaw gain from 650 ct/ct to 500 ct/ct to reduce the amount of extra noise injected between 1 and 10 Hz. The pitch gain is still 300 ct/ct.

In the attached plot, blue is the spectrum without damping, and red is the spectrum with the new damping gain.

Non-image files attached to this comment
Displaying reports 69301-69320 of 84537.Go to page Start 3462 3463 3464 3465 3466 3467 3468 3469 3470 End