Commit 8d2eb094 authored by David Hrbáč's avatar David Hrbáč
Browse files

Typo

parent 4243f341
Pipeline #1999 passed with stages
in 1 minute and 15 seconds
......@@ -27,9 +27,9 @@ Instrumentation via " scalasca -instrument" is discouraged. Use [Score-P instrum
### Runtime measurement
After the application is instrumented, runtime measurement can be performed with the " scalasca -analyze" command. The syntax is:
After the application is instrumented, runtime measurement can be performed with the `scalasca -analyze` command. The syntax is:
scalasca -analyze [scalasca options][launcher] [launcher options][program] [program options]
`scalasca -analyze [scalasca options][launcher] [launcher options][program] [program options]`
An example :
......@@ -39,10 +39,10 @@ An example :
Some notable Scalasca options are:
**-t Enable trace data collection. By default, only summary data are collected.**
**-e <directory> Specify a directory to save the collected data to. By default, Scalasca saves the data to a directory with prefix scorep\_, followed by name of the executable and launch configuration.**
- **-t Enable trace data collection. By default, only summary data are collected.**
- **-e <directory> Specify a directory to save the collected data to. By default, Scalasca saves the data to a directory with prefix scorep\_, followed by name of the executable and launch configuration.**
!!! Note "Note"
!!! Note
Scalasca can generate a huge amount of data, especially if tracing is enabled. Please consider saving the data to a [scratch directory](../../storage/storage/).
### Analysis of reports
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment