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

You are not logged in.

#1 Re: Code_Aster usage » contact interpénétration et questions diverses » 2019-05-26 07:46:50

J’effectuerais plutôt la simulation sur un pas de dent avec un incrément de temps faible afin de bien capter toutes les positions. Il est néanmoins possible d'effectuer la simulation sur 360° afin d'obtenir une "jolie animation". Ci-dessous le couple résistif est défini à l'aide d'une pression avec charge suiveuse pour générer un couple résistif d'où une concentration de contraintes. Le pas de temps est trop grand pour capter correctement les variations de couple (graphe à droite):


#2 Re: Code_Aster usage » No results when using SIEF » 2019-05-23 06:17:43

I don't know why but if I uncheck the reslin_SIEF_ELGA in Paraview it works:

Results Paraview


#3 Re: Code_Aster usage » contact interpénétration et questions diverses » 2019-05-02 06:27:20

vous avez mis une grande rigidité en rotation pour le P1:

GROUP_MA = ('P1',),

Les concentrations de contraintes ont l'air de disparaître en diminuant cette valeur.


#4 Re: Salome-Meca usage » Time set after running simulation » 2019-05-01 08:01:09

I asked the same question in 2017:

This issue is solved in the 2018 version.


#5 Re: Code_Aster usage » contact interpénétration et questions diverses » 2019-04-22 08:39:41

je pense qu'une modélisation C_PLAN est plus appropriée, cf. fichier comm ci-joint. Les contacts ont été modifiés (arrêtes-arrêtes).


#6 Re: Code_Aster usage » CALC_PRESSION and LAGS_C » 2019-03-29 06:33:01

Hello Manolo,
I don’t know why CALC_PRESSION  doesn’t give the same results than LAGS_C. Did you try with GEOMETRIE =  'DEFORMEE'  and  'INITIALE' ?

What I know is that it’s impossible to get a correct contact pressure with such a coarse mesh. The mesh must be very fine (10-20x finer I guess) in order to get close to the real area in contact. The finer you mesh it the closer you will get to the Hertz formulas.


#7 Re: Code_Aster usage » Contact-C_PLAN » 2019-03-20 18:33:48

You apply a displacement of 100 in one step so the body goes through the other one without contact:

No contact

#8 Re: Code_Aster usage » How to plot stress strain curve » 2019-02-23 11:32:03

Within CA or Paraview? Within CA I would do the following:

