Changes between Version 3 and Version 4 of Users/Reference Configurations/GYRE_PISCES


Ignore:
Timestamp:
2017-04-12T19:58:16+02:00 (3 years ago)
Author:
nicolasmartin
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Users/Reference Configurations/GYRE_PISCES

    v3 v4  
    1 = GYRE = 
     1= GYRE_PISCES 
    22 
    3 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]] 
    4 This configuration is coupled to [http://www.geosci-model-dev.net/8/2465/2015/ PISCES] biogeochemichal model.[[BR]] 
     3Idealized 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]] 
     4This configuration is coupled to [http://www.geosci-model-dev.net/8/2465/2015/ PISCES] biogeochemichal model. 
    55 
     6== Running GYRE as a benchmark 
    67 
    7 == Running GYRE as a benchmark: == 
     8This simple configuration can be used as a benchmark since it is easy to increase resolution (and in this case no physical meaning of outputs): 
    89 
    9 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]] 
    10  
    11  
    12 1 - Choose the grid size:[[BR]] 
    13  
    14 In CONFIG/GYRE/EXP00, edit your namelist_cfg file to change the jp_cfg, jpi, jpj, jpk namelist variables in &namcfg:[[BR]] 
    15  
     101. Choose the grid size 
     11In `CONFIG/GYRE/EXP00`, edit your `namelist_cfg` file to change the `jp_cfg`, `jpi`, `jpj`, `jpk` variables in &namcfg: 
    1612||JP_CFG        ||JPI   ||JPJ   ||JPK   ||Number of points      ||Equivalent to|| 
    1713||1             ||  30  ||  20  ||101   ||60600                 ||GYRE 1°      || 
     
    2117||200           ||6000  ||4000  ||101   ||2424000000            ||ORCA 1/16°   || 
    2218 
    23 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]] 
    24  
    25   
     192. 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 
    2620{{{ 
    2721nn_bench    =    1     !  Bench mode (1/0): CAUTION use zero except for bench 
    28  
    2922}}} 
    3023 
    31 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]] 
    32  
    33     
     243. 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`) 
    3425{{{ 
    3526rn_rdt      = 1200.     !  time step for the dynamics 
    3627}}} 
    37   
    3828 
    39 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]] 
    40 In your namelist_cfg file, in edit namelist_cfg and in the &namsplit namelist, add the following line:[[BR]] 
    41  
    42   
     294. 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 
     30{{{#!sh 
     31makenemo [...] add_key "key_dynspg_ts" del_key "key_dynspg_flt" 
     32}}} 
     33In your `namelist_cfg` file, edit namelist_cfg and in the &namsplit namelist, add the following line:  
    4334{{{ 
    44  nn_baro       =    30               !  Number of iterations of barotropic mode/ 
     35nn_baro       =    30               !  Number of iterations of barotropic mode/ 
    4536}}} 
    4637 
     38`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. 
    4739 
    48 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]] 
     40The GYRE CPP keys, namelists and scripts can be explored in the `GYRE` configuration directory (`NEMOGCM/CONFIG/GYRE` and `NEMOGCM/CONFIG/GYRE/EXP00`). 
    4941 
    50 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]] 
     42{{{#!div class="important" 
     43(Nicolas) '''Not clear''' 
    5144 
    52 Find here monthly mean outputs of 10 years run - trunk of 1 year -[[BR]] 
     45Find here monthly mean outputs of 10 years run - trunk of 1 year - 
    5346Download the files from the [http://prodn.idris.fr/thredds/catalog/ipsl_public/reee451/NEMO_OUT/GYRE/catalog.html DODS server of IDRIS ] 
     47}}}