Home

Context Navigation

iofiles

Timestamp:: Apr 6, 2016 4:18:24 PM (9 years ago)
Author:: scharf
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/iofiles

-                      v90
+                      v91
 The model works with a set of files, which are all located in the temporary working directory and which are either expected at the beginning of the run (the so-called input files) or which are produced during the run and/or at the end of the simulation (output files). The following table lists all default files addressed by the model. They are arranged according to the associated FORTRAN unit (unit number). The unit 90 is used for different files, which are opened only briefly and uniquely in the model and closed directly afterwards. Unit numbers 101 - 109, 111 - 113, 116 and 121-160 refer to data files which have netCDF format. These are not opened by a FORTRAN-OPEN-statement but by a corresponding netCDF call ({{{NF90_CREATE}}} or {{{NF90_OPEN}}}). These files are only created on machines where a netCDF library is available. \\\\
 The file names described in the list correspond to the names indicated in the respective OPEN instruction, i.e. the files are expected and saved under these names in the temporary working directory of the model. By default, file names are always written in capital letters. The third column indicates whether it is an input or output file (I and/or O). The netCDF files can be both input and output files (I/O). If restart jobs shall append data to an existing netCDF file (created by a previous job of the job chain), the respective file has to be given as an input file (see more details about the [../netcdf PALM-netCDF-output]). \\\\
 On parallel computers many of the files are read and/or written by the central processing element 0 (PE0) only. These files have processor-independent content (and therefore they can be read or written by other PEs just as well). However, certain files have processor-dependent content. For the binary output of data for restart runs (local file [#BINOUT BINOUT]), for example, each PE outputs only the data of its subdomain. So each processing element writes into its own file with its own file name. These files lie in a subdirectory of the temporary working directory. Their names are build off from the underline ("_") and the four digit processor ID. The data written for restart runs would be e.g. on the files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc. Such files, which have processor-dependent content on parallel computers, are marked in the following list by the fact, that to the file name a line ("/") is attached. If appropriate output files are to be copied through '''mrun''' to permanent files, and/or files with processor-dependent content are supposed to be copied as input files into the temporary working directory of the model, you have to indicate a special file attribute in the appropriate file connection statement (see [wiki:arpe arpe], [wiki:flpe flpe] in the '''mrun''' description). Then the permanent file name will be interpreted as a directory name, in which the input files are expected and/or to which output files are written. The file names in these directories are always named _0000, _0001, _0002 etc. \\\\
+On parallel computers, many of the files are read and/or written by the central processing element 0 (PE0) only. These files have processor-independent content (and therefore they can be read or written by other PEs just as well). However, certain files have processor-dependent content. For the binary output of data for restart runs (local file [#BINOUT BINOUT]), for example, each PE outputs only the data of its subdomain. So each processing element writes into its own file with its own file name. These files lie in a subdirectory of the temporary working directory. Their names are built from the underline ("_") and the four digit processor ID. The data written for restart runs would be e.g. on the files BINOUT/_0000 (PE0), BINOUT/_0001 (PE1), BINOUT/_0002 (PE2) etc. Such files, which have processor-dependent content on parallel computers, are marked in the following list by the fact, that to the file name a line ("/") is attached. If appropriate output files are to be copied through '''mrun''' to permanent files, and/or files with processor-dependent content are supposed to be copied as input files into the temporary working directory of the model, you have to indicate a special file attribute in the appropriate file connection statement (see [wiki:arpe arpe], [wiki:flpe flpe] in the '''mrun''' description). Then the permanent file name will be interpreted as a directory name, in which the input files are expected and/or to which output files are written. The file names in these directories are always named _0000, _0001, _0002 etc. \\\\
 For internal use, the model may open a set of further files, which are not defined by the user but contain no usable information and therefore are not included in this list. \\\\
 Depending on the configuration of the underlying file-system (e.g. Lustre) and the capacity of the I/O-hardware, simultaneous output to a larger number of files, i.e. if a larger number of PEs is used (>1000), may lead to severe problems as job aborts or even to a complete crash of the whole system. In order to circumvent this problem, the maximum number of parallel I/O streams (i.e. the number of files which are simultaneously written), can be limited by using the '''mrun'''-option {{{-w <max # of streams>}}}, where {{{<max # of streams>}}} should be smaller or equal 256 (on the SGI-ICE of HLRN-II). The (parallel) output is then done in a sequential order for blocks of 256 PEs. \\\\
 …
 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. \\\\
+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).
 …
 {{{#!td
 Binary data, which are written by the model at the end of the run and possibly needed by [../runs restart runs] for the initialization. This output file is then read in as file [#BININ BININ]. It contains the [../inipar initial parameters] 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 [../runs example]). \\\\
+The file BINOUT is written by the model only if, with the help of the '''mrun'''-configuration file, the environment variable {{{write_binary}}} is assigned to the {{{true}}} (see [../runs example]). \\\\
 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
 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 [../d3par#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 [../inipar#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 [../userpar#region 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: \\
+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: \\
 {{{#!table style="border:none"
 {{{#!td style="vertical-align:top;border:none;width:40px"
 …
 }}}
 {{{#!td
 This file contains the vertical profiles calculated by the 1D-model within initial runs. The quantities saved are set model-internally and cannot be determined by the user. At the respective output times (see [../inipar#dt_pr_1d dt_pr_1d]) a table with the following information is written to the file: The table 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 (this number should always be 00, because the 1D-model is only switched on at initial runs), executing computer, date, time of the beginning of the run, output time). Afterwards the following columns appear: \\
+This file contains the vertical profiles calculated by the 1D-model within initial runs. The quantities saved are set model-internally and cannot be determined by the user. At the respective output times (see [../inipar#dt_pr_1d dt_pr_1d]) a table with the following information is written to the file: The table 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 (this number should always be 00, because the 1D-model is only switched on at initial runs), executing computer, date, time of the beginning of the run, output time). Afterwards, the following columns appear: \\
 {{{#!table style="border:none"
 {{{#!td style="vertical-align:top;border:none;width:40px"
 …
 {{{#!td
 Time measurements are accomplished through the subroutine {{{cpu_log.f90}}}. The file CPU_MEASURES contains a header with 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) and afterwards two tables with data of CPU times which have been consumed by certain model parts. The model parts analyzed in the first table do not overlap and the CPU times needed for them therefore approximately add up to the “total” value given in the first line of this table. In the second table (heading: special measures) overlaps (in particular with the parts described in the first table) are possible. \\\\
 For each model part it is indicated in the following columns how much CPU time was needed (absolutely and relative), and how often it was called.  With runs on several processors the average values of all processors are indicated. In the case of parallel runs information for those processors with the largest and smallest CPU time follow as well as the standard deviation of all PEs from the average value. With good parallelization the CPU times on the individual processors should differ only little from each other and the standard deviation should be small.
+For each model part it is indicated in the following columns how much CPU time was needed (absolutely and relative), and how often it was called.  With runs on several processors, the average values of all processors are indicated. In the case of parallel runs, information for those processors with the largest and smallest CPU time follow as well as the standard deviation of all PEs from the average value. With good parallelization, the CPU times on the individual processors should differ only little from each other and the standard deviation should be small.
 }}}
 |----------------
 …
 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 [../packages Optional software packages] and [../userint/userpar 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 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 [../packages Optional software packages] and [../userint/userpar 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}}}).
 }}}
 |----------------
 …
 }}}
 {{{#!td
 This file is created in case of particle transport (see the [../parpar particles package]). It contains statistical informations about the number of particles used and about the number of particles exchanged between each single PE. These informations are output after every timestep if switched on by parameter [../parpar#write_particle_statistics write_particle_statistics].
+This file is created in case of particle transport (see the [../parpar particles package]). It contains statistical information about the number of particles used and about the number of particles exchanged between each single PE. This information is output after every timestep if switched on by parameter [../parpar#write_particle_statistics write_particle_statistics].
 }}}
 |----------------
 …
 {{{#!td
 This file is created if particle transport is switched on (see the [../parpar particles package]) and contains all particle data for one or several output times (see [../parpar#dt_write_particle_data dt_write_particle_data]). \\\\
 The first record of this file contains an identification string (PALM version number, run identifier, etc., 80 characters long). The second record also contains a version string (80 characters long) followed by two records with particle group informations (see file {{{check_open.f90}}}). Then, for each output time, two records follow, where the first one gives some general information (numbers of particles, etc.) and the second one contains the actual particle data. A FORTRAN TYPE structure is used for storing the particle attributes. See file {{{advec_particles.f90}}} for the detailed format.
+The first record of this file contains an identification string (PALM version number, run identifier, etc., 80 characters long). The second record also contains a version string (80 characters long) followed by two records with particle group information (see file {{{check_open.f90}}}). Then, for each output time, two records follow, where the first one gives some general information (numbers of particles, etc.) and the second one contains the actual particle data. A FORTRAN TYPE structure is used for storing the particle attributes. See file {{{advec_particles.f90}}} for the detailed format.
 }}}
 |----------------
 …
 }}}
 {{{#!td
 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 [#PARTICLE_RESTART_DATA_OUT PARTICLE_RESTART_DATA_OUT]). This file is needed if particle transport is switched on (see the [../parpar particles package]) and contains all particle informations (particle positions, velocities, etc.) from the end of the preceding run. Concerning runs on several processors it has to be noted that each processing element reads its own file and that 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. \\\\
 The first record of this file contains a version number (four character string) of the subroutine, which output the data that follows ({{{write_particles}}}, see end of file {{{advec_particles.f90}}}). This number has to agree with the version number of the subroutine which is reading the file ({{{init_parrticles.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. Some general informations like the number of particles stored in the file, the number of particle groups, etc. are stored in the second record. The third record includes the particles to be released at the source and the fourth record contains all current particles. In case that particle tails are used (see [../parpar#maximum_number_of_tailpoints maximum_number_of_tailpoints]), a further record may follow, which contains the particle tail informations. A FORTRAN TYPE structure is used for storing the particle attributes. For detailed informations about the file format see the corresponding READ statements in file {{{init_particles.f90}}}.
+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 [#PARTICLE_RESTART_DATA_OUT PARTICLE_RESTART_DATA_OUT]). This file is needed if particle transport is switched on (see the [../parpar particles package]) and contains all particle information (particle positions, velocities, etc.) from the end of the preceding run. Concerning runs on several processors it has to be noted that each processing element reads its own file and that 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. \\\\
+The first record of this file contains a version number (four character string) of the subroutine, which output the data that follows ({{{write_particles}}}, see end of file {{{advec_particles.f90}}}). This number has to agree with the version number of the subroutine which is reading the file ({{{init_parrticles.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. Some general information like the number of particles stored in the file, the number of particle groups, etc. are stored in the second record. The third record includes the particles to be released at the source and the fourth record contains all current particles. In case that particle tails are used (see [../parpar#maximum_number_of_tailpoints maximum_number_of_tailpoints]), a further record may follow, which contains the particle tail information. A FORTRAN TYPE structure is used for storing the particle attributes. For detailed informations about the file format see the corresponding READ statements in file {{{init_particles.f90}}}.
 }}}
 |----------------
 …
     0    0    0    0    0    0    0    0    0    0    0    0
 }}}
 These data must exactly match the horizontal grid. Due to the staggered grid the topography may be displaced by -0.5 [../inipar#dx dx] in x-direction and -0.5 [../inipar#dy dy] in y-direction depending on the parameter [../inipar#topography_grid_convention topography_grid_convention]. See also the example in [source:/palm/trunk/EXAMPLES/topo_file trunk/EXAMPLES/topo_file/]. \\\\
+These data must exactly match the horizontal grid. Due to the staggered grid, the topography may be displaced by -0.5 [../inipar#dx dx] in x-direction and -0.5 [../inipar#dy dy] in y-direction depending on the parameter [../inipar#topography_grid_convention topography_grid_convention]. See also the example in [source:/palm/trunk/EXAMPLES/topo_file trunk/EXAMPLES/topo_file/]. \\\\
 Alternatively, the user may add code to the user interface subroutine [../userint/int#user_init_grid user_init_grid] to allow different data formats.
 }}}
 …
 {{{#!td
 This file contains data of the two-dimensional horizontal cross sections (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the two-dimensional vertical (xz) cross sections (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the two-dimensional vertical (yz) cross sections (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the horizontally averaged vertical profiles (see [../d3par#data_output_pr data_output_pr]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 }}}
 {{{#!td
 This file contains data of the timeseries (see [../d3par#dt_dots dt_dots]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+This file contains data of the time series (see [../d3par#dt_dots dt_dots]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the 3d-volume data (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the horizontal spectra (see [../sppar#data_output_sp data_output_sp]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 }}}
 {{{#!td
 This file contains data of the timeseries of particle quantities (see [../parpar#dt_prel dt_prel]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). For a list of available output quantities see  [../parpar#dt_dopts dt_dopts]. \\\\
 In case of using more than one particle group (see [../parpar#number_of_particle_groups number_of_particle_groups]), seperate time series are output for each of the groups. The long names of the variables in the netCDF file containing the respective timeseries all end with the string '' ' PG '' ## '' ' '', where ## is the number of the particle group (01, 02, etc.). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+This file contains data of the time series of particle quantities (see [../parpar#dt_prel dt_prel]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). For a list of available output quantities see  [../parpar#dt_dopts dt_dopts]. \\\\
+In case of using more than one particle group (see [../parpar#number_of_particle_groups number_of_particle_groups]), separate time series are output for each of the groups. The long names of the variables in the netCDF file containing the respective time series all end with the string '' ' PG '' ## '' ' '', where ## is the number of the particle group (01, 02, etc.). \\\\
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the temporally averaged two-dimensional horizontal cross sections (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the temporally averaged two-dimensional vertical (xz) cross sections (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the temporally averaged two-dimensional vertical (yz) cross sections (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains data of the temporally averaged 3d-volume data (see [../d3par#data_output data_output]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains the masked data of '''location 1''' (see [../d3par#data_output_masks data_output_masks]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains the masked data of '''location 2''' (see [../d3par#data_output_masks data_output_masks]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains the masked data of '''location ...''' (see [../d3par#data_output_masks data_output_masks]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains the temporally averaged masked data of '''location 1''' (see [../d3par#data_output_masks data_output_masks]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains the temporally averaged masked data of '''location 2''' (see [../d3par#data_output_masks data_output_masks]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
 }}}
 |----------------
 …
 {{{#!td
 This file contains the temporally averaged masked data of '''location ...''' (see [../d3par#data_output_masks data_output_masks]) in netCDF format. The data in this file can be visualized by any graphic software which provides a netCDF interface (e.g. [../ncl NCL], [http://www.ferret.noaa.gov/Ferret/ ferret] or [http://meteora.ucsd.edu/~pierce/ncview_home_page.html ncview]). \\\\
 See the description of [../netcdf PALM-netCDF-output] for more detailed informations.
 }}}
 |----------------
+See the description of [../netcdf PALM-netCDF-output] for more detailed information.
+}}}
+|----------------