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
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
Reason for change
There is exactly one change in how we handle on exception violation for the bad TKR ladder in tower 3, layer 35 (the cvs tag is AlarmsCfg-06-00-07).
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
Details (relese notes for AlarmsCfg-06-00-07)
- Status on violation changed from error to clean for the alarm exception on Number_layerOcc_TowerPlane (tower 3, layer 35) for tkrmon trend.
- Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/8338.html
Reasons for Change
- Switch batch queues in GRB task to glastdataq to avoid cpu timeouts from occasionally long xrdcp execution.
- Query for FT1 instead of EXTENDEDFT1 in GRB_afterglow stream
- Improve upper limit calculation in DRP_monitoring
Test Procedure
Tested in dev on data in /ASP/TestSims2.
Rollback Procedure
Revert to ASP-06-00-00.
CCB Jira
Details
(modified packages only)
- pyASP-04-00-01
- use rhel5 version of FASTCopy.py from ISOC tools
- asp_pgwave-02-00-01
- restore EVENT_CLASS column after swapping with CONVERSION_TYPE for old pointfit in refinePositions.py
- throw exception rather than calling sys.exit (and stopping silently) if no candidate sources are found by pgwave
- drpMonitoring-02-00-02
- use more robust UL calculation in fitEnergyBand.py
- split makeDrpLcTables into two parts so that FASTCopy.py that relies on python 2.5 built on rhel5-32 won't conflict with import of cx_Oracle for x86_64 platforms.
- grbASP-05-03-00
- switch from EXTENDEDFT1 to FT1 in GRB_afterglow datacatalog query
- switch to glastdataq for all batch submissions to avoid problems with excessive cpu usage by xrdcp
Reason for change
This is just regular maintenance of the alarm limits, with a few minor tweaks (the cvs tag is AlarmsCfg-06-00-06).
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
Details (relese notes for AlarmsCfg-06-00-06)
- Limits on digi_eor_alarms GPSInLock_TH1 relaxed a little bit.
- Limits on calpeds_eor_alarms CalXAdcPedRMS_LEX8/LEX1_TH1 y_values increased a little to compensate for the slight increase in the noise baseline.
- Lower warning limit on digitrend OutF_Normalized_AcdHit_AcdTile moved from 0.11 to 0.10 for tile 15.
- LImits on digi_eor and Fastmon_eor CondArrROI_TKROpensWindow_TH1 relaxed a little bit.
- Relevant thread: https://www-glast.stanford.edu/protected/mail/datamon/8245.html