TITLE: 06/25 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 145Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

Currently Observing at 150Mpc and have been Locked for just over 2 hours. Relocking went pretty smooth, with the only issue being DRMI/PRMI taking very long to catch still. During maintenance today, the auxiliary pumps around HAM1 were turned off, and the jitter noise that we had been seeing around 550-600Hz is basically almost fully gone.

LOG:

14:30 Observing at 145Mpc and have been Locked for almost 4 hours
14:45 Out of Observing to run SUS Charge measurements
15:00 Lockloss during SWAP_BACK_ETMX
    - It doesnt look like it was due to anything that was happening with the swap

19:31 Started relocking
    - Initial alignment
    - Lockloss from MOVE_SPOTS
22:33 NOMINAL_LOW_NOISE
22:34 Observing

Ryan S., Elenna

Ryan and I are still trying to speed up the MOVE_SPOTS state. Today, Ryan implemented new code that checks the convergence of the loops and only ramps up the ADS gains of loops that are not yet converged to help them converge faster. This appeared to work well, although the state is still slow. We are now taking the spots to the FINAL spots that the camera servos go to, instead of some old spot, so it's possible that which loops that are far off have changed.

Ryan also pointed out that the ENGAGE_ASC_FOR_FULL_IFO state is taking a while because it is limited by the convergence of the PIT3 ADS. This is likely because the POP A offset used in DRMI ASC is not quite right, so I adjusted it for pitch so the PRM should be closer to the full lock position. SDFed.

The last work that was done for the estimator was back on May 21st 84548. The data that I got then was of the Open Loop TFs for when SR3 OSEMINF gains were nominal (aka what they are now) vs our 'more calibrated' values that are shown in 84367. I then wrote a script that takes in the OLTF traces that were exported from diaggui and divides them for each DOF (results). The average between the two divided traces is what we are going to be using as the gain values needed to counter the 'more calibrated' values. I put these gains in as FM7(previously had old unused gains in) in the DAMP filter bank.

Today I changed the M1 coil driver state to 1, set the OSEMINF gains to the ones listed in 84367,  turned on FM7 for all degrees of freedom in the DAMP filter bank to turn on the gain corrections, changed the gain for DAMP Y to be -0.1 instead of the nominal -0.5, and then took SUSPOINT to M1 transfer function measurements.The measurements can be found in: /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/Common/Data/2025-06-24_1700_H1ISIHAM5_ST1_WhiteNoise_SR3SusPoint_{L,T,V,R,P,Y}_0p02to50Hz.xml, in svn as r12356.

After that, I took regular transfer functions with damping on for SR3 M1 to M1. Unfortunately I accidentally took the transfer functions for Pitch with the wrong bin width, so the original xml file there has double the values as the other ones. The saved .mat file, though, has the data all the same size. The measurements can be found in: /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Data/2025-06-24_1900_H1SUSSR3_M1_WhiteNoise_{L,T,V,R,P,Y}_0p02to50Hz.xml, in svn as r12359. The results are found in: /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/SR3/SAGM1/Results/2025-06-24_1900_H1SUSSR3_M1_ALL_TFs.pdf, also r12359.

After these measurements, everything was put back to how it was before, including the OSEMINF gains, the DAMP Y gain, and the DAMP FM7 filters turned back off.

Range comparison plot:
Command Ran:  python3 range_compare.py 1396833438 1434842418 --span 1800
time 1 is April 11th 2024
time 2 is today at 23:20 UTC June 24th 2025
 

(Jordan V., Gerardo M.)

Today we replaced the MKS gauge at FC-C-1, this is the first 6 way cross inside the filter cavity tube enclosure, we installed serial number 390F00490, twice, yes two times.  It turns out that the flange has some scratches on the knife edge, and it was not going to seal regardless of the effort that we put into it.  Once the gauge was removed the scratches transferred to the copper gasket.  We replaced it with serial number 390F00495, this one seems to be doing good.  New conflat was leak tested and no leak was detectable above 2.42e-10 torr*l/sec.

The old gauge serial number is 390F00406 with a date code of June 2021.

TITLE: 06/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 7mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.06 μm/s
QUICK SUMMARY:
H1 has been Locked for close to an hour.

Note:
CDS Alarm H0:VAC-LY_Y3_PT114B_PRESS_TOUR  alarmed at 1434843240.  Oli metioned that Davis said this is nothing to worry about, I'm just documenting it here.
Everything else looks fine.
 

I did a very quick search and didn't find any other posts, so I putting a plot here comparing the motion of the pre-vent HAM1 TT L4C passive stack motion to the current HAM1 ISI motion. ISI motion is generally 1-3 orders of magnitude better, only with a very narrow window at 15hz where the passive stack barely reached down to the ISI motion, but only for the x dof. Blue, green and brown are the ISI, cyan, pink and black are the passive stack.

