Displaying reports 2321-2340 of 77273.Go to page Start 113 114 115 116 117 118 119 120 121 End
Reports until 10:39, Tuesday 16 April 2024
H1 CDS
david.barker@LIGO.ORG - posted 10:39, Tuesday 16 April 2024 - last comment - 12:56, Wednesday 17 April 2024(77207)
h1calcs, cal_hash_ioc and DAQ restarts

WP11812

Jamie, Jonathan, Erik, Dave:

The two CAL HASH channels (H1:CAL-CALIB_REPORT_HASH_INT and H1:CAL-CALIB_REPORT_ID_INT) were moved from the h1calcs model, where they were being acquired as single-precision floats, to a new custom EPICS IOC called cal_hash_ioc, where they are acquired as signed 32bit integers.

The h1calcs.mdl model was modified to remove the EPICS-INPUT parts for these channels. The model was then restarted.

The IOC, which was being tested with H3 channels, was modifed and rstarted to serve the H1 channels as integers.

The EDC was modified to add H1EPICS_CALHASH.ini to its master list. This added 5 channels the the DAQ, the two hash channels and three IOC status channels.

The EDC was restarted, followed in short order by a DAQ restart.

Comments related to this report
david.barker@LIGO.ORG - 13:31, Tuesday 16 April 2024 (77212)

Tue16Apr2024         
LOC TIME HOSTNAME     MODEL/REBOOT 
10:04:52 h1oaf0       h1calcs <<< Model change to remove channels
10:07:51 h1susauxb123 h1edc[DAQ]  <<< EDC has the new channels
10:08:43 h1daqdc0     [DAQ] <<< 0-leg restart, no issues
10:08:55 h1daqfw0     [DAQ]
10:08:55 h1daqnds0    [DAQ]
10:08:55 h1daqtw0     [DAQ] 
10:09:03 h1daqgds0    [DAQ]
10:11:55 h1daqdc1     [DAQ] <<< 1-leg restart, no issues
10:12:06 h1daqfw1     [DAQ]
10:12:07 h1daqtw1     [DAQ]
10:12:08 h1daqnds1    [DAQ] 
10:12:16 h1daqgds1    [DAQ] 

oli.patane@LIGO.ORG - 16:16, Tuesday 16 April 2024 (77222)
Images attached to this comment
louis.dartez@LIGO.ORG - 12:56, Wednesday 17 April 2024 (77250)
N.B. that changes to the channels H1:CAL-CALIB_REPORT_HASH_INT and H1:CAL-CALIB_REPORT_ID_INT will appear on the CDS SDF screen, *not the H1CALCS* screen. They get automatically re-populated each time pydarm export is used to update the calibration in the control room (which should be considered to happen atomically with GDS restarts). So, when updating the calibration both the H1CALCS and the H1CDS SDF screens need to be checked.
LHO VE
david.barker@LIGO.ORG - posted 10:21, Tuesday 16 April 2024 (77206)
Tue CP1 Fill

Tue Apr 16 10:12:16 2024 INFO: Fill completed in 12min 11secs

Jordan confirmed a good fill curbside. Plot looks strange because the DAQ was being restarted during the fill.

Images attached to this report
H1 IOO
sheila.dwyer@LIGO.ORG - posted 10:08, Tuesday 16 April 2024 (77205)
IM4 QPD centered with pico

I used the IM4 pico to center the beam on the QPD with 2W into the mode cleaner this morning (screenshot attached). We had some shifts of input alignment during the vent and difficulty recovering (see 76359 76291).  Now our range is 165 and locking seems reliable, so we are resetting the IM4 QPD to zero here so that we can use this as a reference in the future.  LLO tells us that they realign IM3 to this QPD every few months.

This increased the sum of IM4.  Since this sum is used to normalize our PRG channel, this will need a recalibration.

Images attached to this report
H1 ISC
gabriele.vajente@LIGO.ORG - posted 08:25, Tuesday 16 April 2024 - last comment - 09:40, Wednesday 17 April 2024(77201)
Why is it so hard to fit a good SRCL FF?

Lately it's been very difficult to fit an efficient SRCL feedforward filter, as reported many times by Camilla et al. (76993). Here I'm trying to figure out why. Spoiler alert: I don't have an answer yet.

