Thu Oct 24 10:08:46 2024 INFO: Fill completed in 8min 42secs

Gerardo confirmed a good fill curbside.

Last week (alog80749) the LOCKLOSS_SHUTTER_CHECK guardian node was stuck after not receiving the data it asked nds for. We've seen this happen in the past and I've written some wrapper functions to help with this - (userapps)/sys/h1/guardian/timeout_utils.py. While looking through the code with Sheila and Dave separately, it definitely seems like this node has been edited a bit and has been left in an odd state in need of cleanup. So I:

• Removed the unnecessary counters and other unnecessary code in the CHECK_SHUTTER state
• Added the timeout function calls to the nds data request and some logic around it
• Changed the edges a bit for slightly better state flow
• Added a few more comments, doc strings, and notifications for clarity

We also noticed that ISC_LOCK doesn't actually look directly at this node before powering up anymore. I looks like it was commented out in Dec 2018 for some SRY testing, then never put back in. The node was still watched by the top level IFO node, so it would still have stopped us from Observing, as it was the case last week. I moved that bit of code to the AS_SHUTTERS state where we already check the FAST_SHUTTER node (this node runs a test on the shutter before power up vs LOCKLOSS_SHUTTER_CHECK will check if it fired during the last high power lock loss). This way we won't power up if there was no GS13 kick on the last high power lock loss.

I tested the LOCKLOSS_SHUTTER_CHECK node by running it through the checks normally, and with the value of the GS13 kick incredibly low so it would flag a failure. This node is loaded and ready, and I reloaded ISC_LOCK with the new conditional in the AS_SHUTTERS state, though I have no yet ran this state since we have no IFO right now.

Sheila, Daniel, Vicky

On Tuesday, Sheila and I took some beam profiles of the squeezer pump beam after the pump AOM used for ISS (GAOM1). This is trying to understand and fix the squeezer pump ISS issues that result from GAOM1 becoming misaligned on SQZT0.

Summary and proposed plan: the vertical beam profile we measured looks reasonable, the horizontal profile looks off (potentially related to measuring after the AOM). We could move GAOM1 closer to SHG by 1-2 holes to get closer to the beam waist of ~100um that is about 1.3m after SHG. While GAOM1 is out, we could re-measure the horizontal beam profile to make sure it is OK.

Here are plots of the pitch beam profiles we took before, and the very quick a la mode plot code that adapts Sheila's and Georgia's previous codes. I think the vertical beam profiles we took line up with Georgia's previous measurements and D1201210, which both say there should be a waist like 1.25m - 1.3m after SHG. In real life, we measured from z=0 at the EOM mount edge closest to GAOM1, to the face of the beam profiler (may need to take into account beam profile distance..).

So it seems possible that GAOM1 is like 0.02-0.05 meters (~2 inches?) downstream of the waist. From photos and SQZT0 layout D1201210, there is room to try moving GAOM1 closer to L15 (closer to SHG) by 1-2 holes.

• At LLO (example photo), GAOM1 misalignments are not a pump ISS problem - and their GAOM1 is also several holes closer to L15 than LHO's  (which is what these profiles suggest to try).
• Kinda ignoring the horizontal beam profiles here since we measured after GAOM1, and the beam's yaw profile was not fitting well while measuring. The pump beam after GAOM1 looked kinda double-lobed with some smaller outer fringes even with the AOM drive at 0V, where it should be "passing everything" and not diffracting, but maybe there was some RF leakage.. The profiler's fitting function was fitting both lobes at once and being thrown off by the fringers, so likely over-estimating the waist in yaw (blue). Worth checking the beam profile without the AOM in place.

Useful DCC references:

• SQZT0 layout D1201210 and mode-matching document here: see pg.4, should be a waist of w0~100um at z~1.3m from SHG.
• SQZT0 Green AOMs for PUMP + FCGS paths: E2000561. GAOM1 for pump ISS is M1250-P200L-0.75, a 200 MHz AOM with aperture of 0.75 mm. Updated +200MHz label on SQZT0 medm screen. GAOM1 has a visibly smaller hole than the other AOMs.

TITLE: 10/24 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
CURRENT ENVIRONMENT:
    SEI_ENV state: LIGHT_MAINTENANCE
    Wind: 6mph Gusts, 4mph 3min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY: More NPRO work planned for the day, more ground moving. No alarms to report.

