Reason for change

GlastRelease-17-35-24-lp28 implements the transition from FSW B1-1-3 to FSW B3-0-0. The 2 main reasons for change are:

• moving on to B3-0-0 represents a necessary step in the transition to rhel5, because it's the first FSW build supported with rhel5/gcc4.1
• during verification, we discovered a problem with the ground-computed versions of the MIP/HIP filters which was triggered by the activation of diagnostics on Oct 15, 2009
  • this is the full explanation from JJ: "the code being run in the offline is from B1-1-3, I believe the original build we launched with. This code predates the enabling of the diagnostic information in the data. The policy in this version of the code (package EDS, routine EBF_dirCompose) was to mark as in error any discrepancy between what was asked for and what was received in the data. Since the offline code did not indicate that diagnostic was requested and diagnostic data was found, both the HIP and MIP filters rejected the events based on this mismatch. Another inconsistency in the FSW code is that the GAMMA filter does not check for directory failures. This is really a mistake. (We have never seen a failure, so, so far it is a mistake without consequences; probably we it was not detected.)". (this last bit the reason why we don't see the same problem with the GAMMA filter)
  • incidentally, this inconsistency is the root cause of the problem we observed 2 years ago with the OBF variables for the HIP filter and lead us to the reprocessing of 6 months of GCR data
  • B3-0-0 is functionally identical to what we are running now on the LAT (B2-3-2) and solves the problem with the HIP filter. Therefore, there is a consensus towards switching L1Proc to B3-0-0 even before the FSW is updated.

Test Procedure

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

Rollback procedure

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

CCB Jira

SSC-321@JIRA

Details

GlastRelease-17-35-24-lp28

• there are a few differences between 17-35-24-lp28 and 17-35-24-lp22
• we ran systests comparing 17-35-24-lp28 to 17-35-24-lp22 and they agree
• the full list of changes for 17-35-24-lp28 is the following:
  • OnboardFilter-04-16-04-lp02: First tag supporting B3-0-0; adjust some include statements for compilation against CMT-style obf; patch cmt build to omit B3-0-0; for obf B3-0-0-gl1; fix typo for builds against obf B1-1-3
  • OnboardFilterTds-00-11-03: First tag supporting B3-0-0; Johann's patches for gcc41; for obf B3-0-0-gl1; fix typo for builds against obf B1-1-3
  • SConsFiles-00-22-00: new obf externals and enhancements in processExternals to propagate information about them; bug fix in allExternals affecting obf on Windows; add rhel5 gaudi debug into allExternals; add entry for obf B3-0-0-gl1
  • containerSettings-00-03-00-rp05: move to OBF B3-0-0-gl1; pick up mods to package.scons for OBF

Complete set of tags for L1Proc 3.4

GlastRelease (sim/recon): GlastRelease-17-35-24-lp28

ScienceTools (Level 2): ScienceTools-09-27-01

svac/L1Pipeline: L1Pipeline-03-04-00

calibGenTKR: calibGenTKR-04-08-01
calibTkrUtil: calibTkrUtil-02-09-06-gr02
fitsGen: fitsGen-06-03-00

dataMonitoring/AlarmsCfg: AlarmsCfg-06-00-05
dataMonitoring/Common: Common-06-11-04
dataMonitoring/DigiReconCalMeritCfg: DigiReconCalMeritCfg-01-20-02
dataMonitoring/FastMon: FastMon-05-02-01
dataMonitoring/FastMonCfg: FastMonCfg-02-02-01
datMonitoring/IGRF: IGRF-02-01-00

svac/Monitor: Monitor-02-00-01
svac/EngineeringModelRoot: EngineeringModelRoot-05-00-00
svac/TestReport: TestReport-12-00-00
svac/findGaps: findGaps-02-02-00

users/richard/pipelineDatasets: pipelineDatasets-01-00-00
ft2Util: ft2Util-02-00-03

evtClassDefs: evtClassDefs-00-19-04
GPLtools: GPLtools-02-00-00-wf02

ROOT: ROOT v5.26.00a-gl6