The main problem with the SRCL FF filter (see first plot), is that the transfer function to fit has a large phase rotation, that looks basically like a phase advance (the opposite of a delay) of about 2 ms. This is very large, and being an advance, it can't be realized in a precise and simple wasy digitally.

First observation: we can fit a pretty good SRCL FF if we allow for unstable poles, i.e. poles with positive real parts (see second plot) Of course this is not something that can be implemented in the real time system. The fit ends up having a unstable complex pole at about 420 Hz and about 5 Hz. I have no intepretation for the origin of those poles, and they might very well be only a way to reproduce a phase advance (think of the Padé approximation for phase delays).

So the question is: what is the origin of this large phase rotation? It's not seen at LLO, for example see 70548

Second observation: this phase advance appeared after we switched the LSC FF from ETMX (full chain) to ETMY PUM. The third plot compares the MICH and SRCL feedforward to be fit in two cases: an old measurement when the FF was going to ETMX, and a more recent measurement with the FF going to ETMY PUM only. For both MICH and SRCL the orange traces (FF to ETMY) show a phase advanced with respect to the blue traces (FF to ETMX). For some reasons I don't fully understand, this rotation is more problematic for SRCL than for MICH, although fitting MICH has also been more difficult and the MICH FF is relevant at lower frequencies than SRCL, so maybe the phase advanced isn't that problematic.

Looking at the measurement of the MICHFF to DARM and SRCLFF to DARM, one can see that there seems to be an additional phase delay in the FF path through ETMY PUM with respect to the FF path through ETMX full chain. Since this transfer function is at the denominator when computing the ratio SRCLtoDARM/SRCLFFtoDARM that gives use the LSC FF to fit, this seems to explain the additional phase advance we observe.

The ETMY PUM L2 lock filter bank contains a "QPrime" filter module that compensates partially the additional 1/f^2 due to the actuation from L2 instead of L3. This filter however doesn't seem able to explain this additonal phase delay.

I'm now suspicious that there might be something wrong or mistuned in the ETMY L2 drive, maybe a whitening filter missing or not functioning properly or not properly compensated?

It would be worth doing a quick test in the next commissioning time with full IFO locked: inject some white noise on ETMX L2 L and ETMY L2 L and comapre the two transfer functions to DARM. In theory they should be equal, except for a sign difference. If they're not, then there must be something wrong with ETMY, since we're using ETMX L2 to lock without issues.

Images attached to this report
Comments related to this report
gabriele.vajente@LIGO.ORG - 14:35, Tuesday 16 April 2024 (77215)

This is a comparison of the LHO LSC FF and LLO LSC FF. The difference in the absolute scale might eb due to normalizations, but the SRCL FF does not show the large phase advanced visible at LHO

Images attached to this comment
gabriele.vajente@LIGO.ORG - 07:28, Wednesday 17 April 2024 (77236)

Maybe mistery solved...

The ETMY L2 DRIVEALIGN L filter bank has a "L2L3LP" filter engaged, whiel the corresponding ETMX L2 DRIVEALIGN L filter bank does not. This filter seems to be the origin of the phase rotation. At least it explains part of the phase rotation.

Anybody knows why this filter is engaged in ETMY? Should be turn it off and retune the LSC FF?

