Catching up on the DAC upgrades / CDS work earlier this week I updated some thresholds on the SUS SATMON screen. There were quite a few suspensions and stages to do this time so I decided to generate some code to string match and update the values for me so I don't have to spend the time copy pasting.

The script is called "satmon_update_sats_dac_upgrade.py" and its located in the same directory as SATMON. If you open it in an editor and scroll to the bottom you'll see how to use it. Here's an example line for updating PR2_M3 from a 18 to a 28 bit DAC card.

Jeff, Oli, Jonathan, EJ, Erik, Dave:

On Thursday 15Jan2026 we installed Jeff and Oli's new models for:

h1susmc2, h1suspr2, h1sussr2, h1susbs

h1susitmx, h1susitmy, h1susitmpi

h1susauxb13, h1susauxb2h34

Several DAQ restarts were needed for these installs. The first DAQ restart also had an EDC restart to use updated SDF and CDSMON ini files incorporating the new model names.

The models in h1susb2h34 had two sets of restarts. After the first EJ found some IPC issues which he fixed by editing H1.ipc. All the models were then restarts a second time.

In the first block of restarts h1suspr2 had two starts, the second to fix a 18bit-DAC to 20bit-DAC change.

We had three instances of new models removing channels from the DAQ which were being sent to GDS via the broadcaster. Jonathan removed these from the broadcaster list we are working today on whether they should be added back, perhaps with a different name.

Here are the models and GDS channel lists:

h1susitmx (4):

H1:FEC-29_DAC_OVERFLOW_ACC_2_[4-7]

h1susitmy (4):

H1:FEC-30_DAC_OVERFLOW_ACC_2_[4-7]

h1susauxb2h34 (3):

H1:SUS-BS_M1_NOISEMON_F[1-3]_OUT_DQ

As Jonathan details in his alog, after the restart of h1susauxb2h34 the DAQ was running with duplicate BS-AUX channels which had been added to h1susauxb2h34 and were still running on h1susauxb13 (a temporary model I built on Wed). This was resolved when the new h1susauxb13 was installed.

Restart Log

Thu15Jan2026
LOC TIME HOSTNAME     MODEL/REBOOT
12:32:41 h1susb2h34   h1susmc2    <<< First set of h1susb2h34 restarts
12:33:07 h1susb2h34   h1suspr2    
12:36:07 h1susb2h34   h1sussr2    
12:36:25 h1susb2h34   h1susbs     
12:45:57 h1susb2h34   h1suspr2    <<< Fix 18bit-DAC issue

13:07:10 h1susb2h34   h1susmc2    <<< Second set of h1susb2h34 restarts with fixed IPC
13:07:29 h1susb2h34   h1suspr2    
13:07:54 h1susb2h34   h1sussr2    
13:08:12 h1susb2h34   h1susbs     

13:32:14 h1daqdc1     [DAQ]  <<< DAQ 1-leg, new models and new EDC
13:32:25 h1daqfw1     [DAQ]
13:32:26 h1daqtw1     [DAQ]
13:32:29 h1daqnds1    [DAQ]
13:32:35 h1daqgds1    [DAQ]
13:32:51 h1susauxh56 h1edc[DAQ]  <<< EDC restart
13:34:56 h1daqgds1    [DAQ] <<< GDS1 needed second restart
13:36:31 h1daqgds0    [DAQ] <<< DAQ 0-leg
13:36:39 h1daqfw0     [DAQ]
13:36:39 h1daqtw0     [DAQ]
13:36:40 h1daqnds0    [DAQ]

14:50:28 h1susb13     h1susitmx   <<< New h1susb13 models
14:50:52 h1susb13     h1susitmy   
14:51:13 h1susb13     h1susitmpi  

14:57:31 h1daqdc1     [DAQ] <<< DAQ 1-leg restart for new models
14:57:41 h1daqfw1     [DAQ]
14:57:41 h1daqtw1     [DAQ]
14:57:43 h1daqnds1    [DAQ]
15:04:22 h1daqfw1     [DAQ]  <<< FW1 spontaneous restart
15:07:00 h1daqgds1    [DAQ] <<< GDS1 manual start after missing channels removed
15:09:02 h1daqfw1     [DAQ] <<< 2nd FW1 spontaneous restart
15:17:02 h1daqgds0    [DAQ] <<< 0-leg restart
15:17:09 h1daqfw0     [DAQ]
15:17:09 h1daqtw0     [DAQ]
15:17:10 h1daqnds0    [DAQ]

