-
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
Avoid dying on failed contact point searches #28148
Labels
C: Framework
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: defect
An anomaly, which is anything that deviates from expectations.
Comments
GiudGiud
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
Jul 16, 2024
GiudGiud
added a commit
to GiudGiud/moose
that referenced
this issue
Jul 16, 2024
Dont die horribly when it fails refs idaholab#28148
roystgnr
added a commit
to roystgnr/moose
that referenced
this issue
Jul 19, 2024
Hopefully this fixes our new valgrind errors in next, in a bug apparently introduced by idaholab#28149. Refs idaholab#28148 This code really needs an overhaul to get rid of new/delete everywhere, but I'm trying to make a minimal fix here to get next working ASAP.
N4hom
pushed a commit
to N4hom/moose
that referenced
this issue
Jul 30, 2024
Dont die horribly when it fails refs idaholab#28148
N4hom
pushed a commit
to N4hom/moose
that referenced
this issue
Jul 30, 2024
Hopefully this fixes our new valgrind errors in next, in a bug apparently introduced by idaholab#28149. Refs idaholab#28148 This code really needs an overhaul to get rid of new/delete everywhere, but I'm trying to make a minimal fix here to get next working ASAP.
TheGreatCid
pushed a commit
to TheGreatCid/moose
that referenced
this issue
Aug 1, 2024
Dont die horribly when it fails refs idaholab#28148
TheGreatCid
pushed a commit
to TheGreatCid/moose
that referenced
this issue
Aug 1, 2024
Hopefully this fixes our new valgrind errors in next, in a bug apparently introduced by idaholab#28149. Refs idaholab#28148 This code really needs an overhaul to get rid of new/delete everywhere, but I'm trying to make a minimal fix here to get next working ASAP.
TheGreatCid
pushed a commit
to TheGreatCid/moose
that referenced
this issue
Aug 14, 2024
Dont die horribly when it fails refs idaholab#28148
TheGreatCid
pushed a commit
to TheGreatCid/moose
that referenced
this issue
Aug 14, 2024
Hopefully this fixes our new valgrind errors in next, in a bug apparently introduced by idaholab#28149. Refs idaholab#28148 This code really needs an overhaul to get rid of new/delete everywhere, but I'm trying to make a minimal fix here to get next working ASAP.
Leni-Yeo
pushed a commit
to Leni-Yeo/moose
that referenced
this issue
Aug 28, 2024
Dont die horribly when it fails refs idaholab#28148
Leni-Yeo
pushed a commit
to Leni-Yeo/moose
that referenced
this issue
Aug 28, 2024
Hopefully this fixes our new valgrind errors in next, in a bug apparently introduced by idaholab#28149. Refs idaholab#28148 This code really needs an overhaul to get rid of new/delete everywhere, but I'm trying to make a minimal fix here to get next working ASAP.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C: Framework
P: normal
A defect affecting operation with a low possibility of significantly affects.
T: defect
An anomaly, which is anything that deviates from expectations.
Bug Description
The Newton search in FindContactPoint can try to call reinit on an element side with a point that is way outside of the element.
This causes a libmesh error and crashes the initialization of the simulation
A warning instead of an error could be good enough to get the users to work more on their mesh
Steps to Reproduce
Run the input from this discussion (not_working.i)
#28091 (reply in thread)
or make a similar system
Input
Mesh is 3 cylinders with completely arbitrary hex8 meshes
Impact
User support needs
[Optional] Diagnostics
No response
The text was updated successfully, but these errors were encountered: