Skip to content

[package list]

Score-P

License information

Score-P is available under the 3-clause BSD Open Source license. For more information, check the COPYING file in the sources repository.

From version 9.0 on, this information can also be found in $EBROOTSCOREMINP/share/licenses/Score-P after installing and loading the module.

User documentation

Score-P has moved to the contributed EasyConfigs as we cannot promise timely ports to new versions of the software stack and as we cannot guarantee that it works in all cases on LUMI. Our main profiling and performance analysis tools are the tools from HPE Cray and AMD (see our 4-day trainings), but these tools are offered "as-is" and may be supported by their developers and the EuroHPC pop Centre of Excellence who offer trainings based on these tools.

A nice introductory talk on the Score-P ecosystem and how all its tools can be used, can be found on the pop Center of Excellence web pages, on the "HPC.NRW Tool Talk - Application Profiling with Score-P and Cube" page (or directly on YouTube). Of particular interest is the section "The Score-P Ecosystem", starting at 22:38, which builds up a graphical overview highlighting the role of several packages.

Note that there are a few things to note on LUMI:

  • cpeGNU does not offer support for our HIP adapter, as we require a Clang based compiler. It is available for the others.

  • cpeAOCC offers support for the OpenMP Tools Interface and enables it by default. This is an alternative to OPARI2 and provides support for a wider range of OpenMP. GNU GCC lacks the interface, CCE 16 still has some issues, where we decide to not enable the adapter.

  • We cannot yet provide CubeGui due to the complexity of the installation, and the AppImage provided by the developers also cannot be used on LUMI.

  • On the LUMI-G nodes, the use of Score-P is currently limited unless you are an expert in figuring out compiler options and rewriting Makefiles. Not only is OpenMP offload not supported with instrumentation, but enabling it by loading the GPU target module (loaded by default by cpeCray and cpeAMD) and using -fopenmp causes problems with OPARI2 shown as errors about some include files. This is because the wrappers load paths to include files in an order that the OPARI2-instrumented code does not like and steers it to the wrong include files. If your code does not use OpenMP or you can compile without the GPU target module, or you use the OpenMP tools interface with the ROCm compilers from cpeAMD/PrgEnv-amd, it might work.

User-installable modules (and EasyConfigs)

Install with the EasyBuild-user module: 

eb <easyconfig> -r
To access module help after installation and get reminded for which stacks and partitions the module is installed, use module spider Score-P/<version>.

EasyConfig:

Technical documentation

The Score-P measurement infrastructure is a highly scalable and easy-to-use tool suite for profiling and event tracing of HPC applications.

It has been created in the German BMBF project SILC and the US DOE project PRIMA and will be maintained and enhanced in a number of follow-up projects such as LMAC, Score-E, and HOPSA. Score-P is developed under a BSD 3-Clause License and governed by a meritocratic governance model.

Score-P offers the user a maximum of convenience by supporting a number of analysis tools. Currently, it works with Scalasca, Vampir, and Tau and is open for other tools. Score-P comes together with the new Open Trace Format Version 2, the Cube4 profiling format and the OPARI2 instrumenter.

EasyBuild support

There was earlier work in the central software stack before we got EasyConfigs contributed by the Score-P authors.

Version 8.4 for CPE 23.09

  • The EasyConfig was contributed by Jan AndrĂ© Reuter from JSC as a direct contribution of the developers.

  • For now, the package is not fully functional on LUMI-G. Basically, OpenMP instrumentation via OPARI2 does not work if OpenMP offload is also enabled, which happens if the craype-accel-amd-gfx90a module is loaded and the compiler wrappers are used. This is likely due to some bad ordering of the include files in that case.

  • For some reason, we still need to load the rocm module for the cpeAMD version as otherwise roctracer is not correctly detected. The rocm module does a few initialisations of environment variables that the amd module does not do.

Version 8.4 for CPE 24.03

  • Conversion of the easyconfigs for 23.09 with some build dependencies moved to runtime dependencies as we don't want to rely on RPATH.

Version 9.0 for CPE 24.03

  • Some reworking needed, offered to us by JSC. Also required an update of the EasyBlock.

  • Added license information to the installation.

Archived EasyConfigs

The EasyConfigs below are additional easyconfigs that are not directly available on the system for installation. Users are advised to use the newer ones and these archived ones are unsupported. They are still provided as a source of information should you need this, e.g., to understand the configuration that was used for earlier work on the system.