Displaying reports 45641-45660 of 88291.Go to page Start 2279 2280 2281 2282 2283 2284 2285 2286 2287 End
Reports until 12:29, Tuesday 11 September 2018
H1 PSL (IOO, PSL)
cheryl.vorvick@LIGO.ORG - posted 12:29, Tuesday 11 September 2018 - last comment - 09:38, Wednesday 12 September 2018(43935)
PSL work today:

At 19:10TUC,  I'd restored the ISS and FSS to locking.  At 19:22UTC, unlocked, Mark and Keita are out making measurements.

Comments related to this report
jason.oberling@LIGO.ORG - 09:38, Wednesday 12 September 2018 (43963)

On 9/3/18, P. King tweaked the mode matching into the 70W amplifier.  As Cheryl says, yesterday I took a beam propagation measurement for mode matching into the PMC.  To give an idea what the beam now looks like, I've attached a picture of the beam profile taken ~695mm from the 70W amplifier.

As there is a power drop somewhere between the 70W amplifier and the PMC, we did a quick a power budget using the water-cooled power meter; all measurements were done with the ISS OFF:

  • Before ISS AOM: 72.7W
  • After ISS AOM: 69.3W
  • After mirror M06: 69.2W
  • Before PMC: 69.3W
  • PMC Trans: 50.9W

The largest power loss is at the ISS AOM, where we lose 3.4W.  We had suspected clipping at this AOM, and it looks like that is the case.  We will have to re-think our PMC mode matching scheme to get the beam smaller at the ISS AOM.

With the 70W beam looking better, I wanted to get an idea of where we are now in regards to PMC mode matching.  Without changing the mode matching scheme for the PMC, I took a quick measurement of the PMC visibility using the locked and unlocked voltage from the PMC locking PD.  This was also done with the ISS OFF:

  • Unlocked: -0.151V
  • Locked: -0.026V
  • Visibility: 82.8%

