- 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
 
(191 intermediate revisions by 10 users not shown)
Line 1: Line 1:
'''Hawk''' is the next generation HPC system at HLRS. It will replace the existing [[Cray XC40|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!
{{Note
| text = Please be sure to read at least the [[10_minutes_before_the_first_job]] document and consult the [[General HWW Documentation]] before you start to work with any of our systems.
}}


[[Batch_System_PBSPro_(Hawk)|Batch System PBSPro (Hawk)]]
{{Warning
| text = In prepartion of the next generation supercomputer [[ Hunter_(HPE) | Hunter ]], the hardware configuration has been reduced (from 5632 compute nodes to 4096 compute nodes).
}}


<br>
{{Warning
| text = The ws10 file system will finally be shut down on October 18 of 2024.<BR>  
Users will need to migrate their data stored on ws10 to the default ws11 file system.<BR>
More details, the exact procedure, and instructions for migrating data can be found at the following URL:<BR>
[[Workspace_migration]]
}}


== 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
{| style="border:0; margin: 0;" width="100%" cellspacing="10"
** 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?
| valign="top" style="padding: 0; border: 1px solid #aaaaaa; margin-bottom: 0;" |
<div style="font-size: 105%; padding: 0.4em; background-color: #eeeeee; border-bottom: 1px solid #aaaaaa; text-align: center;">'''Introduction'''</div>
<div style="background: #ffffff; padding:0.2em 0.4em;">
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" | 
<!-- * [[Hawk_installation_schedule#Terms_of_Use | Terms of use ]] -->
* [[HPE_Hawk_access|Access]]
* [[HPE_Hawk_Hardware_and_Architecture|Hardware and Architecture]]
|}
</div>


* 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!
| valign="top" style="padding: 0; border: 1px solid #aaaaaa; margin-bottom: 0;" |
<div style="font-size: 105%; padding: 0.4em; background-color: #eeeeee; border-bottom: 1px solid #aaaaaa; text-align: center;">'''Troubleshooting'''</div>
<div style="background: #ffffff; padding:0.2em 0.4em;">
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" | 
* [[HPE_Hawk_Support|Support (contact/staff)]]
* [[HPE_Hawk_FAQ|FAQ]]
* [http://websrv.hlrs.de/cgi-bin/hwwweather?task=viewmachine&machine=hawk Status,Maintenance for hawk]
* [[HPE_Hawk_News|News]]
|}
</div>


<br>


== 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:
 
 
#%Module1.0
 
BASE_DIR=/opt/hlrs/
{| style="border:0; margin: 0;" width="100%" cellspacing="10"
CAT=performance
 
PACKAGE=Foo
| valign="top" style="padding: 0; border: 1px solid #aaaaaa; margin-bottom: 0;" |
  VERSION=1.23
<div style="font-size: 105%; padding: 0.4em; background-color: #eeeeee; border-bottom: 1px solid #aaaaaa; text-align: center;">'''Documentation'''</div>
<div style="background: #ffffff; padding:0.2em 0.4em;">
FOO_ROOT=$BASE_DIR/$CAT/$PACKAGE/$VERSION
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" |  
setenv FOO_ROOT $FOO_ROOT
* [[Batch_System_PBSPro_(Hawk)|Batch System]]
setenv FOO_VERSION $VERSION
* [[Module environment(Hawk)|Module Environment]]
* [[Storage_(Hawk)| Storage Description ]]
prepend-path PATH                $FOO_ROOT/bin
* [[Compiler(Hawk)|Compiler]]
prepend-path LD_LIBRARY_PATH    $FOO_ROOT/lib        # library search path at time of execution
* [[MPI(Hawk)|MPI]]
prepend-path LIBRARY_PATH        $FOO_ROOT/lib        # equivalent of "-L" for C, C++, and Fortran; works for gcc and clang
* [[Libraries(Hawk)|Libraries]]
prepend-path CPATH              $FOO_ROOT/include    # equivalent to "-I" for C and C++; works with gcc and clang
* [[Manuals(Hawk)|Manuals]]
prepend-path CPLUS_INCLUDE_PATH  $FOO_ROOT/include    # equivalent to "-I" only for C++ compiler; usually not needed as CPATH will do
* [[Optimization|Optimization]]
#prepend-path C_INCLUDE_PATH      $FOO_ROOT/include    # equivalent to "-I" only for C compiler; usually not needed as CPATH will do
* [[Hawk_PrePostProcessing|Pre- and Post-Processing]]
  ###  not verified yet, seems to be intel specific: prepend-path FPATH              $FOO_ROOT/include    # same for Fortran
* [[Big_Data,_AI_Aplications_and_Frameworks|Big Data, AI Applications and Frameworks]]
* [[Performance Analysis Tools]]
* [[CPE|Cray Programming Environment (CPE)]]
 
|}
</div>
 
 
 
| valign="top" style="padding: 0; border: 1px solid #aaaaaa; margin-bottom: 0;" |
<div style="font-size: 105%; padding: 0.4em; background-color: #eeeeee; border-bottom: 1px solid #aaaaaa; text-align: center;">'''Utilities'''</div>
<div style="background: #ffffff; padding:0.2em 0.4em;">
{| style="border: 0; margin: 0;" cellpadding="3"
| valign="top" |  
* [[CAE_utilities|CAE Utilities]]
* [[CAE_howtos|CAE HOWTOs]]
* [[MKL | MKL Fortran Interfaces ]]
|}
</div>
 
|}
 
 
----
[[Help | Help for Wiki Usage]]

Latest revision as of 09:50, 22 July 2024

Note: Please be sure to read at least the 10_minutes_before_the_first_job document and consult the General HWW Documentation before you start to work with any of our systems.


Warning: In prepartion of the next generation supercomputer Hunter , the hardware configuration has been reduced (from 5632 compute nodes to 4096 compute nodes).


Warning: The ws10 file system will finally be shut down on October 18 of 2024.

Users will need to migrate their data stored on ws10 to the default ws11 file system.
More details, the exact procedure, and instructions for migrating data can be found at the following URL:

Workspace_migration



Introduction
Troubleshooting




Documentation
Utilities


Help for Wiki Usage

Retrieved from "https://kb.hlrs.de/platforms/index.php?title=HPE_Hawk&oldid=7475"