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 sectionWe found a typo in one of the xml configuration files for the alarms handler. The effect was that one of the alarms was applied twice on the PMT A of the ACD tiles and never on the PMT B. The new release of dataMonitoring/AlarmsCfg (v4r3p4 as opposed to v4r3p0) includes a fix for this, along with a few other minor improvements (details in the last section).
Test Procedure
We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.
...
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.
v4r3p4
- fastmon_trend_alarms_exceptions.xml and trackermon_trend_alarms_exceptions.xml updated to include the exceptions on the known noisy strips.
v4r3p3
- Lower warning limits on Mean_ToT_con*_Trunc_1_249_TowerPlane in digi_trend changed from 25.0 to 8.0. The idea is that a single noisy strip used to trigger this alarm with the old limits, generating confusion.
...
- This alarm remains to notify serious issues with the TOT measurement.
- High warning limit on AcdPedRMS_PMTA_TH1 in acdpeds_eor.xml changed from 6.0 to 7.0. Not really important as this task is not running in the pipeline, yet.
v4r3p2
- Added alarms on ReconAcdPhaMipsCorrectedAngle_PMTB_TH1_AcdTile_* for the ribbons in the recon_eor.
- Relevant jira(s): GDQMQ-219
v4r3p1
- Wrong plot name in recon_eor_alarms.xml fixed (an alarm was applied on ReconAcdPhaMipsCorrectedAngle_PMTA_Zoom_TH1_AcdTile_* twice and it was not applied on ReconAcdPhaMipsCorrectedAngle_PMTB_Zoom_TH1_AcdTile_*).
- Fitting subrange for ReconAcdPhaMipsCorrectedAngle_PMT*Zoom_TH1_AcdTile* in recon_eor_alarms.xml changed from 0.0-1.5 to 0.2-1.4.
- Upper warning limit on ReconAcdPhaMipsCorrectedAngle_PMTA_Zoom_TH1_AcdTile_* in recon_eor_alarms.xml changed from 1.5 to 1.2.
- Upper warning limit on Lac_Thresholds_Face*TH1_TowerCalLayerCalColumn* in recon_eor_alarms.xml changed from 0.55 to 0.50.
- recon_eor_alarms_postprocess.xml and recon_eor_alarms_postprocess_debug.xml updated according to the new set of alarms.
- Relevant jira(s): GDQMQ-248