Jonathan and Yuri

This is a continuation of WP 12886.  This is the last physical step in the control room/MSR  for the reconfiguration.  We ran a fiber from the warehouse patch pannel to h1daqdc0 and replaced the network card with a newer card.  We will be renaming h1daqdc0, likely to h1daqkc0 (daqd kafka connector), and converting it to send the IFO data into the LDAS as part of the NGDD project.

Next steps on this work is to work on the software setup, and to install the corresponding fiber patch in the LDAS room.

Checking the safe SDF settings for the LSC and ASC model.

ASC model not monitored channels here. No outstanding SDF diffs while unlocked

LSC model not monitored channels here. Also no outstanding SDF diffs while unlocked.

ASCIMC has no unmonitored channels. No safe diffs with IFO unlocked.

I've ran a few different huddle test with the new TemTop dust monitors against 3 different MetOne GT521s. The first tests I ran in the Optics lab and Diode room showed some discrepancies between the spike times but that could be due to a difference in sample times vs the two dust monitors. The PMS21 and GT521s both sample for 60 seconds then hold for 300s, but the PMD331 does not have a built in hold time so it samples continuously or manually. The PMS21 usually reads an order of magnitude or two lower than the other two which makes me wonder if it needs a scale factor, but it also sees these big spikes occasionally that the others don't see which is confusing. The flow rate is listed as being 0.1 CFM on the PMS21, but the GT521s and the PMD331 are also listed as having flow rates of 0.1 CFM. CFM = Cubic feet / minute, its also = 2.83 L/min which is what I read when running the flow test on all of the DMs. *Also the times do not account for daylight savings, so each y-axis timestamp is actually an hour behind the actual PST*.

Test 1 - Optics Lab:

I tested the TemTops one at a time in the Optics lab, the results of the PMD331 and the results of the PMS21. 

Test 2 - Diode Room:

I tested the TemTops at the same time in the Diode room, I started off with only the PMS21 then I added the PMD331. For only the PMS21 we saw the these counts, for only the PMD331 we saw these counts, and for both of them we saw these counts,all against a MetOne GT521s. 

Test 3 - Control Room:

I tested three dust monitors at the same time in the control room ( I grabbed a spare pumped GT521s from the storage racks by the OSB receiving, it's our last properly working spare). I did a day of samples with holds enabled and a day of continuous sampling. When the dust monitors were sampling at slightly different intervals we saw the peaks offset from each other such as at 11-18 ~07:00 PST at the right of the plot. During the continuous testing we can see the peaks from everyone coming into the control room for the end of O4 celebration, I'm not sure why there's some time between the peaks, zooming in on this plot to cut out the large peaks from said celebration we can see the PMD331 and the MetOne GT521s following each other pretty closely, but the PMS21 wasn't really reading  much, there are small bumps around where the peaks from the other DMs are. Adding a scale factor of 10 to the PMS21 counts yield a better looking plot, playing with the scale factor till the PMS21 counts looked more in-line with the other DMs I got to a scale factor of 40 to get this plot.

In breaks in the PEM work this morning I improved the script I used last night so that I don't have to do as many things by hand.  The script is in sheila.dwyer/SQZ/automate_dataset/SQZ_ANG_stepper.py, I'll try to clean it up a bit more and add to userapps soon.  

It's running now and will take 5 minutes of no sqz time, and do the steps needed to measure nonlinear gain (it doesn't give a result, but some times that can be looked at later).  Then it takes some angle steps in 10 degree steps on the steep side of the elipse and 30 degree steps on the slow side of the elipse (where SQZ angle changes slowly with demod angle).  

This current version should take 1 hour to take 3 minutes of data at each point, or 1.5 hours for 4 minutes of data.  

It's now running for FDS with nominal psams settings, this can be aborted if PEM wants to do injections before it's over. 

Wed Nov 19 10:09:29 2025 INFO: Fill completed in 9min 25secs

FRS36084 Dave, TJ:

TJ discovered that some HWS SLED settings were being monitored by multiple slow-SDF systems (h1syscstcssdf and h1tcshwssdf). The former's monitor.req is computer generated, the later's is hand built.

There were 4 duplicated channels: H1:TCS-ITM[X,Y]_HWS_SLEDSET[CURRENT,TEMPERATURE]

