Jeff B, Dave:

I have re-written the check_dust_monitors_are_working script to make the output more readable.

The script defaults to checking the past 12 hours. Additionally it can take a second argument to check for N hours ending M hours ago, where N and M are the two arguments given. For each dust monitor, it internally checks both 0.5um and 0.3um dust counts. If both have shown no variation over the time period provided (i.e. both have zero standard deviation) then a warning message is printed, otherwise an ok message is printed.

Here is a "all is good" example for the past 12 hours:

check_dust_monitors_are_working      
 
Checking dust monitors for possible problems over a period of 12 hours ending 0 hours ago...
 
    H1:PEM-CS_DUST_LVEA2       OK
    H1:PEM-CS_DUST_LVEA3       OK
    H1:PEM-CS_DUST_LVEA4       OK
    H1:PEM-CS_DUST_LVEA5       OK
    H1:PEM-CS_DUST_LVEA6       OK
    H1:PEM-CS_DUST_LVEA10     OK
    H1:PEM-CS_DUST_LVEA30     OK
    H1:PEM-CS_DUST_PSL101     OK
    H1:PEM-CS_DUST_PSL102     OK
    H1:PEM-EX_DUST_VEA1        OK
    H1:PEM-EY_DUST_VEA1        OK
 
done
 

Here is an example with HAM6's monitor in error, prior to this morning's restart of the LEAV6‌ dust monitor:

check_dust_monitors_are_working 12 12
 
Checking dust monitors for possible problems over a period of 12 hours ending 12 hours ago...
 
    H1:PEM-CS_DUST_LVEA2       OK
    H1:PEM-CS_DUST_LVEA3       OK
    H1:PEM-CS_DUST_LVEA4       OK
    H1:PEM-CS_DUST_LVEA5       OK
    H1:PEM-CS_DUST_LVEA6       WARNING: dust counts did not change, please investigate
    H1:PEM-CS_DUST_LVEA10     OK
    H1:PEM-CS_DUST_LVEA30     OK
    H1:PEM-CS_DUST_PSL101     OK
    H1:PEM-CS_DUST_PSL102     OK
    H1:PEM-EX_DUST_VEA1        OK
    H1:PEM-EY_DUST_VEA1        OK
 
done