Simply by cleaning up the 70W beam (via Peter's 70W amp mode matching tweak), we are at >80% visibility.  This is, however, somewhat disconcerting.  Looking at the above power budget, we are only transmitting ~73% of the power incident on the PMC, so something isn't quite adding up here.  Something to think about before next Tuesday.

Images attached to this comment
H1 CDS (GRD)
thomas.shaffer@LIGO.ORG - posted 12:02, Tuesday 11 September 2018 (43933)
h1guardian1 rebooted

The h1guardian1 machine had been up for 125 days (May9th), so we tried a reboot today during maintenance. The few issues that came up:

H1 CDS
david.barker@LIGO.ORG - posted 11:32, Tuesday 11 September 2018 (43932)
h1iscey models restarted following IO Chassis timing glitch

During cable work in the EY CER, the timing to the h1iscey IO Chassis was glitched. I recovered the system by performing a complete power cycle of h1iscey and its chassis. There was a brief negative IRIG-B excursion following the IOP restart.

LHO General
corey.gray@LIGO.ORG - posted 08:05, Tuesday 11 September 2018 (43927)
Morning Status: Tues Maintenance!

TITLE: 09/11 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 6mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.14 μm/s
QUICK SUMMARY:

 

H1 ISC
sheila.dwyer@LIGO.ORG - posted 23:16, Monday 10 September 2018 (43926)
locking this afternoon, quick check of yaw actuator balancing

Locking with higher recycling gain:

Hang Georgia and I spent some time on the steps in the guardian in CARM_5_picometers, similar to what we did a few weeks ago after an increase in recycling gain (43787).  We mainly adjusted the CARM offsets at which things happen: The step where we digitally increase the CARM gain (LSC-REFLBIAS) and engage the boost is at 65% of the ARM cavity build up, which now means a TR_CARM offset of -48, while the transition to the REFL9 happens at 85% of the arm cavity build up as before (now TR_CARM offset = -54).  This has made the build ups more stable during these last steps of the transition and we have succeeded both times we have tried since making the changes.   The TR_REFL 9 input matrix element is now 2, where it used to be 3.

In DRMI on POP, Hang adjusted teh DRMI gains by changing the input matrix.  The MICH ugf is around 9 Hz (as it has been) SRCL is around 40 Hz (it was 60 Hz earlier today), and PRCL is around 50 Hz (was around 30 Hz earlier today).   

In the last few locking attempts we have locked with the ASC error signals close enough to zero that we could engage the ASC loops without any problems, although I know that was not true earlier in the day.  I'm not sure if people reset alignment references.  

HARD Y loops:

In alog 27832 Jenne shows some measurement of HARD yaw loops that do not have the non minimum phase feature that has been bothering us.  

Hang and I re-ran Gabriele's template for measuing CHARD Y, and see that the spot centering efforts haven't changed that feature much.  We also saw that DHARD Y is fairly cross coupled to the CHARD, you can see that our CHARD excitation shows up in the DHARD error signal about a factor of 3 smaller than in the CHARD error signal. 

I sent a line at 8.1 Hz to both ITMs, and adjusted the output matrix to minimize the signal in DHARD Y, I found that I needed a gain of 1.07 in ITMX (with 1 for ITMY) to balance them.  I tried the same for the ETMs, but they were closer to balanced.  I changed the output matrix element for CHARD and DHARD Y to ITMX to see if this would have any impact on the transfer function or the cross coupling to DHARD, but it didn't have much of an impact. 

Leaving IFO locked

I am leaving the IFO locked at DC readout with 2 W input power, a2L is running.  I used the guardian to engage violin mode damping, it is damping 7 modes on each test mass, and they all seem to be fine. 

 

Images attached to this report
LHO VE
kyle.ryan@LIGO.ORG - posted 20:43, Monday 10 September 2018 (43925)
~1730 hrs. local -> spun up Vertex, XBM and YBM turbo pumps in LVEA

Prep. for leak testing tomorrow

H1 SEI (SQZ)
haocun.yu@LIGO.ORG - posted 20:28, Monday 10 September 2018 - last comment - 12:21, Tuesday 11 September 2018(43924)
OPO Cavity Scan Polarization

[Sheila, Nutsinee, Terry, Haocun]

We looked into more of the cavity scan of the OPO, especially on the polarization issue.

Several main conclusions are:

1. We looked into SHG_FIBER_REJECTED and the ratio between OPO_REFL_REJECTED and OPO_REFL under different green power input.

The wrong polarization increased linearly with the ratio remains the same, which means the polarizer on the VOPO platform does work well. (Fig attached 1)

We have a ~7% of power wrong polarization coming out from OPO as measured on SQZT6.    

2. I tried to minimize the wrong polarization ratio by tweaking the waveplates before the input coupler on ISCT6, but unfortunately this helped little by only getting a changing of ~0.1%.

3. We have a polarization mode very close to our 00 mode (~MHz spacing, I will do more precise calculation) (Attachment 2, zoom-in plot 3). This can been seen by comparing the opo trans lining up with rejected.

Not sure yet whether and how this will effect the error signal, etc. 

 

Next steps:

- Modeling of the error signal asymmetry based on PDH and scan asymmetry with thermal expansion.

- Install PBS in OPO Trans path to have a clearer idea on the polarization mode.

- Maybe: tweaking the crystal postilion to see whether we can separate the polarization mode further?

Images attached to this report
Comments related to this report
nutsinee.kijbunchoo@LIGO.ORG - 12:21, Tuesday 11 September 2018 (43930)SQZ

Additional note to what happened yesterday. I think we're close to understand what the heck is going on here.

CR/SB

The modeled carrier/sideband RF power ratio is ~2. The plot was modeled and compared with a scan at low power. The measured CR/SB RF power ratio was 1.96. Not too far off. 

(ignore the y-axis lable. It should be scope Volt).

 

Attenuator vs. no attenuator

In case we're saturating the diode at RF Sheila suggested we compared signal with and without an attenuator. The plot below shows the scan from the same green input power, with ND=1 filter and without.

There was much improvement in the error signal with DN1 filter on.  

For your amusement here's an IQ plot from data with ND filter. I don't have a nice IQ plot from no-filter because I-mon data was so blocky.

 

So in summary, we might've been dealing with three problems on top of one another:

1) Thermal heating (modeling work on-going)

