Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

Reason for change

The updates in the alarm handler limits respond to changes in the hardware configuration as well as in the ground software. Some minor fine tuning based on the experience with the new data is also includedmain 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 v3r0p1v4r3p0, as opposed to the original v2r4p2v4r0p0.
The detailed description of the changes is in the last section.

...

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

SSC-114@JIRA123@JIRA

Details

Here is a cut and paste of all the relevant release notes.

v3r0p1

...

v4r3p0
  • Alarms on the

...

v3r0p0
  • Configuration files for the alarms on the CAL and ACD calibration quantities added (not yet running in the pipeline).
  • Relevant jira(s): GDQMQ-216
v2r5p3
  • Alarm limits on the Tracker (and in particular on Hiro's quantities) updated.
  • The spikes_and_holes algorithm on the GTFE occupancy in fastmon eor is not allowed to produce errors anymore (only warnings).
  • Alarms on tower hit and trigger efficiency re-enabled. Lower limits are 0.98 and 0.90 respectively. An error is issued upon limit violations.
  • Relevant jira(s): GDQMQ-227
v2r5p2
  • Lower limits on the source event rate (merit eor) set to zero, as we were having alarms occasionally firing.
  • Relevant jira(s): GDQMQ-235
v2r5p1
  • Alarms on the quantity ReconAcdPhaMips_PMT*TH1_AcdTile* in recon eor removed as the corresponding plots are undergoing a revision and redefinition process after some changes in GR.
  • Relevant jira(s): GDQMQ-228
v2r5p0
  • Exception in fastmon eor on the noisy strip of tower 3 (which has been masked) removed.
  • 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.

...