Changes between Version 62 and Version 63 of doc/app/iofiles

Timestamp:

Sep 20, 2010 11:34:33 AM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -40 +40 @@
 }}}
 {{{#!td         
-Binary data, which are read in by the model at the beginning of a restart run [wiki:chapter_33 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 [wiki:chapter_41 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. \\\\
+Binary data, which are read in by the model at the beginning of a [../runs restart run]. The appropriate file must have been written by the preceding job of the job chain (see [#BINOUT BINOUT]). This file contains the [../inipar initial parameters] 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. \\\\