How to use allinea-forge

Software
Version
Cluster
allinea-forge
18.1.1
Tegner

Load the appropiate compilers and the module allinea-reports/18.1.1

$ module load gcc/6.2.0
$ module load openmpi/2.0-gcc-6.2
$ module load allinea-forge/18.1.1

Running example

Here is an example from the official documentation

$ mkdir forge-test
$ cd forge-test
$ cp /afs/pdc.kth.se/pdc/vol/allinea-forge/18.1.1/amd64_co7/examples/wave.c .
$ mpicc  wave.c -o wave.teg -lm -g

The binary wave.teg is now instrumented for Allinea MAP (and DDT).

In order to run you must prepend the mpirun command in your bash script or interactive run with map –profile. Here is a simple script that runs the example compiled above:

#!/bin/bash -l

#SBATCH -J forge-test
#SBATCH -t 0:03:00
#SBATCH --nodes 2
#SBATCH -n 48

map --profile [mpirun] -n 48 ./wave.teg

One can also ignore the mpirun command but not its options (see above example). Allinea MAP is aware of that applications are run with mpirun on Tegner. The run will generate two additional files next to the normal output of the mapped application, namely:

<app>_<cores>p_<date-stamp>_<time-stamp>**.map**

You can open the map file in Allinea Forge GUI. The reuslt will look similar to this one:

../../../../_images/map-summary.png

Disclaimer

PDC takes no responsibility for the correctness of results produced with the binaries. Always evaluate the binaries against known results for the systems and properties you are investigating before using the binaries for production jobs.