Any ideas on what might be causing this one? Or atleast what
additional debug information someone might need?
On Fri, Jan 7, 2011 at 4:03 PM, Michael Di Domenico
wrote:
> I'm still testing the slurm integration, which seems to work fine so
> far. However, i just upgraded another cluster to open
You might be confusing LAM/MPI with Open MPI -- they're two different software
code bases. They both implement the MPI standard, but they're entirely
different software projects. Indeed, all the LAM/MPI developers (including me)
abandoned LAM/MPI several years ago and went to work on Open MPI
So are you trying to start an mpi job that one process is one executable
and the other process(es) are something else? If so, you probably want
to use a multiple app context. If you look at FAQ question 7. How do I
run an MPMD MPI Job at http://www.open-mpi.org/faq/?category=running
this sho
Hello,
This feature is very important for my project. It is managing coupling
parallel codes.
Thanks to correct this bug as soon as possible.
Best
Bernard
Open MPI a écrit :
#2681: ompi-server publish name broken in 1.5.x
---+--
Hi,
> What I want is to spawn a bunch of R slaves to other machines on
> the network. I can spawn R slaves, as many as I like, to the local
> machine, but I don t know how to do this with machines on the
> network. That s what hosts parameter of mpi.spawn.Rslaves()
> enables me to do, I think. I
Hi,
Thanks for your reply.
I am afraid your terse response doesn’t shed much light. What I need is “hosts”
parameter I can use to mpi.spawn.Rslaves() function. Can you explain or better
yet give an example as to how I can get this via mpirun?
Looking at mpirun man page, I found an example:
m
