XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''"> 9.5 VFDIAG (Diagnostic Data)
Introduction
This file contains the diagnostic data for the viewfactors which were just calculated. It is identified by the $DIAGNOSTIC_FILE: keyword in the Viewfactor command file. Its default name is VFDIAG. This file is currently a sequential, formatted (ascii) file.
The file contains comments, keyword lines, and numeric data.
Comments are blank lines or lines where the first nonblank character is *. Comments may not immediately precede or be interspersed with numeric data. Comments may immediately precede any keyword line.
Keyword lines consist of a keyword which may be followed by data as described in more detail below. All keyword lines are required and must be in the order shown. The number of occurrences permitted for different keywords is described in more detail below.
The valid keywords and order are:
$TITLE:
$ENCL:
$ENDENCL:
$EOF:
Leading blanks may precede comments and keywords. Comments and keyword lines are read by a FORTRAN '( A )' format into a buffer 132 characters long. Thus, comments and keyword lines (including leading blanks) should not exceed 132 characters.
Numeric data is associated with keywords and may occur on the keyword line or on line(s) immediately following the keyword line. Note that comments are not permitted immediately preceding or interspersed with numeric data. Numeric data is in fixed format which will be described in detail (see
Examples, 146).
Examples
Here are two examples of model diagnostic files:
Detailed Descriptions
$TITLE
The first noncomment line must be:
$TITLE: title
Multiple $TITLE: lines are allowed, but they must all occur before the $ENCL: line. Comments between multiple $TITLE: lines are allowed.
$ENCL and $ENDENCL
The next keyword line is:
with format blanks, A10, 3I10.
Parameter | Description |
EnclID | The ID number of this enclosure |
#Surf | Number of surfaces in this enclosure, |
SymMul | Number of symmetric images of each surface. |
Immediately following, and with no interspersed comments, is the surface data for the #Surf surfaces. A fatal error will occur if the #Surf and the number of surface data do not match. The format and meaning of the surface data is:
( 1X, I10, 3E19.10 ) SURID, SUMSUR, SUMONE, SUMZRO
( 1X, 4E19.10 ) ( SUMNOD( I ), J = 1, NNODE ).
Parameter | Description |
SURID | Surface ID; |
SUMSUR | Sum of the viewfactors from this surface to all other surfaces in this enclosure; |
SUMONE | 1.0 - SUMSUR; |
SUMZRO | Sum of the viewfactors from this surface to all other surfaces in this enclosure which were set to zero by virtue of being less than the zero cutoff value; |
SUMNOD | Sum of the viewfactors from each nodal subarea on this surface to all other nodal subarea on all other surfaces in this enclosure; |
J | Index to the nodal subareas on this surface; |
NNODE | Number of nodes on this surface. |
This pattern is repeated for each surface in the enclosure. After this data has been given for all surfaces in the enclosure, some additional statistical data for the enclosure is given. The format and meaning of the statistical data is:
( 1X, 5E15.7 ) ( MX( J ), AV( J ), SD( J ), AB( J ), ASD( J ) ), J = 0, MXND )
Parameter | Description |
MX | Maximum absolute deviation from unity for the sums of viewfactors; |
AV | Average deviation from unity for the sums of viewfactors; |
SD | Standard deviation of the data used to calculate AV; |
AB | Average absolute deviation from unity for the sums of viewfactors; |
ASD | Standard deviation of the data used to calculate AB; |
J | Index, 0 = entire surface, 1 through MXND = nodal subareas; |
MXND | Maximum number of nodes on any surface in this enclosure. |
The next keyword line is $ENDENCL: with no data.
The pattern:
is repeated for any additional enclosures.
$EOF
The last keyword line is $EOF: with no data. Comments may follow the $EOF: line.
