The current release of Open MPI does not support running a single
universe across multiple machines like you describe. We are currently
working on that capability on a side branch of the OpenRTE effort and
hope to begin testing it soon. Once we fully validate that
functionality, we will bring i
Robert Latham wrote:
This was fine on a single machine. What do you recommend for multiple
machines (e.g. app1 on node1 and app2 on node2)? How do i tell
multiple orted instances that they are part of the same universe?
well, the assumption here is, that the persistent daemon is running such
On Tue, Mar 14, 2006 at 12:37:52PM -0600, Edgar Gabriel wrote:
> I think I know what goes wrong. Since they are in different 'universes',
> they will have exactly the same 'Open MPI name', and therefore the
> algorithm in intercomm_merge can not determine which process should be
> first and whic
I think I know what goes wrong. Since they are in different 'universes',
they will have exactly the same 'Open MPI name', and therefore the
algorithm in intercomm_merge can not determine which process should be
first and which is second.
Practically, all jobs which are connected at a certain p
could you provide me a simple testcode for that? Comm_join and
intercomm_merge should work, I would have a look at that...
(separate answer to your second email is coming soon)
Thanks
Edgar
Robert Latham wrote:
Hi
I've got a bit of an odd bug here. I've been playing around with MPI
process
Hi
I've got a bit of an odd bug here. I've been playing around with MPI
process management routines and I notied the following behavior with
openmpi-1.0.1:
Two processes (a and b), linked with ompi, but started independently
(no mpiexec, just started the programs directly).
- a and b: call MPI_
