Reason for change
There is exactly one change in how we handle on exception violation for the bad TKR ladder in tower 3, layer 35 (the cvs tag is AlarmsCfg-06-00-07).
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-00-07)
- Status on violation changed from error to clean for the alarm exception on Number_layerOcc_TowerPlane (tower 3, layer 35) for tkrmon trend.
- Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/8338.html