Code: batch_systems
¶
Batch Systems define a limited interface to various batch job systems (e.g.
SLURM). Objects of this class can be used on
their own, or can be attached to other objects, e.g. a SetUp
In the top-level of the module, a basic skeleton class which defines the
guarenteed interfaces offered by a BatchSystem
object is defined. It needs
to have the following:
Attributes defining the:
- The submitter (which command is needed to send a script to the queue)
- Flags for the submitter
- The launcher (which command is needed to start an executable on the compute node)
- Flags for the launcher
- The status command (which command is needed to check the queue)
- The resource account (if you buy computer time, this is used to assign your simulation to a specific account)
Methods to check the full queue and your own jobs
Method to construct submitter and launcher commands and flags
names of these attributes and methods are summarized below.
-
class
pyesm.core.batch_systems.
BatchSystem
[source]¶ Bases:
object
Skeleton class to define interface of a batch system
Parameters: host (Host, optional) – Default None
. If the optional argumenthost
remainsNone
, the configuration for the computing host you are currently working on is loaded. This is attached to theBatchSystem
object asself._account
The following additional attributes are defined upon initialization:
-
submitter_flags
¶ Contains keys used to configure the
submitter
. Values of typestr
,int
,float
are then put tostr
in the form:key=value
. Values of the typebool
have their value removed and simply pass the key to the submitter_flags string which appended after the submitter command.Type: dict
-
version
= '0.1'¶
-
Submodules¶
batch_systems.slurm
¶
batch_systems.moab
¶
Note
Not yet implemented.