Thanks for the info.
meanwhile I have set:
mpi_param_check = 0
in my system-wide configuation file on workers
and
mpi_param_check = 1
on the master.
Jerome
Ralph Castain wrote:
Thanks! That does indeed help clarify.
You should also then configure OMPI with
--disable-per-user-config-f
Thanks! That does indeed help clarify.
You should also then configure OMPI with --disable-per-user-config-
files. MPI procs will automatically look at the default MCA parameter
file, which is probably on your master node (wherever mpirun was
executed). However, they also look at the user's h
Hi,
thanks for the reply.
Ralph Castain wrote:
The orteds don't pass anything from MPI_Info to srun during a
comm_spawn. What the orteds do is to chdir to the specified wdir before
spawning the child process to ensure that the child has the correct
working directory, then the orted changes ba
The orteds don't pass anything from MPI_Info to srun during a
comm_spawn. What the orteds do is to chdir to the specified wdir
before spawning the child process to ensure that the child has the
correct working directory, then the orted changes back to its default
working directory.
The or
Hi !
finally I got it:
passing the mca key/value `"plm_slurm_args"/"--chdir /local/folder"' does the
trick.
As a matter of fact, my code pass the MPI_Info key/value
`"wdir"/"/local/folder"'
to MPI_Comm_spawn as well: the working directories on the nodes of the spawned
programs
are `nodes:/loc
Hello Again,
Jerome BENOIT wrote:
Hello List,
I have just noticed that, when MPI_Comm_spawn is used to launch programs
around,
oreted working directory on the nodes is the working directory of the
spawnning program:
can we ask to oreted to use an another directory ?
Changing the working th
Hello List,
I have just noticed that, when MPI_Comm_spawn is used to launch programs around,
oreted working directory on the nodes is the working directory of the spawnning
program:
can we ask to oreted to use an another directory ?
Thanks in advance,
Jerome
