Reports until 17:06, Wednesday 02 September 2015
H1 INJ (CAL)
jeffrey.kissel@LIGO.ORG - posted 17:06, Wednesday 02 September 2015 (21154)
H1 CAL-CS Hardware Injection Channels That are Now Not Monitored by the Settings Definition File (SDF) System
J. Kissel, C. Gray, B. Weaver

Every once and a while while Betsy and Corey are "beating the streets" to find out why there are SDF differences between the settings definition file ("safe.snap") and the current value of the EPICs record for every front-end model, they ask me about differences in the CAL-CS model. Often times, including this time, there are hardware injection channels that show up, simply because the INJ infrastructure lives in the CAL-CS model. Over time, I've been changing these channels to NOT MONITORED, because they all appear to be EPICs records that are constantly updated with information about the last injection, or some recent GRB alert, etc. I attach a screenshot of this list as it currently stands.

For convenience I type the list here and give it the 'ol college try to explain them:
H1:CAL-INJ_EXTTRIG_ALERT_QUERY_TIME < a numeric GPS time that changes any time when TINJ (the hardware injection scheduling software) queries new external alert occurs
H1:CAL-INJ_EXTTRIG_ALERT_TIME       < a numeric GPS time that changes whenever there is a new external alert
H1:CAL-INJ_EXTTRIG_ALERT_SOURCE     < a string record from what telescope the external alert came (SWIFT, FERMI, etc.) that changes whenever there is a new alert
H1:CAL-INJ_EXTTRIG_ALERT_ID         < a unique alpha-numeric record for each record that changes whenever there is a new alert (e.g. E156669)
H1:CAL-INJ_EXTTRIG_ALERT_TYPE       < a string record indicating the claimed astrophysical source of the alert (e.g. GRB) that changes whenever there is a new alert
H1:CAL-INJ_TINJ_ENDED               < a numeric GPS time when the last hardware injecton ended
H1:CAL-INJ_OUTCOME                  < a numeric code labeling the level of success of the last hardware injection
H1:CAL-INJ_TINJ_START               < a numeric GPS time when the last hardware injection started
H1:CAL-INJ_TINJ_STATE               < a status vector of TINJ
H1:CAL-INJ_TINJ_TYPE                < a string indicating the type of last injection
As I understand it, all of the EPICs records are essentially readbacks, and therefore should not be monitored by the SDF system.

You can peruse T1400349 is you'd like more details on TINJ and the hardware injection infrastructure. T1500197 is the document for the external alert system.
Images attached to this report