TITLE: 02/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 6mph Gusts, 3mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY:

• We've been locked for over 20 hours
• PCAL, PSL, VAC work, DAQ and front end restarts are some of the items on the maintenance docket for today
• The magnetic injections are running

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

TITLE: 02/04 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
INCOMING OPERATOR: Oli
SHIFT SUMMARY: Very quiet shift with just one brief drop from observing early on. H1 has now been locked for 11 hours.

• 00:33 - Dropped observing from SQZ dropping out; everything came back automatically
• 00:35 - Observing
• 05:53 - S250204ax

FAMIS 31071

Jason's work in the enclosure on the FSS and increase of chiller flow is clearly seen on many trends (alog82503). PMC Refl continues to rise.

TITLE: 02/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY:

IFO is in NLN and OBSERVING as of 19:06 UTC
Calm day overall with a lot of improvements to locking issues in the weekend from the 8:30 to 11:30 AM comissioning time.

Namely:

SQZ weekend issue fixes: alog 82604

Weekend Low Range Checks (coherence and A2L) changes: alog 82605

SDF Scripts accepted after comissioning: alog 82614 (and attached).

LOG:

Sheila, Jennie W

Sheila realised the QPD offset changes I mad eon January 21st had made the kappa C worse and that this was probably because they were the wrong sign. So I reverted them to the pre-Jan 21st offsets and accepted the values in OBSERVE.snap. We might remeasure these values and update them during the next commissioning period.

The other sdf images were me reverting tramp values after Ibrahim and Sheila measured the test mass A2L values during commissioning.

Jennie W, Mayank, Sheila, Matt

Mayank, Sheila, Matt and I updated the calibration of the OPTIC_ALIGN offsets in the PR2_SPOT_MOVE state that move the IM4, PRM and PR2 mirrors as the commissioner hand tunes the PR3 position. These are set in userapps/isc/h1/guardian/ISC_library.py.

The values were found by Camilla and Matt looking at past spot moves after Elenna realised we hadn't been keeping up with PR2 moves the last tiem we did this in LHO alog#82568.

The new value for pitPR3toIM4 is 11.

The new value for yawPR3toIM4 is 0.755.

The new value for yawPR3toPRM is 1.89.

After updating these in the guardian we went to PR2_SPOT_MOVE state and Mayank stepped a few steps up and down in yaw, then in pitch of PR3 just to check the alignment loops were acting to cancel out this change in the locking loops for PR2, PRM and IM4. We found that PR2 and IM4 M1_LOCK_Y_OUTPUT stayed constant. PRM was moving quite a lot as we thermalised so it was hard to tell. We also checked that the test masses and SR2 and SRM loops were not affected by this yaw change - see image.

During the pitch change we did see some changes in IM4, PRM and PR2 so we may have to update the calibration factor for these sliders in the PR2_SPOT_MOVE state. PR2 P LOCK OUTPUT also changed when we were making Y changes to PR3 due to cross-coupling. The test mass locking loops lag the PR3 pitch movements also so this is something to watch out for.

Olli committed these changes to ISC_library.py for me.

[ Jennie, Siva, Mayank]
Laser: Axcel ,Model Designation: BF-A64-0130-PP

We removed the Lens(f= 250 mm) in front of M2 meter and we placed a lens (1 m focal length) roughly 1 m away from the m2 meter.
The lens was adjusted so that the beam spot falls roughly at the center of traveling range of the stage.

We measured the M2 of the beam which gave the following result
M²x = 1.09 and M²y= 1.10.
Beam Waist Diameter X =702 µm
Beam Waist Diameter Y =703 µm
Beam Waist Position X =132 mm
Beam Waist Position Y =121 mm
Rayleigh Length X = 332 mm
Rayleigh Length Y =331 mm

The m2 value was better compared to the measurement done with the 250mm lens. However the Beam spot location of X and Y direction were off by 10 mm.
This astigmatism could be because of mismatch between beam and the optics axis of the lens.
We tried manually adjusting the lens but this was the minimum we could get by hand.
we can try tomorrow by placing the lens on a vertical x y stage to get fine movement.   

TITLE: 02/03 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
OUTGOING OPERATOR: Ibrahim
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 20mph Gusts, 14mph 3min avg
    Primary useism: 0.05 μm/s
    Secondary useism: 0.34 μm/s
QUICK SUMMARY: H1 has been locked for almost 5 hours.

• Wind moderately low, microseism falling below 95th percentile

Sheila, Camilla, Matt Todd

Sheila, Ibrahim, Tony and Ryan S had lots of SQZ issues over the weekend: 82588, 82599, 82597, 82585, 82581

Changed made to avoid these:

• To avoid mis-clicks changing alignment:
  • Sheila commented out any PSAMS changes from SQZ_MANAGER
