Home


About us
PALM
PALM-4U
Installation
Release notes
Documentation
Getting Help
Gallery
Developers area

Changes between Version 29 and Version 30 of doc/app/iofiles


Ignore:
Timestamp:
Sep 14, 2010 2:15:44 PM (14 years ago)
Author:
fricke
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • doc/app/iofiles

    v29 v30  
    584584{{{#!td
    585585?????
    586 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}}}"). \\\\
     586This 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}}}"). \\\\
    587587??\\
    588 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}}}. 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. Usually it is called by an appropriate OUTPUT - command in the MRUN-configuration file. 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. \\\\   
    589 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].
     588With 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}}}. 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. Usually it is called by an appropriate OUTPUT - command in the '''mrun'''-configuration file. 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. \\\\   
     589With 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].
    590590}}}
    591591|----------------
    … …  
    623623{{{#!td
    624624AVS-Fld-file describing the three-dimensional array data, saved by the model into the local file [#PLOT3D_DATA PLOT3D_DATA], needed by the visualization software AVS. \\\\
    625 This file describes the structure of the file PLOT3D_DATA (e.g. number of arrays, array dimensions, data type etc.). It uses the so-called AVS-Fld-format. It also contains the name of the file (inclusive cycle number, but without path) under which the local file PLOT3D_DATA is saved (this is the file name given in the file connection statement of the MRUN – configuration) in the permanent directory of the user (possibly on remote computers). Under this name AVS expects the data which are to be visualized. If there is no file connection statement for PLOT3D_DATA indicated in the configuration file, that file (filename) is registered "unknown" in the file PLOT3D_FLD and the actual name must be inserted later by hand. The file PLOT3D_FLD should be saved by the user in the same permanent directory as PLOT3D_DATA, so that AVS can find the file PLOT3D_DATA without any problems. If the two files lie in different directories, then the path name of the file PLOT3D_DATA must be added. \\\\
     625This file describes the structure of the file PLOT3D_DATA (e.g. number of arrays, array dimensions, data type etc.). It uses the so-called AVS-Fld-format. It also contains the name of the file (inclusive cycle number, but without path) under which the local file PLOT3D_DATA is saved (this is the file name given in the file connection statement of the '''mrun'''–configuration) in the permanent directory of the user (possibly on remote computers). Under this name AVS expects the data which are to be visualized. If there is no file connection statement for PLOT3D_DATA indicated in the configuration file, that file (filename) is registered "unknown" in the file PLOT3D_FLD and the actual name must be inserted later by hand. The file PLOT3D_FLD should be saved by the user in the same permanent directory as PLOT3D_DATA, so that AVS can find the file PLOT3D_DATA without any problems. If the two files lie in different directories, then the path name of the file PLOT3D_DATA must be added. \\\\
    626626AVS-Fld-files are expected by AVS to have the suffix "{{{.fld}}}". Cycle numbers must not be attached behind this "{{{.fld}}}" suffix. This suffix is attached to the permanent file names (still after possible cycle numbers) by '''mrun''' if "{{{fld}}}" is indicated in the [wiki:column6 column6] of the file connection statement. \\\\
    627 Likewise, AVS expects information about the coordinate system underlying the arrays on this file. This information is output by the model into the local file [#PLOT3D_FLD_COOR PLOT3D_FLD_COOR], whose content the user has to append to the file PLOT3D_FLD 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"). \\\\
     627Likewise, AVS expects information about the coordinate system underlying the arrays on this file. This information is output by the model into the local file [#PLOT3D_FLD_COOR PLOT3D_FLD_COOR], whose content the user has to append to the file PLOT3D_FLD 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"). \\\\
    628628For parallel runs, PLOT3D_FLD is produced by PE0 only.
    629629}}}
    … …  
    644644{{{#!td
    645645File for the description of the coordinate information output by the model into the local file [#PLOT3D_COOR PLOT3D_COOR], which is needed for the visualization of three-dimensional array data by visualization-software AVS. \\\\ 
    646 This file describes the structure of the file PLOT3D_COOR (e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format. It also contains the name of the file (inclusive cycle number, but without path) into which the local file PLOT3D_COOR (this is the file name described in the file connection statement of the MRUN - configuration file) is output in the permanent directory of the user (possibly on remote computers). Under this name AVS expects the data which are to be visualized. If there is no file connection statement for PLOT3D_COOR indicated in the configuration file, that file is registered as "unknown" in the file PLOT3D_FLD_COOR and the actual name must be inserted later by hand. \\\\
    647 AVS expects the information contained in the file PLOT3D_FLD_COOR, as well as the remaining information about the three-dimensional arrays output by the model (see [#PLOT3D_FLD PLOT3D_FLD]) in one and the same file. This is satisfied by appending the file PLOT3D_FLD_COOR after the end of a run are to the file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the MRUN-configuration file: "cat PLOT3D_FLD_COOR >> PLOT3D_FLD"). \\\\
     646This file describes the structure of the file PLOT3D_COOR (e.g. grid spacing, data type etc.) using the so-called AVS-Fld-format. It also contains the name of the file (inclusive cycle number, but without path) into which the local file PLOT3D_COOR (this is the file name described in the file connection statement of the '''mrun'''-configuration file) is output in the permanent directory of the user (possibly on remote computers). Under this name AVS expects the data which are to be visualized. If there is no file connection statement for PLOT3D_COOR indicated in the configuration file, that file is registered as "unknown" in the file PLOT3D_FLD_COOR and the actual name must be inserted later by hand. \\\\
     647AVS expects the information contained in the file PLOT3D_FLD_COOR, as well as the remaining information about the three-dimensional arrays output by the model (see [#PLOT3D_FLD PLOT3D_FLD]) in one and the same file. This is satisfied by appending the file PLOT3D_FLD_COOR after the end of a run are to the file PLOT3D_FLD (e.g. with an appropriate OUTPUT-command in the '''mrun'''-configuration file: "cat PLOT3D_FLD_COOR >> PLOT3D_FLD"). \\\\
    648648For parallel runs, PLOT3D_FLD_COOR is written by PE0 only.
    649649}}}
    … …  
    738738* individual data must be separated by at least one blank. \\
    739739Layout sketch: \\
    740 {{{#!table style="border:none"
    741 {{{#!td style="vertical-align:top;border:none;width:20px"
    742 }}}
    743 {{{#!td style="vertical-align:top;border:none;width:20px"
    744 }}}
    745 {{{#!td style="vertical-align:top;border:none;width:20px"
    746 }}}
    747 {{{#!td style="vertical-align:top;border:none;width:20px"
    748 N
    749 }}}
    750 {{{#!td style="vertical-align:top;border:none;width:20px"
    751 }}}
    752 {{{#!td style="vertical-align:top;border:none;width:20px"
    753 }}}
    754 {{{#!td style="vertical-align:top;border:none;width:20px"
    755 }}}
    756 {{{#!td style="vertical-align:top;border:none;width:20px"
    757 }}}
    758 |------
    759 {{{#!td style="vertical-align:top;border:none;width:30px"
    760 }}}
    761 {{{#!td style="vertical-align:top;border:none;width:30px"
    762 (0,ny)
    763 }}}
    764 {{{#!td style="vertical-align:top;border:none;width:30px"
    765 (1,ny)
    766 }}}
    767 {{{#!td style="vertical-align:top;border:none;width:30px"
    768 (2,ny)
    769 }}}
    770 {{{#!td style="vertical-align:top;border:none;width:30px"
    771 ...
    772 }}}
    773 {{{#!td style="vertical-align:top;border:none;width:30px"
    774 (nx,ny)
    775 }}}
    776 {{{#!td style="vertical-align:top;border:none;width:30px"
    777 }}}
    778 {{{#!td style="vertical-align:top;border:none;width:80px"
    779 top of file
    780 }}}
    781 |------
    782 {{{#!td style="vertical-align:top;border:none;width:30px"
    783 }}}
    784 {{{#!td style="vertical-align:top;border:none;width:30px"
    785 (0,ny-1)
    786 }}}
    787 {{{#!td style="vertical-align:top;border:none;width:30px"
    788 (1,ny-1)
    789 }}}
    790 {{{#!td style="vertical-align:top;border:none;width:30px"
    791 (2,ny-1)
    792 }}}
    793 {{{#!td style="vertical-align:top;border:none;width:30px"
    794 ...
    795 }}}
    796 {{{#!td style="vertical-align:top;border:none;width:30px"
    797 (nx,ny-1)
    798 }}}
    799 {{{#!td style="vertical-align:top;border:none;width:30px"
    800 }}}
    801 {{{#!td style="vertical-align:top;border:none;width:30px"
    802 }}}
    803 |------
    804 {{{#!td style="vertical-align:top;border:none;width:20px"
    805 W
    806 }}}
    807 {{{#!td style="vertical-align:top;border:none;width:20px"
    808 (0,ny-2)
    809 }}}
    810 {{{#!td style="vertical-align:top;border:none;width:20px"
    811 (1,ny-2)
    812 }}}
    813 {{{#!td style="vertical-align:top;border:none;width:20px"
    814 (2,ny-2)
    815 }}}
    816 {{{#!td style="vertical-align:top;border:none;width:20px"
    817 ...
    818 }}}
    819 {{{#!td style="vertical-align:top;border:none;width:20px"
    820 (nx,ny-2)
    821 }}}
    822 {{{#!td style="vertical-align:top;border:none;width:20px"
    823 E
    824 }}}
    825 {{{#!td style="vertical-align:top;border:none;width:20px"
    826 }}}
    827 |------
    828 {{{#!td style="vertical-align:top;border:none;width:20px"
    829 }}}
    830 {{{#!td style="vertical-align:top;border:none;width:20px"
    831 }}}
    832 {{{#!td style="vertical-align:top;border:none;width:20px"
    833 }}}
    834 {{{#!td style="vertical-align:top;border:none;width:20px"
    835 :
    836 }}}
    837 {{{#!td style="vertical-align:top;border:none;width:20px"
    838 }}}
    839 {{{#!td style="vertical-align:top;border:none;width:20px"
    840 }}}
    841 {{{#!td style="vertical-align:top;border:none;width:20px"
    842 }}}
    843 {{{#!td style="vertical-align:top;border:none;width:20px"
    844 }}}
    845 |------
    846 {{{#!td style="vertical-align:top;border:none;width:20px"
    847 }}}
    848 {{{#!td style="vertical-align:top;border:none;width:20px"
    849 (0,0)
    850 }}}
    851 {{{#!td style="vertical-align:top;border:none;width:20px"
    852 (1,0)
    853 }}}
    854 {{{#!td style="vertical-align:top;border:none;width:20px"
    855 (2,0)
    856 }}}
    857 {{{#!td style="vertical-align:top;border:none;width:20px"
    858 ...
    859 }}}
    860 {{{#!td style="vertical-align:top;border:none;width:20px"
    861 (nx,0)
    862 }}}
    863 {{{#!td style="vertical-align:top;border:none;width:20px"
    864 }}}
    865 {{{#!td style="vertical-align:top;border:none;width:90px"
    866 bottom of file
    867 }}}
    868 |------
    869 {{{#!td style="vertical-align:top;border:none;width:20px"
    870 }}}
    871 {{{#!td style="vertical-align:top;border:none;width:20px"
    872 }}}
    873 {{{#!td style="vertical-align:top;border:none;width:20px"
    874 }}}
    875 {{{#!td style="vertical-align:top;border:none;width:20px"
    876 S
    877 }}}
    878 {{{#!td style="vertical-align:top;border:none;width:20px"
    879 }}}
    880 {{{#!td style="vertical-align:top;border:none;width:20px"
    881 }}}
    882 {{{#!td style="vertical-align:top;border:none;width:20px"
    883 }}}
    884 {{{#!td style="vertical-align:top;border:none;width:20px"
    885 }}}
    886 }}}
    887                         N \\
    888     (0,ny)   (1,ny)   (2,ny)   ... (nx,ny)       top of file \\
    889     (0,ny-1) (1,ny-1) (2,ny-1) ... (nx,ny-1)  \\
    890 W   (0,ny-2) (1,ny-2) (2,ny-2) ... (nx,ny-2)   E \\
    891                         : \\
    892                         : \\
    893     (0,0)    (1,0)    (2,0)    ... (nx,0)        bottom of file \\
    894                         S \\
    895 |----------------
     740{{{
     741                        N
     742    (0,ny)   (1,ny)   (2,ny)   ... (nx,ny)       top of file
     743    (0,ny-1) (1,ny-1) (2,ny-1) ... (nx,ny-1) 
     744W   (0,ny-2) (1,ny-2) (2,ny-2) ... (nx,ny-2)   E
     745                        :
     746                        :
     747    (0,0)    (1,0)    (2,0)    ... (nx,0)        bottom of file
     748                        S
     749}}}
     750|----------------
                                                                                                                                                                                                                                                                                                                                                                               
  | Impressum | ©Leibniz Universität Hannover |