Changes between Version 16 and Version 17 of doc/app/initialization_parameters

Timestamp:

Sep 13, 2010 9:44:58 AM (14 years ago)

Author:

kanani

Comment:

--

doc/app/initialization_parameters

@@ -189 +189 @@
 |----------------
 {{{#!td style="vertical-align:top; text-align:left;width: 150px"
-[=#averaging_interval '''averaging_interval''']
-}}}
-{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
-R
-}}}
-{{{#!td style="vertical-align:top; text-align:left;style="width: 100px"
-0.0
-}}}
-{{{#!td
-Averaging interval for all output of temporally averaged data (in s).\\\\
-This parameter defines the time interval length for temporally averaged data (vertical profiles, spectra, 2d cross-sections, 3d volume data). By default, data are not subject to temporal averaging. The interval length is limited by the parameter
-[[#dt_data_output_av dt_data_output_av]]. In any case, '''averaging_interval <= dt_data_output_av''' must hold.\\\\
-If an interval is defined, then by default the average is calculated from the data values of all timesteps lying within this interval. The number of time levels entering into the average can be reduced with the parameter [#dt_averaging_input dt_averaging_input].\\\\
-If an averaging interval can not be completed at the end of a run, it will be finished at the beginning of the next restart run. Thus for restart runs, averaging intervals do not necessarily begin at the beginning of the run.\\\\
-Parameters [#averaging_interval_pr averaging_interval_pr] and [#averaging_interval_sp averaging_interval_sp] can be used to define different averaging intervals for vertical profile data and spectra, respectively.
+[=#topography '''topography''']
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
+C*40
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 100px"
+'' 'flat' ''
+}}}
+{{{#!td
+Topography mode.\\\\
+The user can choose between the following modes:\\\\
+'' 'flat' ''\\\\
+  Flat surface.\\\\
+'' 'single_building' ''\\\\
+  Flow around a single rectangular building mounted on a flat surface.
+  The building size and location can be specified by the parameters building_height, building_length_x, building_length_y, building_wall_left and    building_wall_south.
+
+'single_street_canyon'
+Flow over a single, quasi-2D street canyon of infinite length oriented either in x- or in y-direction.
+The canyon size, orientation and location can be specified by the parameters canyon_height plus either canyon_width_x and canyon_wall_left or  canyon_width_y and canyon_wall_south.
+ 
+
+'read_from_file'
+Flow around arbitrary topography.
+This mode requires the input file TOPOGRAPHY_DATA. This file contains the arbitrary topography height information in m. These data must exactly match the horizontal grid.
+
+Alternatively, the user may add code to the user interface subroutine user_init_grid to allow further topography modes. These require to explicitly set the topography_grid_convention to either 'cell_edge' or 'cell_center'.
+
+Non-flat topography modes may assign a kinematic sensible wall_heatflux and a kinematic wall_humidityflux (requires humidity = .T.) or a wall_scalarflux (requires passive_scalar = .T.) at the five topography faces.
+
+All non-flat topography modes require the use of momentum_advec = scalar_advec = 'pw-scheme', psolver /= 'sor',  alpha_surface = 0.0, galilei_transformation = .F., cloud_physics  = .F.,  cloud_droplets = .F., and prandtl_layer = .T..
+
+Note that an inclined model domain requires the use of topography = 'flat' and a nonzero alpha_surface.
 }}}
 |----------------