[GeoMechanicsApplication] Fixed a bug where the maximum number of iterations was not properly read #12354
Conversation
This file contains 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
In the C++ workflow for settlement analyses, the maximum number of iterations was read from setting "max_iteration", whereas we normally use "max_iterations" (mind the extra 's' at the end of the latter). Now the value is read from the expected setting (i.e. "max_iterations"). Note that a similar approach was already followed for the Python route.
WPK4FEM
approved these changes
May 7, 2024
rfaasse
approved these changes
May 8, 2024
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.
In the C++ workflow for settlement analyses, the maximum number of iterations was read from setting
"max_iteration", whereas we normally use"max_iterations"(mind the extrasat the end of the latter). Now the value is read from the expected setting (i.e."max_iterations").Note that a similar approach was already followed for the Python route.