This is an introduction to paraver as a performance tool
The following guide describes how to execute ATELES with paraver to get a performance analyses. Before executing ATELES with paraver read the following instructions carefully. 

The following steps have to be done before executing ATELES:

Step 1: 
  module switch openmpi intelmpi
  export CC=icc
  export FC=mpiifort 
Go to the ATELES directory, 
  cd /your_folders/ateles
Compile ATELES with simple debug options by:
  ./waf debug

Step 2: 
Execute ATELES under observation of paraview and its performance tools. 
The following file is an example file for the Cluster-Beta of RWTH Rechenzentrum which executes ATELES there:
test/performance/paraver/paraver_ateles.lsf
Before submitting this job to the queue of the Cluster-beta system please check if the directory given in extrae.xml, trace.sh and paraver_ateles.lsf are the correct ones on your account. 
Load the extrae module:
  module load UNITE extrae/2.1.1-intel2-papi  
The job is then submitted to the queue of the system by:
  bsub < test/performance/paraver/paraver_ateles.lsf

Step 3:
Now, analyse the files written by paraver.
If the file .prv does not exist you have to merge the files that are written to the set-0 directory using the merge.sh script:
  ./test/performance/paraver/merge.sh ateles
Load the paraver module:
  module load UNITE  paraver/4.0.10
  wxparaver ateles.prv 

(load config files from test/performance/paraver/configs/)


