Home

Context Navigation

iofiles

Timestamp:: Feb 24, 2021 3:22:31 PM (4 years ago)
Author:: wagner
Comment:: --

Legend:

: Unmodified
: Added
: Removed
: Modified

doc/app/iofiles

-                      v122
+                      v123
 }}}
 {{{#!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 [#BINOUT BINOUT]). This file contains the [../initialization_parameters initial parameters] 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. \\\\
+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 [#BINOUT BINOUT]). This file contains the [../initialization_parameters initial parameters] 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 [../runtime_parameters#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. \\\\
 …
 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.\\\\
+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 [../runtime_parameters#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 [../initialization_parameters 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]. \\\\
+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 [../initialization_parameters 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 [../runtime_parameters#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 [wiki:doc/app/palmrun palmrun]-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 the so-called time step control output of the model. At certain temporal intervals, which are described by the run parameter [../d3par#dt_run_control 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. \\\\
+This file contains the so-called time step control output of the model. At certain temporal intervals, which are described by the run parameter [../runtime_parameters#dt_run_control 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 [../initialization_parameters#dt_run_control_1d 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 HEADER] (however without data concerning the consumed CPU time, because these are only known at the end of a run). With the run parameter [../d3par#force_print_header force_print_header] it can be achieved that this information is also written at the beginning of the file RUN_CONTROL at restart runs. \\\\
+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 HEADER] (however without data concerning the consumed CPU time, because these are only known at the end of a run). With the run parameter [../runtime_parameters#force_print_header 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):  \\
 {{{#!table style="border:none"
 …
 }}}
 {{{#!td style="vertical-align:top;border:none"
 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 [../d3par#create_disturbances create_disturbances]), the character D will appear directly after the velocity value.
+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 [../runtime_parameters#create_disturbances create_disturbances]), the character D will appear directly after the velocity value.
 }}}
 |------
 …
 }}}
 {{{#!td style="vertical-align:top;border:none"
 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 [../d3par#create_disturbances create_disturbances]), the character D will appear directly after the velocity value.
+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 [../runtime_parameters#create_disturbances create_disturbances]), the character D will appear directly after the velocity value.
 }}}
 |------
 …
 }}}
 {{{#!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 [../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 [../userpar#region region]) appears in the header of the respective table. \\
+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 [../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 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
 This file contains data of the two-dimensional horizontal cross sections written by the model (see [../d3par#data_output data_output]). \\\\
 With parallel runs and choice of [../d3par#data_output_2d_on_each_pe data_output_2d_on_each_pe] = ''.T.'' each processing element writes the data of its subdomain to a separate file with the name PLOT2D_XY_<processor-Id>, whereby <processor-Id> is a four digit number (e.g. PLOT2D_XY_0000). After PALM has finished, the contents of these individual files are sampled into one final file using the program {{{combine_plot_fields.x}}} (automatically activated by [wiki:doc/app/palmrun palmrun]). The tool writes informative messages about the actions accomplished into the job protocol (e.g., even if no files were found). By the call of {{{combine_plot_fields.x}}} possibly existing files of the other cross sections (xz and/or yz) and three-dimensional arrays (see [#PLOT3D_DATA PLOT3D_DATA]) are also combined. \\\\
 Further information about the output of plots of two-dimensional cross sections is found in the description of the run parameter [../d3par#data_output data_output].
+This file contains data of the two-dimensional horizontal cross sections written by the model (see [../runtime_parameters#data_output data_output]). \\\\
+With parallel runs and choice of [../runtime_parameters#data_output_2d_on_each_pe data_output_2d_on_each_pe] = ''.T.'' each processing element writes the data of its subdomain to a separate file with the name PLOT2D_XY_<processor-Id>, whereby <processor-Id> is a four digit number (e.g. PLOT2D_XY_0000). After PALM has finished, the contents of these individual files are sampled into one final file using the program {{{combine_plot_fields.x}}} (automatically activated by [wiki:doc/app/palmrun palmrun]). The tool writes informative messages about the actions accomplished into the job protocol (e.g., even if no files were found). By the call of {{{combine_plot_fields.x}}} possibly existing files of the other cross sections (xz and/or yz) and three-dimensional arrays (see [#PLOT3D_DATA PLOT3D_DATA]) are also combined. \\\\
+Further information about the output of plots of two-dimensional cross sections is found in the description of the run parameter [../runtime_parameters#data_output data_output].
 }}}
 |----------------
 …
 }}}
 {{{#!td
 This file contains the data of the three-dimensional arrays (see [../d3par#data_output data_output]) in netCDF format. The specific netCDF format (e.g. classic, 64-bit offset, netcdf4, etc.) depends on the setting of d3par-parameter [../d3par#netcdf_data_format netcdf_data_format].\\\\
+This file contains the data of the three-dimensional arrays (see [../runtime_parameters#data_output data_output]) in netCDF format. The specific netCDF format (e.g. classic, 64-bit offset, netcdf4, etc.) depends on the setting of d3par-parameter [../runtime_parameters#netcdf_data_format netcdf_data_format].\\\\
 With parallel runs and {{{netcdf_data_format}}} < ''5'', each processing element first writes the data of its subdomain in FORTRAN binary format to a separate file named PLOT3D_DATA_<Processor-Id>, where <Processor-Id> is a four digit number (e.g. PLOT3D_DATA_0000). After PALM has finished, contents of these files are collected by the helper routine {{{combine_plot_fields.x}}} (automatically executed by [wiki:doc/app/palmrun palmrun]). This tool expects the files of the individual processing elements under the names described above and outputs the combined data in netCDF format into the final file named PLOT3D_DATA. The tool writes informative messages about the accomplished actions into the job protocol (also if no files were found). Helper routine {{{combine_plot_fields.x}}} also collects files containing two-dimensional data (see e.g. [#PLOT2D_XY PLOT2D_XY]).\\\\
 With {{{netcdf_data_format}}} > ''4'' PALM directly writes the data of the subdomains into one single file using parallel I/O (MPI I/O), which makes a call of {{{combine_plot_fields.x}}} obsolete.
 …
 }}}
 {{{#!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]). \\\\
+This file contains data of the two-dimensional horizontal cross sections (see [../runtime_parameters#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 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]). \\\\
+This file contains data of the two-dimensional vertical (xz) cross sections (see [../runtime_parameters#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 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]). \\\\
+This file contains data of the two-dimensional vertical (yz) cross sections (see [../runtime_parameters#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 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]). \\\\
+This file contains data of the horizontally averaged vertical profiles (see [../runtime_parameters#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 information.
 }}}
 …
 }}}
 {{{#!td
 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]). \\\\
+This file contains data of the time series (see [../runtime_parameters#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]). \\\\
+This file contains data of the 3d-volume data (see [../runtime_parameters#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 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]). \\\\
+This file contains data of the temporally averaged two-dimensional horizontal cross sections (see [../runtime_parameters#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 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]). \\\\
+This file contains data of the temporally averaged two-dimensional vertical (xz) cross sections (see [../runtime_parameters#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 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]). \\\\
+This file contains data of the temporally averaged two-dimensional vertical (yz) cross sections (see [../runtime_parameters#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 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]). \\\\
+This file contains data of the temporally averaged 3d-volume data (see [../runtime_parameters#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 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]). \\\\
+This file contains the masked data of '''location 1''' (see [../runtime_parameters#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 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]). \\\\
+This file contains the masked data of '''location 2''' (see [../runtime_parameters#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 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]). \\\\
+This file contains the masked data of '''location ...''' (see [../runtime_parameters#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 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]). \\\\
+This file contains the temporally averaged masked data of '''location 1''' (see [../runtime_parameters#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 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]). \\\\
+This file contains the temporally averaged masked data of '''location 2''' (see [../runtime_parameters#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 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]). \\\\
+This file contains the temporally averaged masked data of '''location ...''' (see [../runtime_parameters#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 information.
 }}}