Reason for change
As more runs are processed we need to fine tune the settings (namely update the dataMonitoring/AlarmsCfg package) to prevent the alarms from firing due to non issues. The proposed package version is dataMonitoring/AlarmsCfg v2r3p4v2r5p3, as opposed to the v2r2p1 running originally in L1Proc 1.61original v2r4p2.
The detailed description of the changes is in the last section.
...
CCB Jira
Details
FastMon end of run:
- Limits on the number of triggers per tower (for all trigger primitives) made a bit wider as non-uniformities among centre vs. corner towers were causing warnings.
- Limits on the average number of TkrHits per tower changed as the fluctuations among different orbits turned out to be bigger than anticipated, based on the very first runs. Alarm on the RMS of the same plot removed as the distribution has an exponential shape and it wasn't really adding any more information.
- Exception added in order not to report the noisy strip in tower 3 as an issue.
Digi end of run:
- Limits updated according to the changes in FastMon end of run (they all refer to quantities that are available both in FastMon and in Digi, so that they should have the same alarms with the same limits).
Digi trending:
- Upper warning limit on the quantity OutF_Normalized_TkrHits_TowerPlane moved a bit as it was really too tight.
Recon end of run:
- Got rid of the alarms on four vertex-related quantities as the corresponding distributions were too wide and dependent on the pointing vs. scanning mode to put sensible limits.
- Minor adjustments of the limits on the following quantities: SuspCalHi_Highest0_EnergyDistribution_TH1 (leftmost_edge), ReconAcdPhaMips_PMTA_TH1_AcdTile (x_average and x_rms), ReconAcdGlobalPosNotMatchedTracks_RibbonYOriented_TH1_XYZ (gauss_rms)
Merit trending:
...
Here is a cut and paste of all the relevant release notes.
- v2r5p3 ***
- Alarm limits on the Tracker (and in particular on Hiro's quantities) updated.
+ The spikes_and_holes algorithm on the GTFE occupancy in fastmon eor
is not allowed to produce errors anymore (only warnings).
+ Alarms on tower hit and trigger efficiency re-enabled. Lower limits
are 0.98 and 0.90 respectively. An error is issued upon limit
violations.
- Relevant jira(s): GDQMQ-227
- v2r5p2 ***
- Lower limits on the source event rate (merit eor) set to zero, as we were
having alarms occasionally firing.
- Relevant jira(s): GDQMQ-235
- v2r5p1 ***
- Alarms on the quantity ReconAcdPhaMips_PMT*TH1_AcdTile* in recon eor
removed as the corresponding plots are undergoing a revision and redefinition
process after some changes in GR.
- Relevant jira(s): GDQMQ-228
- v2r5p0 ***
- Exception in fastmon eor on the noisy strip of tower 3 (which has been
masked) removed.
- Relevant jira(s): GDQMQ-225