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
Problem with Time-dependent Prescribed Displacement and Implicit Solver #23
Comments
It seems like there is an error in the calculation of the forces, because all vectors for the calculation of the residuals are 0 (a, force and externalForce) in line 3372 in Peridigm.cpp. |
@raedma: Did you solve the problem? I have the same issue. Is there probably an example how to use the implicit solver in Peridigm? |
I did not have time to look at the problem in detail yet. |
I experienced the same problem, but with all kind of solvers. |
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days. |
This issue was closed because it has been stalled for 5 days with no activity. |
Hello,
recently, I wanted to perform a simulation of a tensile test with a constant velocity boundary condition. Here is only the specific boundary condition part of the input deck:
on one end of the model. The calculation works fine as long as I use the Verlet or QuasiStatic solver. However, whenever I try to use to Implicit time integration, nothing happens, specifically, no displacement is applied.
I tried to cross-check if this behavior is specific to my problem. Therefore I used the “Twist_and_Pull” model from the examples folder because it also uses time-dependent boundary conditions. I switched the time integration scheme in Solver1 from
to
While the QuasiStatic result is as expected, again, nothing happens for the Implicit time integration (residual=0). Here is a part of the log file:
Is is possible that there is a bug in the treatment of time in the application of boundary conditions in PeridigmNS::Peridigm::executeImplicit from Peridigm.cpp or am I missing something in the definition?
Regards
Martin
The text was updated successfully, but these errors were encountered: