Changes between Version 114 and Version 115 of doc/app/runtime_parameters

Timestamp:

Sep 15, 2010 9:14:58 AM (15 years ago)

Author:

weinreis

Comment:

--

doc/app/runtime_parameters

@@ -777 +777 @@
 {{{#!td
 Number of additional user-defined subdomains for which statistical analysis and corresponding output (profiles, time series) shall be made.\\\\
-By default, vertical profiles and other statistical quantities are calculated as horizontal and/or volume average of the total model domain. Beyond that, these calculations can also be carried out for subdomains which can be defined using the field '''rmask''' within the user-defined software (see [[chapter 3.5.3]]). The number of these subdomains is determined with the parameter '''statistic_regions'''. Maximum 9 additional subdomains are allowed. The parameter [[../userpar#region|region] can be used to assigned names (identifier) to these subdomains which are then used in the headers of the output files and plots.\\\\
+By default, vertical profiles and other statistical quantities are calculated as horizontal and/or volume average of the total model domain. Beyond that, these calculations can also be carried out for subdomains which can be defined using the field '''rmask''' within the user-defined software (see [[chapter 3.5.3]]). The number of these subdomains is determined with the parameter '''statistic_regions'''. Maximum 9 additional subdomains are allowed. The parameter [[../userpar#region|region]] can be used to assigned names (identifier) to these subdomains which are then used in the headers of the output files and plots.\\\\
 If the default netCDF output format is selected (see parameter [#data_output_format data_output_format]), data for the total domain and all defined subdomains are output to the same file(s) ([[../iofiles#DATA_1D_PR_NETCDF|DATA_1D_PR_NETCDF]], [[../iofiles#DATA_1D_TS_NETCDF|DATA_1D_TS_NETCDF]]). In case of '''statistic_regions''' > 0, data on the file for the different domains can be distinguished by a suffix which is appended to the quantity names. Suffix 0 means data for the total domain, suffix 1 means data for subdomain 1, etc.
 }}}
@@ -785 +785 @@
 }}}
 {{{#!td style="vertical-align:top"
-dummy
-}}}
-{{{#!td style="vertical-align:top"
-dummy
-}}}
-{{{#!td
-dummy
+R
+}}}
+{{{#!td style="vertical-align:top"
+35.0
+}}}
+{{{#!td
+CPU time needed for terminal actions at the end of a run in batch mode (in s).\\\\
+If the environment variable '''write_binary''' is set ''.T.'' (see [[chapter 3.3]]), PALM checks the remaining CPU time of the job after each timestep. Time integration must not consume the CPU time completely, since several actions still have to be carried out after time integration has finished (e.g. writing of binary data for the restart run, carrying out output commands, copying of local files to their permanent destinations, etc.) which also takes some time. The maximum possible time needed for these activities plus a reserve is to be given with the parameter '''termination_time_needed'''. Among other things, it depends on the number of grid points used. If its value is selected too small, then the respective job will be prematurely aborted by the queuing system, which may result in a data loss and will possibly interrupt the job chain.\\\\
+An abort happens in any way, if the environment variable '''write_binary''' is not set to true and if moreover the job has been assigned an insufficient CPU time by '''mrun''' option {{{-t}}}.\\\\
+'''Note:'''\\
+On the IBM computers of the HLRN the time used by the job '''before''' the start of PALM have also to be accounted for (e.g. for compilation and copying of input files).
 }}}
 |----------------