Accepted SQZ alignments sdfs from Monday 79592, plot attached. SQZ and ASCSQZFC are fine as the guardian will take control of them.

Turned ZM2 SAMs back on to 90.

Turned on OFI TEC loop back on. Was at 21fdeg, the set point is closer to 25deg. We will later check what temperature is best.

GV7 was opened (from soft-close) at 09:15 PDT. I've reconfigured the vacuum alarms to now sound on GV7 close.

We have investigated the occurrence and correlation of specific states of the ISC_LOCK and INIT_ALIGN during O4a. We downloaded minute averaged data for these channels, taking the minimum for ISC_LOCK and the mean for INIT_ALIGN for every minute. The total number of minutes in O4a has been 341’281, we report the amount of time spent in each state as a percentage of the total time.

The left panel on the first plot shows the percentage of time spent in each ISC_LOCK states, while the right panel excludes the time spent in the ‘Low noise’ state.

We then looked into detail at the states occupied while the ISC_LOCK was in ‘prep’, ‘initial alignment’ or ‘als’ which make up the biggest contribution when we do not consider the ‘Low Noise’ state, i.e. when the detector is down.

The third plot shows the percentage of time out of the total time spent in ‘prep’ states for each of the sub-states.

The fourth plot shows the same for the ‘als’ states. It is interesting to notice that the total time spent in the state “Locking_arms_green” for O4a has been ~10 days, this includes the ISC_LOCK state 12 and the INIT_ALIGN state 8 while in the ISC_LOCK state 7 (Initial alignment).

In the fifth plot we show the percentage of time for each INIT_ALIGN state when the ISC_LOCK is on ‘Initial_alignment’ computed over the total time spent in this state. One can note that the most common states are ‘Locking_green_arms’, ‘SRC_aligning’, ‘Prc_aligning’ and ‘Init_align_complete’. The total time spent in this latter stage over the course of O4a is 12.5 hours. The last plot is an histogram of the occurrences of the consecutive minutes spent in the ‘init_align_complete’ status by INIT_ALIGN. The mean consecutive time spent in this state is 31 minutes. The outlier at 278 minutes corresponds to 3 am to 7 am on the 22^nd September 2023.

Wed Aug 21 08:08:22 2024 Fill completed in 8min 18secs

Gerardo confirmed a good fill curbside. Text alerts did not come through following cdslogin reboot yesterday. I have re-enabled this for tomorrow's fill.

I rebooted the seismon server (seismon2), which tracks incoming earthquakes.  A slow memory leak was causing it to run out of memory.  It will need another reboot in a few months.

TITLE: 08/21 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
CURRENT ENVIRONMENT:
    SEI_ENV state: MAINTENANCE
    Wind: 6mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.07 μm/s
QUICK SUMMARY: Corner volume pumpdown continues; HAM5/6 HEPIs are still locked but are ready to be unlocked again.

Today's activities:

