| | 353 | [=#dt_data_output_av '''dt_data_output_av'''] |
| | 354 | }}} |
| | 355 | {{{#!td style="vertical-align:top" |
| | 356 | R |
| | 357 | }}} |
| | 358 | {{{#!td style="vertical-align:top" |
| | 359 | value of [#dt_data_output dt_data_output] |
| | 360 | }}} |
| | 361 | {{{#!td |
| | 362 | Temporal interval at which time averaged 3d volume data and/or 2d cross section data shall be output (in s).\\\\ |
| | 363 | If data output of time averaged 2d and 3d data 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 they shall be output. Output can be skipped at the beginning of a simulation using parameter [#skip_time_data_output_av skip_time_data_output_av], which has zero value by default. Reference time is the beginning of the simulation, i.e. output takes place at times t = '''skip_time_data_output_av''' + '''dt_data_output_av''', '''skip_time_data_output_av''' + 2*'''dt_data_output_av''', '''skip_time_data_output_av''' + 3*'''dt_data_output_av''', etc. Since output is only done at the discrete time levels given by the timestep used, the actual output times can slightly deviate from these theoretical values.\\\\ |
| | 364 | The length of the averaging interval is controlled via parameter [#averaging_interval averaging_interval]. |
| | 365 | }}} |
| | 366 | |---------------- |
| | 367 | {{{#!td style="vertical-align:top" |
| | 368 | [=#dt_dopr '''dt_dopr'''] |
| | 369 | }}} |
| | 370 | {{{#!td style="vertical-align:top" |
| | 371 | R |
| | 372 | }}} |
| | 373 | {{{#!td style="vertical-align:top" |
| | 374 | value of [#dt_data_output dt_data_output] |
| | 375 | }}} |
| | 376 | {{{#!td |
| | 377 | Temporal interval at which data of vertical profiles shall be output (to local file DATA_1D_PR_NETCDF) (in s).\\\\ |
| | 378 | If output of horizontally averaged vertical profiles is switched on (see [#data_output_pr data_output_pr]), this parameter can be used to assign the temporal interval at which profile data shall be output. Output can be skipped at the beginning of a simulation using parameter [#skip_time_dopr skip_time_dopr], which has zero value by default. Reference time is the beginning of the simulation, thus t = 0, i.e. output takes place at times t = '''skip_time_dopr''' + '''dt_dopr''', '''skip_time_dopr''' + 2*'''dt_dopr''', '''skip_time_dopr''' + 3*'''dt_dopr''', etc. Since profiles can not be calculated for times lying within a time step interval, the output times can deviate from these theoretical values. If a time step ranges from t = 1799.8 to t = 1800.2, then in the example above the output would take place at t = 1800.2. In general, the output always lie between t = 1800.0 and t = 1800.0 + [#dt dt]. If the model uses a variable time step, these deviations from the theoretical output times will of course be different for each output time.\\\\ |
| | 379 | In order to guarantee an output of profile data at the end of a simulation (see [#end_time end_time]) in any way, '''end_time''' should be equal or a little bit larger than the respective theoretical output time. For example, if '''dt_dopr''' = ''900.0'' and ''3600.0'' seconds are to be simulated, then '''end_time''' >= ''3600.0'' should be chosen.\\\\ |
| | 380 | A selection of profiles to be output can be done via parameter [#data_output_pr data_output_pr]. |
| | 381 | }}} |
| | 382 | |---------------- |
| | 383 | {{{#!td style="vertical-align:top" |
| | 384 | [=#dt_dopr_listing '''dt_dopr_listing'''] |
| | 385 | }}} |
| | 386 | {{{#!td style="vertical-align:top" |
| | 387 | R |
| | 388 | }}} |
| | 389 | {{{#!td style="vertical-align:top" |
| | 390 | 9999999.9 |
| | 391 | }}} |
| | 392 | {{{#!td |
| | 393 | Temporal interval at which data of vertical profiles shall be output (output for printouts, local file [[../iofiles#LIST_PROFIL|LIST_PROFIL)]] (in s).\\\\ |
| | 394 | This parameter can be used to assign the temporal interval at which profile data shall be output. Reference time is the beginning of the simulation, thus t = 0. For example if '''dt_dopr_listing''' = ''1800.0'', then output takes place at t = 1800.0, 3600.0, 5400.0, etc. Since profiles can not be calculated for times lying within a time step interval, the output times can deviate from these theoretical values. If a time step ranges from t = 1799.8 to t = 1800.2, then in the example above the output would take place at t = 1800.2. In general, the output always lie between t = 1800.0 and t = 1800.0 + [#dt dt] (numbers are related to the example above). If the model uses a variable time step, these deviations from the theoretical output times will of course be different for each output time.\\\\ |
| | 395 | In order to guarantee an output of profile data at the end of a simulation (see [#end_time end_time]) in any way, end_time should be a little bit larger than the respective theoretical output time. For example, if '''dt_dopr_listing''' = ''900.0'' and ''3600.0'' seconds are to be simulated, then it should be at least '''end_time''' > ''3600.0 + [#dt dt]''. If variable time steps are used (which is the default), '''dt''' should be properly estimated.\\\\ |
| | 396 | Data and output format of the file [[../iofiles#LIST_PROFIL|LIST_PROFIL)]] is internally fixed. In this file the profiles of the most important model variables are arranged in adjacent columns. |
| | 397 | }}} |
| | 398 | |---------------- |
| | 399 | {{{#!td style="vertical-align:top" |
