Closed danisven closed 8 years ago
A SLURM entry is required in the config file. So far the stand-alone SLURM entry only contains one key namely account_name
. Since, according to the SLURM user guide under required job parameters:
These are the things you typically need to specify for each job (required parameters might differ sligthly depending on which other parameters are set):
Which project should be accounted for the running time (Format: -A [project name]) For example, if you project is named p2010999, you specify -A p2010999 You can find your current projects (and other projects that you have run jobs in) with the program projinfo.
Even for a config file that specifies a pipeline that is to be run locally, without SLURM?
Line 220, generator.py:
assert (any('SLURM' in job.keys() for job in jobs) and 'SLURM' in config_dict),\
'job specified with SLURM but SLURM project-name is missing'
The assert will only be True if at least one of the jobs contain 'SLURM' and the config file contain 'SLURM', no?
Shouldn't the above be changed to something like:
if any('SLURM' in job.keys() for job in jobs): # If any job has been specified to use SLURM
assert 'SLURM' in config_dict, "job specified with SLURM but SLURM entry is missing" # Make sure that there is a SLURM entry in the config file
Because that way we first check if any of the jobs should be run using SLURM, and if so, check that the config file has the SLURM entry somewhere.
Or am I missing something obvious?
Modified the test pipeline in an attempt to run the pipeline locally on the KAW server.
Modified batch_execution.py:
Does this boil down to line 220 in generator.py?
The YAML file I use does not contain 'SLURM'.