Displaying reports 2621-2640 of 83266.Go to page Start 128 129 130 131 132 133 134 135 136 End
Reports until 13:36, Tuesday 25 February 2025
LHO VE
david.barker@LIGO.ORG - posted 13:36, Tuesday 25 February 2025 (83037)
Tue CP1 Fill. New code.

Tue Feb 25 10:17:54 2025 INFO: Fill completed in 17min 49secs

Today was the first run of the new code, which terminates the fill on rate of thermocouple temperature drop rather than dropping below a set limit. This will free us from having to manage the limit during seasonal changes.

TCmins[-144C, -140C] OAT (+11C, 51F).

For now the plot still shows the old -90C trip level. I'm working on a new plot which shows the rate-of-change channels.

I'll make a detailed alog about the new code with its associated MEDM, striptools and plots in the next few days.

Images attached to this report
H1 SEI
thomas.shaffer@LIGO.ORG - posted 11:12, Tuesday 25 February 2025 (83033)
H1 ISI CPS Noise Spectra Check - Weekly

FAMIS26032

The script reported high noise for ITMX ST1 V1, ETMY ST2 V2. Though ITMX does seem a bit elevated, it has been this way for some time, but EY ST2 looks different from previous weeks this was run (last week's alog82911).

Non-image files attached to this report
H1 CDS
david.barker@LIGO.ORG - posted 08:47, Tuesday 25 February 2025 (83030)
Bypass of fire pump alarms while pump testing is ongoing

Bypass will expire:
Tue Feb 25 11:45:00 AM PST 2025
For channel(s):
    H0:FMC-CS_FIRE_PUMP_1
    H0:FMC-CS_FIRE_PUMP_2
 

H1 SQZ
camilla.compton@LIGO.ORG - posted 08:32, Tuesday 25 February 2025 (83022)
NLG vs OPO Trans

Sheila, Camilla

The NLG vs OPO trans powers in 82202 didn't make sense. We thought it could be pump depletion from a high seed so we reduced Seed from 0.6 to 0.2mW. NLG measured following 76542.

125uW for NLG of 80 seemed much more sensible but when we increased the seed back to 0.6uW we got the same NLG so were not seeing pump depletion.

OPO Trans (uW) NLG Seed Launch (mW)
80 11.9 0.2
125 83.0 0.2
125 79.0 0.51

Plot attached shows the power in and refl off OPO, we are happy with the current OPO position and don;t think that the crystal has more losses yet.

Looking at the old data, NLGs measured on Thursday 09 January 2025:

Next time we take NLG data, we should make sure that the seed power is low enough that the OPO trans power is steady at the requested power,  so the OPO is not experiencing pump depletion.

Images attached to this report
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 07:54, Tuesday 25 February 2025 (83029)
OPS Day Shift Start

TITLE: 02/25 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 33mph Gusts, 23mph 3min avg
    Primary useism: 0.11 μm/s
    Secondary useism: 0.78 μm/s
QUICK SUMMARY:

IFO was in PREP_FOR_LOCKING, unable to lock due to microseism and very high winds. IFO is now in PREVENTATIVE MAINTENANCE (and SEI_ENV in MAINTENANCE) for our planned 6 hour Tuesday Maintenance.

A short list of planned maintenance:

Work safe and be mindful of flying tumbleweeds.

H1 CDS
erik.vonreis@LIGO.ORG - posted 07:38, Tuesday 25 February 2025 (83028)
Control room wall displays updated

Control room wall displays were updated and rebooted

H1 CDS
erik.vonreis@LIGO.ORG - posted 06:38, Tuesday 25 February 2025 (83027)
workstations updated

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

H1 General
anthony.sanchez@LIGO.ORG - posted 22:27, Monday 24 February 2025 (83026)
Monday Eve Shift Summary.

TITLE: 02/25 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Earthquake
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

H1 WAS Locked for 3 hours until this Lockloss.
Relocking has resulted in locklosses during various stages of ISC_Lock which seems reasonable given the variability in the wind tonight and high useism.
Made it to LOWNOISE_COIL_DRIVERS[552] when a 5.2 Mag Earthquake from Canada snuck up on us and left me scratching my head for a minute wondering what cause the ground motion to spike.

H1 Manager is currently trying to lock but I imagine the now incoming 5.9 Mag from Puerto Rico might prevent this lock attempt as well.

Also this :
I dont mean to be lude.... but the the Filter Cavity Loo, has been moved,  probably from when the wind blew this afternoon. I'm just  trying to ensure that everyone knew, that you may need to find a new place to go number 2, and don't step in the mud that's blue.



Last minute update:
H1 just lost lock again, Considering the Wind forcast for tonight , Earthquakes that are rolling through, and the useism I'm just going to hold the IFO in down for the night.
Sheila said we may want to cancel the Owl's for the night just looking at the wind forcast for tonight.

Images attached to this report
H1 General (Lockloss)
anthony.sanchez@LIGO.ORG - posted 21:36, Monday 24 February 2025 (83025)
Lockloss

STATE of H1: Lock Acquisition
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 25mph Gusts, 20mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.70 μm/s
QUICK SUMMARY:


04:12:41 UTC Lockloss that has a number of potential causes, ETMX glitch, wind, and increased useism with some small earthquakes passing through all at the same time.
https://ldas-jobs.ligo-wa.caltech.edu/~lockloss/index.cgi?event=1424491980

 

 

Images attached to this report
H1 General
anthony.sanchez@LIGO.ORG - posted 16:34, Monday 24 February 2025 (83024)
Monday Eve Shift Start

TITLE: 02/25 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Wind
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 13mph Gusts, 9mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.44 μm/s
QUICK SUMMARY:

H1 is currently Unlocked due to a High wind event.
Corey had just finished an Initial Alignment before the handoff and we have now gotten past DRMI locking stages.
More high winds are expected tonight so we shall see how long this lock lasts.




 

 

LHO General
corey.gray@LIGO.ORG - posted 16:26, Monday 24 February 2025 (82994)
Mon DAY Ops Summary

TITLE: 02/24 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Wind
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

More Commissioning Than Observing This Shift. 
Wind has been the highlight of the last 12hrs with H1 able to lock once the winds died this morning, but immediately jumped into scheduled Commissioning time.  Then after about 30min of Observing, an earthquake took H1 down.  Then 71min of Observing and then a HUGE (and fairly quick) wind event took H1 down again---with winds gusting up to 65mph (see attached).

There is a wind advisory for the next 24hrs starting at 7pm local time.  Good luck Eve & Owl shifts! :-/  
LOG:

Images attached to this report
H1 ISC (SQZ)
jennifer.wright@LIGO.ORG - posted 15:09, Monday 24 February 2025 - last comment - 10:29, Thursday 27 March 2025(83008)
Updating OMC Offsets Today

Jennie W, Sheila

Summary: We altered the offsets on the H1:ASC_OMC_{A,B}_{PIT,YAW} QPDs which are used to align the beam into the OMC. This was aiming to give us a improvement in optical gain. After doing this we aimed to measure the anti-symmetric port light changing as we chnage the darm offset. We are trying to use both these measurements to narrow down where we have optical loss in that could be limiting our observed squeezing. Performed both measurments successfully but the different alignment of the OMC made the squeezing less good so Camilla (alog #83009) needed to do some tuning.


Last time (alog #82938) I did this I used the wrong values as our analysis used the output channels to the loops instead of the input channels which come before the offsets are put in. The new analysis of our measurement of the optical gain as seen by the 410Hz PCAL line, changing with QPD offset, shows that we want the loop inputs to change to:

H1:ASC_OMC_A_PIT_INMON to 0.3 -> so we should change H1:ASC_OMC_A_PIT_OFFSET to -0.3

H1:ASC_OMC_A_YAW_INMON to -0.15 -> so we should change H1:ASC_OMC_A_YAW_OFFSET to 0.15

H1:ASC_OMC_B_PIT_INMON to 0.1 -> so we should change H1:ASC_OMC_B_PIT_OFFSET to -0.1

H1:ASC_OMC_B_YAW_INMON to 0.025 - so we should change H1:ASC_OMC_B_YAW_OFFSET to -0.025

We stepped these up in steps of around 0.01 to 0.02 while monitoring the saturations on OMC and OM3 suspensions and the optical gain, both to make sure we were going in the correct direction and that we were not near to saturation of the suspensions as hapenened last time I tried to do this.

Attached is the code and the ndscope showing the steps on each offset, (top row left plot, top row center right plot, second row left plot, second row center right plot). The top stage osems for OM3 suspension are shown in the third row left plot, the top stage osems for OMC suspension are in the third row center left plot, and the optical gain is shown in the third row right plot.

The optical gain improved from by 0.0113731 from a starting value of 1.00595, so that is an improvement of 1.13 % in optical gain.


Around 19:04:28 UTC I started the DARM offset step to see if the change in optical gain matches that we would see if we measured the throughput of HAM 6. Unfortuntely I forgot to turn off the OMC ASC which we know affects this measurement of the loss. We stood down from changing the OMC and Camilla did some squeezer measurements, then I made the same mistake again the next time I tried to run it (d'oh). Both times I control-C'd the auto_darm_offset.py form the command line which means the starting PCAL line values, and DARM offset had to be reset manually before I ran the script successfully after turning the OMC ASC gain to 0 to turn it off.

The darm offset measurement started at 19:20:31 UTC. The code to run it is /ligo/gitcommon/darm_offset_step/auto_darm_offset_step.py

The results are saved in /ligo/gitcommon/darm_offset_step/data and /ligo/gitcommon/darm_offset_step/figures/plot_darm_optical_gain_vs_dcpd_sum.

From the final plot in the attached pdf, the transmission of the fundamental mode light between ASC_AS_C (anti-symmetric port) DCPD is (1/1.139)*100 = 87.8 %. We can compare this to the previous measurement from last week with the old QPD offsets to see if the optical loss change matches what we would expect from such a change in optical gain.

Images attached to this report
Non-image files attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 16:14, Monday 24 February 2025 (83023)OpsInfo

Since the script didn't save the correct values for pcal ey and ex (due to the script being run partially twice before a siccessful measurement). I reverted the PCAL values back using SDF before we went into observing. See attached screenshots.

Sheila accepted the new ASC-OMC_A and B OFFSET values in OBSERVE and SAFE (only have the pic for OBSERVE).

Images attached to this comment
jennifer.wright@LIGO.ORG - 11:07, Friday 21 March 2025 (83487)

Comparing OMC losses calculated by OMC throughput and optical gain measurements.

If we take the improvement in optical gain noted above and calculate the improvment in the optical gain ^2, ie.

(g_f^2 - g_i^2)/ g_i^2 = 0.023 = 2.3 %

And compare it to the gain in OMC throughput from this entry to the measurement after changing the OMC ASC offsets above

(T_OMC_f - T_OMC_i)/ T_OMC_i = 0.020 = 2%

Both methods show a similar improvement in the coupling to the OMC, or alternatively decrease in the HAM 6 losses. Since we improved the alignment of the OMC, it makes sense that the losses decrease and them agreeing validates our method of using darm offset steps to calculate OMC throughput and thus the loss in HAM 6.

The optical gain must be squared as it changes with the square root of the power at the output (due to the DARM loop).

For this comparison I was not able to use the measurement of optical gain from the same day as the initial measurement of OMC throughput, (alog #82938) as the calibration was exported to the front-end between these two dates which would have changed the reference value for kappa C.

The code I used for calcultions is attached.

Non-image files attached to this comment
jennifer.wright@LIGO.ORG - 10:29, Thursday 27 March 2025 (83587)

As I did for the previous DARM offset measurement on the 20th Feb, in alog  #83586, I checked that the DARM offset does not show a clear trend in the OMC REFL power. This would be another way of quantifying the mode-matching of the DARM mode to the OMC, but since the mode-matching is good, no trend can be seen in this channel (top plot) as we change the DARM offset.

Images attached to this comment
H1 ISC
sheila.dwyer@LIGO.ORG - posted 14:55, Monday 24 February 2025 (83003)
Fringe wrapping from CPs

Fringe wrapping excitations (all made in test_L excitation with 10000 counts amplitude).

Rough summary:  CPX and CPY have similar levels of fringe wrapping from a longitudnal excitation.  For CPY, a third shelf appears when I turned off the ailgnment offsets that Robert set to reduce the noise he sees while shaking the input arm. 

From Accadia et al the shelf frequency = abs(2*velocity of scatterer/lambda).  So our first shelf at 17Hz comes from some path with a velocity of 9 um/second, the second fringe at 33Hz from a path with twice that velocity at 17.5um/second, and the third fringe which only shows up for CPY with no offsets is at three times that velocity at 50Hz (27um/second).  The max veolcity of R0 should be 2 *pi*0.2 Hz * 7.7um/2 = 4.8um/second.  That's consistent with the first shelf being from some scatter path hits the CP twice, so it scatters out of the cavity by being reflected off one of the CP faces, and also scatters back in by a reflection off the CP. 

Side note, the damping signals for the two CPs seem rather different, I will try to come back later to look at why they are so different.

Editing to add after looking at the damping loops with help from Jeff:

ITMY's R0 F2 has a lot of 60Hz noise.  Jeff suggests copying the 60Hz notch filter from the main chain damping loops into the oseminf filter banks for the reaction chain, and he recomends doing this for F1,F2, F3 and SD since these are all on the same electronics chain. 

At first it seems that we have rather different settings between the R0 damping filters for ITMX + ITMY, but the gains for ITMX are incorporated into filter banks, in the end the damping loops seem to be the same.  The attached spectrum comparison shows that the motion of the two reaction chains looks similar on the osems.

Images attached to this report
H1 ISC (SQZ)
jeffrey.kissel@LIGO.ORG - posted 14:28, Monday 24 February 2025 - last comment - 14:58, Monday 24 February 2025(83013)
Explicity Channel List for ALS / SQZ Fiber and ISCT1 Power Monitors
J. Kissel (with help from S. Dwyer and J. Oberling)
ECR E2400083

As a part of the final design review, the SPI team is looking to understand the future duty cycle of the proposed SPI Pick-off path which gets light from downstream of the PMC, see ECR E2400083 -- and specifically the region highlighted in red in the "other files" proposed layout. In order to do so, here are some relevant channels for existing monitor PDs that measure the power in the current PMC / ALS / SQZ paths.

                                        Units          Today's            Location           Relevant Drawing      PD's Name/Location
                                                    Reported Power                                                 within Drawing

(1) H1:PSL-PWR_PMC_TRANS_OUTPUT          [W]           105.0                 PSL              D1300348             "PD04" in transmission of M18, Row 19 / Col 100

(2) H1:ALS-C_SHG_IR_DC_POWER             [mW]            2.200              ISCT1             D1201103             "DCPD" in reflection of BS1 in red "PSL" path from right-most ALS periscope
 
(3) H1:ALS-C_FIBR_EXTERNAL_DC_POWER      [mW]            0.475               PSL              D1300348             "ThorLabs SM1PD1A" in transmission of ALS-M9, Row 34 / Col 149

(4) H1:ALS-C_FIBR_INTERNAL_DC_POWER      [mW]            0.105             ALS Fiber          D1200136             "ThorLabs SM05PD1A" measuring 50% * 1% sample of beam from PSL
                                                                       Distribution Box

(1) PD is calibrated to display the power downstream of the primary output port of the PMC, even though the PD is measuring a different PMC port and downstream of several power-changing optics (confirmed by Jason to be true).
(2 thru 4) PDs are calibrated to simply report the light at the photodiode, not say, the power of the path upstream of their respective pick-off beam splitters (confirmed by Sheila to be true).

For (2 thru 4), there are versions of those PD signals, (2' thru 4') which *have* been calibrated to the power in the beam path, and those are
(2') H1:ALS-C_SHG_IR_DC_POWERMON         [mW]           56.0         
(3') H1:ALS-C_FIBR_EXTERNAL_DC_POWERMON  [mW]           44.7
(4') H1:ALS-C_FIBR_INTERNAL_DC_POWERMON  [mW]           30.2
 

There's also a useful set of channels the explicitly report the duty-cycle of the PMC too:
   (5) Days, Hours, Minutes of "uptime," resets to zero upon PMC lock loss event
    - H1:PSL-PMC_RELOCK_DAY    [days]
    - H1:PSL-PMC_RELOCK_HOUR   [hours]
    - H1:PSL-PMC_RELOCK_MIN    [minutes]

    How long took to last relock
    - H1:PSL-PMC_RELOCK_DUR    [seconds]

So, if you're performing duty-cycle statistics, say, over a year, you'd trend the H1:PSL-PMC_RELOCK_DAY channel, find the points just before each drop to zero, then take a histogram of those values and find the quantiles to report the median (50% quantile) and then whatever quantile you like to represent "usually."

In the first attached screenshot of MEDM overview screens, I highlight where the channels live. 
    - On the ALS overview screen, 
        (2) is circled in RED, 
        From the hidden "FIBER DISTRIBUTION BOX" link, (3) and (4) are circled in GREEN and YELLOW, 
    - PSL PMC overview screen 
        (1) is circled in MAGENTA, and 
        (5) are circled in BLUE

In the second attached screenshot of the ALS/SQZ subscreens, the screens themselves highlight the "power at the PD" versions, (2 thru 4), in PURPLE, and I highlight the "power in the relevant path" versions, (2' thru 4') in GREEN.

Stay tuned for the results of looking at these channels to derive quantitative estimates of duty cycle. 
Images attached to this report
Comments related to this report
jeffrey.kissel@LIGO.ORG - 14:58, Monday 24 February 2025 (83020)SQZ
Still qualitative at this point, but a good representative time period should be the two years between July 01 2022 00:00 UTC and July 01 2024 00:00 UTC. This time period contains two observatory cycles of "vent > commission > observe," with O4a lasting from May 24 2023 at 15:00 UTC to Jan 16 2024 at 16:00 UTC, and O4b resuming Apr 10 2024 15:00 UTC.

The ndscope command starts with
ndscope H0:VAC-LY_Y1_PT120A_PRESS_TORR H0:VAC-LY_Y1_PT120B_PRESS_TORR . H1:GRD-ISC_LOCK_STATE_N . H1:PSL-PWR_PMC_TRANS_OUTPUT . H1:PSL-PMC_RELOCK_DAY . H1:ALS-C_SHG_IR_DC_POWERMON . H1:ALS-C_FIBR_EXTERNAL_DC_POWERMON H1:ALS-C_FIBR_INTERNAL_DC_POWERMON &

I've saved the .yaml and .mat file of the session in 
    /ligo/home/jeffrey.kissel/2025-02-24/
        alssqzpowr_July2022toJul2024_trend.mat
        alssqzpowr_July2022toJul2024_trend.yaml
and I attach a screenshot of the session.
Images attached to this comment
H1 SUS
camilla.compton@LIGO.ORG - posted 14:18, Monday 24 February 2025 (83019)
VIOLIN_DAMPING Guardian keeps us from Observing for ~2m30

VIOLIN_DAMPING Guardian keeps us from Observing for ~2m30 each time we get to NLN. In Feb, on average we've lost lock from state 600 3 times a day, this is around 0.5% of observing time lost. Is this wait timer in the VIOLIN_DAMPING Guardian required?

H1 CDS
david.barker@LIGO.ORG - posted 13:34, Monday 24 February 2025 (83018)
Added X6,Y6 vacuum gauges to VACSTAT

WP12342

Janos, Dave:

VACSTAT was extended by the addition of the X6 and Y6 beam tube ion-pump vacuum gauges. These are located about 100m from their respective end stations, and are solar powered.

The service was restarted at 11:20. The extended medm is shown attached.

Images attached to this report
H1 PSL
jason.oberling@LIGO.ORG - posted 13:22, Monday 24 February 2025 (83017)
PSL FSS RefCav Remote Alignment Tweak (WP 12349)

We had a lockloss, so I was able to take a few minutes and attempt a remote alignment tweak of the FSS RefCav from the Control Room.  With the IMC OFFLINE, I was able to increase the RefCav TPD from a starting value of ~0.677 V up to ~0.801 V.  With the IMC once again locked the RefCav TPD sits right around ~0.799 V.  This is the highest we've seen the RefCav TPD since our amplifier diode slope measurements (82635 & 82636) and better than the last on-table adjustment in January (82503).  This means that an on-table alignment is not necessary at this point in time, so there will NO PSL enclosure incursion during maintenance tomorrow.  This closes LHO WP 12349.

H1 SQZ
camilla.compton@LIGO.ORG - posted 12:56, Thursday 09 January 2025 - last comment - 13:51, Tuesday 25 February 2025(82202)
SQZ Work Today: Increasing SHG OPO Pump light, Homodyne Measurements, SQZ FIS and FDS Data Set.

Sheila, Camilla

After TJ found out OPO was struggling to get enough SHG pump power to lock 82196, Sheila repeated Daniel's 82057 SHG work as he had increased H1:SQZ-SHG_GR_DC_POWERMON from 95 to 125mW but now it's down to 92mW: Tried steering the beam with picos moves, and by adjusting the temperature it improved to 93mW only.

We went only SQZT0 and Sheila adjusted the alignment into the OPO pump fiber with the OPO unlocked, bringing the the OPO REFL DC power from 1.7 to 1.9mW.   We also moved the SHG wave plate further to maximize the amount of light Now CLF could lock with controlmon around 5.8V. Much better and closer to the center of the range so should avoid this mornings 82196 issues.

Homdyne Work:

To take the below data, SEED power reduced back to 0.6mW, and then:

Type NLG SQZ dB  @ 1kHz Angle DTT Ref Notes
Dark Noise N/A   N/A ref 0 This and shot noise was noisy <300Hz at times when the OPO was locking or scanning, unsure why.
ASQZ 11.2 14.2 241 ref 2 opo_grTrans_setpoint_uW = 80uW
SQZ 11.2 -6.8 154 ref 3 reduced LO loop gain from 15 to -1
SQZ 14.3 -6.1 182 ref 4
opo_grTrans_setpoint_uW = 120uW
reduced LO loop gain from -1  to -12
ASQZ 14.3 17.8 216 ref 5  
ASQZ 16.0 19.1 210 ref 6 opo_grTrans_setpoint_uW = 140uW
SQZ 16.0   191 ref 7  
SQZ 16.0 -6.8 190 ref 8 increased LO loop gain from -12 to -1 as was looking peaky
Shot Noise N/A   N/A ref 1
Blocked SEED, LO only.

We measured ~6.5dB of SQZ on the HD and up to 19dB of ASQZ. Plot attached.

Next time we work on the HD, we should measure the LO loop to know the correct gain to use.

SQZ data set

UTC Type CLF Phase DTT ref
19:02:00 - 19:08:00 No SQZ N/A ref 0
19:14:00 - 19:20:00 (6mins) FDS SQZ 177deg ref 1
19:21:00 - 19:25:00 (4mins) FDS Mid + SQZ 215deg ref 2
19:26:00 - 19:30:00 (4mins) FDS Mid - SQZ 125deg ref 3
19:32:00 - 19:36:00 (4mins) FDS ASQZ (-sign) 108deg ref 4
19:40:00- 19:43:00 (3mins) FIS ASQZ (-sign) 108deg ref 5
19:43:15- 19:45:15 (2mins) FIS ASQZ +10deg (-sign) 118deg ref 6
19:45:30- 19:47:30 (2mins)
FIS ASQZ -10deg
(-sign) 98deg
ref 7
19:48:00 - 19:51:00 (3mins)
FIS SQZ
177deg
ref 8
19:51:30 - 19:54:30 (3mins)
FIS Mid + SQZ
(check, small low freq glitch at 19:53:49)
215deg
ref 9
19:55:00 - 19:58:00 (3mins)
FIS Mid - SQZ
125deg
ref 10
Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 09:05, Tuesday 25 February 2025 (83031)

In 83022  we found that we had pump depletion during these measurements so that the OPO trs powers were actually lower than reported

sheila.dwyer@LIGO.ORG - 13:51, Tuesday 25 February 2025 (83034)

I've imported Camilla's data from dtt, subtracted the dark noise.  As Camilla notes above, the NLG measurements here don't nicely fit a model for a consistent threshold power.  Instead of using the NLG data, I've allowed the threshold power to be one of the parameters that varies in the fit, along with total efficiency and phase noise.  In principle one could also use this data to estimate the technical nosie that limits squeezing, but I haven't tried that with just a few points here.

The attached shows the NLG measurements vs what we would expect given the threshold power that the squeezing and anti-squeezing fits suggest.  This model suggests that the total efficiency to of the homodyne squeezing is only only 81%, which seems too low. 

This script is available here: quantumnoisebudgeting, but needs a lot of cleaning up.

Images attached to this comment
Displaying reports 2621-2640 of 83266.Go to page Start 128 129 130 131 132 133 134 135 136 End