Reason for change

This new GR, v15r47p12, contains an improved error message in case of event errors and also removes an incorrect warning, repeated 160 times per event, in case we have data with TEM diagnostics. Most importantly, it fixes a bug with the ldfReader which prevented the TEM diagnostic from being interpreted correctly. We anticipate that taking data with the TEM diagnostics will be the new default running mode when the new FSW B2-1-0 is uploaded and activated. There is no change to any functionality in this GlastRelease.

We have also added a few new monitoring quantities related to event sizes at Eric Siskind's request, plus a new variable that monitors the distance from the SAA.

Finally, we are getting rid of the chunk-based host list (it didn't obviously help but produced a lot of trouble when some configuration changes were applied to LFS).

Test Procedure

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

Rollback procedure

We can switch back to the previous version of L1Proc.

CCB Jira

SSC-212@JIRA

Details

L1Pipeline v1r74:
- Getting rid of the chunk-based hostlist.

GlastRelease v15r47p12:
- There are a few changes in this GR wrt the version in use in L1, GR v15r47p7:
- ldfReader v7r4p1: windows patch to use const_iterator versus iterator; patch to set diagnostic and error bits properly by taking OR across contributions and making sure all diagnostic data is stored, even those without associated CAL or TKR data; patch check on diagnostic size
- RootIo v21r12gr1: patch to return kTRUE in GleamMessageHandler::Notify
- LdfConverter: patch to set various levels for EbfDebug
- EventIntegrity v0r8p2: Print out the error flag (JIRA GRINF-51) and event id when errors are found.

- There are no changes in the system tests wrt GR v15r47p7.

svac/TestReport: v9r2
- Completeness job option modified (was inconsistent with L1 config)

dataMonitoring/DigiReconCalMeritCfg: v1r4p1
- Added quantities to address JIRA GDQM-309.

dataMonitoring/FastMonCfg: v2r0p0
- Added a new variable (distance to the SAA) in the baseConfig.xml file (JIRA GDQMQ-311).
dataMonitoring/Common: v6r0p0
- Added -s option to pOptionParser to pass to the xml file with the SAA definition to dataMonitoring/FastMon/pDataProcessor.py (necessary for the plot of the distance to the SAA, as in JIRA GDQMQ-311).
dataMonitoring/FastMon: v5r0p0
- Quite a few files modified to accomodate the plot of the distance to the SAA (JIRA GDQMQ-311). The detailed description of the changes is:

  • pDataProcessor.py: one more command line option added (-s) to pass the xml file with the definition of the SAA.
  • pGeomagProcessor.py: added filling of the output tree with the distance to the SAA variable.
  • pM7Parser.py: new class member (the SAA polygon) added.
  • pSAAPolygon.py: EARTH_RADIUS not imported anymore from pSCPosition due to an import clash.
  • pSCPosition.py: added a new class member (the SAA polygon) and a new method returning the distance of a generic point from the polygon itself.

Complete set of tags for L1Proc 1.74

Code Versions

GlastRelease (sim/recon): v15r47p12*

ScienceTools (Level 2) : v9r8p2

Science Ops (task defs, scripts):

Level 1 pipeline code and applications running in L1:

svac/L1Pipeline: v1r74*

calibTkrUtil v2r7p3
calibGenTKR v4r5

dataMonitoring/AlarmsCfg: v5r17p4
dataMonitoring/FastMonCfg: v2r0p0*

dataMonitoring/DigiReconCalMeritCfg: v1r4p1*

dataMonitoring/Common: v6r0p0*
dataMonitoring/FastMon: v5r0p0*
datMonitoring/IGRF: v1r0p1

svac/Monitor: v1r2p37
svac/EngineeringModelRoot: v4r4
svac/TestReport: v9r2*

users/richard/pipelineDatasets: v0r6

ft2Util: v1r2p23

evtClassDefs v0r6

GPLtools: fileOps1