Jenne, Elenna, Oli, Ryan S, Ryan C, Matt
Today the engagement of the camera servos significantly reduced the buildups. The first attachment shows how the PRG, REFL LF and circ power signals dropped as the camera servo guardian engaged the cameras. After reengaging the ADS, we saw that the buildups increased again, although not to the exact same level that they were before the camera engaged. This suggested to us that the camera servos were not going to the same camera set point as before. Oli spoke to the vacuum team that had been doing work at EY and found out that the EY camera cable had been very taut and they tried to loosen it. It's possible they bumped the camera during their work.
While we were considering what to do, we noticed that OMC DCPD sum was increasing rapidly. We realized this was due to a PI ringing up at 10.2 kHz. It's not a PI we usually damp, so there were no PI guardian warnings, and we didn't know how to damp it. Matt thinks this is a PI that we usually see ring up early in the lock, but with a relatively small amplitude, as the Y arm mode passes by. It usually does not need damping. We started getting DCPD saturations warnings, and we were certain we were going to lose lock. We thought perhaps that if we were in a slightly different beam position, that could cause this PI to ring up more than usual. Matt also pointed out that the CO2s had stayed on much longer for commissioning today. I had also held the IFO at 25 W before and after moving spots to perform some ASC measurements. So this was definitely not a normal locking process. However, the PI started to turn around on its own (we think), and we held the lock.
Jenne and I tried engaging the camera servos again, and saw that indeed doing so does reduce the buildups. Our thinking is that if the EY camera got bumped, the digital offset we normally use has probably changed. We also noticed that the low frequency sensitivity was slightly worse than usual, suggesting that wherever the beam was, the A2L decoupling was bad. So, we decided to move the EY camera offsets to see if we could regain the buildups, following the assumption that something had changed at EY. We looked at the camera offset value that was present when the ADS lines were on. We changed the ETMY pitch and yaw offset values. This resulted in a 2 count change for ETMY pitch, from -230 to -228 and a 0.5 ct change in yaw from -349.5 to -349. Changing to these new offsets increased the buildups again. We also saw that the ADS had taken the ETMX camera error signal to a slightly different offset, so we tried changing the ETMX pitch value, but this had no change on the buildups so we reverted.
Even though this whole process was designed to bring us back to the nominal ETMY spot position, it appeared that the low frequency sensitivity was still bad, I ran the A2L script. I watched TJ's A2L script scope and noticed that the A2L starting value for ETMY pitch was very far from zero, so the script never took the A2L value to the minimum. Jenne and I ended up guesstimating what a good A2L value was so that the starting point would be close enough to the minimum that the script steps would go there. This results in a significantly different A2L gain than before for ETMY pitch. I copied the tables below for each A2L script attempt. The nominal ETMY pitch value before was 5.62 and now it is 6.43. According to the a2l lookup script, this is a 3.8 mm change in spot position. The ETMX A2L gains also updated slightly, as you can see below. I did not make any changes to the gains where the diff between final and inital was 0.01 in magnitude.
Now that we have been in NLN for 3.5 hours, the buildups still seem lower than usual. Circulating powers usually read about 382 "kW", but they are currently reading about 374 "kW". Kappa C is also 0.975, and it is usually 0.98. I'm not convinced that the beam is in the correct spot.
Jenne suggested that we could try going back to the old A2L gains, and then adjusting the camera offset until the ADS lines are minimized, which I think is a good idea. However, I do want to point out that our range is currently reading 160 Mpc on sensmon clean.
The new ETMY camera offsets and the updated A2L gains are saved in lscparams and loaded in ISC_LOCK. First try:
Optic | DOF | Initial | Final | Diff |
---|---|---|---|---|
ETMX | P | 3.07 | 3.13 | 0.06 |
ETMX | Y | 4.79 | 4.85 | 0.06 |
ETMY | P | 5.54 | 5.54 | 0 |
ETMY | Y | 1.42 | 1.37 | -0.05 |
ITMX | P | -0.45 | -0.46 | -0.01 |
ITMX | Y | 3.16 | 3.15 | -0.01 |
ITMY | P | 0.19 | 0.2 | 0.01 |
ITMY | Y | -2.75 | -2.75 | 0 |
Second try:
Optic | DOF | Initial | Final | Diff |
---|---|---|---|---|
ETMX | P | 3.13 | 3.12 | -0.01 |
ETMX | Y | 4.85 | 4.85 | 0 |
ETMY | P | 6.3 | 6.43 | 0.13 |
ETMY | Y | 1.37 | 1.37 | 0 |
ITMX | P | -0.46 | -0.46 | 0 |
ITMX | Y | 3.15 | 3.16 | 0.01 |
ITMY | P | 0.2 | 0.19 | -0.01 |
ITMY | Y | -2.75 | -2.75 | 0 |
TITLE: 10/14 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 153Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: We ran into some issues after relocking following maintenance, but everything is stable currently. Is it in the best setup/orientation? Maybe not.
LOG:
Start Time | System | Name | Location | Lazer_Haz | Task | Time End |
---|---|---|---|---|---|---|
22:52 | SAF | Laser HAZARD | LVEA | YES | LVEA is Laser HAZARD \u0d26\u0d4d\u0d26\u0d3f(\u239a_\u239a) | 15:51 |
14:34 | FAC | Eric | Mech room | N | FAC checks | 14:55 |
14:35 | FAC | Randy | Yarm | N | Beam tube inspection, midy to corner | 18:39 |
15:08 | SUS | Jeff | CR | N | ETMX measurements, prep for satamp swap | 16:08 |
15:08 | SUS | Matt | CR | N | ITM measurements | 15:25 |
15:12 | TCS | Matt | LVEA | Y | Turn off sidebands | 15:25 |
15:18 | FAC | Chris | Out buildings | N | FAMIS checks | 16:59 |
15:24 | FAC | Kim | EndX | N | Tech clean | 16:39 |
15:24 | FAC | Nellie | EndX | N | Tech clean | 16:38 |
15:25 | VAC | Gerardo, Jordan | EY | N | Purge air | 17:15 |
15:28 | FAC | Tyler | Yarm | N | Termination slab checks | 19:04 |
15:31 | EE | Fil | CER | Y | ITM work | 16:11 |
15:35 | OPS | RyanS | LVEA | Y -> N | HAZARD TRANSITION, to safe | 15:51 |
16:04 | FAC | Richard | LVEA | N | Safety checks | 16:25 |
16:05 | VAC | Anna | LVEA | N | Join RGA team | 17:15 |
16:06 | VAC | Travis | MidX | N | Emergency pump checks | 17:11 |
16:13 | SUS | Jeff | CR | N | ETMY measurement | 16:51 |
16:14 | EE | Fil | Ends, X -> Y | N | Satamp swap, EY at 16:38 UTC | 17:22 |
16:32 | ISC | Sam | LVEA | N | Measure stuff | 17:13 |
16:33 | Keita, Alicia, Joan-Rene | LVEA | N | Tour, take pictures | 17:14 | |
16:42 | PSL | Rahul, Jennie | Optics lab | LOCAL | ISS PD array | 18:23 |
16:43 | FAC | Nellie, Kim | LVEA | N | Tech clean | 18:21 |
16:51 | SUS | Jeff | LVEA | N | ITMX SAT amp measurement | 17:03 |
17:00 | FAC | Chris | LVEA | N | FAMIS checks | 17:25 |
17:22 | EE | Marc, Fil | LVEA HAM5 | N | SUS R7 rack work, chassis installations | 18:59 |
17:04 | SUS | Jeff | LVEA | N | SR75 measurement in the Biergarten ITMX | 18:05 |
17:11 | VAC | Travis | MidY | N | Emergency pump checks | 17:42 |
17:31 | FAC | Richard, Alicia, Joan-Rene | OSB roof | N | Admire the view | 17:47 |
17:33 | VAC | Janos, Anna | LVEA | N | Move parts | 18:01 |
17:35 | VAC | Jordan | LVEA | N | 1000 amu RGA | 18:01 |
17:48 | IMC | Matt | CR | N | IMC injections | 17:54 |
17:56 | IMC | Matt | LVEA | N | Sidebands back on | 17:58 |
18:00 | TCS | Matt | LVEA | N | Turn back on TCS Y | 18:10 |
18:27 | VAC | Jordan, Anna | LVEA | N | YARM manifold rga | 19:02 |
19:00 | TCS | Matt | LVEA | N | Reset both CO2 lasers | 19:04 |
19:03 | OPS | RyanS | LVEA | N | LVEA sweep | 19:14 |
19:24 | ASC | Elenna | CR | N | Soft ASC loops measurement | 21:06 |
19:49 | PSL | Rahul, Keita | Optics lab | N | ISS Array work, laser safe | 21:46 |
19:50 | FAC | Randy | Yarm beamtube | N | Beamtube inspection | 21:46 |
20:42 | EE | Fil | MidY | N | Grab electronics parts | 21:42 |
21:56 | Matt | Vac prep lab | N | Grab a part | 22:06 | |
21:56 | PSL | Jennie | Optics lab | N | Double check something | 22:11 |
TITLE: 10/14 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
SEI_ENV state: CALM
Wind: 12mph Gusts, 7mph 3min avg
Primary useism: 0.03 μm/s
Secondary useism: 0.18 μm/s
QUICK SUMMARY:
Observing at 155Mpc and have been locked for almost three hours. Everything looking good.
WP12827 SUS HLTS Estimator
Jeff, Oli, Brian L, Edgard, Dave, Ryan C:
New h1suspr3 and h1sussr3 models were installed. Slow channels had been renamed and therefore a DAQ restart was required.
WP12835 h1guardian1 reboot
TJ:
h1guardian1 was rebooted, all nodes now have the latest userapps files and changes will be tracked by GRD-CFC.
DAQ Restart
Dave, Jonathan:
The DAQ was restarted for the model changes. GDS0 needed a second restart. FW1 spontaneously restarted itself soon after the 1-leg restart.
Tue14Oct2025
LOC TIME HOSTNAME MODEL/REBOOT
08:32:35 h1sush2a h1suspr3 <<< model restarts
08:33:06 h1sush56 h1sussr3
08:34:52 h1daqdc0 [DAQ] <<< 0-leg restart
08:35:05 h1daqfw0 [DAQ]
08:35:05 h1daqtw0 [DAQ]
08:35:06 h1daqnds0 [DAQ]
08:35:13 h1daqgds0 [DAQ]
08:36:17 h1daqgds0 [DAQ] <<< GDS0 needed 2nd restart
08:41:11 h1daqdc1 [DAQ] <<< 1-leg restart
08:41:20 h1daqfw1 [DAQ]
08:41:21 h1daqtw1 [DAQ]
08:41:24 h1daqnds1 [DAQ]
08:41:30 h1daqgds1 [DAQ]
08:52:28 h1daqfw1 [DAQ] <<< FW1 spontaneously restarted itself
Jennie W, Keita, Rahul
On Friday, Keita and Rahul and I tried moving PDs 2 and 6 to align them better with the others. As can be seen from the scans we did of the DC voltage of the diodes as we moved the input alignemnt in horizontal translation and yaw from alog #87290, 2 and 6 have a range of alignment that is shifted relative to the other 6.
We also checked this with a IR sensitive camera with a zoom lens.
One person used the camera with a zoom lens to check the spot on the PDs as another person loosened the screws from behind the array and the third person held the barrel of the PD assembly to stop it moving or rotating in an undesired direction.
There is not a lot of space as 2 and 6 are in a column and are very close to diodes 1 and 5 on the right.
The horizontal scan we took after these moves showed we had made things worse, see this image.
Later that afternoon, Keita moved the PD 2 back and checked the alignment and it looks better.
The alignment as of yesterday (Monday) was 143mm in pitch (as read out by the allen key in the PZT mirror pitch actuator wheel) and 0.4145 inches in horizontal translation as read out by the translation stage the PZT mirror sits on.
Keita measured the coupling (after finding an error in my code from the previous coupling measurement I plotted last Thursday (alog #87400)).
The coupling in both vertical and horizontal is below 10, so this should be good enough for install if all else checks out.
Yesterday afternoon, Rahul and I did the vertical scan (slightly off from the horizontal reference position of 0.4145 inches that Keita had aligned to). The data in this graph was collected at a horizontal translation stage reading of 0.4162 inches.
We had to redo the horizontal scan today as I missed out some scan values yesterday. The data was collected with the pitch indicator at 143mm (the allen key on the pitch wheel actuator).
This morning Rahul recentred the QPD on the input beam (translation stage = 0.4145 inches, allen key - 143mm) and we scanned the translation stage horizontally to measure the calibration of the QPD.
This first scan had too large steps to give a good estimate of the slope for the X coordinate on the QPD near the centre, so I repeated the measurement with smaller steps. Although I thought I set the laser to ~120 mA for both measurements the power on the QPD sum was slightly different between the two, see this plot where the original measurement set is in orange and the second set in blue.
Looking at the plot the QPD has the same slope in Y for both measurements but the second set of Y measurements has lower voltages.
The X data overlaps between the two measurements which makes more sense to me, as we assume the QPD electronics normalise the readout of X and Y by the sum channel to account for power fluctuations.
I used the newer measurement to estimate the calibration in the x direction, and the older measurement to estimate the slope in the y-direction, I tried to only use the linear part of the data in my fit and also not use any points with a voltage abive 6 Volts as this is when we expect the QPD to not be linear.
The calibration plot is here with the X calibration line in orange and the Y calibration line in red.
The resultant calibration is 72.0 V/mm in the horizontal direction, at an angle of 7.4 deg with the QPD axis. This is similar to the last calibration we did before several moves of the QPD to recentre it, see alog #87375.
This is worked out by adding the two slopes in quadrature and using atan2(Y_calib/X_calib) to work out the angle of the QPD axis with the horizontal direction of the PZT mirror translation.
WP 12836
ECR E2400330
Modified List T2500232
The following SUS SAT Amps were upgraded per ECR E2400330. Modification improves the whitening stage to reduce ADC noise from 0.05 to 10 Hz.
Suspension | Old | New | OSEM |
ETMX L2 (PUM) | S1100146 | S1100119 | ULLLURLR |
ETMY L2 (PUM) | S1100137 | S1100127 | ULLLURLR |
ITMX L2 (PUM) | S1100135 | S1100118 | ULLLURLR |
ITMY L2 (PUM) | S1000277 | S1100148 | ULLLURLR |
F. Clara, J. Kissel, O. Patane
Here's the characterization data and fit results for S1100148, assigned to ITMY L2's ULLLURLR OSEMs.
This sat amp is a UK 4CH sat amp, D0900900 / D0901284. The data was taken per methods described in T080062-v3, using the diagrammatic setup shown on PAGE 1 of the Measurement Diagrams from LHO:86807.
The data was processed and fit using ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Scripts/
plotresponse_S1100148_ITMY_L2_ULLLURLR_20250917.m
Explicitly, the fit to the whitening stage zero and pole, the transimpedance feedback resistor, and foton design string are:
Optic | Stage | Serial_Number | Channel_Number | OSEM_Name | Zero_Pole_Hz | R_TIA_kOhm | Foton_Design |
---|---|---|---|---|---|---|---|
ITMY | L2 | S1100148 | CH1 | UL | 0.095:5.19 | 120.5 | zpk([5.19],[0.095],1,"n") |
CH2 | LL | 0.0957:5.24 | 120.0 | zpk([5.24],[0.0957],1,"n") | |||
CH3 | UR | 0.0958:5.24 | 120.125 | zpk([5.24],[0.0958],1,"n") | |||
CH4 | LR | 0.0967:5.28 | 120.375 | zpk([5.28],[0.0967],1,"n") |
The attached plot and machine readable .txt file version of the above table are also found in ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Results/
2025-09-17_UKSatAmp_S1100148_D0901284-v5_fitresults.txt
Per usual, R_TIA_kOhm is not used in the compensation filter -- but after ruling out an adjustment in the zero frequency (by zeroing the phase residual at the lowest few frequency points), Jeff nudged the transimpedance a bit to get the magnitude scale within the ~0.25%, shown in the attached results. Any scaling like this will be accounted for instead with the absolute calibration step, i.e. Side Quest 4 from G2501621, a la what was done for PR3 and SR3 top masses in LHO:86222 and LHO:84531 respectively.
Here's the characterization data and fit results for S1100119, assigned to ETMX L2's ULLLURLR OSEMs.
This sat amp is a UK 4CH sat amp, D0900900 / D0901284. The data was taken per methods described in T080062-v3, using the diagrammatic setup shown on PAGE 1 of the Measurement Diagrams from LHO:86807.
The data was processed and fit using ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Scripts/
plotresponse_S1100119_ETMX_L2_ULLLURLR_20250916.m
Explicitly, the fit to the whitening stage zero and pole, the transimpedance feedback resistor, and foton design string are:
Optic | Stage | Serial_Number | Channel_Number | OSEM_Name | Zero_Pole_Hz | R_TIA_kOhm | Foton_Design |
---|---|---|---|---|---|---|---|
ETMX | L2 | S1100119 | CH1 | UL | 0.0949:5.19 | 120 | zpk([5.19],[0.0949],1,"n") |
CH2 | LL | 0.0971:5.32 | 120 | zpk([5.32],[0.0971],1,"n") | |||
CH3 | UR | 0.0964:5.27 | 120 | zpk([5.27],[0.0964],1,"n") | |||
CH4 | LR | 0.0957:5.23 | 120 | zpk([5.23],[0.0957],1,"n") |
The attached plot and machine readable .txt file version of the above table are also found in ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Results/
2025-09-16_UKSatAmp_S1100119_D0901284-v5_fitresults.txt
Per usual, R_TIA_kOhm is not used in the compensation filter -- but after ruling out an adjustment in the zero frequency (by zeroing the phase residual at the lowest few frequency points), Jeff nudged the transimpedance a bit to get the magnitude scale within the ~0.25%, shown in the attached results. Any scaling like this will be accounted for instead with the absolute calibration step, i.e. Side Quest 4 from G2501621, a la what was done for PR3 and SR3 top masses in LHO:86222 and LHO:84531 respectively.
Here's the characterization data and fit results for S1100118, assigned to ITMX L2's ULLLURLR OSEMs.
This sat amp is a UK 4CH sat amp, D0900900 / D0901284. The data was taken per methods described in T080062-v3, using the diagrammatic setup shown on PAGE 1 of the Measurement Diagrams from LHO:86807.
The data was processed and fit using ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Scripts/
plotresponse_S1100118_ITMX_L2_ULLLURLR_20250916.m
Explicitly, the fit to the whitening stage zero and pole, the transimpedance feedback resistor, and foton design string are:
Optic | Stage | Serial_Number | Channel_Number | OSEM_Name | Zero_Pole_Hz | R_TIA_kOhm | Foton_Design |
---|---|---|---|---|---|---|---|
ITMX | L2 | S1100118 | CH1 | UL | 0.0966:5.27 | 120 | zpk([5.27],[0.0966],1,"n") |
CH2 | LL | 0.0961:5.25 | 120 | zpk([5.25],[0.0961],1,"n") | |||
CH3 | UR | 0.0963:5.26 | 120 | zpk([5.26],[0.0963],1,"n") | |||
CH4 | LR | 0.097:5.3 | 120 | zpk([5.3],[0.097],1,"n") |
The attached plot and machine readable .txt file version of the above table are also found in ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Results/
2025-10-14_UKSatAmp_S1100118_D0901284-v5_fitresults.txt
Per usual, R_TIA_kOhm is not used in the compensation filter -- but after ruling out an adjustment in the zero frequency (by zeroing the phase residual at the lowest few frequency points), Jeff nudged the transimpedance a bit to get the magnitude scale within the ~0.25%, shown in the attached results. Any scaling like this will be accounted for instead with the absolute calibration step, i.e. Side Quest 4 from G2501621, a la what was done for PR3 and SR3 top masses in LHO:86222 and LHO:84531 respectively.
Here's the characterization data and fit results for S1100127, assigned to ETMY L2's ULLLURLR OSEMs.
This sat amp is a UK 4CH sat amp, D0900900 / D0901284. The data was taken per methods described in T080062-v3, using the diagrammatic setup shown on PAGE 1 of the Measurement Diagrams from LHO:86807.
The data was processed and fit using ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Scripts/
plotresponse_S1100127_ETMY_L2_ULLLURLR_20250916.m
Explicitly, the fit to the whitening stage zero and pole, the transimpedance feedback resistor, and foton design string are:
Optic | Stage | Serial_Number | Channel_Number | OSEM_Name | Zero_Pole_Hz | R_TIA_kOhm | Foton_Design |
---|---|---|---|---|---|---|---|
ETMY | L2 | S1100127 | CH1 | UL | 0.0963:5.26 | 121.25 | zpk([5.26],[0.0963],1,"n") |
CH2 | LL | 0.0958:5.24 | 121.25 | zpk([5.24],[0.0958],1,"n") | |||
CH3 | UR | 0.0952:5.2 | 121.25 | zpk([5.2],[0.0952],1,"n") | |||
CH4 | LR | 0.0954:5.21 | 121.25 | zpk([5.21],[0.0954],1,"n") |
The attached plot and machine readable .txt file version of the above table are also found in ${SusSVN}/trunk/electronicstesting/lho_electronics_testing/satamp/ECR_E2400330/Results/
2025-09-16_UKSatAmp_S1100127_D0901284-v5_fitresults.txt
Per usual, R_TIA_kOhm is not used in the compensation filter -- but after ruling out an adjustment in the zero frequency (by zeroing the phase residual at the lowest few frequency points), Jeff nudged the transimpedance a bit to get the magnitude scale within the ~0.25%, shown in the attached results. Any scaling like this will be accounted for instead with the absolute calibration step, i.e. Side Quest 4 from G2501621, a la what was done for PR3 and SR3 top masses in LHO:86222 and LHO:84531 respectively.
After maintenance wrapped up this morning, I swept through the LVEA to prep for observing. I unplugged an unused extension cord near the PSL racks and the scissor lift in the vertex/west bay area. Everything else looked okay.
Jeff also mentioned that he moved an SR785 from the PSL racks into the Biergarten for his work this morning, but it's unplugged (in case someone goes looking for it later).
I have created an EPICS IOC which reports any Guardian nodes which use source file(s) which have been modified in userapps but have not been loaded into the nodes. On the next restart of such nodes (e.g. guardian reboot) the new code will be automatically loaded, and so this system permits us to load new code in a scheduled and orderly way, for example by the code-author/node-manager during Tuesday maintenance.
This is similar to the front-end filter-module configuration file change (CFC) system, so I've called this GRD-CFC.
The CDS Overview MEDM has a "GRD CFC" button at the bottom showing the GRD-CFC status as GREEN/YELLOW. Pressing this button opens the H1CDS_GUARDIAN_CFC.adl MEDM (attached).
This MEDM has three main areas:
If any nodes are reporting pending changes, you can get pending file details by running the shell command:
guardian_modified_not_loaded
The output from this command provides information on how to list the line differences between pending files and what is running.
Tue Oct 14 10:08:10 2025 INFO: Fill completed in 8min 7secs
Rebooted h1guardian1 at 1547UTC so that we could start with fresh fresh and it would become easier to manage any file differences with help from some of Dave's new screens and scripts.
All nodes started up on their own, and Ryan C helped me recover them all back to a maintenance state.
I went to test the high gain ASC states I made for SEI_ENV this morning while we were still locked this morning. The good news is that there were no errors in the code and it did exactly what I asked of it. The bad news is that we lost lock while transitioning back to a low gain state. This wasn't a great test though because I had a brain fart and forgot to change the thresholds for the test. The high gains were turned on, then immediately turned back. So I'm not entirely sure if the lock loss was from the transition back, or just the fact that we quickly flipped it back and forth.
The major change between what SEI_ENV does and what the script the operators use right now is that the sleep timers between engaging/disengaging each loop are almost completly gone. At minimum for the next test it seems that we need some for the return back to low gain, or maybe increased tramps.
On the bright side, it looks like the structure of the node and the code seems to work, just need to tune it a bit. For now I've returned this node back to its normal operation, without the high asc states.
M. Todd
Today I ran another OMC scan (following last week's instructions alog 87316 and 87342) after the morning lockloss to see if could a better measurement of the hot state overlaps.
I was still limited to about 12 minutes after the lockloss, so we expect some amount of difference in the full hot state.
I've plotted the results on top of last week's scans, in yellow. Analysis of this will follow in a comment.
Workstations were updated and rebooted. This was an OS packages update. Conda packages were not updated.
The second stage heating contactor had burned up, reducing heating capacity. This is why the zone had difficulty maintaining set point on 10/13. I replaced the ruined contactor and checked functionality.
Another big EQ rolling through. This one is down near Antartica! Debated when to transition to "ASC Hi Gn", since R-wave was going to be 45-60min. But S&P waves triggered EQ Mode + saw a yellow Picket Fence---Clicked on ASC Hi Gn button, but during the transition H1 lost lock. This might have been too big for ASC Hi Gn regardless, but kinda wished I clicked it earlier.
Winds were peaking just under 40mph around the lockloss as well.
Will be hanging out here for a few hours.
Now we wait for R-wave which is probably due to arrive around 2135-ish utc.
We lost lock ~3 seconds after CHARD_Y filters bits are changed, there's also a big jump in ground motion at the same time, and it was gusting >30mph at the corner station.