Reports until 08:29, Thursday 05 September 2024
H1 CDS
david.barker@LIGO.ORG - posted 08:29, Thursday 05 September 2024 - last comment - 08:48, Thursday 05 September 2024(79913)
X-Arm long-range-Dolphin IPC errors from h1susetmx model 02:08 Thursday

At 02:08:03 the h1oaf and h1calcs models reported a single IPC receive error for channels being sent by the h1susetmx model.

Preliminary findings:

For all three channels this was a single IPC error in all receivers (one packet in that second's 16384 packets didn't get received in time)

There was no issue with h1susetmx's CPU usage at the time

There was no issue with h1cdsrfm's EX2CS thread (nor any thread) processing at the time

Images attached to this report
Comments related to this report
david.barker@LIGO.ORG - 08:33, Thursday 05 September 2024 (79914)

The three IPC channels which went into error are the complete set of LRD channels being sent by the h1susetmx model. (grep for RFM0 channels sent by h1sustemx model in the H1.ipc file shown)

05Sep08:17 > grep -B 1 -A 3 RFM0 H1.ipc|grep -B 4 h1susetmx$
[H1:SUS-ETMX_CAL_CS_L1_LINE]
ipcType=RFM0
ipcRate=16384
ipcHost=h1susex
ipcModel=h1susetmx
--
[H1:SUS-ETMX_CAL_CS_L2_LINE]
ipcType=RFM0
ipcRate=16384
ipcHost=h1susex
ipcModel=h1susetmx
--
[H1:SUS-ETMX_CAL_CS_L3_LINE]
ipcType=RFM0
ipcRate=16384
ipcHost=h1susex
ipcModel=h1susetmx
 

david.barker@LIGO.ORG - 08:48, Thursday 05 September 2024 (79917)