...
The previous L1Proc introduced a new type of quantity that needed to be propagated to the Tree mergeing. It was not (oversight). While the testing was done with multi-chunk runs they were not not adjacent and did not trigger this bug. The script is intelligent enough to only do a straight copy in that case. Testing procedures will be changed.
We also have a fix for a memory leak in merging Hiro's TKR monitoring histograms.
And finally, we have a new GR, v15r2, which includes the Pass7 changes and also updates to the GCR algorithmNo other changes are in this version of L1Proc.
Test Procedure
We have processed both MC and real data on the DEV server with this version of L1Proc.
...
svac/Monitor: v1r1p13
- Modfied treemerge.cxx so that the merged quantity is not the largest value, but the last value. This is done in case the DataTransferId has decreasing numbers.
- Added merging of quantity outputnumber (prefix Number_) which is an UInt_t. The merging consists in using the largest value. This is a temporal solution to deal with quantity Number_LastDataTransferId. The proper way to go is to define thsi quantiy as ValChange update the data base to deal with ValChange quantities.
calibTkrUtil v2r2p2:
- Fixing a memory when merging histograms.
svac/EngineeringModelRoot v3r14p4:
- Added ObfFilterStatusBits (Gleam filters).
Complete set of tags for L1Proc 1.51
Code Versions
GlastRelease (sim/recon)
...
v15r2*
ScienceTools (Level 2) : v9r5p4
...
svac/Monitor: v1r1p13*
svac/EngineeringModelRoot: v3r14p3v3r14p4*
svac/TestReport: v6r8
calibTkrUtil v2r2p1 v2r2p2*
users/richard/pipelineDatasets: v0r4
...