FAMIS26028
As noted in the last few checks, ITMX ST1 V1 and ITMY ST1 V2 seem to be higher than other dofs, and this time they are slightly above last week's check as well (alog82366).
Lockloss (ETMx Glitch tag) at 1722utc.
Relocking was not trivial. Had issues with consecutive LOCKING ALS locklosses (pauses appeared to help), but then had ALS COMM Fine Tuning issues where TRX could not get above 0.6 (which is too low). Ultimately, a full Initial Alignment did the trick. Now finally getting ready to power up H1. It's been over 2hrs so far and hope to make it back up within 45min.
Saw Corey's note re: "ISS Diffracted Power Low," so I took the opportunity provided by the recent lockloss to adjust the ISS RefSignal. The RefSignal changed from -1.90 V to -1.88 V, which brought the diffracted power % to ~4% from just below 3%. The diffracted power % changed due to the enclosure slowly returning to thermal equlibrium after yesterday's FSS tune up, which changed the amount of power transmitted through the PMC.
Wed Jan 29 10:05:45 2025 INFO: Fill completed in 5min 42secs
TCmins[-66C, -65C] OAT (-3C, 27F) DetaTempTime 10:05:47. TC-B is nominal again.
If you are trending slow channels which are acquired by the EDC spanning the time of the EDC+DAQ restart yesterday (11:30 Tue 28 Jan 2025) and you are using the default NDS (h1daqnds1) you may see outlier data for a period of about 10 minutes. This is because we staggered the DAQ restart to preserve front-end data, starting with the 0-leg and EDC first, and then the 1-leg later after fw0 was back to writing frames.
The EDC change yesterday was to add/remove mechanical room vacuum channels, and the vacuum systems are at the beginning of the EDC DAQ configuration file. The result of this is that after h1edc was restarted at 11:28, from h1daqfw1's perspective almost all the EDC channels moved relative to each other (channel hop), meaning that for each channel nearby channel data was being written instead for about 10 minutes.
h1daqfw0 does not have this issue because h1edc was restarted while it was down, such that when it started writing frames again it was running with the new h1edc configuration. Ditto for raw minute trends on h1daqtw0.
Switching your NDS from the default h1daqnds1 to h1daqnds0 removes this issue. The attached plots show a 24 hour trend of the outside temperature in degC obtained from nds1 and nds0. The nds1 command is:
ndscope --light -t "24 hours ago" -t now H1:PEM-CS_TEMP_ROOF_WEATHER_DEGC
and the nds0 command is
ndscope --nds h1daqnds0:8088 --light -t "24 hours ago" -t now H1:PEM-CS_TEMP_ROOF_WEATHER_DEGC
Ran the dust monitor check this morning and noticed LAB2 had this note: Error: data set contains 'not-a-number' (NaN) entries
Dave mentioned this dust monitor has been down since christmas time and giving odd data (vs showing signs of being "dead"/offline). The plan was to get it replaced; so this is a known issue. Not sure where it is (Optics Lab or Vacuum Prep?).
The dust monitor is located in the Vacuum prep area, which is adjacent to the PCAL lab past the garb room. I've power cycled it, restarted the IOC and unplugged and replugged it from its network switch. It probably needs to be swapped but I don't have any internally pumped spares left right now, only pumpless spares that hook up to vacumm pumps. There is a internally pumped DMed in the LVEA that is unused currently, it's turned off during observing (LVEA dust monitor 5) as its pump is noisy, that I could potentially swap it for.
TITLE: 01/29 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 4mph Gusts, 2mph 3min avg
Primary useism: 0.02 μm/s
Secondary useism: 0.19 μm/s
QUICK SUMMARY:
H1's been locked 9.5hrs and even stayed locked through a local M4.2 eq off the WA/BC coast. H1 was dropped out of Observing from 1053-1055 due to PI24.
Getting some ISS Diffracted Low Power messages ever few seconds and have some EX glitches from Verbal over the last 4hrs.
Looking like the EX temperature drop & recovery returned to normal at around 12hrs ago (300utc) and it's a balmy 17degF (-8degC) out!
TITLE: 01/29 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: TJ
SHIFT SUMMARY: Just started Observing a few minutes ago after relocking. Relocking went relatively well. Two locklosses during my shift and the only problem with relocking both times was waiting for ALSY and ALSX to calm down so we could lock them. ALSX has an excuse because of the temperature excursion at EX (which is now not too bad - the heating overshot a bit but is coming back down and the rate at which the temperature is changing isn't too bad anymore). However, ALSY doesn't have a good excuse and was also causing issues. We noticed this started happening around January 22nd or 23rd. Almost every lockloss, ALSY does this thing (ndscope) where it will be okay, then gets worse and unlocks, then goes back to being okay, and repeat. A few days ago we checked if it was being caused by the WFS, but the WFS seemed fine and turning them off doesn't stop ALSY from acting strange. Tagging ISC
LOG:
01:00 Lockloss
- ALSX kept losing lock (probably due to temperature changes at EX)
- Let ALS lock and WFS converge more before continuing
- Stuck doing MICH so ran an initial alignment
02:59 NOMINAL_LOW_NOISE
03:02 Observing
04:45 Lockloss
- ALSX and ALSY kept losing lock
- Let ALS lock and WFS converge more before continuing
05:56 NOMINAL_LOW_NOISE
05:59 Observing
| Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
|---|---|---|---|---|---|---|
| 22:41 | FAC | eric | EX | - | checking on temperature drop | 00:11 |
| 23:11 | FAC | tyler | MechRoom.Mids.EY | - | spare heater coil search | 00:35 |
Lockloss @ 01/29 04:44 UTC after 1.75 hours locked
05:59 Observing
Today Francisco and I went down to the EX End station to do a End Station measurement using PS4.
We followed our trusty T1500062 Procedure until aalmost the end, Because Francisco needed to do a beam movement After the ES measurement.
The PS4/PS5 lab measurement used for this was made on 2024-12-10. I did make a PS4/PS5 measurement yesterday, but that was done using the new Lab method. This means this Lab measurement is not availible on the master branch in the form required for the ES measurement analysis tools to use it properly.
python generate_measurement_data.py --WS "PS4" --date '2024-12-10'
Reading in config file from python file in scripts
../../../Common/O4PSparams.yaml
PS4 rho, kappa, u_rel on 2024-12-10 corrected to ES temperature 299.6 K :
-4.702394808525094 -0.0002694340454223 4.3277259408925024e-05
Copying the scripts into tD directory...
Connected to nds.ligo-wa.caltech.edu
martel run
reading data at start_time: 1422121080
reading data at start_time: 1422121480
reading data at start_time: 1422121800
reading data at start_time: 1422122150
reading data at start_time: 1422122510
reading data at start_time: 1422122865
reading data at start_time: 1422122980
reading data at start_time: 1422123840
reading data at start_time: 1422124200
Ratios: -0.4589607901775236 -0.4689807789761762
writing nds2 data to files
finishing writing
Background Values:
bg1 = 9.269796; Background of TX when WS is at TX
bg2 = 5.192082; Background of WS when WS is at TX
bg3 = 9.119009; Background of TX when WS is at RX
bg4 = 5.361966; Background of WS when WS is at RX
bg5 = 9.037959; Background of TX
bg6 = 0.508605; Background of RX
The uncertainty reported below are Relative Standard Deviation in percent
Intermediate Ratios
RatioWS_TX_it = -0.458961;
RatioWS_TX_ot = -0.468981;
RatioWS_TX_ir = -0.453407;
RatioWS_TX_or = -0.464488;
RatioWS_TX_it_unc = 0.085535;
RatioWS_TX_ot_unc = 0.091457;
RatioWS_TX_ir_unc = 0.089022;
RatioWS_TX_or_unc = 0.094409;
Optical Efficiency
OE_Inner_beam = 0.988084;
OE_Outer_beam = 0.990574;
Weighted_Optical_Efficiency = 0.989329;
OE_Inner_beam_unc = 0.057445;
OE_Outer_beam_unc = 0.061558;
Weighted_Optical_Efficiency_unc = 0.084198;
Martel Voltage fit:
Gradient = 1636.809688;
Intercept = 0.225736;
Power Imbalance = 0.978635;
Endstation Power sensors to WS ratios::
Ratio_WS_TX = -1.077654;
Ratio_WS_RX = -1.392043;
Ratio_WS_TX_unc = 0.053955;
Ratio_WS_RX_unc = 0.041453;
=============================================================
============= Values for Force Coefficients =================
=============================================================
Key Pcal Values :
GS = -5.135100; Gold Standard Value in (V/W)
WS = -4.702395; Working Standard Value
costheta = 0.988362; Angle of incidence
c = 299792458.000000; Speed of Light
End Station Values :
TXWS = -1.077654; Tx to WS Rel responsivity (V/V)
sigma_TXWS = 0.000581; Uncertainity of Tx to WS Rel responsivity (V/V)
RXWS = -1.392043; Rx to WS Rel responsivity (V/V)
sigma_RXWS = 0.000577; Uncertainity of Rx to WS Rel responsivity (V/V)
e = 0.989329; Optical Efficiency
sigma_e = 0.000833; Uncertainity in Optical Efficiency
Martel Voltage fit :
Martel_gradient = 1636.809688; Martel to output channel (C/V)
Martel_intercept = 0.225736; Intercept of fit of Martel to output (C/V)
Power Loss Apportion :
beta = 0.998895; Ratio between input and output (Beta)
E_T = 0.994100; TX Optical efficiency
sigma_E_T = 0.000419; Uncertainity in TX Optical efficiency
E_R = 0.995201; RX Optical Efficiency
sigma_E_R = 0.000419; Uncertainity in RX Optical efficiency
Force Coefficients :
FC_TxPD = 7.902395e-13; TxPD Force Coefficient
FC_RxPD = 6.183646e-13; RxPD Force Coefficient
sigma_FC_TxPD = 5.429896e-16; TxPD Force Coefficient
sigma_FC_RxPD = 3.673209e-16; RxPD Force Coefficient
data written to ../../measurements/LHO_EndX/tD20250128/
Martel measurement
WS in the Transmitter module.
WS in the Rx module
WS in the Rx module with Both Beams
PCAL ES trends pdf.
More data can be found here: https://git.ligo.org/Calibration/pcal/-/tree/master/O4/ES/measurements/LHO_EndX/tD20250128?ref_type=heads
Lockloss @ 01/29 01:00 UTC
03:02 Observing
TITLE: 01/28 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Oli
SHIFT SUMMARY:
Maintenance Day roughly ended at noon followed by locking and getting locked fairly smoothly with no issues worth noting.
There has been a temperature drop at EX from this morning due to a heater coil failure. Tyler gave Oli and I a summary of the status of EX's recovery. The Reheat temperature is now up at 80degF (it had been hovering at 60 for the last 7hrs)---it will now oscillate a bit until it returns to normal operations. Tyler said to keep an eye on it and contact him if we loose our Reheat air again.
LOG:
TITLE: 01/29 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 3mph Gusts, 1mph 3min avg
Primary useism: 0.01 μm/s
Secondary useism: 0.11 μm/s
QUICK SUMMARY:
Currently Observing at 159Mpc and have been Locked for 3.5 hours now. The work to fix the fan heating coil at EX just finished and the coils are running, just not with full capability. We have been doing okay even with the temperatures there still fluctuating. The average VEA temps had gone down 2.5°F over the past 7 hours, but now it's slowly going back up.
Lockloss tool tags anthropogenetic, there was a ground motion spike in the 0.3 - 1.0 band that matches up to the lockloss. We lose lock right around the CS_Z motions peak.
Tagging PEM
On Tuesday NOV 19th Eric started the replacement of the ceilign light fixtures in the PCAL Lab.
Francisco and I grabbed 3 HAM Door covers to stretch out over the PCAL table to minimize dust particles on the PCAL optical bench.
I also put all the Spheres away in the cabinet and made sure that they all had their apature covers on.
I went in to shutter the laser using the internal PCAL TX module shutter, and the shutter stopped working.
I then just powered off the laser, removed the shutter, and repaired the shutter in the EE lab.
Put in an FRS ticket: https://services1.ligo-la.caltech.edu/FRS/show_bug.cgi?id=31730
The Shutter is repaired and just waiting for the FAC team to finish the Light fixture replacement to reinstall.
Update: Friday NOV 22nd, there are 2 more light fixtures in the PCAL LAB that need to be replaced. One directly above the PCAL Optics table.
PCAL Laser Remains turned off with the key out.
Since this event the Lab shutter from inside the Tx module hasn't been reading back correctly. Today Fil and I figured out why after replacing the switching regulator LM22676.
There is a reed switch Meder 5-B C9 on the bottom of the PCB that gets switched on via a magnet mounted on the side of the shutter door.
One of these reed switches is stuck in the "closed" position, which leaves the OPEN readback LED on all the time. Parts incoming.
