Reason for change
The new version (v5r12p1, as opposed to v5r10p0, previously running in L1Proc 1.71) contains minor changes described in details 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 dataMonitoring/AlarmCfg for v5r12p1)
v5r12p1
- update TEM_BUG alarm name in fastmon_errors_alarms.xml (GDQMQ-304)
v5r12p0
- Removed some commented lines in calpeds_eor_alarms_exceptions.xml.
- A few obsolete exceptions removed from calhist_alarms_exceptions.xml.
- Exceptions on channel 848 for CalXAdcPedPedRMSDifference_LEX8_TH1 and CalXAdcPedPedRMSDifference_LEX1_TH1 removed in
calpeds_eor_alarms_exceptions.xml---after the new hardware configuration has been loaded on the LAT. - Changed conditions on the min number of events in the following alarms:
- ReconAcdGlobalPosONLYMatchedTracks_RibbonXOriented_TH1_XYZ_1 -> 3000
- ReconAcdGlobalPosONLYMatchedTracks_RibbonYOriented_TH1_XYZ_0 -> 5000
- ReconAcdGlobalPosNotMatchedTracks_RibbonYOriented_TH1_XYZ_1 -> 10000
- ReconAcdGlobalPosNotMatchedTracks_RibbonXOriented_TH1_XYZ_0 -> 10000
(after a bug fix in the Recon).
v5r11p0
- Add an alarm file for the errors from ft2Verify (LONE-137)