...
The initial sample files can be found on SLAC unix at
/unfs/farm/eyg/richardglast/GLASTu13/PipelineMC-tasks/
Caveats at time of writing
- a modified GlastSvc is needed to use an environment variable in the job options file for the run number. It is tagged in cvs but is held hostage to the new TkrRecon upgrade.available in GlastSvc v9r12p1, and appeared in GlastRelease as of HEAD1.403; it is not in EngineeringModel yet!
Configuring the pipeline
Here is a sample xml file for upload to Gino:
Code Block | ||||
---|---|---|---|---|
| ||||
<?xml version="1.0" encoding="UTF-8"?> <pipeline xmlns="http://glast-ground.slac.stanford.edu/pipeline" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://glast-ground.slac.stanford.edu/pipeline http://glast-ground.slac.stanford.edu/pipeline/pipeline.xsd"> <name>allGamma-GR-v4r6-test1<HEAD1.403</name> <type>SimReconDigi</type> <base<dataset-base-path>/nfs/farm/g/glast/u13/DC2/PipelineTest/allGamma/</MC-tasks/allGamma-GR-HEAD1.403/rootData/$(RUN_NAME)</dataset-base-path> <run-log-path>/temp/</run-log-path> <executable name="GleamWrapper" version="v1r0"> /afs/slac/u/ey/richard/GLAST/Pipeline/allGamma /nfs/farm/g/glast/u13/MC-tasks/allGamma-GR-HEAD1.403/config/GleamWrapper.pl </executable> <batch-job-configuration name="xlonglong-job" queue="xlonglong"> <working-directory>log/$(RUN_NAME)/<directory>/nfs/farm/g/glast/u13/MC-tasks/allGamma-GR-HEAD1.403/config</working-directory> <log-file-path>rootDatapath>/nfs/farm/g/glast/u13/MC-tasks/allGamma-GR-HEAD1.403/rootData/$(RUN_NAME)/<log</log-file-path> </batch-job-configuration> <file name="digi" type="DIGI" file-type="root">rootData/$(RUN_NAME)/</file>/> <file name="merit" type="merit" file-type="root">rootData/$(RUN_NAME)/</file>/> <file name="recon" type="RECON" file-type="root">rootData/$(RUN_NAME)/</file>/> <file name="mc" type="MC" file-type="root">rootData/$(RUN_NAME)/</file>/> <processing-step name="gleam" executable="GleamWrapper" batch-job-configuration="xlonglong-job"> <output-file name="mcdigi"/> <output-file name="merit"/> <output-file name="recon"/> <output-file name="digimc"/> </processing-step> </pipeline> |
...
- allGamma.txt - job options file
- the only items to modify are the source name and number of events
- allGamma.sh - shell script that launches Gleam
- modify the CMTCONFIG and GlastRelease and Gleam versions
Accessing files via the pipeline catalogue
A Root class has been written to query the database to find requested files and create a TChain of them. These are in cvs at
http://www-glast.stanford.edu/cgi-bin/viewcvs/users/richard/pipelineDatasets/#dirlist
bash-2.05b$ source ~/GLAST/Pipeline/setupOracleRoot3.sh
bash-2.05b$ root -l
root 0 .L ~/GLAST/Pipeline/pipelineDatasets/v0/rh9_gcc32/libpipelineDatasets.so
root 1 pipelineDatasets* p = new pipelineDatasets();
root 2 int sc = p->selectDatasets("allGamma-GR-HEAD1.403","merit");
root 3 TChain* c = p->makeChain("MeritTuple");