2) RF saturation (fixed-ish. If we decided ND1 is a good one to have then I'd call that fixed.)

3) Polarization peak inside the carrier. Terry calculated this peak to be about a 1MHz away from the carrier. -- This distorted our error signal on the left hand side

 

Judging by the error signal with ND filter on I think the locking issue is mitigated. I haven't tried locking with ND filter in front of the refl yet but the error signal looks linear around transmission peak and crosses zero. 

Images attached to this comment
haocun.yu@LIGO.ORG - 12:14, Tuesday 11 September 2018 (43934)

The "polarization peak" is about 0.02~0.03FSR from the 00 mode, or ~30MHz seperation calculated from the plot.

H1 IOO (IOO, PSL)
cheryl.vorvick@LIGO.ORG - posted 17:24, Monday 10 September 2018 (43922)
PMC heater power change steers the Main PSL beam, and others.

I looked around at signals on the PSL and in the IO path, and found two things.  The first, which is probably unremarkable, is that when the RefCav Trans PD went to 0, the ISS QPD, and IO GigiE cameras don't see a change in the beam alignment.  The second is that when the PMC heater power changed, going from 30 to 60, that change steered the beams coming out of the PMC, as seen on the ISS QPD, and IO GigiE cameras.

Many plots, but the first and last give the most pertinent information. 

Images attached to this report
LHO General (DetChar)
corey.gray@LIGO.ORG - posted 16:00, Monday 10 September 2018 (43917)
Ops Day Shift Summary

TITLE: 09/10 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    Wind: 5mph Gusts, 3mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.19 μm/s 
QUICK SUMMARY:

Commissioners busy working on H1.  The PSL issues weren't observed in the morning, but appeared to go away after a FSS VCO power cycle by Keita.

LHO General
corey.gray@LIGO.ORG - posted 11:12, Monday 10 September 2018 (43915)
Monday Coordination Meeting Notes

Announcement:  Fire late Fri night w/ water pump alarms following.

- If any one sees a fire, let Jeff Jones know, so they can address regarding operations.  One can call 911, or non-emergency number, which is listed in our phone roster.

Commissioning: 

Tues Maint

Other Items:

H1 CDS (PEM)
david.barker@LIGO.ORG - posted 10:59, Monday 10 September 2018 (43914)
MY weather station restart after lightening glitch Friday night

The MY weather station stopped reporting at 23:16 PDT Friday 7th September. This matches the time this area was hit with lightening. I restarted the code and the weather station is reporting again.

