scalasca(1)

🦋 scalasca — the manual page, but make it a vibe 🦋

okay so bestie, welcome to scalasca from the Scalasca Trace Tools manual (that's the scalasca(1) page, iykyk) 💅

---

✨ NAME ✨

scalasca — Scalasca information and proxy command 🫶

---

✨ SYNOPSIS ✨

scalasca [OPTIONS]
scalasca [OPTIONS] ACTION ACTION_ARGS

---

✨ DESCRIPTION ✨

So the scalasca command is literally your bestie for two things. Number one: it lets you query info about a Scalasca Trace Tools installation 👑. Number two: it can act as a proxy command for measurement, analysis, post-processing, and report examination tasks. Versatile icon behavior, honestly.

When you run it with no ACTION argument, the scalasca command hands you a bunch of OPTIONS to query and display information about the Scalasca Trace Tools installation — stuff like the version number, the configuration summary report, or installation-dependent path information ✨. It can also display a quick reference guide if it finds a suitable PDF viewer on the system. Cute!

But if an ACTION argument IS given? Then scalasca becomes a proxy and simply delegates the requested operation to the underlying specific command 🌸. Think of it as a single-entry-point convenience command that is easy to remember — one door, all the rooms. Main character energy fr fr.

---

✨ ACTIONS ✨

Since ACTION arguments enable the delegation of operations, please go read the documentation of the respective underlying command for possible ACTION_ARGS 📖. Also — important!! — ACTION_ARGS have to be provided after the ACTION argument. Order matters, bestie.

• -a, --analyze, --analyse — run the application under the control of the Scalasca measurement collection and analysis nexus scan(1) 🔥
• -e, --examine — examine the measurement analysis report using the Scalasca analysis report explorer square(1) 🔍

---

🌈 Deprecated actions 🌈

• -i, -inst, --instrument — prepare application objects and executable for measurement using the Score-P instrumenter. This action only exists for backward compatibility with the Scalasca 1.x release series. Users are strongly encouraged to use the scorep instrumenter command directly to take full advantage of its improved functionality.

🚨 bestie this one is deprecated, like genuinely — it's just hanging around for backward compatibility with Scalasca 1.x. Please go straight to scorep and get all the improved functionality instead, okay? 💖

---

✨ OPTIONS ✨

• -c, --show-config — print configuration summary, then exit 📋
• -h, --help — print a brief usage summary, then exit 🙋
• -n, --dry-run — print the command(s) to be launched, but do not execute them 👀
• --quickref — display quick reference guide, then exit 📄
• --remap-specfile — show path to remapper specification file used for trace-analysis report post-processing, then exit 🗺️
• -v, --verbose — enable verbose mode 🗣️
• -V, --version — print version information, then exit 🏷️

---

✨ EXIT STATUS ✨

scalasca exits with status 0 on success, and greater than 0 if errors occur. Zero means slay, anything above zero means something went 💀.

---

✨ BUGS ✨

Found a bug? Please report bugs to scalasca@fz-juelich.de 📧. Make sure to include at least the following information in your bug report, no skipping:

• The Scalasca Trace Tools version reported by scalasca -V.
• The Scalasca Trace Tools configuration reported by scalasca -c.
• The Score-P version reported by scorep --version.
• The Score-P configuration reported by scorep-info config-summary.
• The exact command line of the failing command.
• The exact failure/error message.

Also — and this one is big — if the trace analysis fails, please archive a copy of the entire experiment archive directory including the event trace data, because that may be required to aid in debugging 🧚.

⚠️ BUT. ONLY PROVIDE TRACE DATA IF EXPLICITLY REQUESTED, because the data volume may be excessive. Like, ONLY if they literally ask. Don't just send it, bestie, the files are huge 😭

---

✨ EXAMPLES ✨

scalasca --version

Displays the Scalasca Trace Tools version number 🏷️

scalasca --analyze mpiexec -n 4 foo args

Execute the instrumented MPI program foo with command-line arguments args, collecting a runtime summary (default). Results in an experiment directory scorep_foo_4_sum 📁✨

scalasca --examine -s -f filter scorep_foo_4_sum

Post-process measurement reports in scorep_foo_4_sum and generate a score report with the run-time measurement filter rules from the file filter applied 🔍

---

✨ SEE ALSO ✨

scan(1), square(1)

The Score-P instrumentation and measurement system documentation is available online at https://www.score-p.org 🌐

The full Scalasca Trace Tools documentation is available online at https://www.scalasca.org 🌐

---

and that's the whole page, bestie 🎀 that was Version 2.6.2, dated Wed Apr 2 2025 — so go forth, run scalasca -V, and stan a trace tool 💜🦋✨