CARM subcommands

The CARM Tool provides four subcommands covering benchmarking, profiling, visualization, and result conversion, plus a Paraver trace-analysis mode inside the GUI. See each page for detailed usage instructions and examples.


Benchmarking

Measure peak arithmetic performance (GFLOP/s) and memory bandwidth across cache levels to construct a Cache-Aware Roofline Model. Supports multiple ISAs, data types, thread counts, and test types.

carm benchmark --test roofline

GUI

Launch the interactive Dash + Plotly dashboard for exploring roofline plots and application performance data.

carm gui

Profiling

Profile instrumented applications (MPI, threaded, hybrid) to compute roofline metrics (arithmetic intensity, FLOP/s, and memory bandwidth) using PAPI or perf backends.

carm profile [options] -- <command>

Conversion

Convert legacy application or two-header roofline CSV files into GUI-discoverable JSONL, or export JSONL back to CSV:

carm convert legacy-results --from legacy-csv --to jsonl
carm convert results --from jsonl --to legacy-csv --output-dir restored

The output directory defaults to CARM’s user data directory; use --output-dir to choose another destination.

Use --dry-run to validate and preview outputs, and --overwrite to replace existing destination files.


Paraver

Analyze Paraver traces on the roofline — a mode of the GUI (not a separate subcommand) that plots every traced burst and exports the metrics back as Paraver-importable windows.

carm gui --paraver-trace trace.prv --paraver-window-csv window.csv

See the Paraver section for trace requirements, usage, GUI features, and performance guidance.


Table of contents


Copyright © CHaMP Team. Distributed under an Apache 2.0 license.

This site uses Just the Docs, a documentation theme for Jekyll.