> home > support > FAQ > paraver
Using Paraver on HPCx

A more detailed User Guide, for Paraver on HPCx, is available in PDF format can be found here.

Paraver is a GUI-based performance visualisation and analysis tool that can be used to analyze parallel programs using MPI, OpenMP and MPI & OpenMP (Mixed-Mode). Paraver also includes hardware counter profiling and Operating System activity monitoring. User Manuals can be found at the Paraver Home Page: http://www.cepba.upc.es/paraver/. Users should note that:

1. Paraver currently only works with 32-bit executables on HPCx.
2. Paraver uses IBM's DPCL (Dynamic Probe Class Library) which requires a .rhosts file in your home directory. An example .rhosts file for userid jbloggs can be found here.

1. Firstly generate tracefiles for your application code:
   
   In your LoadLeveler script, replace, for example
   
   

   poe ./prog
   

   with:
   
   

   export OMPITRACE_HOME=/usr/local/packages/paraver
export MPTRACE_COUNTGROUP=60
$OMPITRACE_HOME/bin/ompitrace -counters -v poe.real ./prog

   Then submit your batch job to Loadleveler in the usual way.
   N.B. when tracing with Paraver on HPCx, the command poe.real must be used rather than poe ( on HPCx poe is a script which points to the executable poe.real ).
   
   
2. To view the generated tracefiles, firstly set the following environment variables in your login session:
   
   export PARAVER_HOME = /usr/local/packages/paraver
export MPTRACE_COUNTGROUP=60
   
   

   During the run, Paraver will have created a temporary trace file for each process (*.mpit and *.sim files). After the run has completed the user must submit an instruction to pack the individual profile files into one global output. This is undertaken by issuing the command:

   $PARAVER_HOME/bin/ompi2prv *.mpit -s *.sym -o trace_prm.prv
   
   To view the resulting tracefile use the command:
   
   $PARAVER_HOME/bin/paraver trace_prm.prv