wiki:HowToInstall

Version 29 (modified by conty, 10 years ago) (diff)

Add new link for Debian packages

How to install OpenTURNS

This guide can be very usefull to install OpenTURNS on GNU/Linux. If you want a development version, please follow instructions which describe How-To install a development version.

Download

If you want to use OpenTURNS, it's highly recommended to pick up the lastest stable release.

Download the lastest OpenTURNS' release archive from SourceForge.net in the download section.

Dependencies

To compile your OpenTURNS platform, you need some additional libraries, headers (development files) and tools. Of course, you can use your favorite package-manager to download and install these requirements.

  • gcc (>= 3.3.6 except 4.0.x series, tested with 3.4.5, 3.4.6, 4.1.1, 4.1.2 & 4.2.2)
  • g77 (>= 3.3.6 except 4.0.x series, tested with 3.4.5, 3.4.6, 4.1.1, 4.1.2 & 4.2.2)
  • python (>= 2.4.x)
  • R (>= 2.4.x)
  • XercesC (>= 2.6.0, tested with 2.7.0)
  • boost (>= 1.33.1)
  • lapack (>= 3.0)
  • Qt (3.3.x)
  • python-qt if you want to use the embedded image viewer ViewImage (TUI only)

Specific instructions

Since 0.11.1, Debian and Ubuntu/Kubuntu/Xubuntu packages are provided by OpenTURNS team.

If you have one of theses distributions, you can follow the associated specific HowTo:

Unfortunetly, Debian Sarge package isn't support, you must follow this HowTo:

Note: RPM support is coming soon.

Frequently Asked Questions (FAQ)

You may see some more instructions here.

Generic instructions

As you can see with dependencies, OpenTURNS project use autotools and gcc suite to configure and build the sources.

Configure

In this example we use version 0.9.2, if you use another version, just substitute version numbers.

Extract files from downloaded archive :

tar xvzf openturns-0.9.2.tar.gz

if you use gzip compressor, or

tar xjvf openturns-0.9.2.tar.bz2

if you use bzip2 compressor.

Go in sources directory,

cd openturns-0.9.2

To allow OpenTURNS to communicate with R, you need to install the provided R package named rotRPackage:

R CMD INSTALL utils/rotRPackage_1.4.3.tar.gz

To configure building for all OpenTURNS parts - library, TUI, and GUI -, you can simply do:

./configure

but all will be installed in system directories (/usr, /etc) belonging to root. So if you want to install the platform in your own path, run:

./configure --prefix=/your/path

Warning : to compile 0.10.0 version with GCC on SSE2 capable processors, you need to disable SSE2 instructions :

./configure CXXFLAGS="-mno-sse2" 

The SSE2 support is activated by gcc by default on x86_64 architectures.

If you want to disable some parts (TUI, GUI, or both), take a look at

./configure --help

You can also see the options accepted by the sub-modules with:

./configure --help=recursive

Quick build & install

make
make install

Build & install with checks

We encourage you to run the checks before and after installing. Doing so will prevent you from installing a platform that doesn't run correctly (there may be bugs), but if all run successfully, you will have a great confidence in what you've installed.
It is true that running the check will take some time. On a hyperthreaded dual-2.4 GHz host, it will take about 25 minutes for the whole process = configuration + compilation + check tests + installation + installcheck tests.

You can take advantage of the parallel make in using the -j option followed by a number that represents the amount of concurrent compilations. On a 4-way SMP, try 'make -j4' instead of bare 'make'.

make
make check
make install
make installcheck

Post installation

OpenTURNS needs to know where the R executable is and where to store temporary files. These information can be found in the configuration file openturns.conf, which is located in $prefix/etc.

If you want to change the default values, you have to create the directories $HOME/openturns/etc and to copy the openturns.conf file in $HOME/openturns/etc. It is a text file that you can adapt to your needs. Remember that OpenTURNS is not (yet) capable of expanding environment variables, so if you want to define the temporary directory as being $HOME/tmp, you have to expand the path by yourself and write /home/your_name/tmp, assuming that $HOME is /home/your_name.