Computing with Code_Aster: practice and requirement at LCR

Arnaud Delaplace

Date 2

Acquisition of a cluster (48 cores, up to 128 GB memory, 12 TB storage)

Personnal workstations

Partnership for numerical support with different companies (ALNEOS, LOGILAB, NECS...) and national and international universities

Human ressource dedicated to numerical management

LCR computational policy

Strong increase of the computation needs during the last years and for the next years

Date 3

Internal developments (python, C++...)

Code_Aster

Gmsh (mesh, postprocessing), SalomeMeca (advanced mesh), paraview (postprocessing)

When it's possible, open source softwares are preferred (traceability, support from the user community)

OS: Linux, windows

Softwares

Date 4

Open source policy (knowledge sharing, quality, minimizing the risk of using an internal FEM code)

Open code, unlike the “black box” concept of some commercial codes

Applications and materials are Civil Engeeniring oriented

THM/poromechanics already included

High capacity of personnalisation (python compatibility, macr_recal)

Parallel FEM software

Why LCR uses Code_Aster

Date 5

Model parameters identification,

Material optimization,

Reverse analysis of experimental tests,

Computation on structural systems

Application fields in FEM

Mainly based on geomaterials (Thermo-hydro-mechanical simulations, dynamic simulation...), at a material and/or at a structural scales

Date 6

Some examples

Design and optimization at material scale

Date 7

Some examples

Design and optimization at structural element scale

Date 8

Some examples

Design and optimization at structural scale

Date 9

Some examples

+ + +…

Mode 1 at 78 Hz Mode 2 at 105 Hz Mode 203 at 2004 Hz

+ …

Dynamic behaviour of studs

Date 10

A(n) (always) better documentation, in english

A more “user friendly” documentation

A link between Code_Aster subversion number and documentation reference

More documentation on the python modules

A set of examples, with postprocessing

A better version compatibility (or something like LTS versions)

A smoother syntax for beginners

A vtk compatibility

A radiation model

A partial light independent version (for light portable version of Code_Aster)

LCR requirements and hopes...