Displaying reports 1321-1340 of 85695.Go to page Start 63 64 65 66 67 68 69 70 71 End
Reports until 07:58, Thursday 11 September 2025
H1 General
anthony.sanchez@LIGO.ORG - posted 07:58, Thursday 11 September 2025 - last comment - 10:14, Thursday 11 September 2025(86849)
Thusday Ops Day Shift Morning Report.

TITLE: 09/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 136Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 9mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.15 μm/s
QUICK SUMMARY:
Range seems low, but SQZ_man is in FRQ_DEP_SQZ.
The SQZ ASD plot on nuc 33 wasn't running and when I logged in to hit start, it gave me a connection error.
After a reboot of Nuc 33, High Freq SQZn could be better looking.

The H(t) Triggers screen looks WILD... some frequencies have had  issues all night.

 

Images attached to this report
Comments related to this report
camilla.compton@LIGO.ORG - 10:14, Thursday 11 September 2025 (86853)SQZ

We got the high frequency squeezing back to it's nominal -4.5dB as noticed that ZM6 PIT had changed 250urad in the power outage and the SCAN_ALIGNMENT_FDS state didn't have the range to bring it back. Nothing else changed more than ~30urad. I moved ZM6 it back to it's old alignment and reran SCAN_ALIGNMENT_FDS, then ran SCAN_ANGLE_FDS and checked that H1:SQZ-ADF_OMC_TRANS_SQZ_ANG was close to 0 (it was -1.5) before going back to FREQ_DEP_SQZ, which turns back on the ADF angle servo.

Our range than increased to 145MPc.

H1 DetChar (DetChar, ISC)
derek.davis@LIGO.ORG - posted 07:52, Thursday 11 September 2025 (86848)
Extreme rate of glithcing correlated with IMC WFS channels

Related to the poor range challenges reported in 86844, there is an extremely high rate of glitches, close to 1 glitch with SNR > 8 every 10 seconds, an increase in rate of 2 orders of magnitude compared to the day before. The first HVeto run of the day shows that H1:IMC-WFS_A_DC_YAW_OUT_DQ is correlated with these glitches at a significance of 850 (10-20 is the usual threshold for an "interesting" significance) and witnesses 70% of all of the glitches in the most recent lock. 

I've attached an example of these glitches in strain data and the mentioned IMC WFS channel, showing that there is a clear visual correlation between them. 

Other channels that are correlated with these glitches are H1:LSC-MCL_IN1_DQ, H1:IMC-DOF_4_P_IN1_DQ, and H1:LSC-POP_A_RF9_I_ERR_DQ (among many other IMC, LSC, ASC, and PSL channels). The full HVeto results can be found here

One additional observation is that the rate of these glitches is so high that it is possible they could be subtracted post-facto with standard linear subtraction techniques.

Images attached to this report
LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 22:44, Wednesday 10 September 2025 (86847)
OPS Eve Shift Summary

TITLE: 09/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Corey
SHIFT SUMMARY:

IFO is in NLN and OBSERVING (quite poorly) - We're going to OBS with low range (alog 86844)

Post outage recovery allowed us to get into NLN but as we got there, our range was sitting at a cool 103 MPc with a few culprits identified by Elenna and Sheila.

Getting to NLN was easy enough with the one issue being a shutter test guardian issue that was fixed after a few inits and another being the EY HV being off, causing a lockloss when it was turned back on (this happened at OMC_WHITENING). alog 86842. Elenna and Camilla helped me reconcile ~100 SDF diffs (alog 86843 and attached)

SQZ:

SQZ was and still is bad but we managed to improve it by running opo temp and ang adjust (manual and auto) to improve the range up to 130 MPc. Unknown why it's still not the same as before.

IMC:

The IMC was the other point of discussion but we don't really know if this is a problem. Sheila and Elenna were stepping through the IMC PZT whilst wathcing MC_REFL (which looked different). Ultimately we still don't know.

We do know that our calibration is fine so it's just high noise that is keeping us 25 MPc below our usual. This noise seems to be from everywhere according to the coherence checks (attached)

Comissining will continue tomorrow to fix whatever is causing this. On the bright side, high violins damped while we were locked.

LOG:

 

Images attached to this report
H1 ISC (IOO, OpsInfo, SQZ)
elenna.capote@LIGO.ORG - posted 22:35, Wednesday 10 September 2025 - last comment - 22:41, Wednesday 10 September 2025(86844)
Going to observing with poor range

