Looking for the latest In-Lock Sus Charge files i find that last ones were made on Jan 7th and already alogged 82163 .
cdsws25: ls /opt/rtcds/userapps/release/sus/common/scripts/quad/InLockChargeMeasurements/rec_LHO -lt | head -n 6
total 527
-rw-r--r-- 1 test_user controls 160 Jan 7 07:58 ETMX_12_Hz_1420300733.txt
-rw-r--r-- 1 test_user controls 160 Jan 7 07:50 ETMY_12_Hz_1420300262.txt
-rw-r--r-- 1 test_user controls 160 Jan 7 07:50 ITMY_15_Hz_1420300244.txt
-rw-r--r-- 1 test_user controls 160 Jan 7 07:50 ITMX_13_Hz_1420300243.txt
-rw-r--r-- 1 test_user controls 160 Dec 17 07:58 ETMX_12_Hz_1418486333.txt
Since I thought I remember us being locked this past Tuesday morning I checked to see if the SUS_Charge Guardian ran and it looks like it didn't run, but we were actually locked?
I don't see a reason why it wouldn't have run. It looks like since the h1guardian1 machine reboot ont he 14th it hasn't run. Looking at the code it wait for exactly 07:45:00 PT. Maybe it missed that exact second for some reason? That said, the EXECTIME channel for that node shows 0, so I would expect it to catch that second. I've reran SUS_CHARGE through INIT and we'll see if it does it next Tuesday. If not, perhaps we change this to have a >1 second buffer on start time.