Upper case mpi4py communication in convergence controllers #343
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.
I am starting to merge back some of the changes I have in a development branch of mine, so expect some PRs in the upcoming days with random small things. This is one of them.
I ran into issues with the pipeline on GitHub behaving differently from my local machine and going to upper case communication in mpi4py solved that. It is a few more lines, but also should be faster because it does not pickle everything before sending because you have to specify a buffer yourself. There is still the option to do the lower case stuff and I believe it is still used in some places as well.
The tests for which this was relevant are not part of this PR and I don't actually know if the issue persists or has been solved by some updates. Anyways, I guess forgoing the pickling is enough to merit doing this.
The second small change is a different initial guess for RK methods. Instead of the initial conditions, they now use the last stage as recommended by Daniel.