Changes between Version 74 and Version 75 of doc/app/runtime_parameters


Ignore:
Timestamp:
Sep 14, 2010 11:13:15 AM (15 years ago)
Author:
weinreis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/runtime_parameters

    v74 v75  
    287287|----------------
    288288{{{#!td style="vertical-align:top"
     289[=#dt '''dt''']
     290}}}
     291{{{#!td style="vertical-align:top"
     292R
     293}}}
     294{{{#!td style="vertical-align:top"
     295variable
     296}}}
     297{{{#!td
     298Time step to be used by the 3d-model (in s).\\\\
     299This parameter is described in detail with the initialization parameters (see [[../inipar#dt|dt]]). Additionally, it may be used as a run parameter and then applies to all restart runs (until it is changed again). A switch from a constant time step to a variable time step can be achieved with '''dt''' = ''-1.0.''
     300}}}
     301|----------------
     302{{{#!td style="vertical-align:top"
     303[=#dt_averaging_input '''dt_averaging_input''']
     304}}}
     305{{{#!td style="vertical-align:top"
     306R
     307}}}
     308{{{#!td style="vertical-align:top"
     3090.0
     310}}}
     311{{{#!td
     312Temporal interval of data which are subject to temporal averaging (in s).\\\\
     313By 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.\\\\
     314With 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''').\\\\
     315'''Example:'''
     316  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
     317  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.
     318It 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.\\\\
     319Parameter [#dt_averaging_input_pr dt_averaging_input_pr] can be used to define a different temporal interval for vertical profile data and spectra.
     320}}}
     321|----------------
     322{{{#!td style="vertical-align:top"
     323[=#dummy '''dummy''']
     324}}}
     325{{{#!td style="vertical-align:top"
     326dummy
     327}}}
     328{{{#!td style="vertical-align:top"
     329dummy
     330}}}
     331{{{#!td
     332dummy
     333}}}
     334|----------------
     335{{{#!td style="vertical-align:top"
     336[=#dummy '''dummy''']
     337}}}
     338{{{#!td style="vertical-align:top"
     339dummy
     340}}}
     341{{{#!td style="vertical-align:top"
     342dummy
     343}}}
     344{{{#!td
     345dummy
     346}}}
     347|----------------
     348{{{#!td style="vertical-align:top"
    289349[=#dummy '''dummy''']
    290350}}}