profilage_code.md

@@ -4,6 +4,7 @@ title: Profilage de Code
 
 
 
+
 # Code profilers
 
 In this Wiki, we will provide a methodology to install and run some code profilers. This has been tested on a specific Conda environment.
@@ -263,3 +264,27 @@ paraprof scorep-20250310_1624_81500554863145/profile.cubex &
 > **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 &`
+
+### Profile with Scalasca
+
+To profile a code with Scalasca, you need to compile the code by replacing:
+
+- `g++` -> `skin g++`
+- `gfortran` -> `skin gfortran`
+- `mpicxx` -> `skin mpicxx`
+- `mpif90` -> `skin mpif90`
+- `gcc` -> `skin gcc`
+- `mpicc` -> `skin mpicc`
+- `mpif77` -> `skin mpif77`
+
+Once your code has been compiled, you can execute it as follows:
+
+```
+scan test.exe
+```
+
+**Note**: to activate tracing, add a `-t` option to the `scan` command:
+
+```
+scan -t test.exe
+```
\ No newline at end of file