Yes, it’s possible in text mode. The command files that are loaded this way can’t be edited using the graphical features.
However, Text stages and graphical stages may be mixed up. This enables the loading of Python intensive command files. In order to use existing concepts in the next graphical stages, one must use the concept editor (next to the embeded text editor or in stand alone).
Mathematical expressions written with Python (math module) do not prevent the edition in graphical mode.
When the reusable attribute is ticked for a stage, this means that the calculation may be restarted after such a stage.
The last executed stage is set to reusable by default. However, one can decide whether to keep the databases or not. It affects the way the computations are launched (the calculation is faster when reusable is not checked on intermediate stages as only one run of code_aster is launched).
When an objet is enriched (e.g. a mesh to which additional groups are added), this will cause it to appear several times in the combo-box with the name of the command which created it between braces.
When objects appear several times, the sort is done in decreasing order: the first item is the last modified one (result of the last enrichment).
It is an optional feature. One can choose whether to activate this feature globally in the Preferences, it may also be changed manually in each command edition panel (see User manual).
When this feature is enabled, the keywords used in Aster command language are replaced with a more understandable translation.
The content of this tab is refreshed with the textual output during calculations. This requires a ssh connection with the server, including when the calculation is run locally. In this case, the ssh connection to the local host as declared in JobManager (generally localhost) module must work without being asked for a password. When running computation on remote servers, the users must refresh the dashboard manually.
When encountering a bug, it is necessary to define a scenario to reproduce the problem. Please report the bug by describing the scenario and by attaching the needed files at https://bitbucket.org/code_aster/codeaster-src/issues, with reference to the asterstudy component.
For EDF users and partners, please use the usual bugtracker.