How-to-SETTE-test-MEDUSA..md

@@ -27,8 +27,8 @@ Running the tests requires very little work.
 A detailed [How-to page](https://sites.nemo-ocean.io/user-guide/sette.html) explaining SETTE tests has already been written, but to be short :
 
 1. Set your local environment.
-   * make sure you've `module loaded` all needed modules to compile NEMO (see the relevant how-to page : [how-to run on ANEMONE](How-to-run-on-ANEMONE) or [on Archer2](How-to-run-on-ARCHER2)).
-   * in the `nemo/sette/` directory add a `local_settings.sh` files that should look like the following :    
+   * Make sure you've `module loaded` all needed modules to compile NEMO (see the relevant how-to page : [how-to run on ANEMONE](How-to-run-on-ANEMONE) or [on Archer2](How-to-run-on-ARCHER2)).
+   * In the `nemo/sette/` directory add a `local_settings.sh` files that should look like the following :    
      ``` sh
      #!/bin/bash
      export SETTE_COMPILER=X86_ARCHER2-Gnu_4.2
@@ -37,7 +37,11 @@ A detailed [How-to page](https://sites.nemo-ocean.io/user-guide/sette.html) expl
      export SETTE_FORCING_DIR=/work/n01/shared/nemo/FORCING/SETTE_inputs/r4.2.0
      export SETTE_NEMO_VALIDATION_DIR=/work/n01/n01/julpal/NEMO/MEDUSA_dev/nemo/sette
      ```
-     This is an example file for Archer2. make sure to adapt to your environment, and make sure you have the apropriate compiler in `nemo/arch/`
+     This is an example file for Archer2. make sure to adapt to your environment, and make sure you have the apropriate compiler in `nemo/arch/`. \
+    Then run it :    
+    ```sh
+    . ./local_settings.sh
+    ```
 2. A little tweak
    That should not remain for long, but in `nemo/sette/BATCH_TEMPLATE/`, the SETTE scripts looks for a `batch-mpmd-${your-compiler-name}` file. it's not really used as, as you can see, the files are only comments. just copy a similar file with the right name. that does the trick.