From 2c46cd2efa67f73345236ab38591b48bb17b78c5 Mon Sep 17 00:00:00 2001
From: Martin Schroschk <martin.schroschk@tu-dresden.de>
Date: Thu, 16 Sep 2021 09:59:37 +0200
Subject: [PATCH] Fix markdown
---
doc.zih.tu-dresden.de/docs/software/papi.md | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/doc.zih.tu-dresden.de/docs/software/papi.md b/doc.zih.tu-dresden.de/docs/software/papi.md
index 607c3ada0..8d2fad552 100644
--- a/doc.zih.tu-dresden.de/docs/software/papi.md
+++ b/doc.zih.tu-dresden.de/docs/software/papi.md
@@ -46,7 +46,6 @@ The following code example shows the use of the high-level API by marking a code
}
```
-
??? example "Fortran"
```fortran
@@ -70,13 +69,11 @@ The following code example shows the use of the high-level API by marking a code
end program main
```
-
Events to be recorded are determined via the environment variable `PAPI_EVENTS` that lists comma
separated events for any component (see example below). The output is generated in the current
directory by default. However, it is recommended to specify an output directory for larger
measurements, especially for MPI applications via environment variable `PAPI_OUTPUT_DIRECTORY`.
-
!!! example "Setting performance events and output directory"
```bash
@@ -110,13 +107,13 @@ multiple events, please check which events can be measured concurrently using th
!!! example "Example: Determine the events on the partition `romeo` from a login node"
```console
- marie@login$ module load PAPI
- marie@login$ salloc -A <project> --partition=romeo
+ marie@login$ module load PAPI
+ marie@login$ salloc -A <project> --partition=romeo
[...]
- marie@login$ srun papi_avail
- marie@login$ srun papi_native_avail
+ marie@login$ srun papi_avail
+ marie@login$ srun papi_native_avail
[...]
- # Exit with Ctrl+C
+ # Exit with Ctrl+C
```
Instrument your application with either the high-level or low-level API. Load the PAPI module and
--
GitLab