I removed these  channels from tcs/h1/burtfiles/h1tcshwssdf_[monitor.req, safe.snap, OBSERVE.snap] and restarted the psudo-frontend h1tcshwssdf on h1ecatmon0 at 09:00 Wed 19nov2025 PST. The number of monitored channels dropped from 64 to 60 as expected.

I did a full scan of all the monitor.req files and confirmed that there were only these 4 channels duplicated.

I'll add a check to cds_report.py to look for future duplications.

TITLE: 11/19 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: CALM
    Wind: 4mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.39 μm/s 
QUICK SUMMARY: Locked for 13 hours, but it looks like we just got into observing 45min ago due to an SDF diff. Lights are on at MY, Y_BT AIP still in error as mentioned in Ryan's log. Plan for to day is to continue PEM characterization. 

unamplified seed: 0.0055 amplified seed: 0.052, deamplified: 0.00073 NLG = 9.45, seems too small

no sqz: 1447564297 - 1447565492
reduced seed, adjusted temp: amplified max:0.00547 minimum 8.3e-5, unamplified: 2.54e-4 NLG 21.5

FIS, ran scan sqz angle kHz, CLF 6 demod phase left at 149.7 degrees. 1447566037

I started the script to scan squeezing angles with FIS, Ryan Short gave me a pointer on how to have my script change guardian states (puts SQZ ANGLE SERVO to IDLE now).  It is set up to try the current angle +/-10 degrees, run through a bunch of angles in 20 degree steps, flip the CLF sign and run through angles again.  When finished it should request frequency dependent squeezing again and Ryan has set things up so the IFO should go to observing when that happens.  

The script ran anf completed, the IFO didn't go to observing when it completed because I forgot to turn off the pico controler after I lowered the seed.  Here is the log of times:

log of changes : 
149.7 : 1447566755.0 
159.7 : 1447566995.0 
139.7 : 1447567235.0 
200.0 : 1447567475.0 
180.0 : 1447567715.0 
160.0 : 1447567956.0 
140.0 : 1447568195.0 
120.0 : 1447568436.0 
100.0 : 1447568676.0 
80.0 : 1447568916.0 
60.0 : 1447569156.0 
40.0 : 1447569396.0 
20.0 : 1447569636.0 
0.0 : 1447569876.0 
180.0 : 1447570116.0 
160.0 : 1447570356.0 
140.0 : 1447570596.0 
120.0 : 1447570837.0 
100.0 : 1447571076.0 
80.0 : 1447571317.0 
60.0 : 1447571557.0 
40.0 : 1447571797.0 
20.0 : 1447572037.0 
0.0 : 1447572277.0 

TITLE: 11/19 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: None
SHIFT SUMMARY:

H1 had a lockloss from an unknown source early on in my shift, but after an alignment, relocking went easily. Since then, I've been tuning magnetic injection parameters to be used later this week. Also had an alarm for an annulus ion pump at the Y-arm BTM, so I phoned Travis as I was unsure how critical this was. He took a look into it and believes addressing this can wait until morning.

I've set the remote owl operator so that H1 will relock overnight if it unlocks for some reason so that it's ready to go in the morning, but no calls will be made for help. H1 will also start observing, if it can, on the off-chance there's a potential candidate signal.

Sheila has started a script to change the SQZ angle while in frequency independent squeezing, which should take about 90 minutes and will put settings back to nominal when done, at which point H1 should go into observing.

• 00:39 - Lockloss
• 01:23 - Running initial alignment
• 02:31 - Low Noise

Jonathan, Dave, Erik, Richard,

As per WP 12886 we reconfigured the DAQD 0 computers.  The goal was to combine the functionality of the data concentrator (DC0) and frame writer (FW0) into one machine, consolidating them to one machine.  This then frees up the other machine for use with pushing data into the NGDD (Next Generation Data Delivery) kafka brokers in LDAS.

At this point h1daqdc0 is no longer the data concentrator.  H1daqfw0 is the data concentrator + frame writer.

This required a few other changes:

•  Moved h1daqfw2's data feed from h1daqnds0 to h1daqnds1
•  Moved a connection between h1daqfw0 and ldasgw0 (to mount the raw minute trends) to h1daqtw0.
  •  This was used to backup trends to their archive location, it also just makes more sense to have this on h1daqtw0.
  •   Installed a NIC in h1daqtw0 as we were out of ports.

