-
Hello, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
I found the following answer by Murphy-John on a similar problem: I recall having this issue in some of my models. I think it was caused by a boundary condition not applied correctly, so it may be worth reviewing your boundary conditions." |
Beta Was this translation helpful? Give feedback.
-
Hi, |
Beta Was this translation helpful? Give feedback.
I found the following answer by Murphy-John on a similar problem:
"This error occurs when the code cannot find a new element after the position of a Material Point is updated. I don't have much experience with this issue but you could use the debug feature in Visual Studio to locate which Material Point is causing the error and find out why it happened.
I recall having this issue in some of my models. I think it was caused by a boundary condition not applied correctly, so it may be worth reviewing your boundary conditions."
Also, Francesca Ceccato added:
"This error means that the algorithm could not find an element for a moving material point, maybe it is moving too fast (instability iss…