Almost done with the st0 feedforward, X,Y,Z and RY are running. Still have to do tilt decoupling (which will improve low frequency motion), vac work at the chamber kept tripping the ISI during my measurements this morning.

Following the restart of any vacuum Beckhoff controller it is necessary to burt-restore the settings back to what they were prior to the restart (e.g. CP PID settings). We are using the slow controls Vacuum SDF to display which settings need to be restored, but the SDF cannot do the revert itself since it runs on a non-authorized server (h1ecatmon0) which does not have write access to the vacuum system.

Previously I had written a script in user vacuum's home directory on zotvac0 to do this restore for h0vaclx, today I made the script generic, taking the system to be restored as an argument.

The restoration process following a restart of a vacuum system is now:

On any CDS workstation open the vacuum SDF window showing the differences list, we will use this to verifty the restore worked correctly

As user vacuum on zotvac0 (restricted access to vacuum team, CDS and OPS) run the ./burt_restore_vac.bsh script with no arguments to get the usage:

vacuum@zotvac0:~$ ./burt_restore_vac.bsh 
Incorrect arguments given
 
Usage:
    burt_restore_vac.bsh SYS
    where SYS is one of:
    lx ly ex ey mx my mr
 
This morning I ran the script with argument = ly which correctly restored the h0vacly settings to those in h1vacuumsdf's safe.snap file***

Sheila, Camilla, WP#12632.

Moved OPO Crystal Spot using instructions in 80451, last done in January 2025 82134.

• Starting Position: forth spot from the left. 0.830V is the height of green 00 mode. 41% of green power in 01 mode
  • Alignment looked very bad, photos attached. 
• Ending Position: second spot from the left. 2.23V is the height of green 00 mode. 36% of green power in 01 mode
  • Note that we have used this spot before but LLO found that it was okay to go back to old spots and this spot looked better than the edge spot

For all of the used spots we moved through, to the left of the co-resonance, the loss suddenly increased as in the spot to the side of the current co-resonance was in the past used. This made us think that we are set to a different temperature to other times we have moved the spot. 

Measured NLG to be 10 with the OPO TRANS setpoint set to 95uW, the NLG was very low 7 with 80uW, hence staying at 95uW, the NLG's seemed to have dropped this week 85252, we don't know why. 

Tagging OpsInfo: This change will mean that for the next week or so we'll need to more regularly adjust the OPO TEC temperature, instructions are in 80461. Should be done pro-actively when relocking and if range is low in observing. Pop out of observing to adjust while in Observing. 

Today's h1asc model change was a good opportunity to consolidate the new model build procedure now that H1 models are rev-locked (source code locked to specific subversion revision numbers).

1) build the model as normal to verify that it builds (user controls on h1build)

> rtcds build h1asc

2) run model through check_model_changes to check if DAQ changes are pending (user myself on opslogin0)

> check_model_changes h1asc

In this case 4 fast channels are to be added to the DAQ

3) run rev-update on model to check subversion status (user controls on h1build)

> rtcds rev-update h1asc

This showed that the h1asc.mdl model has local mods pending commit.

4) commit local mods to subversion (user myself on opslogin0)

Using the DAQ change information from 2) I committed h1asc.mdl to subversion

> svn ci -m "Elenna 23jun2025 add 4 DQ chans DC6_[P,Y]_[IN1,OUT]" h1asc.mdl

5) run rev-update again (user controls on h1build)

> rtcds rev-update h1asc

At this point I was able to accept svn HEAD as the rev-lock versions for h1asc's source files

6) do a rev-locked build of h1asc (user controls on h1build)

> rtcds build --rev-locked h1asc

7) install the model (user controls on h1build)

> rtcds install h1asc

J. Kissel

In order to prepare for implementing ECR ECR E2400330 which improves the whitening within the UK sat amps to improve the OSEM signal chain's total sensor noise between 0.05 and 10 Hz (see CSWG:11249 for a model of the noise improvement), I want to be sure we have a up-to-date measurement of the damping loop's suppression. This is so it can be divided out from the estimate of sensor noise before vs. after the change. Also, in general, it's good it we have pre-tuned templates for open loop gain transfer functions, as they use a markedly different excitation than "standard" "health check" transfer functions because the excitation must go through the damping loop controller filter.

Note: if we compensate for the change in satamp frequency response well (with the anti-whitening filters in the OSEMINF banks), then the open loop gain / loop suppression / close loop gain should remain unchanged across the whitening filter change, so one we have these we shouldn't need to take them again (unless commissioning demands more changes to the filters). 

Since this kind of inventory is best done digitally for other folks reference and in case I have to delegate, I share it here. 
The following is a table of available and believed "should be the same as now" open loop gain TF templates and aLOGs for all suspensions with UK satellite amplifiers (and the Filter Cavity HSTSs FC1 and FC2 for good measure).
Where there isn't templates that are "still valid," I give a brief note as to why. 

