-
Notifications
You must be signed in to change notification settings - Fork 1k
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
NEML2 material model does not handle solve failure event correctly #27904
Comments
hugary1995
added
T: defect
An anomaly, which is anything that deviates from expectations.
P: normal
A defect affecting operation with a low possibility of significantly affects.
labels
Jun 14, 2024
hugary1995
added a commit
to hugary1995/moose
that referenced
this issue
Jun 14, 2024
- Add a SolveFailedInterface which is very similar to MeshChangedInterface. - Handle the solve failure event in ExecuteNEML2Model by rolling back stateful data. close idaholab#27904
hugary1995
added a commit
to hugary1995/moose
that referenced
this issue
Jun 22, 2024
kyleeswanson
pushed a commit
to kyleeswanson/moose
that referenced
this issue
Jun 25, 2024
jmeier
pushed a commit
to jmeier/moose
that referenced
this issue
Jun 26, 2024
abanki1
pushed a commit
to abanki1/moose
that referenced
this issue
Jul 11, 2024
N4hom
pushed a commit
to N4hom/moose
that referenced
this issue
Jul 30, 2024
Leni-Yeo
pushed a commit
to Leni-Yeo/moose
that referenced
this issue
Aug 28, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Description
When an FEM solve fails, NEML2 material model does not handle the roll-back of solution state correctly.
Steps to Reproduce
This can be easily seen by manually failing a time step using the Terminator.
Impact
This prevents us from getting the correct solution when a solve fails (or fingers crossed the solve never fails).
[Optional] Diagnostics
No response
The text was updated successfully, but these errors were encountered: