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.

Tue Nov 18 10:11:33 2025 INFO: Fill completed in 11min 30secs

Famis 27573 Vibration Sensors To Gauge Health Of HVAC Fans Site 

H0:VAC-MR_FAN6_170_1_ACC_INCHSEC seem to be going up in that few days especially the last 24 hours.
This is also the case for H0:VAC-MY_FAN2_270_2_ACC_INCHSEC in the last day saw a fairly large increase in noise.

1616UTC rebooted the h1guardian1 machine. This was originally to switch over nds1, but Erik informed me that we had already done this some time ago. Since we already had a WP in and this seemed like a good time to do it, I went for a reboot anyway.

All nodes came back up on their own, no issues seen.

TITLE: 11/18 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Calibration
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.46 μm/s 
QUICK SUMMARY: Locked for 22 hours, SUS charge and PEM mag. injections running now. Maintenance today, then PEM measurements for the rest of the week, because....

O4C will end in 30 minutes. What a great run! Well done everyone!!

Ibrahim, Betsy

BBSS Eliptical Baffles (D2500293) were successfully installed today. Pictures from various angles are attached.

Problems - graphics regarding these are attached as slide screenshots

• D2000483 Type 2 - 12 O'Clock Baffle Brace
  • LHO did not recieve coated parts for this*, but it does not seem like this part is visible due to the baffle itself.
    • Note*: LHO recieved one coated part weeks after ours had gone into C&B so wasn't part of same set/load - either way missing one coated.
  • This part is extremely difficult to install due to poor sighting and no room. The screw that fastens this part has to be installed from behind the figure 8, where there isn't even enough room to fit the width of a 9/64 allen wrench. A combination of tweezers, wrenches, bent T-wrenches were used and we finally got it in. However, we could not tighten much in the case of the back.
  • Potential Fix: The sides of that thru hole have free thru holes that could fit another bracket instead of the 12 O'Clock one (~11 and ~1 O'Clock).
• D2000483 Type 1 - 6 O'Clock Baffle Brace
  • Helicoil call-out is incorrectly 1/4-20 X 1.5D but using those results in the helicoils bottoming out and appearing proud. So, removed and used 1D instead - it works. Will redline
• D1900594 V10 Mounting Bracket
  • 2 of these were too long to fit into its recessed spot in the Lower Structure, which seemed like a machining issue (barely 0.2 mm if I had to guess). To fix this, betsy and I filed off the problem surfaces until they fit. The filed surface is a mating surface and we used a clean-file.
  • Part incorrectly called a wire baffle - will edit DCC and redline

Remarks: I added one of those coated screw caps to the Y-Brace (D1900589) strut fasteners since I could see it shining in the head on picture. Comparison pictures for this are below.

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.