> On Feb 27, 2015, at 6:42 AM, Sasso, John (GE Power & Water, Non-GE) > <john1.sa...@ge.com> wrote: > > Unfortunately, we have a few apps which use LAM/MPI instead of OpenMPI (and > this is something I have NO control over). I have been making an effort to > try and convince those who handle such apps to move over to LAM/MPI as it is > (as I understand it) no longer supported and end-of-life. In fact, the > website www.lam-mpi-org <http://www.lam-mpi-org/> is no longer accessible as > the domain name expired on 2/20/2015. > > Aside from a change of library paths in the Makefiles, I am assuming that > hardly any code changes would be needed for them to rebuild and run the code > with OpenMPI. Comments on this?
You are correct - the MPI calls will not change. You would probably need to update any scripts that run the jobs as “lamboot” doesn’t exist any more, but that’s about it > > Yeah, any other recommendations I can give to convince the powers-that-be > that immediate sun-setting of LAM/MPI would be great. Sometimes I feel like > I am trying to fit a square peg in a round hole L Other than the fact that LAM/MPI no longer is supported, the only real rationale would be that OMPI has a lot of enhancements in terms of binding options and other features, supports thru MPI-3, etc. > > --john > > _______________________________________________ > users mailing list > us...@open-mpi.org <mailto:us...@open-mpi.org> > Subscription: http://www.open-mpi.org/mailman/listinfo.cgi/users > <http://www.open-mpi.org/mailman/listinfo.cgi/users> > Link to this post: > http://www.open-mpi.org/community/lists/users/2015/02/26408.php > <http://www.open-mpi.org/community/lists/users/2015/02/26408.php>
