= Nesting parameters =
[[TracNav(doc/app/partoc|nocollapse)]]
\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
'''NAMELIST group name:''' [=#nesting_parameters '''{{{nesting_parameters}}}''']

||='''Parameter Name'''  =||='''[../fortrantypes FORTRAN]\\[../fortrantypes Type]'''  =||='''Default\\Value'''  =||='''Explanation'''  =||
|----------------
{{{#!td style="vertical-align:top;width: 150px"
[=#anterpolation_buffer_width '''anterpolation_buffer_width''']
}}}
{{{#!td style="vertical-align:top;width: 50px"
I
}}}
{{{#!td style="vertical-align:top;width: 75px"
'' 2 ''
}}}
{{{#!td
Width of the anterpolation boundary buffer in terms of number of parent-grid points. If anterpolation_buffer_width = 0, anterpolation is carried out for all parent-grid points inside the child domain except the grid planes next to the boundaries. By setting anterpolation_buffer_width > 0, makes these buffers wider accordingly. The same value is applied to all nested boundaries. \\\\ 
}}}
|----------------
{{{#!td style="vertical-align:top;width: 150px"
[=#anterpolation_starting_height '''anterpolation_starting_height''']
}}}
{{{#!td style="vertical-align:top;width: 50px"
R
}}}
{{{#!td style="vertical-align:top;width: 75px"
'' 0.0 ''
}}}
{{{#!td
This parameter controls the canopy-restricted anterpolation. It is the height in metres relative to the local terrain height above which the anterpolation is performed if in case of two-way coupling. Below this height no anterpolation is made. It is recommended to select this height in such a way that most of the building roofs, or even all of them depending on the case, are below this height. \\\\ 
}}}
|----------------
{{{#!td style="vertical-align:top;width: 150px"
[=#domain_layouts '''domain_layouts''']
}}}
{{{#!td style="vertical-align:top;width: 50px"
derived \\
TYPE \\
pmc_layout(64)
}}}
{{{#!td style="vertical-align:top;width: 75px"
none
}}}
{{{#!td
General information about the nested domains to be used.\\\\
Up to 64 domains can be used. The derived data type has the structure
{{{
   TYPE pmc_layout

      CHARACTER(len=32) ::  name

      INTEGER  ::  id
      INTEGER  ::  parent_id
      INTEGER  ::  npe_total

      REAL(wp) ::  lower_left_x
      REAL(wp) ::  lower_left_y

   END TYPE pmc_layout
}}}
{{{name}}} is the domain name given by the user. {{{id}}} is the number of the domain (can be arbitrarily chosen, but it would be good practise to number the domains in ascending order starting with 1), while {{{parent_id}}} gives the number of the domain in which this domain is embedded. The so-called ''root''-domain which includes all other ''nested''-domains should have the id 1. The ''root''-domain has no ''parent''-domain and must be given ''-1'' as its {{{parent_id}}}. {{{npe_total}}} is the number of PEs to be used for this domain. {{{lower_left_x}}} and {{{lower_left_y}}} are the coordinates in m of the south-left corner of the domain given in the root-model coordinate system. More precisely, {{{lower_left_x}}} is measured from the u-node at i=0 and {{{lower_left_y}}} from the v-node at j=0. The ''root''-domain has {{{lower_left_x}}} = ''0.0'' and {{{lower_left_y}}} = ''0.0''. Note that {{{lower_left_x}}} must be integer divisible by the parent grid dx and similarly {{{lower_left_y}}} by the parent grid dy. A ''nested''-domain must be completely embedded in its ''parent''-domain and there has to be a clearance between the lateral nest boundaries and its parent boundaries. This clearance has to be at least four parent-grid cells in case of Wicker-Skamarock advection scheme and at least two parent-grid cells in case of Piaseck-Williams advection scheme. Possible parallel nests, including their ghost-cell layers, are not allowed to overlap. \\\\
The following gives an example for defining a single nested-domain embedded in a root-domain:
{{{
domain_layouts = 'coarse',  1,  -1,  16,    0.0,    0.0,
                 'fine',    2,   1,  16,  320.0,  128.0, 
}}}
The total number of MPI-processes required by this configuration is 16 + 16 = 32. The numbers of PEs in the x- and y-directions can be additionally specified by setting {{{npex}}} and {{{npey}}} in {{{&runtime_parameters}}} for the respective domain. Of course, the condition {{{npe_total}}} = {{{npex}}} * {{{npey}}} must always hold.
}}}
|----------------
{{{#!td style="vertical-align:top"
[=#nesting_datatransfer_mode '''nesting_datatransfer_mode''']
}}}
{{{#!td style="vertical-align:top"
C*7
}}}
{{{#!td style="vertical-align:top"
'' 'mixed' ''
}}}
{{{#!td
Type of nesting datatransfer mode.\\\\ 
''cascade'', ''overlap'', or ''mixed'' data transfer mode is allowed.
}}}
|----------------
{{{#!td style="vertical-align:top"
[=#nesting_mode '''nesting_mode''']
}}}
{{{#!td style="vertical-align:top"
C*7
}}}
{{{#!td style="vertical-align:top"
'' 'two-way' ''
}}}
{{{#!td
Type of nesting mode.\\\\ 
''one-way'', ''two-way'', and 'vertical' nesting are allowed. The latter implies of a one-dimensional nesting in the vertical direction only (i.e. all domains have the the same horizontal extent).
}}}