Hy Jeff, thanks for replying.
Does it mean that you don't have it working properly yet? I read the thread
at the devel list where you addressed the problem and a possible solution,
but I was not able to find a conclusion about the problem.
I'm in trouble without this function. Probably I'll need
Unfortunately, I think that this is a known problem with INTERCOMM_MERGE and
COMM_SPAWN parents and children:
https://svn.open-mpi.org/trac/ompi/ticket/2904
On Jan 26, 2012, at 12:11 PM, Rodrigo Oliveira wrote:
> Hi there, I tried to understand the behavior Thatyene said and I think is a
Hi there, I tried to understand the behavior Thatyene said and I think is a
bug in open mpi implementation.
I do not know what exactly is happening because I am not an expert in ompi
code, but I could see that when one process define its color as *
MPI_UNDEFINED*, one of the processes on the inter
It seems the split is blocking when must return MPI_COMM_NULL, in the case
I have one process with a color that does not exist in the other group or
with the color = MPI_UNDEFINED.
On Wed, Jan 25, 2012 at 4:28 PM, Rodrigo Oliveira wrote:
> Hi Thatyene,
>
> I took a look in your code and it seems
Hi Thatyene,
I took a look in your code and it seems to be logically correct. Maybe
there is some problem when you call the split function having one client
process with color = MPI_UNDEFINED. I understood you are trying to isolate
one of the client process to do something applicable only to it, a
Hi there!
I've been trying to use the MPI_Comm_split function on an
intercommunicator, but I didn't have success. My application is very simple
and consists of a server that spawns 2 clients. After that, I want to split
the intercommunicator between the server and the clients so that one client
st