Our range is very low even with squeezing (about 130 Mpc). There seems to be some problems with squeezing, but there is significant jitter coherence from 10-40 Hz that is abnormal. The noise on the IMC WFS has increased by about 2x at low frequency, but decreased at high frequency, so there is much more power on them now. Sheila trended IMC refl and MC2 trans and IMC refl is higher than normal, MC2 trans is lower than normal. We can also see that the MC refl camera "looks different" (calling this "tea leaf reading"). The PRCL and SRCL coherence is also much higher than normal.

"It just looks like there is not much squeezing"- Sheila

We've tried some different things to move the IMC alignment around, but nothing seems to be working and we are tired. Our plan is to come back to this in the morning.

We think that something from today's power outage has caused these problems, but we are not sure what.

Screenshots include:

low range coherence check from Ibrahim

IMC WFS spectrum comparison (blue is yesterday, red is now)

IMC PZT change

sqz comparison change this also shows that squeezing is not causing the low frequency extra nosie

Images attached to this report
Comments related to this report
elenna.capote@LIGO.ORG - 22:39, Wednesday 10 September 2025 (86845)

Here is a longer measurement of the IMC WFS and LSC coherence with calib strain. I can't get the coherence to run with calib strain clean right now. I'm not sure how good the cleaning is performing, but I do know that the strain and clean channels looks slightly different bove 100 Hz, so some jitter is being removed.

Images attached to this comment
sheila.dwyer@LIGO.ORG - 22:41, Wednesday 10 September 2025 (86846)

looking at IMC REFL DC, at 2W was 60% higher after the power outage than before, MC2 trans is lower by 2% than before the power outage.

At 60W input power, IMC REFL is 190% of what it was before the power outage, MC2 trans is 96% of what it was. 

We trended MC suspensions and PZT drive, the suspension are within the range of where they were before the power outage but the PZT is different.  We tried opening the PZT loop (MC2 trans to PZT), increasing the MC WFS gain from 0.04 to 0.16, and walking the PZT offet.  It seemed like moving this in either direction in yaw made things worse, moving the pZT back towards it's old position in pitch also made things worse. 

One suspicion could be that the beam from the PSL has shifted in alignment.

H1 ISC (CDS)
elenna.capote@LIGO.ORG - posted 20:31, Wednesday 10 September 2025 (86843)
SDF reconciliation for observing

We had several SDF diffs. I think most of the issues could have been due to the safe being different than observe and the reboot from the power outage restoring old values. Specifically, the OAF online cleaning model coefficients for the jitter cleaning were all changed. I trended back the values and it they had taken on the old coefficients from before I retrained the jitter. Similar issue with TCS sim, which Matt had updated recently.

However, after I accepted the OAF and TCS sim values in OBSERVE, I loaded the safe.snap to see if I could update them in safe. However, the safe.snap file did not have the same differences as in observing. The OAF model had 71 diffs from the jitter coefficients, but in safe there are 6 diffs and none of them are the jitter coefficients.

Meanwhile, if I do the same thing for the TCS sim model and load the safe.snap, there are NO diffs.

So I am wondering if this a weird "burt restore" issue due to the power outage and whatever file was restored was very old and/or wrong. Tagging CDS so we can figure out what happened.

Camilla advised Ibrahim to revert some of the diffs in the HWS model.

We also had to change the PZT offset for the IMC PZT during the recovery process, which we had already accepted in safe so I also accepted in OBSERVE.

Attached are the TCS sim and ASCIMC acceptances. I didn't screenshot the OAF acceptance because the list was very long (but now I wish I had so we could figure out what went wrong with the restore).

Images attached to this report
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
H1 ISC (SUS)
elenna.capote@LIGO.ORG - posted 18:51, Wednesday 10 September 2025 (86842)
ETMY HV was off, caused lockloss turning it on

As we got back up towards observing and entered the OMC_WHITENING state, I saw a guardian message that "ETMY HV ESD appears off". Looking at the suspension screen, I saw that even though the ETMY bias voltage was set, the H1:SUS-ETMY_L3_ESDAMON_DC_OUT16 channel was reading zero. Trending it back, I saw it should be reading something like 200.

Ibrahim, Keita, and I decided that the button we should probably press was the "HV ON/OFF" switch at the bottom of the ETMY screen which is the H1:SUS-ETMY_BIO_L3_RESET switch. Keita said "this is probably going to cause a lockloss" and I said "yeah probably" and then I pressed it and it caused a lockloss. However, I don't think we could have gone into observing like that, because that bias voltage is set to cancel out ground noise. In hindsight, Keita and I realized we should have probably: 1) set the bias offset to zero, 2) turned on the HV switch, 3) then slowly ramped up the ETMY ESD bias offset to the nominal value.

