Displaying reports 201-220 of 85053.Go to page Start 7 8 9 10 11 12 13 14 15 End
Reports until 10:12, Tuesday 07 October 2025
H1 PSL
jason.oberling@LIGO.ORG - posted 10:12, Tuesday 07 October 2025 (87338)
PSL Amplifier Pump Diode Operating Current Tweak

J. Oberling, R. Short

This morning we tweaked the operating current of the PSL 4S-HP amplifier pump diodes; this was done with the ISS OFF.  The tweaks can be seen in the attached plot.  End numbers:

With the ISS back ON, we had to decrease the RefSignal to -2.01 V to put the diffracted power % back at our usual 4% (this is due to the increase in power out of the PMC).

To end, we took the opportunity to tweak the beam alignment into the RefCav.  We started with a TPD of ~0.533V, and ended with a TPD of ~0.55V.

A rotation stage calibration will need to be performed due to the increased power out of the PMC.

Images attached to this report
H1 PEM (PEM)
corey.gray@LIGO.ORG - posted 09:05, Tuesday 07 October 2025 (87337)
Dust Monitor Check Notifications for DR2

Did the Dust Monitor Check and a new (to me atleast) problem would be for DR2 (Diode Room 2).

LHO General
corey.gray@LIGO.ORG - posted 08:55, Tuesday 07 October 2025 - last comment - 12:59, Tuesday 07 October 2025(87334)
Tues DAY Ops Transition: Maintenance Day

TITLE: 10/07 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 2mph Gusts, 1mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s 
QUICK SUMMARY:

First things first, at Camilla's request, I did a PAUSE for TCS_ITM[x/y]_CO2_PWR Guardians---this was for a possible Matt T. test (he just walked in and was hoping for a recently-thermalized H1, but H1is only at NLN for 1.25hrs (he's contacting Sheila).

Other than that, preparing for Maintenance!

P.S. There was a dust alarm for one of the Optics Labs when I arrived

Comments related to this report
corey.gray@LIGO.ORG - 12:59, Tuesday 07 October 2025 (87347)

Notes On H1 Overnight:  NO Wake-Up Calls; Lockloss down from 1131-1331utc (due to earthquake dropping H1 +L1); Reacquisition AUTOMATIC (no alignment run); H1 was then locked about 90min before it was intentionally unlocked for Maintenance.

H1 CDS
erik.vonreis@LIGO.ORG - posted 06:50, Tuesday 07 October 2025 (87333)
Workstations updated

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

H1 General (OpsInfo)
anthony.sanchez@LIGO.ORG - posted 22:17, Monday 06 October 2025 (87332)
Monday Eve Shift End.

TITLE: 10/07 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY:
Super Event Candidate: S251006dd ! 
Other than that it was a very quiet night, H1 has been locked for 10 hours  without issue.

Note to the morning ops:  
Please pause the Co2_PWR guardian before lockloss this Tuesday, see mattermost. 

LOG:
No Log

 


 

H1 General
anthony.sanchez@LIGO.ORG - posted 16:36, Monday 06 October 2025 (87330)
Monday Eve Shift Start

TITLE: 10/06 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 10mph Gusts, 4mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s 
QUICK SUMMARY:
H1 has been locked for 4.5 hours & we have no plans to deviate from observing all night.

 

 

LHO General
ryan.short@LIGO.ORG - posted 16:32, Monday 06 October 2025 (87329)
Ops Day Shift Summary

TITLE: 10/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Commissioning time with one lockloss this morning followed by a pretty straightforward relock this afternoon. H1 has now been locked and observing for 4.5 hours.

LOG:

