imp
imp copied to clipboard
salilab
setup_environment.sh does not propagate mpirun path in $PATH
It is not clear that/why it should. It isn't passed to cmake anywhere, I think.
On Thu, Mar 6, 2014 at 10:42 AM, Yannick [email protected] wrote:
see title.
— Reply to this email directly or view it on GitHubhttps://github.com/salilab/imp/issues/759 .
no, but since the mpi module expects to use mpirun for some usages, it would make sense to use the mpirun version IMP was compiled agains.t
Le 06/03/14 20:05, drussel a écrit :
It is not clear that/why it should. It isn't passed to cmake anywhere, I think.
On Thu, Mar 6, 2014 at 10:42 AM, Yannick [email protected] wrote:
see title.
— Reply to this email directly or view it on GitHubhttps://github.com/salilab/imp/issues/759 .
— Reply to this email directly or view it on GitHub https://github.com/salilab/imp/issues/759#issuecomment-36923929.
It looks like FindMPI.cmake defines MPIEXEC. We could split that and add where it is to the IMP_PATH.
Usual practice is to put user-desired tools after the setup script, e.g. setup_environment.sh mpirun my_imp_mpi_script
Tests of the IMP.mpi module use MPIEXEC to run parallel tests.