- After the replacement of the PT-154 gauge (https://alog.ligo-wa.caltech.edu/aLOG/index.php?callRep=79599), and after the small volume of the gauge was pumped overnight, now it has been valved together with the main volume
- The small Pfeiffer turbo, along with the leak checker was taken off from the gauge's volume
- Then, the HAM7-BSC3 small FCT section was valved together with HAM7 - FCV-1 opened
- The 2 aux carts have been taken off from the HAM5/HAM6 annulus system
- An aux cart was added to GV7 for safety reasons, to protect its annulus system during opening it up
- The HAM6 turbo was valved out. The reason for valving it out so early is that the backing scroll pump had horrendous noise, so it needs rebuilding, and would have not been a good decision to let it run overnight. Especially, that the backing pressure was slowly growing. The hoses, cables, and the cart was also put away
- RGA scans were collected at the corner, before opening up the large gate valves - GV5 and GV7. The results will be posted to the comment section

Yesterday morning I unlocked HAM5&6 HEPIs, unaware that VAC needed back up on that chamber to disconnect turbos. This afternoon, Mitch and Ibrahim helped me re-lock those HEPIs. Because we didn't think any alignment work would be needed before unlocking again, we didn't use the normal procedure to try to preserve HEPI position, I just turned off the loops and we engaged the stops. Even so, the biggest offsets from operating position are less than 50 um/urad, most are more like 10.

TITLE: 08/20 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Corrective Maintenance
SHIFT SUMMARY: Just some light maintenance activities today as pumpdown continues. HAM5/6 HEPIs were locked so VAC team could valve out the turbopump on top of HAM6.
LOG:

MiriamR, RickS, TonyS, FranciscoL

On Monday, August 19, we moved the X-End pcal inner beam to be centered on the Rx input port. The previous configuration had the inner beam to the right of the Rx input port by 5mm. We centered the beam to the desigated position before the interferometer resumes the obsevation run.

Note: Screwing the yaw-adjuster in a clock-wise motion moves the beam from the right side of the target to the center (goes to the left).

The voltage from BothBeamsBefore.jpg was of 3.383 V as measured with a hanheld voltmeter, after moving the beams (see BothBeamsAfter.jpg) the voltage was of 3.384. EndStationLog.pdf has a list of voltage values with the corresponding times (local timezone) at which they were measured.

Janos, Dave:

After review of the current pressure alarms, we came up with the following changes:

1. Janos requested that PT120B (BSC2-BS) be replaced with PT132_MOD2 (BSC3-ITMX). The latter is a less noisy signal.

2. For alarms where the high level is an order of magnitude greater than the signal average, reduce the high to be about 3*avg

These changes were made and installed at 13:50 during the reboot of cdslogin.

To help with the review of the vacuum alarms I wrote a python program which compares the alarm HIGH value with a hours worth of minute trend data (AVG and MAX). If MAX/HIGH > 10 it flags the channel.

Code output before the change:

Compare Vac Alarm levels with past 1 hour of data
     H0:VAC-LX_X4_PT144B_PRESS_TORR   VE gauge, LX X1-beamtube, CC: high=5e-08 avg=2.27E-09 max=2.29E-09 ratio=2.18E+01!
     H0:VAC-MX_X1_PT343B_PRESS_TORR   VE gauge, MX X1-beamtube, CC: high=5e-09 avg=1.91E-09 max=1.93E-09 ratio=2.59E+00
     H0:VAC-MX_X5_PT346B_PRESS_TORR   VE gauge, MX X2-beamtube, CC: high=5e-09 avg=1.34E-09 max=1.35E-09 ratio=3.70E+00
     H0:VAC-EX_X1_PT523B_PRESS_TORR   VE gauge, EX X2-beamtube, CC: high=5e-09 avg=1.16E-09 max=1.17E-09 ratio=4.27E+00
     H0:VAC-LY_Y4_PT124B_PRESS_TORR   VE gauge, LY Y1-beamtube, CC: high=5e-08 avg=3.08E-09 max=3.15E-09 ratio=1.59E+01!
     H0:VAC-MY_Y1_PT243B_PRESS_TORR   VE gauge, MY Y1-beamtube, CC: high=5e-09 avg=1.39E-09 max=1.41E-09 ratio=3.55E+00
     H0:VAC-MY_Y4_PT245B_PRESS_TORR           VE gauge, MY CP4, CC: high=5e-09 avg=1.32E-09 max=1.34E-09 ratio=3.74E+00
     H0:VAC-MY_Y5_PT246B_PRESS_TORR   VE gauge, MY Y2-beamtube, CC: high=5e-09 avg=1.73E-09 max=1.77E-09 ratio=2.83E+00
     H0:VAC-EY_Y1_PT423B_PRESS_TORR   VE gauge, EY Y2-beamtube, CC: high=5e-09 avg=1.28E-09 max=1.29E-09 ratio=3.87E+00
     H0:VAC-LY_Y3_PT114B_PRESS_TORR VE gauge, CP1 LY vac gauge, CC: high=5e-08 avg=2.30E-09 max=2.33E-09 ratio=2.14E+01!
 H0:VAC-LX_Y8_PT132_MOD2_PRESS_TORR       VE gauge, PT120B BSC2 CC: high=2e-07 avg=1.94E-07 max=1.95E-07 ratio=1.03E+00
     H0:VAC-LY_X0_PT100B_PRESS_TORR                       HAM1 VAC: high=5e-06 avg=3.34E-08 max=3.35E-08 ratio=1.49E+02!

Code output after the change:

Compare Vac Alarm levels with past 1 hour of data
     H0:VAC-LX_X4_PT144B_PRESS_TORR   VE gauge, LX X1-beamtube, CC: high=6e-09 avg=2.28E-09 max=2.30E-09 ratio=2.61E+00
     H0:VAC-MX_X1_PT343B_PRESS_TORR   VE gauge, MX X1-beamtube, CC: high=5e-09 avg=1.92E-09 max=1.94E-09 ratio=2.58E+00
     H0:VAC-MX_X5_PT346B_PRESS_TORR   VE gauge, MX X2-beamtube, CC: high=5e-09 avg=1.34E-09 max=1.35E-09 ratio=3.69E+00
     H0:VAC-EX_X1_PT523B_PRESS_TORR   VE gauge, EX X2-beamtube, CC: high=3e-09 avg=1.17E-09 max=1.17E-09 ratio=2.56E+00
     H0:VAC-LY_Y4_PT124B_PRESS_TORR   VE gauge, LY Y1-beamtube, CC: high=9e-09 avg=3.10E-09 max=3.17E-09 ratio=2.84E+00
     H0:VAC-MY_Y1_PT243B_PRESS_TORR   VE gauge, MY Y1-beamtube, CC: high=5e-09 avg=1.40E-09 max=1.41E-09 ratio=3.54E+00
     H0:VAC-MY_Y4_PT245B_PRESS_TORR           VE gauge, MY CP4, CC: high=5e-09 avg=1.33E-09 max=1.34E-09 ratio=3.72E+00
     H0:VAC-MY_Y5_PT246B_PRESS_TORR   VE gauge, MY Y2-beamtube, CC: high=5e-09 avg=1.74E-09 max=1.77E-09 ratio=2.83E+00
     H0:VAC-EY_Y1_PT423B_PRESS_TORR   VE gauge, EY Y2-beamtube, CC: high=5e-09 avg=1.29E-09 max=1.29E-09 ratio=3.86E+00
     H0:VAC-LY_Y3_PT114B_PRESS_TORR VE gauge, CP1 LY vac gauge, CC: high=6e-09 avg=2.32E-09 max=2.35E-09 ratio=2.55E+00
 H0:VAC-LX_Y8_PT132_MOD2_PRESS_TORR           VE gauge, PT132 BSC3: high=6e-07 avg=1.94E-07 max=1.95E-07 ratio=3.08E+00
     H0:VAC-LY_X0_PT100B_PRESS_TORR                       HAM1 VAC: high=9e-08 avg=3.34E-08 max=3.35E-08 ratio=2.68E+00

FAMIS tasks 24854 and 24878, WP 12043

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

MX: Scroll pump hours: 221.5

       Turbo pump hours: 132

       Crash bearings: 100%

EX: Scroll pump hours: 7149.3

       Turbo pump hours: 1100

       Crash bearings: 100%

FAMIS tasks 24926 and 24950, WP 12052

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

MY: Scroll pump hours: 83.4

       Turbo pump hours: 219

       Crash bearings: 100%

EY: Scroll pump hours: 81.9

       Turbo pump hours: 1288

       Crash bearings: 100%

This morning, I attempted to improve the FSS RefCav alignment as the signal on the trans TPD has been falling over the past month. Using the two picomotor-controlled mirrors in the FSS path, I was only able to increase the signal from 0.54V to 0.66V, which is much less than I was hoping for. I'm still seeing what looks like a pitch misalignment on the RefCav REFL camera, but any further adjustment with the picos doesn't seem to be providing much more improvement on the TPD, so we'll likely need to go into the enclosure for some on-table alignment in the future to improve the alignment further.

WP12044 TW1 raw minute offload

Dave:

As the first part of the file copy, I configured h1daqtw1 to write its raw minute trends to a new empty directory, freezing the past 6 months of data in a renamed minute_raw_1408206258.

I temporarily reconfigured h1daqnds1 to serve the past 6 months of minute trends from this directory. The nds1 daqd process was restarted at 09:56 PDT with coordination with the control room.

WP12049 h1calcs model change

Louis, Joe B, Jeff, Erik, Dave:

A new h1calcs model was installed at 08:44 PDT. No DAQ restart was required.

Picket Fence

Erik,

Was restarted, remote station switch. Please see Erik's alog for details.

This morning, I manually ran through the usual magnetic injection suite (21 total injections across all stations) that's run before Tuesday maintenance during normal observing times to verify things were working. The only hiccup I encountered was that none of the injections at EX seemed to run; the amplifiers turned on correctly, the correct filter modules were applied, and Guardian showed no errors, but the magnetometers gave no response when the injection was supposed to start and I saw no signal in the appropriate _EXCMON channels. After conversing with Dave and Erik and seeing there was no problem starting a manual excitation, they suggested that the PEM_MAG_INJ Guardian likely needed to be restarted to re-establish connection with the frontends at EX since some of them were restarted in June. After restarting the node, I ran through the suite again and there were no issues.

The last successful test ran from 1408203575 to 1408204731 (about 22 minutes), and I've left the Guardian in WAITING.

Camilla, Oli

We looked into the weird results we were seeing in the ITMX In-Lock SUS charge measurements. The coherence when the bias is on for both the bias and length drives is always good, but the coherences are bad (usually below 0.09) for both bias and length drives when the excitations run with the bias off.

I compared the differences in the coherence value outputs in the python script versus the matlab script(screenshot), and although the values are calculated slightly differently and are not exactly the same, they are resonably close enough that we can say that there is not an issue with how we are calculating the coherences.

Next, we used ndscope to look at the latest excitations and measurements from July 09th (ndscope-bais on, ndscope-bias off). Plotting L3_LOCK_BIAS_OUTPUT, L3_DRIVEALIGN_L2L_OUTPUT, L3_LVESDAMON_UL_OUT_DQ, and L3_ESDAMON_DC_OUT_DQ for both ITMX and ITMY, if there was an issue with the excitations not going through, we would expect to see nothing on the ESDAMON and LVESDAMON channels, but we do see them on ITMX.

We were still confused as to why we would see the excitations go through the ESDAMON channels but still have such low coherence, so we compared the ITMX measurements to ITMY on dtt for the July 09th measurements looking at how each excitation showed up in DARM and what the coherence was. When the bias was on, both the bias drive and Length drive measurements look as we expect, with the drive in their respective channels, a peak seen in DARM at that frequency, and a coherence of 1 at that frequency(bias_drive_bias_on, length_drive_bias_on). However, in the comparisons with the bias off, we can see the excitations in their channels for both ITMX and ITMY, but while ITMY has the peak in DARM like the bias on measurements, ITMX is missing this peak in DARM(bias_drive_bias_off, length_drive_bias_off). The coherence between DARM and the excitation channel is also not 1 on ITMX.

We showed these results to Sheila and she said that these results for ITMX with the bias off make sense if there is no charge built up on the ITM, which would be the first time this has been the case! So there are no issues with the excitations or script thankfully.

We will be making changes to the analysis script to still run the analysis even if the coherence is low, and will be adding a note explaining what that means.