Changes between Version 17 and Version 18 of doc/app/iofiles

Timestamp:

Sep 14, 2010 9:07:52 AM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -79 +79 @@
 {{{#!td
 This file contains the so-called time step control output of the model. At certain temporal intervals, which are described by the run parameter [../d3par#dt_run_control dt_run_control], a line with the values of certain control parameters is written into this file. Additionally, such a control line is always written, whenever the time step of the model changes. All data and quantities always refer to the entire model domain. \\\\
-If the 1D-model is switched on for the initialization of the 3D-models, then control lines are likewise written into this file at certain temporal intervals (see [../ini#dt_run_control_1d dt_run_control_1d]). \\\\
+If the 1D-model is switched on for the initialization of the 3D-models, then control lines are likewise written into this file at certain temporal intervals (see [../inipar#dt_run_control_1d dt_run_control_1d]). \\\\
 By default, the file RUN_CONTROL only lists information about the selected model parameters at the beginning of the initial run. These informations are written at the beginnning of a run. They correspond to those of the file [#HEADER HEADER] (however without data concerning the consumed CPU time, because these are only known at the end of a run). With the run parameter [../d3par#force_print_header force_print_header] it can be achieved that this information is also written at the beginning of the file RUN_CONTROL at restart runs. \\\\
 The individual columns of the 1D - time step control output have the following meaning (listed by the respective heading of the appropriate column in the file):  \\
@@ -532 +532 @@
 }}}
 |----------------
+{{{#!td style="vertical-align:top; width: 50px"
+18
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#CPU_MEASURES CPU_MEASURES/] \\
+[=#CPU_MEASURES_O (CPU_MEASURES_O)]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+O
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+ASCII
+}}}
+{{{#!td
+Time measurements are accomplished through the subroutine {{{cpu_log.f90}}}. The file CPU_MEASURES contains a header with some basic information of the respective run (model version, run identifier consisting of basic file name and number of the job in the job chain, executing computer, date, time of the beginning of the run) and afterwards two tables with data of CPU times which have been consumed by certain model parts. The model parts analyzed in the first table do not overlap and the CPU times needed for them therefore approximately add up to the “total” value given in the first line of this table. In the second table (heading: special measures) overlaps (in particular with the parts described in the first table) are possible. \\\\ 
+For each model part it is indicated in the following columns how much CPU time was needed (absolutely and relative), and how often it was called.  With runs on several processors the average values of all processors are indicated. In the case of parallel runs information for those processors with the largest and smallest CPU time follow as well as the standard deviation of all PEs from the average value. With good parallelization the CPU times on the individual processors should differ only little from each other and the standard deviation should be small.  
+}}}
+|----------------