Home

Context Navigation

iofiles

Timestamp:: Sep 14, 2010 11:19:14 AM (14 years ago)
Author:: fricke
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/iofiles

-                      v22
+                      v23
 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).  \\\\
+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 [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]. \\\\
+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.
 }}}
 …
 Information about the selected model parameters (physical and numerical values) as well as general information about the run. \\\\
 This file contains the values of all important steering parameters (numerical procedures, computing grid and model dimensions, boundary conditions, physical dimension, turbulence quantities, actions during the simulation, 1D-model-parameters) as well as data concerning the selected plot and list outputs. The headlines of the file list the program version used, date and time of the beginning of the run, the name of the executing computer, the run identifier (corresponds to the selected base file name) and the number of the run (number of the restart run). With parallel runs the number of processors as well as the assigned virtual processor net also appear. After these headlines run time and time step information appear (point of starting time, related to t=0 of the initial run, end-time, time actually reached, CPU time, etc.). If a model run is incorrectly terminated (e.g. run time error or excess of the permitted CPU time), information over the time reached and the necessary CPU time is missing (to understand: the file HEADER is written twice by the model; once briefly after beginning of the simulation (naturally here the information over the time reached is missing etc.) and then briefly before the normal end of the simulation. The second, now complete output overwrites the first output.).  \\\\
 At the end of the file, information about the values of user parameters (see [wiki:chapter_37 chapter 3.7] and [wiki:chapter_43 chapter 4.3]) can be output by the user with the help of the subroutine {{{user_header}}} (located in the file {{{user_interface.f90}}}). If no user parameters were found, the string '!*** {{{no user-defined variables found}}}' appears at the end of the file. If user parameters were indicated, the string '{{{user-defined variables and actions}}}' is printed, followed by informations about the user-defined subdomains for which profiles and time series are output. All further information to appear here, must be provided by the user (by appropriate WRITE statements in {{{user_header}}}).
+At the end of the file, information about the values of user parameters (see [wiki:chapter_37 chapter 3.7] and [wiki:chapter_43 chapter 4.3]) can be output by the user with the help of the subroutine {{{user_header}}} (located in the file {{{user_interface.f90}}}). If no user parameters were found, the string '' '!*** no user-defined variables found' '' appears at the end of the file. If user parameters were indicated, the string '' 'user-defined variables and actions' '' is printed, followed by informations about the user-defined subdomains for which profiles and time series are output. All further information to appear here, must be provided by the user (by appropriate WRITE statements in {{{user_header}}}).
 }}}
 |----------------
 …
 }}}
 |----------------
+{{{#!td style="vertical-align:top; width: 50px"
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#TOPOGRAPHY_DATA TOPOGRAPHY_DATA]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+I
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+ASCII
+}}}
+{{{#!td
+Two-dimensional rastered topography height information (in m above ground). \\\\
+In case of  [../inipar#topography topography] = '' 'read_from_file' '' the subroutine init_grid reads the topography height information (in m above ground) for each grid point in a free floating point format. The ascii file format is ESRI grid - also known as ARC/INFO ASCII GRID - without the header. The data on file are laid out naturally, i.e. in W-E orientation horizontally and in S-N orientation vertically, they must thus be organized as follows:
+}}}
+|----------------