This is a spack repository with recipes for:
- DDC,
- Deisa,
- Gysela,
- layout-contiguous,
- PDI and its plugins.
Each of these can be installed in a few simple steps:
- setup spack,
- (optional): reuse already installed packages,
- (optional): reuse already installed compilers,
- install:
To use it, you should first setup spack:
# 1. Get and enable Spack
git clone https://github.com/spack/spack.git
. spack/share/spack/setup-env.sh
# 2. Get and enable this spack repo
git clone https://github.com/pdidev/spack.git spack/var/spack/repos/pdi
spack repo add spack/var/spack/repos/pdi
You can tell your local spack instance that there is an upstream spack instance by editing spack/etc/spack/defaults/upstreams.yaml
.
upstreams:
name-of-spack-instance:
install_tree: /path/to/spack/opt/spack
This will let spack use the already installed packages when it sees fit, (which is almost never).
You can however force spack to use already installed package by using the flag --reuse
when calling spack install
.
For example on Ruche, you can do:
cat<<EOF > spack/etc/spack/defaults/upstreams.yaml
upstreams:
ruche-system:
install_tree: /gpfs/softs/spack/opt/spack/
EOF
If there are packages already present on the machine that you want spack to use e.g. MPI, you can specify them as externals through the packages.yaml
file found in either in a Spack installation’s etc/spack/
or a user’s ~/.spack/
directory. Here’s an example of an external configuration:
packages:
openmpi:
externals:
- spec: "[email protected]%[email protected] arch=linux-debian7-x86_64"
prefix: /opt/openmpi-1.4.3
- spec: "[email protected]%[email protected] arch=linux-debian7-x86_64+debug"
prefix: /opt/openmpi-1.4.3-debug
- spec: "[email protected]%[email protected] arch=linux-debian7-x86_64"
prefix: /opt/openmpi-1.6.5-intel
Is it recommended to only put MPI implementations, CMake and openssl
as externals and let spack take care of the rest.
For compilers, you can specify them in the user's ~/.spack/linux/compilers.yaml
.
compilers:
- compiler:
spec: [email protected]
paths:
cc: /usr/bin/gcc
cxx: /usr/bin/g++
f77: /usr/bin/gfortran
fc: /usr/bin/gfortran
flags: {}
operating_system: centos7
target: x86_64
modules: []
environment: {}
extra_rpaths: []
This can be done automatically by calling spack compiler find
when the compilers are loaded.
This is needed if you want to use the Intel compilers.
For example on Ruche, you can do:
spack load [email protected]
spack compiler find
spack unload [email protected]
Then depending on what you want to install, go to the following:
You can install DDC using the following instructions after you've done the setup:
# Install DDC
spack install ddc
You can install Deisa using the following instructions after you've done the setup:
# Install Deisa
spack install deisa
Before installing Gysela, you choose select the set of options that suit you:
build_type=X
to specify build type, valid values are'Release', 'Timed', 'Deterministic', 'Debug' and 'Scorep'
(defaults toRelease
),+pdi
for compilation with PDI for IOs (defaults tooff
),gysela_dir=/path/to/put/gysela
to choose where to install Gysela (defaults to$HOME/gysela
). This information is also available by doingspack info gysela
.
Gysela sometimes has issues when lapack is provided by open-blas.
It is thus recommended to use ^intel-mkl
(or ^netlib-lapack
) when calling spack install.
To check what you will actually install, you can run:
# Get info about what you will install with Gysela
spack solve ${YOUR_OPTIONS} gysela
Warning: Since Gysela is not publicly available for download, you will need a ssh key properly installed to download it.
You can install Gysela using the following instructions after you've done the setup:
# Install Gysela
spack install ${YOUR_OPTIONS} gysela
For example on Ruche, you can do:
# Install Gysela
export GYSELA_INSTALLDIR="${HOME}/gysela_spack"
spack install --reuse "gysela gysela_dir=${GYSELA_INSTALLDIR} %[email protected] +pdi ^netlib-lapack"
To actually run Gysela you need to move to the installation directory selected in the previous section and load the module.
# move to the installation directory
cd "${GYSELA_INSTALLDIR}/wk"
# load the appropriate spack modules
spack load gysela
# now you can run
./subgys
You can install layout-contiguous using the following instructions after you've done the setup:
# Install layout-contiguous
spack install layout-contiguous
You can install PDI and most of its plugins using the following instructions after you've done the setup:
# Install PDI and most of its plugins
spack install pdiplugin-decl-hdf5 pdiplugin-decl-netcdf pdiplugin-flowvr pdiplugin-mpi pdiplugin-pycall pdiplugin-serialize pdiplugin-set-value pdiplugin-trace pdiplugin-user-code
If you only need some of the plugins, you can adapt the last line.
PDI Decl'SION plugin depends on the SIONlib recipe. To install it, you need to use the following instructions after you've done the setup:
# 1. Get SIONlib spack repo
git clone https://gitlab.jsc.fz-juelich.de/cstao-public/SIONlib/spack-repository.git spack/var/spack/repos/SIONlib
spack repo add spack/var/spack/repos/SIONlib
# 2. Install decl-sion plugin
spack install pdiplugin-decl-sion
PDI FTI plugin depends on the FTI recipe. To install it, you need to use the following instructions after you've done the setup:
# 1. Get SIONlib spack repo
git clone https://github.com/leobago/fti-spack spack/var/spack/repos/FTI
spack repo add spack/var/spack/repos/FTI
# 2. Install fti plugin
spack install pdiplugin-fti