H1 IOO (IOO, PSL)
richard.savage@LIGO.ORG - posted 08:24, Monday 10 September 2018 - last comment - 10:35, Monday 10 September 2018(43906)
IMC now locking (FSS issues appears to have

Quick update.

First thing this morning, when preparing to address the FSS not locking issue, we found that the IMC was locked and the PSL status appears to be nominal, at least the FSS.  The ISS was not locked but acquired quickly when the loop was enabled.

GabrieleV is investigating and pressing ahead with trying to lock the ifo.

Comments related to this report
jeffrey.kissel@LIGO.ORG - 10:35, Monday 10 September 2018 (43913)IOO, ISC, PSL
Associated with FRS Ticket 11427
H1 PSL (ISC, PSL)
craig.cahillane@LIGO.ORG - posted 01:41, Sunday 09 September 2018 - last comment - 18:47, Tuesday 11 September 2018(43896)
Unable to lock FSS
At around Sep 09 2018 07:10:53 UTC (GPS 1220512271), the IMC and FSS lost lock.  I was unable to recover the FSS.

The FSS is railed at about 11.9 volts.  I can move this value around by turning off the autolocker and moving around the common and fast gain sliders, but as soon as I reengage the autolocker it rails again.
The laser crystal temp at the time of the unlocking was 0.31 K.  I tried manually setting the temperature there, but the PZT just is not responding, and every time I ask it for control it rails to 11 V.

I pressed pretty much every button and shook every slider on the PSL_FSS medm screens.  I don't know what else to do from the control room.  My uninformed opinion is that somehow the PZT lost it's lower DC power rail, since it always rails positively.
However, I can get the Fast monitor to read negatively if I disengage the autolocker, turn on the "mode loop" (no idea what that is), and turn up the fast gain (Picture 2 below), so I'm not sure what's actually going on.

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 12:23, Sunday 09 September 2018 (43899)

There is no DC response from the FSS refl PD. The value on the REFL PD doesn't change when the PMC is locked or unlocked, however I can see that the diode did show a higher level of reflected light during a time when the FSS was unlocked last Tuesday.  

In the second attached screenshot you can see that as I have locked and unlocked the RFPD over the last hour or so there has been no response on the FSS PD. 

Another issue that is confusing is that the PMC sometimes reports that it is locked when it is not.  The PMC medm screen has a misleading statement that the PMC is resonant if H1:PSL-PMC_MIN_TRIGGER < H1:PSL-PMC_TRIGGER_OUTPUT < H1:PSL-PMC_REF

Looking in the PMC model this is unrelated to the logic that goes into the flag H1:PSL-PMC_RESONANT, which is missing from the medm screen.  

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 07:29, Monday 10 September 2018 (43905)FRS, ISC, SYS
Corresponds to FRS Ticket 11427.
keita.kawabe@LIGO.ORG - 12:52, Monday 10 September 2018 (43919)CDS, ISC, PSL

It's IMC VCO failure.

See the first attachment, at some point IMC VCO failed and eventually came back.

No VCO output = no diffracted light into RefCav.

That's the reason why there was no response from FSS DC diodes even though Sheila locked/unlocked PMC.

Reference input of IMC VCO is taken off of an RF amp and 8-way splitter (D1000124) that is also used for COMM and DIFF which were OK (indeed everything except IMC VCO was OK, see 2nd attachment), so this cannot be the amplifier problem, it should be VCO itself or the cable connecting the splitter and VCO.

It happened again at about 11:50 AM (or 18:50 UTC).

See the third plot. This time I went to the floor and wanted to power cycle VCO, but since it doesn't have a convenient power switch I disconnected the reference input cable (that's where VCO OUTPUTMON dropped from -10 to -34dB). After playing around with it,  swapping cables with one of ALS VCOs and such, I couldn't find anything wrong, reconnected everything back, and it seems to be working OK for now. 

I cannot tell if this is an electronics or a shoddy connection or shoddy cable/attenuator.

Images attached to this comment
keita.kawabe@LIGO.ORG - 14:01, Monday 10 September 2018 (43920)

IMC VCO showed this behavior 5 times (counting today/yesterday as one) in the past 4 months where the output intermittently dropped to -10dBm.

I also plotted COMM VCO output, you might think something happened to COMM too for #3 and #4, but it's actually not the case (2nd and 3rd attached).

Images attached to this comment
keita.kawabe@LIGO.ORG - 14:17, Monday 10 September 2018 (43921)

I've found the FSS auto locker parameters totally out of whack.

Oscillation threshold of 3 doesn't make sense, even when it's oscillating I don't think H1:PSL-FSS_PC_PP goes above 3. I manually set it back to 0.6.

State transition delays of [delay1, 2, 3]=[10, 10, 10] sec don't make sense either. The servo is first turned on with low gain after the refcav is brought close to resonance for delay1 sec. Then wait for delay2 and the common gain is ramped. Then wait for delay3 and the temperature loop is turned on. I manually changed them back to [0.1, 1, 0.1].

Images attached to this comment
marc.pirello@LIGO.ORG - 14:55, Tuesday 11 September 2018 (43937)

I pulled the PSL-VCO (S1200558) and performed some testing on it today.  Power checks out, tuning checks out, monitors work, I was unable to compete the phase noise test before noon.  I checked the attenuators and the REF cable, these passed as well.  I changed the REF cable position on the RF Amplifier Splitter from position 5 to position 7. 