H1 IOO
sheila.dwyer@LIGO.ORG - posted 16:38, Wednesday 10 September 2025 (86841)
IMC locking difficulty after power outage: MC2 whitening in error (and many other whitening chassis)

writting this down for future people recovering from power outages:

We weren't able to lock the IMC, the alignment was not good but not terrible.  With 2 Watts into the IMC, H1:IMC-TRANS_OUT16 was about 10000 counts, while the IMC was well aligned it was 11000 counts.  MC2 trans NSUM however was about 6 counts, well it should be 200-300 counts. 

On the whitening screen for MC2 trans (LSC> Whitening) there were errors Invalid data chn (4,3,2,1).  Elenna found this alog by searching the error message, 12120, Daniel Patrick and Fil reproduced a solution like this. 

 

LHO General
thomas.shaffer@LIGO.ORG - posted 16:32, Wednesday 10 September 2025 (86838)
Ops Day Shift End

TITLE: 09/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Locked for about 10 hours when a brief power outage on site took everything down. We have been in recovery since (see list of alogs below). We are currently getting the IMC to lock after realizing that there was an issue with the whitening and Daniel logged into Beckhoff to fix it.

Power outage alogs:

LOG:

LHO General
ibrahim.abouelfettouh@LIGO.ORG - posted 15:59, Wednesday 10 September 2025 (86840)
OPS Eve Shift Start

TITLE: 09/10 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.11 μm/s
QUICK SUMMARY:

IFO is DOWN due to a POWER OUTAGE

We're still recovering H1, with the IMC being a big hiccup in recovery.

H1 CDS
filiberto.clara@LIGO.ORG - posted 15:57, Wednesday 10 September 2025 (86839)
CDS EE Power Outage Notes

1. Both corner station HV interlocks tripped. Reset. The Fast Shutter, HAM6 PZT, and ITM ESD high voltage enabled.
2. PSL and SQZ high voltage enabled
3. Safety Laser Interlock System tripped, Reset. Lasers enabled.
4. ETMX ESD HV interlock tripped. Reset, HV enabled
5. ETMY ESD HV was found powered on
6. Found 2 ETMY SEI ISI Coil Drivers with overtemp errors. Reset button on front panel cleared all faults. Need to check all ECRs have been applied to chassis.
7. Jim reported issues bringing back ETMX HEPI. Normal power OFF/ON did not bring main pump controller panel online. Asked Patrick to check the Beckhoff software, no issues found. Unit eventually powered on when the ON button was activated during troubleshooting.
8. EY Pulizzi was found unresponsive and power cycled. Erik restarted code. This enabled power to WIFI and ITMY camera

Images attached to this report
H1 General
ryan.crouch@LIGO.ORG - posted 15:40, Wednesday 10 September 2025 (86826)
SIte power outage recovery notes
Non-image files attached to this report
H1 PSL
ryan.short@LIGO.ORG - posted 14:41, Wednesday 10 September 2025 (86835)
PSL Recovered Following Power Outage

The PSL is fully recovered with all subsystems and watchdogs enabled following the site power outage earlier today. I'll add more details in a comment to this entry later.

H1 SUS
ryan.crouch@LIGO.ORG - posted 14:36, Wednesday 10 September 2025 (86834)
Sliders restored post Power outage recovery

I restored all the sliders using my restore script on IFO_ALIGN_COMPACTEST to before the glitch, 19:00 UTC.

Images attached to this report
H1 SEI
jim.warner@LIGO.ORG - posted 12:46, Wednesday 10 September 2025 - last comment - 15:19, Wednesday 10 September 2025(86829)
Connecting to h1hpipumpctrll0 after power outage

I had some difficulty connecting to the corner hepi pump controller after the power outage. The workstations have gotten too far ahead of the old Athena controller, so when I attempted to ssh to the pump station, I got:

Unable to negotiate with XX.XXX.X.XX port 22: no matching key exchange method found. Their offer: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1

I had to add some options to ssh:

ssh -oKexAlgorithms=+diffie-hellman-group1-sha1 -oHostKeyAlgorithms=+ssh-dss controls@h1hpipumpctrll0

After deleting the old host key again I was able to connect.

Comments related to this report
jim.warner@LIGO.ORG - 15:19, Wednesday 10 September 2025 (86837)

The end stations were easier with their beckhoff controllers. EX wouldn't start pumping at first, but I think the vfd just needed powered off more completely. I turned it off for 5 secs when I  first arrived, that apparently wasn't enough to reset the vfd. Fil turned it off for maybe 20 secs, and fans came on when he powered it back up, which I didn't hear when I power cycled it earlier. EY came right back up.