table1 = POST_RELEVE_T(ACTION=_F(GROUP_NO=('dispZ', ),
                                 OPERATION=('EXTRACTION', ),
                                 RESULTANTE=('DZ', ),

                                 NOM_CMP=('DZ', ),
                                 OPERATION=('EXTREMA', ),

tab01 = table1.EXTR_TABLE()
Forces = []
for l in tab01:
tab02 = table2.EXTR_TABLE()
dispMax = []
for l in tab02:
    if l['EXTREMA'] == 'MAXI_ABS':

import matplotlib.pyplot as plt
fig1, ax1 = plt.subplots(1, 1)
ax1.plot(dispMax, Forces, '-o')
ax1.set_xlabel('DEPL max')

#9 Re: Code_Aster usage » [SOLVED]Problem:the matrix is singular or almost singular.... » 2019-02-22 17:29:40

You can transform your STAT_NON_LINE to DYNA_NON_LINE keeping exactly the same boundary conditions and adding, for instance:


All the initial velocities and accelerations will be automatically set to zero.
Without damping your net will be oscillating forever so it will be hard to compare the results with the static analysis.
You can add damping either in the materials or use a dissipative scheme, for instance HHT with a low alpha-value, for instance -0.3. That should stabilize the net after a few oscillations.


#10 Re: Code_Aster usage » How to plot stress strain curve » 2019-02-17 07:28:13

table0 = POST_ELEM(MINMAX=_F(GROUP_MA=('v1', ),
                             NOM_CMP=('SIXX', ),

I tried this code with v1 containing only one 3D element and it works.

#11 Re: Code_Aster usage » How to plot stress strain curve » 2019-02-15 21:07:52

you can print the min/max values of the SIGM_ELGA with:

                             NOM_CMP=('SIXX', ),


You can also plot them, for instance:

tab01 = table0.EXTR_TABLE()

timeV = []
maxV = []
for l in tab01:

import matplotlib.pyplot as plt
fig1, ax1 = plt.subplots(1, 1)
ax1.plot(timeV, maxV, '-o')


#12 Re: Code_Aster usage » [SOLVED]Problem:the matrix is singular or almost singular.... » 2019-02-13 20:50:42

chenghui62000 wrote:

5. Is the thermal dilation coefficient is necessary during the material definition? I have deleted this parameter, and the simulation can still give the same results.

Useless because no thermal load.

chenghui62000 wrote:

6. The initial load (pre-tension, I think) is important for the simulation because it can avoid the singular matrix. But, it won't bring overestimation in the final results?

According to U4.42.01 §16.3:
"This keyword makes it possible to define an initial pre-tensioning allowing the convergence of
calculation into nonlinear (it is thus useless into linear). It is applied only to the first step of time. "
Therefore it does'nt affect the final result, you can try to modify this value, it has no effect.

chenghui62000 wrote:

7. There only two forces on the nodes are actually applied to the simulation, I could find the reason why. because I think I have applied all the three node forces in my comm file.

The force F3 is applied to the GROUP_NO F2.

#13 Re: Code_Aster usage » [solved] thickness for C_PLAN and D_PLAN » 2019-02-13 07:10:02

Hello nirmaljoshi,
it's not possible. What I usually do when I deal with several parts with different thicknesses is changing the Young's modulus. For instance:

part 1: thickness = 1.0: E = 200'000 MPa
part 2: thickness = 0.5: E = 100'000 MPa


#14 Re: Code_Aster usage » postprocess without re-running the whole analysis » 2019-02-06 11:37:23

You must click on stage 2 only. If it doesn't work that means you didn't save the base of the first analysis (Reusable) and that the results of the first stage don't exist anymore.

#15 Re: Code_Aster usage » postprocess without re-running the whole analysis » 2019-02-06 09:33:35

with Asterstudy:
The first analysis must have been done with "Reusable" in order to keep the base.

1-2) Add a new stage with the post-processing
3-4) Run only the new stage

Asterstudy poursuite


#16 Re: Code_Aster usage » [SOLVED]Problem:the matrix is singular or almost singular.... » 2019-02-04 22:32:13

nice! I tried to remove the gravity at the end of the simulation and it does converge. The gravity is really needed at the very beginning of the simulation, that was a good idea Jean-Pierre!

#17 Re: Code_Aster usage » [SOLVED]Problem:the matrix is singular or almost singular.... » 2019-02-03 22:53:57

Hello Jean-Pierre,
attached the original comm file, the modified ones and the mesh.



#18 Re: Code_Aster usage » [SOLVED]Problem:the matrix is singular or almost singular.... » 2019-02-03 07:51:38

I found dbpatankar's answer very interesting so I tried to run the analysis with DYNA_NON_LINE in order to overcome instabilities and understand the problem better.

The deformations seem correct with POU_D_T but not with BARRE elements:


I cannot figure out why the BARRE deformation is so strange, is it because of the vertical loads on horizontal elements? The deformations of the BARRE elements are huge, on the above picture I reduced the forces by 100 in order to be able to display it.


#19 Re: Code_Aster usage » Post-processing issues » 2019-01-01 22:34:44

Hello Anirudh,
this topic has been discussed in different posts, for instance:
https://code-aster.org/forum2/viewtopic … 012#p58012

It'a a pity to have to open the results twice but it's the only workaround I found.


#20 Re: Code_Aster usage » [solved] matrix factorization error and duplicate nodes » 2018-12-23 22:07:03

Hello Nirmaljoshi,
There is one DOF which is not constrained: the X rotation around the node 'supportnode'.

Even after adding a second node to 'supportnode' in order to constrain that DOF, the matrix remains singular.

I tried to re-mesh your geometry and it works. I don't know why your mesh doesn't work, there are some elements with poor aspect ratio (>6) but I don't think that should make the matrix singular.

I decreased your nodal force from 50000 to 50 because the deformation was huge.

I attach the old mesh, the modified mesh and the modified comm file.

Any ideas why the first mesh doesn't work are welcome.

Good luck,


#21 Re: Code_Aster usage » Facteur 1000 sur les résultats » 2018-12-12 07:12:46

à ma connaissance vous ne pouvez pas appliquer directement une force. Vous pouvez par contre calculer la longueur d'une arrête ou l'aire d'une surface avec une boucle Python. Ceci est expliqué dans le livre de Jean-Pierre Aubry au chapitre 17.4. Vous pouvez ensuite convertir votre force en force linéique ou surfacique.


#22 Re: Code_Aster usage » Facteur 1000 sur les résultats » 2018-12-09 07:03:27

il doit effectivement y avoir un problème d'unités. Ce serait plus facile avec le maillage et le code...


#24 Salome-Meca usage » Error when switching from text mode to graphical mode » 2018-12-03 18:51:56

Replies: 0

there are some typing errors, for instance a missing bracket before a list of GROUP_MA:
GROUP_MA='gr01', 'gr02')
which lead to the following error when switching to graphical mode:

Traceback (most recent call last):
  File "/home/konyaro/salome_meca/V2018.0.1_public/modules/ASTERSTUDY_201801/lib/python2.7/site-packages/asterstudy/gui/study.py", line 181, in try_call_except
    result = function(self, *args, **kwargs)
  File "/home/konyaro/salome_meca/V2018.0.1_public/modules/ASTERSTUDY_201801/lib/python2.7/site-packages/asterstudy/gui/study.py", line 1405, in setStageGraphicalMode
  File "/home/konyaro/salome_meca/V2018.0.1_public/modules/ASTERSTUDY_201801/lib/python2.7/site-packages/asterstudy/common/conversion.py", line 237, in get_errors
    exc = error.original_exception
AttributeError: 'exceptions.IndentationError' object has no attribute 'original_exception'

It's very annoying because the whole study is lost after this error.


#25 Re: Code_Aster usage » Higway Signal tutorial - a few questions » 2018-12-03 17:35:43

Paraview is a great tool but I agree that the MED-reader is not optimal:
-    The split of fields is hard to understand and to work with
-    The "Extract Group" filter behavior is weird, especially with 2D and 1D elements

I guess it is due to the MED-reader as it works very well with OpenFOAM results.

Board footer