TITLE: 03/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

Covered the morning for TJ while he did TCS work & here are the activities from when I was in the chair.
LOG:

• Technical cleaning:  Karen done @EY 1629, Kim.Emma done @EY.FCES
  • 1724 LVEA cleaning (karen.kim).  1816-Karen OUT.
• Lights catwalk
• 1525-1827 Taking over Ops for TJ (corey)
• 1530 Transitioning LVEA to HAZARD
• 1535 FARO (jason, ryanc)
  • 1540 tyler joining
• 1535-1656 EY accelerometer (fil)
  • 1553 marc joining
• 1541 tcsx beam profiling (tj, camilla)
• 1545-1751 Purge air (loud) on in LVEA for x-beam manifold test (gerardo)
  • 1607 janos joining
  • 1714 Shutting down test. (janos)
• 1600 PEM injection set-up (robert)
• 1613-1750 EX.EY sus charge (rahul)
  • 1744 EX had its ESD offset put at a POSITIVE value (to help peck away at cutting down charge) [jeffk]
• 1615-1806 oplev cabling at ex.ey (fernando)
• 1623 LN2 truck at EY's cp7
  • 1659 LN2 truck at corner's cp1
• 1735-1745 Field trip in Control Room
• 1749-1758 Squeezer rack measurement (nutsinee)
  • 1813 Returning 
  • 1816 HAM7 watchdog trip (ops note: let Jim know!)
• 1750-1813 itmx cps investigations in control room & on floor (jim)
• 1815 PEM set-up & channel checks at EX.EY (robert)

Tue Mar 26 10:09:35 2024 INFO: Fill completed in 9min 31secs

TCs started lower, so I restored the trip temps to -120C (as shown on plot)

WP11786

Jeff, Joe, Jonathan, Dave

A new h1calcs model was installed, this adds two slow channels

++: slow channel H1:CAL-CALIB_REPORT_HASH_INT added to the DAQ
++: slow channel H1:CAL-CALIB_REPORT_ID_INT added to the DAQ
 

A DAQ restart was required.

WP11743 SUS DACKILL removal

Jeff, Oli, TJ, Dave:

This morning we installed new HAM SUS and ISI models:

h1susmc[1,2,3], h1suspr[m,2,3], h1sussr[m,2,3], h1susfc[1,2], h1isiham[2,3,4,5]

All required a DAQ restart.

J. Kissel, T. Shaffer
ECR E1700387
IIET 9392
WP 11743

