Changes between Version 126 and Version 127 of doc/app/iofiles
- Timestamp:
- Feb 27, 2021 11:32:54 AM (4 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
doc/app/iofiles
v126 v127 312 312 }}} 313 313 {{{#!td 314 This file contains horizontally (and possibly temporally) averaged vertical profiles of some model variables. The quantities saved are set model-internally and can not be determined by the user. At each output time (see [../runtime_parameters#dt_dopr_listing dt_dopr_listing]) two tables are written to the file consecutively. The first contains variables which are defined on the scalar / u-v-grid-levels, the second table contains variables which are defined on the w-grid-levels. If subdomains were defined with the initialization parameter [../initialization_parameters#statistic_regions statistic_regions] for additional statistic evaluation, then the tables described above are written for each individual subdomain. The name of the respective subdomain (see [../user par#region region]) appears in the header of the respective table. \\314 This file contains horizontally (and possibly temporally) averaged vertical profiles of some model variables. The quantities saved are set model-internally and can not be determined by the user. At each output time (see [../runtime_parameters#dt_dopr_listing dt_dopr_listing]) two tables are written to the file consecutively. The first contains variables which are defined on the scalar / u-v-grid-levels, the second table contains variables which are defined on the w-grid-levels. If subdomains were defined with the initialization parameter [../initialization_parameters#statistic_regions statistic_regions] for additional statistic evaluation, then the tables described above are written for each individual subdomain. The name of the respective subdomain (see [../user_parameters#region region]) appears in the header of the respective table. \\ 315 315 In each case the tables consist of a header, followed by the profiles arranged next to each other in columns. The header contains some basic information about the respective run (model version, run identifier consisting of basic file name and number of the job in the job chain, executing computer, date, time of the beginning of the run, name of the subdomain, output time, kind of averaging). On the u-v-level the following columns are written: \\ 316 316 {{{#!table style="border:none" … … 581 581 Information about the selected model parameters (physical and numerical values) as well as general information about the run. \\\\ 582 582 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.). \\\\ 583 At the end of the file, information about the values of user parameters (see [../packages Optional software packages] and [../userint/user paruser-defined parameters]) 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 information 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}}}).583 At the end of the file, information about the values of user parameters (see [../packages Optional software packages] and [../userint/user_parameters user-defined parameters]) 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 information 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}}}). 584 584 }}} 585 585 |----------------