code_aster from a developer's perspective

• You use code_aster as an end user, but as soon as you need to modify a constitutive law or add a computation option, you're stuck: you don't know where to look in the source code.
• You've tried to compile code_aster but the dependencies (Spack, external libraries, environment setup) gave you a hard time, and you can't quite tell what comes from Spack versus what actually belongs to code_aster.
• You want to contribute cleanly to the codebase (bug fixes, new developments, patches) but you don't master the full workflow: build, unit testing, non-regression testing, packaging.

One day, one complete workflow

You follow the full chain checkout → environment → build → modify → rebuild → test → package → run. Not a quick tour of the code, but a real end-to-end thread.

You get your hands in the code

Every theoretical step is immediately followed by hands-on work on the actual code_aster source, in Python as well as C++/Fortran. You leave with modifications you compiled and validated yourself.

Trainers who develop code_aster every day

Our engineers contribute to the codebase as part of industrial projects at Simvia. On site, they share best practices and pitfalls in real time — the kind you won't find in any documentation.

Close, hands-on supervision

Small group of trainees, with a trainer on hand to unblock anyone stuck during the hands-on work.

From dev environment to HPC delivery

You leave able to build a Docker image, convert it for Apptainer/Singularity, and run a verification job on your cluster.

• Industry: engineers and developers who want to contribute to the code_aster codebase, package deliverables, or deploy the code on HPC.
• Academia: researchers and PhD students developing their own features within code_aster.

Solid practice of code_aster as an end user (commands, catalogs). Basic notions of Python and C++/Fortran are helpful. No prior compilation experience required.