Reason for change
The new version (AlarmsCfg-05-23-01, as opposed to AlarmsCfg-05-22-05) is mainly for putting in the new alarm limits on the merit normalized rates after the new normalization factors have been put into production. There are a few minor more minor changes, mainly in order to protect alarms against low statistics, which are detailed below.
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-23-01)
- AlarmsCfg-05-23-01 04-Feb-2010 lbaldini Minor change.
- Alarm on the digi eor GPSInLock_TH1 protected against low statistics (condition on min entrioes changed from 500 to 1250).
- AlarmsCfg-05-23-00 04-Feb-2010 lbaldini Alarms on the normalized rates retuned.
- Retuned the alarms on the normalized rates after the new normalization factors have been put in production.
- Relevant Jira(s): GDQMQ-317.
- AlarmsCfg-05-22-06 04-Feb-2010 lbaldini Minor changes.
- Condition on the minimum number of entries changed for CondArrCNO_CalLoOpensWindow_TH1 (reference_histogram algorithm, both digi and fastmon end-of-run) changed from 1000 to 2500.
- Upper warning limit for the alarm on the digi trending quantity Rate_NTkrHits_TowerPlane changed from 2.5 to 2.75. See the thread https://www-glast.stanford.edu/protected/mail/datamon/3560.html for more details.