Changes between Version 6 and Version 7 of doc/app/netcdf

Timestamp:

Sep 16, 2010 1:56:44 PM (15 years ago)

Author:

herbort

Comment:

--

doc/app/netcdf

@@ -1 +1 @@
 == netCDF data output ==
 
-PALM is able to output data of different quantities as time series, vertical profiles (usually horizontally averaged), two-dimensional cross sections or 3d-volume data. Depending on the kind of output (time series, profiles, etc.) and the output format (ASCII  or binary) data are written to different files (file descriptions can be found [wiki:doc/app/iofiles here]). By default, all data output files are in netCDF format ([[http://www.unidata.ucar.edu/software/netcdf/]]), which can be processed by many public domain and commercial (graphic) software. Data from netCDF files can also be easily read from FORTRAN programs provided that a netCDF library is available. More detailed informations about the PALM-netCDF-output is given [wiki:doc/app/ncgen here] and [wiki:doc/app/ncexample here].
+PALM is able to output data of different quantities as time series, vertical profiles (usually horizontally averaged), two-dimensional cross sections or 3d-volume data. Depending on the kind of output (time series, profiles, etc.) and the output format (ASCII  or binary) data are written to different files (file descriptions can be found [wiki:doc/app/iofiles here]). By default, all data output files are in netCDF format ([[http://www.unidata.ucar.edu/software/netcdf/]]), which can be processed by many public domain and commercial (graphic) software. Data from netCDF files can also be easily read from FORTRAN programs provided that a netCDF library is available.
 
 Due to historical reasons, PALM can also output data in other formats suitable for some special graphic software. The exact format of these files corresponds to the requirements of the respective software. Still available at IMUK is '''AVS''' (e.g. iso-surfaces of 3d volume data). A description of the usage of the '''AVS''' software is given [wiki:doc/app/avs here].
@@ -9 +9 @@
 
 
-The standard data output of PALM is netCDF (network Common Data Form) in 64-bit offset format. netCDF is an interface to a library of data access functions for storing and retrieving data in the form of arrays. netCDF is an abstraction that supports a view of data as a collection of self-describing, portable objects that can be accessed through a simple interface (protable means that netCDF data files can be read on any machine regardless of where they have been created). Array values may be accessed directly, without knowing details of how the data are stored. Auxiliary information about the data, such as what units are used, may be stored with the data. Generic utilities and application programs can access netCDF datasets (files) and transform, combine, analyze, or display specified fields of the data, e.g. the contents of a netCDF dataset can be viewed using the command '''ncdump''' (see further below). Many (public domain) graphic software has built in interfaces to read netCDF datasets (e.g. '''ferret''' or '''NCL'''). The complete netCDF documentation is available from the netCDF homepage ([[http://www.unidata.ucar.edu/software/netcdf/]]). The netCDF tutorial for FORTRAN90 can also be found on our web server.
+The standard data output of PALM is netCDF (network Common Data Form) in 64-bit offset format. netCDF is an interface to a library of data access functions for storing and retrieving data in the form of arrays. netCDF is an abstraction that supports a view of data as a collection of self-describing, portable objects that can be accessed through a simple interface (protable means that netCDF data files can be read on any machine regardless of where they have been created). Array values may be accessed directly, without knowing details of how the data are stored. Auxiliary information about the data, such as what units are used, may be stored with the data. Generic utilities and application programs can access netCDF datasets (files) and transform, combine, analyze, or display specified fields of the data, e.g. the contents of a netCDF dataset can be viewed using the command '''ncdump''' (see further below). Many (public domain) graphic software has built in interfaces to read netCDF datasets (e.g. '''ferret''' or '''NCL''' ([wiki:doc/app/ncl see here])). The complete netCDF documentation is available from the netCDF homepage ([[http://www.unidata.ucar.edu/software/netcdf/]]). The netCDF tutorial for FORTRAN90 can also be found on our web server.
 
 The general output format of PALM data is determined by the runtime-parameter [wiki:doc/app/d3par#data_output_format data_output_format] (data_output_format = 'netcdf', by default). For historical reasons, some alternative formats can be selected. The accuracy of the netCDF output data can be set with parameter [wiki:doc/app/d3par#netcdf_precision netcdf_precision]. By default, data have single (4 byte) precision. Runtime-parameter [wiki:doc/app/d3par#data_output_format data_output_format] can be used to choose between the different netCDF file formats (classic, 64-bit offset, netCDF4/HDF5). The 64-bit offset format allows creating large files (file size only limited by the underlying file system), but each output variable (array) is still limited to 2GB. In netCDF4 format, there is no limit for the size of variables, and it also allows parallel I/O into one output file. However, some (graphic) software still does not support netCDF4 format. 
@@ -15 +15 @@
 PALM allows the output of various data (e.g. cross sections, vertical profiles, timeseries, etc.) into different files. The following table gives an overview about the different kind of netCDF output data offered by PALM. Beside the local names of the files, the table also lists the minimum parameter settings which are necessary to switch on the output, as well as the parameters to be used to control the output.
 
+||='''Kind of data'''  =||='''Local filename'''  =||='''Parameter settings \\ necessary to switch on output'''  =|| \
+||='''Further parameters for \\ output control'''  =||
+|----------------
+{{{#!td style="vertical-align:top; text-align:left;width: 150px"
+vertical profiles
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 50px"
+DATA_1D_PR_NETCDF
+}}}
+{{{#!td style="vertical-align:top; text-align:left;style="width: 75px"
+data_output_pr, dt_data_output (or dt_dopr)
+}}}
+{{{#!td
+averaging_interval, (or averaging_interval_pr), data_output_format, dt_averaging_input, dt_averaging_input_pr, skip_time_data_output (or skip_time_dopr), statistic_regions
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+timeseries
+}}}
+{{{#!td style="vertical-align:top"
+DATA_1D_TS_NETCDF
+}}}
+{{{#!td style="vertical-align:top"
+dt_dots
+}}}
+{{{#!td
+data_output_format, statistic_regions
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+spectra
+}}}
+{{{#!td style="vertical-align:top"
+DATA_1D_SP_NETCDF
+}}}
+{{{#!td style="vertical-align:top"
+comp_spectra_level, data_output_sp, dt_data_output (or dt_dosp), spectra_directions
+}}}
+{{{#!td
+averaging_interval (or averaging_interval_sp), data_output_format, dt_averaging_input_pr, skip_time_data_output (or skip_time_dosp)
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+2d cross section (xy)
+}}}
+{{{#!td style="vertical-align:top"
+DATA_2D_XY_NETCDF
+}}}
+{{{#!td style="vertical-align:top"
+data_output (or data_output_user), dt_data_output (or dt_do2d_xy), section_xy
+}}}
+{{{#!td
+data_output_format, data_output_2d_on_each_pe, do2d_at_begin, skip_time_data_output (or skip_time_do2d_xy)
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
 
+}}}
+{{{#!td style="vertical-align:top"
 
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td
+
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td
+
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td
+
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td
+
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td
+
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td
+
+}}}
+|----------------
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td style="vertical-align:top"
+
+}}}
+{{{#!td
+
+}}}
+|----------------