Monte Carlo generation of events will involve creating runs from scratch with no external agent triggering runs.
The initial sample files can be found on SLAC unix at
/u/ey/richard/GLAST/Pipeline/
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.
Configuring the pipeline
Here is a sample xml file for upload to Gino:
<?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</name>
<type>SimReconDigi</type>
<base-path>/nfs/farm/g/glast/u13/DC2/PipelineTest/allGamma/</base-path>
<run-log-path>/temp/</run-log-path>
<executable name="GleamWrapper" version="v1r0">
/afs/slac/u/ey/richard/GLAST/Pipeline/allGamma/GleamWrapper.pl
</executable>
<batch-job-configuration name="xlong-job" queue="xlong">
<working-directory>log/$(RUN_NAME)/</working-directory>
<log-file-path>rootData/$(RUN_NAME)/</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="xlong-job">
<output-file name="mc"/>
<output-file name="merit"/>
<output-file name="recon"/>
<output-file name="digi"/>
</processing-step>
</pipeline>
In addition there are two files that the pipeline uses to run Gleam:
- GleamWrapper.pl - run by the pipeline
- gleam.pl - prepares environment variables for use in the Gleam shell script
In general these can be reused from task to task without modification (except gleam.pl does execute allGamma.sh - this could be made generic).
Configuring Gleam
There are 2 files that need to be modified in this process:
- 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