Changes between Version 10 and Version 11 of doc/app/iofiles

Timestamp:

Sep 14, 2010 8:14:01 AM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -81 +81 @@
 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]). \\\\
 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):  \\\\
+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):  \\
 {{{#!table style="border:none"
-{{{#!td style="vertical-align:top;border:none"
+{{{#!td style="vertical-align:top;border:none;width:80px"
 ITER.
 }}}
@@ -139 +139 @@
 }}}
 }}}
-The individual columns of the 3D - time step control output have the following meaning (listed by the respective heading of the appropriate column in the file): \\\\
+The individual columns of the 3D - time step control output have the following meaning (listed by the respective heading of the appropriate column in the file): \\
 {{{#!table style="border:none"
-{{{#!td style="vertical-align:top;border:none"
+{{{#!td style="vertical-align:top;border:none;width:80px"
 RUN
 }}}