Changes between Version 385 and Version 386 of doc/app/initialization_parameters

Timestamp:

May 23, 2018 10:10:33 AM (7 years ago)

Author:

Giersch

Comment:

--

doc/app/initialization_parameters

@@ -2226 +2226 @@
 '' 'cyclic_fill' ''\\\\
       Here, 3d-data from a precursor run are read by the initial (main) run. The precursor run is allowed to have a smaller domain along x and y compared with the main run. Also, different numbers of processors can be used for these two runs. Limitations are that the precursor run must use cyclic horizontal boundary conditions and that the number of vertical grid points, [#nz nz], must be same for the precursor run and the main run. If the total domain of the main run is larger than that of the precursor run, the domain is filled by cyclic repetition of the (cyclic) precursor data. This initialization method is required if a turbulent inflow is used (see [#turbulent_inflow turbulent_inflow]). 3d-data must be made available to the run by activating an appropriate file connection statement for local file [../iofiles#BININ BININ]. The usage of a turbulent inflow is explained [../examples/turbinf here]. \\ Note that in case of [#reference_state reference_state]='' 'initial_profile','' the main run uses the initial profile of the precursor run. \\\\
-Values may be combined, e.g. '''initializing_actions''' = '' 'set_constant_profiles initialize_vortex' '', but the values of '' 'set_constant_profiles' '', '' 'set_1d-model_profiles' '' , and '' 'by_user' '' must not be given at the same time.
+'' 'inifor' ''\\\\
+      Initialization with provided input data derived from larger-scale model (COSMO data). \\\\
+Values may be combined, e.g. '''initializing_actions''' = '' 'set_constant_profiles initialize_vortex' '', but the values of '' 'set_constant_profiles' '', '' 'set_1d-model_profiles' '' , '' 'cyclic_fill' '', '' 'read_restart_data' '', '' 'inifor' '' and '' 'by_user' '' must not be given at the same time.
 }}}
 |----------------