H1 CDS
david.barker@LIGO.ORG - posted 12:24, Wednesday 10 September 2025 - last comment - 07:51, Friday 12 September 2025(86827)
H1 is down due to power outage.

We had a site wide power outage around 12:11 local time. Recovery of CDS has started.

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 12:40, Wednesday 10 September 2025 (86828)

I've turned the alarms system off, it was producing too much noise.

We are recovering front end models.

david.barker@LIGO.ORG - 13:51, Wednesday 10 September 2025 (86831)

Jonathan, Erik, Richard, Fil, Patrick, EJ, TJ, RyanS, Dave:

CDS is recovered. CDSSDF showing WAPs are on, FMCSSTAT showing LVEA temp change.

Images attached to this comment
david.barker@LIGO.ORG - 13:52, Wednesday 10 September 2025 (86832)

Alarms are back on (currently no active alarms). I had to restart the locklossalert.service, it had gotten stuck.

richard.mccarthy@LIGO.ORG - 07:51, Friday 12 September 2025 (86872)

BPA Dispatcher on duty said they had a breaker at the Benton substation open & reclose. At that time, they did not have a known cause for the breaker operation.  Hanford fire called to report a fire off Route 4 by Energy Northwest near the 115KV BPA power lines. After discussions with the BPA dispatcher the bump on the line or breaker operation, may have been caused by a fault on the BPA 115KV line causing the fire. BPA was dispatching a line crew to investigate.

 

H1 SUS (ISC)
oli.patane@LIGO.ORG - posted 11:06, Wednesday 10 September 2025 - last comment - 14:16, Wednesday 10 September 2025(86822)
IMC LSC/ASC Comparison from Satellite Amplifier Swap

Satellite amplifiers for MC1 and MC3 were swapped during maintenance (15:00-19:00 UTC) on July 22, 2025 (85922), and MC2 satamp had been swapped before that (85770). I wanted to see if we could determine any improvement in noise in the LSC and ASC input mode cleaner channels.

LSC Channel: 
    - H1:IMC-L_OUT_DQ
ASC Channels:
    - H1:IMC-MC2_TRANS_PIT_OUT_DQ
    - H1:IMC-MC2_TRANS_YAW_OUT_DQ
    - H1:IMC-WFS_A_DC_PIT_OUT_DQ
    - H1:IMC-WFS_A_DC_YAW_OUT_DQ
    - H1:IMC-WFS_B_DC_PIT_OUT_DQ
    - H1:IMC-WFS_B_DC_YAW_OUT_DQ
    - H1:IMC-WFS_A_I_PIT_OUT_DQ
    - H1:IMC-WFS_A_Q_PIT_OUT_DQ
    - H1:IMC-WFS_A_I_YAW_OUT_DQ
    - H1:IMC-WFS_A_Q_YAW_OUT_DQ
    - H1:IMC-WFS_B_I_PIT_OUT_DQ
    - H1:IMC-WFS_B_Q_PIT_OUT_DQ
    - H1:IMC-WFS_B_I_YAW_OUT_DQ
    - H1:IMC-WFS_B_Q_YAW_OUT_DQ

I looked at many times before and after these swaps looking for the lowest noise for each to be the best representative of the noise level we can achieve, and have settled on a set of before and after times that differ depending on the channel.
BEFORE:
2025-06-18 09:10 UTC (DARK RED)
2025-07-07 09:37 UTC (DARK BLUE)
AFTER:
2025-08-01 07:05 UTC (GREEN)
2025-08-01 10:15 UTC (PINK)
2025-08-02 08:38 UTC (SEA GREEN)
2025-09-05 05:23 UTC (ORANGE)
These measurements were taken for 47 averages with a 0.01 BW.

Results:

