Blog from March, 2010

Request to update alarm settings in L1Proc 1.83
Luca Baldini posted on Mar 13, 2010

Reason for change

The new version (AlarmsCfg-05-24-04, as opposed to AlarmsCfg-05-23-06) features a few limit changes on the merit trend normalized rates (due to the fact that we changed the evaluation of the associated errors, see GDQMQ-340).

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

Details (release notes for dataMonitoring/AlarmCfg for AlarmsCfg-05-24-4)

  • AlarmsCfg-05-24-04 14-Mar-2010 pesce Some changes on the limits for the normalized rates.
    • Warning limit for merit trend OutF_NormRateEvtsBeforeFilters changed from 1.15 to 1.17 and
      for OutF_NormRateDiffuseEvts changed from 1.75 to 1.85.
    • Relevant Jira: GDQMQ-341
  • AlarmsCfg-05-24-03 12-Mar-2010 pesce Some changes on the limits for the normalized rates.
    • Warning limit for merit trend OutF_NormRateEvtsBeforeFilters from 0.80 to 0.75.
    • Relevant Jira: GDQMQ-341
  • AlarmsCfg-05-24-02 11-Mar-2010 pesce Some changes on the limits for the normalized rates.
    • Warning limit for merit trend OutF_NormRateSourceEvts changed from 1.65 to 1.75.
    • Relevant Jira: GDQMQ-341
  • AlarmsCfg-05-24-01 10-Mar-2010 pesce Some changes on the limits for the normalized rates.
    • Warning limit for merit trend OutF_NormRateMeritTriggerEngine (trigger engine 7) changed from 0.80 to 0.75 and warning limit for merit trend OutF_NormRateDiffuseEvts changed from 1.65 to 1.75.
    • Relevant Jira: GDQMQ-341
  • AlarmsCfg-05-24-00 10-Mar-2010 lbaldini Some changes on the limits for the normalized rates.
    • High warning limit for merit trend OutF_NormRateSourceEvts and OutF_NormRateDiffuseEvts changed from 1.5 to 1.65.
    • Relevant Jira(s): GDQMQ-341
  • AlarmsCfg-05-23-07 05-Mar-2010 lbaldini Improved protection against low statistics.
    • Condition on the min number of entries for Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn and Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn changed from 200 to 500 (a typical value for a normal run being ~5000).
Request to Deploy ASP v3r2p0
James Chiang posted on Mar 12, 2010

Reasons for Change

  • Include updates for SCons builds to run in pipeline.
  • Various minor fixes (see details below)

Test Procedure

CMT and SCons versions both tested in dev on data in /ASP/TestSims2.

Rollback Procedure

Revert to ASP v3r1p2

CCB Jira

SSC-249@JIRA

Details

  • ASP v3r2p0
    • AspHealPix v0r0p4*
      • SConscript changes
    • AspLauncher v1r4p3*
      • adjust offset for stream ids for weekly monitoring task so that web interface can find the data (ASP-64@JIRA)
    • AspPolicy v0r6p1
    • BayesianBlocks v3r0p0*
      • Exposure weighting bug-fix (not used in ASP); switch to ML cost function
    • asp_pgwave v1r10p4
    • drpMonitoring v1r7p7
    • grbASP v4r9p1*
      • SConscript changes
      • set extraction radius for second pass (*_LAT_2.fits) to 180 to avoid multiple acceptance cones
    • pyASP v3r6p4*
      • SConscript changes
    • asp_healpix v2r2p4*
      • SConscript changes
    • asp_skymaps v1r13p4*
      • SConscript changes
    • asp_pointlike v6r14p2*
      • SConscript changes
Request to deploy L1Proc 1.83
Unknown User (wbfocke) posted on Mar 08, 2010

Reason for change

To update monitoring code.

Test Procedure

We have processed runs in the DEV pipeline with this version of L1Proc.

Rollback procedure

We can easily switch back to the previous version of L1Proc.

CCB Jira

SSC-247@JIRA

Details

L1Pipeline: L1Pipeline v1r83

Complete set of tags for L1Proc 1.83
Code Versions
GlastRelease (sim/recon): GlastRelease-v15r47p12gr10
ScienceTools (Level 2) : v9r15p5
Science Ops (task defs, scripts):
Level 1 pipeline code and applications running in L1:

svac/L1Pipeline: L1Pipeline v1r83

  • Switch logs back to u52.
  • Remove requirement for rhel40 from jobs that run isoc code.
  • Add 2d orbit plot.
  • Reserve big scratch for calHist.
  • Add baseVersion task variable.

calibTkrUtil v2r9p1
calibGenTKR v4r5

dataMonitoring/AlarmsCfg: AlarmsCfg-05-23-07

  • AlarmsCfg-05-23-07 05-Mar-2010 lbaldini Improved protection against low statistics.
    Condition on the min number of entries for Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn and Lac_Thresholds_FaceNeg_TH1_TowerCalLayerCalColumn changed from 200 to 500 (a typical value for a normal run being ~5000).

dataMonitoring/FastMonCfg: FastMonCfg-02-01-01

dataMonitoring/DigiReconCalMeritCfg: DigiReconCalMeritCfg-01-04-06

dataMonitoring/Common: Common-06-07-01

dataMonitoring/FastMon: FastMon-05-01-01

dataMonitoring/IGRF: IGRF-02-01-00

  • IGRF-02-01-00 15-Feb-2010 lbaldini Bug fix for the 2k.1 issue.
    Markus updated and committed the IGRF code. It should now be fine until 2015 and deliver magnetic fields from a multipole expansion up to l=13 (was l=10). The update is documented in some more detail in GDQMQ-332.

svac/Monitor: Monitor-01-06-00

  • GDQMQ-340 Change the way the error on the normalized rates is calculated.

svac/EngineeringModelRoot: v4r4
svac/TestReport: TestReport-10-01-00

users/richard/pipelineDatasets: v0r6

ft2Util: v1r2p31

evtClassDefs v0r14

GPLtools: GPLtools-01-15-01-fo06

  • Improved retry of file copies.

Things that still need to be done.

Things that need to be checked before going to prod

Please write a comment if you actually check one of the items.

  • Take a look at the normalized rates.
  • Make sure we didn't screw up with the new IGRF.
Request to update alarm settings in L1Proc 1.82 (round 3)
Luca Baldini posted on Mar 02, 2010

Reason for change

The new version (AlarmsCfg-05-23-06, as opposed to AlarmsCfg-05-23-05) features a few minor limit changes and protections against low statistics (see details below).

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

Details (release notes for dataMonitoring/AlarmCfg for AlarmsCfg-05-23-05)

  • AlarmsCfg-05-23-06 19-Feb-2010 lbaldini Minor changes.
    • Lower warning limit changed from 0.85 to 0.80 for the two merit trend quantities OutF_NormRateEvtsBeforeCutsWithFswGAMMAFilter and OutF_NormRateEvtsBeforeFilters.
      See https://www-glast.stanford.edu/protected/mail/datamon/4118.html for more details about this change.
    • Condition on the minimum number of entries (1000) added on the x_average and x_rms algorithms for CondArrCNO_TKROpensWindow_TH1 (both digi and fastMon).