Mondaic

Site Configuration Builder

This interactive configuration builder helps you create a valid Salvus configuration file. See the Salvus Flow Configuration page for detailed explanations. Choose a release and site type, fill in the form, then switch to the TOML tab to copy the result.

Create configuration for Salvus versionand site type
The default number of processors Salvus will be run with on this site, if not explicitly specified.
The maximum number of processors Salvus will be run with on this site. Serves to protect against accidental user errors.
Absolute path to the Salvus binary on the site.
Run directory on the site. Salvus will copy all files it requires to run into this directory. Must be read-and writeable.
Run directory on the site. Use for very large and/or temporary output. Must be read-and writeable. If site's systems has a scratch file system use it here.
optional
Update interval in seconds for commands that have to periodically ping the remote site. Don't choose this value too small for shared machines to conserve resources. We recommend 30.0 seconds for sites with a job queuing system and around 1.0 to 5.0 seconds for direct execution sites depending on the expected average job size.
optional
Only use this on dark sites (e.g. sites with no internet access). If this is set to True, Salvus will negotiate a license token with Mondaic's license server and send along the token.
optional
Set this to true if each compute node on the target site has at least one CUDA capable GPU accelerator attached and a CUDA driver version that is greater than or equal to 410.48 (CUDA 10.0).
optional
Force usage of a login bash shell. A bit slower but sometimes necessary/easier if a system performs some essential setup in a login shell.
optional
Optionally specify environment variables to be set before every call on the site. Repeat this group as often as needed.
site_specific
optional
This site uses a small Python script to launch SalvusCompute. Most system have a version of Python on the path. If that is not the case, specify the full path to the Python binary to be used here. It can be any Python >= 2.7.
optional
This site will usually just use the `mpirun` that comes with the Salvus distribution and use it for example as `mpirun -n 2 ...`. This part can be customized here. This can be changed with this setting by setting it to for example `/custom/mpirun -n {RANKS}`. Make sure to include the {RANKS} parameter here.
optional
By default, Salvus will attempt to decouple child processes from the parent process to enable async workflows. This results in child processes that keep running even if the parent process is terminated. If this option is set to True, Salvus will not decouple child processes.