Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 1/12
Organization (S): EDF/MTI/MN
Handbook of Descriptif Informatique
D1.01 booklet: Environment of development and tools
D1.01.02 document
Environment of development on platform
autonomous: run_aster
Summary:
This document describes the environment of development on autonomous platform (SOLARIS, HPUX, IRIX,
linux or Windows NT 4). It comprises in particular a note of use of the procedure run_aster and
description of the files of associated parameters.
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 2/12
1
General and pre presentation required
1.1 Objectives
The constitution of a local version and the overload of Code_Aster, in addition to the traditional procedures of
compilation of the source code (C and FORTRAN) and of edition of the links, requires some operations
particular like the constitution of the catalogs compiled associated the process control language and
the description of the finite elements. Procedures of validation by the execution of a series of tests of
references constitute a point of passage essential to the validation of a development, with
less to ensure itself of nonthe regression.
The concern of ensuring the portability on various platforms and various operating systems has
conduit to write a whole of procedures presenting a minimum of adherence system. The choice
directed itself towards the language of script tcl, which ensures us a broad diffusion and makes it possible to touch with
the time the world Unix and Windows. The call of procedures not being really user-friendly, it seemed
useful to coat their calls, without to develop a complex interface. We thus have
chosen a simple means to call in a generic way various operations of construction and
of use of an executable room by using a single ordering and a file of parameter to words
keys easily éditable.
This document describes the various accessible operations, the syntax of the file of associated parameter,
like all the preliminary actions of organization of the sources and bookstores.
1.2 Pre
necessary
The target machine must make it possible to reach directly or by assembly of the type NFS the sources, with
bookstores and with the files of tests, it is not envisaged a distant access of type rsh, CCP under Unix. These
various files must be deposited under a fixed tree structure organized (under Unix) of
following way:
sources FORTRAN
bibfor/algeline
bibfor/algorith
bibfor/assembled
bibfor/calculel
bibfor/cataelem
bibfor/elements
jeveux bibfor/
bibfor/modelled
bibfor/postrele
bibfor/prepost
bibfor/soustruct
bibfor/stbtrias
bibfor/supervis
bibfor/utilifor
bibfor/utilitai
fermetur
sources C
bibc/algeline
bibc/include
bibc/supervis
bibc/utilitai
sources CATALOG
catapy/command
catalo/compelem
catalo/options
catalo/typelem
Python sources
bibpyt/Accas
bibpyt/Cata
bibpyt/Lecture_Cata_Ele
bibpyt/Superviseur
sources of the tests
tests/
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 3/12
The preliminary installation of software TCL/TK is necessary, all scripts of construction resting
on this language. In addition it is essential to have proceeded to the installation of version 2.1 of
python. The machine must have a compiler FORTRAN (FORTRAN 77 for Code_Aster) and
of a compiler C.
The linkage editing requires bookstores MED version 2.0 and HDF version 5.0 which will have to be built
au préalable using the procedure of provided installation.
bookstore MED
libmed.a
bookstores HDF
libhdf5.a
bookstore python
libpython2.1.a
TclTk bookstores
libtcl8.3.a libtk8.3.a libX11.a
bookstore BLAS *
/usr/lib64/libcomplib.sgimath.so
detection of the signals *
lfpe
* only under SGI IRIX64
1.3
Description of the result of the procedure of installation
The procedure of installation in addition to the source files described above, deposits scripts of
construction and some repertories under the repertory indicated at the time of the installation. The file of
configuration and script is adapted according to the provided information (compilers used,
bookstores,…).
scripts of launching
tcl/run_aster.tcl
tcl/aster.tcl
tcl/run
tcl/run_aster
tcl/conf/init_conf
tcl/make_aster
tcl/make_exec
tcl/make_cata
tcl/make_etude
tcl/make_lib
tcl/make_test
repertories of development
dvp/
(used by scripts)
dvp1/
dvp2/
The procedure run_aster consists of three command files tcl (aster.tcl,
run_aster.tcl and run) and of one (or several) file (S) of parameters (for example make_exec,
make_cata, make_etude…).
aster.tcl contains the various procedures tcl associated with each action.
run_aster.tcl contains the procedure of analysis of the file of parameter and a generic procedure
launching the calls to the various actions.
run makes it possible to coat the call with the preceding procedures directly since Shell script (Unix or
Windows) without passing by a Tcl window (of wish type).
Script run_aster makes it possible to position the environment python.
In addition, it is essential to provide a file of configuration describing the whole of
adherences related to the object computer (platforms SOLARIS, HP, IRIX, linux, or NT). It
file (tcl/conf/init_conf) makes it possible to indicate the various tools (compiler, linkage editor,
bookstores, etc), their access path and all options specific to the platform.
The execution of make_aster makes it possible to build a complete version of the code in nodebug mode or
debug and led to the creation of the following tree structure:
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 4/12
modules nodebug objects
obj/
obj_f/
modules debug objects
dbg/
dbg_f/
bookstores nodebug
lib_obj/lib_aster.lib
lib_obj/ferm.lib
lib_obj/asterm.obj
bookstores debug
lib_dbg/lib_aster.lib
lib_dbg/ferm.lib
lib_dbg/asterm.obj
executable nodebug
asteru.exe
executable debug
asterd.exe
catalogs compiled
elements
order/
cata_ele.pickled
2
Use of the procedure
2.1 General
The script of launching is coated in an executable file (run_aster under Unix,
run_aster.bat under Windows) calling Shell script tcl directly. This script must be launched on
object computer, possibly after connection in rlogin (under Unix).
% run_aster will mon_fichier_para
The file of parameters will mon_fichier_para is analyzed overall:
·
all that follows the character % is ignored,
·
the key words all are in small letters, their command is indifferent, but it is the last
occurrence in the file which is taken into account,
·
the key words are located on the left character: (the white are ignored around),
·
it has two types of key words:
- those being used to activate a task: make_aster, make_exec, make_cata,
make_lib, make_test, make_etude,… they carry out the various tasks in one
fixed command (key word action),
-
those being used to inform the files and the various parameters (key word parameter),
·
any line not containing a key word is ignored,
·
all the file names must be indicated in absolute.
The repertory or provided file names, are it always in absolute (for example
/home/used/mon_fichier_de_donnees.dat).
2.2
Description of the file of parameters
The symbol: separate the key word from the associated value. The key word action are all of the form
make_action or maj_action, they yes takes only the value or not. Key words
parameters depend on the key word action, they are described for each command in the paragraph
[§2.4].
Syntax is common to the whole of the key words action, except for the key word make_etude.
In this case, to inform the various result or data files associated with a study,
the key word is consisted of the name of the logical unit followed of at least one of the letters D or R indicating
that the file is in data or/and result.
Example:
fort.20 DR.: /home/to use/toto.mail
The key word rep_tcl is obligatory in any file of configuration, it makes it possible to charge them
various procedures appearing in the file aster.tcl.
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 5/12
2.3
Description of the file of configuration
This file makes it possible to define the various compilers, their localization, the parameters used, them
external bookstores and the bookstores system. It is a file with key words which follows the syntax of the files
parameters (one uses the same analyzer). There is no checking during the analysis of this file
of configuration, no key word is obligatory, the default value is put at ““(chain reduced to
a white).
Key word
Associated parameter
f77
file name
Compiler FORTRAN 77
DC
file name
Compiler C
lib
file name
Order filing of the bookstores
link
file name
Linkage editor
python
File name
Executable python (interpreter of commands python)
rep_incl
name of repertory
Contains the includes C; the file names must
to have the extension .h
opcc
character string
Described the options of compilation C
opcc_dbg
character string
Described the options of compilation C in debug mode
opf77
character string
Described the options of compilation FORTRAN
opf77_dbg character string
Described the options of compilation FORTRAN in mode
debug
path_hdf
name of repertory
Contains bookstores HDF
path_med
name of repertory
Contains bookstores MED
op_link
character string
Described the options of linkage editing
lib_sys
character string
List bookstores systems
lib_hdf
character string
List bookstores HDF
lib_med
character string
List bookstores MED
The file of configuration associated with the platform with installation (init_conf) belonged to
supply and is adapted at the time of the installation.
2.4
Description of the commands available
One describes the whole of the possible actions below, while specifying what is awaited behind each
key word. The key words must imperatively appear in the file of parameters, they can
if required to be assigned to the value ““(chain reduced to a white character).
In the tables below, one boldfaces the parameters which are likely to be
modified with each execution of script. In theory, the other parameters (type of platform,
localization of the sources/catalogs/Aster bookstores of reference, of scripts tcl, the files of
configuration) are unchanged from one execution to another and can thus be indicated once for
all.
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 6/12
2.4.1 Initial construction of a version of Code_Aster: make_aster
This procedure makes it possible to build the bookstores, executable modules and the catalogs
compiled reference. It is recommended to build the optimized version and the instrumented version
for the déboggage.
Key word
Associated parameter
make_aster yes
rep_tcl
name of repertory
Repertory containing the provided files tcl
fic_conf
file name
File of configuration specific to the platform
used
platform
IRIX, HPUX, SOLARIS, Punt-form targets (used for compilation
P_LINUX or PPRO_NT
conditional)
IRIX: platform SGI
HPUX: platform HP
SOLARIS: platform SUN
P_LINUX: linux on platform x86
PPRO_NT: Windows on platform x86
debug
debug or nodebug
debug: the sources are compiled in debug mode
(- G)
nodebug: the sources are compiled with the level
of optimization specified in the file of configuration
2.4.2 Construction of executable - a key word make_exec
This procedure makes it possible to constitute an executable module, by possibly overloading them
bookstores of reference by “personal” sources FORTRAN or C (added routines, or
modification of the routines of reference).
Key word
Associated parameter
make_exec yes
rep_tcl
name of repertory
Repertory containing the provided files tcl
fic_conf
file name
File of configuration specific to the platform
used
platform
IRIX, HPUX, SOLARIS, Punt-form targets (used for compilation
P_LINUX or PPRO_NT
conditional)
IRIX: platform SGI
HPUX: platform HP
SOLARIS: platform SUN
P_LINUX: linux on platform x86
PPRO_NT: Windows on platform x86
debug
debug or nodebug
Debug: the sources are compiled in debug mode (-
g)
nodebug: the sources are compiled with some
level of optimization
rep_ref
name of repertory
Repertory containing the bookstores and the environment
of execution of reference (obtained by make_aster)
source
list names of
Repertories containing the files FORTRAN and/or C
repertories
“personal” with which one wants to overload
version of reference. The file names must
to have the extension .f or .c. Various names of
repertories must separated by the character | .
rep_obj
name of repertory
Repertory containing of the modules user objects,
the files must have the extension .o (Unix) or
.obj (Windows)
rep_lib
name of repertory
Repertory containing of the bookstores user, them
files must have the extension .lib
exec
file name
Name of the produced executable file
The key words rep_obj and rep_lib are optional.
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 7/12
2.4.3 Construction of the catalogs compiled - key word make_cata
This procedure makes it possible to build the catalogs of commands and elements compiled to leave
catalogs of reference of Code_Aster and files catalogs sources (in complement or in
overload).
The operations of compilation of catalog is based on the presence of a card used at the time of
management of configuration on the machine of reference, it is thus essential to preserve this
card when it exists and to add it in new the catalogs.
Key word
Associated parameter
make_cata yes
rep_trav
name of repertory
repertory used during the execution of Code_Aster
(to compile the catalogs); this repertory is
normally destroyed at the end of the procedure
platform
IRIX, HPUX, SOLARIS, platform targets (used for compilation
P_LINUX or conditional PPRO_NT)
IRIX: platform SGI
HPUX: platform HP
SOLARIS: platform SUN
P_LINUX: linux on platform x86
PPRO_NT: Windows on platform x86
fic_conf
file name
file of configuration specific to the platform used
rep_tcl
name of repertory
repertory containing the provided files tcl
rep_catalo
name of repertory
repertory containing the tree structure of the sources of
catalogs of reference
catalo
list names of
file directory catalogs of elements
repertories
“personal” with which one wants to overload them
catalogs of reference.
For the catalogs of command, the names of
files must have the extension .capy and include
card # & MODIF or # & AJOUT.
For the catalogs of elements, the names of the files
must have the extension .cata and include the card
% & MODIF or % & AJOUT. Various names of
repertories must separated by the character | .
unigest
file name
File used during the management of configuration and
which one exploits lines CATSUPPR to destroy
catalogs of corresponding elements [D1.02.01]
exec
file name
name of the executable aster used to compile them
catalogs (it must exist)
rep_coco
name of repertory
catalog compiled commands produces
elco
file name
catalog compiled elements produces
Note:
The compilation of the catalogs of elements is an incremental operation which rests on
file cata_ele_pickled (built by make_aster).
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 8/12
2.4.4 Construction of a bookstore - key word make_lib
This procedure makes it possible to build a personal bookstore starting from source files (FORTRAN
or C).
Key word
Associated parameter
make_lib
yes
debug
debug or nodebug
debug: the source are compiled in debug mode (- G)
nodebug: the source are compiled with some
level of optimization
platform
IRIX, HPUX, SOLARIS, Punt-form targets (used for compilation
P_LINUX or conditional PPRO_NT)
IRIX: platform SGI
HPUX: platform HP
SOLARIS: platform SUN
P_LINUX: linux on platform x86
PPRO_NT: Windows on platform x86
fic_conf
file name
File of configuration specific to the platform
used
rep_tcl
name of repertory
Repertory containing the provided files tcl
source
list names of
Repertory containing the files FORTRAN and/or C
repertories
“personal” with which one wants to overload
version of reference. The file names must
to have the extension .f or .c (separated by 1 “L”)
rep_lib
name of repertory
Repertory recipient of the produced bookstore
lib_aster
name of the bookstore
Name of the produced bookstore deposited under rep_lib
2.4.5 Passage of a list of tests - key word make_test
This procedure makes it possible to launch a series of tests. A Aster test consists of a certain number
files (of which has minimum a command file and a file of parameters) whose names are
constituted starting from the name of the test and a suffix. The principal suffixes are as follows:
Suffix
Logical unit
Type of file
.comm fort.1
Aster commands
.mail fort.20
grid with the Aster format
.mgib fort.19
grid with the Gibi format
.msup fort.19
grid with the Ideas format
will.para -
parameters of execution
.mess fort.6
file MESSAGE
.resu fort.8
file RESULTAT
.erre fort.9
file ERREUR
.27 fort.27
associated data file for
this test with the logical unit 27
The file containing the list of the tests must contain a name of test per line, all that follows the character
% is ignored.
Key word
Associated parameter
make_test yes
rep_tcl
name of repertory
Repertory containing the provided files tcl
rep_trav
name of repertory
Repertory used during the execution of Code_Aster (for
to compile the catalogs); this repertory is normally
destroyed at the end of the procedure
liste_test file name
List tests with launching
rep_test
name of repertory
Repertory of the files of tests
rep_ref
name of repertory
Repertory of reference of the sources
rep_py
name of repertory
Sources
python overloading the environment
of execution
exec
file name
Name of executable used
rep_coco
name of repertory
Catalog compiled commands used
elco
file name
Catalog compiled elements used
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 9/12
2.4.6 Passage of a study - key word make_etude
This procedure makes it possible to launch a study. A Aster study consists of a certain number of
files for which it is necessary to associate a logical unit and an indicator D or R to specify if the file or
the repertory is in data and/or results. The parameters of execution passed overall
behind the key word para (the list perhaps obtained while launching the executable one with the parameter - H or
- help).
If the value of the key word make_etude is positioned with not, the repertory of execution is prepared with
there catalogs compiled, the environment python and data files in order to be able to launch
the debugger. During the execution of the procedure, the line of ordering of launching of the executable one
Code_Aster is displayed with all the parameters necessary.
Key word
Associated parameter
make_etude
yes or not
yes: the execution of Code_aster will be launched afterwards
recopy environment and data in
repertory of work.
not: the repertory of work is prepared in order to be able
to launch an execution with the debugger.
rep_tcl
name of repertory
Repertory containing the provided files tcl
rep_trav
name of repertory
Repertory used during the execution of Code_Aster (for
to compile the catalogs); this repertory is normally
destroyed at the end of the procedure
exec
file name
Name of executable used
rep_coco
name of repertory
The catalog of compiled commands contains used
elco
file name
Catalog compiled elements used
base
name of repertory
Repertory of greeting of the Aster base (given and
results)
d_base
name of repertory
Repertory of greeting of the Aster base (given
only)
r_base
name
of
repertory
Repertory of greeting of the base Aster (results
only)
d_ensi
name of repertory
File directory to the Ensight format in data
r_ensi
name of repertory
File directory to the Ensight format in results
para
character string
List parameters of execution
The various logical units are indicated in the following form:
fort.ij DR.: nom_de_fichier
where ij indicates the number of associated unit, at least one of the indicators D or R must be present.
Among the parameters of execution, it is essential to provide the size of the zone managed memory
dynamically during the execution, the unit used is the méga word of entirety.
- memjeveux 16 thus correspond to 64 méga bytes on a platform 32 bits.
2.5
Files of parameters delivered at the time of the installation
Several files of parameters directly usable are delivered under the repertory tcl at the time of
the installation, they were automatically adapted to the configuration of the user and can be
immediately last in parameter of the procedure run_aster.
make_aster
allows to build a complete version in debug mode or not of
bookstores, of executable and the catalogs compiled.
make_exec
allows to build executable starting from the source files FORTRAN and
C (extensions .f or .c) deposited under the repertories dvp1/and dvp2/, it
result is deposited under dvp/asteru.exe
make_cata
allows to build the catalogs of commands and elements compiled with
to leave the source files catalogs (extension .cata and .capy) deposited
under the repertory dvp/, the results are deposited under dvp/command and
dvp/elements
make_etude
allows to carry out an execution of Code_Aster with the files
asteru.exe, command and elements with the data deposited under
study/
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 10/12
make_test
allows to launch the execution of deposited under the repertory/study with
files asteru.exe, command and elements. The list of the tests used is
deposited in the file study/liste_ct.
make_lib
allows to build a bookstore starting from sources located under/dvp, it
result is deposited under/dvp/lib
These files can be recopied (like examples) then modified.
3 Example
of use
3.1
File of configuration on platform x86 under linux
% Fichier of configuration associates has aster.tcl
%
% PPRO_linux version with supervisor python
% ==================
%
f77: /usr/bin/g77
DC: /usr/bin/GCC
lib: /rear usr/bin/- rv
link: /usr/bin/g77
python: /usr/local/bin/python2.1
rep_incl: /home/aster/STA6.2/include
path_hdf: /home/aster/MED2.0/hdf/lib
path_med: /home/aster/MED2.0/lib
opcc: - C - I/usr/local/include/python2.1
opcc_dbg: - C - G - I/usr/local/include/python2.1
opf77: - C - O3
opf77_dbg: - C - G
op_link: - Xlinker - export-dynamic - lieee - ldl - lpthread - lutil
lib_sys: - L/usr/local/lib/python2.1/config - lpython2.1 - L/usr/local/lib - ltk8.3 - ltcl8.3 lX11
lib_hdf: /home/aster/MED2.0/hdf/lib/libhdf5.a - lm - lz
lib_med: /home/aster/MED2.0/lib/libmed.a
3.2 File of parameters used to build executable under
linux
% parameters obligatory:
% ==========================
rep_tcl: /home/aster/STA6.2/tcl
% construction of executable overloading bookstores:
% ==========================================================
fic_conf: /home/aster/STA6.2/tcl/conf/init_conf
make_exec: yes
source: /home/aster/STA6.2/dvp
rep_ref: /home/aster/STA6.2
exec: /home/aster/STA6.2/dvp/asteru.exe
debug: nodebug
platform: P_LINUX
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 11/12
3.3 File of parameters used to carry out an execution under
linux
obligatory parameters:
==========================
rep_tcl: /home/aster/STA6.2/tcl
construction of executable overloading bookstores:
===========================================================
fic_conf: /home/aster/STA6.2/tcl/conf/init_conf
make_etude: yes
rep_ref: /home/aster/STA6.2
rep_trav: /tmp/trav_aster
rep_coco: /home/aster/STA6.2/command
elco: /home/aster/STA6.2/elements
exec: /home/aster/STA6.2/dvp/asteru.exe
para: - memjeveux 16 - reference mark nun
fort.1 D: /home/aster/STA6.2/tests/ttnl100a. COM
fort.19 D: /home/aster/STA6.2/tests/ttnl100a. mgib
fort.6 R: /home/aster/STA6.2/tests/ttnl100a. mess
fort.8 R: /home/aster/STA6.2/tests/ttnl100a. resu
fort.9 R: /home/aster/STA6.2/tests/ttnl100a. wander
r_base: /home/aster/BASE
platform: P_LINUX
3.4
Example of call
% run_aster make_exec
% run_aster make_etude
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Code_Aster ®
Version
6.0
Titrate:
Environment of development on autonomous platform: run_aster Date:
05/02/02
Author (S):
Key J.P. LEFEBVRE
:
D1.01.02-B Page
: 12/12
Intentionally white left page.
Data-processing Descriptive handbook
D1.01 booklet: Environment of development and Outils
HI-75/01/005/A
Outline document