Changes between Version 279 and Version 280 of doc/app/runtime_parameters

Timestamp:

Aug 28, 2017 1:08:10 PM (8 years ago)

Author:

kanani

Comment:

--

doc/app/runtime_parameters

@@ -514 +514 @@
 }}}
 {{{#!td
-Temporal interval at which time series data shall be output (in s).\\\\ 
-The 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).\\\\
+Temporal interval at which time series data shall be output (in s).\\\\
 The default value of '''dt_dots''' is calculated as follows:\\\\
 {{{
@@ -524 +523 @@
 ENDIF
 }}}
-(which minimizes the number of calls of routine {{{flow_statistics}}}).\\\\
-By default time series data is output to the local file [[../iofiles#DATA_1D_TS_NETCDF|DATA_1D_TS_NETCDF]]. Because of the default settings of '''dt_dots''', it will generally be created for each model run. The file's format is netCDF.  Further details about processing netCDF data are given in chapter [../netcdf netCDF data output].\\\\
-The file contains the following time series quantities (the first column gives the name of the quantities as used in the netCDF file):\\\\
+minimizing the number of calls of routine {{{flow_statistics}}}.\\\\
+The 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]). If '''dt_dots''' < time step [#dt dt], then data of the time series are written after each time step. This can be forced by setting '''dt_dots''' = 0.\\\\
+Time series data are output to the local file [[../iofiles#DATA_1D_TS_NETCDF|DATA_1D_TS_NETCDF]], which is generally created for each model run due to the default settings of '''dt_dots'''. The file's format is NetCDF.  Further details about processing of NetCDF data are given in chapter [../netcdf NetCDF data output].\\\\
+The file contains the following time-series quantities (the first column gives the name of the quantities as used in the NetCDF file), all of which are automatically output without having to be prescribed by the user, since the size of the time-series file is rather small:\\\\
 ||='''Quantity name''' =||='''Meaning''' =||='''Unit''' =||
 ||E ||Total kinetic energy of the flow, E = 0.5 * (u^2^+v^2^+w^2^), (3D domain average) ||m^2^/s^2^ ||
@@ -581 +581 @@
 ||rrtm_asdir ||albedo for direct shortwave radiation (horizontal average) ||0-1 ||
 \\\\
-Additionally, the user can add his own time series quantities to the file, by using the user-interface subroutines [[../userint/int#user_init|user_init.f90]] and [[../userint/int#user_statistics|user_statistics.f90]] These routines contain (as comment lines) a simple example how to do this.\\\\
-Time series data refers to the total domain, but time series for subdomains can also be output (see [../inipar/#statistic_regions statistic_regions]). However, the following time series always present the values of the total model domain (even with output for subdomains): ''umax, vmax, wmax, div_old, div_new.''
+Additionally, the user can add own time series quantities to the file by using the user-interface subroutines [[../userint/int#user_init|user_init.f90]] and [[../userint/int#user_statistics|user_statistics.f90]]. These routines contain a simple example (as comment lines) on how to do this.\\\\
+By default, time-series data refer to the total domain, but data can also be output for user-defined subdomains (see [../inipar/#statistic_regions statistic_regions]). However, the following time series always present the values of the total model domain (even with output for subdomains): ''umax, vmax, wmax, div_old, div_new.''
 }}}
 |----------------