Added support for large strain in pyFANS #124
Draft
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.
Added support for large strain in pyFANS, by reading in the strain_type from the reader.
This will construct an appropriate version of MaterialManager and Solver.
The results are stored in std::variant to reduce code duplication.
Furthermore, fixed the MPI implementation when using pyFANS in micro-manager.
Issue was: when running micro-manager using MPI it will create its own processes and will manage MPI. Each resulting rank will then manage a series of pyFANS instances. However, when using pyFANS in such a setting, it "sees" that there are other ranks in MPI_COMM_WORLD and will attempt to communicate with them.
But this is wrong, as it should only run in a single rank.
Fixed by introducing a communicator variable, that is set to either MPI_COMM_WORLD or MPI_COMM_SELF.
Checklist:
CHANGELOG.md.