We should turn this filter off when we engage the FF (assuming it's needed some time during lock acquistion, to be checked) and retune the LSC FF. When we do that, we should reduce the excitation amplitude and reshape it, taking into account the filter we turned off.

Images attached to this comment
camilla.compton@LIGO.ORG - 09:40, Wednesday 17 April 2024 (77240)

Gabriele, Camilla. This ETMY_L2_DRIVEALIGN_L2L filter is used while locking in TRANSISTION_FROM_ETMX (when we control DARM on EY)  and then again when the LSC FF is turned on in LOW_NOISE_LENGTH_CONTORL, plot attached. To not need to change the sensitive TRANSISTION_FROM_ETMX state we should turn the filter off with ISC_LOCK  before turning the LSC FF's on. Will need to retune the LSC FF's (from scratch starting with both MICH and SRCL FF off, and adjusting the excitation to take this L2L3LP filter into account).

Images attached to this comment
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 08:14, Tuesday 16 April 2024 (77202)
OPS Day Shift Start

TITLE: 04/16 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 7mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

IFO was unlocked upon entry - now staying down for Planned Tuesday Maintenance

H1 General
thomas.shaffer@LIGO.ORG - posted 07:23, Tuesday 16 April 2024 - last comment - 07:42, Tuesday 16 April 2024(77199)
OWL Operator intervention

A lock loss this morning from unknown reasons had the IFO running an initial alignment after it struggled to lock in the main locking. I was alerted after it timed out locking green in initial alignment. By the time I logged in and accidentally restarted green locking, increase flashed had fixed it and it have moved on in the initial alignment sequence. I'll let it finish with the hopes that it will help maintance recover slightly quicker, but not start locking again since maintenance is about to start.

I'm not sure why green was struggling so much this morning, I'll have to dive deeper into it later it. It doesn't normally time out if it can lock this easily.

Comments related to this report
thomas.shaffer@LIGO.ORG - 07:42, Tuesday 16 April 2024 (77200)

SRC wouldn't lock, but flashes looked good. Somehow, it looks like the changes I made switching from POP_A to AS_C got reverted (<a href="https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=77113">alog77113</a>). As soon as I switched back to using AS_C with 0.005 and 0.004 thresholds it locked right up.

I'll also have to check on why this was reverted when I get in.

H1 CDS
erik.vonreis@LIGO.ORG - posted 07:01, Tuesday 16 April 2024 (77198)
Workstations updated

Workstations were updated and rebooted.  This was an os package update.  Conda packages were not updated.

H1 SQZ (OpsInfo, SEI, SUS)
victoriaa.xu@LIGO.ORG - posted 06:18, Tuesday 16 April 2024 - last comment - 06:18, Tuesday 16 April 2024(77188)
FC locking issues from wind

Naoki, Corey, Vicky

Corey is taking it to OBSERVE without squeezing tonight.

We traced down an issue to FC2 0.3-0.5 Hz oscillations, which maybe is worse right now due to wind. We think this excess FC2 motion is preventing FC from locking. 

FC2 0.3-0.5 Hz oscillations screenshot - see the FC Green VCO control signal trying to lock and failing - at the same time, we can see the FC2_M1_L oscillations around 0.4 Hz, even with no control signals sent to FC2 SUS. So, seems like FCGS VCO is trying to track the FC2 L oscillations, but the real FC2 motion is too much for the FCGS VCO to hold lock, and this prevents further locking. Corey says perhaps this FC2 motion is extra bad right now due to the wind. I don't remember this issue in O4a. Without FC2 L motion calming down a bit, I don't think we can hold a stable FC lock. 

So, we decided to go to Observe without SQZ tonight, at least until the wind calms down. Maybe could try SQZ later if wind calms down.

Edit: It seems FC has been struggling to lock with winds > 30-40 MPH these last couple days, see screenshot with FC locking and wind speeds.

Images attached to this report
Comments related to this report
naoki.aritomi@LIGO.ORG - 18:57, Monday 15 April 2024 (77189)

Rahul, Corey, Naoki

Rahul found that FC2 M1 OSEM OFFSET were OFF, which should be ON. He will report the detail later. After we turned on the offset, FDS was recovered. So we went to observing with squeezing.

corey.gray@LIGO.ORG - 19:28, Monday 15 April 2024 (77190)

As I was getting ready to change H1 configuration for NLN w/ NO Squeezing, Rahul mentioned the input filters for the FC2.  So, before I changed anything, we halted No-Squeezing and decided to try for Squeezing---Naoki was able to get us there fairly quick.  And then we went to Observing.....but this only lasted about 30min before the FC unlocked again.  (this also happened to coincide with winds increasing again with gusts touching 40mph)

So we may still have an issue with FC2/HAM8 isi shaking (I believe Naoki & Jim were saying the noise is around 0.3Hz.)

I will return to following the procedure for No-Squeezing as Vicky posted originally.

corey.gray@LIGO.ORG - 19:34, Monday 15 April 2024 (77191)

And just like that, H1 had a lockloss.....about 5-sec prior to the lockloss I heard a loud creak in the Control Room/building which I'm assuming is due to a big wind gust.  :(  (see attached for a look at the winds---it's windier than last night!  And last night at around this time is when the winds increased and the SQZ started having issues during a 4hr wind storm)

I still have NOT made the changes to SQZ guardians for NO SQUEEZING.  

