Just to clarify, as this is a frequent misconception: the statement that the absolute path will setup your remote environment is only true when using the rsh/ssh launcher. It is not true when running under a resource manager (e.g., SLURM, LSF, PBSPro, etc.). In those cases, it is up to the RM configuration as to whether or not the local environment is forwarded, and we have no control or influence over the remote path.
> On May 24, 2016, at 6:14 AM, Jeff Squyres (jsquyres) <jsquy...@cisco.com> > wrote: > > Doesn't Abaqus do its own environment setup? I.e., I'm *guessing* that you > should be able to set your environment startup files (e.g., $HOME/.bashrc) to > point your PATH / LD_LIBRARY_PATH to point to whichever MPI implementation > you want, and Abaqus will do whatever it needs to a) be independent of your > environment, and b) be able to function with whatever underlying MPI it wants > to use. > > This is a supposition on my part -- I am not an Abaqus user. > > Note, too that popular MPI implementations support a command line option such > that if you invoke the absolute path name of mpirun/mpiexec, it'll setup the > PATH / LD_LIBRARY_PATH on the remote servers to echo that of the local > server. E.g.: > > /path/to/open/mpi/install/bin/mpirun -np 4 --host a,b,c,d my_program > > >> On May 24, 2016, at 6:25 AM, Dave Love <d.l...@liverpool.ac.uk> wrote: >> >> Megdich Islem <megdich_is...@yahoo.fr> writes: >> >>> Yes, Empire does the fluid structure coupling. It couples OpenFoam (fluid >>> analysis) and Abaqus (structural analysis). >>> Does all the software need to have the same MPI architecture in order to >>> communicate ? >> >> I doubt it's doing that, and presumably you have no control over abaqus, >> which is a major source of pain here. >> >> You could wrap one (set of) program(s) in a script to set the >> appropriate environment before invoking the real program. That might be >> a bit painful if you need many of the OF components, but it should be >> straightforward to put scripts somewhere on PATH ahead of the real >> versions. >> >> On the other hand, it never ceases to amaze how difficult proprietary >> engineering applications make life on HPC systems; I could believe >> there's a catch. Also you (or systems people) normally want programs to >> use the system MPI, assuming that's been set up appropriately. >> _______________________________________________ >> users mailing list >> us...@open-mpi.org >> Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users >> Link to this post: >> http://www.open-mpi.org/community/lists/users/2016/05/29299.php > > > -- > Jeff Squyres > jsquy...@cisco.com > For corporate legal information go to: > http://www.cisco.com/web/about/doing_business/legal/cri/ > > _______________________________________________ > users mailing list > us...@open-mpi.org > Subscription: https://www.open-mpi.org/mailman/listinfo.cgi/users > Link to this post: > http://www.open-mpi.org/community/lists/users/2016/05/29302.php
