Difference between revisions of "HOWTO run an analysis launch on bggen simulations"
From GlueXWiki
(Created page with "= Setup the Software & Environment = '''1)''' Checkout (or svn update) the launch scripts if needed: <pre> svn co https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/lau...") |
(→Prepare the Launch) |
||
Line 27: | Line 27: | ||
</pre> | </pre> | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
− | + | ||
Revision as of 18:23, 12 November 2021
Setup the Software & Environment
1) Checkout (or svn update) the launch scripts if needed:
svn co https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/launch
2) You will need only the following 3 files:
launch.py script.sh jobs_analysis_bggen.config
Prepare the Launch
1) Update jobs_analysis_bggen.config. Be sure to update the location for the SCRIPTFILE, JANA_CONFIG, and ENVFILE where appropriate. The xml file that was used for the analysis launch for data should be chosen:
ENVFILE analysis-2017_01-ver46.xml
2) Also update the paths for INDATA_TOPDIR, OUTDIR_LARGE (for trees and histograms), and OUTDIR_SMALL (for log files):
INDATA_TOPDIR /cache/halld/gluex_simulations/REQUESTED_MC/F2018_ver02_21_bggen_batch01_20211104064237pm/hddm OUTDIR_LARGE /volatile/halld/home/$USER/bggen OUTDIR_SMALL /farm_out/$USER/bggen
4) Create the SWIF workflow. The workflow must match the workflow name in the job config file:
swif create -workflow <my_workflow>
5) Register jobs for the workflow:
~/monitoring/launch/launch.py jobs_analysis_bggen.config <run_min> <run_max>
6) Run the workflow:
swif run -workflow <my_workflow>