...
The I&T pipeline is now using GlastRelease instead of EngineeringModel. GR v13r6p1 is nearly identical to GR v13r5p6 which is used for the Big Run and has been extensively validated (on MC!) for MC (more about real data later). Here I only list the differences with respect to GR v13r5p6:
...
No changes with respect to GR v13r5p6 except for ACD DIgi IDs. This is due to a change in the system tests themselves which now use the dense ACD tile ID notation and not the sparse one. Note that the system tests for GlastRelease do not contain any tests using real data. I have done additional validation on real cosmic ray data like remaking a digi+recon SVAC report and compared it to the original report. No problems have been observed.
...
svac pipeline code and tasks:
code/tasks v3r9p4v4r0p0:
pipelineDatasets v0r3v0r4
ISOC code and tasks:
v0r5p0
Apps that run in pipeline:
eLog: v2r3p2
ConfigTables: v4r0p3v2r3p3
TestReport:
v4r1 awb
- Fixed Acd Mips maps so it works correctly with the new ACD code.
- Updated to run with Root V5.16 (GR v13).
- Changed the word 'EngineeringModel' to 'GlastRelease' in the report.
...
svac/Monitor: version mk20070719
dataMonitoring/Common: version acdemi2
New! Configuration report
We will start making a configuration report for each run. While the main effort will be put into the one for pipeline 2 we will put in something for pipeline 1 and TVAC.
Note that this replaces the old (and broken) config report. Currently we extract the LatC Moot key and a) dump a text file with detailed trigger information and b) an ntuple containing register values into the 'configReport' directory which will be linked from the runs database (replacing the old link to the old configReport). This is done using applications in the configData package which is part of GR. We will work on making a more presentable report in the very near future.