Reason for change
We request to put AlarmsCfg-06-04-01 in production. The new tag implements a few tweaks to the alarm limits, 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
Details (release notes for AlarmsCfg-06-04-01)
A few tweaks in the alarms on the GPS 20 MHz deviation. Essenatially for digi_eor_alarms.xml, digi_trend_alarms.xml and fastmon_eor_alarms.xm the basic diff is
< <warning_limits min="-196.0" max="-165.0"/>
< <error_limits min="-200.0" max="-150.0"/>
---
> <warning_limits min="-210.0" max="-180.0"/>
> <error_limits min="-230.0" max="-160.0"/>
Relevant thread(s):
A lot of emails circulated on the datamon list over the last few weeks, see, e.g.,
https://www-glast.stanford.edu/protected/mail/datamon/13535.html