Changes between Version 70 and Version 71 of doc/app/runtime_parameters
- Timestamp:
- Sep 14, 2010 9:49:02 AM (15 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/app/runtime_parameters
v70 v71 85 85 Multiple quantities can be assigned, e.g. '''data_output''' = '' 'e', 'u', 'w' ''.\\\\ 86 86 By assigning the pure strings from the above table, 3d volume data is output. Cross section data can be output by appending the string '_xy', '_xz', or '_yz' to the respective quantities. Time averaged output is created by appending the string '_av' (for cross section data, this string must be appended after the cross section string). Cross section data can also be (additionally) averaged along the direction normal to the respective section (see below). Assignments of quantities can be given in arbitrary order:\\\\ 87 Example: \\\\88 '''data_output''' = '' 'u', 'pt_xz_av', 'w_xy', 'u_av' ''. \\\\87 Example: 88 '''data_output''' = '' 'u', 'pt_xz_av', 'w_xy', 'u_av' ''. 89 89 This example will create the following output: instantaneous 3d volume data of u-velocity component (by default on file [[../iofiles#DATA_3D_NETCDF|DATA_3D_NETCDF]]), temporally averaged 3d volume data of u-velocity component (by default on file [[../iofiles#DATA_3D_AV_NETCDF|DATA_3D_AV_NETCDF]]), instantaneous horizontal cross section data of w-velocity component (by default on file [[../iofiles#DATA_2D_XY_NETCDF|DATA_2D_XY_NETCDF]]), and temporally averaged vertical cross section data of potential temperature (by default on file [[../iofiles#DATA_2D_XZ_AV_NETCDF|DATA_2D_XZ_AV_NETCDF]]).\\\\ 90 90 The user is allowed to extend the above list of quantities by defining his own output quantities (see the user-parameter [[../userpar#data_output_user|data_output_user]]).\\\\ … … 122 122 Other netCDF formats (classic, netCDF4/HDF5) can be selected with parameter [#netcdf_data_format netcdf_data_format].\\\\ 123 123 For historical reasons, other data formats are still available. Beside 'netcdf', data_output_format may be assigned the following values:\\\\ 124 '' 'avs' '' 124 '' 'avs' '' 125 125 output of 3d volume data in FORTRAN binary format to be read by the graphic software '''AVS''' (see chapter [[4.5.5]])\\\\ 126 126 Multiple values can be assigned to '''data_output_format''', i.e. if the user wants to have both the "old" data format as well as cross section data in NetCDF format, then '''data_output_format''' = '' 'avs', 'netcdf' '' has to be assigned.\\\\ … … 203 203 ||[[span(hyp ,style=color: blue)]] ||Hydrostatic pressure ||dbar || 204 204 \\\\ 205 Beyond that, initial profiles (t=0) of some variables can additionally be output (this output is only done once with the first plot output and not repeated with the profile output at later times). The names of these profiles result from the ones specified above leaded by a hash "#". Allowed values are: \\\\206 #u, #v, #pt, #km, #kh, #l, #lpt, #q, #qv, #s, #sa, #vpt \\\\205 Beyond that, initial profiles (t=0) of some variables can additionally be output (this output is only done once with the first plot output and not repeated with the profile output at later times). The names of these profiles result from the ones specified above leaded by a hash "#". Allowed values are: 206 #u, #v, #pt, #km, #kh, #l, #lpt, #q, #qv, #s, #sa, #vpt 207 207 Profile names preceded by a hash automatically imply that profiles for these variables are also output at later times. It is not necessary and not allowed to specify the same profile name with and without hash simultaneously(this would lead to an netCDF error).\\\\ 208 208 These initial profiles have been either set by the user or have been calculated by a 1d-model prerun.\\\\ … … 224 224 Alternatively, by assigning '''data_output_2d_on_each_pe''' = ''.F.'', the respective data is gathered on PE0 and output is done directly into one file, so {{{combine_plot_fields.x}}} does not have to be called. However, in case of very large numbers of horizontal gridpoints, sufficient memory is required on PE0. 225 225 }}} 226 |---------------- 227 {{{#!td style="vertical-align:top" 228 [=#dummy '''dummy'''] 229 }}} 230 {{{#!td style="vertical-align:top" 231 dummy 232 }}} 233 {{{#!td style="vertical-align:top" 234 dummy 235 }}} 236 {{{#!td 237 dummy 238 }}} 239 |---------------- 226 240 {{{#!td style="vertical-align:top" 227 241 [=#dummy '''dummy'''] … … 305 319 |---------------- 306 320 {{{#!td style="vertical-align:top" 321 [=#disturbance_amplitude '''disturbance_amplitude'''] 322 }}} 323 {{{#!td style="vertical-align:top" 324 R 325 }}} 326 {{{#!td style="vertical-align:top" 327 0.25 328 }}} 329 {{{#!td 330 Maximum perturbation amplitude of the random perturbations imposed to the horizontal velocity field (in m/s).\\\\ 331 The parameter [#create_disturbances create_disturbances] describes how to impose random perturbations to the horizontal velocity field. Since the perturbation procedure includes two filter operations, the amplitude assigned by '''disturbance_amplitude''' is only an approximate value of the real magnitude of the perturbation. 332 }}} 333 |---------------- 334 {{{#!td style="vertical-align:top" 335 [=#disturbance_energy_limit '''disturbance_energy_limit'''] 336 }}} 337 {{{#!td style="vertical-align:top" 338 R 339 }}} 340 {{{#!td style="vertical-align:top" 341 0.01 342 }}} 343 {{{#!td 344 Upper limit value of the perturbation energy of the velocity field used as a criterion for imposing random perturbations (in m^2^/s^2^).\\\\ 345 The parameter [#create_disturbances create_disturbances] describes how to impose random perturbations to the horizontal velocity field. The perturbation energy is defined as the volume average (over the total model domain) of the squares of the deviations of the velocity components from the mean flow (horizontal average). If the perturbation energy exceeds the assigned value, random perturbations to the fields of horizontal velocities are imposed no more. The value of this parameter usually must be determined by trial and error (it depends e.g. on the total number of grid points). 346 }}} 347 |---------------- 348 {{{#!td style="vertical-align:top" 307 349 [=#dummy '''dummy'''] 308 350 }}} … … 316 358 dummy 317 359 }}} 360 |---------------- 361 {{{#!td style="vertical-align:top" 362 [=#dummy '''dummy'''] 363 }}} 364 {{{#!td style="vertical-align:top" 365 dummy 366 }}} 367 {{{#!td style="vertical-align:top" 368 dummy 369 }}} 370 {{{#!td 371 dummy 372 }}}