mc_runjob
Quick Start Guide

Installation :

To install mc_runjob (standard D0 installation) :

• setup n32 (on d0mino only)
• setup D0RunII version-tag
• setup d0cvs
• newrel -t version-tag my_dir
• cd my_dir
• addpkg mc_runjob v02-03-03
• d0setwa
• cd mc_runjob
• setenv MC_RUNJOB_CARD_PATH .\:`pwd`/templates/cards (tcsh/csh users)
• export MC_RUNJOB_CARD_PATH=.:`pwd`/templates/cards (bash/sh users)
• cd py_script
• setenv MC_RUNJOB_PATH .\:`pwd`/scripts (tcsh/csh users)
• export MC_RUNJOB_PATH=.:`pwd`/scripts (bash/sh users)

(or remote installation) :

• Setup the mini-tarfiles for your remote distribution.
• ftp mc_runjob.tar.gz from d0mino (from ~ggraham/umd2/mcc3_tarfiles/tarfiles)
• gzip -d mc_runjob.tar.gz
• tar xvf mc_runjob.tar
• setenv SRT_LOCAL `pwd` (tcsh/csh users)
• export SRT_LOCAL=`pwd` (bash/sh users)
• cd mc_runjob
• setenv MC_RUNJOB_CARD_PATH .\:`pwd`/templates/cards (tcsh/csh users)
• export MC_RUNJOB_CARD_PATH=.:`pwd`/templates/cards (bash/sh users)
• cd py_script
• setenv MC_RUNJOB_PATH .\:`pwd`/scripts (tcsh/csh users)
• export MC_RUNJOB_PATH=.:`pwd`/scripts (bash/sh users)

Usage :

python Linker.py option-list

Available Options :

• StandardD0=0/StandardD0=1 (0 default) On d0mino, StandardD0=1 is recommended. On remote sites without standard D0 software installation, StandardD0=0 is required.
• SaveOnMake=0/SaveOnMake=1 (1 default) When on, job configuration information is automatically saved to the job directory on a "Make Job". When off, this must be done explicitly.
• MiniDB=0/MiniDB=1 (0 default) When on, status information will be written to a file called ".database/database" in the directory specified CurrentDir in samglobal configurator. It is buggy in v02-03-03 and may sometimes cause an error message.
• debuglevel=n n=0 : No debug output. n=10 : Lots of output.
• script=script-name The linker will execute the first mc_runjob macro script named script-name in the path specified by MC_RUNJOB_PATH.
• control=GUI The Linker will spawn a GUI version of itself.

What happenes next :

Upon invocation, the Linker exits unless one the script option or the control option is given on the command line. In order to do anything interesting, you must tell the Linker to instantiate one or more Configurators via a macro script or the GUI. Most Configurators encapsulate the knowledge of running a particular D0 offline executable, though some encapsulate other knowledge such as running a batch job or interfacing with SAM. A special Configurator called samglobal is required to run any D0 executable.

In the scripts subdirectory of py_script, there are several example mc_runjob macro scripts you can try. These are set up to process data from generation stage through the RecoAnalyze stage.

• Where are the executables run ? The executables are run in local release areas built by the corresponding Configurators. These local release areas are all stored in the directory given as CurrentDir in the samglobal Configurator.
• Where does the output go ? The output of each job is stored under a directory given as DestinationDir in the samglobal Configurator.
• Where do the card files come from ? The cardfile obtained is the first cardfile corresponding to the physics process found in the search path given by the environmental variable MC_RUNJOB_CARD_PATH. The naming convention is production-decay.generator where production and decay are specified in the corresponding Configurator and generator is "isa" or "pythia".

Examples :