How-to-run-MEDUSA-1D-on-ARCHER2-and-ANEMONE.md

@@ -5,7 +5,7 @@
 To do this we assume you already have your environment ready and have checked out a NEMO4-MEDUSA branch.
 If not, check the appropriate page from this [ wiki page](https://git.noc.ac.uk/acc/medusa_4.2.x/) .
 
-This 1D how to page is valid for both `ARCHER2` and `ANEMONE`. Just mind the path and libraries to load, depending the machine you are running with.  
+This how to page is valid for both `ARCHER2` and `ANEMONE`. Just mind the path and libraries to load, depending the machine you are running with.  
 * On `ARCHER2` 
   ```sh
   NEMO='/work/n01/n01/${userID}/medusa_4.2.x/nemo'
@@ -19,9 +19,14 @@ This 1D how to page is valid for both `ARCHER2` and `ANEMONE`. Just mind the pat
   COMPILER='x86-64_Anemone'
   ```
 
-## Compiling 1D config
+## Compiling MEDUSA 1D "the old way"
+
+I call it "the old way", as you'll have to compile in few different steps, manually. You can use this way of doing to learn and understand how the config works. If you just want to compile and get something running, jump to the next section : ` Compiling MEDUSA 1D "the easy way"`
+
+### Compile the 1D config 
+
 First thing is to compile a first time a new config based on `C1D_PAPA` : 
-from your NEMO4.2 base directory (should be something like `${NEMO}` defined just above, but od course, adapt to your own medusa path).
+from your NEMO4.2 base directory (should be something like `${NEMO}` defined just above, but of course, adapt to your own medusa path).
 * Some corrections listed in Andrews documentations for ARCHER2 only ([here](https://docs.archer2.ac.uk/research-software/nemo/nemo/#setting-up-the-correct-environment)  -- 
   This should have already been done to compile your `ORCA2_MEDUSA` configuration, but better to double-check) : 
   * Update `ext/FCM/lib/Fcm/Config.pm ` by changing `FC_MODSEARCH => '', ` into `FC_MODSEARCH => '-J', `
@@ -35,7 +40,7 @@ from your NEMO4.2 base directory (should be something like `${NEMO}` defined jus
   ```
   It should compile successfully the dynamic side only, but will create the right files at the right place. Here our 1D config is called `C1D_MED`
 
-## Compile MEDUSA 1D 
+### Compile MEDUSA 1D 
 Modify our new config component and cpp keys. At the moment they are based on `C1D_PAPA` which is dynamics only.
 * update `cfgs/work_cfgs.txt` 
   change our config line to be (just add the TOP component)  : 
@@ -58,6 +63,27 @@ Modify our new config component and cpp keys. At the moment they are based on `C
    ```sh
    ./makenemo -m ${COMPILER} -r C1D_MED -j 16
    ```
+
+## Compiling MEDUSA 1D "the easy way"
+
+To make things easier, and reduce the risks of error, i've added a MEDUSA 1D reference configuration : `C1D_MED_PAPA`. That means that you just need to compile it to get MEDUSA running in 1D. 
+
+So, you still need to load the right libraries, and make sure you use the right compiler, before compiling your config. Adapting from the section above :  
+
+From your NEMO4.2 base directory (should be something like `${NEMO}` defined just above, but of course, adapt to your own medusa path).
+* Some corrections listed in Andrews documentations for ARCHER2 only ([here](https://docs.archer2.ac.uk/research-software/nemo/nemo/#setting-up-the-correct-environment)  -- 
+  This should have already been done to compile your `ORCA2_MEDUSA` configuration, but better to double-check) : 
+  * Update `ext/FCM/lib/Fcm/Config.pm ` by changing `FC_MODSEARCH => '', ` into `FC_MODSEARCH => '-J', `
+  * Add this arch file into your `arch` directory :
+    ```sh 
+    cp /work/n01/shared/nemo/ARCH/arch-X86_ARCHER2-Gnu_4.2.fcm arch/ 
+    ```  
+* Now you can compile your MEDUSA 1D configuration -- valid whatever the machine -- type : 
+  ```sh
+  ./makenemo -m  ${COMPILER} -r C1D_MED_PAPA -n C1D_MED -j 16
+  ```
+  It should compile successfully the dynamic and the passive tracer all at once. Here our 1D config is called `C1D_MED`. Compiling this way, All the files are at the right place already, so - still, double check - you should be able to happily skip the file management part of the next section. 
+ 
 ## Running The PAPA "ready to use" config.
 
 From here, NEMO-Executable is ready, but we still need to include MEDUSA's namelist and other files to be able to run it.