Welcome to the forums. Please post in English or French.

You are not logged in.

#1 Re: Code_Aster usage » Nonlinear Simulation of Shell Structure » 2019-12-05 14:26:29

Is there nobody who can help me? I'm gratefule for any feedback.

#2 Re: Code_Aster usage » Stop Simulation due to FORC_NODA » 2019-11-16 13:45:11

Thank you so much for your answer. But unfortunately another mechanical size doesn't work in my case. Briefly to the background: I perform a compression test of a shell structure. At a certain displacement the structure collapses and there is a drop in force. The exact time as well as the deformations and stresses at this time in my model are not known. For this reason, this point can only be identified by the force drop. After this force drop I would like to finish the simulation in a controlled way, because I am only interested in the maximum force.

#3 Re: Code_Aster usage » Nonlinear Simulation of Shell Structure » 2019-11-16 13:41:24

Hello jean pierre aubry,

I'm surprised the model doesn't work for you. I've just tested it again and it's starting to work for me (see attached file - i aborted it manually after startup).
I'm still a beginner with Code_Aster but already have a lot of experience with FEM (Abaqus/LSDyna/Optistruct). It would be nice if you could tell me what you think is wrong in the *.comm file - that was the question.
The mesh size may be very small, but it was validated in Abaqus by a mesh convergence study. Independently of this, I also ran the model with a coarser net in Code_Aster, which leads to much longer simulation times than in Abaqus or LSDyna.

#4 Re: Code_Aster usage » Stop Simulation due to FORC_NODA » 2019-11-13 08:58:23

Can't anybody help me?

In Abaqus there is this option via the urdfil subroutine. Is there anything similar in Code_Aster?

#5 Code_Aster usage » Nonlinear Simulation of Shell Structure » 2019-11-13 08:55:14

Replies: 4

Hello, everybody,
I'm in the process of calculating a shell structure under pressure. The simulation is also running, but the calculation time is very long. If I calculate the same model in Abaqus with the element type S4R the analysis takes about 4 minutes. In Code Aster the same simulation takes more than an hour.
Am I doing something wrong, or are the algorithms in Abaqus simply more efficient? I would be very grateful for tips.
The files of the simulation are attached.

Greetings Fabian
Windows 10
Salome-Meca 2019

#6 Code_Aster usage » Stop Simulation due to FORC_NODA » 2019-11-08 13:57:55

Replies: 5

Hello everybody,

there is the possibility to track the reaction force of a node during the simulation and to define a clean abort criterion for the simulation?

For example, if the force drop is more than 5% of the considered node.