Based on Keita's trending, REFERENCEMON drops out, this would cause OUTPUTMON to drop out as well and it does.  DIVIDERMON does not drop out all the way, curiously.  The power OK signal was good throughout these incidents, the intermittent fault is not likely power related.

Looking at the past 4 months behavior posted by Keita above, the glitching seems to be periodic, and when I zoomed in most of this glitching is happening on Tuesdays before noon.

5 = Tuesday June 12, 11 AM

4 = Tuesday June 24, 11 AM

3 = Tuesday July 31, 8 AM

2 = Thursday August 16, 9 AM

keita.kawabe@LIGO.ORG - 18:47, Tuesday 11 September 2018 (43952)

So it misbehaved when somebody worked near the rack. Maybe poor connection at the connector (too little or too much torque?) combined with poor strain relief.

H1 ISC
gabriele.vajente@LIGO.ORG - posted 19:18, Saturday 08 September 2018 - last comment - 09:24, Wednesday 12 September 2018(43895)
Recycling gain is now 47.4

[Hang, Craig, Gabriele]

Summary

We moved PR3, PRM and the soft degrees of freedom to improve the beam centering on all four test masses and increase the recycling gain.

We started with a recycling gain of about 38.2 and finished with a recycling gain of 47.4 [+24%]

A lock loss terminated our work, so there is still some re-alignment to do to get the test masses centered. And there might be more recycling gain.

 

We added dithering lines in yaw to all four test masses, and we could improve the centering significantly. At the end all Y2L coefficients are zero, and the dithering signals are quite close to zero. The two ITMs are reasonably centered, as is ETMX. Instead ETMY seems to have a larger mis-centering.

If we need to put back the Y2L coefficients, we probably only need to set ETMY to about 4.

Details

We finally lost lock after more than 6h continuous lock.

 

Images attached to this report
Comments related to this report
peter.fritschel@LIGO.ORG - 06:04, Sunday 09 September 2018 (43897)

Wow, very impressive. Hiro's simulations (G1700140) gave a PRG of only 39, though that was including an ad-hoc loss per arm of 50 ppm.

jenne.driggers@LIGO.ORG - 11:33, Sunday 09 September 2018 (43898)

This is awesome! 

Our PR gain is POP_A_LF / IM4_TRANS_SUM with calibrations to take into account reflectivity branching ratios, but we're quite close to the edge of IM4 trans.  I think our normalized yaw number is more than 0.8.  (We haven't pico'ed yet, to keep an alignment reference, but I think it might be about time to pico and say that this is better than O2.)  I'm suspicious that our PR numbers that we've been reporting might be systematically high, if the number we're dividing by is smaller than the total actual amount of power in transmission of IM4. 

That said, this has been true since our vent recovery (and also to a lesser extent during O2), so the +24% is certainly real, but the absolute values we've been reporting for PR gain might be high.  We should pico and check the calibrations to be sure.

sheila.dwyer@LIGO.ORG - 12:36, Sunday 09 September 2018 (43900)

