-
Stephen A. Wood authored
1. If there are multiple ROCs with scalers (hardware, TI, FADC), then there will be multiple event 129s. In the case where analysis of these events is defered to the end of the analysis, all the event 129s will be analyzed as if a single event, resulting in one entry in the tree. 2. Scalers are read either when a given time interval has passed since the last scaler read (usually 2 seconds), or every time an event is tagged as a sync event. In the case of the "timed" reading of events, different ROCs with scalers are not guaranteed to read their scalers at the same event. But or sync event scaler reads, all ROCs read their scalers. This commit adds an option SetOnlyUseSyncEvents(Bool_t). If set, only scaler events triggered by the sync event will be analyzed.
Stephen A. Wood authored1. If there are multiple ROCs with scalers (hardware, TI, FADC), then there will be multiple event 129s. In the case where analysis of these events is defered to the end of the analysis, all the event 129s will be analyzed as if a single event, resulting in one entry in the tree. 2. Scalers are read either when a given time interval has passed since the last scaler read (usually 2 seconds), or every time an event is tagged as a sync event. In the case of the "timed" reading of events, different ROCs with scalers are not guaranteed to read their scalers at the same event. But or sync event scaler reads, all ROCs read their scalers. This commit adds an option SetOnlyUseSyncEvents(Bool_t). If set, only scaler events triggered by the sync event will be analyzed.