TITLE: 10/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 157Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 4mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.20 μm/s
QUICK SUMMARY: H1 has been locked and observing for 2 hours. Sounds like it's been a relatively quiet day so far.

• Wind is low, microseism moderately low
• All other systems nominal

We get another false positive VACSTAT alarm for PT132 due to a noise spike. Alarm was raised at 14:29, I cleared it by restarted vacstat_ioc on cdsioc0 at 15:41

The AIP for GV10 is red, system railed about 2 hours ago.  System will be assessed next Tuesday or at the next opportunity, we may need to replace the ion pump for GV10.

FAMIS 26333, last checked in alog80540

All fans within noise range and largely unchanged compared to last check.

No clear reason why, the lockloss website isn't updating "online last update: 237.1 min ago (2024-10-11 09:23:15.156027)"

Fri Oct 11 10:12:04 2024 INFO: Fill completed in 12min 0secs

Gerardo confirmed a good fill curbside. TCs looking much better today.

Lockloss at 16:21 UTC (9:47 lock)

TITLE: 10/11 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 154Mpc
OUTGOING OPERATOR: TJ
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 4mph Gusts, 2mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY:

• We've been locked for 8 hours, inb Observing since 06:36 UTC
• Secondary microseism is decreasing
• SQZ doesn't look great at high frequency
• Low range check

TITLE: 10/11 Eve Shift: 2330-0500 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: TJ
SHIFT SUMMARY:

IFO is LOCKING at FIND_IR. I see IR resonances in both Comm and Diff (screenshot) so I believe guardian will be able to find IR (though it has now taken a few mins).

Super calm shift. Was observing the entire time until at 04:28 UTC, we had a Lockloss (Lockloss alog 80610).

LOG:                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                           

Lockloss after 9hrs and 45 minutes in NLN.

Cause so far unknown but known not to be the PSL (IMC and ASC lost lock 200ms apart).

Closes FAMIS 26011. Last checked in alog 80261. 

No significant changes from last week.

TCS Monthly Trends

Closes FAMIS 28453. Last checked in alog 79893.

• H1 TCS ITMY CO2 Laser Power is below threshold and has been for a month. Last time, it was only under by 0-1W but over the course of the last month, it has gone down to 30W (threshold is 35W) (top CO2 trend).
• HWS SLED for both has been slowly decreasing and for the case of ITMY, seems like it may reach the 1mW threshold for replacement soon. (top HWS trend)
• HWS Probe Spherical Power look very different to last month's though there's no threshold given in the guide alog. The trend looks to be fluctuating a lot from the flatline 65ish cts last month's check had. Unknown if this is a cause for investigation. (middle HWS trend)
• HWS simulated change in lensing does look more similar to the the middle trend (as they should) than last month. Unknown what this implies. (end HWS trend)

Blade tips on BBSS M1 were lowered to -3.0mm (previously -1.5mm) and transfer functions measurements were taken on October 04th. See Ibrahim's alog for an overview of our issues with the BBSS and why the blade heights have been changed.

Results for this set of transfer functions

Length and pitch for this set of transfer functions compared to previous (aug 30) LHO measurements and LLO October 7th measurements, zoomed

Length and pitch for last three measurements (LHO 08/30, LLO 10/07, LHO 10/04) compared their respective best-fitting models (different physical d1's)

TITLE: 10/10 Day Shift: 1430-2330 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY: Currently Observing at 158Mpc and locked for 5 hours. A lot of time out of Observing today due to continued PSL troubleshooting and commissioning. Relocking after our one lockloss wasn't too bad.
LOG:

14:30 Observing and Locked for 4 hours

15:02 Out of Observing for Commissioning
15:29 Lockloss
    16:24 Going through CHECK_MICH_FRINGES a second time, so decided to run an initial alignment only for PRC, MICH, and SRC
    15:29 manual initial alignment done, relocking
    16:39 Lockloss from LOCKING_ALS
    16:49 IDLE for PSL power swap
    17:45 Started relocking
    17:51 Lockloss from ACQUIRE_DRMI_1F
18:42 NOMINAL_LOW_NOISE
20:25 Observing

21:45 Out of Observing to run calibration sweep
22:51 Observing

23:25 - 23:37 Trash truck onsite - tagging PEM, DetChar                                                                                                                                                                                                                                                                                                                                                                                                                                                                             

The sum of the counts on the QPD IMC-IM4_TRANS_NSUM_OUT has been around 53W since July 2nd, 2024(attachment1). Before this, the nsum value was around 58W. On July 2nd, the PMC was swapped (78813), and so the pointing into the ifo changed. After the PMC change the IMC alignment was updated to realign the beam(78816), but the IM4 trans beam is still not hitting in the same place as it was before. As a result, the beam is very off in yaw when it hits the QPD, so yaw is currently at +0.98 so it's on the edge. You can also tell the beam is partially off the QPD because of how much change we see in the IM4 trans values as compared to before July 2nd.

WP 12136

One of the solar panels on Y2-8 was replaced. Panels provide power to a vacuum gauge inside the beamtube enclosure.

F. Clara, G. Moreno

I ran the noise budget injections for frequency noise, input jitter (both pitch and yaw) and PRCL. All injections were run with CARM on one sensor (REFL B). The cable for the frequency injection is still plugged in as of this alog, but I reset the gains and switches so we are back on two CARM sensors and the injection switch is set to OFF.

All injections are saved in the usual /ligo/gitcommon/NoiseBudget/aligoNB/aligoNB/H1/couplings folder under Frequency_excitation.xml, IMC_PZT_[P/Y]_inj.xml, and PRCL_excitation.xml.

I realized an intensity noise injection might be interesting, but when I went to run the template for the ISS excitation, I was unable to see an excitation. I think there's a cable that must be plugged in to do this? I am not sure.

*********Edit************

Ryan S. sent me a message with this alog that has notes about how intensity noise injections should be taken. Through this conversation, I realized that I had misread the instructions in the template. I toggled an excitation switch on the ISS second loop screen, when I should have instead set the excitation gain to 1.

I was allowed another chance to run the intensity injections, and I was able to do so, using the low, middle, and high frequency injection templates in the couplings folder.

Also, the Input jitter injections have in the past been limited to 900 Hz, because the IMC WFS channels are DQed at 2048 Hz. However, the live IMC channels are at 16 kHz, so I edited the IMC injection templates to run up to 7 kHz, and use the live channels instead of the DQ channels. That allowed the measurements to run above 900 Hz. However, the current injections are band-limited to only 1 or 2 kHz. I think we can widen the injection band to measure jitter up to 7 kHz. I was unable to make those changes because we had to go back to observing, so this is future to-do item. I also updated the noise budget code to read in the live traces instead of the DQ traces.

Unfortunately, in my rush to run these injections, I forgot to transition over to one CARM sensor, so both the intensity and jitter measurements that are saved are with CARM on REFL A and B.