Changes between Version 224 and Version 225 of doc/app/initialization_parameters

Timestamp:

Nov 7, 2013 11:43:46 AM (11 years ago)

Author:

fricke

Comment:

--

doc/app/initialization_parameters

@@ -429 +429 @@
      In ocean runs, potential density is used instead of temperature (calculated from the initial potential temperature and salinity profile, see [#sa_surface sa_surface] and [#sa_vertical_gradient sa_vertical_gradient] for how to set the initial salinity profile).
 
-     In case of [#initializing_actions initializing_actions]= '' 'cyclic_fill' '', the main run uses the initial profile of the precursor run.
+     In case of [#initializing_actions initializing_actions]= '' 'cyclic_fill,' '' the main run uses the initial profile of the precursor run.
 
 '' 'horizontal_average' ''\\
@@ -1961 +1961 @@
       A 2d-Gauss-like shape disturbance (x,y) is added to the initial temperature field with radius 10.0 * [#dx dx] and center at jc = ([#nx nx]+1)/2. This may be used for tests of scalar advection schemes (see [#scalar_advec scalar_advec]). Such tests require a horizontal wind profile constant with hight and diffusion switched off (see '' 'initialize_vortex' ''). Additionally, the buoyancy term must be switched of in the equation of motion  for w (this requires the user to comment out the call of buoyancy in the source code of {{{prognostic_equations.f90}}}).\\\\
 '' '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. \\\\
+      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.
 }}}