Hi Gilles,
MPI provides explicit comparison functions to compare opaque handles, for
communicators it is MPI_Comm_compare.
- Joachim
From: users on behalf of Guillaume De Nayer
via users
Sent: Friday, June 24, 2022 5:13:17 PM
To: users@lists.open-mpi.org
Cc:
Thank you for these infos!
On 06/24/2022 05:06 PM, Jeff Squyres (jsquyres) via users wrote:
> Open MPI and MPICH are completely unrelated -- we're entirely different code
> bases (note that Intel MPI is derived from MPICH).
>
> Case in point is what Gilles cited: Open MPI chose to implement MPI_
Open MPI and MPICH are completely unrelated -- we're entirely different code
bases (note that Intel MPI is derived from MPICH).
Case in point is what Gilles cited: Open MPI chose to implement MPI_Comm
handles as pointers, but MPICH chose to implement MPI_Comm handles as integers.
Hence, you ca
Hi Gilles,
I'm using both openmpi and intel mpi. I have with both problem with the
communicators. Therefore, I tried to get some infos about them.
Thx a lot for your help.
Have a nice day
On 06/24/2022 02:14 PM, Gilles Gouaillardet via users wrote:
> Guillaume,
>
> MPI_Comm is an opaque handler
Guillaume,
MPI_Comm is an opaque handler that should not be interpreted by an end user.
Open MPI chose to implement is as an opaque pointer, and MPICH chose to
implement it as a 32 bits unsigned integer.
The 4400 value strongly suggests you are using MPICH and you are hence
posting to the wro
On 06/24/2022 01:38 PM, Jeff Squyres (jsquyres) via users wrote:
> Guillaume --
>
> There is an MPI Standard document that you can obtain from mpi-forum.org.
> Open MPI v4.x adheres to MPI version 3.1 (the latest version of the MPI
> standard is v4.0, but that is unrelated to Open MPI's version
Hi Gilles,
MPI_COMM_WORLD is positive (4400).
In a short code I wrote I have something like that:
MPI_Comm_dup(MPI_COMM_WORLD, &world);
cout << "intra-communicator: " << "world" << "---" << hex << world << endl;
It returns "8406" (in hex).
later I have:
MPI_Comm_accept(port_name, MPI_
Sorry if I did not make my intent clear.
I was basically suggesting to hack the Open MPI and PMIx wrappers to
hostname() and remove the problematic underscores to make the regx
components a happy panda again.
Cheers,
Gilles
- Original Message -
> I think the files suggested by Gilles
Guillaume --
There is an MPI Standard document that you can obtain from mpi-forum.org. Open
MPI v4.x adheres to MPI version 3.1 (the latest version of the MPI standard is
v4.0, but that is unrelated to Open MPI's version number).
Frankly, Open MPI's support of the dynamic API functionality
(c
I think the files suggested by Gilles are more about the underlying call to get
the hostname; those won't be problematic.
The regex Open MPI modules are where Open MPI is running into a problem with
your hostnames (i.e., your hostnames don't fit into Open MPI's expectations of
the format of the
Guillaume,
what do you mean by (the intercommunicators are all negative"?
Cheers,
Gilles
On Fri, Jun 24, 2022 at 4:23 PM Guillaume De Nayer via users <
users@lists.open-mpi.org> wrote:
> Hi,
>
> I am new on this list. Let me introduce myself shortly: I am a
> researcher in fluid mechanics. In
Hi,
I am new on this list. Let me introduce myself shortly: I am a
researcher in fluid mechanics. In this context I am using softwares
related on MPI.
I am facing a problem:
- 3 programs forms a computational framework. Soft1 is a coupling
program, i.e., it opens an MPI port at the beginning
12 matches
Mail list logo