Looking at TR_X_NORM and TR_Y_NORM (which are normalized so that the single arm build ups are 1, at the time of the best recycling gain the build ups were 1646 and 1732 relative to the single arm, which would indicate a recycling gain of 45.  Gabriele pointed out that the reflectivity of PRM is 3.1% according to galaxy, which means that this gives a recycling gain of 53.0

Another option for estimating the circulating power would be to try this method which has been done at LLO: 36745

jeffrey.kissel@LIGO.ORG - 13:15, Sunday 09 September 2018 (43902)COC, SYS
WOW! Amazing!! Congratulations!!
gabriele.vajente@LIGO.ORG - 14:03, Sunday 09 September 2018 (43903)

Here's a quick computation of the power recycling gain as a function of the round trip losses in the arm (in ppm, sorry I forgot the units in the plot), assuming Tprm = 3.1%.

The two marked points correspond to the values of recycling gain estimated with POP_LF and with the arm transmission.

 

Images attached to this comment
gabriele.vajente@LIGO.ORG - 09:17, Monday 10 September 2018 (43909)

Dark offsets for TR_X and TR_Y are not very well set. The table below shows the TR values in different configurations, and the corresponding estimated recycling gain. Taking into account the dark offsets now the X and Y arm transmission give consistent recycling gains.

  Dark Single arm Full IFO Recycling gain
X 0.045 1.00 1648 53.5
Y -0.007 0.98 1736 54.5

 

valery.frolov@LIGO.ORG - 09:25, Monday 10 September 2018 (43910)
The REFL_A_LF also goes up by about 5% (relative to unlocked so it measures the ifo reflectivity) as expected. Great job!
gabriele.vajente@LIGO.ORG - 16:44, Monday 10 September 2018 (43923)

From the level of reflected power (w.r.t. the off resonance state) we can estimate again the round trip losses.

The plot below shows that the REFL level we measured after re-aligning (8.3%) corresponds to about 61 ppm round trip losses, and a recycling gain of 53.4, which is very close to the recycling gain we can estimate from the arm power buildup.

 

Images attached to this comment
georgia.mansell@LIGO.ORG - 19:08, Tuesday 11 September 2018 (43953)

The recycling gain improvement is seen in the CARM offset reduction sequence too. I ran the script that Sheila and Gabriele posted in alog-43344 on data from yesterday (starting at t = 1220674303).

This plots the reflected power (normalised) vs the arm build up (transmission normalised to a single arm). As we step through the CARM offset reduction, the TR_X increases and the REFL_DC decreases. The slope is an indication of the power recycling gain.

As of yesterday we're going better than the previous measurements, including compared to O1.

Images attached to this comment
gabriele.vajente@LIGO.ORG - 09:24, Wednesday 12 September 2018 (43965)

In addition to Georgia's analysis, here is a similar plot, with also some fit lines. The new curve is again consistent with no losses in the PRC and arm round-trip losses of about 66 ppm.

 

Images attached to this comment
H1 ISC (ISC)
craig.cahillane@LIGO.ORG - posted 00:11, Saturday 08 September 2018 - last comment - 11:21, Thursday 13 September 2018(43881)
FSS_OSCILLATION has an oscillation...
(In this post I mean "railing" as "parked at the maximum actuation range", where "oscillation" means "PZT is fighting the EOM")

The FSS Fast Path has been railing recently, preventing the FSS from locking.  (Pic 1)

It seems as though FSS_OSCILLATION does not in fact monitor the FSS RMS, but triggers on a threshold.  When the FSS voltage would pass a certain value, the PSL_FSS guardian would send it to state FSS_OSCILLATING.
This state brings the common gain down to -10 dB, then slowly back up to wherever it started.  This works great for stopping oscillations, but not for permanent rails.

I modified the PSL_FSS code to increase the oscillation threshold from 0.6 to 3 V for five seconds whenever the fast voltage is railed at greater than 10 volts with extremely low RMS.  This should allow the FSS loop to close and bring the temperature within range.  Railing hasn't happened again, so I haven't had a chance to test the state, but it does still suppress actual oscillations.
Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 11:31, Saturday 08 September 2018 (43891)

[Hang Gabriele]

There might be some problem with the logic of the FSS_OSCILLATION state. This morning the guardian was continuously reducing the gain to -10 db, and then ramping it up to more than +100 db. Our guess is that the self.high_gain variable which is set in the main() function got a wrong, large value. Maybe we should hard code a gain of 20 db there?

We fix the problem by stopping the guardian, setting the FSS common gain to 20 db and restarting the guardian.

hang.yu@LIGO.ORG - 12:47, Saturday 08 September 2018 (43893)

For now we hacked the PSL_FSS guardian the FSS_OSCILLATING state so that the FSS_COMMON_GAIN could not exceed 20 dB. We could thus lock the IMC without needing to manually pause the PSL every time. 

Specifically, we modified the original

if not ezca['FSS_OSCILLATION'] or not ezca['FSS_RESONANT']

into:

if (not ezca['FSS_OSCILLATION'] or not ezca['FSS_RESONANT']) and (ezca['FSS_COMMON_GAIN']<20.)

keita.kawabe@LIGO.ORG - 11:38, Monday 10 September 2018 (43916)

H1:PSL-FSS_OSCILLATION is set whenever H1:PSL-FSS_PC_PP exceeds the threshold.

jason.oberling@LIGO.ORG - 14:36, Wednesday 12 September 2018 (43971)

More info in alog 43970.

keita.kawabe@LIGO.ORG - 11:21, Thursday 13 September 2018 (43989)

Above comment of mine, "H1:PSL-FSS_OSCILLATION is set whenever H1:PSL-FSS_PC_PP exceeds the threshold.", is totally false, see Jason's alog.

H1 SUS
sheila.dwyer@LIGO.ORG - posted 14:58, Tuesday 04 September 2018 - last comment - 12:27, Monday 10 September 2018(43816)
ITMY optical lever calibration was wrong by about a factor of 2

We've had two measurements which suggest ITMY actuation is weaker than it should be, (Georgia's measurement of the ITM ESD actuation strengths 42315 and 42302 and Gabriele's measurement of the ASC actuators 43797), so I have double checked the optical lever calibration. 

I found a time in the past when (August 13th at 21:22 to 21:25 UTC) we ran the script that adjusts the alignment of the ITM by pointing the green beam onto the EMT baffle PD's. 

The optical lever indicates a 16.5 urad change in ITM pitch between the time when the beam hits PD1 and PD4, and a 14.1 urad change in yaw.  

According to the drawing that Keita and Gerardo put together, 9087, the ITM pitch difference between pointing to the two diodes should be 11.76''/4km/2 = 37.2 urad pitch and 37.4 urad for yaw.  

This means that our current calibrations (pit gain = 23.9 yaw gain = 24.0) are too small by 2.25 for pit and 2.65 for yaw. 

I have not attempted to check the slider calibration since people are locking the interferometer right now. 

The calibration has not changed since October 5th 2014, and this is the closest alog I can find: 14312

 

Comments related to this report
keita.kawabe@LIGO.ORG - 11:19, Wednesday 05 September 2018 (43833)

Summary:

Now OL PIT and YAW agree with M0 PIT and YAW sliders within 10%-ish, so everything is sane now.

I confirmed that the whitening was OK.

I see that OL beam size on the OL diode for IY is much bigger than IX though it's not clear how long this has been the case. This explains why IY OL has a smaller sensitivity and thus needs larger digital gain.

It seems like either IY OL calibration was off from the start or the OL beam size changed at some point.

What I did:

1. Moved M0 PIT and YAW sliders and confirmed that OL reasonably agrees with the sliders (1st attachment).

2. Misaligned ITMY so the output of OL SEG1 is maximized, then SEG4, SEG2, SEG3, each time looking at the spectrum.

Maximized segments look all similar (except f>1kHz), which it should be as this is dominated by the intensity noise. This means that whitening is OK. (2nd attachment).

3. Also looked at DC and saw that the beam is larger than the segment.

When a segment output is maximized, the output is ~16.3k regardless of which one is maximized (attachment 3, SEG1 was maximized here).

When OL is centered, SUM is about 30.4k, so each segment can accommodate only slightly more than 50% of the entire beam at best.

Dark offsets are negligible (~>10 counts).

4: ITMX OL beam is smaller than ITMY.

When SEG1 of ITMX oplev (not ITMY) was maximized it was ~24.4k (4th attachment) while, when OL is centered, SUM is about 27.6k, so this is about 90% of the entire beam contained in one segment.

Apparently OL beam is smaller on ITMX OL diode than on ITMY, which explains why the OL sensitivity is smaller for ITMY now.

Images attached to this comment
jeffrey.kissel@LIGO.ORG - 12:27, Monday 10 September 2018 (43918)
I've accepted the changes to the ITMY optical lever calibration into the SDF system. See attached screenshot.
Images attached to this comment
Displaying reports 45641-45660 of 88291.Go to page Start 2279 2280 2281 2282 2283 2284 2285 2286 2287 End