Images attached to this comment
rahul.kumar@LIGO.ORG - 21:16, Monday 15 April 2024 (77195)

I have switched ON the osem input filters after they were found to be OFF on SUSFC2 (HAM8) and have also accepted them in the SDF.

Images attached to this comment
LHO General
corey.gray@LIGO.ORG - posted 23:59, Monday 15 April 2024 (77186)
Mon EVE Ops Summary

TITLE: 04/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

With another 4hr wind storm, Squeezing wasn't possible due to a noisy HAM8 & an FC2 mirror oscillating at 0.35Hz.  This wind storm also caused a lockloss.  Initial Alignment was run (skipping SRC).  Winds calmed, and made it to Observing w/ Squeezing due to quieter conditions.  Overall about 5hrs of downtime due to winds preventing Squeezing and causing a lockloss. 
LOG:

H1 General (SQZ)
corey.gray@LIGO.ORG - posted 22:01, Monday 15 April 2024 (77196)
Back To Observing With Squeezing -knock on wood-

Similar to yesterday, we had a 4hr wind storm.  This caused issues with the Squeezer during the last lock and then eventually had gusts that rumbled the detector for a lockloss!  Reacquisition was tough, so optedfor a "partial" Initial Alignment (skipping SRC since SRY doesn't acquire).  After an IA, H1 locked on its first attempt. 

Aaaaaand, we also have Squeezing....BECAUSE...30min ago the wind storm calmed down!  (and I was all ready to make changes to SQZ nominal states for guardian nodes!)

I believe SQZ_FC now has the ASC "on" from Naoki's earlier work, so I ACCEPTED the SDF diffs for this (attached).

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 19:59, Monday 15 April 2024 (77192)
Mid-Shift Status: Mon EVE

H1 just had a lockloss (after 10.5hr lock) due to a big wind gust (coincident with an audible "creak" in the Control Room).  Prior to this, coincident with the beginning of this current wind storm about 3.5hrs ago, the Squeezer unlocked taking us out of Observe (similar to last night when wind storm occurred).  Naoki & Vicky spent a bit of time trying to get the squeezer back, but I overheard them talking about lots of motion on SQZ optics).  

Was getting ready to transition H1 to a No Squeezing state for the night, but the Squeezer locked back up (see Naoki/Rahul alog). But it only lasted 30min until winds increased.

Here we are after the H1 lockloss.  By default, will see if Squeezing is possible, but if we run into the same issues & it's windy, will transition H1 for No-Squeezing operations for the night.

H1 CDS
david.barker@LIGO.ORG - posted 16:14, Monday 15 April 2024 (77187)
New SUS OPLEV Overview MEDM with links to Control Screens

Fernando, Dave:

We have released a new SUS Oplev Overview MEDM in which the BSC oplevs have CONTROL buttons to open Fernando's control screens.

I took the opportunity to macrotize the overview, with the oveview opening two MICRO MEDMs: H1SUS_OPLEV_MICRO.adl is opened directly for the HLTSs, and H1SUS_OPLEV_WCTRL_MICRO.adl is opened for the BSCs. The latter in turn opens H1SUS_OPLEV_MICRO.adl and adds the CONTROL button. The control adl file resides in the SYS/H1/MEDM directory and is called H1SYS_OPLEV_CONTROL.adl.

The new Oplev Overview was created in the SUS/H1/MEDM directory, the original remains in the SUS/COMMON/MEDM directory and has not been modified.

To see the new Oplev MEDM you will need to start a new SITEMAP.

Attachment shows the Overview MEDM, with ETMY's Control MEDM superimposed.

Images attached to this report
LHO General
corey.gray@LIGO.ORG - posted 16:10, Monday 15 April 2024 - last comment - 08:37, Tuesday 16 April 2024(77185)
Mon EVE Ops Transition

TITLE: 04/15 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: SEISMON_ALERT
    Wind: 10mph Gusts, 5mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY:

