MEDUSA-DOCU-:-Rivers.md

@@ -71,7 +71,7 @@ first runs did not work because of something in the newly made river input files
 * Andrew gave another go with the last results in mind to improve the results      
   This Time the automation has been run on both DIN/SIL and DIC/ALK riverine input sets.    
   It seems to runs better, the model runs for 10years before failing. The run use the `fct` advection scheme for the passive tracers (same all physics) which is the one having the most chance of failing - just to avoid having to retest everything again. and this set of files :   
-  ```fortran 
+```fortran 
 &nammsa_river
    ln_read_rivn   = .true.
    ln_read_rivsi  = .true.
@@ -91,7 +91,7 @@ first runs did not work because of something in the newly made river input files
    sn_riv_c  =  'river42_total_DIC_flux_LS200km_SP10_5ITER_ORCA025.nc',  -12 , 'RIV_C'   ,   .true.  , .true. , 'yearly'  ,    ''            ,    ''    ,    ''
    sn_riv_a  =  'river42_total_ALK_flux_LS200km_SP10_5ITER_ORCA025.nc',  -12 , 'RIV_ALK' ,   .true.  , .true. , 'yearly'  ,    ''            ,    ''    ,    ''
 /
-  ```
+```
   The error is no more in the Arctic rivers.    
   It still is a river problem, but around china/korea. 1 pixel switch to crazy DIC :   
   <img src="uploads/7ecaf7642c7d63e863e79882d8166cca/image.png" width=49%>
@@ -100,4 +100,4 @@ first runs did not work because of something in the newly made river input files
   * A quick test could be to add the nutrient down to a shallower depth of 10m instead of 70. 
   * we could also strengthen the C security we've added in the C uptake... 
   I quickly check by changing the river depth. we'll see. 
-  With river, the total production in 1986 is of 31 Pg-C per y still too low for our liking. this will need some tweaking. 
+  With river, the total production in 1986 is of 31 Pg-C per y still too low for our liking. this will need some tweaking.
\ No newline at end of file