2. Making contact#

It is obviously not a question of reading the entire user manual comprehensively. As of May 2011, it contains 338 documents (including 242 concerning the actual use of orders) representing thousands of physical pages. Many documents probably do not concern the user during the first modeling and calculation; it is however absolutely necessary to consult the documents describing the functionalities implementing this first modeling. This is for two reasons:

  • avoid errors of use,

but also, be aware of the possibilities of*Code_Aster similar to those that are sought (workarounds) and that could perhaps prove useful.

It is therefore advisable to consult the user documentation according to the approach proposed below.

2.1. Can Code_Aster deal with the subject of my problem?#

Four documents purport to answer this question. They are presented from the most synthetic to the most complete.

2.1.1. For a quick response#

Consult the pages of the brochure presenting the areas of code modeling, on the Product section website, where the physical phenomena that can be modeled by the code are summarily described.

2.1.2. For a more detailed answer#

Consult the document [U1.02.00] Introduction to Code_Aster, in particular chapters 1.3 (Phenomena, modeling, finite elements and behaviors) and 1.4 (Several methods of analysis) where the phenomena that can be modelled by the code are described synthetically.

2.1.3. For a more up-to-date answer (taking into account the latest developments)#

Consult the slides of the last presentation of new code features at the annual Code_Aster User Day on the date of publication of this document: Product section of the website.

2.1.4. For an even more developed answer…#

This is a field of questioning where the answer can no longer be directly provided by objects present on the document server. For example, the answer may be OUI and consist of modeling subtleties or modeling convoluted paths. In any case, it is aimed at users who are already aware. The service AOM (A helps with the O optimization of M modeling) of Feedback (REX) makes it possible to submit to the Aster Development Team (EDA) a particular modeling problem to be implemented with Aster resources. A person from EDA is then responsible for helping the applicant to carry out the modeling.

2.2. Has Code_Aster already dealt with a similar (neighboring) problem to mine?#

Two paths are proposed: the path of elementary test cases, the path of industrial applications.

2.2.1. Elementary test cases#

The test case database associated with Code_Aster is provided with local installations or can be viewed on the centralized server. These tests serve three purposes:

  • the verification of programmed models by comparison with reference solutions (analytical or calculated);

  • the computer verification of Code_Aster: the exhaustive coverage of computer paths, the verification of the non-regression of operation when porting to different system solutions.

  • the educational presentation of simple implementations: small studies that are quickly understood by reading the command files and associated validation documents (V).

It is this third function of test cases that we are talking about here. The user will see if an elementary test case treats a problem similar to his own: Document server, section VALIDATION/Test Cases By Names, the list of documentation of the names of the test cases (classified by field of application) is displayed as well as their titles, or else, the Usage/Examples section of the site.

2.2.2. Industrial studies#

A number of industrial studies (applications), carried out using Code_Aster, were presented at the annual user day.

These documented studies are available on the site, Product/Applications section. It contains the collection of studies sheets from the periodical ASTER echoes since its creation (10/91, 39 issues published on 01/2003) and a collection of industrial studies in all areas of code modeling presented at the annual*Code_Aster days.