Reason for change
We request to put AlarmsCfg-06-05-00 in production. The new tag implements a few changes to the alarm limits on the 20MHz clock frequency, as detailed in the last section of this page.
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
add link to CCB JIRA request (not yet created)
Details (release notes for AlarmsCfg-06-05-00)
Relaxing the alarms limits on the 20MHz clock frequency deviation.
In digi_eor_alarms.xml and fastmon_eor_alarms.xml: upper limits for x_average of Tick20MHzDeviation_TH1 raised to -150(warning) and -100(error)
In digi_trend_alarms.xml: upper limits for Mean_Tick20MHzDeviation raised to -150(warning) and -100(error)
Relevant thread(s):
https://www-glast.stanford.edu/protected/mail/datamon/13785.html