Reason for change
The new version (AlarmsCfg-05-20-01, as opposed to AlarmsCfg-05-19-04) includes some limits to take into account the noisy channel 2414, and the unexpected reboot to FSW 2.0.2, after to EPU0 reboot.
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 (release notes for dataMonitoring/AlarmCfg for AlarmsCfg-05-20-01)
AlarmsCfg-05-20-01 02-Oct-2009 bregeon Add temporary alarms because of noisy cal channel 2414
- Add exceptions for channel 2414 for calPedsAnalyzer:
CalXAdcPedRMS_LEX1_TH1 y_values
CalXAdcPedRMS_LEX8_TH1 y_values - Add exceptions for Tower 12 b/C of channel 2414 for digi and fastmon eor:
CalX_NHit_TH1_Tower_ x_average and x_rms
CalLogEndRangeHitCounter_Range*_TH2_Tower_12 spikes_and_holes - Change back lkower limits on digi trending Mean_CompressionLevel changed from
8.0, 8.0 to 7.0, 7.8 to accommodate with the reboot to the B2-0-2
AlarmsCfg-05-20-00 30-Sep-2009 lbaldini Added alarms on the CAL hitmaps.
- Added alarms on the CAL hitmaps to identify possible spikes and/or holes,
along the lines of what we already have for the tracker.
Specifically alarms ("empty_bins" and "spikes_and_holes") have been added,
with reasobale settings, on:
CalLogEndRangeHitCounter_Range0_TH2_Tower_*
CalLogEndRangeHitCounter_Range1_TH2_Tower_*
CalLogEndRangeHitCounter_Range2_TH2_Tower_*
CalLogEndRangeHitCounter_Range3_TH2_Tower_*
See also http://www-glast.stanford.edu/protected/mail/datamon/3435.html and
the relative thread.
AlarmsCfg-05-19-05 28-Sep-2009 lbaldini Minor limit change for ACD tile 73.
- Upper warning limit for AcdPedPedMeanDeviation_PMTB_TH1 (y_value) changed
from 8 to 12. This is temporary change that will be reverted as soon as we
have updated the claibration constants.
- Relevant jira(s): GDM-321
AlarmsCfg-05-19-04 24-Sep-2009 monzani added two checks to verify
- Added two more error conditions to the verify alarm file: checking the FSW
compression level (GDQMQ-320), checking that periodic evts never have the TEM bug (GDQMQ-319)