Changes between Version 19 and Version 20 of doc/app/iofiles


Ignore:
Timestamp:
Sep 14, 2010 9:54:11 AM (15 years ago)
Author:
fricke
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • doc/app/iofiles

    v19 v20  
    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. \\\\
    625625This 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. \\\\
    626 AVS-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 }}}
    628 |----------------
     626AVS-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. \\\\
     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"). \\\\
     628For parallel runs, PLOT3D_FLD is produced by PE0 only.
     629}}}
     630|----------------
     631{{{#!td style="vertical-align:top; width: 50px"
     63233
     633}}}
     634{{{#!td style="vertical-align:top; width: 150px"
     635[=#PLOT3D_FLD_COOR PLOT3D_FLD_COOR]
     636}}}
     637{{{#!td style="vertical-align:top; width: 50px"
     638O
     639}}}
     640{{{#!td style="vertical-align:top; width: 100px"
     641ASCII/ \\
     642AVS-Fld
     643}}}
     644{{{#!td
     645File 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. \\\\ 
     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"). \\\\
     648For parallel runs, PLOT3D_FLD_COOR is written by PE0 only.
     649}}}
     650|----------------