Changes between Version 141 and Version 142 of doc/app/initialization_parameters


Ignore:
Timestamp:
Jan 3, 2011 8:48:24 AM (14 years ago)
Author:
heinze
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/initialization_parameters

    v141 v142  
    767767      The upstream-spline scheme is used (see Mahrer and Pielke, 1978: Mon. Wea. Rev., 106, 818-830). In opposite to the Piascek-Williams scheme, this is characterized by much better numerical features (less numerical diffusion, better preservation of flow structures, e.g. vortices), but computationally it is much more expensive. In addition, the use of the Euler-timestep scheme is mandatory ([#timestep_scheme timestep_scheme] = '' 'euler' ''), i.e. the timestep accuracy is only of first order. For this reason the advection of scalar variables (see [#scalar_advec scalar_advec]) should then also be carried out with the upstream-spline scheme, because otherwise the scalar variables would be subject to large numerical diffusion due to the upstream scheme.\\\\
    768768Since the cubic splines used tend to overshoot under certain circumstances, this effect must be adjusted by suitable filtering and smoothing (see [#long_filter_factor long_filter_factor]). This is always neccessary for runs with stable stratification, even if this stratification appears only in parts of the model domain.\\\\
    769 With stable stratification the upstream-spline scheme also produces gravity waves with large amplitude, which must be suitably damped (see [../d3par#rayleigh_damping_factor rayleigh_damping_factor]).\\\\
     769With stable stratification the upstream-spline scheme also produces gravity waves with large amplitude, which must be suitably damped (see [../inipar#rayleigh_damping_factor rayleigh_damping_factor]).\\\\
    770770'''Important:'''\\
    771771The  upstream-spline scheme is not implemented for humidity and passive scalars (see [#humidity humidity] and [#passive_scalar passive_scalar]) and requires the use of a 2d-domain-decomposition. The last conditions severely restricts code optimization on several machines leading to very long execution times! The scheme is also not allowed for non-cyclic lateral boundary conditions (see [#bc_lr bc_lr] and [#bc_ns bc_ns]).