Nicely Observing H1 handed off by RyanC.  He mentioned, same issue with SRC for alignment and needing to skip it (that's atleast 3x in a row).  He also mentioned a drop out of Observing due to SQZ_FC as observed last night (and tweaks Naoki made for this).  Currently, waiting for a M5.9 S.Korea earthquake to roll through with its R-wave in 10min.

Comments related to this report
ryan.crouch@LIGO.ORG - 08:37, Tuesday 16 April 2024 (77203)

Forgot my log                                                                                                                                                                                                                                                                                                                                                                                                                                                                                    

Start Time System Name Location Lazer_Haz Task Time End
15:20 FAC Chris FCES N Move snorkle lift to FCES 16:20
16:03 FAC Kim MidX n Tech clean 17:03
18:04 EE Fil MidY n Parts search 19:04
17:10 CAL Francisco PCAL lab LOCAL PCAL work 20:10
18:18 FAC Tyler AHU N AHU1 fan 18:35
H1 SQZ
naoki.aritomi@LIGO.ORG - posted 20:39, Sunday 14 April 2024 - last comment - 06:32, Tuesday 16 April 2024(77164)
SQZ issue

Vicky, Naoki

In the last lock, the FC IR kept unlocking. We first thought the timer issue similar to 76280 so we removed the timer, but it did not help. We checked the FC IR OLG and it was fine. Then we found that the FC ASC input signal moved a lot. We turned off FC ASC and the stability was improved. We decided to go to observe without FC ASC tonight. 

Comments related to this report
victoriaa.xu@LIGO.ORG - 21:30, Sunday 14 April 2024 (77166)

As a separate issue (I think) than FC not locking, the pump ISS control voltage was dropping below 2V and losing lock. I aligned the fiber polarization, but more importantly sent more power from the pump aom to the fiber, aka reduced the rejected power on H1:SQZ-SHG_REJECTED_DC_POWERMON, to keep pump ISS locked. On a Tuesday with extra time, might be worth checking if the pump path alignment (pump aom + fiber) is still good.

corey.gray@LIGO.ORG - 23:14, Sunday 14 April 2024 (77167)

Once we got back to NLN, continued to have the issue with SQZ_FC unlocking.  Naoki & Vicky continued to work on it. 

Currently we have SQUEEZING.

To get to OBSERVING, I had to ACCEPT some Diffs (see attached).

If the SQZ_FC unlocks again, Operators should take steps to put H1 in NLN + NO SQUEEZING (I'm set up to follow the procedure to do this if it happens in the next 45min, otherwise, I sent a text to the OWL shift operator.)

Images attached to this comment
victoriaa.xu@LIGO.ORG - 06:32, Tuesday 16 April 2024 (77197)

See LHO:77188 - these FC locking issues seem correlated with >30-40 mph winds, likely moving FC2 SUS too much to hold lock. We had seen the FCGS trans beam (on SQZT8 in FCES) moving a lot on the camera, which suggested the FC cavity axis was moving a lot. This is why we disabled FC ASC this night. If that helped, it's b/c FC2 SUS, aka the FC cavity axis, was moving due to winds. We traced this down the following night 77188 when higher winds prevented even FC green VCO locking, and we saw the FCGS control signal was railing and correlated with FC2 SUS motion with no control signal.

Both nights (this and following one) - FC locked overnight once winds calmed down, see screenshot.

H1 SQZ
naoki.aritomi@LIGO.ORG - posted 13:19, Tuesday 09 April 2024 - last comment - 06:22, Tuesday 16 April 2024(77060)
SQZ OMC mode scan with cold OM2

Eric, Naoki, Vicky, Jennie W, Sheila

We did SQZ OMC mode scan with cold OM2. The PSAMS is 175/100 (strain voltage 8.9/-0.69). The attached figure shows the result (ref 34). The SQZ OMC mode matching is 0.64/(0.64+2*0.03)~91.4%.

We followed the instruction in 74892. Here are some notes.

PSAMS 175/100, cold OM2

DARK

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 15:45, Wednesday 10 April 2024 (77096)

I used my code to fit the scan and C02 peak for this scan. As we saw with the PSL beam the new OMC means we cannot resolve these two peaks.

But if I assume one is buried in the noise and do the fit anyway we get (0.027 - 0.0038)/(0.027 + 0.64 - 0.0038) = 3.5%  mode-mismatch for the squeezed beam matching to the OMC, with a fitted HWHM of 0.33 MHz.

NB: The factor 0.0038 mA is what I had to add to the scan data to shift the baseline to be above zero otherwise the fitting doesn't work well.

If I just use the measured height of C02 from the full scan (which is like assuming both C02 and C20 are overlapped) the mode-mismatch would be (0.029 - 0.0038)/(0.029 + 0.64 - 0.0038) = 3.8 %.

The OMC (001 is the current) parameters are given in this alog by Matt Todd, this gives a value for the half-width at half-maximum of 0.31MHz which matches our fitted one fairly closely.

The C02 peak graph (second image) has the OMC scan data in blue, fit in red, and initial guesses for the fit in purple.

Non-image files attached to this comment
victoriaa.xu@LIGO.ORG - 06:22, Tuesday 16 April 2024 (77183)

Looking at this SQZ-OMC mode scan (data, mode scan), and running the same scripts as before (e.g. LHO:70866), this loss estimate based on OMC visibility using the squeezer beam doesn't really make sense. Hopefully PSL scans will make more sense. May be worth re-taking this squeezer measurement sometime.

Mode-matching and visibility make sense: Single-bounce SQZ-OMC mode mismatch ~ 4% based on TEM02/20 is consistent with Jennie's peak fitting, HOM content ~ 9-12%, and OMC locked/unlocked visibility = 1-locked/unlocked ~ 90%.

Loss estimate does not make sense: the inferred OMC transmission is ~72%, and if we ignore mode mismatch (ie assume 100% matching) this corresponds to an OMC transmission of 81%. But ~20% omc loss is ruled out by observed squeezing levels.

5.4 dB SQZ corresponds to a total loss of 20-25%, see params below including 12.3% expected sqz losses. This limits OMC losses < 10-15%, if assuming no mode-mismtch. With mode-mismatch, squeezing suggests OMC losses << 10%. This is not saying much, except this measurement is off.

  • 5.4 dB of kHz squeezing, e.g. LHO:77073 
  • 5 - 25 mrad phase noise (Nutsinee's < 5mrad recent estimate from in-loop noises LHO:77124 & O4a 20-25 mrad phase noise from DARM NLG sweep LHO:74318)
  • NLG ~ 17.2 (many measurements @ 80 uW green trans)
  • ~12.3% known SQZ losses, excluding OMC losses and mode mismatch. This is known sqz injection losses of 7.3% + known readout losses, excluding OMC losses, of 5.4%.
           ---> 1 - (1-.073)*(1-.054) = 12.3% sqz loss, excluding OMC losses and all mode-mismatch ( O4 SQZ wiki, gsheet )

So squeezing rules out the ~20% omc losses inferred from this sqz-omc visibility measurement. I'm not sure what is exactly is wrong, but in the mode scan, there was considerable TEM01/10 misalignment despite running OMC ASC + manual alignment. Unsure if alignment is the issue, or maybe something wasn't right with the squeezer beam, such that alignment couldn't improve (worth checking the beam round-ness on sqzt7?).

Script output below (code in git). Running this and Sheila's script in LHO:70866, I get the same output. So, the script seems OK, but something else is wrong with this measurement.

--------------- er16 sqz ------------------

processing measurement for er16 sqz

P_Refl_on_res*1e3 = 0.12831 mA 
P_Refl_off_res*1e3 = 1.00626 mA
Trans_A*1e3 = 0.62987 mA  (I assume OMC-DCPD_SUM_OUTPUT is calibrated into mA with the new OMC, I did not check this calibration.)
removed trans blocked of -0.00332 mA

Power on refl diode when cavity is off-resonance: 1.006 mW
Power on refl diode when cavity is on-resonance: 0.128 mW
Trans power when cavity is on-resonance: 0.734 mW 
Incident power on OMC breadboard (before QPD pickoff): 1.026 mW
Measured efficiency (DCPD current/responsivity if QE=1)/ incident power on OMC breadboard: 71.546 %

Using 4.0% mode-mismatch from Jennie peak fitting, visibiilty_00*100 = 90.885%

assumed QE: 100 %
power in transmission (for this QE) 0.734 mW
HOM content infered (like mode matching):  11.964 % 
Cavity transmission infered:  82.057 % 
predicted efficiency () (R_inputBS * mode_matching * cavity_transmission * QE): 71.546 %

omc efficency for 00 mode (incl R_inBS * cavity_transmission * QE, no mm): 81.270 %
round trip loss: 1606 (ppm)
Finesse: 372.613
Non-image files attached to this comment
Displaying reports 2321-2340 of 77273.Go to page Start 113 114 115 116 117 118 119 120 121 End