• To stop SQZ angle servo oscillating with a ~15 minute range, see attached plot  (note we also saw it oscillate when OPO temp was wrong in 82249):
  • In SQZ_ANG_ADJUST, Sheila reduced the servo gain from 0.5 to 0.1
  • In SQZ_ANG_ADJUST, Sheila removed the checker that only changed the SQZ phase if it was >3deg off.
• SHG power has been low this weekend:
  • We think this was due to the Zone 4 LVEA temp dropping ~0.4degF, see attached plot. Shiela/Ibrahim then adjusted the temperature while the LVEA was colder to improve the SHG green power, but  once it warmed up this was not the correct temperature. I've added to the SQZ wiki to help troubleshoot this in the future.
• RESET_SQZ_ASC had incorrect gains hardcoded into it and resets only ZM4 and ZM5 when we are using ZM4 and ZM6:
  • Matt edited this save the sus lock gains for ZM4,5,6, reset them and then turn them back to their previous values.
  • We tested this by taking SQZ_MANAGER to NO_SQUEEZING and then OFFLOAD_SQZ_ASC, put back in SQZ and then went to RESET_SQZ_ASC_FDS (which clears all ASC)
  • This now works well and can be used if SQZ angle/ ASC runs away. I reduced the limits for when the SQZ angle is reset form 100-250 to now if outside 150-250deg.
• After the OMC alignment was changed, the SQZ looked a lot better. We ran SQZ_SQZANG_FDS to check the best sqz angle plot here, then adjusted adf deg 1deg, sdf.

I'm also updating SQZ troubleshooting wiki, to hopefully be more clear and allow the operator team to more easily solve future SQZ issues.

During commisioning this morning, we added the final part of the ESD glitch limiting, by adding the actual limit part to ISC_LOCK. I added a limit value of 524188 to ETMX_L3_ESD_UR/UL/LL/LR filter banks, which are the upstream part of the 28 bit dac configuration for SUS ETMX. These limits are engaged in LOWNOISE_ESD_ETMX, but turned off again in PREP_FOR_LOCKING.

In LOWNOISE_ESD_ETMX I added:

            log('turning on esd limits to reduce ETMX glitches')
            for limits in ['UL','UR','LL','LR']:
                ezca.get_LIGOFilter('SUS-ETMX_L3_ESD_%s'%limits).switch_on('LIMIT')

So if we start losing lock at this step, these lines could be commented out. The limit turn-off in PREP_FOR_LOCKING is probably benign.

Diffs have been accepted in sdf.

I think the only way to tell if this is working is to wait and see if we have fewer ETMX glitch locklosses, or if we start riding through glitches that has caused locklosses in the past.

Mon Feb 03 10:07:31 2025 INFO: Fill completed in 7min 28secs

TCmins [-89C, -87C] OAT (1C, 34F) DeltaTempTime 10:07:40

Low range coherence check due to the low range we've been having in our last lock. Attached below.

Shown is worse range for 10Hz to 55Hz compared to Dec 15 '24.

Closes FAMIS 26355, Last checked in alog 82451

Laser Status:
    NPRO output power is 1.845W
    AMP1 output power is 70.07W
    AMP2 output power is 135.9W
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN
    PDWD watchdog is GREEN

PMC:
    It has been locked 5 days, 21 hr 55 minutes
    Reflected power = 27.05W
    Transmitted power = 101.4W
    PowerSum = 128.4W

FSS:
    It has been locked for 0 days 0 hr and 49 min
    TPD[V] = 0.7664V

ISS:
    The diffracted power is around 3.2%
    Last saturation event was 0 days 0 hours and 49 minutes ago

Possible Issues:
    PMC reflected power is high

TITLE: 02/03 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Lock Acquisition
OUTGOING OPERATOR: Tony
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.36 μm/s
QUICK SUMMARY:

IFO is LOCKING at ACQUIRE_PRMI

IFO was locking when I came in having lost lock only 30 mins ago (14:57 UTC).

Sheila, Mayank

We wanted to double check the calibration of IM4 trans into power on PRM, similar to 63812 and 62213

• 10 Watts, single bounce ITMY 16:24 UTC
• OMC locked 16:35 UTC.  Sensor correction was off so this alignment is wobbling more than it otherwise would. 
• sensor correction on 16:40 UTC - 16:45 UTC.  1420908058 for 300 seconds
• IM4 trans and AS_C whitening gains were 18dB at the time of this measurement. 
• Medians:
  • H1:IMC-IM4_TRANS_NSUM_OUT16 9.855005
  • H1:IMC-PWR_IN_OUT16 9.997126
  • H1:ASC-AS_C_SUM_OUT16 0.007815647
  • H1:OMC-DCPD_SUM_OUT16 15.558
• Using Craig's code here to get all the optic transmissions (he cites where the numbers came from at the top of the file), we expect 0.244% of the power incident on PRM to reach HAM6 in single bounce. 
• If we continue to trust the calibration of AS_C, and the known transmissions that Craig collected, we would apply a correction of 0.9566 to IM4 trans.