Does anyone have plans to support OpenMPI as an Apple OS X
"Framework"? I'm
interested because I would like to make PETSc a framework using a MPI
Framework.
Thanks,
Barry
Hi, just trying to join the threads...
If someone has this same problem, you can check also:
[OMPI users] Error initializing openMPI
I am also attaching to this email the requested information (file
ompi-output.tar.gz).
Thanks Jeff, Thanks Rainer.
On Tue, 30 Oct 2007, Jeff Squyres wrote:
Also, you will want to check that you have valid entries in
/etc/dat.conf. You might see the message you report if this is empty.
Jeff Squyres wrote:
Note that you still definitely need "self" in the BTL list. "self"
is the loopback device/btl (i.e., one MPI process sending to itself;
no
George is right that the error message either indicates that the
dlopen() of the udapl component is failing (which seems unlikely, or
you'd see errors when you run ompi_info -- we use the same exact code
to open components in ompi_info as we do in MPI processes), the udapl
BTL is electing n
Note that you still definitely need "self" in the BTL list. "self"
is the loopback device/btl (i.e., one MPI process sending to itself;
not sending to another process on the same host).
On Nov 1, 2007, at 3:52 PM, Jon Mason wrote:
On Wed, Oct 31, 2007 at 06:45:10PM -0400, Tim Prins wrote:
On Thu, Nov 01, 2007 at 07:41:33PM -0400, George Bosilca wrote:
> There are two things that are reflected in your email.
>
> 1. You can run Open MPI (or at least ompi_info) on the head node, and
> udapl is in the list of BTL. This means the head node has all
> libraries required to load udapl,
Hi,
This question is about the use of a simulation package called GROMACS.
PS: On our cluster (quad-core nodes), GROMACS does not scale well
beyond 4 cpus. So, I wish to run two different simulations, while
requesting 2 nodes (1 simulation on each node) to best exploit the
policies of our MAUI sc
Hi,
Is there any standard way of attaching/retrieving attributes to MPI_Request
object?
Eg. Typically there are dynamic user data created when starting the
asynchronous operation and freed when it completes. It would be convenient
to associate them with the request object itself to simplify the c