Channel                                                     Comments
H1:IMC-L_OUT_DQ Here the best 'after swap' time that I was able to find is noticeably worse than the best before time, so either the swap made the LSC noise worse, or we just haven't been able to reach that level of lowest noise again since the swap.
H1:IMC-MC2_TRANS_PIT_OUT_DQ Small noise drop between 0.8-3 Hz
H1:IMC-MC2_TRANS_YAW_OUT_DQ Slight noise drop between 0.6-3 Hz?
H1:IMC-WFS_A_DC_PIT_OUT_DQ Looks about the same as before, maybe a bit of improvement between 7-9.5 Hz
H1:IMC-WFS_A_DC_YAW_OUT_DQ Noise between 6-10 Hz has dropped slightly
H1:IMC-WFS_B_DC_PIT_OUT_DQ No difference
H1:IMC-WFS_B_DC_YAW_OUT_DQ No difference
H1:IMC-WFS_A_I_PIT_OUT_DQ Looks like the noise above 1 Hz has dropped slightly
H1:IMC-WFS_A_Q_PIT_OUT No difference
H1:IMC-WFS_A_I_YAW_OUT No difference
H1:IMC-WFS_A_Q_YAW_OUT No difference
H1:IMC-WFS_B_I_PIT_OUT Looks about the same as before, maybe a bit of improvement between 7-9.5 Hz. Showing the sea green AFTER trace to verify that the pink AFTER bump seen at 10 Hz is not an issue caused by the satamp swap.
H1:IMC-WFS_B_Q_PIT_OUT Looks about the same as before, maybe a bit of improvement between 7-9.5 Hz. Showing the sea green AFTER trace to verify that the pink AFTER bump seen at 10 Hz is not an issue caused by the satamp swap.
H1:IMC-WFS_B_I_YAW_OUT Looks about the same as before, maybe a bit of improvement between 7-9.5 Hz
H1:IMC-WFS_B_Q_YAW_OUT Looks about the same as before, maybe a bit of improvement between 7-9.5 Hz
Images attached to this report
Comments related to this report
oli.patane@LIGO.ORG - 11:09, Wednesday 10 September 2025 (86823)SQZ

The SQZ filter cavity version of this: 86624

jeffrey.kissel@LIGO.ORG - 14:16, Wednesday 10 September 2025 (86833)IOO, ISC
The plots from LHO:86253 show the before vs. after M1 OSEM noise performance for 
    MC1
    MC2, and
    MC3.

Comparing the page 3 summaries of each of these .pdfs show that 
    - We only expect change between ~0.2 and ~8 Hz. So, any improvement seen in the 7 to 9.5 Hz region is very likely *not* related to the sat amp whitening change.
    - For MC2, the LF and RT OSEM degrees of freedom --  both the before and after traces show that L and Y are well above the expected noise floor below for the entire region below 10 Hz.
    - The change all DOFs is a broadband change in noise performance; not only is there nothing *sensed* by these OSEMs above ~5 Hz, but there's also no change and thus any resonance-like features that change in the IMC signals will not be related to the sat amp whitening filter change.

We should confirm that the data used for the MC2 "before vs after" were both taken with the IMC length control OFF (i.e. the IMC was OFFLINE).

Back to the IMC metrics -- 
    (1) Only IMC-L and the MC TRANS signals appear to be dominated by residual seismic / suspension noise below 10 Hz. Hence
        (a) I believe the improvement shown in the MC TRANS QPD, tho I would have expected more.
        (b) I believe that we're seeing something that is limited by seismic / suspension noise in IMC-L, but the fact that got worse doesn't agree with the top-mass OSEM's stated improvement from LHO:86253, so I suspect the story is more complicated.
    (2) it's clear that all of the DC "QPD" signals from the IMC WFS are not reading out anything seismically related below 10 Hz. Maybe this ASD shape is a function of the beam position? Maybe the real signal is drown out by ADC noise, i.e. the signal is only well-whitened above 10 Hz? Whatever it is, it's drowning out the improvements that we might have expected to see -- we don't see *any* of the typical residual seismic / suspension noise features.
    (3) WFS B RF signals appear to also be swamped by this same color of noise. WFS A RF signals show a similar color, but it's less in magnitude, so you see some residual seismic / suspension peaks popping up above it. But it's not low enough to show where we might expect the improvements -- the troughs between resonances. So given the quality of this metric, I'm not mad that we didn't see an improvement.

So -- again -- I really only think that metrics (1), i.e. IMC-L and MC2 TRANS are showing noise that is/was dominated by residual seismic / suspension noise below 10 Hz, so that's why we see no change in the IMC WFS signals; not because we didn't make an improvement in what they're *supposed* to be measuring.

We'll have to figure out what happened with IMC-L between June and Sep 2025, but the plethora of new high-Q (both "mechanical" and "digital") features between 3 and 10 Hz suggests that it's got nothing to do with the sat amp whitening improvement. The slope of increased broadband noise between 1 to 3 Hz doesn't match what we would  expect, nor does it match the demonstrated improvement in the local M1 OSEM sensors. We should check the DC signal levels, or change the window type, to be sure this isn't spectral leakage. 


Displaying reports 1321-1340 of 85695.Go to page Start 63 64 65 66 67 68 69 70 71 End