Make mpi4py optional #268
Open
Make mpi4py optional #268
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looking at removing the requirement for mpi4py (making it optional), following user discussions.
For:
Installing mpi4py can be problematic and is often not needed.
Against:
An argument for keeping it might be that even if you don't use it, many of the examples including most of the example simulators (every case that uses the template evaluator) uses libEnsemble’s MPI executor and therefore requires an MPI. So we could make MPI a required dependency, but then might it be just as simple to keep mpi4py required?
I have not updated the platform Specific Instructions