TJ, Jeff, Oli

It was brought up that it would be nice if we had a guardian state for taking our regular suspension health check transfer functions, since it requires a few different things to be changed, some of which differ from sus type to sus type. So I created three new states, PREP_HEALTH_CHECK (67), which gets everything in the correct state for running our default transfer functions, HEALTH_CHECK (70), which is just an idle state, and REVERT_HEALTH_CHECK (73), which reverts the changes made in PREP_HEALTH_CHECK. I set the edge of PREP_HEALTH_CHECK to come off of FULLY_ENABLED, and then REVERT_HEALTH_CHECK comes back around and goes into FULLY_ENABLED (state graph).

The things that need to be true for every suspension type are:

• Top mass coil driver state set to 1 (unless permanently jumpered to 2) (here are the optics+stages for LHO that need their coil driver states changed)
• Test bank outputs switched ON
• Test bank gains set to 1
  • making sure to save the gain and then put it back when leaving the HEALTH_CHECK state
• Damping bank outputs OFF
• Alignment biases OFF

Additionally, there are some sus specific requirements:

• (QUAD R0) Turn off any Main Chain L2 to Reaction Chain R0 damping/tracking
  • aka turn off the outputs to the R0's L2 WIT DAMP block (SUS-{QUAD}_R0_L2DAMP_{L, P, R, Y})
• (BSFM) Turn off any optical lever damping loops
  • aka turn off the outputs to M2's OLDAMP block (SUS-BS_M2_OLDAMP_{P, Y})
• (TMTS) Turn off any QUAD to M1 damping / tracking
  • aka turn off the output to M1's FF_L block (SUS-{TMTS}_M1_FF_L)
• (OMCS / OMs / RMs) Turn off any ISC DC centering input
  • aka turn off the output to M1's LOCK block (SUS-{OMCS, HTTS}_M1_LOCK_{L, P, Y})

Ibrahim, Betsy

Today Betsy and I successfully installed the shear plates onto the BBSS. In the attached pictures, you can see:

• the shear plates with their half coating
• the Y stiffness brackets that attach the Upper structure to the PUM tablecloth to the shear plates
• The gap for the HRTS mount

Next, I intend to install the HRTS mount, the HRTS itself and start B&K (with Rahul)

FAMIS 26044, last checked in alog84268

The script reports BSC high frequency noise is elevated for the following sensors:

ITMX_ST1_CPSINF_V1
ETMY_ST2_CPSINF_V2

Dry air skid checks, water pump, kobelco, drying towers all nominal.

Dew point measurement at HAM1 purge inlet port, prior to pumpdown, -43.7 °C. 

The HAM1 purge exhaust dewpoint at top of chamber was measured to be -40.3C just before turning off the purge and starting pumpdown.

Jonathan, Patrick, Janos, Ryan, Dave:

The HAM1 pressure gauge PT100 is temporarily only available as a raw voltage signal (H0:VAC-LY_X0_PT100B_PRESS_VOLTS).

I wrote an EPICS IOC which reads this voltage signal, converts it to a pressure (Torr) and exports it as a "H1" version of the PT100B cold cathode signal. The new EPICS channel is:

H1:VAC-LY_X0_PT100B_PRESS_TORR

The new IOC is currently running in a tmux session on opslogin0. It was started at 11:31 Tue20may2025, at which time HAM1 was still at atmospheric pressure (10.0V, 750Torr)

WP12558 was opened to add this new channel to the DAQ so that this week's HAM1 pump down could be trended.

We restarted the DAQ 0-leg at 12:16, the EDC at 12:17 and the 1-leg at 12:22

I took the opportunity to complete WP12523 and add the new CDS rack power strip EPICS channels to the EDC.

EDC details:

Addition of H1EPICS_VACHAM1.ini (3 channels) and H1EPICS_PWRSTRIP.ini (36 channels) for a total additon of 39 channels, which give a new total of 59,311 chans in the EDC.

I added the new HAM1 pressure channel to the vacuum overview (see attached).

The pump down was already on its way when we added it to the DAQ, attached trend shows data is available from 12:22 onwards, at which time the pressure was at 200Torr

Tue May 20 10:05:48 2025 INFO: Fill completed in 5min 44secs

FRS34130

On Friday 16th May 2025 several cameras whose processes are running on one of the new AMD EPYC 9124 servers stopped working. Their MEDMs went "white-box" and their camera images went "blue-screen". The cameras and their last good data points are:

