Paraver trace analysis
The CARM Tool can analyze Paraver traces. It plots every burst of a Paraver trace as a point on the roofline: the GUI runs Paraver’s paramedir tool over the trace, reads the hardware-counter data it extracts, and computes roofline metrics (arithmetic intensity, FLOP/s, bandwidth) per burst. The results can be exported back as Paraver-importable windows.
Quick Start
# Install the CARM Tool with GUI extras
pip install "carm-roofline[gui]"
# Add Paraver's bin directory to your PATH (provides paramedir)
export PATH=/path/to/paraver/bin:$PATH
# Analyze a trace (or call from Paraver's context menu for full integration)
carm gui --paraver-trace trace.prv --paraver-window-csv window.csv
Prerequisites
- The CARM Tool with GUI extras —
pip install "carm-roofline[gui]". See the Installation page for the full instructions. - Paraver (version 4.12 or later) and Extrae — BSC’s trace visualization and generation tools. Extrae instruments the application and produces the trace.
paramedironPATH— the CARM Tool uses Paraver’sparamedirtool to extract counter data from the trace. Add Paraver’sbin/directory to yourPATH(e.g.export PATH=/path/to/paraver/bin:$PATH).- A Paraver trace (
.prv), optionally the respective window CSV
CLI flags
Paraver mode is a mode of carm gui, enabled by giving a trace:
| Flag | Meaning |
|---|---|
--paraver-trace <path> | Path to the .prv trace; enables Paraver GUI mode |
--paraver-window-csv <path> | Path to the window/mask CSV (required when --paraver-trace is given) |
The usual GUI options (--gui-host, --gui-port, --results-dir, --verbose) combine with Paraver mode.
Contents
| Page | Description |
|---|---|
| Trace Requirements | Which hardware counters the trace must include |
| Usage | Step-by-step workflow: launch from Paraver or the CLI |
| Features | GUI controls, filtering, coloring, and exports |
| Performance | Keeping the GUI responsive with large traces |