Optic    aLOG             Templates                                                                                         Still Valid?        If not, why not?
ETMX M0  (n/a)            none                                                                                              NO                  *Never measured
ETMX R0  (n/a)            none                                                                                              NO                  *Never measured

ETMY M0  LHO:6933         2013-07-??_????_H1SUSETMY_M0_*_WhiteNoise_OLGTF.xml                                               NO                  *Way old, not enough DOFs
ETMY R0  LHO:68405        2023-04-04_1731_H1SUSETMY_R0_WhiteNoise_*_0p01to50Hz_OpenLoopGainTF.xml                           Yes                 *But would be good to remeasure w/ and w/o R0 tracking

ITMX M0  LHO:7720         2013-09-10_2306_H1SUSITMY_M0_[R,V]_WhiteNoise_OLGTF.xml                                           NO                  *Way old, not enough DOFs
ITMX R0  (n/a)            none                                                                                              NO                  *Never measured

ITMY M0  (n/a)            none                                                                                              NO                  *Never measured
ITMY R0  (n/a)            none                                                                                              NO                  *Never measured

TMSX     (n/a)            none                                                                                              NO                  *Never measured

TMSY     LHO:6654         2013-06-06_1511_H1SUSTMSY_M1_[L,P]_WhiteNoise_OLGTF.xml                                           NO                  *Only L and P measured
 
BS       LHO:71269        2023-07-12_2000_H1SUSBS_M1_CDBIOState_1_WhiteNoise_*_0p01to50Hz_OpenLoopGainTF.xml                Yes                 *Oplev Damping OFF
         LHO:71465        2023-07-18_1740_H1SUSBS_M1_CDBIOState_1_OLDampingON_WhiteNoise_*_0p01to50Hz_OpenLoopGainTF.xml    Yes                 *Oplev Damping ON

MC1      LHO:85291        2022-10-13_1900_H1SUSMC1_M1_CDBIOState_1_WhiteNoise_*_0p01to100Hz_OpenLoopGainTF_new.xml          Yes

MC2      LHO:85291        2022-10-13_1900_H1SUSMC1_M1_CDBIOState_1_WhiteNoise_*_0p01to100Hz_OpenLoopGainTF_new.xml          Yes

MC3      (n/a)            none                                                                                              NO

PRM      LHO:85292        2022-10-13_1900_H1SUSMC1_M1_CDBIOState_1_WhiteNoise_*_0p01to100Hz_OpenLoopGainTF_new.xml          NO                  *EPICs gains changed since

PR2      LHO:85292        2022-10-12_2020_H1SUSPR2_M1_CDBIOState_1_WhiteNoise_*_0p01to100Hz_OpenLoopGainTF_new.xml          NO                  *EPICs gains changed since

PR3      LHO:64152        2022-07-26_1820_H1SUSPR3_M1_WhiteNoise_*_0p02to50Hz_OpenLoopGainTF.xml                            Yes

SRM      LHO:85285        2025-06-24_1704_H1SUSSRM_M1_WhiteNoise_*_0p01to100Hz_OpenLoopGainTF.xml                           NO                  *EPICs gains changed since

SR2      LHO:65314        2022-10-13_1900_H1SUSMC1_M1_CDBIOState_1_WhiteNoise_*_0p01to100Hz_OpenLoopGainTF_new.xml          NO                  *EPICs gains changed since

SR3      LHO:85255        2025-05-21_1800_H1SUSSR3_M1_WhiteNoise_*_0p02to50Hz_OpenLoopGainTF.xml                            Yes

FC1      LHO:85290        2022-10-14_2330_H1SUSFC1_M1_CDBIOState_1_WhiteNoise_*_0p01to100Hz_OpenLoopGainTF_new.xml          Yes

FC2      (n/a)             none                                                                                             NO

OMC      LHO:60054        2021-09-28_1640_H1SUSOMC_M1_WhiteNoise_*_0p02to50Hz_OpenLoopGain_2014vs2021Designs.xml            Yes

IM1      LHO:64039        2022-07-19_H1SUSIM1_M1_WhiteNoise_*_OLG.xml                                                       Yes

IM2      LHO:64039        2022-07-19_H1SUSIM2_M1_WhiteNoise_*_OLG.xml                                                       Yes

IM3      LHO:64039        2022-07-19_H1SUSIM3_M1_WhiteNoise_*_OLG.xml                                                       Yes

IM4      LHO:64039        2022-07-19_H1SUSIM4_M1_WhiteNoise_*_OLG.xml                                                       Yes 

