Any valid OTF trace can be viewed in Vampir; the best way to generate such a trace is using the VampirTrace utility. (You may also be able to generate an OTF trace using other profiling/tracing utilities, such as TAU.) This page describes the use of the Vampir utility. For details on using VampirTrace to generate traces, see the software map entry for that utility.
Note that although Vampir and Intel Trace Analyzer are essentially different forks of the same software, they are incompatible with respect to trace file formats. Specifically, ITA reads traces stored in STF (Structured Trace Format), a proprietary format owned by Intel, and cannot read OTF traces; similarly, Vampir can no longer read STF traces.
VampirServer is the distributed analysis part of the Vampir suite. As such, a familiarity with using Vampir in it's standard, serial mode is advised. For information on this, please see our software page for Vampir on raijin.
We recommend launching VampirServer in an interactive PBS batch job. To do this, you need to submit the job to the queue:
where the walltime, number of CPUs, and memory have been appropriately selected (I recommend using a multiple of 16 for ncpus and then twice that in GB for the memory request - for example, 32 CPUs and 64GB of memory). If you want the job to start quicker, considering using the express queue, although note that it consumes SUs at a significanly faster rate. Once the job has started, you need to load the vampir module:
and then you can launch the VampirServer processes using
Once it has started the VampirServer processes, you will get output similar to this: