Home

Context Navigation

iofiles

Timestamp:: Sep 14, 2010 7:23:10 AM (14 years ago)
Author:: fricke
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/iofiles

-                      v7
+                      v8
 }}}
 {{{#!td
+??
+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.
+Parameter for model steering. This file is needed by the model in each case. Its content and structure is described in detail in [wiki:chapter_441 chapter 4.4.1] shows a simple example.
 }}}
 |----------------
 …
 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. \\\\
+{{{#!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. \\\\
 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. \\\\
+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. \\\\
 At the end of the initial parameters a record with the string "!***end!***" follows (filled up with trailing blanks up to a length of 30 characters).  \\\\
 Afterwards the fields of the prognostic and diagnostic variables follow. This part of the file also begins with a record consisting of a character string of length 10, which contains the version number of the subroutine that wrote the arrays that follow (write_3d_binary.f90). It must agree with the number of the reading subroutine (read_3d_binary.f90). \\\\
+At the end of the initial parameters a record with the string '!***end!***' follows (filled up with trailing blanks up to a length of 30 characters).  \\\\
+Afterwards the fields of the prognostic and diagnostic variables follow. This part of the file also begins with a record consisting of a character string of length 10, which contains the version number of the subroutine that wrote the arrays that follow ({{{write_3d_binary.f90}}}). It must agree with the number of the reading subroutine ({{{read_3d_binary.f90}}}). \\\\
 The following record contains the number of processors which were used in the model run producing this file, the processor ID of the special processor, which creates the file, as well as the lower and upper array indices of the subdomain belonging to this processing element. If no complete agreement with the values of the current model run exists, then this is aborted. This examination must be made in particular on parallel computers, because the jobs of a job chain always have to use the same number of processors and the same virtual processor grid. \\\\
 After these tests the individual arrays as well as parameters and variables for plots of horizontally averaged vertical profiles follow. Like the initialization parameters, they consist of two records. In the first record, the name of the array or the variable (character string, consisting of 20 characters, filled with trailing blanks) is located, in the second one its values follow. The sequence of the individual variables may be arbitrary again. The parameters for the plot and the respective variables are only read in if for the run parameter [../d3par#use_prior_plot1d_parameters use_prior_plot1d_parameters] = .T. is selected, otherwise they will be skipped.\\\\
 At the end of the file there has to be a record with the character string "!***end!***" (filled up with trailing blanks up to a length of 20 characters).
+At the end of the file there has to be a record with the character string '!***end!***' (filled up with trailing blanks up to a length of 20 characters).
 }}}
 |----------------
 …
 }}}
 {{{#!td
+??
+Binary data, which are written by the model at the end of the run and possibly needed by restart runs '''??(see chapter 3.3)??''' for the initialization. This output file is then read in as file [#BININ BININ]. It contains the initial parameters '''??(see chapter 4.1)??''' of the model run, arrays of the prognostic and diagnostic variables as well as those parameters determined so far during a job chain and variables for plots of horizontally averaged vertical profiles (see [../d3par#data_output_pr data_output_pr]). With runs on several processors it has to be noted that each processing element writes its own file and the file content is processor-dependent. A specification of the file format can be found in the description of the file [#BININ BININ]. \\\\
+The file BINOUT is written by the model only if, with the help of the '''mrun'''-configuration file, the value ''true'' is assigned for the environment variable ''write_binary'' '''?? (see chapter 3.3)??'''. \\\\
+Binary data, which are written by the model at the end of the run and possibly needed by restart runs [wiki:chapter_33 chapter 3.3] for the initialization. This output file is then read in as file [#BININ BININ]. It contains the initial parameters [wiki:chapter_41 chapter 4.1] of the model run, arrays of the prognostic and diagnostic variables as well as those parameters determined so far during a job chain and variables for plots of horizontally averaged vertical profiles (see [../d3par#data_output_pr data_output_pr]). With runs on several processors it has to be noted that each processing element writes its own file and the file content is processor-dependent. A specification of the file format can be found in the description of the file [#BININ BININ]. \\\\
+The file BINOUT is written by the model only if, with the help of the '''mrun'''-configuration file, the value ''true'' is assigned for the environment variable ''write_binary'' [wiki:chapter_33 chapter 3.3]. \\\\
 With large grid point numbers the file BINOUT (or the files residing in directory BINOUT/) will be very large and should be stored (if available) on the archive system of the remote computer.
 }}}
 …
 }}}
 {{{#!td style="vertical-align:top"
 Ascii
+ASCII
 }}}
 {{{#!td