New URL for NEMO forge!   http://forge.nemo-ocean.eu

Since March 2022 along with NEMO 4.2 release, the code development moved to a self-hosted GitLab.
This present forge is now archived and remained online for history.
Changeset 7025 for branches/2016/dev_r6999_CONFIGMAN_1/NEMOGCM/TOOLS/SIREN/src/docsrc/2_quickstart.md – NEMO

Ignore:
Timestamp:
2016-10-13T11:08:38+02:00 (8 years ago)
Author:
jpaul
Message:

see ticket #1781

File:
1 edited

Legend:

Unmodified
Added
Removed
  • branches/2016/dev_r6999_CONFIGMAN_1/NEMOGCM/TOOLS/SIREN/src/docsrc/2_quickstart.md

    r6393 r7025  
    77Actually SIREN creates all the input files you need to run a NEMO regional configuration.<br/> 
    88  
    9 SIREN is composed of a set of 5 Fortran programs : 
     9SIREN is composed of a set of 6 Fortran programs : 
    1010<ul> 
    1111 <li>create_coord.f90 to create regional grid coordinates.</li> 
     
    1616 This break may cause inconsistency between forcing fields  at boundary and regional fields. 
    1717 </li> 
     18 <li>create_meshmask.f90 to create meshmask file(s) which contain(s) all the ocean domain informations.</li> 
    1819 <li>create_restart.f90 to create initial state file from coarse grid restart 
    1920 or standard outputs. 
     
    3536Here after we briefly describe how to use each programs, 
    3637and so how to create your own regional configuration. 
    37 @note A set of GLORYS files (global reanalysis on *ORCA025* 
    38 grid), as well as examples of namelists are available in dods repository.<br/> 
    39 You could create and forced a first release of your own regional configuration, 
    40 with those files.  
     38@note As demonstrator for a first start a set of GLORYS files (global reanalysis on *ORCA025* grid), as well as examples of namelists are available [here](https://cloud.mercator-ocean.fr/public.php?service=files&t=877fb1b6e4f589340fc0df1ea6a53228). 
     39 
    4140<!-- ######################################################################  --> 
    4241# Create coordinates file # {#coord} 
     
    121120example: ORCA05</dd> 
    122121</dl> 
    123 @sa For more information see @ref md_docsrc_6_perio 
     122@sa For more information see @ref md_src_docsrc_6_perio 
    124123</dd> 
    125124</dl> 
     
    150149~~~~~~~~~~~ 
    151150@image html grid_zoom_60.png 
    152 @image latex grid_zoom_40.png 
     151<center>@image latex grid_zoom_40.png 
     152</center> 
    153153<!-- @note ghost cells all around the grid are not shown here. --> 
    154154 
     
    167167~~~~~~~~~~~ 
    168168@image html grid_glob_over_30.png 
    169 @image latex grid_glob_over_20.png 
     169<center>@image latex grid_glob_over_20.png 
     170</center> 
    170171<!-- @note in blue, the east-west overlap band of ORCA grid. --> 
    171172 
     
    184185~~~~~~~~~~~ 
    185186@image html grid_glob_band_30.png 
    186 @image latex grid_glob_band_20.png 
     187<center>@image latex grid_glob_band_20.png 
     188</center> 
    187189 
    188190</ul> 
     
    361363 
    362364<!-- ######################################################################  --> 
     365# Create meshmask (ocean domain informations) # {#meshmask} 
     366 
     367 
     368Depending on the vertical grid you choose to use, NEMO may not see the bathymetry as you defined it just before. To get the ocean domain informations as seen by NEMO, SIREN allows you to create the meshmask file(s) which contain(s) all those informations. 
     369 
     370To create this new meshmask file(s), you have to run : 
     371~~~~~~~~~~~~~~~~~~ 
     372./SIREN/create_meshmask.exe create_meshmask.nam 
     373~~~~~~~~~~~~~~~~~~ 
     374 
     375Here after is an example of namelist for *create_meshmask.exe*.<br/> 
     376In this example, you create one meshmask file named *mesh_mask.nc*.<br/> 
     377It uses coordinates file *coord_fine.nc* to define horizontal grid. 
     378and defines z-coordinate with partial steps. 
     379The minimum depth of the final Bathymetry is 10m.  
     380~~~~~~~~~~~ 
     381&namlog 
     382/ 
     383 
     384&namcfg 
     385   cn_varcfg = "PATH/NEMOGCM/TOOLS/SIREN/cfg/variable.cfg" 
     386/ 
     387 
     388&namin 
     389   cn_bathy = "PATH/bathy_merged.nc" 
     390   cn_coord = "PATH/coord_fine.nc" 
     391   in_perio = 4 
     392/ 
     393 
     394&namhgr 
     395   in_mshhgr = 0 
     396/ 
     397 
     398&namzgr 
     399   ln_zps   = .TRUE. 
     400   in_nlevel= 75 
     401/ 
     402 
     403&namdmin 
     404   dn_hmin=10. 
     405/ 
     406 
     407&namzco 
     408   dn_ppsur   = -3958.951371276829 
     409   dn_ppa0    =   103.953009600000 
     410   dn_ppa1    =     2.415951269000 
     411   dn_ppkth   =    15.351013700000 
     412   dn_ppacr   =     7.000000000000 
     413   dn_ppdzmin = 6. 
     414   dn_pphmax  = 5750. 
     415   ln_dbletanh= .TRUE. 
     416   dn_ppa2    =   100.760928500000 
     417   dn_ppkth2  =    48.029893720000 
     418   dn_ppacr2  =    13.000000000000 
     419/ 
     420 
     421&namzps 
     422   dn_e3zps_min = 25. 
     423   dn_e3zps_rat = 0.2 
     424/ 
     425 
     426&namsco 
     427/ 
     428 
     429&namcla 
     430/ 
     431 
     432&namlbc 
     433/ 
     434 
     435&namwd 
     436/ 
     437 
     438&namgrd 
     439/ 
     440 
     441&namzoom 
     442/ 
     443 
     444&namout 
     445   in_msh = 1 
     446/ 
     447~~~~~~~~~~~ 
     448 
     449Let's get describe this namelist more accurately.<br/> 
     450 
     451As previously, we have the **namlog** and **namcfg** describe above.<br/> 
     452 
     453The **namin** sub-namelist defines the Bathymetry to be used. 
     454Mainly SIREN need Bathymetry to create meshmask. 
     455Here we also read coordinates directly on a file.  
     456@note here again you could add the *in_perio* parameter if need be i.e. if your 
     457Bathymetry was not created by SIREN.<br/> 
     458@note By default SIREN suppress closed sea/lake from the ORCA domain. 
     459 
     460The **namhgr** sub-namelist defines the horizontal grid. 
     461the type of horizontal mesh is choose between :<ul> 
     462<li> in_mshhgr=0 : curvilinear coordinate on the sphere read in coordinate.nc</li> 
     463<li> in_mshhgr=1 : geographical mesh on the sphere with regular grid-spacing</li> 
     464<li> in_mshhgr=2 : f-plane with regular grid-spacing</li> 
     465<li> in_mshhgr=3 : beta-plane with regular grid-spacing</li> 
     466<li> in_mshhgr=4 : Mercator grid with T/U point at the equator</li> 
     467<li> in_mshhgr=5 : beta-plane with regular grid-spacing and rotated domain (GYRE configuration)</li> 
     468</ul> 
     469 
     470The **namzgr** sub-namelist allows to choose the type of vertical grid (z-coordinate full steps, partial steps, sigma or hybrid coordinates) and the number of level. 
     471 
     472The **namdmin** sub-namelist dfines the minimum ocean depth. It could be defines in meter (>0) or in number of level (<0). 
     473 
     474The **namzco** sub-namelist defines respectively parameters to compute z-coordinate vertical grid (**needed for all type of vertical grid**) 
     475<!-- By default, those parameters are defined the same way than in GLORYS (i.e. 75 vertical levels).<br/> --> 
     476 
     477The **namzps** sub-namelist defines extra parameters needed to define z-coordinates partial steps. 
     478 
     479The **namsco** sub-namelist defines extra parameters needed to define sigma or hybrid coordinates (not needed here). 
     480 
     481The **namcla** sub-namelist defines cross land advection for exchanges through some straits only used for ORCA2 (see namgrd). 
     482 
     483The **namlbc** sub-namelist defines lateral boundary conditions at the coast. It is needed to modify the fmask. 
     484 
     485The **namwd** sub-namelist defines the wetting and drying parameters if activated (see namzgr sub-namelist) 
     486 
     487The **namgrd** and **namzoom** sub-namelists define grid configuration. Those namelist only activated local correction. 
     488 
     489Finally, this **namout** sub-namelist defines the number output file(s).<br/> 
     490 
     491@sa For more information about how to create meshmask, see create_meshmask.f90 
     492 
     493<!-- ######################################################################  --> 
    363494# Create initial state # {#restart} 
    364495 
     
    442573Finally, this **namout** sub-namelist defines the output files.<br/> 
    443574Here we ask for output on 81 processors, with *restart_out.nc* as file "basename".<br/> 
    444 So SIREN computes the optimal layout for 81 porcessors 
     575So SIREN computes the optimal layout for 81 processors 
    445576available,<br/> 
    446 and split restart on output files named *restart_out_num.nc*, where *num* is the porc number. 
     577and split restart on output files named *restart_out_num.nc*, where *num* is the proc number. 
    447578 
    448579@note SIREN could also create the other fields you may need for 
     
    592723   <b> 
    593724   - @ref index 
    594    - @ref md_docsrc_1_install 
    595    - @ref md_docsrc_2_quickstart 
    596    - @ref md_docsrc_3_support_bug 
    597    - @ref md_docsrc_4_codingRules 
    598    - @ref md_docsrc_5_changeLog 
     725   - @ref md_src_docsrc_1_install 
     726   - @ref md_src_docsrc_2_quickstart 
     727   - @ref md_src_docsrc_3_support_bug 
     728   - @ref md_src_docsrc_4_codingRules 
     729   - @ref md_src_docsrc_5_changeLog 
    599730   - @ref todo 
    600731   </b> 
Note: See TracChangeset for help on using the changeset viewer.