adding a context to StandardWellPrimaryVariables::checkFinite #6625
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
GitPaean
added
the
manual:irrelevant
GitPaean
force-pushed
the
context_check_finite
branch
from
7edc0e4 to
63ff06e
Compare
Member
Author
|
jenkins build this please |
GitPaean
force-pushed
the
context_check_finite
branch
from
63ff06e to
2f1a52c
Compare
so we can give some more information about where the non-finite primary variable is generated.
Member
Author
|
jenkins build this please |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
so we can give some more information about where the non-finite primary variable is generated.
it was spotted during working with #6621 .
we have two occasions where we check the non-finite primary variables, while the message is not clear when the non-finite primary variable is generated after the newton update.