Greetings, and welcome to the wonderful world of MPI. :-)
First thing to note is that there are multiple different software packages that
implement the MPI specification. Open MPI -- the mailing list that you sent to
-- is one of them. MPICH, from Argonne National Labs, is another.
From the
Hello,
I am an undergraduate student. I have just started learning MPI and I have
to use the Einstein Toolkit code which uses MPI for my project.
I get this error when I try to check the output of my simulation:
*Fatal error in PMPI_Comm_rank: Invalid communicator, error
On Apr 4, 2018, at 12:58 PM, Quentin Faure wrote:
>
> Sorry, I did not see my autocorrect changed some word.
>
> I added the -l and it did not change anything. Also the mpicxx —showme does
> not work. It says that the option —showme does not exist
If 'mpicxx --showme'
Sorry, I did not see my autocorrect changed some word.
I added the -l and it did not change anything. Also the mpicxx —showme does not
work. It says that the option —showme does not exist
Quentin
On Apr 4, 2018, at 10:45, Quentin Faure
>
On Wed, 2018-04-04 at 11:57 -0400, George Bosilca wrote:
> We can always build complicated solutions, but in some cases sane and
> simple solutions exists. Let me clear some of the misinformation in
> this thread.
>
Oh, well, when I wrote the stuff I described earlier, it was before
MPI existed,
I had the -l but it did not change anything. Also the mlicxx —showme does not
work, it says that the option —showmen does not exist.
Quentin
On Apr 3, 2018, at 14:25, Nathan Hjelm >
wrote:
I guess I should point out the reason the compiler thought you had
>>
>> — I tried building older netloc with hwloc 2.0 and it throws compiler
>> errors. Note that netloc was cloned from it’s git repo.
>
> My guess is that the "map" part that joins netloc's info about the
> fabric with hwloc's info about the nodes doesn't like hwloc 2.0. But
> that should be
We can always build complicated solutions, but in some cases sane and
simple solutions exists. Let me clear some of the misinformation in this
thread.
The MPI standard is clear what type of conversion is allowed and how it
should be done (for more info read Chapter 4): no type conversion is
Dear colleagues,
FWIW, years ago I was looking at this problem and developed my
own solution (for C programs) with this structure:
--Be sure your code that works with ambiguous-length types like
'long' can handle different sizes. I have replacement unambiguous
typedef names like 'si32', 'ui64'
Le 04/04/2018 à 16:49, Madhu, Kavitha Tiptur a écrit :
>
> — I tried building older netloc with hwloc 2.0 and it throws compiler errors.
> Note that netloc was cloned from it’s git repo.
My guess is that the "map" part that joins netloc's info about the
fabric with hwloc's info about the nodes
Hi
Chiming in on this conversation, we have a few questions/concerns with some of
the responses we received from you.
>>
>> If you really want the old netloc API now, you could try hwloc 2.x with
>> the old netloc. But that's certainly not maintained anymore, and that
>> only works for IB while
Brice,
We don't actually care if it is a graph or a different API. We'll anyway
simply parse the graph and create our own internal structures that we can map
to our internal algorithms. We simply need some model (any model) to retrieve
the network topology. That's it. We'll take care of
I'm also interested in re-igniting the discussion, if others are also
interested. I'm curious about the current state of netloc, and what we all
want it to look like. Maybe we should move the discussion to the devel list
or have a teleconf or something to kick things off?
On Wed, Apr 4, 2018 at
13 matches
Mail list logo