Home | Project | Software | Gallery | News | Development | Use | Documentation | Search/Ask
 
Use
Guidelines
Restricted acces either to user or developer of elsA Advice
Restricted acces either to user or developer of elsA Utilities
Restricted acces either to user or developer of elsA Known bugs
Restricted acces either to user or developer of elsA Problem processing
Installation
Validation tool
 
Site jumps
Validation ref.
User news
Restricted acces either to user or developer of elsA Problem report
 
 
© 1999-2016 ONERA Terms of use
  

Installation of elsA

Here follow overall directions to build elsA from the source code or to properly install an already built binary distribution. For a more detailed description refer to chapter 2 "How to install elsA" of the document Development process tutorial.
For your first use of an executable, see the User's Starting Guide.

Please replace the vx.y strings you find below with the release number of your delivery.

Installing Python

The elsA use requires the Python interpreter. A complete installation of Python release 2.2 or higher is necessary. The Python Web site provides download pages and instructions for installation which is staightforward (see also Development process tutorial chapter 2.1.1.4).

Workspace for installation from source

You must first choose a working directory, let us say Some_Work_Directory, with at least 50 MegaBytes available. You must set environment variable ELSAWKSP : S-01 $ export ELSAWKSP=Some_Work_Directory
(Above, the numbers refer to the line number and the $ sign is the shell prompt.)

The directory tree containing elsA source code with top directory named Kernel has to be copied in the ELSAWKSP directory. For instance from a Unix tarball : S-02 $ cd $ELSAWKSP
S-03 $ gunzip elsA-vx.y.src.tar.gz
S-04 $ tar xf elsA-vx.y.src.tar

Build and install

S-05 $ cd $ELSAWKSP/Kernel
You have to indicate where the Python interpreter is located.
For instance, if it is in /usr/local/bin, you set the E_PPREFIX, E_PPREFIX1 and E_PYVERSION environment variables as follows : S-06 $ export E_PPREFIX=/usr/local/
S-07 $ export E_PPREFIX1=/usr/local/
S-08 $ export E_PYVERSION=2.2

Set the ELSAPROD variable which must be a concatenation of a prefix specifying the platform and one or several optional suffixes. Examples of valid ELSAPROD are as follows : S-09 $ export ELSAPROD=sgi_32
S-09 $ export ELSAPROD=hp_r8_mpi
S-09 $ export ELSAPROD=ibm_dbg

Now you can build the elsA executable : S-10 $ make -f cfg/Makefile.mk elsa
For a complete installation, you may "install" the executable and the Python runtime configuration files. You then have to define the ELSADIST variable which defines the installation directory that can be different from ELSAWKSP directory (in the example below it is the same). S-11 $ export ELSADIST=$ELSAWKSP
S-12 $ make install
S-13 $ rm -rf $ELSAWKSP/Kernel

All the necessary files to run elsA are now in the directory $ELSADIST/Dist.

From binary

Binaries should be extracted and expanded in the same current directory, let us say MyDirectory, where a sub-directory elsA-vx.y/Dist will be created : B-01 $ cd MyDirectory
B-02 $ gunzip Dist-vx.y.prod.tar.gz
B-03 $ tar xf Dist-vx.y.prod.tar

Test

To use the installed version (either from source or from binary distribution) you have to set environment variables. The first one ELSAHOME will give the directory which contains the sub-directory Dist. You must also specify where the elsA Python files are located with the PYHONPATH variable. You set the ELSAPROD variable, and you may adjust your PATH to use directly the elsA executable with no path indication. If you run a shared executable, you must also set the LD_LIBRARY_PATH variable. Furthermore, if the Python installations used to create elsA executable and to run it are not the same (for instance not on the same computer), you may have to set the PYTHONHOME variable : give the path of the directory containing the sub-directory bin of the Python installation used to run elsA. T-01 $ export ELSAHOME=DistUpDirectory
T-02 $ export PYTHONPATH=$ELSAHOME/Dist/lib/py
T-03 $ export ELSAPROD=Prod
T-04 $ export PATH=$PATH:$ELSAHOME/Dist/bin/$ELSAPROD
(T-05 $ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:$ELSAHOME/Dist/bin/$ELSAPROD)
(T-06 $ export PYTHONHOME=binUpDirectory)

And then you may check your installation and environment by running elsA with the plain Python script file sh_cart_2blk.py : T-07 $ elsA sh_cart_2blk.py
You may compare the ouput with this one.

(updated $Date: 2016/04/28 13:06:54 $)Home Site map Contacts