As always, in bold you find what is already covered at release v1.0.
Required Components
Application name and remarks follow:
FEniCS fenics
FFTW fftw version 2 and 3
GSL gsl
MATLAB matlab
PETSc petsc built with double,complex,64-bit indices
R R
Trilinos trilinos
CMake cmake
GridFTP gridftp
gnuplot gnuplot
HDF5 hdf5
hpn-ssh clients only
Mayavi mayavi version 2
NetCDF netcdf
PAPI papi
ParaView paraview
pigz pigz multicore-parallel gzip
Python python see the Python subsection
TotalView totalview
Visit visit LLNL Visit
VTK vtk
Python module
There is also an apparent need for an extended Python module, covering
cython
gnuplot Python interface to gnuplot
Ipython
matplotlib
mpi4py requires MPI
NumPy
petsc4py requires PETSc
Pypar
PyTables requires hdf5
PyTrilinos requires hdf5, trilinos
ScientificPython
SciPy
SciTools
SymPy
PRACE CPE Compatibility
Finally, the PRACE CPE is the compatibility layer centers strive to be compliant against:
Bash bash
BLACS blacs [1]
BLAS blas [1]
C compiler c [2]
C++ compiler c++ [2]
Emacs emacs
Fortran compiler fortran [2]
Java compiler java [1]
LAPACK lapack [1]
MPI mpi [1]
ScaLAPACK scalapack [1]
tcsh tcsh
GNU Make gmake
NEdit nedit
Perl perl
Tcl tcl
Tk tk
OpenSSH openssh clients only
PRACE CPE prace container module
As per the following, some aliasing work will be required (or it can be done via alt. namespace):
[1] provide an alias to the recommended, highest performance, library or utility, supporting the platform recommended compiler. In case of a library, this might be fully contained in another product. If a recommended vendor library does not fully contain the module file library (including its API), separate libraries must be provided (e.g. IBM ESSL).
[2] provide an alias to the recommended compiler, capable of compiling parallel (MPI) programs, with or without OpenMP.
boegel
commented
11 years ago
Hi,
most of the content on this has been "shamelessly borrowed" from: https://openwiki.uninett.no/metacenter:reference:noturcpe
As always, in bold you find what is already covered at release v1.0.
Required Components
Application name and remarks follow:
Python module
There is also an apparent need for an extended Python module, covering
PRACE CPE Compatibility
Finally, the PRACE CPE is the compatibility layer centers strive to be compliant against:
As per the following, some aliasing work will be required (or it can be done via alt. namespace):
[1] provide an alias to the recommended, highest performance, library or utility, supporting the platform recommended compiler. In case of a library, this might be fully contained in another product. If a recommended vendor library does not fully contain the module file library (including its API), separate libraries must be provided (e.g. IBM ESSL). [2] provide an alias to the recommended compiler, capable of compiling parallel (MPI) programs, with or without OpenMP.
Sources to bootstrap some easyconfigs
Mockup -untested- versions for some of the missing small items above can be found at: https://github.com/fgeorgatos/easybuild.experimental/blob/master/contrib/pkgsrc/b/bash-2.05b.eb or, https://github.com/fgeorgatos/easybuild.experimental/blob/master/contrib/pkgsrc/b/bash-4.1.5(1)-release.eb https://github.com/fgeorgatos/easybuild.experimental/blob/master/contrib/pkgsrc/t/tcsh-6.18.01.eb https://github.com/fgeorgatos/easybuild.experimental/blob/master/contrib/pkgsrc/e/emacs-22.3.eb https://github.com/fgeorgatos/easybuild.experimental/blob/master/contrib/pkgsrc/j/jdk1.7.0-20090502--NetBSD_5.0.eb
Default PRACE module dependencies and variables
The PRACE module should automatically has as dependencies:
c c++ fortran mpi blas lapack blacs scalapack fftw/3 netcdf hdf5and adjust variables:PRACE Applications
Finally, these apps have to be available as modules, too:
PRACE Benchmarks
For completeness -but not a prerequisite to resolve this issue-, here are the applications selected for the PRACE application benchmark suite:
Ref: http://www.hpcwire.com/hpcwire/2010-02-15/prace_benchmark_suite_finalised.html