Back on December 05th 2024 we had a really large earthquake come through from northern California. This large nearby earthquake reminded Sheila of an old script that checked to see if the test masses had acquired any charge from hitting an earthquake stop during an earthquake. This script had been used to discover hysteresis after particularly large earthquakes in 2017 (37799) and in 2020 (55880). We decided it would be a good idea to check for this earthquake, so we wrote a quick python script move_all_quads_pitch.py that changed the OPTICALIGN pitch for 110 seconds before moving everything back. I then took the matlab script from 2020, check_hysteresis_2020.m and edited the times and channels so that it would grab minute trends for the DAMP_IN and COILOUTF_OUT channels for the week leading up to the earthquake, and then grabbed raw trends for those same channels after the earthquake and during the period of time where we had moved the OPTICALIGN pitch. I plotted the OSEM readings (DAMP_IN) versus the applied force (COILOUTF_OUT) for both times against each other for each test mass and got this plot. Looking at this in addition to the pitch drift plots from the summary pages(ITMX, ITMY, ETMX, ETMY), it doesn't look like any of the test masses encountered any hysteresis as a result of any earthquake stop hits.

All these scripts and results can be found in userapps/sus/h1/scripts/check_hysteresis_after_EQ and have been committed to svn.

After TJ and I replaced the fiber collimator for the ETMX HWS signal last week, we can see some believable ETMX HWS signals. Ther is still something strange happening as we power up (maybe retroflections off ITM before we move spots), but once we reach 60W we can see the test mass change curvature as expected. See attached ETMX signals at 3 minutes, 5 minutes, 20 minutes and trends. We don't expect this HWS signal to be accurate as have done no calculating of the mode matching after we removed a lens in 81734 but we took the data to do so.

There's a dead pixel we should remove but the code has an error "Plotting error: Object Array cannot be loaded when allow_pickle= False" that's not letting me see the Original image.

Camilla, Sheila

We pico'd to center on the POP QPDs, which we were falling off.  POP A QPD is used during DRMI ASC, we had been using a large offset.  Now in full lock POPA is centered, and in the sdf safe and observe files I've accepted turning off the offset and setting it to 0.

We also noticed a bug with the picomotor code, which is that if someone changes the current motor while the H1:SYS-MOTION_C_PICO_A_INUSE (yellow box on medm) is showing, the current motor channel changes and the medm makes it look like the current motor has changed, but clicking will move the wrong motor.  The second screenshot shows this happening, at the time of thei first time cursor, the current motor was 6 but motor 5 was moving.

WP12249

In preparation for the TW0 raw minute trend offload of data accumulated since 18th June 2024 (6 months) TW0 was configured to freeze the old data and write to a new location and NDS0 was configured to serve the past 6 months a trends from their temporary location.

NDS0 DAQD was restarted at 11:41 PDT. This is not the default NDS, so it should have had no impact on control room or FOM.

Shiela and I put back in the SRCL ASC and LSC offsets we found in 81792 to maximize thew coupled cavity poll. Again, the range didn't increased, the FCC increased ~3HZ but hkappa_C decreased ~0.5%. We planned to improved OMC alignment to bring back up the range and kappa_C. Plot attached.

We started repeating the OMC ASC injections form 78616, but this saturated the OMC SUS so we aborted and decided that any gains made would be very small and not worth the time. Reverted SRCL ASC and LSC offsets.

Mon Dec 16 10:15:30 2024 INFO: Fill completed in 15min 27secs

Gerardo confirmed a good fill curbside.

Sheila, Camilla

In 81760 we saw that SQZ was adding noise 20-40Hz. I repeated today FDS and no sqz and don't see the same added noise, only a very small amount around 20Hz. See attached (4 minute 0.1Hz average). We're not sure what would be changing. It's possible that the range correlates with FC beamspot, see attached plot. This morning Sheila showed that the ~5MPc drift in the range during the last locks is mainly around 20-40Hz dtt.

I re-enabled FC beamspot control plot as in 80970, edited sqzparams, reloaded  SQZ_FC and accepting sdfs. We have not checked the offsets.

Sheila, Brice

Brice asked for some injections to check for bicoherence, and to check the bicoherence code that his group is working on.

