- 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
No edit summary |
No edit summary |
||
| Line 25: | Line 25: | ||
== Modulefile best practice == | == Modulefile best practice == | ||
* | * 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 | ||
Revision as of 14:28, 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
- 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?
- unclear that (h)mpt provides MPI lib -> call it "mpi/hmpt" and "mpi/mpt" instead?
- remove MPI delivered with RHEL
- Intel loads gcc module -> use (LD_)LIBRARY_PATH intead
- be careful: cc points to /usr/bin/gcc!
Modulefile best practice
- 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