FC2 04:02

FC_TRANS_B 09:00

ETMX 10:03

ETMY 11:01

Note ETMX h1cam25 was not pingable, all the others were.

Yesterday I went to EX and EY to investigate. I power cycled both end station cameras by disconnecting their ethernet from the POE injector. After restarting their processes they came back online.

On the way back I did the same for the FC_TRANS_B from the CDS mezzanine in the FCES.

This morning I found that FC2 had also stopped (more about that laater) and got it running again by just restarting its process, no camera power cycle needed.

Looking at the logs we found 

"WaitObject duplicate failed (0): Too many open files. Reached open files limit"

type errors around these times. Debian has a limit of 1024 open file descriptors per process, and scanning the /proc/<pid>/fd/ dir sizes for h1digivideo5 showed that FC2 had 1024 open, which is how we found that camera had stopped working at 04:02 Friday.

Two immediate action items:

1. install num_open_fd check in cds_report for camera processes to trend and alert on an hourly basis if we are getting close to the limit
2. investigate if pylon code is responsible and if so can it be fixed.

TITLE: 05/20 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, 1mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.28 μm/s
QUICK SUMMARY: Pumpdown of HAM1 starts today as the main activity. The LVEA is currently Laser SAFE.

Workstations were updated and rebooted.  This was an OS packages update. Conda packages were not updated.

VACSTAT went into sensitive mode after BSC3 PT132_MOD2 glitched, spending 2 seconds at 3.2e-07Torr before returning to 1.5e-07.

I have restarted VACSTAT to clear this glitch.

Gerardo, Jordan, Travis, Randy, Janos

Today between 10 am and 2 pm both the Y+ and Y- HAM1 doors have been installed. The installation went smoothly, no issues were found.
A valve on the new interlock gauge-assembly was opened, and the HAM1 volume will be purged overnight. This is to clean the in-vacuum surfaces before pumpdown, resulting in lower gas load and therefore faster pumpdown.
After the door installation, the pumpdown of the joint HAM1/HAM2 Annulus volumes have been started. 2 turbo/pumping cart systems are pumping the volume, they are standing next to HAM1 and HAM2 - see attached photo.

Please do not move the pumping carts, as it can result in immediate damage in the turbo pumps. If you still need to do any activities which need these pumping carts to be moved, please talk to vacuum team members first!

TITLE: 05/19 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Doors are on HAM1 and things are being wrapped up in order to start pumping down!
LOG:

FAMIS 31406

The sock filters had slight discolorization, but there were floating string-like particulate in both reservoirs (pic1 & pic2). This isn't a new finding, but I was hoping after the last flush in October that it would have reduced the amount of floaters over time as they were filtered out, but this doesn't seem to be the case.

As per WP 12455 Dave and Jonathan replaced the power supply on h1daqframes-1.  Due to the available space in the rack we decided to power off the system so that we could move it safely and replace the power supply.

We did some double checking to verify which machines where hooked together.  We followed the physical connections and cross checked them with the names and numbers for interfaces on each machine.  This was good as the labels on the front of the system where wrong.  This is the frame disk associated with h1daqfw1.

We powered down h1daqfw1, verified that the link to h1daqframes-1 had gone dark.  After that we powered off h1daqframes-1 pushed it forwared enought to replace the power supply, pushed it back in th place and restarted it.

After the disk server was back we restarted h1daqfw1 as well.

Dave will fix the labeling.

TJ, Camilla, Sheila

TJ and Camilla got the HWSs working, and now we turned on the SR3 heater at 15:54 UTC, 2W requested power.  This is to do a check of the SR3 heater calibration and range similar to 27262

Camilla made these measurements with 20W input power into the IMC, PRM and ITMY misaligned single bounce beam.  We didn't place the 90/10 BS M12 in the pop path yet so that we would have about 35uW to measure beam profiles. There's a rough pen sketch of where these locations are in this photo.

Camilla also made ruler measurements of some distances:

• PM1 to 50/50 BS M15 is 405mm
• PM1 to center of L2 is 229 mm
• center of L2 to M15 is 178 mm
• dichroic M10 to PM1 is 360 mm
• bottom of periscope  (M8 or M9) to dichroic M10 482mm
• HR side of M15 (50/50 BS) to front of LSC diode box is 158 mm, diode itself is 3 mm proud of diode box.