You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Reason for change

We have fine tuned some alarm limits after the first runs taken with the new configuration (Moot key 2450). The proposed version of the dataMonitoring/AlarmsCfg package is v5r3p1, as opposed to v4r10p2, previously running in L1Proc 1.68.

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

SSC-1@JIRA

Details

  • v5r3p1 *
  • Disabled all the new alarms on the timing in fastmon and digi eor, since they still need tuning and reference histograms.
  • v5r3p0 *
  • Some more fine tuning of the alarm limits based on the first data taken in the new configuration (Moot key 2450).
  • Limits on AcdPedPedRMSDifference* in acdpedsanalyzer relaxed.
  • Limits on RPM_GainMeanDifference_TH1 in calgainsanalyzer relaxed.
  • One exception removed from the trackermon (hot strip masked).
  • Added exception for digi trend, Mean_TkrHitsPerEvt_TowerPlane and OutF_Normalized_TkrHits_TowerPlane, tower 0 GTFE 14.
  • Limits on calpedsanalyzer CalXAdcPedPedRMSDifference_LEX1_TH1 relaxed.
  • Limits on CalX_Total_NHit_TH1 (low_high_ratio) in digi and fastmon eor relaxed a little bit.
  • Limits on digi eor TkrPlanesHit_TH1_Tower put separately on tower 0, for which we have a noisy strip deforming the distribution.
  • v5r2p1 *
  • Some limits on the acd peds relaxed.
  • Relevant jira(s): GDQMQ-279.
  • v5r2p0 *
  • All the y-values alarms on digi and fastmon eor updated to the new trigger window width (14 ticks instead of 12).
  • Limits relaxed on some of the timing quantities in digi and fastmon eor.
  • v5r1p0 *
  • Channel 1983 added as an exception on the the LEX1 and LEX8 pedestal rms values (cal_eor).
  • Warning max for CalXAdcPedRMS_HEX8_TH1 (y_values) in calpeds_eor moved from 3.7 to 4.0 (the margin wasn't large enough).
  • Warning min for CalXAdcPedPedRMSDifference_HEX8_TH1 (y_values) in calpeds_eor moved from 0.25 to 0.15.
  • Warning min for CalXAdcPedPedRMSDifference_LEX8_TH1 (y_values) in calpeds_eor moved from -1.0 to -1.5.
  • Warning min for RPM_RMS_TH1 (y_values) in calgains_eor moved from 0.15 to 0.10.
  • Relevant jira(s): GDQMQ-279
  • v5r0p1 *
  • Configuration file for the error logger on the verify module implemented.
  • Relevant jira(s): GDQMQ-250
  • v5r0p0 *
  • Implement alarms on timing quantities, mostly Condition Arrival Times, in both fastmon and digi. Settings will have to be tuned when the new timing configuration in uploaded.
  • First use of the reference histograms for alarms
  • Add an alarm on CondSummaryWord using the reference histogram, as a test
  • Relevant jira(s): GDQMQ-271
  • v4r11p0 *
  • Configuration file for the pErrorLogger on the FastMon fully implemented.
  • Relevant jira(s): GDQMQ-250
  • No labels