launchers.toml

Row includes built-in launchers to enable OpenMP and MPI on the built-in clusters. You can override these configurations and add new launchers in the file $HOME/.config/row/launchers.toml.

The launcher configuration defines how each launcher expands into a command prefix, with the possibility for specific settings on each cluster. For example, an action with the configuration:

[[action]]
name = "action"
command = "command {directory}"
launchers = ["launcher1", "launcher2"]

will expand to:

<launcher1 prefix> <launcher2 prefix> command $directory || {{ ... handle errors }}

in the submission script.

The prefix is a function of the job's resources and the size of the group in the current submission. The section Launcher configuration details how this prefix is constructed.

Default launcher configuration

The default configuration will be used when there is no cluster-specific configuration for the currently active cluster. Every launcher must have a default configuration. Create a new launcher by creating a table named <launcher name>.default in launchers.toml. For example:

[launcher1.default]
# launcher1's default configuration

Cluster-specific launcher configuration

Define a launcher configuration specific to a cluster in the table <launcher name>.<cluster>, where <cluster> is one of the cluster names in clusters.toml. For example:

[launcher1.none]
# launcher1's configuration for the cluster `none`.

---