You might want to take a look at PRRTE (https://github.com/openpmix/prrte) - it
does exactly what you describe., only from the other way around. It provides a
customizable launcher that supports the various cmd lines, and then uses a
common RTE backend.
We don't use SLURM_TASKS_PER_NODE for pla
Sorry for the slow reply!
I didn't want to get fixated on why the variable was unset, though I can
understand the existence of a check if Slurm always sets this (I don't
recall that being the case for all configurations historically, but perhaps
it is now). The reason I'd unset it (!) is because I
Martyn? Why are you saying SLURM_TASKS_PER_NODE might not be present?
It sounds to me like something is wrong in your Slurm environment - I really
believe that this envar is always supposed to be there.
> On Mar 15, 2021, at 4:20 AM, Peter Kjellström wrote:
>
> On Fri, 12 Mar 2021 22:19:09 +0
On Fri, 12 Mar 2021 22:19:09 +
Ralph Castain via devel wrote:
> Why would it not be set? AFAICT, Slurm is supposed to always set that
> envar, or so we've been told.
Maybe confusion on the exact name?
AFAIK slurm always sets SLURM_TASKS_PER_NODE but only sets
SLURM_NTASKS_PER_NODE (almost s
Why would it not be set? AFAICT, Slurm is supposed to always set that envar, or
so we've been told.
On Mar 12, 2021, at 2:15 AM, Martyn Foster via devel mailto:devel@lists.open-mpi.org> > wrote:
Hi Ralph,
Slurm is 19.05.
To be clear - its not unexpected that SLURM_TASKS_PER_NODE is unset in
Hi Ralph,
Slurm is 19.05.
To be clear - its not unexpected that SLURM_TASKS_PER_NODE is unset in the
configuration.
Martyn
On Thu, 11 Mar 2021 at 16:09, Ralph Castain via devel <
devel@lists.open-mpi.org> wrote:
> What version of Slurm is this?
>
> > On Mar 11, 2021, at 8:03 AM, Martyn Foster
What version of Slurm is this?
> On Mar 11, 2021, at 8:03 AM, Martyn Foster via devel
> wrote:
>
> Hi all,
>
> Using a rather trivial example
> mpirun -np 1 -rf rankfile ./HelloWorld
> on a Slurm system;
> --
> While tryin