Start Time System Name Location Lazer_Haz Task Time End
22:52 SAF Laser HAZARD LVEA YES LVEA is Laser HAZARD Ongoing
14:40 FAC Randy X-arm N BTE inspection 22:40
14:50 JAC Corey JAC Lab N JAC table work 17:03
14:58 FAC Nellie MY N Technical cleaning 15:44
15:21 FAC Kim MX N Technical cleaning 16:23
15:37 PEM Robert LVEA - Setting up measurements 16:08
16:01 OPS TJ JAC Lab N Talking to Corey 16:21
16:20 FAC Nellie Opt Lab N Technical cleaning 16:33
16:43 PEM Robert LVEA - Moving accelerometer 16:54
17:11 PEM Robert LVEA - Moving accelerometer 17:29
17:30 PEM Robert LVEA - Moving accelerometer 17:39
17:33 JAC Fil JAC Lab N JAC table work 19:16
17:41 ISC Sheila, Matt LVEA - Looking at sidebands 17:46
18:04 PEM Robert LVEA - Shutting down measurement 18:19
19:59 ISC Keita, Jennie Opt Lab Local ISS array work 21:34
20:48 OPT Corey, RyanS OpticsLab n Organizing JAC, SPI optics 21:53
21:56 JAC Corey LAC Lab N JAC table work 22:10
H1 PEM
ryan.short@LIGO.ORG - posted 16:25, Monday 06 October 2025 (87328)
Dust Monitor Trends - Monthly

FAMIS 37257, last checked in alog86733

Following the power outage at the start of September, dust counts were high across the corner station and came back down over the course of several days. The diode room dust monitor seems to flatline more often and looks to need to be restarted now.

Images attached to this report
H1 SUS (SUS)
edgard.bonilla@LIGO.ORG - posted 15:09, Monday 06 October 2025 - last comment - 17:07, Monday 06 October 2025(87326)
Added a Length estimator to the HLTS_W_EST simulink diagrams + DQ channels to monitor

Made a modification to the library parts needed for adding an OSEM estimator to the Length degree of freedom for the HLTS models. The change comes with an addition of a few DQ channels, listed on the.txt attached. This work is part of the ECR summarized here: E2500251.

The library parts modified live in /opt/rtcds/userapps/trunk/sus/common/models/ , they are HLTS_MASTER_W_EST.mdl and SIXOSEM_T_STAGE_MASTER_W_EST.mdl.
The changes were committed to the userapps svn under revision 33319.

Summary of changes:

SIXOSEM_T_STAGE_MASTER_W_EST.mdl

HLTS_MASTER_W_EST.mdl

List of new DQ channels:

The attached text file lists both the PR3 and SR3 channels that we will be adding with the aforementioned model changes.. All new DQ channels are sampled at 512 samples/second.

 

Non-image files attached to this report
Comments related to this report
brian.lantz@LIGO.ORG - 17:07, Monday 06 October 2025 (87331)

I have updated the MEDM screens to include the Length estimator, and I've fixed a few little things along the way.
You will need to $ svn up the  ...userapps/trunk/sus/common/medm/ directory to get the changes

I've updated these screens:

sus/common/medm/

   hxts/SUS_CUST_HLTS_OVERVIEW_W_EST.adl
   estim/ESTIMATOR_OVERVIEW.adl
   estim/FADE_CONTROL.adl
   estim/CONTROL_6.adl

 

updated the SUS_CUST_HLTS_OVERVIEW_W_EST.adl screen
- fixed the indicator for the estimators. Green = ON, grey = off
- added Len estimator
- moved things just a bit so that everything fits
- left the 3 estim indicators as separate buttons because they launch separate related displays.

updated ESTIMATOR_OVERVIEW.adl
- fixed channel names for the indicator on the fader switch (was ...SWITCH_FADE_blah_blah_MON, now is ...SWTICH_MON_blah_blah)
This model change happened a while ago. I guess we missed the MEDM update then

fixed the FADE_CONTROL.adl screen with new names per the ESTIMATOR_OVERVIEW

        (these are in revision 33320)

I also fixed the state indicators in the CONTROL_6 screen and the ESTIMATOR_OVERVIEW screen

The indicator is GREY if the output button is OFF
In the MEDM text file it looks like this:

"basic attribute" {
        clr=7
        }
