New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable Terminator to cut linear / nonlinear solves immediately #24479
Labels
Comments
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
… to date on evaluation refs idaholab#24479
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
… to date on evaluation refs idaholab#24479
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
… to date on evaluation refs idaholab#24479
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
May 25, 2023
Closing as completed by #24463 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reason
Asked for in email list eons ago
And recently:
Design
Use the "fail non linear check" mechanism
OR
Throw exception and catch it
Throwing is very disruptive, so better to just fail the next check
Impact
Faster recovery from bad solves
The text was updated successfully, but these errors were encountered: