Home

Context Navigation

runtime_parameters

Timestamp:: Sep 16, 2010 5:36:53 PM (15 years ago)
Author:: weinreis
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/runtime_parameters

-                      v188
+                      v189
 Temporal interval of data which are subject to temporal averaging (in s).\\\\
 By default, data from each timestep within the interval defined by [#averaging_interval averaging_interval] are used for calculating the temporal average. By choosing '''dt_averaging_input''' > ''dt'', the number of time levels entering the average can be minimized. This reduces the CPU-time of a run but may worsen the quality of the average's statistics.\\\\
 With variable time step (see [#dt dt]), the number of time levels entering the average can vary from one averaging interval to the next (for a more detailed explanation see [#averaging_interval averaging_interval]). It is approximately given by the quotient of '''averaging_interval''' / MAX(''' dt_averaging_input''', '''dt''') (which gives a more or less exact value if a fixed timestep is used and if this is an integral divisor of '''dt_averaging_input''').\\\\
+With variable time step (see [#dt dt]), the number of time levels entering the average can vary from one averaging interval to the next (for a more detailed explanation see [#averaging_interval averaging_interval]). It is approximately given by the quotient of '''averaging_interval''' / MAX(''' dt_averaging_input''', '''dt''') (which gives a more or less exact value, if a fixed timestep is used and if this is an integral divisor of '''dt_averaging_input''').\\\\
 '''Example:'''
   With an averaging interval of 100.0 s and '''dt_averaging_input''' = ''10.0,'' the time levels entering the average have a (minimum) distance of 10.0 s (their distance may
   of course be larger if the current timestep is larger than 10.0 s), so the average is calculated from the data of (maximum) 10 time levels.
+  of course be larger, if the current timestep is larger than 10.0 s), so the average is calculated from the data of (maximum) 10 time levels.
 It is allowed to change '''dt_averaging_input''' during a job chain. If the last averaging interval of the run previous to the change could not be completed (i.e. has to be finished in the current run), the individual profiles and/or spectra entering the averaging are not uniformly distributed over the averaging interval.\\\\
 Parameter [#dt_averaging_input_pr dt_averaging_input_pr] can be used to define a different temporal interval for vertical profile data and spectra.
 …
 ENDIF
 }}}
 This parameter can be used to assign the temporal interval at which data points shall be output. Reference time is the beginning of  the simulation, i.e. output takes place at times t = '''dt_dots''', 2*'''dt_dots''', 3*'''dt_dots''', etc. The actual output times can deviate from these theoretical values (see [#dt_dopr dt_dopr]). Is '''dt_dots''' < [#dt dt], then data of the time series are written after each time step (if this is requested it should be '''dt_dots''' = 0).\\\\
+This parameter can be used to assign the temporal interval at which data points shall be output. Reference time is the beginning of  the simulation, i.e. output takes place at times t = '''dt_dots''', 2*'''dt_dots''', 3*'''dt_dots''', etc. The actual output times can deviate from these theoretical values (see [#dt_dopr dt_dopr]). Is '''dt_dots''' < [#dt dt], then data of the time series are written after each time step (if this is requested, it should be '''dt_dots''' = 0).\\\\
 The default value of '''dt_dots''' is calculated as follows:\\\\
 {{{
 …
 Temporal interval at which horizontal cross section data shall be output (in s).\\\\
 If output of horizontal cross sections is switched on (see [#data_output data_output] and [#section_xy section_xy]), this parameter can be used to assign the temporal interval at which cross section data shall be output. Output can be skipped at the beginning of a simulation using parameter [#skip_time_do2d_xy skip_time_do2d_xy], which has zero value by default. Reference time is the beginning of the simulation, i.e. output takes place at times t = '''skip_time_do2d_xy''' + '''dt_do2d_xy''', '''skip_time_do2d_xy''' + 2*'''dt_do2d_xy''', '''skip_time_do2d_xy''' + 3*'''dt_do2d_xy''', etc. The actual output times can deviate from these theoretical values (see [#dt_dopr dt_dopr]).\\\\
 Parameter [#do2d_at_begin do2d_at_begin] has to be used if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
+Parameter [#do2d_at_begin do2d_at_begin] has to be used, if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
 }}}
 |----------------
 …
 Temporal interval at which vertical cross sections data (xz) shall be output (in s).\\\\
 If output of horizontal cross sections is switched on (see [#data_output data_output] and [#section_xz section_xz]), this parameter can be used to assign the temporal interval at which cross section data shall be output. Output can be skipped at the beginning of a simulation using parameter [#skip_time_do2d_xz skip_time_do2d_xz], which has zero value by default. Reference time is the beginning of the simulation, i.e. output takes place at times t = '''skip_time_do2d_xz''' + '''dt_do2d_xz''', '''skip_time_do2d_xz''' + 2*'''dt_do2d_xz''', '''skip_time_do2d_xz''' + 3*'''dt_do2d_xz''', etc. The actual output times can deviate from these theoretical values (see [#dt_dopr dt_dopr]).\\\\
 Parameter [#do2d_at_begin do2d_at_begin] has to be used if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
+Parameter [#do2d_at_begin do2d_at_begin] has to be used, if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
 }}}
 |----------------
 …
 Temporal interval at which vertical cross section data (yz) shall be output (in s).\\\\
 If output of horizontal cross sections is switched on (see [#data_output data_output] and [#section_yz section_yz]), this parameter can be used to assign the temporal interval at which cross section data shall be output. Output can be skipped at the beginning of a simulation using parameter [#skip_time_do2d_yz skip_time_do2d_yz], which has zero value by default. Reference time is the beginning of the simulation, i.e. output takes place at times t = '''skip_time_do2d_yz''' + '''dt_do2d_yz''', '''skip_time_do2d_yz''' + 2*'''dt_do2d_yz''', '''skip_time_do2d_yz''' + 3*'''dt_do2d_yz''', etc. The actual output times can deviate from these theoretical values (see [#dt_dopr dt_dopr]).\\\\
 Parameter [#do2d_at_begin do2d_at_begin] has to be used if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
+Parameter [#do2d_at_begin do2d_at_begin] has to be used, if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
 }}}
 |----------------
 …
 Temporal interval at which 3d volume data shall be output (in s).\\\\
 If output of 3d-volume data is switched on (see [#data_output data_output]), this parameter can be used to assign the temporal interval at which 3d-data shall be output. Output can be skipped at the beginning of a simulation using parameter [#skip_time_do3d skip_time_do3d], which has zero value by default. Reference time is the beginning of the simulation, i.e. output takes place at times t = '''skip_time_do3d''' + '''dt_do3d''', '''skip_time_do3d''' + 2*'''dt_do3d''', '''skip_time_do3d''' + 3*'''dt_do3d''', etc. The actual output times can deviate from these theoretical values (see [#dt_dopr dt_dopr]).\\\\
 Parameter [#do3d_at_begin do3d_at_begin] has to be used if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
+Parameter [#do3d_at_begin do3d_at_begin] has to be used, if an additional output is wanted at the start of a run (thus at the time t = 0 or at the respective starting times of restart runs).
 }}}
 |----------------
 …
    '''mask_x (2,:)''' = ''1000.''\\\\
    This example will create outputs at the specified points (in m, if [#mask_scale_x mask_scale_x] is not used) of the model domain.
 If you use [#mask_scale_x mask_scale_x] '''mask_x''' has to be assigned in "grid point position along x-direction [m]/'''mask_scale_x''' " (e.g. '''mask_scale_x''' = ''10.0'' -> '''mask_x (1,:)''' = ''0., 5., 10., 50., 55., 60.'').\\\\
+If you use [#mask_scale_x mask_scale_x], '''mask_x''' has to be assigned in "grid point position along x-direction [m]/'''mask_scale_x''' " (e.g. '''mask_scale_x''' = ''10.0'' -> '''mask_x (1,:)''' = ''0., 5., 10., 50., 55., 60.'').\\\\
 The default results in output at every grid point along the x-direction, i.e. from 0 to nx.\\\\
 If you want to output quantities at positions with constant spaces (e.g. every 100m), use the parameter [#mask_x_loop mask_x_loop].\\\\
 …
    '''mask_y (2,:)''' = ''1000.''\\\\
    This example will create outputs at the specified points (in m, if [#mask_scale_y mask_scale_y] is not used) of the model domain.
 If you use [#mask_scale_y mask_scale_y] '''mask_y''' has to be assigned in "grid point position along y-direction [m]/'''mask_scale_y''' " (e.g. '''mask_scale_y''' = ''10.0'' -> '''mask_y (1,:)''' = ''0., 5., 10., 50., 55., 60.'').\\\\
+If you use [#mask_scale_y mask_scale_y], '''mask_y''' has to be assigned in "grid point position along y-direction [m]/'''mask_scale_y''' " (e.g. '''mask_scale_y''' = ''10.0'' -> '''mask_y (1,:)''' = ''0., 5., 10., 50., 55., 60.'').\\\\
 The default results in output at every grid point along the y-direction, i.e. from 0 to ny.\\\\
 If you want to output quantities at positions with constant spaces (e.g. every 100m), use the parameter [#mask_y_loop mask_y_loop].\\\\
 …
    '''mask_z (2,:)''' = ''1000.''\\\\
    This example will create outputs at the specified points (in m, if [#mask_scale_z mask_scale_z] is not used) of the model domain.
 If you use [#mask_scale_z mask_scale_z] '''mask_z''' has to be assigned in "grid point position along z-direction [m]/'''mask_scale_z''' " (e.g. '''mask_scale_z''' = ''10.0'' -> '''mask_z (1,:)''' = ''0., 5., 10., 50., 55., 60.'').\\\\
+If you use [#mask_scale_z mask_scale_z], '''mask_z''' has to be assigned in "grid point position along z-direction [m]/'''mask_scale_z''' " (e.g. '''mask_scale_z''' = ''10.0'' -> '''mask_z (1,:)''' = ''0., 5., 10., 50., 55., 60.'').\\\\
 The default results in output at every grid point along the z-direction, i.e. from 0 to nz.\\\\
 If you want to output quantities at positions with constant spaces (e.g. every 100m), use the parameter [#mask_z_loop mask_z_loop].\\\\
 …
 For each mask a separate '''mask_z_loop''' has to be assigned.\\\\
 The default results in output at every grid point along the z-direction, i.e. from 0 to nz.\\\\
 '''Note:''' If mask_z is also specified, mask_z_loop will be ignored. If you have assigned [../inipar#dz_stretch_level dz_stretch_level], '''mask_z_loop''' will fail above '''dz_stretch_level'''. If masked outputs are desired above '''dz_stretch_level''' you should use [#mask_z mask_z] instead.\\\\
+'''Note:''' If mask_z is also specified, mask_z_loop will be ignored. If you have assigned [../inipar#dz_stretch_level dz_stretch_level], '''mask_z_loop''' will fail above '''dz_stretch_level'''. If masked outputs are desired above '''dz_stretch_level''', you should use [#mask_z mask_z] instead.\\\\
 Further examples are given in [../maskedoutput#Examples Masked data output].
 }}}