2/4/2018 Workflow for a Code-Aster simulation - Code Aster

Contact Legal Notice Privacy policy

Enter search term

About us Code-Aster Services References Project Cases

Workflow for a Code-Aster simulation Our Seminars & Training

Why use Code-Aster?
There are many ways to perform the sequence of a simulation: preparing the
Windows or Linux? Code-Aster, Introduction (05 -
geometry, creating the mesh, analysing the model, postprocessing. And perhaps you
Installing Code-Aster 09 Feb 2018)
wish also to fill in software-driven a template for a report with your analysis results.
Workflow for a Code-Aster Read more …
simulation We describe here briefly only one of these ways. Thereby we seek to keep as much as
How do I start to learn possible seperated and independent the several tasks. So we start them all from the
Code-Aster? Linux Shell and do not use SalomeMeca's Aster module to setup and run an analysis. Code-Aster Dynamic Analysis
Installation Issues (01 - 02 March 2018)

Read more …
Read more…
This means that you do not need to have installed the SalomeMeca package. It is
sufficient to have a Code-Aster and a Salome installation. View all Seminars & Training…

Moreover if you use a different mesher and postprocessing tool then you even do not
need Salome. But you must procure translators for the mesh conversion and/or for Our latest Project Cases
reading Code-Aster's output files or you must insert suitable code in the Code-Aster
2016-10-05
command file to procure for the translation.

1. Start SalomeMeca (or Salome):

/opt/SALOME-MECA-2014.1/appli_V7_3_0/runSalomeMeca
Simulation of concrete creep
The path where runSalomeMeca and the other programs reside may be different in and shrinkage (MFPA Leipzig)

your installation. Read more …

2016-03-21
2. In Salome (or SalomeMeca) open the Geometry module
Then import an existing geometry in .step or .brep-format (Menu: File - import) or
create your geometry step-by-step starting with Menu: New Entity. When ready explore
your geometry with Menu: Measures - What is?. This informs you about the
"SubShapes" contained in your geometry object. Example: for a cube solid you will find MAGNA Steyr Fuel Systems
compares elapsed time: Code-
the follwing SubShapes: 1 shell (closed hull composed of 8 faces), 8 faces, 6 wires Aster versus Nastran
(closed sequence of lines enclosing a face), 12 lines, 8 vertices.
Read more …

2015-10-14
3. Change in Salome (or SalomeMeca) to the Mesh module
Create the mesh based on your geometry (Menu: Mesh - Create Mesh). The mesh
knows only the element topology (SEG2, QUAD8, TETRA4, HEXA8-elements and many
others,..) but does not contain any information about materials, properties (plate
thicknesses, beam cross section etc.) or loads. Therefore it is necessary to create
groups (of nodes and/or elements) to be included in the mesh definition.

Mazars model for historical

Read more… masonry
Read more …

4. Beside the Mesh you need a second input file: the command-file (.comm)
This is a file in ASCI-format containing a sequence of Code-Aster commands. During Read all Project Cases…
the Code-Aster run these commands will be processed successively in order to

http://www.code-aster.de/workflow-for-a-code-aster-simulation.html 1/2
2/4/2018 Workflow for a Code-Aster simulation - Code Aster
perform the desired analysis steps. The commands perform tasks such as reading the
mesh file from the hard disk (LIRE_MAILLAGE), assigning materials to groups of
elements or to the whole mesh (AFFE_MATERIAU), assigning loads and boundary
conditions to groups of nodes or elements (AFFE_CHAR_MECA), starting the solver for
a linear mechanical analysis (MECA_STATIQUE), and so on. A novice in Code-Aster, but
also an experienced user will never know the vast quantity of Code-Aster commands
and all their options. That's why the developpers of Code-Aster have created a very
nice tool: eficas, the Code-Aster command editor:

/opt/SALOME-MECA-2014.1/appli_V7_3_0/runSession eficasQt

When using eficas to create your command file you are protected from writing wrong
syntax or from arranging commands in a wrong sequence.

Read more…

5. Next you need an export-file (.export)

Basically the .export-file contains a list of the names of all files - input and output
files - participating at the Code-Aster run. The tool to create the export-file is astk:

/opt/SALOME-MECA-2014.1/appli_V7_3_0/runSession astk

It is common and practical - but of course not exhaustive - to include at least two
input files: .med (mesh in med-format) and .comm, and three output-files: .resu(lt),
.mess(age) and .rmed(results in .med-format)

Read more…

6. Now start the analysis:

/opt/SALOME-MECA-2014.1/appli_V7_3_0/runSession as_run yourfile.export

If the analysis runs well (generally it does not at the beginning!) you will find all
output files on your hard disk.

Read more…

7. Postprocessing
Let's hope that you have inserted the command IMPR_RESU (print result to output file)
in your command file after the solver command. Depending on the format
specification (FORMAT='MED' or FORMAT='RESULTAT') given in IMPR_RESU the results
will be printed to the .rmed-file or in ASCI-Format to the .resu-File. The .rmed-file can
be opened in a graphical postprocessor such as

the ParaViS module of SalomeMeca, or

gmsh

where you can create the usual plots of the deformed structure, vanMises stresses
and so on.

Read more…

Ingenieurbüro für Mechanik · Dr.-Ing. Johannes Ackva · Markgrafenstrasse 21 · D 91717 Wassertrüdingen · Phone: +49 (0)9832 708152 · code-aster@code-aster.de

http://www.code-aster.de/workflow-for-a-code-aster-simulation.html 2/2