or
> must be in the same group. Is my understanding incorrect?
>
>
>
> Thanks
>
> Rick
>
>
>
> From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Gilles
> Gouaillardet
> Sent: Monday, October 17, 2016 10:38 AM
>
>
> To: Open MPI Users
[mailto:users-boun...@lists.open-mpi.org] On Behalf Of Gilles
Gouaillardet
Sent: Monday, October 17, 2016 10:38 AM
To: Open MPI Users
Subject: Re: [OMPI users] communications groups
Rick,
So you have three types of tasks
- 1 dispatcher
- several sensors
- several proxies
If proxies do not communicate
Of *Gilles Gouaillardet
> *Sent:* Monday, October 17, 2016 9:30 AM
> *To:* Open MPI Users
> *Subject:* Re: [OMPI users] communications groups
>
>
>
> Rick,
>
>
>
> I re-read the MPI standard and was unable to figure out if sensorgroup is
> MPI_GROUP_EMPTY or a gro
ot;.
Rick
From: users [mailto:users-boun...@lists.open-mpi.org] On Behalf Of Gilles
Gouaillardet
Sent: Monday, October 17, 2016 9:30 AM
To: Open MPI Users
Subject: Re: [OMPI users] communications groups
Rick,
I re-read the MPI standard and was unable to figure out if sensorgroup is
MPI_GROUP_
nt:* Friday, October 14, 2016 5:44 PM
> *To:* Open MPI Users
> *Subject:* Re: [OMPI users] communications groups
>
>
>
> Rick,
>
>
>
> Let's assume that you have started 2 processes, and that your sensorList
> is {1}. The worldgroup will then be {P0,
Rick,
In my understanding, sensorgroup is a group with only task 1
Consequently, sensorComm is
- similar to MPI_COMM_SELF on task 1
- MPI_COMM_NULL on other tasks, and hence the barrier fails
I suggest you double check sensorgroup is never MPI_GROUP_EMPTY
and add a test not to call MPI_Barrier on
-boun...@lists.open-mpi.org] On Behalf Of George
Bosilca
Sent: Friday, October 14, 2016 5:44 PM
To: Open MPI Users
Subject: Re: [OMPI users] communications groups
Rick,
Let's assume that you have started 2 processes, and that your sensorList is
{1}. The worldgroup will then be {P0, P1}, which trimm
Rick,
Let's assume that you have started 2 processes, and that your sensorList is
{1}. The worldgroup will then be {P0, P1}, which trimmed via the sensorList
will give the sensorgroup {MPI_GROUP_EMPTY} on P0 and the sensorgroup {P1}
on P1. As a result on P0 you will create a MPI_COMM_NULL communic
Designation: Non-Export Controlled Content
Folks;
I have the following code setup. The sensorList is an array of
ints of size 1. The value it contains is 1. My comm world size is 5. The call
to MPI_Barrier fails every time with error "invalid communicator". This code is
pretty mu
