Elmer Discussion Forum

I thought they were two independent bodies connected by springs, but apparently they share nodes at the boundary? That is a different problem than I thought.

I thought perhaps it was due to rigid body modes, ElasticSolve and StressSolve so not much like rigid body modes in a static solution. So I added some constraints to take out rigid body motion without impacting the results. ElasticSolve converged much faster, but still arrived at 0.0044 answer. I at...

I ran it and received the same error, not seen that error before floodfill is a programming function to fill an array typically by area. It must have something to do with the BCs These BCs do not throw the error Boundary Condition 1 Target Boundaries(3) = 4 5 6 Name = "cube_4_faces" AV {e}...

The whole case is here
https://github.com/mrkearden/case

Solution with conforming mesh

You can use Salome to import the stp file which comes in as one solid, but use the explode command to show that it is really 13 different solids (or bodies) in Elmer. The goal would be to merge these 13 into one sold to obtain a conforming mesh, Or use the 13 to define mortar conditions. bodies.png

Mika is correct that the Large Deflection = False works in Elastic Solver when the UMAT subroutine is defined for the material.
Converges quickly to the desired answer regardless of number on non=linear iterations.

scanning in the case of elasticsolver is just a step solution where each step depends on the previous solution.

I did not do transient, I did scanning, which does not incorporate the acceleration or velocity terms.

If I run it in steps instead of steady state, the result path is not a linear line, there is a curve, a non-linear response This is with the
Large Deflection = False
which elastic solver ignores