Reason for change
The proposed package version is dataMonitoring/AlarmsCfg v2r5p3, as opposed to the original v2r4p2.
The detailed description of the changes is in the last section.
Test Procedure
We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.
Rollback procedure
The package can be rolled back to the previous version by flipping a soft link. Also note that the package is completely independent from any other package running in the pipeline and will not cause a version change of L1Proc.
CCB Jira
Details
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