Displaying reports 821-840 of 85658.Go to page Start 38 39 40 41 42 43 44 45 46 End
Reports until 12:30, Monday 06 October 2025
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
LHO VE
david.barker@LIGO.ORG - posted 11:18, Monday 06 October 2025 (87317)
Mon CP1 Fill

Mon Oct 06 10:05:25 2025 INFO: Fill completed in 5min 22secs

 

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 SUS (OpsInfo)
elenna.capote@LIGO.ORG - posted 10:53, Monday 06 October 2025 (87314)
Roll mode damping notes

Ryan S, Elenna

Today the roll mode was a bit high, and was rung up further during the SFI testing that Sheila and Camilla ran. We have found its best practice to turn the roll mode damping off when these injections are happening.

Once the injections finished, we turned the damping back on, and it seemed like the mode was either not damping or getting slightly worse. We turned the damping off for seven minutes, and saw that the mode clearly rung up much faster. So, we reengaged the damping, and then tried a slightly higher gain of 42 and then 45 and saw that the mode actually did start to come back down.

So, in short, if a gain of 40 is not bringing the mode down fast enough, it seems like we can at least tolerate a gain of 45. I can't remember if this is an SDF or not, but I know it is guardian controlled to be 40. Tagging opsinfo in case this is useful information.

H1 IOO (ISC, PSL)
jennifer.wright@LIGO.ORG - posted 10:48, Monday 06 October 2025 (87276)
Coupling measurements from the 30th September with higher dither amplitude

Rahul, Jennie W, Keita

 

Just catching up on historical alogs

