CMake Options for NEST¶
Before compiling and installing NEST, the source code has to be
configured with cmake
. In the simplest case, the commands:
cmake <nest_source_dir>
make
make install
will build NEST and install it to the site-packages of your Python environment.
Note
If you want to specify an alternative install location, use
-DCMAKE_INSTALL_PREFIX:PATH=<nest_install_dir>
. It needs to be
writable by the user running the install command.
Choice of compiler¶
We systematically test NEST using the GNU gcc and the Clang compiler suites. Compilation with other up-to-date compilers should also work, but we do not regularly test against those compilers and can thus only provide limited support.
To select a specific compiler, please add the following flags to your
cmake
command line:
-DCMAKE_C_COMPILER=<C-compiler> -DCMAKE_CXX_COMPILER=<C++-compiler>
Options for configuring NEST¶
NEST allows for several configuration options for custom builds:
Use Python to build PyNEST¶
|
Build PyNEST [default=ON]. |
|
Use Cython to cythonize pynestkernel.pyx [default=ON]. If OFF, PyNEST has to be build from a pre-cythonized pynestkernel.pyx. |
For more details, see the Python binding section below.
Select parallelization scheme¶
|
Build with MPI parallelization [default=OFF]. |
|
Build with OpenMP multi-threading [default=ON]. Optionally set OMP compiler flags. |
See also the section on building with MPI below.
External libraries¶
|
Build with libneurosim [default=OFF]. Optionally give the directory where libneurosim is installed. |
|
Build with MUSIC [default=OFF]. Optionally give the directory where MUSIC is installed. |
|
Build with sionlib [default=OFF]. Optionally give the directory where sionlib is installed. |
|
Build with Boost [default=ON]. To set a specific Boost installation, give the install path. |
|
Build with GNU Readline library [default=ON]. To set a specific library, give the install path. |
|
Build with ltdl library [default=ON]. To set a specific ltdl, give the install path. NEST uses ltdl for dynamic loading of external user modules. |
|
Build with the GSL library [default=ON]. To set a specific library, give the install path. |
NEST properties¶
|
Specify elementary unit of time [default=1000 tics per ms]. |
|
Specify resolution [default=100 tics per step]. |
|
External NEST modules to be linked in, separated by ‘;’, [default=OFF]. |
|
Build with detailed internal time measurements [default=OFF]. Detailed timers can affect the performance. |
|
Split of the 64-bit target neuron identifier type [default=’standard’]. ‘standard’ is recommended for most users. If running on more than 262144 MPI processes or more than 512 threads, change to ‘hpc’. |
Generic build configuration¶
|
Build static executable and libraries [default=OFF]. |
|
Enable user defined optimizations [default=ON (uses ‘-O2’)]. When OFF, no ‘-O’ flag is passed to the compiler. Explicit compiler flags can be given; separate multiple flags by ‘;’.” |
|
Enable user defined warnings [default=ON (uses ‘-Wall’)]. Separate multiple flags by ‘;’. |
|
Enable user defined debug flags [default=OFF]. When ON, ‘-g’ is used. Separate multiple flags by ‘;’. |
|
User defined flags for the Intel compiler [default=’-fp-model strict’]. Separate multiple flags by ‘;’. |
|
C++ standard to use for compilation [default=’c++11’]. |
|
Link additional libraries [default=OFF]. Give full path. Separate multiple libraries by ‘;’. |
|
Add additional include paths [default=OFF]. Give full path without ‘-I’. Separate multiple include paths by ‘;’. |
|
Additional defines, e.g. ‘-DXYZ=1’ [default=OFF]. Separate multiple defines by ‘;’. |
|
Set a user defined version suffix [default=’’]. |
Configuring NEST for Distributed Simulation with MPI¶
NEST supports distributed simulations using the Message Passing Interface (MPI). Depending on your setup, you have to use one of the following steps in order to add support for MPI:
Try
-Dwith-mpi=ON
as argument forcmake
.If 1. does not work, or you want to use a non-standard MPI, try
-Dwith-mpi=/path/to/my/mpi
. The mpi directory should contain the include, lib and bin subdirectories of the MPI installation.IfO 2. does not work, but you know the correct compiler wrapper for your installation, try adding the following to the invocation of
cmake
:-DMPI_CXX_COMPILER=myC++_CompilerWrapper \ -DMPI_C_COMPILER=myC_CompilerWrapper -Dwith-mpi=ON
When running large-scale parallel simulations and recording from many
neurons, writing to ASCII files might become prohibitively slow due to
the large number of resulting files. By installing the SIONlib
library and supplying its
installation path to the -Dwith-sionlib=<path>
option when calling
cmake
, you can enable the recording backend for binary files, which solves this problem.
In order to run the distributed tests upon make installcheck
, NEST
needs to know how to execute the launcher of your MPI implementation.
CMake is usually able to detect the command line for this, but you can
customize it using the follwing configuration variables (common
defaults are shown below):
-DMPIEXEC=/usr/bin/mpirun
-DMPIEXEC_NUMPROCS_FLAG=-np
-DMPIEXEC_PREFLAGS=
-DMPIEXEC_POSTFLAGS=
The final command line is composed in the following way:
$MPIEXEC $MPIEXEC_NUMPROC_FLAG <np> $MPIEXEC_PREFLAGS <prog> $MPIEXEC_POSTFLAGS <args>
For details on setting specific flags for your MPI launcher command, see the CMake documentation.
See the Guide to parallel computing to learn how to execute threaded and distributed simulations with NEST.
Support for libneurosim¶
In order to allow NEST to create connections using external libraries,
it provides support for the Connection Generator Interface from
libneurosim. To request the use of libneurosim, you have to use the
follwing switch for the invocation of cmake
. It expects either
ON or OFF, or the directory where libneurosim is installed:
-Dwith-libneurosim=[OFF|ON|</path/to/libneurosim>]
For details on how to use the Connection Generator Interface, see the guide on connection management.
Python Binding (PyNEST)¶
Note that since NEST 3.0, support for Python 2 has been dropped. Please use Python 3 instead.
cmake
usually autodetects your Python installation.
In some cases cmake
might not be able to localize the Python interpreter
and its corresponding libraries correctly. To circumvent such a problem following
cmake
built-in variables can be set manually and passed to cmake
:
PYTHON_EXECUTABLE ..... path to the Python interpreter
PYTHON_LIBRARY ........ path to libpython
PYTHON_INCLUDE_DIR .... two include ...
PYTHON_INCLUDE_DIR2 ... directories
e.g.: Please note ``-Dwith-python=ON`` is the default::
cmake -DCMAKE_INSTALL_PREFIX=<nest_install_dir> \
-DPYTHON_EXECUTABLE=/usr/bin/python3 \
-DPYTHON_LIBRARY=/usr/lib/x86_64-linux-gnu/libpython3.4m.so \
-DPYTHON_INCLUDE_DIR=/usr/include/python3.4 \
-DPYTHON_INCLUDE_DIR2=/usr/include/x86_64-linux-gnu/python3.4m \
<nest_source_dir>
Compiler-specific options¶
NEST has reasonable default compiler options for the most common compilers.
Intel compiler¶
To ensure that computations obey the IEEE754 standard for floating point
numerics, the -fp-model strict
flag is used by default, but can be
overridden with
-Dwith-intel-compiler-flags="<intel-flags>"
Portland compiler¶
Use the -Kieee
flag to ensure that computations obey the IEEE754 standard for floating point numerics.