R. Short, J. Oberling, F. Clara

Continuing from yesterday, this morning Ryan and I looked at mode matching solutions and found one we liked, see attached.  It seems pretty robust, in that we can have the lenses several mm off and still get >99.9% mode overlap (not easily seen in the picture as the other lens positions are off screen).  Once the LVEA was transitioned to Laser Safe we went out to do the readback adjustments on the new NPRO.  All of the adjustments were going well until we got to the Laser On/Off Monitor adjustment.  For information on this particular adjustment see the file 'Some further information needed... .docx' in T1900456.  No matter how we adjusted the potentiometer we could not get the PSL Beckhoff software to recognize that the laser was on.  We installed a 25-pin breakout board and looked at the voltage, all we saw was 0.032 V.  No matter how the pot was adjusted this value never moved, but very occasionally jump up to a higher voltage (1.5 V to 2.5 V range).  This looked like a connection problem, so we took the power supply to the EE shop and enlisted Fil's help in figuring this out.  We referenced what little wiring diagram info we had to carefully trace the signal path, check the proper resistor was installed in R33 (4.7k, it was correct), and made sure all the wiring had been done properly (it was).  Fill cleaned some excess flux from around where the remote board picks off the signal it needs to detect if the laser is on or off (for future reference, this is the top side of power supply resistor R1 for the ON signal and the left side (when looking at the vertically mounted circuit board from the inside) of component T11 for the OFF signal).  He also didn't like the way the solder around remote board resistor R33 looked so he reflowed it.  At this point he wanted to power it up, so we plugged it in.  Unfortunately the power supply interlocks itself if no laser is attached (as expected), so we took the power supply back out to the PSL racks and hooked it up to the laser (but not the Beckhoff system).  A breakout board was hooked to Diagnostics port 2 and we turned on the power supply.  With the laser off the pin read 0V (as it should), and with the laser on the pin read ~7V (yay!).  So apparently either cleaning the flux or reflowing the solder fixed the connection problem.  We then wired the power supply to the PSL Beckhoff system and tuned the correct potentiometer so the voltage was at the ~10V it should be.  The software correctly detects when the laser is on, when it is off, and is capable of turning the laser on and off, and all of the diagnostic readbacks are reading the correct values.  At this point it was after 1pm, so we broke for some lunch.

After lunch we went in to the enclosure to begin recovering Amp1.  With all of the lenses between the NPRO and Amp1 removed, and the NPRO power turned down to ~85mW (using WP14), we roughly aligned the beam through Amp1.  We had ~53mW incident on Amp1 and were able to get 2.38 mW in transmission.  While this doesn't seem like much, there are no lenses installed so the beam is overfilling the amp's entrance aperture and every optical element inside the amp, so this is expected.  When I had removed lens L02 it was a little stuck in its mount, and when it came out I inadvertently put my thumb right on the surface.  So time was spent getting the lens cleaned before storage.  This done, we then grabbed the lenses needed for our mode matching solution.  Back in 2021 we had stored them with First Contact on them, so we removed it.  It left behind a large amount of residue on every surface, so the lenses require cleaning again.  As we do not have First Contact in the PSL enclosure, we contacted Camilla about the location of more.  Since neither Ryan nor I have worked with First Contact much, Camilla offered to clean the lenses in the morning; since it was already 4pm we took her up on that offer (Thank You!!!).  We then began building the component stack needed to mount the third lens of the mode matching solution.  Turns out when we installed this PSL confiuration back in 2021 we used all of the spacer blocks designed to put the lens at our 4" beam height, so all we had left were the old spacer blocks designed for a 100mm beam height.  What we do have, however, is small 1.6mm spacers that could be used to get the height correct, but they needed modified so they work with our larger spacer block.  I contacted Tyler about doing this quick mod in the morning, and he agreed (Thank You!!!).

So on deck for tomorrow:

• Lens cleaning (Camilla)
• 1.6mm spacer mods (Tyler)
• Install mode matching solution, align lenses, take beam propagation measurements and do Gaussian fit to ensure mode matching is doing what we expect, modify if it isn't
• Begin aligning through Amp1 and powering it up

Late entry.
On Tuesday (10-22-2024) quarterly functionality test was performed at the MX and EX Turbo stations.
WP 12137

