Dear Wolfgang,
thank you for your guidance, I did what you suggested. Basically all calls
in the system matrix construction have been removed but integration of unit
per each element, with zero rhs. To make the system solvable, (non-zero,
but it should be non relevant) Dirichlet boundary
Hi Alberto,
I might be having a similar or even the same problem with petsc! In my case,
the memory accumulated is proportional to the number of iterations done in the
SolverFGMRES solver. Also, when using trilinos (switch between petsc and
trilinos see step 40 I believe), this does not(!)
On 7/24/20 3:32 AM, Alberto Salvadori wrote:
It turns out that this code produces a memory loss, quite significant since I
am solving my system thousands of times, eventually inducing the run to fail.
I am not sure what is causing this issue and how to solve it, maybe more
experienced users
Dear community
I have written the simple code below for solving a system using PETSc,
having defined
Vector incremental_displacement;
Vector accumulated_displacement;
in the class LargeStrainMechanicalProblem_OneField.
It turns out that this code produces a memory loss, quite significant
