tune_nemo.md

@@ -12,12 +12,11 @@
 ## Vertical grid
 
 
-Here graph for ORCA2 ORCA025 vertical grid depth* and e3*
-
-Normally, common vertical grid is used , if not (for one another config..)  
+Here we show a view of ORCA2/ORCA025 vertical grid with depth* and vertical scale factor e3*
 
 ![Depth grid (NTATL025-SARG)](images/plot_depth_ORCA.png)
 
+Normally, vertical grid from ORCA family is used.  
 
 
 
@@ -33,16 +32,23 @@ Normally, common vertical grid is used , if not (for one another config..)
 | section available | some keys | Description / tips  | dependency |
 |:---:|:---:|:---:|:---:|
 | namrun | nn_rstctl | 2: read the date on restart file | |
-|         | ln_rstart | T  |  |  
+|         | ln_rstart | T / F |  |  
 | namdom | ln_linssh | linear free surface :  e3 before, now and after are set equal one for all, and we use exactly the same calculation as in non-linear case (except that update of e3 at each time-step is by-passed)  |  | 
-|  | rn_dt  | time step |  divisible by 86400s : .. 900/960/1080/1152/1200/1350/1440/1600/1800.. blabla |
-|  | rn_hmin | -  | tricky for runoff for high resolution config  |
-| namtsd | ln_tsd_init | | if F can be read  reatrt file if ln_restart T |
-| namsbc | nn_fsbc | ( timestep * nn_fsbc )./60 = frequency in minutes you prescribed the 1h atmo field interpolated in time )   | for instance if 1h hour data input (ts=150s/nn_fsbc=8) => each 20 min,  use of data interpolated / better if 15,20,30 ...  | 
+|  | rn_dt  | time step |  divisible by 86400s : .. 900/960/1080/1152/1200/1350/1440/1600/1800..  |
+|  | rn_hmin | -  | Minimum levels nemo could see (tricky for runoff to deal with high resolution config)  |
+| namtsd | ln_tsd_init | | if False,  it will wait for a restart file (if ln_restart T) |
+| namsbc | nn_fsbc | ( timestep * nn_fsbc )./60 = frequency in minutes you prescribed the 1h atmo field interpolated in time )   | for instance if you have 1h hour input frequency (ts=150s/nn_fsbc=8) => each 20 min, nemo will interpolate your input data / better if 15,20,30 ...  | 
 | nambdy | ln_dm2dc    = .false. | | if shortwave inputs frequency <24h  then ln_dm2dc    = .false. |
 | nambdy | ln_tra_dmp=.false. | | if condition "frs" on tracers  : cn_tra ='frs' the same  for "dyn3d" |
 
 
+rappel 
+bdy avec marées
+bdy differentes facon de precrire
+
+runoff
+
+
 <a name="tune-nemo-tuning-config"></a>
 ========================
 #### Some Tuning for your config
@@ -62,7 +68,7 @@ to process tides simulation on namelist_cfg:
   * variable vertical coordinate / &nam_vvl  / *zstar* ln_vvl_zstar = T 
   * Hydrostatic pressure gradient option / &namdyn_hpg / ln_hpg_sco  = .true.   !  s-coordinate (standard jacobian formulation)
   * The total volume correction is not working with tides.  ln_vol=.FALSE.
-
+  * rajout bdy line
  
 _Update bathy_ :
 
@@ -144,7 +150,7 @@ then, reprocess your nesting, you will have :
 
 
 4 )
-On Domaincfg tools, we use the new bathymetry file :
+On Domaincfg tools, we use the new bathymetry files :
 ```console
 ln -s ../NESTING/1_coordinates_ORCA12.nc coordinates.nc
 ln -s ../NESTING/1_bathy_meter_ORCA12.nc bathy_meter.nc
@@ -193,6 +199,10 @@ _Trends mld_:
          ln_tra_trd = .true. ! (T) 3D tracer trend output
          ln_tra_mxl = .true. ! (T) 2D tracer trends averaged over the mixed layer
      d) on the file_def xml file , activate trends mld  ==>   enable=.TRUE.
+     e) if one year 365 days , be dividible by the time step ....
+
+
+_Trends 3D_:
 
 
 _Tides Diags_: