A simple utility for executing multiple sequential or multi-threaded applications in a single multi-node batch job
This is the new 3.7 Version
Launcher v 3.1. The new version includes:
export LAUNCHER_BIND=1
before calling paramrun
LAUNCHER_NHOSTS
, LAUNCHER_PPN
, and the information returned by hwloc to determine the number of contexts to give to each launcher
process. If you are using scheduler integration, these values will be determined through your scheduler's regular mechanisms.launcher
process. This way, an application which uses OpenMP or PThreads can still use multiple threads without those threads migrating to hardware contexts which belong to other launcher
processes.SLURM_NODELIST
env. variable from the passed environment in order to get around an issue when using zsh.As always, feel free to submit issues and requests. If anyone wishes to get involved with the Launcher project with code contributions, documentation, telling others about launcher, let us know at the launcher-users group (https://groups.google.com/forum/#!forum/launcher-users).
First release candidate for Launcher v 3.1. The new version includes:
export LAUNCHER_BIND=1
before calling paramrun
LAUNCHER_NHOSTS
, LAUNCHER_PPN
, and the information returned by hwloc to determine the number of contexts to give to each launcher
process. If you are using scheduler integration, these values will be determined through your scheduler's regular mechanisms.launcher
process. This way, an application which uses OpenMP or PThreads can still use multiple threads without those threads migrating to hardware contexts which belong to other launcher
processes.SLURM_NODELIST
env. variable from the passed environment in order to get around an issue when using zsh.As always, feel free to submit issues and requests. If anyone wishes to get involved with the Launcher project with code contributions, documentation, telling others about launcher, let us know at the launcher-users group (https://groups.google.com/forum/#!forum/launcher-users).
Minor release to fix issue with starting dynamic scheduling due to STDIN attach issue in backgrounded processes (discovered on the Cray XC40 - Lonestar5).
New in version 3.0: