Code Aster

code aster source files are dispatched into 3 repositories. [src][1]: containing Python, C/C++, Fortran source files, its build scripts and most of the testcases, validation : few testcase files with proprietary data, data : material data that can not be freely distributed. Other independent repositories exist: [devtools][2]: contains helper scripts. [changelog][3]: publishes the changelog of each incremental version. This repository contains the source files of code aster and its build scripts. The branches are: main : The development branch where the current work goes. v15 : The maintenance branch for the stable versions. Only fixes are added, no new features. v14 : The branch of the old stable version. Not updated anymore. Two tags are used aliases and moved when new versions are published: stable : The latest frozen state of the stable version in the maintenance branch (ex. 15.5.0). testing : The latest frozen state of the development version in the development branch (ex. 16.1.0). Two names are often used in discussions to identify the code during its enhancements: unstable : The head of the development branch. stable-updates : The head of the maintenance branch. Singularity containers are available from the [website][9] in the section Download/salome meca. The current version salome meca and the prerequisites are provided in these containers. Of course the container must be updated each time that new prerequisites are required by the development version. See the [Installation and Development][4] documentation and its changelog page to select the correct image to be used. The prerequisites can be installed natively (see [Compiling code aster from scratch][6]). If one prerequisite is missing, one should use the option --no-enable-all during the configuration stage (by default all prerequisites are required/enabled):