15:50:54 h1susauxb2h34 h1susauxb2h34 <<< new model (unknowingly adding duplicate chans)

15:54:02 h1daqdc1     [DAQ] <<< DAQ restart for model change, 1-leg
15:54:11 h1daqfw1     [DAQ]
15:54:11 h1daqtw1     [DAQ]
15:54:15 h1daqnds1    [DAQ]
15:54:20 h1daqgds1    [DAQ]
16:02:39 h1daqgds0    [DAQ] <<< 0-leg
16:02:45 h1daqfw0     [DAQ]
16:02:46 h1daqnds0    [DAQ]
16:02:46 h1daqtw0     [DAQ] <<< At this point FW2 is unstable due to duplicate channels, not sure why 0-leg & 1-leg are running at this point

17:23:09 h1susauxb13  h1susauxb13 <<< new model (removed duplicate BS chans)

17:23:53 h1daqdc1     [DAQ] <<< 1-leg
17:24:03 h1daqfw1     [DAQ]
17:24:03 h1daqtw1     [DAQ]
17:24:07 h1daqnds1    [DAQ]
17:31:19 h1daqgds1    [DAQ] <<< GDS1 manual restart after removing GDS chans from broadcaster
17:33:22 h1daqgds0    [DAQ] <<< 0-leg restart
17:33:27 h1daqfw0     [DAQ]
17:33:28 h1daqnds0    [DAQ]
17:33:28 h1daqtw0     [DAQ]
17:37:55 h1daqfw0     [DAQ] <<< FW0 spontaneous restart
 

TITLE: 01/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 8mph Gusts, 4mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.22 μm/s 
QUICK SUMMARY:

More alignment going on today, and going to laser safe in the afternoon

Since nobody seems to have made an alog, here it is.

We've steered the JAC transmission beam into HAM2 and removed the viewport cover on HAM2 on the +Y side to look inside. At first we had a hard time seeing anything. We steered the beam in YAW and PIT and still nothing.

After a while we found that if we position the IR viewer at a specific position and look into the baffle hole of the MC refl periscope (circled in yellow in the 1st attachment), we can see some kind of ugly IR that definitely comes from JAC, but no beam seemed to be coming out of the baffle hole.

2nd attachment shows the picture shot by an IR sensitive camra when we focused on the IR, and the 3rd attachment shows the same picture shot from the same position but focused on the  baffle.

