Jim, RyanC
We noticed that the oplev damping values seemed pretty large, so we turned off the output for the OLDAMP. The noise increase started the morning of the 1st which makes sense as it's when the vent started.
WP 12505. Patrick, Gerardo I tried various restarts of the Beckhoff PLC on h0vaclx, but none of them changed the error on the PT110 gauge. I did notice an additional diagnosis of the error, which is that the status of the EtherCAT ports is abnormal, which I think is an indication that something is not right with the connection of the gauge to the h0vaclx EtherCAT network. Gerardo went out to reseat the cable and look for anything odd about it. I went through and checked the relay trip point levels for each of the gauges on h0vaclx. I found PT110, PT180 and PT170 set to 1E-5 and changed them to 5E-5. PT132 was already at 5E-5. The other gauges do not have the trip points enabled. PT110 1E-5 -> 5E-5 PT140 not enabled PT180 1E-5 -> 5E-5 PT170 1E-5 -> 5E-5 PT132 5E-5 PT193 not enabled PT192 not enabled PT191 not enabled
I used the vacuum SDF safe.snap file to restore CP2's PID settings. To speed this up in the future I wrote a script to do this, the script should be ran on a machine with write access to the vacuum controls IOCs.
/ligo/home/vacuum/burt_restore_h0vaclx.bsh
cp /opt/rtcds/userapps/release/cds/h1/burtfiles/h1vacuumsdf/h1vacuumsdf_safe.snap /tmp/h1vacuumsdf_safe.snap
cat /tmp/h1vacuumsdf_safe.snap|grep "^H0:VAC-LX_"|awk '{print "caput ",$1,$3}' > /tmp/h0vaclx
while read -r i;do
${i}
done < /tmp/h0vaclx
Error is fixed, all we had to do was connect the Ethernet cable to correct port, yes somehow I managed to connect it on the wrong port, but the odd part is that we had a valid pressure signal, except for the error noted by Patrick.
For future reference, specifically, the correct port (in vs. out) on the gauge itself.
After discussing with Jeff this morning, I have flipped the sign of the Coil Output filters Gain to get the damping loops going on both RM1 and RM2. These changes have been accepted in the SDF. Jeff had set it to nominal value (i.e how it was pre-vent), however this makes the suspension very angry with the WD tripping immediately.
RM1 Coil Output Filter Gain:- H1:SUS-RM1_M1_COILOUTF_UL_GAIN -1 H1:SUS-RM1_M1_COILOUTF_LL_GAIN 1 H1:SUS-RM1_M1_COILOUTF_UR_GAIN 1 H1:SUS-RM1_M1_COILOUTF_LR_GAIN -1
RM2 Coil Output Filter Gain:-
H1:SUS-RM2_M1_COILOUTF_UL_GAIN 1 H1:SUS-RM2_M1_COILOUTF_LL_GAIN -1 H1:SUS-RM2_M1_COILOUTF_UR_GAIN -1 H1:SUS-RM2_M1_COILOUTF_LR_GAIN 1
This sign change is done to compensate for the sign change of the osem voltages (now inmons are +ve counts, pre-vent it was -ve counts), along with wrong polarity of the magnets (which has always been there in RM2).
Both RM1 and RM2 are damping fine now.
I also took Un-damped and Damped osem spectra (un-calibrated) for both RM1 and RM2 and the results shows that the BOSEM sensor noise above 10Hz (since ISI is locked) is acceptable, even though slightly high due to declining health (their OLC are on a gradual decline) of the BOSEMs itself.
Gerardo alerted me to the fact that PT110 is indicating an error on the H0:VAC-LX_Y0_PT110_ERROR channel. I logged in to h0vaclx and traced this to an unexpected value for the info data state readout. This should be 8 but is reading 15368. I don't know why or what 15368 means. He indicated that this appeared after they swapped in this gauge for another, so I suspect that this is the issue somehow.
J. Freed
Last week, this week, and the next week, the goal is to finalize the double mixer design, drawings and chassis. M. Pirello. has begun the drawings while I finalize the design, and we will work on the layout as well as the front plate.
Currently 83439 shows that phase noise is good except for harmonics every 4096Hz away from carrier. While any frequency more than 100Hz around the carrier should not affect SPI some of them do have an effect (namely the 8192Hz harmonic), 81593 also shows an ocsiloscope reading of the output which shows how messy the signal looks. This as such this week the focus is on reducing those harmonics.
The Q2 transistor on the Low Noise Power Board failed last week, was replaced, then it popped and replaced again. The problem was diagnosed to be the power pins on the ZFL-500HLNB+ amp. The pins stick out and touched the metal casing of another minicircuit part causing a short on the +15V supply from the low noise power board. A temporary solution of electrical tape was use to isolate the pins while a more perminate isolation for the pins will be there when it is finalized
AGBW.jpg Shows that the Agilent 4396B in spectrum analyzer mode gives less information with a smaller resolution bandwidth. The higher resolution bandwidth shows more harmonics with greater power on said harmonics. I do not know why this is, which is why I will be looking at phase noise when trying to improve harmonics.
The Agilent 4396B in network analyzer mode was used to take transfer functions of the double mixer phase delayer, IMG_1472.jpg shows the set up. The source power was 13dBm, the central frequency was 80MHz. The Span and Resolution Bandwidth were both 40kHz but changeing these values did not change much as the amplitude and phase was relativly flat around 80 MHz. A 10dB attinuator was added to the output to remove the overload message on port B that appered around 7dBm input power when I was incresing power to 13dBm.This is ok as I could calibrate the machine by replacing the phase delayer with a addaptor that let the signal go straight through. This calibration became my (0dBm 0deg) reference. I took measuments of one port of the phase delayer at a time while terminating the other.
| Gain (dB) +- 0.01 | Phase (deg) +- 0.1 | |
| Port 1 | -3.31 | -84.6 |
| Port 2 | -2.93 | 3.1 |
| Difference | 0.38 | -87.7 |
This is slightly off from what was hoped for with (0dBm -90deg) difference. SPI has some 0.5dB attinuators as well as 1dB attinuators. Due to the attinuators not being their listed value at 80 MHz, Two 0.5dB attinuators on port 2 and one 1dB attinuator on port 1 seems to nearly correct the power differnece.
Continuing from here is characterizing the mixers, the summer, and RF couplers to gain inisight on reducing the harmonics.
M. Todd, C. Compton, S. Dwyer, A. Brooks
As a continuation of the last alog, this is discussing how we can estimate thermal actuator contributions to the surface curvature to the test masses.
Summary:
The dataset used to estimate the ring-heater to surface curvature gain factor contained several ring heater settings and the corresponding HOM spacings at various "positions" in the span of time when that ring-heater power was used. For example, if the ring-heater power was changed and kept the same for 3 months, the HOM spacing data was examined at a random (long-lock time) portion of this 3-month period. This time, I tried to be a bit more systematic, such that we have a dataset with HOM spacing data at the beginning and end of each ring-heater power setting period. This can give us an idea if there are any drifts over time in the HOM spacing or coupling factors of the ring-heater power to surface curvature.
Each HOM spacing data-point is taken from a OMC spectrogram during a lock, and the errorbars associated with each are the spread of that HOM spacing peak.
The estimated ring-heater power to surface curvature gain is .7563 uD/W, which is very similar to the initial estimates done by Aiden; however, this is not the same value as the current one in TCS-SIM, indicating some adjustments may need to be made.
The blue dataset in the plot is data taken at the beginning of a ring-heater power setting period, while the yellow dataset is taken towards the end of the corresponding period. The estimated ring-heater power to surface curvature gain is the same for both datasets, however there is a relatively consistent downward drift over time by a few Hz in the HOM spacing. I'm not sure of the reason for this but it could be due difference in arm powers at each time.
Additionally, we expect the HOM spacing due to self-heating on top of the cold state to be around 5340 Hz, however TCS-SIM projects it to be around 5620 Hz.
Thus we estimate the change in HOM spacing due to self-heating alone to be around 175 Hz, where TCS-SIM projects it to be around 450 Hz. This indicates the gain factor mapping absorbed power to surface curvature change may be to high, or our estimate of the absorbed power is too high. The latter can be estimated from the Hartmann wavefront sensors.
I took a look at the YAW angle for the HAM HEPIs associated with PR2 (incorrect by me) (HAM2), SR2 (HAM4), and SR3 (HAM5) based on this previous alog83705. I believe the IPS channel units are in nrad, so the largest yaw angle I see is on HAM2 with 1800 nrad or 1.80 urad, HAM2 and 4 are different by ~ 1.10 urad.
I added on the RESIDUALMON channels at Jims recommendation which directly tells you the error from the reference location.
Here's HAM3, 0.392 urad as seen by HEPI
Wed Apr 30 10:11:57 2025 INFO: Fill completed in 11min 53secs
Gerardo confirmed a good fill curbside.
TJ was unable to run the 'guardutil archive-clone ...' command due to permission issues. We looked at it, and the relevant error message was: fatal: failed to copy file to 'IMC_LOCK/.git/objects/2f/826f205c25a6189503d831106e2dd97d7a39dc': Permission denied' Tracing through paths, this was in /guardian/archive/IMC_LOCK/.git/.... The permissions + ownership of that file where 0600 (rw for the user), everything else was 0444 (r only for everyone) and owned by guardian:controls. Changing the permissions to 0444 fixed things. We did a search from the guardian machine for other files with that problem and found 24 files under /srv/guardian/archive, so we reset the permissions to clear up future problems. Find command for searching: find . -type f -perm 600 Command for updating: find . -type f -perm 600 | xargs chmod 0444 I suspect this is a umask issue that someone had a umask of 077 set when they did an archive request.
Morning dry air skid checks, water pump, kobelco, drying towers all nominal.
Dew point measurement at HAM1 , approx. -41C
TITLE: 04/30 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
SEI_ENV state: MAINTENANCE
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.12 μm/s
QUICK SUMMARY:
The planned work today includes:
PCal team took PS4 to EY again today for the first every April measurement of End Y! Previous Aprils' measurements have apparently all been EndX.
Following T1500062V-18, Nothing really out of the ordinary except I put RX here instead of bolting to the side of the breadboard like I normally do, to see if that has any effect on the load balancing of the RX optical bread board or any impact to the overall measurement during the time when WS was in the RX side.
Beam spot
python3 generate_measurement_data.py --
WS "PS4" --date "2025-03-24"
Reading in config file from python file in scripts
../../../Common/O4PSparams.yaml
PS4 rho, kappa, u_rel on 2025-03-24 corrected to ES temperature 299.4 K :
-4.701550919294612 -0.0002694340454223 4.0632996079052654e-05
Copying the scripts into tD directory...
Connected to nds.ligo-wa.caltech.edu
martel run
reading data at start_time: 1429997850
reading data at start_time: 1429998230
reading data at start_time: 1429998550
reading data at start_time: 1429998990
reading data at start_time: 1429999330
reading data at start_time: 1429999640
reading data at start_time: 1430000100
reading data at start_time: 1430000600
reading data at start_time: 1430000920
Ratios: -0.5349326615859125 -0.5432025342228874
writing nds2 data to files
finishing writing
Background Values:
bg1 = 17.394679; Background of TX when WS is at TX
bg2 = 4.438216; Background of WS when WS is at TX
bg3 = 17.479506; Background of TX when WS is at RX
bg4 = 4.610581; Background of WS when WS is at RX
bg5 = 17.487987; Background of TX
bg6 = -0.718008; Background of RX
The uncertainty reported below are Relative Standard Deviation in percent
Intermediate Ratios
RatioWS_TX_it = -0.534933;
RatioWS_TX_ot = -0.543203;
RatioWS_TX_ir = -0.527567;
RatioWS_TX_or = -0.535369;
RatioWS_TX_it_unc = 0.055737;
RatioWS_TX_ot_unc = 0.055881;
RatioWS_TX_ir_unc = 0.056510;
RatioWS_TX_or_unc = 0.055480;
Optical Efficiency
OE_Inner_beam = 0.985953;
OE_Outer_beam = 0.985408;
Weighted_Optical_Efficiency = 0.985681;
OE_Inner_beam_unc = 0.042868;
OE_Outer_beam_unc = 0.044311;
Weighted_Optical_Efficiency_unc = 0.061653;
Martel Voltage fit:
Gradient = 1637.860873;
Intercept = 0.156301;
Power Imbalance = 0.984776;
Endstation Power sensors to WS ratios::
Ratio_WS_TX = -0.927527;
Ratio_WS_RX = -1.383600;
Ratio_WS_TX_unc = 0.045873;
Ratio_WS_RX_unc = 0.042755;
=============================================================
============= Values for Force Coefficients =================
=============================================================
Key Pcal Values :
GS = -5.135100; Gold Standard Value in (V/W)
WS = -4.701551; Working Standard Value
costheta = 0.988362; Angle of incidence
c = 299792458.000000; Speed of Light
End Station Values :
TXWS = -0.927527; Tx to WS Rel responsivity (V/V)
sigma_TXWS = 0.000425; Uncertainity of Tx to WS Rel responsivity (V/V)
RXWS = -1.383600; Rx to WS Rel responsivity (V/V)
sigma_RXWS = 0.000592; Uncertainity of Rx to WS Rel responsivity (V/V)
e = 0.985681; Optical Efficiency
sigma_e = 0.000608; Uncertainity in Optical Efficiency
Martel Voltage fit :
Martel_gradient = 1637.860873; Martel to output channel (C/V)
Martel_intercept = 0.156301; Intercept of fit of Martel to output (C/V)
Power Loss Apportion :
beta = 0.998844; Ratio between input and output (Beta)
E_T = 0.992240; TX Optical efficiency
sigma_E_T = 0.000306; Uncertainity in TX Optical efficiency
E_R = 0.993389; RX Optical Efficiency
sigma_E_R = 0.000306; Uncertainity in RX Optical efficiency
Force Coefficients :
FC_TxPD = 9.160033e-13; TxPD Force Coefficient
FC_RxPD = 6.229843e-13; RxPD Force Coefficient
sigma_FC_TxPD = 5.093831e-16; TxPD Force Coefficient
sigma_FC_RxPD = 3.305931e-16; RxPD Force Coefficient
data written to ../../measurements/LHO_EndY/tD20250429/
This adventure was brought to you by, Francisco L & Tony S.
Calibration is currently regenerating the O4b uncertainty budgets. Due to a missed change to the ETMX UIM suspension filters, which was found in LHO alog 82804, and then fixed only on Feb 27, 2025 (see LHO alog 83088), we need to add a correction TF to be included in the uncertainty budgets. I attach a graph of that correction TF (corrected model / original model) and the text file needed for that correction. We will be using correction TF in all our uncertainty budgets for O4b, and up to Feb 27, 2025 around 20:00 UTC, or GPS 1424721618 for O4c.
Since after the July-Aug break, the low frequency response got closer to unity due to other mixed effects, we only apply the TF correction in uncertainty calculation before the break:
From 1396796418 = Wed Apr 10 15:00:00 UTC 2024 to 1404864018 = Sat Jul 13 00:00:00 UTC 2024
After the break, we leave it to GPflow to take care of the unmodeled residual using monitoring data.
Although the low-frequency response got closer to unity at later times, we found that GPflow still could not sufficiently capture the unmodeled residual.
We now determine that the above TF correction should be applied thoughout O4b at LHO.
Summary: This work aims to understand the shape of the DARM sensing function as affected by mode mismatches and input power. It seems that the mismatches affect the detuning of the SRCL DOF, that is it affects the locking point, but not the shape of the DARM sensing funciton. However, the input power, which causes radiation pressure, has a bigger effect on it. If I do not include QUADsuspension option, then I get a flat response function regardless of the mismatch or the input power.
For the past week I have been studying the effect of SCRL DOF detuning (or sometimes I refer to it as offset) on the DARM readout using FINESSE.
In FINESSE, that is done by changing SRCL.DC, and looking at the transfer function from DARM.AC.i to AS.DC.o
The reason being to understand the measurement of the sensing function taken and show here.
My system include up to maxtem=4, QUADsuspensions, InitialLock > DARM_RF_to_DC.
Before we start doing that, let’s understand the error signal of SRCL DOF. This is read at POP45_I channel. The ideal tuning of this loop is SRCL.DC=90, that is the case where the carrier beam is anti-resonant in the SRC, while the sidebands are. At that detuning, the error signal is 0. However, since we do not have a perfect model, there is some mode mismatch between SRC and the arm cavities. This will inject some higher order modes carrier and sidebands into the SRC and that changes the locking point. Using the default cold state LHO model, the detuning at which the error signal is 0 is SRCL.DC=-90.4643
This is shown in the plot below (Error_signals_vs_detuning.pdf)
Let’s look at this offset as the mode mismatch changes. I adjust ITMlenses focal lengths and measure the mismatch between SRX and XARM cavities, and SRY and YARM cavities. I also have an amplitude detector to measure the power in the HG20/02 modes at the AS port, which might be partially resonant in the SRC due to its low finesse. (Detuning_vs_SRC_ARMS_mismatch.pdf)
On the x-axis is the SRY to YARM mismatch percentage, and on the y-axis is the SRX to XARM mismatch percentage. I’m not sure why there is such a big difference of mismatches in the default cold state model, but the qualitative behavior is what we need here.
The colors represent SRCL.DC offset while the numbers on each cell represent the power in the 2nd high order mode in W.
We notice that as the SRY to YARM mismatch gets closer in magnitude to SRX to XARM mismatch the offset decreases and goes towards 90, and the power in the 2nd HOM also gets smaller, which suggests that the presence of these modes affects the offset, as we would expect(see also This old technical note)
I believe the reason that the HOM gets smaller as the mismatches get closer together can be imagined similar to what the Michelson interferometer does to the fundamental mode for HG20/02 modes that are at the same phase, they cancel each other out at the AS port.
Finally, let us look at the DARM sensing function, which is our goal of this investigation.
We would expect the sensing function to be flat starting around ~7Hz and keep like that until it starts rolling off at ~ 200 Hz.
Now, here is the surprise, I plotted the response function in the default case where there is mismatch between SRC and the arm cavities, and then I changed ITMXlens focal lengths to get almost perfect mode matching, and it turns out that they are not that different, as seen below (Comparison_with_different_MM.pdf)
What seems to be affecting the response function is not the mode matching (even though it affects the locking point), but the input power value. If I reduce the input power to 1W instead of 60W that is used in the comparison plot, I get the following response function (yes, I checked the error signal zero point is still at 90.464 (1W_DARM_readout_vs_detuning.pdf)
And so, from this investigation, it seems that the input power affects the response function more than the mode matching, while the mode matching affects the locking point.
Next, I reset the model and I started changing the reflectivity of the SRM, narrowing the linewidth and increasing the finesse of the cavity. As the finesse increases, the detuning goes towards 90 degrees. This could be from reducing the effect of the HOM on the fundamental mode in SRCL. (SRM_reflectivity.pdf)
I keep forgetting to reset the dust monitor alarm levels after IOC restarts so I wrote a little script to check all of the dust monitor alarms levels and reset them if needed based on E1600132. It does not reset the LVEA ones, it just notifies, as these ones alarm levels are sometimes modified.
The scripts is called check_dm_alarms_lvls.py and lives at /ligo/cds/userscripts/. I've also updated the wiki with this info.
I have added a call to this script to the aliased "check_dust_monitors_are_working" bash script that operators usually run at the beginning of the shift.
Late entry 4-16 (Wednesday) activities: - The previously received, poorly packaged Inficon gauge has been tested, and found functional. These tests continue, and also the HAM1 vacuum interlock gauge will be installed soon - The BSC8 Annulus Ion Pump - after some aux cart pumping - is now able to hold the annulus pressure, at the mid- E-6 Torr region - The rough pumpdown of the corner has started at 16:20, at the OMC turbo station, with a pair of ISP-1000 mobile pumping carts. In 4 hours, ~185 Torr was achieved, which means 1930 l/s effective pumping speed, which well corresponds with the 2000 l/s theoretical speed of the pumps - The rough pumping still needs to be terminated in the end of the days, and so it was at 20:20 - All the turbo stations have been prepared for the HV pumping at the corner
The dew point of the blow-off air was -15 deg C.
