WP12091 Add new TEST_NOTIFY Guardian Node

TJ, Dave:

TJ created the new node and the new H1EDCU_GRD.ini. I updated H1EPICS_GRD.ini. DAQ+EDC restart needed.

WP12087 Add VACSTAT gauge channels to DAQ.

Dave:

I added the gauge metadata channels to H1EPICS_VACSTAT.ini. DAQ+EDC restart needed.

This failed due to channel name lengths exceeding 54 characters. This change was then backed out.

Verify PEM signal cabling to h1iopcdsh8 IO Chassis

Fil, Dave:

Fil verified the PEM cabling was as per h1pemh8. See Fil's alog for details.

New LIGO 28AO32 DAC driving ETMX L2 and ESD signals

Daniel, Richard, Marc, Fil, TJ, Tony, Dave, Erik, Jonathan, EJ

The 28AO32 DAC was wired to drive the SUS ETMX DAC channels which were being driven by its 20bit DACs. Existing AI chassis were used for these drives to remove one more change.

Two additional AI chassis were installed in this rack. One to keep the first 20bit DAC in a good state, the second to drive the h1susetmxpi DAC drives (last two channels of second 20bit DAC).

DAQ Restart

Jonathan, Dave:

The DAQ + EDC were restarted for the Guardian and VACSTAT changes. This was a very messy restart.

DC0 did not restart, it found that the new VACSTAT channel names were too long.

I reverted the change to H1EPICS_VACSTAT and we did a second restart of the DAQ 0-leg and EDC.

FW0 spontaneously restarted itself after only writing a few full frames.

When we were sure FW0 was stable again, we restarted the 1-leg with no issues.

The name-too-long issues should have been caught by my check_daq_channels_validity.py code. I subsequently found there was a bug in the code, and it was not checking the new DAQ INI files, rather the running version. This has been fixed and tested.

WP 12089

All FCES PEM cabling is now labeled. PEM sensors are connected to PEM chassis as follows:

1. CH1 - HAM8 Microphone
2. CH2 - HAM8 Accelerometer X
3. CH3 - HAM8 Accelerometer Y
4. CH4 - HAM8 Accelerometer Z
5. CH5 - FCES Accelerometer Beam Tube
6. CH6 - HAM8 Accelerometer Floor
7. CH7 - HAM8 Mag X
8. CH8 - HAM8 Mag Y
9. CH9 - HAM8 Mag Z

Worth noting that the PEM AA Chassis shares ADC channels with the ISC AA Chassis. A special rear interface board is installed in the PEM AA Chassis.

D. Barker, F. Clara

I've hand edited the LIGO DAC MEDMs for h1susetmx and h1iopsusex models so the large drive signals are no longer being clipped at both ends.

I restarted the seismic blrms monitors and they now appear to be publishing 48 hours of data.

Tue Sep 17 08:11:31 2024 INFO: Fill completed in 11min 27secs

Gerardo confirmed a good fill curbside.

WP 12080  After turning the HWS lasers back on in 80043, today I reinstalled the masks. To get the right amount of light on the CCD camera, ITMX is set to 1Hz and ITMY to 20Hz. New references taken at 15:50UTC, 30 minutes after we lost lock, so the IFO wouldn't have been 100% cold. 

TITLE: 09/17 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.08 μm/s
QUICK SUMMARY:

H1 is locked for over 5 hours  but not observing. Looks like we were taken out of Observing at 7am.
Most Likely because it's running the Magnetic injections.
Inlock charge measurements are next.

 

Workstations were updated.  This was an OS packages update.  Conda packages were not updated.

TITLE: 09/17 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently Observing at 160Mpc and have been Locked for almost 3 hours. One lockloss during my shift due to an earthquake, but relocking was completely hands-off besides me choosing to run an initial alignment.
LOG:

23:30UTC Observing and have been Locked for 3 hours
01:02 Lockloss from earthquake
     01:08 Started initial alignment
     01:29 Initial alignment done, relocking
02:09 NOMINAL_LOW_NOISE
02:12 Observing

Lockloss @ 09/17 01:02 UTC after 4.5 hours locked from Texan earthquake

TITLE: 09/16 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 148Mpc
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 12mph Gusts, 9mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.10 μm/s
QUICK SUMMARY:

Currently observing at 150Mpc and have been Locked for 3 hours.

TITLE: 09/16 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: After several EQs overnight ringing up violins, we took time to damp them before commissioning this morning. One lockloss after getting back to observing, followed by a straightforward relock.

• 14:30 - H1 up to OMC_WHITENING damping violins
• 15:54 - Reached NLN, starting commissioning
• 18:34 - Started observing, commissioning finished
• 19:16 - Lockloss - alog80119
• 20:39 - Observing

H1 has now been locked and observing for almost 3 hours.

LOG:

J. Kissel