The distance from the sensor to the subject according to the lens' indicator was something like 4m for IR and 1.5-2m for the baffle. The indicator is only good for visible light and not for IR, but empirically the scale is not a factor of 2 off for IR, so we're looking at something that is far from the baffle (i.e. we're looking at the image of the source reflected by the periscope mirrors).

Another possibility that Masayuki points out is that it could be some IR beam (probably not the main beam) hitting the vertical metal pillar of the periscope behind the bottom periscope mirror and we're looking at that through the space between the baffle hole and the periscope mirror (see the 4th attachment). I think that unlikely because the pillar is merely inches away from the baffle and the distance indicator of the lens doesn't agree. But we'll see.

Tomorrow we intend to remove the septum window cover for IFO REFL and POP and look into HAM2 from there, that way hopefully it's easier to find where the JAC beam lands in HAM2.

We had some hiccups in our end of day daqd restart.

1. There were duplicate channels between the h1susb13 and h1susb2h34 models.  We are not sure how these got through, the daqd should have crashed on startup with an error message.  We found this as it caused issues on the test framewriter on h1daqfw2.

• For reference the config hash of 562535cec2c965d73750304a89d2b169 contains the duplicate channels.  Jonathan is looking into why it didn't get flagged.

2. After Oli removed the old block from h1susb13 we found that there were some GDS broadcaster channels that were dropped that probably shouldn't be.  We removed them from the broadcast list in order to get the daqd to run.  Listing the channels here so that they can be added back in tommorow:

• H1:SUS-BS_M1_NOISEMON_F1_OUT_DQ
• H1:SUS-BS_M1_NOISEMON_F2_OUT_DQ
• H1:SUS-BS_M1_NOISEMON_F3_OUT_DQ

[Sheila, Karmeng]

Today we checked and managed to reduce some of the saturation on ZM4, and offload it onto ZM6. The changes were undone for now.

We briefly did the power budget check, but the power measured at the output of the SFI1 is fluctuating (between 0.79mW to 1.6mW) when the input to SFI1 is at 0.79mW. The power is stable down the propagation (after AP1 and SFI2), unsure what causes the fluctuation. Will continue to look into this tomorrow.

We also did an OMC scan, the pink trace is the scan when ZM4 is in its original setting (YAW: 1779.5), and the red trace is correspond to ZM4 misalignment (YAW: 1769.5).

TITLE: 01/15 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Update to "Status of Things":  HAM1-2 Septum had a viewport cover removed (so, 3 of 4 are covered) for JAC alignment.  ~100mW coming from the PSL to HAM1 for JAC (not noted on the white board).

JAC alignment work continued most of the day.  Did not roll IOT2 into place (latest plans are to do this tomorrow [Fri] afternoon) with the LVEA being transitioned to SAFE prior to this work (aiming for lunchtime).  

SQZ alignment work continued in the afternoon.

SUS model/daq work appears to be nearing completion (Jeff, Oli, RyanS, Dave (remote), EJ (remote)) !
LOG:

• 1541-1555 Optics Lab clean (kim)
• 1606-1712 LVEA cleaning (kim, nellie)
• 1625-1839 EY parts to LVEA (randy,mitch)
• 1710-1715 JAC work:  PSL lightpipe opening for JAC, no beams out of chamber (masayuki)
  • 1717-1724 Checking high voltage (masayuki)
  • 1816-2053 Out to HAM1 again (masayuki)
• 1746-2126 PCal measurements (tony)
• 1755-1720 MY cleaning (nellie)
• 1756-1802 Grabbing garb (ibrahim)
• 1830-1843 pulling/inspecting a mirror mount inside HAM1 for JAC (rahul) + joined by Jason briefly
  • 1844-1848 quick trip to optics lab to look for siskiyou mount (corey)
  • 1835-2030 EE support for JAC (marc)
• 1902-1930 JAC (jennie, daniel)
• 1916-2053 Jason joining JAC crew with 2- LH Siskiyou Mirror Mounts!
• 1922-1950 swifting FCES (kim)
• 1927-1937 CER for cable change (oli)
• 1941 Injection work around BSC2/Beer Garden throughout the day (robert)
• 2022-2031 Heading out to HAM1 (jennie)
• 2031-2055 CER to take photo of chasis (jeff, oli)
• 2130 DAQ Restart (dave)
• 2200 JAC alignment afternoon work (masayuki, jennie)
  • 2210 jason joins
• 2216-0000 SQZ alignment on floor & in the control room (sheila, karmeng)
• 2235-2312 Looking for cables at MY (travis)
• 2347 CER visual check (jeff)
• 0008 Word of DAQ Restarts done for the day (Dave)
• 0028 Robert heading back out for injection work near BSC2

FAMIS 31120

Starting last Thursday, the NPRO temperature is a bit more unstable than usual, but I'm not exactly sure why. There was a brief incursion into the anteroom last Friday, which is seen in the usual places, but everything appears to have come back as expected. The RefCav still looks to need some alignment, which I will likely get to next week. Otherwise, the PSL is looking good.

Thu Jan 15 10:08:48 2026 INFO: Fill completed in 8min 45secs

Closes FAMIS#39747, last checked 88725

Laser Status:
    NPRO output power is 1.845W
    AMP1 output power is 70.39W
    AMP2 output power is 139.1W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 6 days, 18 hr 2 minutes
    Reflected power = 26.47W
    Transmitted power = 104.5W
    PowerSum = 131.0W

FSS:
    It has been locked for 2 days 23 hr and 18 min
    TPD[V] = 0.4029V

ISS:
    The diffracted power is around 4.0%
    Last saturation event was 0 days 0 hours and 0 minutes ago

Possible Issues:
    PMC reflected power is high

TITLE: 01/15 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 9mph Gusts, 5mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.25 μm/s 
QUICK SUMMARY:

JAC work continues with IOT2L being rolled up to HAM2 this morning for [IOT2 will be later today or Fri] alignment checks & IMC locking.  Equipment moves in LVEA and from EY, and I believe there is more Squeezer alignment as well at HAM7.

For FAMIS #39850: All fan trends look nice and flat.

Kar Meng, Sheila

This afternoon we aligned the squeezer beam to AS_C, AS_A, and AS_B QPDs.  This is currently done with OM1, OM2, SRM, and ZM6 at the same alignment they were at in the end of O4.  That means that the beam location on ZM5 should be the same as it was at the end of O4 (75732).  With this alignment, we are using up most of the actuator range on ZM4, so we will either have to move ZM6 and the spot position on ZM5, or mechanically yaw ZM4.  We can't easily reach ZM5 with an IR card to check if the beam position on it is centered, if we can find a way to get an IR card on a long stick to asses that centering that would be helpful.  

As part of this, we set up alignment loops from AS_A to ZM4 and AS_B to ZM5, they are slow but reliable.  I will attach a screenshot of settings here tomorow.

We also checked the alignment of the beam onto the CLF FIBER rejected PD, which was off because the fiber collimator was tilted to realign the the new OPO cavity axis.  Kar Meng adjusted the pitch of the TFP, then slid the PD to center the beam in yaw, and lastly yawed the PD to make sure the reflection was going nicely to the black glass V.  

TITLE: 01/14 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

Today's big activities:  JAC alignment continues  at HAM1.  SUS model/daq work continues from Control Room and CER.  HAM7 squeezer alignment continues.
LOG:

• 1545 sus model/daq begins with daq restart (jonathan/cds)
  • 1810 CER (olli,jeff)
  • 1828 CER for power supply rack install (marc)
  • 2124 Oli left + Marc went out again to help with AntiAlias issue.
  • 2228 Jeff confirms Marc's work was complete and CER work is done.
• 1556-1704 LVEA technical cleaning, checks, prep (kim.nellie)
  • 1758 Kim back to LVEA
• 1653-1937 Checking lasers and taking meeting in PCal Lab area (tony)
• 1713 nuc20 restarted for a new CDS Overview (dave)
•  1743-2337 Y-arm trailer moves to EY (randy)
• 1747 HAM1 JAC begins morning work(Masayuki)
  • 1811 -1855 Rahul
  • 1814-1842, 1934- Jennie
  • 1913 Betsy running parts out
• 1845-1854 Parts search (travis)
• 1936-1942 Checking light fixture in LVEA (eric)
• 2017-0008 HAM7 alignment work continuing (sheila,karmeng)
  • 2207 Sheila/Karmeng out for control room work
  • 2309 Sheila/Karmeng back to HAM7
• 2119 JAC Alignment for afternoon (jennie,masayuki,keita)
  • 2119 Gerardo joining to help with VAC/viewports
  • 2155 Jennie out
  • 2306 Jennie, Jason heading to HAM1
  • 2336 Rahul out, 2359 Jason out
• 2150-2354 Switching integrating spheres in PCal lab (tony)
• 2200-2235 putting panels back on chasis in CER (dave)

Marc, Jeff, Fil, Oli

Yesterday we pulled most of the AI chassis (D1000305 or D1600077) from SUS-C1 and SUS-C6, modified them for ECR E2400409 and E2500296 (IIET 35739 and 35706, respectively), and reinstalled them as part of our work converting SUSB123 and SUSH34 into SUSB13 and SUSB2H34 (88765). 

Every AI chassis in SUS-C1 and SUS-C6 was meant to be pulled, upgraded, and reinstalled EXCEPT SUS-C1 U24. Additionally, we needed to also modify a spare D1000305 AI chassis for installation into SUS-C2. We did all this, but along the way we accidentally also pulled and upgraded the AI chassis in SUS-C1 U24 (previously S1104380). Luckily, we hadn't modded the spare (S2100712) yet so we installed it into SUS-C1 U24 and installed that modified chassis in the SUS-C2 U14 spot.

Here are the steps for how we modified the AI chassis:
- Disconnected all affected AI output cables in SUS-C1 and SUS-C6
- Removed the existing 6x 2x 8CH DAC AI chassis (D1000305 or D1600077),
- Modified them to become D2500353 1x 32CH AI chassis 
    . Replaced the 2x 8CH AI rear panel with WD relays (D1000551) with 1x 32CH AI rear panel without WD relays (D2500097)
    . Replaced the 2x 8CH back panel (D1000552 with 1x 32CH back panel (D2400308)
- Relabeled AI chassis from D1000305 to D2500353, or from D1600077 to D2500397, and reinstalled
- Cabled everything up according to the corresponding version of the wiring diagram (SUSB13, SUSB2H34)

Pulled, upgraded, and reinstalled:
                                            D1000305 > D2500353     D2500097
SUS Chain               Rack / Position     Chassis S/N             Rear Board S/N     32CH DAC Card / IO Slot    Channels
ITMY M0/R0/L1           SUS-C6 / U38        S1108073                S2501317           DAC0 / Slot#2              0-15

ITMX M0/R0/L1           SUS-C6 / U37        S1108072                S2501319           DAC0 / Slot#2              16-31

ITMY L2, ITMX L2        SUS-C6 / U35        S1108074                S2501316           DAC1 / Slot#4              0-15

MC2 M1,PR2 M1,SR2 M1    SUS-C1 / U31        S1104379                S2501321           DAC2 / Slot#5              0-15

SR2 M1, MC2 M2/M3       SUS-C1 / U30        S1104368                S2501320           DAC2 / Slot#5              16-31

                                            D1600077 > D2500397
                                            Chassis S/N
ITMX ESD, ITMY ESD      SUS-C6 / U21        S1600245                S2501318           DAC1 / Slot#4              16-27

Upgraded and newly installed (technically was pulled from SUS-C1 U24 by accident):
BS M1/M2                SUS-C2 / U14        S1104380                S2501322           DAC3 / Slot#6              0-11

NOT upgraded but chassis swapped:
                                                    D1000305              D1000305
SUS Chain                        Rack / Position    Chassis S/N Before    Chassis S/N Now    
PR2 M2, PR2 M3, SR2 M2, SR2 M3   SUS-C1 / U24       S1104380              S2100712

J. Kissel, F. Clara, O. Patane, M. Pirello, D. Barker
ECR E2500296, E2400409
WP 12962
D2300401 (for susb13) and D2300383 (for susb2h34)
G2301306 -- PARTII 2023 plan, PARTII Update 

We've completed all electronics hardware moves, cabling/recabling and new installations that we plan to do on SUS MC2, PR2, SR2, BS, and the future LO1 and LO2 for now.

Given that this change to the electronics is somewhere in between versions of the D2300401 h1susb13 and D2300383 h1susb2h34 wiring diagrams -- the interim configuration we're in now that 

    Does have
        - susb2h34 and susb13, as well as susauxb13 and susauxb2h34 with all their ADC and DAC cards, as they will be in O5.
        - All of the BS electronics have been moved from SUS-C5/SUS-C6 to SUS-C1/SUS-C2, and their CER cabling dragged along with it
        - all AI chassis driven by 28-bit 32CH DACs (7 in total) have been converted from a pair of D1000305 2x8CH DAC AIs to a pair of D2500353 1/2x32CH DAC AIs.
        - ITM AA chassis inputs (both OSEM sensors, optical levers, and CD monitors) and AI chassis outputs have been re-arranged such that the grouping is far more sensibly arranged and modular per QUAD.
    
    Doesn't have 
        - BBSS-like BS TOP mass converted to QOSEMs
        - BBSS-like BS M3 OSEM sensing and actuation electronics
        - Any LO1 or LO2 electronics
        - The BS optical lever in its final AA chassis position (because the BS TOP mass OSEMs still need that spot)
        
        - Any changes to the field cabling
            - the BS M1 satamps, M2 satamps, and M3 optical lever whitening chassis are all still in SUS-R6)
-- we planned /documented all of this work on google slides -- see PARTII Update -- which is linked in the abstract of G2301306.

We'll add more details, gotchas, and pictures below in the comments.

Wed Jan 14 10:10:16 2026 INFO: Fill completed in 10min 12secs

TITLE: 01/14 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: None
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.45 μm/s 
QUICK SUMMARY:

Foggy morning on site where the LVEA continues to be in Laser HAZARD for in-chamber work at HAM1 & HAM2.  

MuseumEXP continues with new-exhibit work at LExC this week.

Attached is the mode-matching layout for the VOPO. The target primary waist of the VOPO (from TT1700104) is 221.2um(s), 206um(t) for 1064nm and 159.2um(s), 148.8um(t) for 532nm.

The mode matched minor and major beam waist is 198.6um, 204.2um for 1064nm and 152.6um, 185um for 532nm. For the fundamental injection via the rear mirror, the measured waist is 197.25um, 231.85um. These waist is measured at the position marked with a "star". The mode-matching calculation has been reviewed by a fur-low scientist.