No, the root processor can be different for every broadcast, but for a same
broadcast every process involved must know who the root is. That's the only
condition MPI imposes.
George.
On Apr 29, 2013, at 13:15 , giggzounet wrote:
> Hi,
>
> I'm new on this list. I'm using MPI for years but I
Thank you!
I agree that using NFS to share the home directory now..
I wanted to use --preload-binary option.
eiichi
On Mon, Apr 29, 2013 at 10:15 AM, Jeff Squyres (jsquyres) <
jsquy...@cisco.com> wrote:
> FWIW, to avoid using the --prefix option, you can set your PATH /
> LD_LIBRARY_PATH to poin
FWIW, to avoid using the --prefix option, you can set your PATH /
LD_LIBRARY_PATH to point to the Open MPI installation on all nodes.
Many organizations opt to have NFS-shared home directories, so that when you
modify your "main" shell startup file (e.g., .bashrc) to point PATH and
LD_LIBRARY_P
Well, it looks like you included a node called "ibc18" in your hostfile, and
ssh doesn't recognize that node or know how to reach it.
On Apr 29, 2013, at 6:12 AM, "sudhirs@" wrote:
> Dear users,
> I am getting following error while doing a calculation. The job is getting
> terminated before wr
Dear users,
I am getting following error while doing a calculation. The job is getting
terminated before writing anything in output file .
==
ssh: ibc18: Name or service not known^M
-
It works!!!
By putting two dash'es and no equal sign, it worked fine!!
[root@host1 tmp]# mpirun --prefix /myname --host host2 /tmp/hello.out
Hello World from processor host2, rank 0 out of 1 processors
[root@host1 tmp]#
It looks like one dash "-prefix" also works if I don't put an equal sign..
T
Hmmokay. No, let's not bother to install a bunch of stuff you don't
otherwise need.
I probably mis-typed the "prefix" option - it has two dashes in front of it and
no equal sign:
mpirun --prefix ./myname ...
I suspect you only put one dash, and the equal sign was a definite problem,
which
I tried configuring/building an OMPI on the remote host but I was not able
to...
The remote host (host2) doesn't have any development tools, such as gcc,
make, etc...
Since I am able to run an MPI hello_c binary on the remote host, I believe
the host has all the necessary libraries needed for MPI.
Hi,
I'm new on this list. I'm using MPI for years but I don't have written a
lot of code with MPI. Therefore is my question perhaps ridiculous:
I'm using a Computational Fluid Mechanics (CFD) Solver. This Solver uses
MPI to exchange the data between the different partitions. In this
solver the "r
