edmond.merilh@LIGO.ORG - posted 12:22, Friday 27 January 2017 - last comment - 13:50, Friday 27 January 2017(33681)
ETMY CDS Overview
at about 20:18 ETMY IOP/SUS CDS Overview was showing some timing and ADC errors (only to name the ones that I could quickly identify) that lasted for only a few seconds and then reverted back to 'Green" status. I will notify Dave Barker and I'm flagging Detchar as we are in Observing mode. This did not upset the Intent bit and there were no other alerts other than the visual one that I happened to notice.
This is another occurance of the ongoing end-station-sus adc and timing overruns we see on these faster computers. The glitch rate is low, and are cleared on the following minute, so most go un-noticed. I just did a recheck on the rates, and they are at around 10 per day for both ETMX and ETMY, occuring randomly in time.
If you want to trend these occurances, I have some scripts which do this. The data is in the STATE_WORD channel, which also includes higher order bits which tend to dominate the signal. So I have a script to just look at the TIMING and ADC bits.
in /ligo/home/david.barker/daq/ there are the scripts
get_iopsusey_stateword_mintrends.bsh, get_iopsusex_stateword_mintrends.bsh and mask_out_stateword_tim_adc_bit.py
Running the first two will get 3 days of minute trends for these channels and write them to a data file, running the python script (with the data file as an argument) lists the local times of each event.