TITLE: 06/27 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: We've been locked for just under 5 hours, calm day.
LOG:

• The LOCKLOSS_SHUTTER_CHECK failed at 09:05 UTC, I've added a check in H1_MANAGER to specifically look for the SHUTTER_FAIL state.
• 17:02 UTC lockloss
  • 18:25 UTC I adjusted the OPO temperature while relocking
  • The FC struggled to lock IR and we ended up changing the threshold
  • 19:33 UTC Observing
    • 19:43 UTC We dropped observing for <1min as the SQZ ASC turned on and threw out an SDF diff which I unmonitored

TITLE: 06/27 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 147Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 14mph Gusts, 9mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

IFO is in NLN (since 18:36 UTC) and OBSERVING since 19:33 UTC (4.5 hr lock)

An hour was spent comissioning to fix SQZ ASC, which now runs deeper into thermalization after NLN.

Otherwise, just planning to continue observing as long as possible!

Closes FAMIS 26399. Last checked in alog 85208.

All fans nominal, comparable to last week and within threshold.

Closes FAMIS 26456. Last checked in alog 84705

Trends look normal. SEI BRS Maintenance work in Mid-May was part of vent work and is the only excursion from the threshold lines.

J. Kissel, F. Clara
ECR E2400330

Fil modified another UK SatAmp (D0900900 / D0901284) per ECR E2400330, which means "rev'ing" up the D0901284 circuit board inside from -v4 to -v5.

However, this one, S1000278, seems to have more variability in components that were not changed between channels -- namely if I 
    - fit the measured zero and pole frequency, and 
    - assume that a perfect, as drawn, value for the R181 = R182 resistors (as Fil confirms that these were +/-0.1% resistors)
the total capacitance seems to have a ~2% variability. 

Not unreasonable, given that typical off-the-shelf caps of value 10 [uF] have +/-10% variability, so with two of these caps parallel, you could expect the total capacitance to be between 18 and 22 [uF], or +/-10%.

As such, I propose we set a tolerance for these transfer functions to have the following values at the following "check" frequencies (i.e. logspace(log10(5),log10(50),3), which is a requestable frequency vector on an SR785 frequency response sweep, if fstart = 50, and fstop = 0.5, with N points = 3). These assume values assume 1% variation in transimpedance amp feedback resistor, and 2.5% variation in whitening cap.

    Freq    Mag (Upper Bound)    Mag (Lower Bound)    Phase (Upper Bound)   Phase (Lower Bound)  
    [Hz]    [V/V] or dB([V/V])  [V/V] or dB([V/V])          [deg]               [deg]

    0.5      5.4098 or 14.664       5.0554 or 14.075      -106.23             -106.5

    5.0     38.415  or 31.69       36.671  or 31.286      -135.09             -133.72

    50.     54.987  or 34.805      53.868  or 34.627      -174.2              -173.9

    Freq    Mag Tolerance              db(Mag Tolerance)          Phase Tolerance 
    [Hz]    [V/V] +/- [V/V]         dB([V/V]) +/- dB([V/V])     [deg]  +/-   [deg]

    0.5      5.2313 +/- 0.17847       14.372 +/- 0.29138      -106.36  +/-  0.12754

    5.0     37.547  +/- 0.86844       31.491 +/- 0.19861      -134.41  +/-  0.67952

    50.     54.428  +/- 0.55902       34.716 +/- 0.088757     -174.05  +/-  0.14395

That being said, we wouldn't replace the non-ECR components if the SatAmp didn't pass this test, we'll just use those under-performing SatAmps to be used on low priority stages, i.e. ones not used for damping loop control, i.e. not top mass stages. If many end up exceeding this thresholds, then we can start to prioritize which suspensions get the best.

Fri Jun 27 10:12:24 2025 INFO: Fill completed in 12min 21secs

The filter cavity was having a hard time locking, and it looks like the FC green trans power has been dropping slowly over the last 3 weeks, which seems to be caused by a drop in the SHG power from around 100-110 mW down to 77 mW . 

