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

You are not logged in.

#1 Re: Code_Aster development » Call to RAPH_MECA in DYNA_NON_LINE vs STAT_NON_LINE » Today 08:29:34


There's a subtle difference between STAT_NON_LINE and DYNA_NON_LINE.
Static prediction is made by a direct calculation based on the stresses of the previous time step, without integrating the behavior law (option in code_aster: FORC_NODA).
Dynamic prediction is made by integrating the behavior law (option in code_aster: RAPH_MECA).
In general, there is no difference. But in your case, yes!

#2 Re: Code_Aster development » Error when running python inside code aster » 2023-12-01 17:31:24


Yes, since V15.3, there is no longer a limit on the size of variable names in code_aster.
Documents are not up to date.

#3 Re: Code_Aster usage » Errors/ none-identical beahviour on nonlinear (material/contact) calc » 2023-10-20 08:24:21


Reference about what ? Problem of non-convexity sur contact surface ? Non-uniqueness solution for Coulomb Friction ?

#4 Re: Code_Aster usage » Impression du fichier de commande (.comm) au début du fichier .mess » 2023-10-20 08:20:41

Ah oui, tu as raison JP, j'ai aussi l'écho dans le output !

J'aurais pas du écouter mon voisin de bureau !

#6 Re: Code_Aster usage » Impression du fichier de commande (.comm) au début du fichier .mess » 2023-10-17 18:18:05


Depuis la version 15.3, aster est un module Python, le superviseur n'existe plus.
De fait, quand on exécute un script Python, vous n'avez pas l'écho de ce que vous avez écrit.
Il n'y a donc plus l'écho "du fichier .comm" car ça n'a plus de sens

#7 Re: Code_Aster usage » PRES_REP / FORCE_COQUE command difference » 2023-10-14 07:51:56


It's the same load.
We've made PRES_REP do the same thing as FORCE_COQUE/PRES for plates.

#8 Re: Code_Aster usage » Gasket Material Law » 2023-10-05 20:31:15


Rubber and elastomer seals are extremely rare in the nuclear industry.

They are not very common materials, except for damping devices (e.g. earthquake and equipment vibration).

Most often, they are rigid joints, sometimes represented by a porous material.

If you need this kind os behaviour: ELAS_HYPER or MFront

#10 Re: Code_Aster installation » Where is Code_Aster (website) going? » 2023-09-22 14:52:33


Don't worry.
These are legitimate and very frequent questions.

We have to deploy our software on many different types of media. The best tool at the moment is containers. A container contains salome_meca, but there's nothing to stop you using only code_aster, especially in the case of problems such as graphics cards.
Internally, code is qualified on platforms such as Debian10. Soon Debian11.
You can always compile code_aster externally. The only difference is that we no longer make "aster-full" packages, which had become too time-consuming. There are many prerequisites for code-aster. The salome-meca container contains them all, with the guarantee that they'll work whatever happens.
In addition, the sources are updated every week (in fact, every day) on the Gitlab repository, so nothing has changed in that respect.

About the support. The answer is: no.
EDF is an electricity producer, not a software vendor.
Some companies have tried to set up this kind of service, but the problem is that the French market is too small and it's not profitable for them.

For a long time now, we've known that the only solution is for the open-source community to organize itself so that this kind of service can emerge.
It's possible, but it's difficult. Don't forget that a mechanical computation code is an extremely complex object on a restricted market. Look at the size and power of the software editors in this market (ANSYS, Dassault Systèmes, etC.). This is no coincidence...

#11 Re: Code_Aster installation » Where is Code_Aster (website) going? » 2023-09-22 07:23:58


ode_aster is even more developed and active than ever.
On the other hand, we don't have any time to devote to animating the free community, including the website. This was already the case 15 years ago, and the time was taken from people's personal time (evenings and weekends).
Now, it's mainly devoted to EDF industrial issues.
I'd also like to make two comments:
- 10 or 15 years ago, one or two questions a week was manageable. Now it's several dozen, and the questions are particularly difficult.
- code distribution and tools keep pace with modern developments: containers, use of Git. There will also be major changes in documentation.
Finally, I notice that the community can't organize itself. It's open-source code, and apart from a few notable exceptions (like our Italian friends), it's mostly a collection of isolated people who come in once to ask a couple of questions and then disappear. Nevertheless, as many people answer the questions with accuracy and enthusiasm, I think it's not very nice not to notice.

