User's-Guide/Installation/Machine-specific-stuff.md

-# Machine specifc stuff
+[[_TOC_]]
 
-Most cluster have their specificities that can be used to boost the developement cycle or  that must be worked around.
+Most cluster have their specificities that can be used to boost the development cycle or  that must be worked around.
 
-## Testing
+# Testing
 
 Some cluster specific scripts have been developed that allows to run the tests in parallel. These scripts will automatically dispatch the tests on the cluster and track the results. From the build directory:
 
@@ -12,9 +12,8 @@ Some cluster specific scripts have been developed that allows to run the tests i
 
 refers to those script help for more details.
 
-## Occigen (CINES)
-
-### Environment
+# Occigen (CINES)
+## Environment
 You need load the environment that way in order to workaround an *occigen* specific environment dependency issue:
 ```
 module purge
@@ -46,9 +45,9 @@ Once this environment is loaded, you just need to run `cmake`:
 
 refer to those script help (`-h`) option for more details.
 
-## Licallo (O.C.A.)
+# Licallo (O.C.A.)
 
-### Environment
+## Environment
 You need load the environment that way in order to workaround an *occigen* specific environment dependency issue:
 ```
 module purge
@@ -66,28 +65,28 @@ module load boost-intel19/1.68.0
 module load hdf5-intel2019/1.8.20-seq
 module load git
 ```
-### Configuration
+## Configuration
 
 Once this environment is loaded, you just need to run `cmake`:
 ```
 [elega@login0:~/fargOCA/build]$ cmake [options] ..
 ```
-### Build
+## Build
  As usual
 
-### Testing
+## Testing
 
 Platform specific scripts allows you to run the test in parallel
  * `<builddir>/tools/dev/licTest.sh` dispatch the tests on the cluster and track the result. You can interrupt the monitoring phase and resume it later with...
  *  `<builddir>/tools/dev/licTrackTest.sh` track the dispatched tests.
 
 refer to those script help (`-h`) option for more details.
-### Build
+## Build
 As usual
 
-## Ada (Idris)
+# Ada (Idris)
 
-### Environment
+## Environment
 
 The following environment has been tested
 
@@ -119,7 +118,7 @@ module load cmake/3.7.2
 [roth005@ada338: bld2]$ 
 ```
 
-### Configuration
+## Configuration
 MPI detect does not work that well, so wee need to provide the MPI wrapper as compilers:
 ```
 [roth005@ada338: bld2]$ cmake -DCMAKE_BUILD_TYPE=Release -DCMAKE_C_COMPILER=mpiicc -DCMAKE_CXX_COMPILER=mpiicpc ../
@@ -143,7 +142,7 @@ MPI detect does not work that well, so wee need to provide the MPI wrapper as co
 
 As usual
 
-### Test:
+## Test:
 We test the unit tests and integration tests (with 4 MPI process) with:
 ```
 <builddir>$./tools/dev/adaTest.sh
@@ -153,9 +152,9 @@ You can interupt the tracking phase and relaunch it wth:
 ```
 <builddir>$./tools/dev/adaTrackTest.sh
 ```
-## Aurora (Lund)
+# Aurora (Lund)
 
-### Environment
+## Environment
 
 Currently running with:
 ```
@@ -173,19 +172,19 @@ Currently Loaded Modules:
 [alain@aurora1 rel]$ 
 ```
 
-### Configuration
+## Configuration
 
 ```
 cmake -DCMAKE_C_COMPILER=icc -DCMAKE_CXX_COMPILER=icpc ..
 ```
 
-### Build
+## Build
 
 ```
 make -j 8
 ```
 
-### Testing
+## Testing
 
 For ctest, srun needs to know the slurm account, which can be set in the .bashrc: