Changes between Version 33 and Version 34 of doc/app/iofiles

Timestamp:

Sep 14, 2010 3:17:06 PM (14 years ago)

Author:

fricke

Comment:

--

doc/app/iofiles

@@ -570 +570 @@
 |----------------
 {{{#!td style="vertical-align:top; width: 50px"
+21
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#PLOT2D_XY PLOT2D_XY] \\
+[=#PLOT2D_XY_O (PLOT2D_XY_O)]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+O
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+Binary
+}}}
+{{{#!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 '''mrun'''). 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].
+}}}
+|----------------
+{{{#!td style="vertical-align:top; width: 50px"
+22
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#PLOT2D_XZ PLOT2D_XZ] \\
+[=#PLOT2D_XZ_O (PLOT2D_XZ_O)]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+O
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+Binary
+}}}
+{{{#!td
+This file contains the data of the xz cross sections written by the model. \\\\
+The description of the local file [#PLOT2D_XY PLOT2D_XY] applies to this file, respectively.
+}}}
+|----------------
+{{{#!td style="vertical-align:top; width: 50px"
+23
+}}}
+{{{#!td style="vertical-align:top; width: 150px"
+[=#PLOT2D_YZ PLOT2D_YZ] \\
+[=#PLOT2D_YZ_O (PLOT2D_YZ_O)]
+}}}
+{{{#!td style="vertical-align:top; width: 50px"
+O
+}}}
+{{{#!td style="vertical-align:top; width: 100px"
+Binary
+}}}
+{{{#!td
+This file contains the data of the yz cross sections written by the model. \\\\
+The description of the local file [#PLOT2D_XY PLOT2D_XY] applies to this file, respectively.
+}}}
+|----------------
+{{{#!td style="vertical-align:top; width: 50px"
 30
 }}}
@@ -584 +639 @@
 {{{#!td
 This file contains the data of the three-dimensional arrays (see [../d3par#data_output data_output]) written by the model in a format readable for the visualization software AVS. Beyond that AVS needs coordinate information, which are output into the local file [#PLOT3D_COOR PLOT3D_COOR], as well as the local files [#PLOT3D_FLD PLOT3D_FLD] and [#PLOT3D_FLD_COOR PLOT3D_FLD_COOR], which describe the structure of the files PLOT3D_DATA and PLOT3D_COOR in the so-called AVS-FLD-format. Due to the fact that AVS expects these information in only one (so-called FLD -) file, the content of the file PLOT3D_FLD_COOR must be appended to the file PLOT3D_FLD by the user after the end of the model run (e.g. with an appropriate OUTPUT - command in the '''mrun'''-configuration file: "{{{cat PLOT3D_FLD_COOR >> PLOT3D_FLD}}}"). \\\\
-With parallel runs each processing element writes the data of its subdomain to a separate file with the name PLOT3D_DATA_<Processor-Id>, where <Processor-Id> is a four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable for AVS, but after the end of the model run they can be combined to one file readable for AVS with the help of the program {{{combine_plot_fields.x}}} (automatically activated by mrun). This tool expects the files of the individual processing elements under the names described above and outputs the combined file into a new file PLOT3D_DATA.
-The tool writes informative messages about the accomplished actions into the job protocol (e.g., even if no files were found). By the call of {{{combine_plot_fields.x}}} also possibly existing files with two-dimensional plot data (see e.g. PLOT2D_XY) are combined. \\\\   
+With parallel runs each processing element writes the data of its subdomain to a separate file with the name PLOT3D_DATA_<Processor-Id>, where <Processor-Id> is a four digit number (e.g. PLOT3D_DATA_0000). These files are not suitable for AVS, but after the end of the model run they can be combined to one file readable for AVS with the help of the program {{{combine_plot_fields.x}}} (automatically activated by '''mrun'''). This tool expects the files of the individual processing elements under the names described above and outputs the combined file into a new file PLOT3D_DATA.
+The tool writes informative messages about the accomplished actions into the job protocol (e.g., even if no files were found). By the call of {{{combine_plot_fields.x}}} also possibly existing files with two-dimensional plot data (see e.g. [#PLOT2D_XY PLOT2D_XY]) are combined. \\\\   
 With parallel runs the output of data of large volume is also possible in compressed form. For this purpose the initialization parameter  [../d3par#do3d_compress do3d_compress] = ''.T.'' must be set and the desired output accuracy has to be indicated with the help of [../d3par#do3d_comp_prec do3d_comp_prec]. In favorable cases the file size can be reduced by a factor of up to 5. For the visualization of compressed data a special AVS module ({{{read_compressed_field}}}) and a further entry in the '''mrun'''-configuration file are needed. More details can be found in [wiki:chapter_456 chapter 4.5.6].
 }}}