Example package to write SusyNt nutples
Prerequisites:
- cvmfs (
echo ${ATLAS_LOCAL_ROOT_BASE}) and setupATLAS - svn access and kerberos ticket (
klist)
Follow these commands to set up an area to write SusyNtuples.
git clone [email protected]:susynt/susynt-write.git
cd susynt-write
git checkout nXXXX
source bash/setup_area.sh --stable |tee install.log
source bash/setup_release.sh 2>&1 |tee compile.log
The commands above will checkout and compile all the packages that are
necessary to run NtMaker. If you are not a developer or do not have
a github account (make one if this is the case!), replace the first
line in the above with:
git clone https://github.com/susynt/susynt-write.git
The option "--stable" for the script setup_area.sh ensures that you will checkout the tags for the specific SusyNt production nXXXX. If you do not provide the "--stable" option, you will checkout the master/development branches of both SusyNtuple and SusyCommon.
You you can test NtMaker as:
cd SusyCommon/run
NtMaker -f <xaod_file.root>
(see test_and_log.sh for recent example input files):
For the submission of your jobs to the grid, see susynt-submit.
The commands above are needed only on the first setup. On the following sessions (from a clean environment):
cd susynt-write
rcSetup
Note1: the submission of the jobs must be performed from a different directory from the one where the packages are compiled.
Note2: if you want to submit a production, you should use the
--stable option of setup_area.sh.