Looked at the spectum of th 50W CO2 lasers on the fast VIGO PVM 10.6 ISS detectors when the CO2 is locked (using the laser's PZT) and unlocked/ free running: time series attached. Small differences <6Hz, see spectrum attached. 

Tue Dec 17 10:02:58 2024 INFO: Fill completed in 2min 56secs

Quick fill, coincident with dewar filling.

Ryan S noticed that the range drop before the lockloss at 11:34UTC could be related to the glitches we've been seeing as Omicron sees similar glitches screenshot. DARM looks worse 30-100Hz plot.

Besfreo the lockloss we see a 26-28Hz wobble in DARM (not in the other LSC loops) plot.

TITLE: 12/17 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Preventive Maintenance
OUTGOING OPERATOR: Oli
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 2mph 3min avg
    Primary useism: 0.03 μm/s
    Secondary useism: 0.39 μm/s
QUICK SUMMARY:

IFO re-locked itself twice overnight and is currently running magnetic injections before we start maintenance activities.

Slight strangeness that the IFO mode was in "relocking" H1:ODC-OBSERVATORY_MODE = 21 when I arrived.

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

IFO is in INITIAL_ALIGNMENT and ENVIRONMENT

Still recovering from the 7.4 EQ today in Vanuatu. After this, there were many 5+ Mag aftershocks and our primary microseism is still above the 0.1 line. We briefly left EQ mode for 5 or so minutes before another earthquake (Atlantic Ocean this time) caused us to reactivate.

I began locking at 05:22 UTC and managed to get to PRMI but had no flashes. A few minutes later, another EQ hit and we lost lock. At this point, I started initial alignment. I believe IFO will be able to lock very soon since seismic conditions are coming down quickly.

Lockloss Alog 81859

Other:

As the pacific plate shook, Robert took the time to conclude his viewport work, meaning we are capable of transitioning to LASER SAFE once again. I have informed the morning operator independently too.

Interesting LL that happened between the detection of a 7.4 mag EQ but before any picket fence or STS detection. So I don't think it's EQ caused but seems suspicious. Either way, we're riding out a huge EQ right now and will attempt locking afterwards.

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

Today H1 has been locked the entire shift (over 18hrs!) with the main activity being H1 out of Observing for the Monday Commissioning work (which went 30min over for the period of 1630-2006utc).

Microseism has mostly been flat just under the 95th percentile.
LOG:

Vacuum Prep's Dust Monitor (H1:PEM-CS_DUST_LAB2) continues to alarm on the Alarm Handler (white/invalid alarm) & comes up as NOT OK/Error on the Dust_Monitor script check.

• 1615-1632 optics lab/vacuum prep cleaning (karen)
  • 1645-1715 PCal cleaning w/ Tony escort (karen)
  • 1720-1833 MY cleaning (karen)
• 1628-1717 MX cleaning (kim)
• 1630-2006 MONDAY COMMISSIONING!!!!
  • 1630-1720 no-squeezing measurements (camilla)
  • 1635 viewport work which includes removing PR2 camera---Dave was on top of this asking what happened to it. (robert)
    • LVEA is HAZARD and for Robert's work there is aluminum foil covering the viewports he was working on (if there is a lockloss, he can reinstall the viewport covers).  Tomorrow at the start of Maintenance 
  • Commissioning extended 30+min for L1 & H1.
• 1942 Beginning to make free disk space via nds0 over next multiple days--will not affect work in control room (dave via WP#12249)
• 1944-2052 Working on Tractor Tire near water tank (tyler, les schwabb)
• 2213-2220 Measurements in PCal Lab (tony)
• 2253-2255 Receiving roll-up (christina)
• 2335 Closing a Mechanical Room HVAC fan door which was ajar---RyanS/Jason noticed it (tyler)

Closes FAMIS#26020, last checked 81715

Things to note:

• On HAM7 around 50 Hz, V1/V2/V3 have a large spike that wasn't there last week
• On ITMX Stage1, new spike  in V3 around 48 Hz
• On ITMY Stage1, new spike in V2/V3 around 48 Hz
• On BS Stage1, new spike in V2/V3 around 48 Hz
• On ETMX Stage2, V2/V3 spike at 30 Hz is a bit larger

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

IFO is in NLN and OBSERVING as of 6:34 UTC (17hr 30 min lock!)

Environment looks good.

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.

Closes FAMIS#28383, last checked 81688

Once again, the coherence for ITMX bias drive bias off is below the coherence threshold - this time the coherence is 0.01, much lower than the threshold of 0.1, so there are once again no new analyzed measurements for ITMX.

ETMX, ETMY, ITMX, ITMY

Ansel reported that a peak in DARM that interfered with the sensitivity of the Crab pulsar followed a similar time frequency path as a peak in the beam splitter microphone signal. I found that this was also the case on a shorter time scale and took advantage of the long down times last weekend to use  a movable microphone to find the source of the peak. Microphone signals don’t usually show coherence with DARM even when they are causing noise, probably because the coherence length of the sound is smaller than the spacing between the coupling sites and the microphones, hence the importance of precise time-frequency paths.

Figure 1 shows DARM and the problematic peak in microphone signals. The second page of Figure 1 shows the portable microphone signal at a location by the staging building and a location near the TCS chillers. I used accelerometers to confirm the microphone identification of the TCS chillers, and to distinguish between the two chillers (Figure 2).

I was surprised that the acoustic signal was so strong that I could see it at the staging building - when I found the signal outside, I assumed it was coming from some external HVAC component and spent quite a bit of time searching outside. I think that this may be because the suspended mezzanine (see photos on second page of Figure 2) acts as a sort of soundboard, helping couple the chiller vibrations to the air. 

Any direct vibrational coupling can be solved by vibrationally isolating the chillers. This may even help with acoustic coupling if the soundboard theory is correct. We might try this first. However, the safest solution is to either try to change the load to move the peaks to a different frequency, or put the chillers on vibration isolation in the hallway of the cinder-block HVAC housing so that the stiff room blocks the low-frequency sound. 

Reducing the coupling is another mitigation route. Vibrational coupling has apparently increased, so I think we should check jitter coupling at the DCPDs in case recent damage has made them more sensitive to beam spot position.

For next generation detectors, it might be a good idea to make the mechanical room of cinder blocks or equivalent to reduce acoustic coupling of the low frequency sources.