TITLE: 09/29 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 146Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 6mph 5min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:
H1 has been locak for just under an hour.
 

TITLE: 09/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 155Mpc
INCOMING OPERATOR: Tony
SHIFT SUMMARY:

Started shift with H1 in OBSERVING.  2hr commissioning break (followed by an immediate lockloss)!
LOG:

• 1521-1547 Optics lab/vac prep cleaning (karen)
• 1704 (1004amPT) H1 takes a notable drop in range from 153 down to 140Mpc;  It slowly returned to normal over the following hour.  
  • There were no obvious environmental culprits 
  • But Oli found that it was related to the CP1 autofill (as seen over the summer in July)
• 1746-1806 EY HVAC checks--no VEA incursion (tyler)
• 1826-1853 MY run (camilla)
• 1902 Down for COMMISSIONING (camilla, naoki)
• 2013-2125 MX turbo pump work (jordan)
• 2025-2125 MX turbo pump work (travis)
• 2106 Back to COMMISSIONING
• 2109 LOCKLOSS after an 18.5hr lock
• 2113-2125 MY for parts (travis)
• 2226 Back to OBSERVING

There is a noticeable dip in today's range 09/29 at 17:00UTC (attachment1). Zoomed in(attachment2), it is two separate dips set next to each other, where each affected our range for about 20 minutes.

I found that the H1:PEM-CS_ACC_BEAMTUBE_YMAN_X accelerometer had measured a lot of movement at the time of the first dip and lowered our range by almost 10Mpc (excluding the glitches)(attachment3). We found that this dip was correlated to the CP1 fill(73169) that started at 17:00UTC and lasted 18 minutes(attachment4). This had been seen in the range previously by Marissa and Brina (71301).

With regards to the second range dip we have not found a cause for that yet - all we know is that it showed up the most distinctly in BLRMS bands 1(10-20Hz) and 5(100-450Hz)(attachment5). It is also possible that this dip would otherwise have been a small range fluctuation if not for the CP1 fill having just affected us.

After LLO's 67058 ring heater tests, we adjusted our ETM RHs, hoping to reduce our high frequency noise that LLO induced during their test.

We adjusted ETMX up from 0.9W to 1.1W and ETMY down from 1.0W to 0.9W/segment 19:02 to 21:05UTC.

No big changes seen, our range, circulating power and squeezing got worse and kappa_c slightly increased, plotted attached. No visible change in DARM. Our HOM peaks moved slightly towards each other as expected. We lost lock before we thermalized back to nominal RH powers and could check that the offloading of SQZ pointing Naoki was doing ( 73171) didn't have an effect on the IFO.

Interesting is that with our best low frequency noise in end of march 68491, our circulating powers with 60W input in were actually lowest they have been. Plot attached.

As reported in alog73105, the ZM6 looks more saturated recently so I offloaded the ZM6 by moving ZM4. The ZM5 and ZM6 follow the movement of ZM4 by SQZ ASC. The first attached figure shows that the ZM6 LL/UR output reduced from 32000 to 21000 by ZM4 change. The second/third attached figures show the saturation of ZMs before/after this offload. You can see that the ZM6 LL/UR output reduced from red to orange region, while the ZM4 output increased from green to orange region. I have not seen the obvious SQZ BLRMS change by this offload.

I have updated the picket fence code in an intermediate step towards a better GUI. The details are in SEI log 2281.

The current set of stations for LHO can be seen in the attached images. The red lines in the plot represent the direction of incoming earthquakes on the database.

Fri Sep 29 10:18:06 2023 INFO: Fill completed in 18min 1secs

Gerardo confirmed a good fill curbside.

PSL Report FAMIS report:
Laser Status:
    NPRO output power is 1.829W (nominal ~2W)
    AMP1 output power is 67.04W (nominal ~70W)
    AMP2 output power is 134.8W (nominal 135-140W)
    NPRO watchdog is GREEN
    AMP1 watchdog is GREEN
    AMP2 watchdog is GREEN

PMC:
    It has been locked 7 days, 1 hr 3 minutes
    Reflected power = 16.23W
    Transmitted power = 109.0W
    PowerSum = 125.2W

FSS:
    It has been locked for 0 days 13 hr and 30 min
    TPD[V] = 0.7832V

ISS:
    The diffracted power is around 2.6%
    Last saturation event was 0 days 13 hours and 30 minutes ago

Possible Issues: None

TITLE: 09/29 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 7mph Gusts, 5mph 5min avg
    Primary useism: 0.01 μm/s
    Secondary useism: 0.13 μm/s
QUICK SUMMARY:

H1's been locked 12.5hrs, useism continues drifting down, and winds are calm, and overnight all looks well from the Control Room this morning (L1's range is lower than H1 due to No Squeezer.).

TITLE: 09/29 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: Oli
SHIFT SUMMARY: Mostly quiet shift with just one lockloss and a straightforward recovery. H1 has now been locked and observing for 4.5 hours.

