XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''"> 5.1 Submitting a Viewfactor Job for Analysis
Submitting a Viewfactor job for execution is very simple. Viewfactor analyses take a lot of computer time and real time. Therefore, it is recommended that the model and the VFCTL file be carefully reviewed to double check that the correct data files are present. This will protect you from submitting an analysis with the wrong data and from abnormal execution due to user error.
Review the Viewfactor Control/Parameters
You should review the Viewfactor Solution Parameters in the Analysis form or the VFCTL file being used for this analysis asking the following questions:
1. Is the path name correct?
2. Do all of the input data files exist in the correct directory or will they be automatically created based on the submit options?
3. Are these input data files the correct files for the problem to be analyzed?
The following parameters are described in
Keywords in the VFCTL File, 88:
1. Does the run control parameter, $RUN_CONTROL:, specify the desired execution sequence?
2. Is the convergence criteria parameter, $CONVERGE:, correct?
3. Is the zero cutoff parameter, $ZERO:, correct?
4. Is the curve approximation parameter, $APPROX_CURVE:, correct?
5. Are the maximum integration order parameters, $GAUSS_ORDER:, correct for
contour integration,
double area integration, and
finite element weighting?
6. Are the axisymmetric surface subdivision parameters, $AXISYM_SURFACE:, correct for the
minimum number of subdivisions and
maximum number of subdivisions?
Review Directory for Required Files
Generally, a Viewfactor analysis will not get very far if the required files are not available. This is a problem if you submit a Viewfactor analysis, go to lunch, and expect to see results later. You may wish to double check that the input data files are actually the correct and desired files for the model you are analyzing.
The specific files and filenames required depend on the value of the run control parameter and the filenames given in the VFCTL file. The generic file names for the various values of the run control parameter are given below:
$RUN_CONTROL: 0
The following files are required:
VFINDAT
TEMPLATEDAT
The following files are created:
VFRESTARTSTAT
VFRESTARTDAT
VFRAWDAT
VFRESDAT
VFNODEDAT
VFDIAG
VFMSG
$RUN_CONTROL: 1
The following file is required:
VFINDAT
The following files are created:
VFRESTARTSTAT
VFRESTARTDAT
VFRAWDAT
VFDIAG
VFMSG
$RUN_CONTROL: 2
The following files are required:
VFRAWDAT
TEMPLATEDAT
The following files are created:
VFRESTARTSTAT
VFRESTARTDAT
VFRESDAT
VFNODEDAT
VFDIAG
VFMSG
Note: | The above files will be automatically created if execution is spawned from within the Patran analysis menu. |
The Viewfactor Command Line
This section uses examples from a VAX specific installation. Your system may require different commands. Refer to the
Introduction & Overview (Ch. 1) in the Patran Installation and Operations Guide or your system manager.
A Viewfactor analysis is submitted by typing at your computer command prompt the command VSUBMIT followed optionally by the VFCTL filename. The filename must be separated from the command by a comma and/or one or more blank spaces. If no VFCTL file name is given, it will default to VFCTL in the default directory. VSUBMIT may be abbreviated as VSU.
Examples: | Let $ be the computer system level prompt. Commands are entered by pressing the RETURN key. |
$VSUBMIT | Submits a Viewfactor analysis with the VFCTL file from the default directory. |
$VSU VFCTL_TEST_RUN | Submits a Viewfactor analysis with the control file VFCTL_TEST_RUN from the default directory. |
$VSU [SMITH.VF.FILES]VFCONTROL.CON | Submits a Viewfactor analysis with the control file VFCONTROL.CON from the directory [PHILLIPS.VF.FILES] on the default disk. The actual analysis will be run as a batch or background job and you will receive mail or other notification when the job has terminated. You may also run Viewfactor in interactive mode by using the command VF_RUN instead of VSUBMIT. |
Note: | A Viewfactor Submit script is automatically created if execution is spawned from within Patran analysis menu. |