-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supplemental instructions to install MPI compiler #161
Comments
Hi @blakeaw, thank you for pointing this out. I have been relying implicitly on the having the sudo apt-get update -y
sudo apt-get install -y libhdf5-openmpi-dev python3-mpi4py as described in the documentation installs the MPI compiler. But here, probably explicit is better than implicit; I will add sudo apt-get install libopenmpi-dev libopenmpi2 to the install docs when I get a chance. |
Ok, I see. Thanks! I'd also maybe recommend listing the dependencies first by moving the Install dependencies subsection to the front of the Installation section of the README (and similarly in the documentation). That way users see the dependencies (in particular, the non-python ones) and can make sure they are installed first before they try to install hymd itself. Also, if you rearrange you could probably move this line |
Hi @mortele, it looks good. Thanks. I'll go ahead and close. Just as a side note, as the warning in installation docs suggested I couldn't get mpi-enabled h5py to install with python 3.10. But there weren't any problems installing in a new conda environment with python 3.8. |
Hi,
This issue is part of the JOSS Review at openjournals/joss-reviews#4149
Since a MPI compiler is required for installation it might be good to include supplemental instructions for installing the compiler in case users don't already have one installed on their system. For example, I installed hymd in a WSL2 Ubuntu 20.04 instance which didn't have MPI compilers already. I ended up using the following for mpich:
And then installing mpi4py:
This comment may have some overlap with Issue #157.
The text was updated successfully, but these errors were encountered: