Changes between Version 1 and Version 2 of doc/tec/nesting

Timestamp:

Mar 7, 2017 1:08:04 PM (8 years ago)

Author:

maronga

Comment:

--

doc/tec/nesting

@@ -3 +3 @@
 
 == Job preparation ==
-The nesting system is activated by specifying a {{{&nestpar}}} NAMELIST in the _p3d file of the root domain, e.g.:
+The following example provide a step-by-step tutorial on how to set up a nesting system with one parent (root) domain and two child domains.
+
+1. Prepare parameter files for all domains, e.g. for run with topography and separate topography data for each domain:
+{{{
+testrun_p3d (root/parent domain)
+testrun_01_p3d (child domain 1)
+testrun_02_p3d (child domain 2)
+testrun_topo
+testrun_01_topo
+testrun_02_topo
+}}}
+
+2. The nesting system is activated by specifying a {{{&nestpar}}} NAMELIST in the _p3d file of the '''root domain''', e.g.:
 {{{
  &nestpar domain_layouts = 'root domain',      1,  -1,  24,    0.0,    0.0,
@@ -12 +24 @@
 /
 }}}
+For details on the parameters, see [wiki:doc/app/nestpar#nestpar nestpar].
+
+3. Add file connection statements for all child domains to the {{{.mrun.config}}} file, 
+{{{
+#----------------------------------------------------------------------------
+# List of input-files for nested model runs
+#----------------------------------------------------------------------------
+PARIN_01                  in:job        nest#      $base_data/$fname/INPUT   _01_p3d
+PARIN_02                  in:job        nest#      $base_data/$fname/INPUT   _02_p3d
+TOPOGRAPHY_DATA_01        in:locopt     nest#      $base_data/$fname/INPUT   _01_topo
+TOPOGRAPHY_DATA_02        in:locopt     nest#      $base_data/$fname/INPUT   _02_topo
+}}}
+
+4. Execute {{{mrun}}} and specify the nesting input files, i.e.,
+{{{
+mrun -d testrun -r "d3# nest# ts# pr# ..." -X "72" ...
+}}}
+Make sure that the total number of PEs (here 72) the sum of the PEs allocated for the individual domains (3 x 24).