Once this work was done and h1daqfw2 was shown to be producing identical frames to h1daqfw[01] work was able to move onto the consolidation.

The basic steps:

• Turn off the rts-transport services on DC0 (dix_xmit, cps_xmit, cps_recv)
• Turn off the rts-transport services on FW0 (dix_recv)
• Reconfigure the networking on FW0 to receive the FE DAQ data stream
  • We had some problems and ended up replacing the optic and the NIC in the FW machine.  We had gotten data flowing, but the frames were not identical.  After some investigation it was found that we were dropping data from the FE systems.  This was traced to errors on the interface.  Erik and Richard cleaned the optics, that didn't help much.  We replaced the optic, that helped, but we still had errors.  Then we replaced the NIC with one of the new NICs we had on hand and the errors went away.
  • If this had happened on DC0 it would have been easy to spot as we would have seen that as CRC errors on the main display.  But FW0 doesn't have those up.
• Reconfigure the networking on FW0 to send data to TW0
• Reconfigure TW0 to run cps_recv to be the data concentrator
• Reconfigure TWo to run cps_xmit (for TW0) and dix_xmit (for the rest of the daqd system)
• Make sure everything is working

the H1:DAQ-DC0 epics variables are used in many places, so Dave and Jonathan configured h1daqfw0 to output H1:DAQ-DC0 epics variables, and put a small IOC together to output the set of H1:DAQ-FW0 variables we need.  This is an area we need to revisit.  One likely approach is to make use of a feature in cps_recv that outputs the daqd STATUS, CRC_CPS, CRC_SUM variables and then to move the daqd on FW0 back to outputing the FW0 variables.

This work validates that we can combine the DC and FW computers into one.

The next step is to turn the old DC machine into the producer for NGDD data.  We will run the fiber to connect it through to LDAS later this week and work on setting that system up.

My checklist for this is in the DCC https://dcc.ligo.org/T2500385

TITLE: 11/18 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Planned Engineering
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: USEISM
    Wind: 13mph Gusts, 9mph 3min avg
    Primary useism: 0.06 μm/s
    Secondary useism: 0.47 μm/s 
QUICK SUMMARY: H1 has been locked for almost 2 hours and team PEM is running measurements.

• Wind low, microseism steady right around 90th percentile
• FW0 is still down due to ongoing CDS work
• All other systems nominal

TITLE: 11/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Planned Engineering
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Happy end to O4! After 4 hours of maintenance today, we relocked mostly automatic with one hiccup in the SQZ_FC guardian that was using a DC0 GPS channel that temporarily didn't exists due to the 0-leg data concentrator work that is still on going. We have been locked for almost 2 hours now and the PEM team is at work running end of run characterization.
LOG:

• 1547 Lock loss - SUS charge swapping to ITMX
• 1601 Norco at gate, headed to EY
• 1600 O4C complete
• 1616 h1guardian1 reboot
• 1620 Norco at the gate, headed to MY
  • This truck broke down and the trailer has been left at MY, truck has been towed away
• 2200 Low noise, PEM inj. starting

Link to report here.

Summary:

• H1 had an average observing duty cycle of 50.37% for the week.
• Week started with good conditions for observation, except for some seismic activity which started with an earthquake (Monday)
• Strong winds and increasing microseismic noise provoked one day (Friday) of 0% of observation and a lot of glitches the rest of the days .
• On Saturday the observation resumed until the end of the week.
• For the observing days (Monday, Tuesday, Wednesday, part of Saturday and Sunday), strong winds (still) and high microseismic noise caused locklosses.
• We observed persistent violin modes (specifically fundamental at ~500Hz) following lock-losses all week. Weak Bounce/Rolls were not observed.
• FScan Plots were available for all the days except Friday. Lowest line count on Thursdat with ~1000 lines and highest on Wednesday with ~3000 lines.
• Relevant Round Winners (Hveto only worked on Wednesday, Thursday and Sunday):
  • • H1:PSL-ISS_PDA_REL_OUT_DQ: Winner once (Wednesday).
    • H1:ASC-DHARD_P_OUT_DQ: Winner once (Thursday).
    • H1:LSC-PRCL_IN1_DQ: Winner once (Sunday).