Procedure checklist for both stations completed.  No issues were identified at this time.

EX: Scroll pump hours: 7151

       Turbo pump hours: 1103

       Crash bearings: 100%

MX: Scroll pump hours: 223

       Turbo pump hours: 134

       Crash bearings: 100%

TITLE: 10/23 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
SHIFT SUMMARY: PSL NPRO swap continues. There also was other maintenance activities and ground moving near the staging building.
LOG:                                                                                                                                                                                                                                                                     

Busy day for VACSTAT today, at 15:11 it detected a glitch on HAM6 PT110. This is also a 2 second square wave, but in this case glitching in the opposite direction, pressure dropping to 80%.

J. Freed, M. Pirello, J. Kissel

SPI Double Mixer D2400315 prototype is now built and ready to be tested T2400327, in the SPI DAQ test stand D2400283

Closes FAMIS#26471, last checked 80120

Things look steady and similar to the last check.

J. Kissel echoing E. Dohmen

Just a bit of useful info from E.J. that I think others might be interested in (and giving myself bread crumbs to find the info in the future):

- The PRODUCTION (H1 included) systems are only at 5.1.4 with no plans on upgrading soon. 

- h1susetmx computer, however is at a prototype version of 5.3.0 in order to support LGIO DAC testing (see LHO:79735)

- One can find the running release notes for modern versions (since RCG 2.0) of the RCG at
https://git.ligo.org/cds/software/advligorts/-/blob/master/NEWS?ref_type=heads

VACSTAT alarm on BSC3. This is another false alarm due to a sensor glitch.

I have restarted vacstat_ioc.service on cdsioc0 to reset.

I cold booted h1hwsmsr1 after it partially froze so that it could not be logged in to.  The hard drive LED was solid on.

WP 12159

High voltage disabled. Control Chassis powered off. Cable to chamber disconnected at rack/chassis.

Continuity test of pins:

1. Pins A & C tied together
2. Pins B & D tied together
3. Pins E & F tied together

All pins and shell open to chamber ground.

J. Kissel
WP 12140

I've completed 6 SUS + 4 ISI = 10 of 12 total DOF excitations that I wanted to drive before I ran out of time this morning. Each drive was "successful" in that I was able to get plenty of coherence between the 4 DOFs of ISI drive and SUS response, and some coherence between 6 SUS drive DOFs and ISI response. As expected, the bulk of the time was spent tuning the ISI excitations. I might have time to "finish" the data set and get the last two missing DOFs, but I was at least able to get both directions of LPY to LPY transfer functions, which are definitely juicy enough to get the analysis team started.

Measurement environmental/configuration differences of the HAM2 ISI from how they are nominally in observing:
    - PR3 M1 DAMP local damping loop gains are at -0.2, where they are nominally at -1.0. (The point of the test.)
    - CPS DIFF is OFF. (needed to do so for maintenance day)
    - Coil Driver z:p = 1:10 Hz analog low-pass (and digital compensation for it) is OFF. (need to do so to get good SNR on SUS M1 drive without saturating the SUS DACs)

