Development/Score-P: Difference between revisions
No edit summary |
No edit summary |
||
| Line 61: | Line 61: | ||
Check the installation of this Score-P instance using <kbd>scorep-config</kbd>: |
Check the installation of this Score-P instance using <kbd>scorep-config</kbd>: |
||
<pre> |
<pre> |
||
| ⚫ | |||
$ |
|||
| ⚫ | |||
</pre> |
</pre> |
||
Revision as of 17:52, 5 November 2020
| Description | Content |
|---|---|
| module load | devel/scorep |
| Availability | bwUniCluster | BwForCluster_Chemistry |
| License | BSD 3-clause License |
| Citing | n/a |
| Links | Homepage | Documentation | News Mailinglists | Bug Reports |
| Graphical Interface | No |
| Included modules | - |
Introduction
The Score-P Project is a profiling and tracing library with supportive tools developed mainly by by the [VI-HPS] project.
Versions and Availability
A list of versions currently available on all bwHPC Clusters can be obtained from the
Cluster Information System CIS
{{#widget:Iframe |url=https://cis-hpc.uni-konstanz.de/prod.cis/bwUniCluster/devel/scorep |width=99% |height=120 }} On the command line interface of any bwHPC cluster you'll get a list of available versions by using the command module avail devel/scorep. Please note that Score-P installation may be hidden in the sense that it's dependent on the MPI, which in turn is dependent on the compiler. So while there are a multitude of compiler version's only some may feature an MPI, which offers tracing using Score-P. Please use module --ignore-cache spider to evaluate all possible installations.
$ : bwUniCluster 2.0 $ module load compiler/gnu/10.2 mpi/openmpi ; module avail devel/score ------------------------ /opt/bwhpc/common/modulefiles/Core ------------------------- devel/scorep/6.0
Loading
Score-P may be loaded with a specific and MPI:
$ module load compiler/gnu/10.2 mpi/openmpi devel/scorep
Check the installation of this Score-P instance using scorep-config:
$ scorep-info config-summary
Documentation
For online documentation see the links section in the summary table at the top of this page. For local documentation consult the man page.
$ man gdb