1. code_aster
  2. codeaster-src

Source

codeaster-src /

Filename Size Date modified Message
astest
bibc
bibcxx
bibfor
bibpyt
catalo
catapy
data
doc
i18n
mfront
wafcfg
waftools
115 B
[repo] change encoding to utf-8 and end of line for all source files
31.9 KB
Added tag 13.2.7 for changeset 56c0272007a0
5.9 KB
[#23678] Rename, remove test-cases linked to COQUE_*_PLAN
35.1 KB
[repo] major repository maintenance: fortran source files in free format
1.9 KB
[repo] update readme files
12 B
[repo] update to 7.0.1
16 B
[repo] update to 7.0.1
waf
590 B
[#25149] hide warnings from hg
99.7 KB
[#25149] wrap waf main script to automatically set environment
141 B
[#25149] wrap waf main script to automatically set environment
14.8 KB
[#25149] update to waf 1.8.22
home page:http://www.code-aster.org/
forge:https://bitbucket.org/code_aster/
dev documentation:
 https://bitbucket.org/code_aster/codeaster-src/src/default/doc/
user documentation:
 http://www.code-aster.org/V2/spip.php?rubrique5

Repositories

Code_Aster source files are stored into several repositories:

  • src: source files (C, fortran, python), most of the verification testcases and build scripts (~350MB)
  • validation: a few testcase files with non-public data (~1GB)
  • data: data about materials that can not be freely distributed
  • perf: this one containing some testcase files used for performance benchmarking.

Other independent repositories exist:

  • devtools: contains helper scripts for the developers

Branches and tags

The branches are:

  • default: currently version 13, the development branch where the current work goes
  • v12: version 12, the maintenance branch for the stable version 12
  • v11: version 10, the branch for the old stable version 11

Each published version is tagged with its number. Examples: 12.3.8, 13.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. 12.4.0).
  • testing: the latest frozen state of the development version in the development branch (ex. 13.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

Look at the doc/ directory in the source tree.