# code_aster
**Repository Path**: yiestudio/code_aster
## Basic Information
- **Project Name**: code_aster
- **Description**: Partially copy from https://gitlab.com/codeaster/src.git
- **Primary Language**: Unknown
- **License**: GPL-3.0
- **Default Branch**: main
- **Homepage**: None
- **GVP Project**: No
## Statistics
- **Stars**: 0
- **Forks**: 0
- **Created**: 2026-08-25
- **Last Updated**: 2026-08-25
## Categories & Tags
**Categories**: Uncategorized
**Tags**: None
## README
# code_aster source files
[](https://codeaster.readthedocs.io/en/latest/?badge=latest)
[](https://github.com/psf/black)
> Home page:
>
> Forge:
**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.
## Content of the [src][1] repository
This repository contains the source files of code_aster and its build scripts.
Usually the repositories are cloned under `$HOME/dev/codeaster`.
## Branches and tags
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.
Each published version is tagged with its number. Examples: 15.4.8, 16.0.9.
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.
## Installation
code_aster needs some prerequisites.
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):
```bash
./waf configure --no-enable-all
./waf install -j 8
```
### Example
From the version 16.3.2 to the current development version, the container name
is [salome_meca-lgpl-2022.1.0-1-20221225-scibian-9.sif][5].
```bash
$ mkdir $HOME/containers && cd $HOME/containers
# download and the container image (.sif) here
$ singularity run --app install salome_meca-lgpl-2022.1.0-1-20221225-scibian-9.sif
# build code_aster in the container environment
$ cd $HOME/dev/codeaster/src
$ $HOME/containers/salome_meca-lgpl-2022.1.0-1-20221225-scibian-9 --shell
Singularity> ./waf configure install -j 8
# or, with the embeeded makefile
Singularity> make bootstrap
```
[1]: ../../../../src
[2]: ../../../../devtools
[3]: ../../../../changelog
[4]: https://gitlab.com/codeaster-opensource-documentation/opensource-installation-development
[5]: https://code-aster.org/FICHIERS/singularity/salome_meca-lgpl-2022.1.0-1-20221225-scibian-9.sif
[6]: https://gitlab.com/codeaster-opensource-documentation/opensource-installation-development/-/blob/main/install/install-code-aster-native.md
[9]: https://www.code-aster.org/