So -- to we really need to focus our measurement energy on the QUADs which have really never been characterized and the recycling cavity HSTS which have their EPICs gains changed in 2023.
The good news is that 2023 me tuned a full set of QUAD R0 open loop gain TF templates using ETMY, so these templates should be viable for both the rest of the R0 chains as well as the main chain with little-to-no tuning (assuming alignment biases are not eating up a different amount of DAC range).
That leaves on the TMTS not having tuned templates, so that's where we'll have to spend our tuning time.
We obviously have templates that will work for the missing / out-of-date HSTSs.

I'll begin the campaign during upcoming Tuesdays, in advance of making the ECR E2400330 change.

WP12623 h1asc add fast channels to DAQ

Elenna, Dave:

A new h1asc model was rev-locked and installed. Four new fast DQ channels were added to the DAQ (channel, rate):

> H1:ASC-DC6_P_IN1_DQ, 256
> H1:ASC-DC6_P_OUT_DQ, 512
> H1:ASC-DC6_Y_IN1_DQ, 256
> H1:ASC-DC6_Y_OUT_DQ, 512

DAQ restart needed.

WP12570 Restart Digivideo Cameras with latest pylon

Patrick, Jonathan, Dave:

Jonathan updated pylon on h1digivideo[4,5,6] and restarted all the camera servers on these machines. This should fix the bug of stuck open files accumulating when the camera connection is interrupted.

No DAQ restart needed.

Add PID SMOO channels to vacuum SDF

Dave:

Prior to today's h0vacly restart I added the missing CP PID-control SMOO channels to the vacuum SDF monitor.req and safe.snap files. SDF was restarted 08:29. No DAQ restart needed.

WP12577, 12608, 12615 Upgrade LY Vacuum Controls

Janos, Gerardo, Patrick, Jonathan, Erik, Dave:

Patrick installed a new h0vacly system this morning. Main items are:

• Renaming of FCES Ion pump channels
• Removal of old PT100 channels

Pleae see Patrick's alog for details.

A extended DAQ restart was required, renaming Ion Pump raw minute trend files for uninterrupted lookback and construcing new PT100 (HAM1) raw minute trends following the upgrade of h0vaclx last Tuesday (17th June 2025).

DAQ Restart

Jonathan, Erik, Patrick, Dave:

Immediately following the restart of h1asc at 11:52, the DAQ was restarted using the following procedure:

1. both trend writers were turned off, allowing raw minute trend file changes on a static system
2. ip_copy_scripts.bsh was ran on both TWs, for each Ion Pump channel which is being renamed, this copied the old file into the correct directory for the new file, preserving recent lookbacks.
3. Erik ran his script to merge the previous HAM1 PT100 data sets into the new channel name.
4. A new H0EPICS_VACLY.ini was generated
5. 0-leg was restarted, followed by a EDC restart on h1susauxb123
6. 1-leg was restarted, requiring a second restart of GDS1.

It was at this late point that I remembered that the temporary H1 version of PT100B is no longer needed, and indeed this channel has no data following the removal of the PT100B Volts channel from h0vacly. However since it is still in the EDC, we need to continue running the temporary IOC until the next DAQ restart. I've removed it from edcumaster.txt as a reminder.

GPS Leap Seconds Updates

Jonathan, Erik, Dave:

Erik's FAMIS task reminded us that the leapseonds files expiration date of 30 June 2025 is rapidly approaching. Although no leap seconds are to be applied, the files need to be updated to reset their expiration dates. Please see Erik and Jonathan's alog for more details.

DNS testing 

Erik:

ns1 (backup DNS server) was used by Erik to see if we can reproduce the error whereby loss of connection to GC caused internal CDS name resolution issues. It did not.

Kiet, Evan, Anamaria 

We noticed that since August 24th, 2024—following the detector maintenance break in O4b—NonSENS has been consistently injecting noise into the 58–60 Hz band.

The ratio of strain after/before cleaning has been tracked via the DetChar summary pages. Attached to this alog are three examples, taken on August 24th, 2024; December 23rd, 2024; and March 31st, 2025. The peak around 58–60 Hz appears to grow over this period, and and remains present after the O4c commissioning break. 

We’ve also attached the NonSENS noise budget for March 31st, 2025. It shows a peak in the jitter noise at 58–60 Hz, which aligns with the band NonSENS has been injecting noise into, so perhaps it is not subtracting jitter correctly? 
 

Ansel, Sheila, Camilla

Last week, Ansel noticed that there is a 2Hz comb in DARM since the break, similar to that that we've seen from the HWS camera sync frequency and power supplies and fixed in 75876.  The cabling has not been changed since, the camera sync frequency has been changed.

Our current camera sync frequencies are: ITMX = 2Hz, ITMY = 10Hz. We have typically seen these combs in H1:PEM-CS_MAG_LVEA_OUTPUTOPTICS_Y_DQ. With a 0.0005Hz BW on DTT I can't easily see these combs, see attached.