Now that you have written the file to configure your algorithm, it is time to run it
To execute the job using this script, go to your run
directory, and
execute your macro with the command:
ATestRun_eljob.py --submission-dir=submitDir
If your algorithm does not run, there could be an issue with the “Shebang” line in your steering macro. You can just override this and directly run with python using
python ../build/x86_64-centos7-gcc8-opt/bin/ATestRun_eljob.py --submission-dir=submitDir
.
While you are in principle free where you put your
submitDir
, avoid putting them into thesource
directory, as that is usually version controlled and you risk your data files being added to the repository (which is bad). Also avoid putting them into thebuild
directory, as you often want to keep the contents ofsubmitDir
around, while thebuild
directory should only contain files you don’t mind losing. Putting it inside therun
directory is a reasonable choice if you have enough space there, but if it ends up containing large files you may need to put it onto a separate data disk. If you run in batch you may also need to put it inside a directory that is accessible from the worker nodes.
Go to your run
directory and execute your jobOptions with Athena using
the following command:
athena MyAnalysis/ATestRun_jobOptions.py
You can override many of the options specified in the jobOptions when calling the
athena
command. For example, you can set the number of events to process with the--evtMax
option (-1 is the default value and causes all events to be processed):athena MyAnalysis/ATestRun_jobOptions.py --evtMax=-1
Or you can override the input files used with the
--filesInput
option:athena MyAnalysis/ATestRun_jobOptions.py --filesInput=another.file.root