Standard table:

Unit	Name	I/O	Format	Description/contents
11	PARIN/ (PARIN_O)	I	ASCII/ NAMELIST	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.4.1? shows a simple example.
13	BININ/ (BININ_O)	I	Binary	Binary data, which are read in by the model at the beginning of a restart run chapter 3.3?. The appropriate file must have been written by the preceding job of the job chain (see BINOUT). This file contains the initial parameters 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 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: 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 nz and 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). 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 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).
14	BINOUT/ (BINOUT_O)	O	Binary	Binary data, which are written by the model at the end of the run and possibly needed by restart runs chapter 3.3? for the initialization. This output file is then read in as file BININ. It contains the initial parameters 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 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. 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 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.
15	RUN_CONTROL/ (RUN_CONTROL_O)	O	ASCII	This file contains the so-called time step control output of the model. At certain temporal intervals, which are described by the run parameter dt_run_control, a line with the values of certain control parameters is written into this file. Additionally, such a control line is always written, whenever the time step of the model changes. All data and quantities always refer to the entire model domain. If the 1D-model is switched on for the initialization of the 3D-models, then control lines are likewise written into this file at certain temporal intervals (see dt_run_control_1d?). By default, the file RUN_CONTROL only lists information about the selected model parameters at the beginning of the initial run. These informations are written at the beginnning of a run. They correspond to those of the file HEADER (however without data concerning the consumed CPU time, because these are only known at the end of a run). With the run parameter force_print_header it can be achieved that this information is also written at the beginning of the file RUN_CONTROL at restart runs. The individual columns of the 1D - time step control output have the following meaning (listed by the respective heading of the appropriate column in the file): ITER. Number of time steps accomplished so far HH:MM:SS Time (in hours: minutes: seconds) DT Time step (in s) UMAX Maximum absolute wind velocity (u-component) (in m/s) VMAX Maximum absolute wind velocity (v-component) (in m/s) U* Friction velocity (in m/s) ALPHA Angle of the wind vector (to the x-axis) at the top of the Prandtl layer (k=1) (in degrees) ENERG. Kinetic energy of the 1D-model (in m2/s2), averaged over all grid points The individual columns of the 3D - time step control output have the following meaning (listed by the respective heading of the appropriate column in the file): RUN Serial-number of the job in the job chain. The initial run has the number 0, restart runs accordingly have larger numbers. ITER. Number of time steps accomplished since starting time t=0 of the initial run. HH:MM:SS Time (in hours: minutes: seconds) since starting time t=0 of the initial run. DT (E) Time step (in s). The following character indicates whether the time step is limited by the advection criterion (A) or the diffusion criterion (D). After changes of the time step a further character follows, which indicates with which time step procedure the changed time step was accomplished (L: Leapfrog, E: Euler). This does not apply for the default Runge-Kutta timestep scheme. UMAX Maximum absolute wind velocity (u-component) (in m/s). If at the appropriate output time a random disturbance was added to the horizontal velocity field (see create_disturbances), the character D will appear directly after the velocity value. VMAX Maximum absolute wind velocity (v-component) (in m/s). If at the appropriate output time a random disturbance was added to the horizontal velocity field (see create_disturbances), the character D will appear directly after the velocity value. WMAX Maximum absolute wind velocity (w-component) (in m/s). U* Horizontal average of the friction velocity (in m/s). W* Convective velocity scale (in m/s). The assumed boundary layer height is determined via the heat flux minimum criterion. THETA* Characteristic temperature of the Prandtl - layer (in K). Z_I Height of the convective boundary layer (in m), determined via the criterion of the heat flux minimum. ENERG. Average resolved total energy of the flow field (in m2/s2), normalized with the total number of grid points. DISTENERG Average resolved disturbance energy of flow field (in m2/s2), normalized with the total number of grid points. DIVOLD Divergence of the velocity field (sum of the absolute values) (in 1/s) before call of the pressure solver, normalized with the total number of grid points. DIVNEW Divergence of the velocity field (sum of the absolute values) (in 1/s) after call of the pressure solver, normalized with the total number of grid points. UMAX (KJI) Indices of the grid point with the maximum absolute u-component of the wind velocity (sequence: k, j, i). VMAX (KJI) Indices of the grid point with the maximum absolute v-component of the wind velocity (sequence: k, j, i). WMAX (KJI) Indices of the grid point with the maximum absolute w-component of the wind velocity (sequence: k, j, i). ADVECX Distance (in km) the coordinate system has been moved in x-direction with Galilei-Transformation switched on (see galilei_transformation). ADVECY Distance (in km) the coordinate system has been moved in y-direction with Galilei-Transformation switched on (see galilei_transformation).
16	LIST_PROFIL/ (LIST_PROFIL_O)	O	ASCII	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 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 statistic_regions for additional statistic evaluation, then the tables described above are written for each individual subdomain. The name of the respective subdomain (see region) appears in the header of the respective table. 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 of 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: k Vertical grid point index. zu Height of the grid point level (in m). u u-component of the wind velocity (in m/s). du Deviation of the u-component from the initial profile at the time t=0 (initialization profile) (in m/s). v v-component of the wind velocity (in m/s). dv Deviation of the v-component from the initial profile at the time t=0 (initialization profile) (in m/s). pt Potential temperature (in K). dpt Deviation of potential temperature from the initial profile at the time t=0 (initialization profile) (in K). e Turbulent kinetic energy (subgrid-scale) (in m2/s2). Km Turbulent diffusion coefficient for momentum (in m2/s). Kh Turbulent diffusion coefficient for heat (in m2/s). l Mixing length (in m). On the w-level the following columns are written: k Vertical grid point index. zw Height of the grid point level (in m). w'pt' Vertical subgrid-scale kinematic heat flux (in K m/s). wpt Vertical total ( subgrid-scale + resolved) kinematic heat flux (in K m/s). w'u' u-component of the vertical subgrid-scale momentum flux (in m2/s2). wu u-component of the total vertical momentum flux ( subgrid-scale + resolved) (in m2/s2). w'v' v-component of the vertical subgrid-scale momentum flux (in m2/s2). wv v-component of the total vertical momentum flux ( subgrid-scale + resolved) (in m2/s2).