5. Print file and error messages

code_aster writes calculation information to a file that has the following meaning:

File	Content
MESSAGE	Information about the calculation process. Repetition of the command file, provided and its interpretation by code_aster. Fulfilment time for each order. Messages sent during execution, cf. below.

Other files are used to interface with graphics processing programs.

A distinction is made between different types of messages, which are described below.

Code	Message type
F	fatal error message, execution stops after various printings. The concept created by the current order is lost. However, the concepts produced previously are validated and the GLOBALEest database saved. It is used to detect serious errors that cannot allow the normal continuation of a Code_Aster command.
E	error message, the execution continues a little bit: this type of message makes it possible to analyze a series of errors before stopping the program. <F>*The emission of a type message* <E>*is always followed by the emission of a type* message. The product concepts are validated and the GLOBALEest database is available for a POURSUITE.
S	error message, the concepts created during the execution, including the current command, are validated by the supervisor, the execution stops with the “clean” closure of the database GLOBALE. It is therefore reusable in POURSUITE. In particular, this message makes it possible to avoid a convergence or time problem during an iterative process.
A	alarm message. The number of alarm messages is automatically limited to 5 identical sequent messages. Users with type A messages are recommended to “repair” their command file to make them disappear.
I	informational message for users. It is recommended to review the content of these messages, without requiring any modification of the command file or increased vigilance.

NB: exceptions behave exactly like errors<S>. They are in fact errors <S>adapted to a particular case.