> "George" == George Bosilca writes:
George> Why are you using system() the second time ? As you want
George> to spawn an MPI application calling MPI_Call_spawn would
George> make everything simpler.
Yes, this works! Very good trick... The system routine would be more
flexible, b
Why are you using system() the second time ? As you want to spawn an MPI
application calling MPI_Call_spawn would make everything simpler.
George
On Jul 3, 2014 4:34 PM, "Milan Hodoscek" wrote:
>
> Hi,
>
> I am trying to run the following setup in fortran without much
> success:
>
> I have an MP
Unfortunately, that has never been supported. The problem is that the embedded
mpirun picks up all those MCA params that were provided to the original
application process, and gets hopelessly confused. We have tried in the past to
figure out a solution, but it has proved difficult to separate th
Hi,
I am trying to run the following setup in fortran without much
success:
I have an MPI program, that uses mpi_comm_spawn which spawns some
interface program that communicates with the one that spawned it. This
spawned program then prepares some data and uses call system()
statement in fortran.
This looks to me like a message from some older version of OMPI. Please check
your LD_LIBRARY_PATH and ensure that the 1.9 installation is at the *front* of
that list.
Of course, I'm also assuming that you installed the two versions into different
locations - yes?
Also, add "--mca rmaps_base_v
When i used --map-by slot:pe=8, i got the same message
Your job failed to map. Either no mapper was available, or none
of the available mappers was able to perform the requested
mapping operation. This can happen if you request a map type
(e.g., loadbalance) and the corresponding mapper was n
