- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -
HPE Hawk: Difference between revisions
From HLRS Platforms
Jump to navigationJump to search
| Line 35: | Line 35: | ||
* In case of dependencies, load explicit versions instead of default one! | * In case of dependencies, load explicit versions instead of default one! | ||
As an example a modulefile for package | As an example a modulefile for package "foo" version 1.23 (within the category "performance") should look like: | ||
BASE_DIR=/opt/hlrs/ | BASE_DIR=/opt/hlrs/ | ||
CAT=performance | CAT=performance | ||
| Line 42: | Line 42: | ||
FOO_ROOT=$BASE_DIR/$CAT/$PACKAGE/$VERSION | FOO_ROOT=$BASE_DIR/$CAT/$PACKAGE/$VERSION | ||
setenv FOO_ROOT $FOO_ROOT | setenv FOO_ROOT $FOO_ROOT | ||
setenv FOO_VERSION $VERSION | setenv FOO_VERSION $VERSION | ||
Revision as of 16:15, 7 August 2019
Hawk is the next generation HPC system at HLRS. It will replace the existing HazelHen system. The installation is planed to take place in Q4 2019. For more detailed information see the Hawk installation schedule.
This Page is under construction!
TODO
- 2019-08-07, dick@hlrs: hmpt always uses GCC (the 1st in PATH) -> adapt s.t. other compilers can also be used
- 2019-08-07, dick@hlrs: hmpt is ABI-compatible with MPICH-derivativs, but not so mpt
- user should know about this!
- @HPE: is hmpt a MPICH-derivatice, but not so mpt?
- 2019-08-07, dick@hlrs: unclear that (h)mpt provides MPI lib -> call it "mpi/hmpt" and "mpi/mpt" instead?
- 2019-08-07, dick@hlrs: remove MPI delivered with RHEL
- 2019-08-07, dick@hlrs: Intel loads gcc module -> use (LD_)LIBRARY_PATH intead
- 2019-08-07, dick@hlrs: be careful: cc points to /usr/bin/gcc!
Modulefile best practices
- Set an environment variable to the root path of your installation (cf. e.g. MPI_ROOT in /usr/share/Modules/modulefiles/hmpt/2.19).
- Set not only CPATH but also respective variables used by PGI / Intel / etc. -> someone has to figure out the list of those variables, same w.r.t. (LD_)LiBRARY_PATH.
- Include your Name (finger does not work anymore), E-Mail and date of installation into the modulefile.
- It's possible to hold the modulefile(s) together with the actual installation in the respective directory and just create symlinks in /opt/hlrs/modulefiles/.
- Directory structure of /opt/hlrs/ shall be replicated in /opt/hlrs/unsupported-modulefiles/.
- In case of dependencies, load explicit versions instead of default one!
As an example a modulefile for package "foo" version 1.23 (within the category "performance") should look like:
BASE_DIR=/opt/hlrs/ CAT=performance PACKAGE=Foo VERSION=1.23 FOO_ROOT=$BASE_DIR/$CAT/$PACKAGE/$VERSION setenv FOO_ROOT $FOO_ROOT setenv FOO_VERSION $VERSION prepend-path PATH $FOO_ROOT/bin prepend-path LD_LIBRARY_PATH $FOO_ROOT/lib # library search path at time of execution prepend-path LIBRARY_PATH $FOO_ROOT/lib # equivalent of "-L" for C, C++, and Fortran; works for gcc and clang prepend-path CPATH $FOO_ROOT/include # equivalent to "-I" for C and C++; works with gcc and clang prepend-path CPLUS_INCLUDE_PATH $FOO_ROOT/include # equivalent to "-I" only for C++ compiler; usually not needed as CPATH will do #prepend-path C_INCLUDE_PATH $FOO_ROOT/include # equivalent to "-I" only for C compiler; usually not needed as CPATH will do ### not verified yet, seems to be intel specific: prepend-path FPATH $FOO_ROOT/include # same for Fortran