Blog from August, 2014

Request to update alarm settings in L1Proc 4.8
Luca Baldini posted on Aug 05, 2014

Reason for change

We request to put AlarmsCfg-06-04-00 in production. The new tag implements a few tweaks to the alarm limits, as detailed in the last section of this page.

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-383@JIRA

Details (release notes for AlarmsCfg-06-04-00)

  •  merit_trend OutF_NormRateMeritTriggerEngine (engine 7): raise the upper warning limit from 1.15 to 1.25
  •  merit_trendOutF_NormRateEvtsBeforeCuts: raise the upper warning limit from 1.15 to 1.20
  •  merit_trendOutF_NormRateEvtsBeforeCutsWithFswGAMMAFilter: raise the upper warning limit from 1.15 to 1.20
  •  Minimum number of entries for fastmon_eor CalLogEndRangeHitCounter_Range0_TH2_Tower_* changed from 1000000 to 750000.
  •  acdpeds_eor upper warning limit for AcdPedPedMeanDeviation_PMTB_TH1 (y_values) changed from 8 to 10.
  •  Added exceptions for calpeds_eor for channels 824: CalXAdcPedPedRMSDifference_HEX1_TH1, CalXAdcPedPedMeanDifference_HEX1_TH1 and CalXAdcPedPedMeanDifference_HEX8_TH1
  •  Added exceptions for calpeds_eor for channels 3060: CalXAdcPedPedMeanDifference_LEX8_TH1, CalXAdcPedPedRMSDifference_LEX8_TH1

Relevant thread(s):

https://www-glast.stanford.edu/protected/mail/datamon/12916.html
https://www-glast.stanford.edu/protected/mail/datamon/12589.html