In prep for today's watchdog upgrades (LHO:76696), TJ and I have 
   - Ensured all HAM triple SUS have their alignment offsets accepted / stored in their safe.snap (they're typically unmonitored, so this takes special action)
   - Brought the IMC guardian to OFFLINE, and brought the guardian to "AUTO" such that it's no longer managed by ISC_LOCK
   - Brought the MC2, PRM, PR2, SR2, SRM gguardians to "AUTO" such that they're no longer managed
   - Brought MC1, MC2, MC3, PRM, PR2, PR3, SRM, SR2, SR3, FC1, and FC2 to SAFE
   - Brought SEI MANAGER guardians for HAM2, HAM3, HAM4, HAM5, HAM7, and HAM8 to ISI_DAMPED_HEPI_OFFLINE

We're ready for restarts!

TITLE: 03/26 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1:Maintenance
CURRENT ENVIRONMENT:
    SEI_ENV state: Maintenance
    Wind: 2mph Gusts, 2mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY: We lost lock at 14:41UTC, cause still to be looked at. Maintenance activities have started.

TITLE: 03/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: None
SHIFT SUMMARY:
Since the last mid shift report there was another lockloss at 6:08 UTC .
Once again relocking went just fine without an Initial_Alignment in 56 minutes with out intervention by the opperator.
There was a PI 31 ring up @ 6:51 UTC but while I was trying to find te right buttons to press it was supressed.

LOG:
Camilla's measurements will start Running again at 2am and continue until 6am.

TITLE: 03/26 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 4mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.19 μm/s
QUICK SUMMARY:

Lock lasted 8 hours and 51 min
Lockloss 3:34 UTC still investigating the cause of this lockloss.
Camilla had some measurements running while we were in Observing see Alog 76695 and was concerned that perhaps her measurements had made the arm powers drop significantly. So I pulled up some ndscopes of H1:GRD-ISC_LOCK_STATE_N and the Circulating Arm powers  H1:ASC-X_PWR_CIRC_OUT16 & H1:ASC-Y_PWR_CIRC_OUT16.
I did see that the arm power did dip before H1:GRD-ISC_LOCK_STATE_N changed to a down state.

But!!! I also did the same for the Lockloss that happened this morning with out her measurement running and saw the same behavior of the Arm power dipping before the Down state was declared by ISC_LOCK. I then decided (arbitrarily) that it was reasonable to think that the time between the ISC_LOCK state change and an observed loss of 10% of the Power in the arms would be a good metric to determine if the lockloss was "Caused" by this measurement.
I have effectively convinced myself that Camilla's A2L measurements have not caused this lockloss.... but I'm open to evidence that I have overlooked.

Relocking:
I have not taken ISC_LOCK through Initial_Alignment before relocking. H1 Is alrerady back to NOMINAL_LOW_NOISE  44 Minutes from NLN to NLN with out intervention from the Operator.  49Min 9 Sec from OBSERVING to OBSERVING.


 

Sheila, Jennie W

At around 21:49 UTC we used the step_45MHz.py in userapps/isc/h1/scripts to step the modulation depth in steps of 1dB down from 21dBm to 18dBm. This script adjusts the loop gains to compensate for a drop in power on the RF45 PDs.

Its also important to open the POP beam diverter to monitor what is happening to the RF 45 PD signals.

This is to check that the noise does not decrease with decreasing modulation depth which would imply that the modulator was imposing noise on the carrier through the ISS loop.

At around 22:18 UTC we put the modulation depth down by 3 dB we saw a 4% increase in the DARM broadband noise (measured the level at 2kHz with cursors) which is the green trace in the second image. The level of KAPPA C (shown in first image on bottom plot) only decreased by around 1% over this time, so we suspect some other cause other than a change in optical gain being responsible for this.

When we stepped the modulation depth up by 3dB (third image) we saw no change in the noise from the nominal state (purple trace on second image). Kappa C (bottom plot) looks almost the same as the nominal also.

In the fourth image it can be seen that f_C does not change much either.

DriptaB, LouisD, TonyS, FranciscoL

We noticed a 0.4% change from the value at the end of O4a for the X/Y ratio. We found alog 76562 where the Pcal EY EPICS values were changed. We have now changed them back to O4a values. See screenshot of SDF screen to find values. We will follow up with an updated value of X/Y to see if anything went wrong.

For future reference: steps to update SDF

1. 'caput' the channels to be changed
2. sitemap --> CAL EX(Y) --> GDS --> SDF TABLE --> ACCEPT (under select all, only afer triple checking numbers) --> CONFIRM.
3. SDF RESTORE SCREEN --> ! SELECT REQUEST FILE --> open "safe.snap" --> LOAD TABLE. Look for differences and confirm changes if needed (was not needed for EY).
4. Load OBSERVE.snap by following step (3).
5. Open FORCE COEFF CALCULATION and check that changes were applied.

Sheila, Naoki

We plan to scan the ZM alignment and need the fast SQZ BLRMS for that. We copied the BP filter for BLRMS 5 at 1.7kHz to BLRMS 6 and replaced the 0.1 Hz LP to 1 Hz LP for BLRMS 6.  So the BLRMS 6 is same as BLRMS 5 now, but has 1 Hz LP instead of 0.1 Hz LP. The SDF is attached.

TITLE: 03/25 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Commissioning
OUTGOING OPERATOR: Ryan S
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 5min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.25 μm/s
QUICK SUMMARY:
H1 has been locked for 4 hours and 22 minutes, We are currently in commissioning while Robert does injections.
The current plan is to stay in comissioning until 6PM then go into Observing.

TITLE: 03/25 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Commissioning
INCOMING OPERATOR: Tony
SHIFT SUMMARY: Locked most of the day; several commissioning activities ongoing with observing periods in between.

• 16:15 - Lockloss; likely human caused
• 17:00 - Starting initial alignment
• 17:27 - IA finished, starting lock acquisition
• 18:03 - Lockloss from TRANSITION_FROM_ETMX
• 18:43 - Reached NLN
• 19:23 - Started observing
• 20:32 - Dropped observing for commissioning tests

LOG:

J. Kissel
ECR E1700387
IIET 9392
WP 11743

Tomorrow, we continue on the adventure towards upgrading the suspension watchdog systems that Oli, Dave and I have been chugging along on for the previous two weeks (see, eg, LHO aLOGs 76305, 76269 and 76545).
This week, we're tackling a big chunk -- all of the HAM triple suspensions, both large and smal, i.e. the 7 HSTS and 2 HLTS. 

Note :: these are the final suspensions that are hooked up to their respective ISIs, so this should be the last major upgrade.

As such I've:
    In the SUS model library parts,
    - Converted the BLRMS trigger generating systems to include a trust-worthy RMS calculation, coupled with a down-stream low-pass filter,
    - Removed all evidence of the USER DACKILL watchdog aggregator system
    - While I was there, I removed remaining evidence of the long-defunct / depricated "online detector characterization" ODC system, long since replaced by guardian state information
    On the top level SUS models,
    - Removed all evidence of the USER DACKILL watchdog aggregator system
    - Removed the IPC sender of the USER DACKILL to the respective ISI
    - Verified that the removal of library block output ports didn't botch any of the top level connections, reconnecting and re-organizing as needed
    On the top level of the ISI models,
    - Replaced the IPC receiver of the USER DACKILL watchdog from all respective SUS

which impacts all of the following models:

    Top Level ISI               Top Level Optic     Governing Library Part
    h1isiham2.mdl               h1susmc1.mdl        HSTS_MASTER.mdl
                                h1susmc3.mdl        HSTS_MASTER.mdl
                                h1suspr3.mdl        HLTS_MASTER.mdl
                                h1susprm.mdl        RC_MASTER.mdl

    h1isiham3.mdl               h1susmc2.mdl        MC_MASTER.mdl
                                h1suspr2.mdl        RC_MASTER.mdl

    h1isiham4.mdl               h1sussr2.mdl        RC_MASTER.mdl

    h1isiham5.mdl               h1sussr3.mdl        HLTS_MASTER.mdl
                                h1sussrm.mdl        RC_MASTER.mdl

    (no change to isiham7)      h1susfc1.mdl        HSTS_MASTER.mdl

    (no change to isiham8)      h1susfc2.mdl        HSTS_MASTER.mdl

In addition, some of the lower level SUS library parts were also impacted,
    SIXOSEM_T_STAGE_MASTER.mdl
    FOUROSEM_STAGE_MASTER.mdl
    FOUROSEM_STAGE_MASTER_OPLEV.mdl

All of the above model changes have been committed to the userapps SVN repo in revs 27310, 27311, 27312, and 27313.
    

We aimed to do A2L steps over the weekend, 15 minutes/step  76630, 76683, but as Elenna points out with the camera servos running the beam spot stayed static on the mirror while the mirror actuation point changed.

Looking at data from A2L tuning in April 2023 68384 attached plot, A2L steps are ~0.4 for a change of around 2 in the camera offset  (TRAMP 120s). We'll keep around the steps same as the weekend: +/- 1.0 per 15 minutes to up to +/-2.0 in the H1:ASC-CAM_{PIT,YAW}{1,2,3}_OFFSET channels during observing with nominal TRAMPs extended from 10s to 120s. These offsets are already unmonitered in sdf as reset each lock, I unmonitered the TRAMPs.

These offfsets vary up to 3 counts lock to lock, see attached plot. Set based on ADS converging.

Script saved in /ligo/gitcommon/labutils/beam_spot_raster/camera_servo_offset_stepper.py  Scheduled to run if we're in NLN via tmux session on cdsws26 at:

• 6pm - 10pm on CAM1 (BS => CAM1 => PRM)
• 10pm to 2am on CAM2 (ETMX => CAM2 => ITMX, ETMX)
• 2am to 6am  on CAM3 (ETMY => CAM3 => ITMY, ETMY)

Tony will be here during the first set so can cancel the others if there is any issues.

We scanned the FC detuning as shown in the first attachment. The nominal FC detuning is -28. The FC detuning below -31 seems better around 30 Hz. The second attachment shows that the BNS range at -34 FC detuning seems a few Mpc better than nominal so we set the FC detuning at -34 as shown in the third attachment.

A sinc function / temperature measurement from the single pass (spare) SHG is shown. The basic idea of the experiment was to see if the crystal is intact (it is). For this purpose, the crystal was pumped with 1064 nm and after one pass (single pass) it was checked how much green light was generated. The temperature was adjusted to find the best possible phase matching temperature.

No similarity to Mount Saint Helens, as described in 76239, was observed. Conclusion, the crystal is intact. (What seems strange is the asymmetry in the side maxima.)

• Pump power 20 mW
• Dark noise 0.9 µW
• Transmitted power 16.8 mW --> just 84 % power is transmitted (probably because the focus was too large, resulting in clipping somewhere inside the housing)
• Fit equation: A*(np.sinc((T-T0)/width))**2 
• Plot is dark noise corrected

Setup:

•  NTC (71-01T1002FF)
•  TEC (Laird)
•  controller (Thorlabs)

J. Kissel, L. Dartez
ECR E2400103
IIET 30760
WP 11786

To better coordinate and confirm the front end portion of the calibration pipeline and the GDS portion running on the DMT machines remain in sync in terms of calibration model installed, which is necessary for good calibration, we are adding two slow 16 Hz EPICS channels to the h1/l1calcs models (so both LLO and LHO) that will be added to the GDS broadcaster list so the GDS calibration pipeline can read them. These are H1/L1:CAL-CALIB_REPORT_ID_INT and H1/L1:CAL-CALIB_REPORT_HASH_INT.

Louis and I created the top-level EPICs records today; see attached screenshot.

The change has been committed to the userapps SVN under:
    /opt/rtcds/userapps/release/cal/h1/models/
        h1calcs.mdl          committed at rev 27307.


It's in no way a complicated add to the model, but I've ran a test compile of the h1calcs.mdl on the build machine anyways just to check. The test compiled succeeded without issue.