FRS9371

The CDS alarms system status is now shown on the CDS Overview MEDM. The attached snapshots show the system when there are no alarms, and when two test alarms were raised.

Clicking on the "CDS ALARM" button on the overview opens the alarm MEDM.

Details:

The locklossalert EPICS IOC was modified to provide, as EPICS PVs, the ALARMS GPS time, the number of active alarms, and the channels which are in alarm.

locklossalert and alarms both run on cdslogin, and so a temporary file is used for the interprocess communication. Alarms updates the file on the minute and LLA reads the file at the 30 second mark.  If the temporary file stops being updated, the oveview button will turn magenta to indicate a stopped service.

With the IFO down due to an earthquake, went out to the LVEA to verify installation and location of the Picomotor Driver E. This controller was slotted for Optical Lever but never implemented.

Control and readback cables are connected to the Corner 2 Slow Controls Chassis (D1100680) in the CER. Cables labeled H1:IO_305 and H1:IO_306 are connected in slot 5 on the rear of the chassis. Cables are routed to the HAM6 ISC racks. No driver is installed in the LVEA. Cables are disconnected and coiled up in the cable tray.

7.0 off the coast of N. California. Tripped all ISIs and many suspensions.

Thu Dec 05 10:07:59 2024 INFO: Fill completed in 7min 56secs

Jordan confirmed a good fill curbside.

FranciscoL, SheilaD

Changed H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN by 3.63 % using KappaToDrivealign.py at gps 1417450784.

Script output:

Average H1:CAL-CS_TDEP_KAPPA_TST_OUTPUT is -3.6267% from 1.
Accept changes of    
H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN from 191.711517 to 198.664299
Proceed? [yes/no]
yes
Changing
H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN
H1:SUS-ETMX_L3_DRIVEALIGN_L2L_GAIN => 198.6643

First figure (kappa2drivealign_ndscope) is an ndscope of the relevant channels. The the second plot (top to bottom) is CAL-CS_TDEP_KAPPA_TST_OUT with a verticar marker aligned at a time where the uncertainty from CAL-CS_TDEP_PCAL_LINE3_UNCERTAINTY (third plot)  increased. This increase in uncertainty is expected from turning off lines before calibration measurement.

KAPPA_TST_OUT is around 1 from minute 5 to the marker, which is the objective of changing the drive gain.

Following our usual instructions.

Simulines start:

PST: 2024-12-05 08:35:51.659267 PST
UTC: 2024-12-05 16:35:51.659267 UTC
GPS: 1417451769.659267
 

Simulines end:
PST: 2024-12-05 08:59:32.899615 PST
UTC: 2024-12-05 16:59:32.899615 UTC
GPS: 1417453190.899615
 

2024-12-05 16:59:32,822 | INFO | File written out to: /ligo/groups/cal/H1/measurements/DARMOLG_SS/DARMOLG_SS_20241
205T163552Z.hdf5
2024-12-05 16:59:32,830 | INFO | File written out to: /ligo/groups/cal/H1/measurements/PCALY2DARM_SS/PCALY2DARM_SS
_20241205T163552Z.hdf5
2024-12-05 16:59:32,834 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L1_SS/SUSETMX_L1_SS
_20241205T163552Z.hdf5
2024-12-05 16:59:32,838 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L2_SS/SUSETMX_L2_SS
_20241205T163552Z.hdf5
2024-12-05 16:59:32,843 | INFO | File written out to: /ligo/groups/cal/H1/measurements/SUSETMX_L3_SS/SUSETMX_L3_SS
_20241205T163552Z.hdf5
ICE default IO error handler doing an exit(), pid = 911686, errno = 32

We should return to Observing at 20 UTC.

TITLE: 12/05 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
OUTGOING OPERATOR: Ryan C
CURRENT ENVIRONMENT:
    SEI_ENV state: CALM
    Wind: 3mph Gusts, 1mph 3min avg
    Primary useism: 0.02 μm/s
    Secondary useism: 0.17 μm/s
QUICK SUMMARY: Locked for 36 hours! Looks like we just made it through a 5.6 from Alaska, as well as some smaller quakes in CA. Otherwise a calm environment and no alarms.

TITLE: 12/05 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 161Mpc
INCOMING OPERATOR: Ryan C
SHIFT SUMMARY: Very quiet shift with H1 observing throughout; current lock stretch is now over 26 hours. Only thing to report is that the SQZ_PMC Guardian has occasionally been saying the PMC PZT volts are low; currently around 6V and has been low for a few hours (see attached trend), but hasn't unlocked.

FAMIS 28455, last checked in alog81106

Only things of note on these trends are that the ITMX spherical power has been dropping for the past week and a half, which Camilla agrees looks strange, and the ITMY SLED power has reached the lower limit of 1, so it will need replacing soon. Everything else looks normal compared to last check.

TITLE: 12/04 Eve Shift: 0030-0600 UTC (1630-2200 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
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: H1 is running smoothly, has been observing for 20+ hours.

• Wind and secondary microseism low
• All other systems nominal

TITLE: 12/04 Day Shift: 1530-0030 UTC (0730-1630 PST), all times posted in UTC
STATE of H1: Observing at 158Mpc
INCOMING OPERATOR: Ryan S
SHIFT SUMMARY: Locked for 20 hours. Very quiet shift with nothing to report.
LOG:                                                                                        

FAMIS 21691

pH of PSL chiller water was measured to be just above 10.0 according to the color of the test strip.

Wed Dec 04 10:07:33 2024 INFO: Fill completed in 7min 30secs

Gerardo confirmed a good fill.

FAMIS 26019

I somehow missed this email last week so it's a week late. The last time this was ran on Nov 10, the main differences are:

• I noticed more narrow band peaks in some of the plots, particularly the HAMs, seemed higher than in the past.
• HAM8 looks a touch quieter than before
• ITMY looks much quieter

Camilla C., TJ

Recently, the CO2Y laser that we replaced on Oct 22 has been struggling to stay locked for long periods of time (alog81271 and trend from today). We've found some loose or bad cables in the past that have caused us issues, so we went out on table today to double check they are all ok.

The RF cables that lead into the side of the laser can slightly impact the output power when wiggled, in particular the ones with a BNC connector, but not to the point that we think it would be causing issues. The only cable that we found loose was for the PZT that goes to the head of the laser. The male portion of the SMA that comes out of the laser head was loose, and cannot be tightened from outside of the laser. We verified that the connection from this to the cable were good, but wiggling it did still introduce glitched in the PZT channel. I don't think that we've conviced ourselves that this is a problem though, because the PZT doesn't seem to glitch when the laser loses lock and instead it will run away.

An unfortunate consequence of the cable wiggling was that one of the Beckhoff plugs at the feedthrough must have been unseated slightly and caused our mask flipper read backs to read incorrectly. The screws for this plug were not working so we just pushed the plug back in to fully seat it and all seemed to work again.

We still are not sure why we've been having these lock losses lately, the 2nd and 3rd attachments show a few of them from the last day or so. They remind me of back in 2019 when we saw this - example1, example2. The fix ultimately a chiller swap (alog54980), but the flow and water temp seem more stable this time around. Not completely ruling it out yet though.

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.