Changes between Version 1 and Version 2 of doc/app/iofiles

Timestamp:

Sep 13, 2010 2:29:37 PM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -1 +1 @@
 Standard table:\\
-||='''Parameter Name'''  =||='''Type'''  =||='''Default Value'''  =||='''Explanation'''  =||
+||='''Unit'''  =||='''Name'''  =||='''I/O'''  =||='''Format'''  =||='''Description/contents'''  =||
 |----------------
-{{{#!td style="vertical-align:top; text-align:left;width: 150px"
-[=#averaging_interval '''averaging_interval''']
+{{{#!td style="vertical-align:top; width: 50px"
+11
 }}}
-{{{#!td style="vertical-align:top; text-align:left;width: 50px"
-R
+{{{#!td style="vertical-align:top; width: 150px"
+PARIN \\
+(PARIN_O)
 }}}
-{{{#!td style="vertical-align:top; text-align:left;width: 100px"
-0.0
+{{{#!td style="vertical-align:top; width: 50px"
+I
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+ASCII/ \\
+NAMELIST
 }}}
 {{{#!td
-ff
+??
+Parameter for model steering. This file is needed by the model in each case. Its content and structure is described in detail in ''' ???chapter 4.0. Chapter 4.4.1 ??? ''' shows a simple example.  
 }}}
 |----------------
 {{{#!td style="vertical-align:top"
-[=#<insert_parameter_name> '''<insert_parameter_name>''']
+13
 }}}
 {{{#!td style="vertical-align:top"
-<insert type>
+BININ \\
+(BININ_O)
 }}}
 {{{#!td style="vertical-align:top"
-<insert value>
+I
 }}}
+{{{#!td style="vertical-align:top"
+Binary
+}}}
+{{{#!td
+??      
+Binary data, which are read in by the model at the beginning of a restart run ''' ??(see chapter 3.3)?? '''. The appropriate file must have been written by the preceding job of the job chain (see [#BINOUT BINOUT]). This file contains the initial parameters ''' ??(see chapter 4.1)?? ''' of the job chain, arrays of the prognostic and diagnostic variables as well as those parameters and variables for plots of horizontally averaged vertical profiles (see [../d3par#data_output_pr data_output_pr]), which have been determined by the job chain so far. Concerning runs on several processors it has to be noted that each processing element reads its own file and the file content is processor-dependent. The number of processors which can be used must not be changed during a job chain and/or if a job chain is continued. \\\\
+Knowledge of the file structure is usually not necessary, because the file is produced and also read again by the model, but it can be useful for error determination in case of read errors. Therefore the file structure is described in the following.  \\\\
+The first record of this file contains a version number (ten character string) of the subroutine, which output the data that follows (write_var_list.f90). This number has to agree with the version number subroutine which is reading the file (read_var_list.f90) in case of a restart run. Otherwise the model run is aborted. Version numbers are changed whenever new code revisions require a change of the file format. \\\\
+Starting from the second record, all initial parameters follow (exception: [../inipar#initializing_actions initializing_actions]), whereby each parameter fills two records. In the first record the name of the parameter is saved as a character string (30 characters long, short names are filled by trailing blanks, longer names are cut off at the end), in the second record the value (or the values) of the parameter follow. The sequence of parameters on the file may be arbitrary, however the first and second variable must be [../inipar#nz nz] and [../d3par#statistic_regions statistic_regions]. If a variable with unknown name is found the model run is aborted.       
+}}}
+|----------------