We increased the dither amplitude to 1Vpp to give us better coherence in our horizontal input dither -> PD array RIN measurement compared to our previous alog (#87140).

We got pretty good coherences on PDs 2,3 5 -8. All of these measured between about 0.1 per m and 30 per m RIN.

After showing the results to Keita he got us to do two more measurements where we changed the input alignment yaw either side of the nominal to see if this had the expected results on the magnitude and phase of the transfer function.

The results are shown in the attached graphs, PD number is on the x axis and Magnitude, phase and coherence of each measurement are on the 3 y-axis. The measurements with the input aligned are shown in blue.

To get the two other measurements I looked at the two leeft-most diodes on the array (I think these are 4 on the top and 8 on the bottom) with the beam viwer as Rahul moved the PZT steering mirror in yaw.

For these three measuremenrts Keita pointed out that the discrepancy between the diodes phases didn't make much sense.

 

 

Images attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 09:53, Monday 06 October 2025 (87312)
PSL 10-Day Trends

FAMIS 31106

PMC REFL has been continuing to increase, but nothing much of note this week otherwise.

Images attached to this report
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
LHO General
ryan.short@LIGO.ORG - posted 07:39, Monday 06 October 2025 (87307)
Ops Day Shift Start

TITLE: 10/06 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.09 μm/s 
QUICK SUMMARY: H1 has been locked for 37.5 hours. Commissioning time scheduled today from 15:30 to 18:30 UTC.

H1 General
anthony.sanchez@LIGO.ORG - posted 22:07, Sunday 05 October 2025 (87306)
Sunday Ops Eve Shift End

TITLE: 10/06 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY:
H1 has been locked for 28 hrs, currently Observing.
I Have nothing else to report. 

LOG:
No Log

 

H1 General
anthony.sanchez@LIGO.ORG - posted 16:35, Sunday 05 October 2025 (87305)
Sunday Ops Eve Shift Start

TITLE: 10/05 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 16mph Gusts, 10mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.11 μm/s 
QUICK SUMMARY:
H1 is Locked and Observing & I've got no plans to change that.

LHO General
ryan.short@LIGO.ORG - posted 16:30, Sunday 05 October 2025 (87304)
Ops Day Shift Summary

TITLE: 10/05 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Very quiet day with H1 observing throughout; nothing of consequence to report. H1 has been locked for 22.5 hours.

LHO General
ryan.short@LIGO.ORG - posted 12:02, Sunday 05 October 2025 (87303)
Ops Day Mid-Shift Report

State of H1: Observing at 158Mpc

H1 has been locked for 18 hours; quiet morning so far with no drops from observing.

LHO General
ryan.short@LIGO.ORG - posted 16:30, Saturday 04 October 2025 - last comment - 09:06, Monday 06 October 2025(87297)
Ops Day Shift Summary

TITLE: 10/04 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY: H1 remained lock the whole day with only a few drops from observing, most of which were intentional. After the squeezer relocked, the range was a bit low, but the SQZ angle servo eventaully brought it back up over the course of about an hour. I probably could have run a SQZ angle scan right before going back into observing to fix the range sooner. H1 has now been locked for 27 hours.
LOG:

Comments related to this report
camilla.compton@LIGO.ORG - 09:06, Monday 06 October 2025 (87310)SQZ

This SQZ Lockloss was caused by the OPO PZT running out of range. Plot attached, when the OPO relocked with the PZT at ~100V, the SQZ angle servo worked as expected to bring the range back. 

Images attached to this comment
H1 ISC
elenna.capote@LIGO.ORG - posted 11:58, Thursday 02 October 2025 - last comment - 11:57, Monday 13 October 2025(87260)
Camera spot calibration

Today I began calibrating the camera servo signals into spot positions. I ran the A2L script at the nominal camera spot positions. Then, I changed the camera offset and waited for the camera servo to converge. Then I remeasured the A2L gain. Using the a2l_lookup function in /opt/rtcds/userapps/release/isc/common/scripts/decoup/BeamPosition the A2L gain can be converted into a spot position in mm. This is a slow process so it will take time to get the conversions for all.

  Camera offset A2L gain Conversion
ETMY Pitch start: -230, end: -231 start: 5.62, end: 5.92

(-23.2 mm - -21.8 mm)/-1ct 

= 1.4 mm/ct

ITMX Pitch start: -230, end: -231 start: -0.45, end: -0.56

(6.46 mm - 5.96 mm)/-1ct  

= -0.5 mm/ct

 

Comments related to this report
elenna.capote@LIGO.ORG - 10:23, Monday 06 October 2025 (87313)

I continued today following the same process stated above.

  Camera offset A2L gain Conversion
ETMX P start: -173, end: -172 start: 3.04, end: 2.92

(-9.38 mm - -9.93 mm)/ 1ct 

= 0.55 mm/ct

ETMY Y start: -349.5, end: -348.5 start: 1.41, end: 1.06

(3.90 mm - 5.18 mm) / 1ct 

= -1.28 mm/ct

ETMX Y start: -422, end: -421 start: 4.85, end: 4.68

(17.22 mm - 17.84 mm)

= -0.62 mm/ct

elenna.capote@LIGO.ORG - 11:57, Monday 13 October 2025 (87442)

I reran the ITMX beam spot calibration following the same method described above, but this time I checked how the beam spot moved on both ITMX and ITMY when I changed the BS camera offset. Turns out, they give the same answer, so that's good.

  Camera Offset A2L gain Conversion
ITMX P (ITMY P) start: -230 ct, end: -231 ct start: -0.45 (0.19), end: -0.55 (0.09)

(6.41 mm - 5.96 mm)/-1 ct

= -0.45 mm/ct

ITMX Y (ITMY Y) start: -236 ct, end: -237 ct start: 3.18 (-2.75), end: 3.06 (-2.63)

(11.26 mm - 11.70 mm)/ -1ct

= 0.44 mm/ct (-0.44 mm/ct for ITMY)

 

H1 SQZ
camilla.compton@LIGO.ORG - posted 11:24, Monday 29 September 2025 - last comment - 08:51, Monday 06 October 2025(87197)
ZM2,5 Fridge Wrapping with No SQZ light and Different Alignments on OFI_PD_A

Sheila, Camilla. Saved to camilla.compton/Documents/sqz/templates/dtt/Fringe_wrapping.xml

ZM2,5 Fridge Wrapping with No SQZ light

As Sheila suggested in 86836, the amount of backscatter we are seeing from SQZ should be due to light from the IFO being backscattered rather than any excess SQZ light. To confirm this I took SQZ DOWN, mis- aligned FC, blocked all three SQZ beams on SQZT0 and re-opened the beam-diverter so that the IFO light could get into HAM7 but there was no SQZ generated light. The ZM2 and ZM5 scatter shelves were the same in both this and the nominal SQZ configurations, confirming all backscattered light is coming from the IFO. Plot attached. This plot does show our ZM5 scatter has increased since 2024, ZM2 is the same.

I did the same with the 30Hz injection too, saved to Fringe_wrapping_nosqz.xml, refs 0-8 are no sqz beams, refs 9-17 are nominal FDS. Plot attached, if anything, the shoulders of the 30Hz peak are larger with no sqz beams, so again, there is no difference. 

ZM2,5 Fridge Wrapping with Different Alignments on OFI_PD_A

In FRS # 35457 and 87071, we theorized that the backscatter could be off the OFI_PD_A which we shows out beam is clipping, when we change the alignment to this PD using ZM4/5, we change the level of light on OFI_PD_A, showing we are clipping and not centered on the PD, but this also changes the level of SQZ so it's hard to compare. Unsure if there's a real difference, plot attached and ndscope. It's possible that with more light on PD_A (less clipping) there is a more scatter and a secondary ZM5 scatter shelf ~25-40Hz. Would want to repeat or misalign more to confirm. 

References on Fringe_wrapping.xml No Injection ZM5 Inj ZM2 Inj
Nominal FDS
(ZM5 Yaw -460urad, -4.6dB, OFI_PD_A = 0.031)
0 1,2 3,4
No SQZ light, BeamDiv Open to IFO 5 6,7 8,9
FDS, ZM5 Yaw -510urad, -3.4dB, OFI_PD_A = 0.024 10 11,12 13,14
FDS, ZM5 Yaw -440urad, -3.4dB, OFI_PD_A = 0.033 15 16,17 18,19

Other ideas that haven't been done yet: change the temperature of SFI2 and repeat backscatter measurements, repeat above with increased alignment changes the OFI_PD_A changes. 

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 14:45, Monday 29 September 2025 (87203)

Elenna realized while I was doing this that we should turn off the 13Hz Roll mode damping before injecting into ZM2/5 as this increased DARM noise might confusing the damping signals. 

camilla.compton@LIGO.ORG - 08:51, Monday 06 October 2025 (87308)

To turn off the roll mode damping: sitemap > SUS > Bounce Roll > DAMPING Filters. Then turn the gain of the one damping to zero (already should be a 10s Tramp).

Images attached to this comment
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
Displaying reports 821-840 of 85658.Go to page Start 38 39 40 41 42 43 44 45 46 End