Stop Simulation due to FORC_NODA

fabian0989 · 2019-11-08 13:57:55

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.

fabian0989 · 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?

AsterO'dactyle · 2019-11-14 22:45:49

Hello,

No, but you can't have a look at DEFI_LIST_INST/DELTA_GRANDEUR option.
Maybe another parameter (internal state variable, displacement or stress) could be equivalent to FORC_NODA in your case

fabian0989 · 2019-11-16 13:45:11

Hello,
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.

AsterO'dactyle · 2019-11-16 23:30:55

Hello,

Structure collapses => instability => matrix becomes singular ?

You can stop _correctly_ when matrix becomes singular, see forma03b for instance

GPSalachs · 2019-11-19 10:47:39

Have you tried any python scripting to save the results and see where the problem is?

#1 2019-11-08 13:57:55

Stop Simulation due to FORC_NODA

#2 2019-11-13 08:58:23

Re: Stop Simulation due to FORC_NODA

#3 2019-11-14 22:45:49

Re: Stop Simulation due to FORC_NODA

#4 2019-11-16 13:45:11

Re: Stop Simulation due to FORC_NODA

#5 2019-11-16 23:30:55

Re: Stop Simulation due to FORC_NODA

#6 2019-11-19 10:47:39

Re: Stop Simulation due to FORC_NODA

Board footer