After many years of hard work by our historical fathers, users are getting organized on the industrial side, with co-development agreements, particularly in the nuclear sector, or via highly professional solutions such as SimScale. I invite you to follow the news we regularly post on LinkedIn (often at weekends too...).

#12 Re: Code_Aster usage » Does MAZARS really workfor 3D with Non-local? » 2023-09-16 07:51:36


Mazars' model doesn't fit EDF's needs. It's not robust enough.
We prefer other models.
We haven't done away with it yet, but we probably will soon.

#13 Re: Code_Aster usage » Manual for R7.01.30 RGI_BETON » 2023-09-15 13:50:03

This document is confidential and for EDF internal use only.

#14 Re: Code_Aster usage » DYNA_VIBRA- Space-time load applied node by node » 2023-09-15 13:46:19


Solution (in you mail box wink




Problem: create resuChar !

The most versatil way:

                     _F(CHAM_GD=presOne, INST=0.0, ),
                     _F(CHAM_GD=presTwo, INST=1.0, ),
                     _F(CHAM_GD=presThree, INST=2.0, ),
                    ) )

You have to create fields presOne, presTwo, etc...

# Rank of table in file
instOne = 1
                                                SEPARATEUR=' ');

presOne = CREA_CHAMP(OPERATION='EXTR',             

# Rank of table in file
instTwo = 2
                                                SEPARATEUR=' ');

presTwo = CREA_CHAMP(OPERATION='EXTR',             

Table file form:
K8       R       
A3       -100
A2       -200
A4       -300 
A1       -400
K8       R       
A3       -10
A2       -20
A4       -30 
A1       -40

#15 Re: Code_Aster usage » Calcul s'arrête sans explication » 2023-05-31 20:09:20

Hmmm ....

Your GROUP_MA='demi-cyl' is not correct.


demicyl                           2264   (without - )

Special characters as "-" or space are not a good idea

#16 Re: Salome-Meca installation » SalomeMeca singularity on MacOS » 2023-05-14 09:20:43

Hello !

Very nice ! Good job !

Many Mac users will be very happy!

#17 Re: Code_Aster usage » queries about case SSNP160 H2 diffusion » 2023-05-01 22:24:14


Answer is in the command file:

from code_aster.MacroCommands.Contrib.diffusion_H2 import (CHAMP_DETOILE,

in sources:

https://gitlab.com/codeaster/src/-/tree … ds/Contrib

THe file is diffusion_H2.py

#19 Re: Code_Aster usage » Code_ASTER for impact simulation » 2023-03-08 22:38:20


Please avoid off-topic discussions.
There is only simulation, mechanics and code_aster on this site.

Thank you all!

#20 Re: Code_Aster usage » [SOLVED] Forming Simulation|Remeshing of a Distorted Mesh with HOMMARD » 2023-03-07 19:57:16


You have some testcases about this strategy:
[V1.01.253] ZZZZ253 – Calcul non linéaire mécanique avec changement de maillage
[V6.03.158] SSNP158 - Adaptation de maillage en non-linéaire

#22 Re: Code_Aster usage » [SOLVED] NAFEMS-Test CGS-4 Behavior of CONTINUE-Contact with friction » 2023-02-14 14:19:29


Yes, this is a known issue

False results were noticed on a study for the penalized formulation of friction (for non-zero coefficients of friction of course). Risk of false results for this friction formulation pending instruction.

There are currently works to have a more reliable formulation.
The other methods (augmented Lagrangian) give correct results but do not always converge.

#23 Re: Code_Aster usage » Unknown operator: LIAISON_SOLIDE_SPH » 2023-01-04 16:53:50


I don't know these commands. They were developed by someone else in the community and I have no information on the subject.


#24 Re: Code_Aster usage » CODE ASTER Citation » 2022-12-12 23:58:58


Strange request !
Do you use code_aster in another field than science or engineering ?

#25 Re: Code_Aster usage » Unknown operator: LIAISON_SOLIDE_SPH » 2022-12-10 18:10:05


CALC_CHAMP with this syntax, LIAISON_SOLID_SPH and IMPR_FONC_MULT are not part of code_aster standard commands.