After discussing with Frederic Cleva and the Nice team, we set up a specific monitoring of PSTAB glitches.

An omicron online process (Om_parameters_pstab_00) was introduced to monitor V1:PSTAB_PD1_AC glitches. This process measures the glitch rate in V1:PSTAB_PD1_AC, only considering triggers with SNR>70.

Important #1: the glitch rate is measured before clustering, which means that the rate of individual omicron tiles is measured and it can be very large. This is not an issue since we use a high SNR threshold. Therefore, the rate is 0 most of the time. When there is a glitch in PSTAB, the rate takes non-zero (and very large) values.

Important #2: when the rate is too large (very high SNR glitches), Omicron saturates. A special value (-10) is given to the rate measurement.

The name of the rate channel is V1:OMICRON_RATE_SNR_70_ADC_PSTAB_PD1_AC and it sampled at 1 Hz. This channel can be accessed in the raw data.

Important #3: the rate is measured over 6 s. Multiple PSTAB glitches can be included in a single time window and it is impossible to know how many. As a result, this channel cannot be used to count the exact number of glitches. It will only provide a lower limit on the number of glitches.

Important #4: omicron only processes the data when the flag V1:DQ_META_NOMINAL_LOCK is active. The PSTAB glitch rate channel is set to -1 when the ITF is not locked.