"dynamic attribute" {
        vis="calc"
        calc="(A&1024) == 0"
        chan="$(IFO):SUS-$(OPTIC)_M1_EST_$(DOF)_FUSION_MODL_SUSP_T_2GAP_SW2R" 

This needs to be the top layer.

if the output is ON, then the display is green/ red if the state is good/bad.

The state indicator updates to the MEDM repo are -r 33321 for the CONTROL_6 screen and -r 33322 for the ESTIMATOR_OVERVIEW screen

share and enjoy!

 

H1 TCS
camilla.compton@LIGO.ORG - posted 12:30, Monday 06 October 2025 (87321)
New HWS Refs Taken at 2W and 60W

Matt, Camilla

As we took new HWS references at 25W last week while troubleshooting HWS (87234, 87252), today we tried to take new references while at 2W today. I did this after the green beams were shuttered around CHECK_VIOLINS_FOR_POWERUP.

However ITMX signal looked very noisy, so Matt and I removed 3 dead pixels, following the wiki. For this to take effect we needed to again take new references, so we said this at 60W just for ITMX. The reported spherical power diopters shouldn't be trusted for ITMX, but relative change in diopters will be fine.

H1 General
ryan.short@LIGO.ORG - posted 12:09, Monday 06 October 2025 (87319)
H1 Back to Observing

H1 is back to observing as of 19:06 UTC after dropping at 15:30 UTC for planned commissioning. There was a lockloss during that time, possibly from commissioning activities, that was simple to relock from after running an initial alignment.

H1 TCS
ryan.crouch@LIGO.ORG - posted 11:30, Monday 06 October 2025 (87315)
TCS Monthly Trends

Last checked in alog86721, closes FAMIS28465.

The CO2s look fine although the flow for ITMX seems more variable than ITMY.

For the HWSs ITMX_SLEDPOWERMON is trending downwards, it passed the scope cursor Y=1mW on 9/17/25 ~10:21 UTC. ITMY is also trending downward, as they both were during the last check. From the 10th to the 16th the HWS spherical power dropped, which tracks as starting due to the power outage.

Images attached to this report
H1 ISC
matthewrichard.todd@LIGO.ORG - posted 11:17, Monday 06 October 2025 - last comment - 07:54, Tuesday 07 October 2025(87316)
Instructions to run a single bounce OMC scan

M. Todd, S. Dwyer


I'm sure there are other sources for this instruction set, but it will serve me later having written this out -- lending some muscle memory hopefully. We are interested in taking several OMC scans over the next couple weeks to estimate mode-matching of various cavities to the OMC in comparison to our models.

Step 1: Suspension Settings for the TMs and PRM/SRM:

Going to sitemap > ASC > IFO Align Compact , you can find shortcuts for each of the suspensions. We will want to take both the ETMs to misaligned as well as the PRM and SRM. If we want to do a single bounce with ITMX, we misalign ITMY and vice-versa.

To misalign an optic from IFO Align Compact, click on the full optic suspension shortcut with the corresponding optic name (e.g. overlapping squares + "ETMX"). At the top of the suspension screen, take the guardian state to misaligned. 

Step 2: Turn on ASC centering loops for the OMs

Going to sitemap > ASC > ASC Overview > DC Centering (middle screen), turn on the inputs to DC3 and DC4 pitch and yaw loops.

Make sure that the inputs to the centering loops start to go to zero and the outputs are not blowing up to infinity.

Then go to sitemap > OMC > OMC Overview > fast shutter and ensure that the status reads open, otherwise, hit open.

Step 3: Turn on OMC ASC and set gains and offsets

Going to sitemap > GRD > ISC Overview find the OMC guardian and take it to ASC_QPD_ON

Going to sitemap > OMC > OMC control, set the MASTER GAIN to 0.02  and bring the LSC offset to the far left ( -50.0 ). 

Step 4: Go out and turn off the sidebands (9, 45, 118 MHz)

Going out to the PSL racks, in the far right stack towards the bottom find the EOM drivers labeled 9MHz and 45MHz and flick the switch on the panel to OFF

Then below the RF Combiner Amplifier, unplug the cable going to the BNC port label 118 MHz.

Step 5: Run OMC scan

An example can be found in my templates /ligo/home/matthewrichard.todd/Templates/omc/20251006_OMC_scan.xml

Open the template with DTT and save it as another copy, naming it with whatever date you are running it plus any notes.

Images attached to this report
Comments related to this report
matthewrichard.todd@LIGO.ORG - 07:54, Tuesday 07 October 2025 (87336)

[Note] This should be done at 10W nominally, so take the LASER_PWR guardian to POWER_10W before running the measurement (ensuring the IMC is locked).

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 09:06, Monday 06 October 2025 - last comment - 12:38, Monday 06 October 2025(87309)
SFI2 temperature with ZM fringe wrapping measurements

Camilla, Sheila

We repeated a test similar to 78125, where we changed the SFI2 temperature and measured fringe wrapping by exciting ZM2 and ZM5.  The temperature of SFI2 changes the backscatter shelf amplitude seen when exciting ZM2, but not ZM5, suggesting that the source of the scattering is upstream of the isolation of SFI2.

Images attached to this report
Comments related to this report
valery.frolov@LIGO.ORG - 09:52, Monday 06 October 2025 (87311)

The attached plot shows ZM2 and ZM5 fringing measurements at LLO. The total OMC current is 50 mA.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 12:38, Monday 06 October 2025 (87322)

Here's a model of our ZM fringe wrapping measurements (the same plot as in 86836, plotted with a model that's roughly emulating Valera's measurement above.  It looks like LLO has about 200pW of interferometer light reaching the filter cavity, but none of the extra scatter we see from before SFI2.

Images attached to this comment
H1 CAL
ryan.short@LIGO.ORG - posted 12:09, Saturday 04 October 2025 - last comment - 15:15, Monday 06 October 2025(87295)
Broadband and Simulines Calibration Sweeps

Following instructions from the TakingCalibrationMeasurements wiki, at 18:33 UTC I dropped H1 out of observing to run the usual calibration sweeps. Calibration monitor and report attached.

Broadband - 18:34:20 to 18:39:38 UTC

Simulines - 18:40:57 to 19:04:04 UTC

File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20251004T184057Z.hdf5
File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20251004T184057Z.hdf5
File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20251004T184057Z.hdf5
File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20251004T184057Z.hdf5
File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20251004T184057Z.hdf5

Images attached to this report
Non-image files attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 15:15, Monday 06 October 2025 (87327)

Comparing the broadband from this Saturday to the previous broadband on Sept 27, there has been a significant change in the calibration uncertainty. We know that there was a small change in the overall calibration since the last model push on 8/28, which could be related to the power outage. However, I can't think of any significant change in the last week that could account for this difference.

We do know that:

  • Kappa C since the power outage is lower by 1%, and,
  • Kappa TST has been increasing  for more than a month now, and is now 3% higher, likely due to charging.

However, both of those bullet points should be accounted for by the TDCFs.

Images attached to this comment
H1 IOO (ISC, PSL)
jennifer.wright@LIGO.ORG - posted 18:17, Friday 03 October 2025 - last comment - 13:04, Monday 06 October 2025(87290)
ISS vertical calibration

Jennie W, Keita,

Since we don't have an easy way of scanning the input beam in the vertical direction, Keita used the pitch of the PZT steering mirror to do the scan and we read out the DC voltages for each PD.

The beam position can be inferred from the pictures setup - see photo. As the pitch actuator on the steering mirror is rotated the allen key which is in the hole in the pitch actuator moves up and down relative to the ruler.

height on ruler above table = height of centre of actuator wheel above table + sqrt((allen key thickness/2)^2 + (allen key length)^2) *np.sin(ang - delta_theta)

where ang is the angle the actuator wheel is at and delta_theta is the angle from the centre line of the allen key to its corner which is used to point at the gradations on the ruler.

The first measurement from our alignment that Keita found yesterday that minimised the vertical dither coupling is shown. It shows voltage on each PD vs. height on the ruler.

From this and from the low DC voltages we saw on the QPD and some PDs yesterday Keita and realised we had gone too far to the edge of the QPD and some PDs.

So in the afternoon Keita realigned onto all the of PDs.

Today as we were doing measurements on it Keita realised we still had the small aperture piece in place on the array so we moved that for our second set of measurements.

The plot of voltage with ruler position and voltage with pitch wheel angle are attached.

Images attached to this report
Comments related to this report
jennifer.wright@LIGO.ORG - 13:02, Monday 06 October 2025 (87323)

Keita did a few more measurements in the verticall scan after I left on Friday, attached is the updated scan plot.

He also then set the pitch to the middle of the range (165mm on the scale in the graph) and took a horizontal scan of the PD array using the micrometer that the PZT mirror is mounted on. See second graph.

Images attached to this comment
jennifer.wright@LIGO.ORG - 13:04, Monday 06 October 2025 (87324)

From the vertical scan of the PD array it looks like diodes 2 and 6, which are in a vertitcal line in the array, are not properly aligned. We are not sure if this is an issue with one of the beam baths through the beamsplitters/mirrors that split the light onto the four directions for each vertical pair of diodes or if these diodes are just aligned wrongly.

H1 SQZ
sheila.dwyer@LIGO.ORG - posted 13:25, Tuesday 23 September 2025 - last comment - 14:13, Tuesday 07 October 2025(86836)
filter cavity length and backscatter

This is an alog I started before the power outage, because we were worried that the filter cavity backscatter was the reason for our intermittent squeezer noise.  (We now realize that the noise we are looking for is not from the filter cavity 87071.)

The overall message is that the filter cavity backscatter seems low compared to DARM, but there is a source of scattered light upstream of SFI2.

Filter cavity length

I've constructed a model of the filter cavity length loop using the foton filters for PRM in the CAL-CS model.  As noted in 78728 we need to modify the analog gains for M3 for FC2.  I've used a filter cavity pole of 34 Hz, and adjusted the sensor gain to get the model to match the measured open loop gain (plot).  The measurement used in that plot has poor coherence below 5 Hz, which explains why the model doesn't seem to fit there. This model also matches the cross over measured by injected at M1 LOCK L well (plot)

The next plot shows the uncalibrated error signal (measured at LSC DOF2 IN1), with the loop correction applied (error_spectrum * (1-G)), and a line which I've added as a crude estimate of sensor noise.  You can see that there seems to be a bump in sensor noise around 100 Hz that isn't included in my rough estimate, I am not sure what that is.  

The next plot shows calibrated length noise

Backscattered power

Using the measurement of excitations on ZM2 in 86778,we can estimate the amount of backscattered light that is reaching the filter cavity.  The DCPD spectra, calibrated into RIN and with the DARM loop removed are plotted here and here with different FFT lengths.  Next time if we do this measurement with a lower frequency and higher amplitude excitation we will be able to use a longer FFT length for the plot and still se

I've made a model of the noise caused by backscattered light using equation 4 (and 5) from P1200155.  The excitation was a 1Hz 100 count excitation into test L, in the osems this showed a peak to peak amplitude of 0.37 um, and to go from optic motion to path length change we need roughly a factor of 4 since ZM2 is at a low angle of incidence and it is double passed.  To match the shelf frequency in the measurement I had to increase the amplitude used in the model by a factor of 3.4.  Using a QE of 100% gives a PD responsivity of 0.858 A/W, and 46.6mW of power on the OMC PDs.  This model doesn't include any phase modulation from any other elements in the optical path, but the real measurement does, which is why the measurements shows a nice shelf but the model shows a series of peaks when I use a longer FFT. I think would be less apparent if we make the measurement with a lower frequency higher amplitude excitation next time. 

The result of this shows that we have 12 pW of scattered light passing ZM2, since backscatter that reaches the filter cavity should all be reflected back towards the IFO along with the squeezing this means that we have 12 pW of scattered carrier from the OFI reaching the filter cavity.  Comparing this to table 1 of T1800447 this is a lower scattered light power reaching the diodes than expected, for a similar level of carrier light reaching the DC PDs, which suggests that all three Faradays are providing the isolation level expected or slightly better.  When driving ZM5, we get 12 nW of power scattered back to the interfometer, suggesting that there is a scattering source where we would not expect one to be.  This seems most likely to be upstream of SFI2, since we only expect nW of total scattered light downstream of SFI2.  If you are interested in looking at a diagram of possible scatters there is a VIP layout here, the beam which leaves B:M5 goes to a PD mounted on the ISI which is called B:PD1 and is intended to monitor light scattered from the OFI towards the squeezer.  

Coupling and noise projection

The last two plots here show the results of a filter cavity noise injection, similar to what Naoki did in 78579.  This suggests that this noise is large enough to include in our noise budget, but not nearly large enough to explain the excess noise we see in DARM when the filter cavity error signal is seeing extra noise. 

The code and data to produce this are in sheila.dwyer/SQZ/FilterCavity/fc_lsc_model.py

Images attached to this report
Comments related to this report
sheila.dwyer@LIGO.ORG - 11:29, Monday 06 October 2025 (87318)

I posted this as a comment on the wrong alog on Friday, adding it here now.  Also see follow up measurements with changes to SFI2 temperature, and the comparison measurement from LLO 87309

Power level heading towards HAM7 from OFI:

The power on the DCPDs is 47mW, and there is 12pW retro-reflected off the filter cavity, so the total isolation provided by OFI + SFI2 + SFI1 is 2.5e-10 in power ratio, or 96dB.  The OFI isolation ratio was measured to be 43dB in 79379.  If this is true it would imply that one of the SFIs is providing less than the 30dB isolation assumed in T1800447, and we should have 2uW of carrier light headed towards SFI2.

Our readback of the 1% pick off of light from the interferometer heading towards SFI2, B:PD1 (OFI PD A) says that we have 0.03mW on it, meaning 3mW from the IFO going towards SFI2, about 1mW of this would be carrier based on (87114),which seems too high.  

The responsivity of this PD was checked in 60284, and later double checked because it seemed low (the settings are still the same).  The similar PD OFI PDB has a measured responsivity of 0.25A/W and the excelitas website lists a peak responsivity of 0.6A/W at 850nm for these PDs.  (ffd-200h-si-pin) If we think that this calibration was mistaken and the real responsivity is more like OFI PD B, 0.25A/W, there is 0.72 mW of light from the OFI heading towards SFI2,  ~240 uW of carrier, the OFI isolation would only be 23dB, and the SFIs must be providing something like 36 dB each.  

Reflectivity:

If my interpretation of the fringe wrapping measurements into power are correct (12 nW of power is retroreflected from the path that includes ZM5), we are reflecting 50ppm of the carrier scattered toward HAM7 using the (recalibrated) 240uW value from OFI PDB, or 0.6% if we believe the isolation ratio measurement for the OFI and use the 2uW value.  B:BS1 is a 1%, so the maximum reflectivitiy we could get from scatter in the B:PD1 path would be 0.01%.  This means that the B:PD1 path can't explain the reflectivity needed if there is 2uW headed towards HAM7, and even if there is 240uW heading towards HAM7 this PD seems unlikely to explain the scatter, since it would need to reflect half the light that's incident on the PD.  Camilla did alog the check of the alignment (and the beam dump catching the retro-reflection off this diode: 65006

sheila.dwyer@LIGO.ORG - 14:13, Tuesday 07 October 2025 (87350)

Daniel looked at some of the excelitas website catalog and he thinks that our measurement of 0.06A/W could be a reasonable responsivity for the OFI PD A. LLO's responsivity for this PD is set to 0.065A/W.  

This morning we opened the squeezer beam divererter while Matt was doing single bounce OMC scans, (87342) when there was 9.25W incident on PRM.  

9.25W on PRM * 0.0299 PRM transmission * 0.25 (2 BS passes) * 0.03234  = 22.4mW expected arriving at OFI.  AS_C_NSUM is calibrated into Watts arriving at HAM6, which says 22.9mW for this time.  

OFI PD A reports a 1.1uW increase in measured power when the beam diverter opens (first attachment), meaning that there is about 100uW from the OFI sent to HAM7 in single bounce, or 0.4% of the light arriving at the OFI is sent to HAM7 according to this PD, or 23dB of isolation for this port.  The 43dB measurement I referenced above is isolation for HAM6 scatter, and it doesn't apply to the light sent to HAM7.

So, this suggests that perhaps we can trust this OFI PD readback, and perhaps there is about 1mW of carrier sent to HAM7 when we are in full lock.  This means that we need a reflectivity of 10ppm to explain our fringe wrapping measurement;  if the scattering happens behind the 1% beam splitter it should have a reflectivity of 10% to explain what we see.  

LLO has 50mA on the OMC PDs, compared to 40mA here, their OFI PD A reports 0.01mW power in full lock, 3 times less than what we see here.  

Images attached to this comment
H1 ISC
elenna.capote@LIGO.ORG - posted 19:20, Wednesday 10 September 2025 - last comment - 14:40, Monday 06 October 2025(86704)
Estimating arm power from the HARD pitch modes

With help from E. Bonilla, M. Todd, and S. Dwyer

Some background:

The HARD loop open loop gain transfer function can provide information about the arm power. The radiation pressure within the arm cavity adds an additional torsional stiffness term that stiffens the hard mode and softens the soft mode, causing the eigenmodes of the suspension to shift up (hard mode) or down (soft mode) in frequency.

We can measure this shift in frequency by taking the open loop gain of the hard loop, and dividing out the known digital controller to measure the high power plant hard plant.

The highest frequency pole in the suspension plant is the most interesting to study, as this is the hard mode that is most susceptible to the arm power. Edgard's technical document on the Sidles Sigg modes in the BHQS, T2300150, gives a good explanation as to why. Note that his document covers the BHQS design, which differs from the QUAD design in several respects, but the underlying physics is the same. Figure 2 on page 3 demonstrates the behavior of the suspension eigenmodes with respect to increasing intracavity power, demonstrating that the highest frequency hard mode will shift in frequency the most compared to the other modes (the opposite is true for the soft mode). Figure 2 will appear different for the QUAD model in pitch due to the large cross coupling of length to pitch (which mixes length modes into the shifting as well, yuck).

Some equations:

Following his document, we can use Equation 4 as a first order approximation for the hard mode frequency:

f_hard = 1/2*pi * sqrt(k_4 + k_hard / I_4)

where k_4 is the torsional stiffness of the fourth eigenmode of the QUAD, k_hard is the torsional stiffness induced by the radiation pressure torque and I_4 is the moment of inertia of the fourth eigenmode of the QUAD.

k_hard can be shown to depend on arm power via:

k_hard = P_arm *_L_arm / c * gamma_hard

where gamma_hard = ((ge + gi) + sqrt((ge - gi)^2 +4)) / (ge*gi - 1)

and P_arm is the arm cavity power, L_arm is the arm cavity length, and ge,i is the g factor of the ETM or ITM (ge,i = 1 - L_arm / Re,i)

The arm power will then depend on the following:

The last point is what makes this measurement somewhat degenerate; we know that the radii of curvature of the test masses changes from the design value due to the applied ring heater power and the absorbed power from self heating. However, Matt has been working lately to understand what these values are by checking the higher order mode spacing and finesse models. If we use the higher order mode spacing, and known measurements of the absorbed power from the ITM Hartmann wavefront sensors, we can remove some of the degeneracy.

Esimating the test mass RoCs:

In alog 86107, Sheila estimates the location of the X and Y arm higher order modes:

Using ge*gi = cos^2(pi*f_HOM/FSR) I find that the ge*gi for the X arm is 0.8158 and the Y arm is 0.8178

Matt reports that the ITMX absorbed power is 160 mW and ITMY is 140 mW. His new estimate for the coupling of the self heating is -20.3 uD/W for the ITMs (G2501909, slide 11). The ITM radius of curvatures are reported on galaxy as 1940.3 m for ITMX and 1940.2 for ITMY.

The ITM defocus when we are in the hot state can be calculated via

D = Dc + B * P_rh + Ai * P_self

where Dc = 1/R_cold, B is the ring heater coupling factor in D/W, P_rh is the known ring heater power applied to the test masses, Ai is the coupling above, and P_self is the absorbed power reported above

This gives the hot RoCs for the ITMs as 1949.94 m for ITMX and 1950.96 m for ITMY.

Using the product of the g factors above, we can then estimate the hot RoCs for the ETMs as 2246.54 m for ETMX and 2243.08 m for ETMY.

Calculating the arm power:

These numbers give the following g factors:

Mirror g factor
ITMX -1.0485
ITMY -1.0474
ETMX -0.7781
ETMY -0.7808

Using the QUAD model parameters I found in /ligo/svncommon/SusSVN/sus/trunk/QUAD/Common/MatlabTools/QuadModel_Production/h1itmy.m and some help from Edgard, I found:

I_4 0.419 kg m^2
k_4 19.7118 Nm

I remeasured both the CHARD pitch and DHARD pitch transfer functions. I divided out the current controllers and used the InteractiveFitting program written by Gabriele to fit the plant. Both measurements give the same result: f_hard = 2.603 Hz

Combining all of the above numbers gives:

P_arm = 332.1 kW, when using the X arm parameters

P_arm = 328.3 kW, when using the Y arm parameters

To be clear, Sheila and I don't think these are the arm powers in the X and Y arm, since the f_hard value will depend on the average power between the arms in the CHARD and DHARD transfer functions. Instead, these values provide a possible range of arm powers.

I am currently reporting these values without any uncertainty (bad!), since the uncertainty will depend on the measurement uncertainty of the OLG, the HOM spacing, and self heating estimate. Once I have a better sense of all of these uncertainties, I will update here.

Furthermore, there are higher order corrections that can be applied to the estimate of the hard mode frequency. For example, Eq 22 in Edgard's document estimates the additional effect due to the effective spring between the PUM and test mass. However, that estimate is not exactly correct for the QUAD model, since the higher order correction will need to account for the length-to-pitch cross coupling. The yaw model may be simpler to use, so I plan to remeasure the HARD yaw OLGs and use them to calculate another arm power estimate.

Overall, putting this result in the context of our other arm power estimates is interesting:

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 14:40, Monday 06 October 2025 (87325)

I stated that it may be simpler to use the yaw mode measurement to calculate arm power, however that is not possible. Attached is a figure that demonstrates the hard and soft yaw mode shift with arm power using the QUAD model (Fig 68 in my thesis). We believe we are somewhere in the 300-400 kW region of this plot. At these powers, the yaw hard and soft modes have not been fully decoupled from each other, which means that the approximation that we can use this mode to calculate the arm power is not valid. Edgard's technical document goes into further detail about this approximation. This is validated from the open loop gain measurements I made for DHARD and CHARD Y here, which show that the mode is still near 3 Hz.

However, the pitch mode has fully decoupled, so the values I report above are valid, excepting whatever higher correction is required from length-to-pitch cross coupling.

Incidentally, this probably means we could damp the yaw hard mode from the top mass at this power, but that is an entirely different discussion.

Images attached to this comment
Displaying reports 201-220 of 85053.Go to page Start 7 8 9 10 11 12 13 14 15 End