Patrick, Dave
The conlog reporting of frequently changing EPICS channels has discovered several code issues in the past week. Conlog reports hourly those channels which have logged 500 or more changes in the previous hour. I have written a python script to concatinate 24 hourly reports into a daily report, which I'll post in the alog.
Below is the log from yesterday (Monday 11/17). We discovered a guardian node which was setting the end station SUS L1_LOCK_L filters RSET (clearing history) at 16Hz. This was fixed between 1pm and 2pm.
The per-second number is calculated as total/(hours-active * 3600). Numbers in the 16 range are most probably front end or guardian related, higher than 16 most probably Beckhoff or scripts.
11/17/2014 hs total per-sec
H1:SUS-ETMX_L1_LOCK_L_RSET 14 751286 14.9
H1:SUS-ETMY_L1_LOCK_L_RSET 14 751286 14.9
H1:ALS-C_COMM_VCO_TUNEOFS 02 90021 12.5
H1:ALS-Y_FIBR_LOCK_TEMPERATURECONTROLS_ON 06 62062 2.9
H1:ALS-Y_CAM_ITM_PIT_POS 24 58548 0.7
H1:ALS-Y_CAM_ITM_YAW_POS 24 58548 0.7
H1:ALS-Y_CAM_ITM_SUM 24 58539 0.7
H1:GRD-ALS_YARM_USERMSG 05 16658 0.9
H1:ALS-X_REFL_SERVO_IN1EN 05 11208 0.6
H1:SUS-IM4_M1_OPTICALIGN_Y_OFFSET 03 6052 0.6
H1:SUS-IM4_M1_OPTICALIGN_P_OFFSET 02 3136 0.4
H1:GRD-ALS_XARM_STATUS 02 3082 0.4
H1:GRD-ALS_COMM_USERMSG 03 1781 0.2
H1:SYS-MOTION_C_PICO_A_CURRENT_DRIVE 02 1516 0.2
H1:GRD-ALS_XARM_TARGET_S 01 632 0.2
H1:GRD-ALS_XARM_STATE_S 01 550 0.2
H1:SUS-PRM_M1_OPTICALIGN_P_OFFSET 01 504 0.1
Some of the GRD channel changes are likely reflective of actual changes in the system. It's not clear to me that conlog should be monitoring the following guardian channels:
None of those channels are set by users, so they may change as fast as the system changes.