At 17:49 UTC we injected into LSC-DARM2 at 3e-2 counts at 23Hz and 25 Hz, and 1e-2 at 48 Hz.  (red 4 +5)

At 18:00:30-18:04 UTC we injected into LSC-MICH1 at 25 Hz at 3e-3 counts, LSC-SRCL1 at 23 Hz at 3e-3, and LSC DARM2 at 48 Hz amplitude 1e-2. (ref 6-8)

At 18:10 UTC we injected into LSC-SRCL at 23 Hz at 3e-3, and ASC-DHARD_P at 25 Hz, and LSC-DARM2 at 48 Hz at 1e-2. 

Template is saved at /sheila.dwyer/Noise/line_injections/line_injections_dec16_2024.xml

FAMIS 31064

The PMC mode-matching check done in the enclosure last Tuesday is clearly seen on many trends.

PMC REFL is still steadily increasing along with a steadily decreasing RefCav TPD and ISS diffracted power percentage. It's possible this is due to alignment drifting into the PMC, so if time allows during maintenance tomorrow, I'll try an alignment adjustment along with the already planned FSS path tuneup.

TITLE: 12/16 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 156Mpc
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 11mph Gusts, 7mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.31 μm/s
QUICK SUMMARY:

H1's been locked 9.25+hrs and microseism is just touching up on the 95th percentile.  Rainy drive on the way in.

TITLE: 12/16 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Lock Acquisition
INCOMING OPERATOR: Oli
SHIFT SUMMARY:

IFO is LOCKING at MOVE_SPOTS

Very quiet shift with one Lockloss (alog 81838). DRMI was able to lock 20 minutes post LL, which is great recovery time! (and this includes having to go through PRMI and touching PRM/BS).

Conditions are relatively quiet with very low wind and seismic motion. The microseism has leveled off but seems like it may be turning around and increasing again.

Other than that, there is a quiet whistling/alarm-like sound coming from the MSR. However, I don't know if it was always there and I only realized now or if something is up. I went in briefly to see if something was immediately wrong (red lights or anything) but couldn't find anything of concern. I went to the source of the sound, pictures below from front and back. Since we were quietly observing, guardian had no messages, nothing apparent upon investigation in the MSR and there were no alerts in the control room, I elected not to call CDS but did tag them here and messaged Dave regarding the problem. Investigating further, there was one alog from 2017 that mentioned that there is a sounding alarm in the MSR which only told me that such a thing was possible. In that alog, it was due to the temperature, but checking the thermostats in the room, they seemed (and felt) to be workng.

LOG:

None

CHARD Y signal was oscillating above the other channels on NUC29 (ASC) pre-lockloss.

Lockloss tool shows the ETM Glitch channel did see a non-saturating glitch ~12ms before the Lockloss, so it may be that though I don't know if 10ms is enough time to confirm this as the cause.

TITLE: 12/15 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Ibrahim
SHIFT SUMMARY:

Microseism continues to plummet.  

Robert has been running electric ground measurements at various points in the Corner Station--NOT in LVEA (i.e. Mechanical Room's Squeezer racks and Vacuum racks on & under the Mezzanine).

Only one lockloss during the shift with a 52-min relock (noted below).  Range is currently a bit higher with even a 168Mpc data point.
LOG:

• 2109 LOCKLOSS (after a 11hr41min lock)
  • ALSx was off in YAW (intervened via TMSx yaw)
  • Check_Mich_Fringes run, then PRMI....with PRM yaw tweak to lock it up, DRMI locked up within ~2min.
  • 2158 M5 Incoming EQ from Japan.
  • 2205 OBSERVING

TITLE: 12/16 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 159Mpc
OUTGOING OPERATOR: Corey
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 9mph Gusts, 7mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.26 μm/s
QUICK SUMMARY:

IFO is in NLN and OBSERVING as of 22:03 UTC.

Conditions are good. Wind is low, microseism is low.

While checking FOMs noticed the SYSTEMATIC_ERROR ndscope on nuc24's "Calibration Screen" was dead/showing no data---clicked the START for the window to get this back.

Sun Dec 15 10:16:47 2024 INFO: Fill completed in 16min 44secs