I adjusted the picos and the SHG temperature, and recovered the SHG power to 86 mW, so there is still a lot of missing power.  The filter cavity locked after this.

I've added a template for this adjustment to userapps/sqz/h1/Templates/ndscope/SHG_alignment_temp_adjust.yaml

Lockloss at 17:02 UTC in NLN while we were waiting for the FC to lock.

TITLE: 06/27 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 4mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.05 μm/s
QUICK SUMMARY:

• We were stuck in PREP_FOR_LOCKING with ISC_LOCK stalled with IFO_NOTIFY and H1_MANAGER asking for help (10:22 UTC)
• As soon as I requested H1_MANAGER back to idle it released ISC_LOCK and we started to lock again
  • At first glance I'm not sure why it was stuck
  • The timer "to NLN with an initial alignment already having run" was why it was calling for help but it should have kept trying to lock itself?

TITLE: 06/27 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 150Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 04:13 UTC

Quite the frustrating shift in which I encountered:

• Issue ALSX Crystal Freq -- - has been happening for at least a week now. Fix: Toggle the ALSX PLL on/off but this barely works if at all. Eventually, it cleared on its own after about 45 minutes of low hope.
• Issue: 2 Lockloss-causing 3.0 EQs in south Oregon. Fix: Increase luck.
• Issue: SQZ_ASC issues and inability to lock SQZ LO. Fix: With Camilla, saw that SQZ ASC was driving ZM4/6 cts to the 900s so reset history and edited SQZ params to disable SQZ FC until tomorrow. After resetting the history, SQZFC worked just fine. This issue caused us to drop from OBSERVING from 04:13 to 04:53 UTC. (accepted SDF below)
• Issue: DRMI Locking: Truly no clue if it is an amalgamation of bad aligment, winds from 20-30mph and high microseiem (primary) or just bad luck. The flashes for both PRMI and DRMI both times were more than sufficient to lock DRMI yet we waited in these states for more than a cumulative hour just waiting for lock. I had to run 2 initial alignments after I could not lock on the first auto one for over 2 hrs. I ran a second manual initial alignment and this seemed to work. Then, we lost lock due to an ADS_EXCURSION (according to Lockloss Tool) and the DRMI issues were back. After repeating MICH, PRMI and DRMI multiple times, finally PRMI caught and I was able to lock (and eat). Lock trouble details about this in alog 85377. Fix: Manual Initial Alignment (apparently)

LOG:

None

WP12637 Install HWS Camera Controls

TJ, Camilla, Dave:

I made a slight change to my original Dec 2023 hws_camera_control.py code to use the python epics module to do the cagets directly, and to also use this to add caputs which will try, in a non-blocking way, to send the camera's status to a central EPICS IOC.

The central IOC code is hws_camera_status_ioc.py which runs on cdsioc1 under puppet control.

The camera control code runs every minute in an infinite loop. Each loop it checks the status of H1 using Guardian ISC_LOCK (greater or equal to 600 denotes H1 LOCK). If H1 is locked and the camera is on, it turns the camera off. If H1 is not locked and the camera is off, it turns the camera on.

A mini-overview of the 4 HWS cameras (ITMX, ITMY, ETMX, ETMY) is available on the CDS Overview screen. The block is divided into 4 segments, each camera is shown either in SKYBLUE (camera is enabled, images are being taken) or GREEN (camera is disabled, no noise being created).

Note that the color scheme relates to what is nominal for OBSERVE. Green indicates the cameras have power, but their frame acquisition has been disabled.

Clicking on the HWS block on the CDS Overview opens a detailed screen (see attachment). For each camera this shows if the camera is powered (ETMY is the only one powered down) and if the camera is enabled. The control code also reports its current time, its uptime, its start time and details of where and how it is running.

Second attachment shows the four tmux sessions running the control code, and the arguments used.

Signal railed about 5:18 PM local time, I checked trend data for PT120 and PT180 and no pressure rise noted inside the main volume.  Attached is 3 day trend of the pump behavior, very glitchy for a long while already.

System will be evaluated as soon as possible.  AIP last replaced on 2015, see aLOG 18261.

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.