profilage_code.md

@@ -8,7 +8,7 @@ The tools that were tested are proposed:
 -   [TAU](https://www.cs.uoregon.edu/research/tau/home.php), which allows the profiling of `for` loops
 -   [Scalasca](https://www.scalasca.org/)
 
-In order to be able to perform source instrumentation using Tau, the [PDT]() [Salt](https://github.com/ParaToolsInc/salt) source instrumentation tool must be installed.
+In order to be able to perform source instrumentation using Tau, the [PDT](https://www.cs.uoregon.edu/research/pdt/home.php) and [Salt](https://github.com/ParaToolsInc/salt) source instrumentation tool must be installed.
 
 ## Preparing the install
 
@@ -308,10 +308,10 @@ Next, execute your code as follows:
 ./test.exe
 ```
 
-A `scorep-` folder will appear containing all the profiling informations. It can be opened by using the `paraprof` tool as follows:
+A `paraprof.0.0.0` file will appear containing all the profiling informations. It can be opened by using the `paraprof` tool as follows:
 
 ```
-paraprof scorep-20250310_1624_81500554863145/profile.cubex &
+paraprof profile.0.0.0 &
 ```
 
 > **Note**: `.cubex` files can also be analysed using the Cube software, available as an App Image [here](https://apps.fz-juelich.de/scalasca/releases/cube/4.8/dist/CubeGUI-4.8.2.AppImage): `CubeGUI-4.8.2.AppImage scorep-20250310_1624_81500554863145/profile.cubex &`
@@ -321,6 +321,11 @@ paraprof scorep-20250310_1624_81500554863145/profile.cubex &
 To profile a code with Score-P, you first need to define some environment variables:
 
 ```
+export MPICH_CXX=g++
+export MPICH_CC=gcc
+export MPICH_FC=gfortran
+export MPICH_F77=gfortran
+
 export LD_LIBRARY_PATH=$CONDA_PREFIX/lib:$PROFILER_PATH_SCOREP/lib
 export PATH=$PROFILER_PATH_SCOREP/bin:$PATH
 export PATH=$PROFILER_PATH_SCOREP/x86_64/bin/:$PATH