Personal tools


From UABgrid Documentation

(Difference between revisions)
Jump to: navigation, search
(added category software)
Line 39: Line 39:
[[Category:Software]][[Category:Developer Tools]]

Latest revision as of 07:41, 6 April 2012

This page is a Generic stub.

You can help by expanding this page..

LAM/MPI is one of the predecessors of the Open MPI project. Open MPI represents a community-driven, next generation implementation of a Message Passing Interface (MPI) fundamentally designed upon a component architecture to make an extremely powerful platform for high-performance computing.

From the lam-mpi website:

LAM/MPI is now in a maintenance mode. Bug fixes and critical patches are still being applied, but little real "new" work is happening in LAM/MPI. This is a direct result of the LAM/MPI Team spending the vast majority of their time working on our next-generation MPI implementation -- Open MPI. Although LAM is not going to go away any time soon (we certainly would not abondon our user base!) -- the web pages, user lists, and all the other resources will continue to be available indefinitely -- we would encourage all users to try migrating to Open MPI. Since it's an MPI implementation, you should be able to simply recompile and re-link your applications to Open MPI -- they should "just work." Open MPI contains many features and performance enhancements that are not available in LAM/MPI.

Project website:

[edit] Load SGE module

The following Modules files should be loaded for this package (for LAM, you must load this module in your profile script and your job script):

For GNU:

module load lammpi/lam-7.1-gnu

For Intel:

module load lammpi/lam-7.1-intel

In order to use LAM-MPI you must load the module in your ~/.bashrc script along with your job submit script. Add the following to your ~/.bashrc (replace -intel with -gnu if using GNU):

For Bash Users edit ~/.bashrc:

module load lammpi/lam-7.1-intel

For Csh Users edit ~/.cshrc:

module load lammpi/lam-7.1-intel

Use the lam_loose_rsh parallel environment in your job script (example for a 4 slot job)

#$ -pe lam_loose_rsh 4