Next: Remarks Concerning Samcef Up: Tips and Hints Previous: Remarks Concerning OpenFOAM Contents

##
Remarks Concerning Code Aster

From Paul CARRICO (2005/02/12)

Brief presentation of CODE ASTER: Code Aster is an implicit solver under GPL licence from the French company EDF (Electricité de France).

Code Aster and its documentations is downloadable at the following address:
http://www.code-aster.org
(NOTA : the documentation is in French at the moment but many users are translating it in English and in German)

The following list is not exhaustive but it briefly presents the capabilities of the solver:

- Mechanical modelisations: Code aster allows linear and non linear calculations in static, dynamic, acoustic etc. Many mechanical laws are implemented in the solver such as damage, fatigue, creep, viscosities (elastic, plastic) etc. For isotropic and non-isotropic materials (orthotropic ones for example). Because of EDF fields, the materials used in Code Aster are essentially Metallic ones and Geomaterial one, but there are probably some others.

- Thermal and thermomechanical calculations: The Thermal solver performs linear and non-linear calculations for pure thermal but also for thermomechanical simulations.

- Input interface: EFICAS is the input interface for coding the input file, but it's not a pre-processing as you can find in many commercial code.

- Tools: Many tools are provided with Code Aster: HOMARD for mesh refinement, GIBI and GMSH for post-processing.

CGX to ASTER export format (i.e HOWTO use this export format) The export format allows to export meshes and sets from CGX to Code Aster for linear and quadratic 1D, 2D and 3D eleme nts. For this, just type: 'send all aster' for exporting a complete mesh. The file will have the '.mail' extension. Type 'send set aster nam' for exporting the GROUP-NO (node group) and the GROUP-MA (mesh group) which compose the set. The file will have '.nam' extension

The later item is particularly useful to apply boundary conditions onto (DOF, pressure, force, displacement, temperature, etc.). Since of these boundary conditions are coded with EFICAS in the input file, I thought it was not necessary to develop another features than the 2 previous ones !

Next: Remarks Concerning Samcef Up: Tips and Hints Previous: Remarks Concerning OpenFOAM Contents