At 11:13 PM 7/13/2004, Damien Buie wrote:
>I have three question,
>
>1) I am at the beginning of the learning curve for mpi programming. I was
>wondering which of the two open source systems is better mpich2 or lam/mpi?
People I work with must support both. Even though supporting both with the
same application makes it impractical to use all the MPI2 features, either
may be "better" in a given situation. Lam appears to be simpler, at least
for the end user. I've run into situations where an application could be
static linked with lam, but not with mpich... When the simplification
includes not supporting faster interconnect on a cluster which has e.g.
both gigE and infiniband, there is an evident reason to choose the mpich2
family. With the changes in mpich2 being more recent, not all the problems
have been worked out of applications I'm involved with.
>2) I have installed the binary for maxosx on my workstation but it put the
>files in usr/local/bin, this is fine but it conflicts with the mpich2 that
>I had already installed. So how can I uninstall the lam/mpi program. Or
>what files are created in the lam/mpi installation.
I guess if you installed lam in /usr/local/bin, you would simply remove the
files it put there. Actually, I'm answering this to point out that it
seems better to make special directories when you will be needing multiple
MPI versions. For example, on the x86-64 OS, I might install the 32-bit
copy of lam in /usr/local/32/ so that I can switch between 32- and 64- bit
copies by adjusting PATH environments.
>3) Is it possible to run the lam/mpi with the xlf fortran compiler.
I would think so, as long as you have a working compatible C installed
along with it. gcc ought to do, although I don't know anyone who has
checked that. We gave up on this route, however, as people able to support
such a system seem able to pay the price for the IBM MPI, and aren't
interested in alternatives.
Tim Prince
|
