Changes between Version 36 and Version 37 of doc/tec/nesting

Timestamp:

Apr 8, 2019 7:59:16 AM (6 years ago)

Author:

hellstea

Comment:

--

doc/tec/nesting

@@ -15 +15 @@
 The child domain obtains boundary data of the three velocity components and all prognostic scalar variables from the parent domain, where the boundary data is interpolated from the coarse parent grid onto the fine child grid. 
 The other way around, the updated child solution after the timestep is transferred back onto the parent grid by anterpolation. 
-The self-nesting can be operated as a 1-way nesting, where only the anterpolation step is omitted, i.e. there is no feedback in the parent by the child model, and as a 2-way nesting, where parent and child solution mutually depend on each other. 
+The self-nesting can be operated as a 1-way nesting, where the anterpolation step is omitted, i.e. there is no feedback in the parent by the child model, and as a 2-way nesting, where parent and child solution mutually depend on each other. 
 
 Child domains can be recursively nested within each other under the condition that the child domain fits completely into its respective parent domain. Child domains can also be parallel to each other sharing the same parent domain, but the parallel child domains must not overlap each other. Recursive and parallel children may co-exist in the same run. Please note also that the outer boundaries of a nested child domain must match the underlying parent-grid lines in all directions. Morever, inside the child domain, all the parent-grid lines must match the corresponding child-grid lines. Therefore, also the grid-spacing ratios in each coordinate direction must be integer valued. This also implies that vertical grid stretching is not allowed in nested runs except in the root domain above the top level of the highest nested domain. The domain decomposition (pe grid) of all children must be such that the subdomain size is never smaller than the parent grid-spacing in the respective direction.