We started installing electronics chassis for JAC:

• Heater driver, S2500960.
• DB9 breakout panel, S2500958.
• PZT driver, S2500954.
• RF doubler: S2500737.
• RF amp: S1000637 (was already installed).
• Two sat amps for JM1 and JM3, S1106042 and S2500411.

Still missing:

• Two 4-chn WFS demod chassis.
• Two AA chassis.
• JAC in-vacuum electronics interface chassis.

The necessary coax cables were also installed and terminated where possible.

The RefCav Refl spot was off this morning and the TPD had been trending down the last several days, so I took the opportunity to tweak the beam alignment into it from the Control Room.  The ISS was ON for this work.

When I started the RefCav TPD was ~0.520 V and when I finished the TPD was ~0.548 V.  I then noticed the ISS was diffracting ~4.5%, which is higher than its norm, so I adjusted the ISS RefSignal to -2.01 V from -2.00 V.  This brought the diffracted power % down to around its normal value of ~4%.  At this diffraction % the RefCav TPD is now ~0.550 V and the PMC Trans is now ~106.9 W.

I took the OPLEV charge measurements for both the ends this morning. I noticed that both of the scripts leave the L3 bias offset switch off when its should be on.

I ran into the same issue as had previously with ETMX constantly saturating no matter what amplitude I used. Jeff suggested I look at the biases and see if they're correct, the biases used for ETMX were [-9, -4, 0, 4, 9] and I changed them to [-8. -4. 0. 4. 8] in ESD_Night_ETMX.py which stopped the overflows. The L3 bias offset on ETMX is -8.9 while we're DOWN, as soon as the bias is changed to -9 I started seeing overflows. Before I changed the bias offset I was trying some different amplitudes and I was getting overflows at what looked like ~10/15k/sec for everything, i ctrl+ced out a measurement and saw that the overflows did not stop, which lead me to chech the L3 bias offset where had not correctly restored it to -8.9 as its supposed to. After changing the L3 bias offset list in the measurement code I then had to fine tune the amplitude after starting low. Amplitudes of 10000, 12000, and 20000 weren't enough, I ended up at 100,000 which gave me the best measurement I've seen in months. LR did still have some big error bars, the charge is high on LR, and UR but looks low at UL and LL, and the recent trend actually looks to be decreasing, looking at the year long trend it actually looks fairly stable considering the massive error bars on a lot of the measurements. Every quadrant is under + 100 [V].

ETMY also initially had some saturations but reducing the gain by 20% stopped them and still yielded good coherence. ETMY's charge is slightly high, it's just under + 100 [V] on 2/3 of the quadrants, UR is the only quadrant below +/- 50 [V], it has risen since May, but zooming out to the whole year it doesn't look to have much of a trend, May wasn't a great measurement.

M. Todd, J. Wright, S. Dwyer

Here is my attempt to summarize as many of the OMC scan measurements of the input beam overlap with the OMC mode, as well as PRC and SRC gouy phases -- all at different thermal states.

During PRC Align, IMC unlocked and couldn't relock due to the FSS oscillating a lot - PZT MON was showing it moving all over the place, and I couldn't even take the IMC to OFFLILNE or DOWN due to the PSL ready check failing. To try and fix the oscillation issue, I turned off the autolock for the Loop Automation on the FSS screen, and after a few seconds re-enabled the autolocking, and then we were able to go to DOWN fine, and then I was able to relock the IMC.

TJ said this has happened to him and to a couple other operators recently.

Something happened with BRSY this morning during maintenance that caused it to ring up more than normal and now the damping is not behaving quite as expected. For now, I have paused the ETMY sensor correction guardian with the BRSY out of loop and turned off the output of the BRS so it won't be used for eq mode, should that transition happen.

So far today, I did a bunch of "recapturing frames" in the BRS C# code, which has usually fixed this issue in the past. We also restarted the beckhoff computer, then the plc, C# and epics ioc. This did not recover the BRS either. Marc, Fil and I went to EY and looked at the damping drive in the enclosure and I think it was behaving okay. When the drive came on, the output would reach ~1.8V, then go to 0V when it turned off.

I've contacted UW and we will take a look at this again tomorrow.