Reason for change
The main reason for change is that a change in the Recon_ReconAcdPhaMipsCorrectedAngle_PMTA_TH1_AcdTile plot is causing a lot of spurious alarms to fire. Those alarms have been moved to another quantity (Recon_ReconAcdPhaMipsCorrectedAngle_PMTA_Zoom_TH1_AcdTile), which is more suitable. The proposed package version is dataMonitoring/AlarmsCfg v4r3p0, as opposed to the original v4r0p0.
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
Here is a cut and paste of all the relevant release notes.
v4r3p0
- Alarms on the MIP peak of the ACD tiles moved to the zoomed plot (Recon_ReconAcdPhaMipsCorrectedAngle_PMTA_Zoom_TH1_AcdTile), as the not-zoomed one (Recon_ReconAcdPhaMipsCorrectedAngle_PMTA_TH1_AcdTile) became log-log and is no more suitable for that.
v4r2p0
- All the useless <parameter name="max" value="9999"/> removed from the digi_eor_alarms.xml file.
- All the useless <parameter name="max" value="9999"/> removed from the fastmon_eor_alarms.xml file.
- All the useless <parameter name="max" value="9999"/> removed from the recon_eor_alarms.xml file.
v4r1p0
- Added conditions on the number of entries in recon_eor to prevent the alarms from being evaluated when there's not enough statistics.