• 00:37 Lockloss - alog
• 01:21 Alignment too poor to get PRMI (MICH_FRINGES didn't help), starting initial alignment
• 01:41 Alignment complete, starting lock acquisition
• 02:34 Reached NLN, fully automated acquisition
• 02:53 Started observing

LOG:

No log for this shift.

Lockloss @ 00:37 UTC - no obvious cause. Lockloss tool analysis failed, but I don't see anything abnormal on those plots.

LSC and ASC trends attached.

TITLE: 09/28 Eve Shift: 23:00-07:00 UTC (16:00-00:00 PST), all times posted in UTC
STATE of H1: Observing at 151Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 29mph Gusts, 25mph 5min avg
    Primary useism: 0.04 μm/s
    Secondary useism: 0.21 μm/s
QUICK SUMMARY: H1 has been locked for over 18 hours.

• All systems look good, wind is elevated but not extreme

TITLE: 09/28 Day Shift: 15:00-23:00 UTC (08:00-16:00 PST), all times posted in UTC
STATE of H1: Observing at 152Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Much more productive day, we stayed locked the whole shift and ran a calibration suite. Locktime of 18:08 as of 23:00UTC

• While LLO was down from an EQ I took a calibration measurement, we dropped out of observing from 19:29UTC to 19:59UTC for it.
• 21:58UTC Superevent S230928cb, again no verbal alarm for this event.
• We survived several earthquakes today

LOG:

I ran a calibration suite today,

/ligo/groups/cal/H1/measurements/PCALY2DARM_BB/PCALY2DARM_BB_20230928T193035Z.xml

Simulines:
GPS start: 1379964982.031822

GPS stop: 1379966313.087435

2023-09-28 19:58:14,885 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20230928T193609Z.hdf5
2023-09-28 19:58:14,928 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS_20230928T193609Z.hdf5
2023-09-28 19:58:14,946 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS_20230928T193609Z.hdf5
2023-09-28 19:58:14,963 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS_20230928T193609Z.hdf5
2023-09-28 19:58:14,982 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS_20230928T193609Z.hdf5

 

Full report available here.

Summary:

• Daily observing duty cycle: 87%, 32.3%, 66.2%, 43.8%, 71.3%, 73.9%, 91.9%. Week average: 66.6%
• Observed noise lines in h(t) occurring intermittently, particularly at 15, 29, and 32 Hz, throughout the week
• Lock-losses mostly caused by hardware/power issues, earthquakes, in some cases it looked like an earthquake caused a lock-loss but I could not find an obvious candidate in USGS
• High microseism throughout the beginning of the week, range floated in the 140-145 Mpc range from Mon-Wed, began to improve once microseism had calmed down in the latter half of the week
  • Mon had both high microseism and high winds, however the detector managed to ride out most of it
• Not much observing time on Tues due to maintenance
• On Thurs the detector lost observing time due to a hardware problem + alignment difficulties when attempting re-lock
• On Fri we noticed a regurly occurring ground motion in the corner station, which was picked up by multiple sensors and was weakly coupling to strain, as reported in this alog
  • Feature had appeared before, but not with the same frequency/regularity
  • Persisted throughout Fri/Sat, on Sun it changed and is now occurring less often, and more sporadically
  • Similar feature sometimes seen at LLO
  • DetChar suggested to follow-up by upconverting microphone data to audible range to help identify a cause
• Better duty cycle and range during the weekend, Sun in particular was very quiet (almost to 160 Mpc on Sun)
• Re-appearance of comb associated with OM2 heater (alog), later seemed to change frequency spacing
• Few PyCBC triggers with chi2-weighted SNR above 10
• H1:SUS-ETMX_L3_OPLEV_PIT_OUT_DQ and H1:ASC-DHARD_Y_OUT_DQ were frequently in the top two Hveto round winners for the week

We've been locked for 14hours, we've rode through a few earthquakes this morning. The airhandler alarm for MX has lost connection. The wind is also a lot more managable this morning/afternoon.

Thu Sep 28 10:22:26 2023 INFO: Fill completed in 22min 21secs

Gerardo confirmed a good fill curbside

Oli, Camilla

ISC_LOCK takes longer to recognize and move to the LOCKLOSS state when a lockloss occurs than we want it to, sometimes leading to confusion regarding lockloss causes. Example: 71659

The part of ISC_LOCK that determines whether we have lost lock is in the is_locked function in ISC_library.py(attachment1). The current parameters for determining a lockloss rely on the H1:LSC-TR_X_NORM_INMON channel - once that channel's value falls below 500, ISC_LOCK will recognize that we have lost lock and will take us to the LOCKLOSS state.

Currently, when we are locked LSC-TR_X_NORM_INMON sits right around 1540, and when a lockloss happens, it takes ~0.55-0.65s after the lockloss start (based on ASC-AS_A_DC_NSUM_OUT) to drop below 500, and then takes another ~0.07-0.15s for ISC_LOCK to register this and take us to LOCKLOSS. To minimize this latency, since LSC-TR_X_NORM_INMON never gets below 1450 once we reach NOMINAL_LOW_NOISE, Camilla and I think it would be useful for the LSC-TR_X_NORM_INMON is_locked threshold value to be raised significantly to allow ISC_LOCK to register locklosses faster than it is currently. By raising the threshold to 1300 for example(attachment2), the time between the lockloss start and ISC_LOCK changing states would be reduced by a factor of 2-3.