The HAM-A driver chassis (D1100687) seems to now be the go-to, favored, coil driver for any and all new SUS stages that come along (see G1100968 for tabulated summary). However, each of these new SUS stages have different actuation requirements, so the actuator systems are often tailored to have the drivers with different output impedance, driving AOSEMs or BOSEMs, and then a bespoke magnet size.

As such, here, in prep for an update to the Controls Design Summary Table (again, G1100968), I demonstrate the output of a new, quick, comparison script 
    /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/
         compare_OSEM_actuator_strength.m (rev 11998)
that compares the output of our trusty "have to get it right, or else the IFO doesn't work" function that returns properties of SUS stages,
    /ligo/svncommon/SusSVN/sus/trunk/Common/MatlabTools/
make_OSEM_filter_model.m (rev 11997)
which I've just today updated to make sure that the HATS and OFIS information was correct when used.

Here's the output, sorted by total actuation strength per actuator (individual channel coil driver transconductance * single magnet+coil force coefficient):
    {'susType'}    {'isoStage'}    {'Osem Type'}    {'Magnet Size'}    {'Force Co [N/A]'}    {'Driver Type'   }    {'Driver TC [mA/V]'}    {'Total Strength [N/V]'}
    {'HATS'   }    {'M1'      }    {'B'        }    {'4.0Dx4.0T'    }    {[       0.39254]}    {'-v1 (100 Ohm)' }    {[          9.1059]}    {[           0.0035744]}
    {'BHSS'   }    {'M1'      }    {'A'        }    {'2.0Dx6.0T'    }    {[        0.0309]}    {'-v1 (100 Ohm)' }    {[          10.055]}    {[          0.00031069]}
    {'OFIS'   }    {'M1'      }    {'A'        }    {'3.0Dx6.0T'    }    {[        0.0695]}    {'-v2 (1.2 kOhm)'}    {[          0.9133]}    {[          6.3474e-05]}
    {'OPOS'   }    {'M1'      }    {'A'        }    {'2.0Dx6.0T'    }    {[        0.0309]}    {'-v2 (1.2 kOhm)'}    {[          0.9133]}    {[          2.8221e-05]}
    {'HTTS'   }    {'M1'      }    {'B'        }    {'2.0Dx3.0T'    }    {[         0.021]}    {'-v2 (1.2 kOhm)'}    {[         0.90474]}    {[          1.8999e-05]}
    {'HAUX'   }    {'M1'      }    {'A'        }    {'1.9Dx3.2T'    }    {[        0.0158]}    {'-v2 (1.2 kOhm)'}    {[          0.9133]}    {[           1.443e-05]}
    {'HATS'   }    {'M3'      }    {'A'        }    {'2.0Dx0.5T'    }    {[       0.00281]}    {'-v2 (1.2 kOhm)'}    {[          0.9133]}    {[          2.5664e-06]}

Notes: 
    - this is *per actuator*. One must go a step further and count number of actuators and lever arms if you want to convert to actuation strength in the Euler basis.
    - the magnet size is n.nDxn.nT for Diameter and Thickness (where thickness is aka length).

Just interesting to see "on paper," all in one place; not even the controls design summary table summarizes the information in this way.

Closes FAMIS#26470, last checked 79524
 
HEPI pump trends looking as expected (attachment)

Lockloss @ 19:16 UTC - link to lockloss tool

No obvious cause; I don't notice any DARM "wiggles" or "glitches" in this lockloss either.

I did two different tests to PRCL today that would hopefully help improve the low frequency noise.

PRCL feedforward test:

I tried fitting a new feedforward with Gabriele last week. We saved this in FM6. However, the comparison of the injection without feedforward and with feedforward showed that the coupling was worse with feedforward.

PRCL offset test with new HAM1 FF:

I engaged the previously tested PRCL offset (alog 79989), and tried the new HAM1 feedforward I fit. Not only does this HAM1 feedforward perform better than the previous tuning, generally the HAM1 coupling is smaller than without the PRCL offset.

Comparison plot. Compare the gold traces with the blue traces. These are both HAM1 feedforward OFF times, except gold is with no PRCL digital offset, and blue is with PRCl digital offset at -58. There is improvement in the noise in CHARD P, CHARD Y, and INP1 P (left three plots). PRC2 P noise looks the same (right side, second down). Then, red shows the new HAM1 feedforward with the PRCL digital offset. The reduction is noise is the same or better than the noise reduction achieved in the previous HAM1 feedforward tuning (see alog 79799). Again, I find it suspicious that the signifcant change seems to come from the loops that use the RF45 demod signal (CHARD and INP1), while the loop using RF9 only do not change (PRC2).

I consider this test a success, and the lower noise in CHARD Y with the PRCL offset on (left, second plot down) is evident.

The PRCL offset is back in the guardian in LOWNOISE_LENGTH_CONTROL and SDFed for observe. I SDFed the new HAM1 feedforward settings in both safe and observe.