Elmer Discussion Forum

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

By "nothing non-linear" I meant I thought the displacements were to small too reach the large displacement theory,
Yes ElasticSolver is using the large deflection formulation

According to the manual
Large Deflection = False

only shows up in the shell solver, not ElasticSolver

On the mortar condition there needs to be BC surfaces at the interface. Loading the mesh into ElmerGUI there are only 10 boundary surfaces all on the top faces of the surface.
I can't change this without the stp file.

The outer edge seams to conform, but the inner edge does not

MAIN: Number of timesteps to be saved: 1 CalculateMeshPieces: Number of separate pieces in mesh is 13 ERROR:: CalculateMeshPieces: Number of pieces differ from the requested 1 STOP 1 You have 13 separate pieces To check for a conforming mesh, add this statement to the simulation section of a sif: De...

Whenever post is solver 1 and magdyn is solver 2, post goes first before magdyn runs. So it is trying to calculate the fields before the whitney solver runs

Your mesh looks good, and they are second order elements, all should be fine. I assume that your iterative solver did not truly converge, leaving the answer a little short. For solid mechanics I avoid that by using direct methods, there are three available. No worries about convergence when solving ...

Then data will not be shared since Elmer shares data through the nodes. A conforming mesh isn't absolutely required but you can use mortar conditions to join the two boundaries. If there are coincident nodes causing the break the the nodes can be merged in Salome or ElmerGrid ElmerGrid 8 2 my.unv -a...

Then data will not be shared since Elmer shares data through the nodes. A conforming mesh isn't absolutely required but you can use mortar conditions to join the two boundaries. If there are coincident nodes causing the break the the nodes can be merged in Salome or ElmerGrid ElmerGrid 8 2 my.unv -a...

I just change it from iterative solver to direct and it ran much quicker, obviously Linear System Solver = Direct !Iterative Linear System Direct Method = Mumps Windows version may not have Mumps, but it would have banded or umfpack. Direct may run out of memory, in which case you are stuck with the...