Reason for change
The new version (AlarmsCfg-05-24-03, as opposed to AlarmsCfg-05-23-06) features a few limit changes on the merit trend normalized rates (due to the fact that we changed the evaluation of the associated errors, see GDQMQ-340).
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 (release notes for dataMonitoring/AlarmCfg for AlarmsCfg-05-24-3)
- AlarmsCfg-05-24-03 12-Mar-2010 pesce Some changes on the limits for the normalized rates.
- Warning limit for merit trend OutF_NormRateEvtsBeforeFilters from 0.80 to 0.75.
- Relevant Jira: GDQMQ-341
- AlarmsCfg-05-24-02 11-Mar-2010 pesce Some changes on the limits for the normalized rates.
- Warning limit for merit trend OutF_NormRateSourceEvts changed from 1.65 to 1.75.
- Relevant Jira: GDQMQ-341
- AlarmsCfg-05-24-01 10-Mar-2010 pesce Some changes on the limits for the normalized rates.
- Warning limit for merit trend OutF_NormRateMeritTriggerEngine (trigger engine 7) changed from 0.80 to 0.75 and warning limit for merit trend OutF_NormRateDiffuseEvts changed from 1.65 to 1.75.
- Relevant Jira: GDQMQ-341
- AlarmsCfg-05-24-00 10-Mar-2010 lbaldini Some changes on the limits for the normalized rates.
- High warning limit for merit trend OutF_NormRateSourceEvts and OutF_NormRateDiffuseEvts changed from 1.5 to 1.65.
- Relevant Jira(s): GDQMQ-341
- AlarmsCfg-05-23-07 05-Mar-2010 lbaldini Improved protection against low statistics.
- Condition on the min number of entries for Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn and Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn changed from 200 to 500 (a typical value for a normal run being ~5000).