Reason for change
This is just ordinary maintenance of the alarm limits. We require to put AlarmsCfg-06-01-02 in production.
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 (relese notes for AlarmsCfg-06-01-02)
- Calorimeter channels 1692 pushed in the group of the guys with higher limits (30/30) for the calpeds eor alarm on CalXAdcPedRMS_LEX8_TH1, algorithm y-values.
- Limits on the GPSInLock_TH1, x-average alarm loosened a little bit.
- Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/10008.html