Interesting things to call out that are the same as observing:
    - The PR3 alignment sliders were ON. P = -122 [urad]; Y = 100 [urad]. (Don't *expect* dynamics to change with ON vs. OFF, but we have seen diagonal response change if close an EQ stop. Haven't ever looked, but I wouldn't be surprised of off-diagonal responses change. Also DAC range gets consumed by DC alignment request, which is important for driving transfer functions.)
    - Corner station sensor correction, informed by the Bier Garten "ITMY" T240 on the ground. (the h1oaf0 computer got booted this morning, so we had to re-request the SEI_CS configuration guardian to be in WINDY. The SEI_ENV guardian had been set to LIGHT_MAINTENANCE.)
    - PR3 is NOT under any type of ISC global control; neither L, P, or Y. (global ISC feedback for the PRC's LPY DOFs goes to PRM and PR2.)

There are too many interesting transfer functions to attach, or even to export in the limited amount of time I have. 
So -- I leave it to the LSC team that inspired this test to look at the data, and use as needed.

The data have been committed to the SVN here:
    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/SAGM1/Data/
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_L_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_T_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_V_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_R_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_P_0p02to50Hz.xml
        2024-10-15_1627_H1SUSPR3_M1_WhiteNoise_Y_0p02to50Hz.xml

    /ligo/svncommon/SusSVN/sus/trunk/HLTS/H1/PR3/Common/Data
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_L_0p02to50Hz.xml
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_T_0p02to50Hz.xml
            [ran out of time for V]
            [ran out of time for R]
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_P_0p02to50Hz.xml
        2024-10-15_1627_H1ISIHAM2_ST1_WhiteNoise_PR3SusPoint_Y_0p02to50Hz.xml


For the SUS drives templates, I gathered:
     Typical:
     - The top mass, M1, OSEM sensors, in the LTVRPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M1_DAMP_?_IN1_DQ             [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The top mass, M1, OSEM sensors, in the T1T2T3LFRTSDD OSEM Sensor/Coil Basis, calibrated into microns, [um].
         H1:SUS-PR3_M1_OSEMINF_??_OUT_DQ         [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The top mass, M1, OSEM coils' requested drive, in the T1T2T3LFRTSD OSEM Sensor/Coil Basis, in raw (18 bit) DAC counts, [ct_M1SUS18bitDAC].
         H1:SUS-PR3_M1_MASTER_OUT_??_DQ          [Filtered with the 32x filter, then downsampled to to fs = 512 Hz]

     For this set of templates:
     - The bottom mass i.e. optic, M3, OSEM sensors, in the LPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M3_WIT_?_DQ                  [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The bottom mass i.e. optic, M3, optical lever, in PIT YAW Euler Basis, calibrated into mircoradians, [urad].
         H1:SUS-PR3_M3_OPLEV_???_OUT_DQ          [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The ISI's Stage 1 GS13 inertial sensors, projected to the PR3 suspension point LTVRPY Euler basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_SUSPOINT_PR3_EUL_?_DQ       [Filtered with the 4x filter, then downsampled to to fs = 1024 Hz]
     - The ISI's Stage 1 super sensors, in the ISI's Cartesian XYZRXRYRZ basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_ISO_*_IN1_DQ                [Filtered with the 2x filter, then downsampled to to fs = 2048 Hz]

Note: The six M1 OSEM sensors in the Euler Basis are set to be the "A" channels, such that you can reconstruct the transfer function between the M1 Euler Basis to all the other response channels in the physical units stated above. As usual the excitation channel for the given drive DOF (in each template, that's H1:SUS-MC3_M1_TEST_?_EXC) is automatically stored, but these channels are in goofy "Euler Basis (18-bit) DAC counts," so tough to turn into physical units.

For the brand new ISI drive templates, I gathered:
     - The ISI's Stage 1 super sensors, in the ISI's Cartesian XYZRXRYRZ basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_ISO_*_IN1_DQ                [Filtered with the 2x filter, then downsampled to to fs = 2048 Hz]
     - The ISI's Stage 1 GS13 inertial sensors, projected to the PR3 suspension point LTVRPY Euler basis, calibrated into nanometers or nanoradians, [nm] or [nrad]
         H1:ISI-HAM2_SUSPOINT_PR3_EUL_?_DQ       [Filtered with the 4x filter, then downsampled to to fs = 1024 Hz]

     - The top mass, M1, OSEM sensors, in the LTVRPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M1_DAMP_?_IN1_DQ             [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The bottom mass i.e. optic, M3, OSEM sensors, in the LPY Euler Basis, calibrated into microns or microradians, [um] or [urad].
         H1:SUS-PR3_M3_WIT_?_DQ                  [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The bottom mass i.e. optic, M3, optical lever, in PIT YAW Euler Basis, calibrated into mircoradians, [urad].
         H1:SUS-PR3_M3_OPLEV_???_OUT_DQ          [Filtered with the 64x filter, then downsampled to to fs = 256 Hz]
     - The ISI's Stage 1 actuators' requested drive, in the H1H2H3V1V2V3 ISI actuator basis, in raw (16-bit) DAC counts, [ct_ISIST116bitDAC].
         H1:ISI-HAM2_OUTF_??_OUT                 [Didn't realize in time that there are DQ channels H1:ISI-HAM2_MASTER_??_DRIVE_DQ stored at fs = 2048 Hz, or I would have used those.]

Note: Here, I set the number of "A" channels to twelve, such that both the ISI's Cartesian basis and the PR3 Suspoint basis versions of the GS13s can be used as the transfer function reference channel.