Changes between Version 3 and Version 4 of Users/ReferenceConfigurations/GYRE_PISCES

Timestamp:

2017-04-12T19:58:16+02:00 (7 years ago)

Author:

nicolasmartin

Comment:

--

Users/ReferenceConfigurations/GYRE_PISCES

@@ -1 @@
-= GYRE =
+= GYRE_PISCES
 
-Idealized configuration representing double gyres in the North hemisphere,Beta-plane with a regular grid spacing at 1° horizontal resolution (and possible use as a benchmark by easily inscreasing grid size), 101 vertical levels, forced with analytical heat, freshwater and wind-stress fields.[[BR]]
-This configuration is coupled to [http://www.geosci-model-dev.net/8/2465/2015/ PISCES] biogeochemichal model.[[BR]]
+Idealized configuration representing double gyres in the North hemisphere, Beta-plane with a regular grid spacing at 1° horizontal resolution (and possible use as a benchmark by easily inscreasing grid size), 101 vertical levels, forced with analytical heat, freshwater and wind-stress fields.[[BR]]
+This configuration is coupled to [http://www.geosci-model-dev.net/8/2465/2015/ PISCES] biogeochemichal model.
 
+== Running GYRE as a benchmark
 
-== Running GYRE as a benchmark: ==
+This simple configuration can be used as a benchmark since it is easy to increase resolution (and in this case no physical meaning of outputs):
 
-This simple configuration can be used as a benchmark since it is easy to increase resolution (and in this case no physical meaning of outputs):[[BR]]
-
-
-1 - Choose the grid size:[[BR]]
-
-In CONFIG/GYRE/EXP00, edit your namelist_cfg file to change the jp_cfg, jpi, jpj, jpk namelist variables in &namcfg:[[BR]]
-
+1. Choose the grid size
+In `CONFIG/GYRE/EXP00`, edit your `namelist_cfg` file to change the `jp_cfg`, `jpi`, `jpj`, `jpk` variables in &namcfg:
 ||JP_CFG        ||JPI   ||JPJ   ||JPK   ||Number of points      ||Equivalent to||
 ||1             ||  30  ||  20  ||101   ||60600                 ||GYRE 1°      ||
@@ -21 +17 @@
 ||200           ||6000  ||4000  ||101   ||2424000000            ||ORCA 1/16°   ||
 
-2 - In namelist_cfg again, avoid problems in the physics (and results will not be meaningful in terms of physics) by setting nn_bench = 1 in &namctl[[BR]]
-
- 
+2. In `namelist_cfg` again, avoid problems in the physics (and results will not be meaningful in terms of physics) by setting `nn_bench = 1` in &namctl
 {{{
 nn_bench    =    1     !  Bench mode (1/0): CAUTION use zero except for bench
-
 }}}
 
-3 - If you increase domain size, you may need to decrease time-step (for stability) by changing rn_rdt value in &namdom (i.e. for jp_cfg=150, ORCA12 equivallent, use rn_rdt=1200.)[[BR]]
-
-   
+3. If you increase domain size, you may need to decrease time-step (for stability) by changing `rn_rdt` value in &namdom (i.e. for `jp_cfg = 150`, ORCA12 equivalent, use `rn_rdt=1200`)
 {{{
 rn_rdt      = 1200.     !  time step for the dynamics
 }}}
- 
 
-4- Optionnal, in order to increase the number of MPI communication for benchmark purposes: you can change the number of sub-timesteps computed in the time-splitting scheme each iteration. First change the list of active cpp keys for your experiment, in CONFIG/"your configuration name"/cpp_"your configuration name".fcm : replace key_dynspg_flt by add key_dynspg_ts, and recompile/ create your executable again (makenemo...).[[BR]]
-In your namelist_cfg file, in edit namelist_cfg and in the &namsplit namelist, add the following line:[[BR]]
-
- 
+4. Optional, in order to increase the number of MPI communication for benchmark purposes: you can change the number of sub-timesteps computed in the time-splitting scheme each iteration. First change the list of active CPP keys for your experiment, in `CONFIG/"your configuration name"/cpp_"your configuration name".fcm` : replace key_dynspg_flt by key_dynspg_ts and recompile/create your executable again
+{{{#!sh
+makenemo [...] add_key "key_dynspg_ts" del_key "key_dynspg_flt"
+}}}
+In your `namelist_cfg` file, edit namelist_cfg and in the &namsplit namelist, add the following line: 
 {{{
- nn_baro       =    30               !  Number of iterations of barotropic mode/
+nn_baro       =    30               !  Number of iterations of barotropic mode/
 }}}
 
+`nn_baro=30` is a kind of minimum (we usually use 30 to 60).So than increasing the `nn_baro` value will increase the number of MPI communications.
 
-nn_baro=30 is a kind of minimum (we usually use 30 to 60).So than increasing the nn_baro value will increase the number of MPI communications.[[BR]]
+The GYRE CPP keys, namelists and scripts can be explored in the `GYRE` configuration directory (`NEMOGCM/CONFIG/GYRE` and `NEMOGCM/CONFIG/GYRE/EXP00`).
 
-The GYRE cpp keys, namelists and scripts can be explored in the GYRE configuration directory (NEMOGCM/CONFIGURATION/GYRE and NEMOGCM/CONFIGURATION/GYRE/EXP00) , in the NEMO browser (using the same login as the web site).[[BR]]
+{{{#!div class="important"
+(Nicolas) '''Not clear'''
 
-Find here monthly mean outputs of 10 years run - trunk of 1 year -[[BR]]
+Find here monthly mean outputs of 10 years run - trunk of 1 year -
 Download the files from the [http://prodn.idris.fr/thredds/catalog/ipsl_public/reee451/NEMO_OUT/GYRE/catalog.html DODS server of IDRIS ]
+}}}