Inline help:

python3 submit.py --help

Create the Job configuration using the command:

python3 submit.py -f submit.yaml --create

Submit the jobs to the queues via the command:

python submit.py -f submit.yaml --submit

The conf file uses the YAML format. You can find several examples in this directory. Most of the parameters should be self explenatory. Each task corresponds to a sample.

The tool supports:

• HT-Condor local submission: each task will be mapped to a dedicated condor cluster. Input files can be specified via the dataset name using one of:
  • input_dataset: official DBS dataset name
  • input_directory: directory where the files sit.
  • input_files: the same file set is used for all jobs.

The implemented input splitting modes are: file_based (meant to work with input_dataset and input_directory), lumi_based (in the sense of LS) and events_ranges (meant to work with input_files). For the job_flavor and other condor parameters please refer to the CERN Condor documentation

• CRAB remote submission: this is controlled setting the crab: True parameter. In this case the input needs to be specified using input_dataset and for the configuration of splitting_mode and splitting_granularity you need to refer to the CMS CRAB Sw Guide. The rest of the parameters can be customized via the template file crab_MODE.py (see the documentation about the template structure in the following).

If you want to add a new set of templates you need to define a new mode (MODE) customizing the relevant files in the directory templates/.

Note the code assumes that all string starting with TEMPL_ are variables in the templated files that need to be replaced.

The templated files are of 4 kinds:

1. condorSubmit_MODE.sub: this defines the structure of the Condor submission file. If you don't need to modify it you can use the condorSubmit_DEFAULT.sub one (see CERN Condor documentation). (This is only used when submitting via HT-Condor).
2. jobCustomization_MODE_cfg.py. which defines what needs to be changed for the configuration of each cmsRun job of the cluster. (This is only used when submitting via HT-Condor).
3. run_MODE.sh: this is the script which actually gets executed on the node, setups the config and calls cmsRun. Again a run_DEFAULT.sh exists and should work for most cases. (This is only used when submitting via HT-Condor).
4. crab_MODE.py is the templated crab configuration file. (This is only used when submitting via Crab3).

Note that if the yaml configuration defines a mode that is not implemented for a certain file the script will fall back to the corresponding file in DEFAULT mode.