Professional Documents
Culture Documents
Main Index
Corporate Europe Asia Pacific
MSC.Software Corporation MSC.Software GmbH MSC.Software Japan Ltd.
2 MacArthur Place Am Moosfeld 13 Shinjuku First West 8F
Santa Ana, CA 92707 USA 81829 Munich, Germany 23-7 Nishi Shinjuku
Telephone: (800) 345-2078 Telephone: (49) (89) 43 19 87 0 1-Chome, Shinjuku-Ku
Fax: (714) 784-4056 Fax: (49) (89) 43 61 71 6 Tokyo 160-0023, JAPAN
Telephone: (81) (3)-6911-1200
Fax: (81) (3)-6911-1201
Worldwide Web
www.mscsoftware.com
Disclaimer
This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with
the terms of such license.
MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not
intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no
liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information
contained herein.
User Documentation: Copyright ©2008 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or distribution of this
document, in whole or in part, without the prior written consent of MSC.Software Corporation is prohibited.
The software described herein may contain certain third-party software that is protected by copyright and licensed from
MSC.Software suppliers. Contains IBM XL Fortran for AIX V8.1, Runtime Modules, (c) Copyright IBM Corporation 1990-2002,
All Rights Reserved.
MSC, MSC/, MSC Nastran, MD Nastran, MSC Fatigue, Marc, Patran, Dytran, and Laminate Modeler are trademarks or registered
trademarks of MSC.Software Corporation in the United States and/or other countries.
NASTRAN is a registered trademark of NASA. PAM-CRASH is a trademark or registered trademark of ESI Group. SAMCEF is
a trademark or registered trademark of Samtech SA. LS-DYNA is a trademark or registered trademark of Livermore Software
Technology Corporation. ANSYS is a registered trademark of SAS IP, Inc., a wholly owned subsidiary of ANSYS Inc. ACIS is a
registered trademark of Spatial Technology, Inc. ABAQUS, and CATIA are registered trademark of Dassault Systemes, SA.
EUCLID is a registered trademark of Matra Datavision Corporation. FLEXlm is a registered trademark of Macrovision
Corporation. HPGL is a trademark of Hewlett Packard. PostScript is a registered trademark of Adobe Systems, Inc. PTC, CADDS
and Pro/ENGINEER are trademarks or registered trademarks of Parametric Technology Corporation or its subsidiaries in the
United States and/or other countries. Unigraphics, Parasolid and I-DEAS are registered trademarks of UGS Corp. a Siemens
Group Company. All other brand names, product names or trademarks belong to their respective owners.
P3:V2008R1:Z:VWFTR:Z:DC-USR-PDF
Main Index
Contents
Viewfactor Analysis
1 Introduction
About the Viewfactor Program 2
Features and Benefits 3
Guide Organization 7
Nomenclature 9
Conventions 9
Font Types and Typefaces 9
Filenames 9
Units 9
2 Overview
Purpose 12
Main Index
ii Viewfactor Analysis
==
Specifying Radiation Boundary Conditions Using Patran Reference Manual (VFAC Boundary
Condition) 38
Purpose of the Viewfactor Form 38
Form for the VFAC LBC 38
Input Data for the Viewfactor Form 38
Requirement for Oriented 2-D Surfaces Related to the VFAC LBC 40
Neutral File Data Packet Created from the VFAC LBC 40
Advanced Features of the VFAC Boundary Condition 42
Referencing Participating Media Radiation Nodes 42
Role of Radiation Participating Media in Patran Thermal 42
Participating Media Resistor Networks 42
Defining the Participating Media Node 44
Referencing Ambient or Space Radiation Nodes 44
Role of Ambient Radiation Nodes 44
Suggested Practices to Improve Model Accuracy 44
Ambient Node Resistor Networks in Patran Thermal 45
Defining the Ambient Node 46
Identifying a Surface as Being Convex 47
Significance of Convex Surfaces to Viewfactor Calculations 47
Benefits of Identifying Convex Surfaces to Viewfactor Execution Time 47
Caveats Regarding Convex Surfaces in Axisymmetric Models 48
Identifying a Surface as Not Obstructing the View Between Other Surface Pairs 49
Benefits of Identifying Nonobstructing Surfaces to Viewfactor Execution Time 49
Examples with Nonobstructing Surfaces Identified 49
Caveats Regarding Nonobstructing Surfaces in Axisymmetric Models 49
Relationship of VFAC LBC Data to VFINDAT File Data 51
Main Index
CONTENTS iii
PATQ Translation from the Patran Neutral File to the VFINDAT File 80
Spawning From Patran vs. Stand-Alone Execution 80
Step-by-Step Procedure (Stand-Alone Execution) 80
5 Analysis
Submitting a Viewfactor Job for Analysis 98
Review the Viewfactor Control/Parameters 98
Review Directory for Required Files 98
$RUN_CONTROL: 0 98
$RUN_CONTROL: 1 99
$RUN_CONTROL: 2 99
The Viewfactor Command Line 99
Output Created by a Viewfactor Execution 101
Main Index
iv Viewfactor Analysis
==
VFMSG 101
VFDIAG 101
VFRAWDAT 102
VFRESDAT 102
VFNODEDAT 102
6 Post-Analysis
Introduction 110
Viewfactor 125
Obstructions 128
Main Index
CONTENTS v
Main Index
vi Viewfactor Analysis
==
Main Index
Chapter 1: Introduction
Patran Viewfactor Analysis
Introduction
1
About the Viewfactor Program 2
Features and Benefits 3
About this Guide 5
Using this Guide 6
Guide Organization 7
Overview of Viewfactor Analysis 8
Nomenclature 9
Main Index
2 Patran Viewfactor Analysis
About the Viewfactor Program
Main Index
Chapter 1: Introduction 3
Features and Benefits
These elements faces represent all of the elements faces usually needed to model thermally radiating surfaces.
Viewfactor provides support for multiple symmetries in the model. For 3-D geometries, Viewfactor provides support for
reflection across a plane and rotation of “n” times by “x” degrees about an arbitrary axis. For 2-D XY geometries, it
provides for reflections across a line in the XY plane and rotation of “n” times by “x” degrees about an arbitrary axis
perpendicular to the XY plane. For 2-D axisymmetric geometries, it provides for reflections across a line perpendicular
to the Z-axis and in the RZ plane. Four separate symmetry objects and symmetry operations may be combined in the
same model. Viewfactor does not check for the validity of any symmetry operations. These symmetry operators provide
a convenient way to deal with thermal models which are symmetric in all respects except for the radiation component of
the problem.
Viewfactor is closely coupled with Patran and Patran Thermal and is specifically designed to work well with them. Patran
is responsible for the generation of the thermal model and boundary conditions. The Patran Thermal PATQ interface
program handles all data translation between the Patran neutral file and the Viewfactor input file. Viewfactor reads the
input file and the Patran Thermal template file and then generates a file containing radiation resistors for QTRAN
analysis processing.
Viewfactor provides support for all of the commonly used model coordinate systems. These are 2-D XY, 2-D RZ
axisymmetric, and 3-D XYZ coordinate frames.
Coupled with the capabilities in the Patran Thermal module Viewfactor provides support for time and temperature-
dependent material properties such as surface emissivities and participating media transmissivities.
Viewfactor provides for efficient obstruction checking at the element level.
Multiple enclosures are modeled in both Viewfactor and Patran Thermal. This feature, along with the multiple
wavebands for spectral surfaces, allows for the modeling of phenomenon such as partially transmitting windows.
No fixed problem size limit exists for Viewfactor. Memory for the particular model being analyzed is allocated during
run time. Problem size is limited only by available virtual memory, available CPU resources, and storage space for the
output data. Core memory requirements are linear functions of the model size, not higher order functions as is true for
some viewfactor analysis programs.
Through use of the Patran Thermal template file, Viewfactor provides support for optically thin participating media.
The geometric calculations involved in determining obstructions and viewfactors are saved as an intermediate result and
can be reused with different material properties in the same model. These CPU intensive calculations need not be
repeated when material properties change.
Viewfactor checks for convergence of its numerical integration algorithms and increases or decreases the integration
order as appropriate. This provides excellent performance as measured by the product of accuracy and speed.
Diagnostic data is provided to aid in verifying the accuracy of an analysis.
Viewfactor provides support for radiation to an ambient or space environment node.
Convex surfaces may be flagged to help reduce execution time.
Main Index
4 Patran Viewfactor Analysis
Features and Benefits
Nonobstructing surfaces may be flagged in order to reduce the time required to check for obstructed views.
Main Index
Chapter 1: Introduction 5
About this Guide
Main Index
6 Patran Viewfactor Analysis
Using this Guide
Main Index
Chapter 1: Introduction 7
Guide Organization
In addition, there are appendices at the end of the document which provide supplemental information on a number of
topics. The Guide also has a comprehensive index to aid the reader in locating information on particular topics.
Main Index
8 Patran Viewfactor Analysis
Overview of Viewfactor Analysis
Chapters 3-7 - The Analysis Cycle, deal with the details of thermal analysis as it relates to the thermal radiation boundary
condition and its subsequent modeling and analysis using P⁄THERMAL,and Patran. Other aspects of the analysis cycle,
such as general model creation, other thermal boundary conditions, material properties, thermal network analysis, and
thermal results postprocessing, are described in more detail in Volume 1 of the MSC Patran Thermal User’s Guide and the
Patran Reference Manual. Please refer to these other documents for information relating to those parts of the thermal
analysis cycle not pertaining directly to the thermal radiation boundary condition. Unfortunately, the analysis of complex
thermal phenomena is itself complex. The software described here was designed to model complex phenomena, such as
temperature and/or time dependent emissivities and transmissivities. Therefore, the analysis cycle is more complex than
it would be if only simple phenomena were being modeled. This complexity is the price for the richness of the thermal
modeling and highly nonlinear system solution capabilities available in this software. This complexity will not go away.
For the analyst wishing to model the simpler phenomena, the complexity generally reduces to simple steps in the analysis
cycle. With this in mind, it is advisable to obtain a thorough understanding of the cycle presented here and then become
proficient at using the parts applicable to your thermal analysis needs.
Chapters 8-10 - Theory and Specifications, deal with the following topics:
• Formulae and methods used to compute the radiation viewfactors.
• Computational limitations brought on by the finite precision of computers.
• Rules governing the generation of Patran Thermal radiation resistors.
• Format specifications for the data files (VFINDAT, VFRAWDAT, VFRESDAT, TEMPLATEDAT, VFDIAG, and
VFNODEDAT).
Generally, this information will only be needed by the engineer concerned with the limitations of the computer algorithms
and who wishes to obtain a more complete understanding of what is being done in the program, or wishes to interface the
Viewfactor data files to other software. MSC.Software Corporation does not guarantee that the data file formats will
remain unchanged.
Appendices - Examples, Appendix E contains examples of thermal radiation analysis problems presented as complete
analysis cycles. These examples were designed to present the important features and capabilities of the Viewfactor code,
as well as some of the advanced features of Patran Thermal as they pertain to analysis of thermal radiation problems. The
problems are generally simple in other aspects and thus are easy to model and not too time-consuming. Once you have
gained sufficient understanding of the analysis cycle, a quick review of the example problems will refresh your memory
after you’ve been away from this software for a period of time. Some of the examples were also designed to demonstrate
the correctness of the thermal analysis and to build confidence in the use of the Viewfactor code.
Other topics covered in the appendices are error conditions, memory requirements, and technical support.
Main Index
Chapter 1: Introduction 9
Nomenclature
1.7 Nomenclature
Certain documentation conventions (such as different typefaces having meaning), special characters with specific
meaning (such as slashes in Patran commands), technical definitions, and symbols used in this document are defined or
described in this section.
Conventions
Font Types and Typefaces
Computer messages or responses are printed in plain character format:
SYSTEM RESPONSES ARE IN A PLAIN LETTER STYLE
Commands (or queries) that you enter are printed in bold typeface which is darker and heavier than normal or plain text:
commands entered by the user are in bold type
Some fields, or parts of a surface, may be optional. Fields contained within brackets [ ] are optional for data input.
Generally, optional data fields that do not receive input will default to a predetermined value.
VFAC,TID[,NBANDS]
Filenames
A generic file naming convention is used in this guide. This reduces confusion for users on the various computer
platforms and operating systems supported by MSC.Software Corporation.
Generic file names contain no delimiters. A file referred to as “filenameELS” in this Guide would appear as
“filename.ELS” for VAX, Apollo, Celerity, Hewlett-Packard, Data General, SGI, Prime and Cray. It would appear
as “filename ELS” for the IBM VM/CMS, and as “filename_ELS” for the CDC NOS/VE.
Units
As you are proceeding with your modeling tasks in Patran and Patran Thermal, remember that they are unit-less or
dimensionless. That is to say they will accept as input any number and it is your responsibility to make sure that the units
you are using are consistent. Typically, the type of units to be used is defined or locked in when you choose your material
properties. These units for your material properties must be consistent with the other dimensioned quantities within the
model, such as length.
Main Index
10 Patran Viewfactor Analysis
Nomenclature
Main Index
Chapter 2: Overview
Patran Viewfactor Analysis
Overview
2
Purpose 12
Relationship of Viewfactor to Patran and Patran Thermal 13
Viewfactor Data and Program Flow 16
Summary of the Analysis Cycle for a Thermal Radiation Problem 20
Main Index
12 Patran Viewfactor Analysis
Purpose
2.1 Purpose
This chapter provides an overview of performing a Viewfactor analysis. It describes how the Viewfactor code is related to
the other Patran products (Patran and Volume 1 of Patran Thermal) showing the high level data and program flow in
Viewfactor. It summarizes the typical analysis cycle for a thermal radiation problem using Patran.
Main Index
Chapter 2: Overview 13
Relationship of Viewfactor to Patran and Patran Thermal
Description
The relationship of the Viewfactor code to Patran and Patran Thermal is shown schematically in Figure 2-1. Patran
Thermal’s PATQ takes the geometric and boundary condition data from a Patran neutral file and converts it to data about
the thermally radiating surfaces. The data is then output to the VFINDAT file. The TEMPLATEDAT file is the Patran
Thermal template file, with the addition of a new template, called VFAC (Viewfactor). The template data is necessary
Main Index
14 Patran Viewfactor Analysis
Relationship of Viewfactor to Patran and Patran Thermal
for Viewfactor to make thermal network resistors for Patran Thermal. The Viewfactor run is a noninteractive process
whose execution is controlled by data in the VFCTL file.
USER INPUT
Patran
CREATE DISPLAY
MODEL RESULTS
Patran Thermal
VFRESTXT PATQ QTRAN
OTHER
THERMAL
FILES
TEMPLATEDAT VFRESDAT
VFINDAT
VFNODEDAT
VFCTL
Viewfactor
Calculate Make
Viewfactors Resistors
VFRAWDAT
VFDIAG VFMSG
Main Index
Chapter 2: Overview 15
Relationship of Viewfactor to Patran and Patran Thermal
be input by Patran Thermal and used in the thermal analysis of the problem. The results of the thermal analysis are output
by Patran Thermal in the file QOUTDAT and nodal results files. These files may be displayed along with the geometric
model using the postprocessing capabilities of Patran.
There are several other files shown in Figure 2-1 which we have not yet discussed. These are VFRESTXT, VFDIAG, and
VFMSG. These files do not participate in the computer analysis of the problem. They are provided to assist you in
determining that the problem is correctly modeled and the analysis has been correctly performed. In the event you have
an error, they will be helpful in finding and correcting it.
VFRESTXT is a text version of VFRESDAT. Since VFRESDAT is stored in binary form, it cannot be read by most
computer file editors. The capability to translate the binary VFRESDAT file into a text file, VFRESTXT, is provided in
Patran Thermal’s PATQ. You may then examine the thermal network resistors generated by Viewfactor using the text
editor of your choice. VFRESDAT files tend to be large and are best implemented in binary form, which is more compact
than text form. You will find, in most cases, that the VFRESTXT file is too large to be examined in detail.
The files VFDIAG and VFMSG contain information useful in evaluating a Viewfactor execution. VFMSG
predominately contains text information concerning the progress of the Viewfactor program execution and reports of any
errors which were detected. You are strongly advised to examine the VFMSG file for error messages, since this is the
only way to know if errors occurred. The VFDIAG file contains predominately numerical data relating to the sums of
viewfactors to each surface. This data can often be compared to expected values for the sums of viewfactors and thus
used to judge the correctness of the viewfactor analysis.
Main Index
16 Patran Viewfactor Analysis
Viewfactor Data and Program Flow
Description
Figure 2-2 shows a high level abstraction of the program structure contained in Viewfactor. The program functions are
described in outline form, with the level of indentation representing the level of nesting in the program. Data files are
shown in ovals with arrows to the general portion of the program where the data is input or output. The file VFMSG
receives output throughout the program execution and thus does not have an arrow from a specific portion of the program.
Main Index
Chapter 2: Overview 17
Viewfactor Data and Program Flow
Figure 2-2 High Level Data and Program Flow for Viewfactor
The execution of Viewfactor is controlled by parameters in the control file VFCTL. These parameters serve three general
purposes:
1. Set program parameters, such as the value of the parameter used for convergence checking.
Main Index
18 Patran Viewfactor Analysis
Viewfactor Data and Program Flow
2. Specify file names other than the default names for the data files.
3. Control which parts of the Viewfactor program are executed and subsequently which input data files are required
and which output data files are created.
The third function of program control is described here. All of these functions are described in more detail in Viewfactor
Execution From Patran Thermal, 79.
Referring to Figure 2-2, you should be able to identify the following program parts:
Part I Initialize.
Part II Calculate Viewfactors.
Part III Make Patran Thermal Resistors.
Part IV Exit from the Viewfactor program structure.
Parts I and IV are always executed. Through the use of a parameter in the VFCONTROL file you may cause any one of
three execution modes to occur.
MODE 1 In the first mode, all of the Parts I through IV are executed. The required data input is a VFCTL file, a
VFINDAT file, and a TEMPLATEDAT file. The output produced is a VFRESDAT file, a VFNODEDAT file,
a VFRAWDAT file, a VFDIAG file, and a VFMSG file. This mode takes in the geometric description of the
radiating surfaces and their Patran Thermal surface template data and creates as output resistor network data
for Patran Thermal. Also created as output for possible later use (see the description of the third mode below)
is the raw viewfactor data. Diagnostic data is also output.
Main Index
Chapter 2: Overview 19
Viewfactor Data and Program Flow
MODE 2 In the second mode, only Parts I, II, and IV are executed. Part III (Make Patran Thermal Resistors) is not
executed and thus no thermal network data is generated. The TEMPLATEDAT file is not required for this
mode, although no harm will be caused by its presence. The required data input is a VFCTL file and a
VFINDAT file. The output produced is a raw viewfactor file, VFRAWDAT, and the diagnostic files VFDIAG
and VFMSG. The VFRAWDAT file produced here may be used in the third mode described in the next
paragraph. The second mode is useful if you only want to generate viewfactor data and do not care about the
Patran Thermal network resistors. It is also useful if you do not yet have the TEMPLATEDAT file describing
the surface properties and wish to begin the viewfactor calculations. You must take care to make sure that the
thermal radiation problem described in the VFINDAT file and the property data identified in the yet to be
created TEMPLATEDAT file are compatible. This is described in more detail in Compatibility Requirements
for Model and VFAC Templates, 65 and Introduction, 120. The intermediate file VFRAWDAT and the
TEMPLATEDAT file may be combined to make the thermal network resistors at some later time by using the
third mode.
MODE 3 In the third mode, only Parts I, III, and IV are executed. Part II, (Calculate Viewfactors) is not executed and
thus there must already be in existence and available to the program a data file of raw viewfactor data,
VFRAWDAT. This mode also requires a TEMPLATEDAT file of surface data for the Patran Thermal resistors
that will be created. The VFCTL file is also input in this mode. The output created here is the thermal resistor
network for the radiating surfaces, contained in the files VFRESDAT and VFNODEDAT, and the diagnostic
data contained in the files VFDIAG and VFMSG.
This third mode allows you to change the surface property definition by changing the information contained in
the TEMPLATEDAT file. Then run this mode of the Viewfactor program again. Note that in this way you may
generate a new and different thermal resistor network simply by changing the TEMPLATEDAT file. You do
not have to rerun the computationally expensive viewfactor calculations which were already performed in the
first or second modes described above. This provides great savings of computer time in cases where the
geometry does not change, but you wish to run two or more thermal analyses using different radiative surface
properties. It is also useful for performing initial analysis using simpler material properties (e.g., constant
properties). Once the analyst is satisfied that the problem is correctly modeled, the material properties may be
changed to more closely represent reality (e.g., temperature dependent properties). By submitting simpler,
computationally faster models for preliminary analysis the analyst can optimize the use of available computer
resources and improve overall performance.
When using this mode you must take special care to define the radiating surfaces in such a way that they are
capable of supporting all of the various material property definitions you plan to attach to each surface in the
future. This method is described in more detail in Patran Thermal TEMPLATEDAT Files for Surface Property
Description, 52 and Introduction, 120.
Main Index
20 Patran Viewfactor Analysis
Summary of the Analysis Cycle for a Thermal Radiation Problem
Problem Definition
The first step is to define the problem. This includes identifying the geometry, boundary conditions, materials, material
properties and approximations to be used in the analysis. You may find it useful and efficient to outline the entire analysis
procedure as it pertains to the problem at hand. This should help avoid unpleasant surprises later on. It also ensures that
all the steps in a complex process are followed.
General Preprocessing
This step involves creating or inputting the geometric model, creating a finite element mesh on the model, and assigning
boundary conditions and material identifications, in Patran. This step requires close coordination with the next step,
General Patran Thermal Preparation, so that the boundary conditions and material properties identified in Patran
correspond to material definitions and boundary conditions in the supporting Patran Thermal files. These activities and
entities are described more fully in the MSC Patran Thermal User’s Guide. Planning at this stage of the analysis is
important if you wish to be able to easily change boundary conditions and/or material property definitions in the future.
Main Index
Chapter 2: Overview 21
Summary of the Analysis Cycle for a Thermal Radiation Problem
Note: The VFCTL file is automatically created when the analysis is submitted from the Analysis form in Patran.
Viewfactor Analysis
Viewfactor will usually be executed as a noninteractive batch process. Merely invoke the command procedure to submit
Viewfactor and its control file, VFCTL, for execution, or select “Execute Viewfactor Analysis” in the Analysis / Submit
Options form.
Since Viewfactor analysis tends to be computationally expensive, review all aspects of the model carefully before
beginning the viewfactor analysis. This will help to minimize the number of Viewfactor analyses submitted with
incorrect or incomplete data. Viewfactor has some data checking and error detection capabilities, but it cannot detect all
user errors. The procedure for submitting a Viewfactor job is described in detail in Submitting a Viewfactor Job for
Analysis, 98.
Viewfactor will create a number of output files. The files created depend on some parameters in the VFCTL file. The
various files created as Viewfactor output are described in Viewfactor Data and Program Flow, 16 and Output Created by
a Viewfactor Execution, 101. When the viewfactor analysis is completed, the Viewfactor diagnostic files, VFDIAG and
VFMSG, should be reviewed for acceptable diagnostic data values and possible error messages, as described in
Reviewing the Viewfactor Output, 103.
Main Index
22 Patran Viewfactor Analysis
Summary of the Analysis Cycle for a Thermal Radiation Problem
analysis will be contained in the Patran Thermal QOUTDAT file and in nodal results files for use with the Patran
postprocessing tools.
Postprocessing
The capabilities of Patran and the Patran Thermal interface permit analysis results to be displayed and examined quickly
and efficiently. For more information about thermal results postprocessing, refer to the Patran Thermal User’s Guide. Refer
to the Patran Reference Manual for general postprocessing information.
Refinements
After examining the analysis results, you may be satisfied with the analysis, in which case this analysis cycle terminates.
You may wish to refine or modify the computer model of the problem and perform the analysis again, in which case the
analysis cycle starts over and repeats itself as applicable.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem
Patran Viewfactor Analysis
Purpose 24
Radiation Enclosure Concept 25
Surface Orientation in Patran 31
Specifying Radiation Boundary Conditions Using Patran Reference Manual
(VFAC Boundary Condition) 38
Advanced Features of the VFAC Boundary Condition 42
Relationship of VFAC LBC Data to VFINDAT File Data 51
Patran Thermal TEMPLATEDAT Files for Surface Property Description 52
Compatibility Requirements for Model and VFAC Templates 65
Symmetry as Applied to the Model and Viewfactor Radiation Exchange 67
Main Index
24 Patran Viewfactor Analysis
Purpose
3.1 Purpose
This chapter presents the concepts, processes, and commands that describe the thermal radiation specific attributes of heat
transfer analysis problems being modeled in the Patran System. Most of this chapter deals with preprocess model building
in Patran.
The concept of radiation enclosure is specific to thermal radiation analysis and is described in Radiation Enclosure
Concept, 25. The concept of surface orientation, while not unique to thermal radiation analysis, has not been introduced
previously in MSC.Software Corporation thermal analysis tools, and is described in Surface Orientation in Patran, 31.
Specifying Radiation Boundary Conditions Using Patran Reference Manual (VFAC Boundary Condition), 38 and Advanced
Features of the VFAC Boundary Condition, 42 deal with identifying the radiative boundary conditions and other associated
information using the Patran Radiation Boundary condition.
Relationship of VFAC LBC Data to VFINDAT File Data, 51 explains the relationship of the Viewfactor LBC form to the data
in the VFINDAT input data file for Viewfactor. Patran Thermal TEMPLATEDAT Files for Surface Property Description, 52
and Compatibility Requirements for Model and VFAC Templates, 65 discuss the Patran Thermal TEMPLATEDAT file and
the associated VFAC template data. In the last section of this chapter, page 67, the role of symmetry in thermal radiation
problems is discussed. The method for specifying the existence and type of symmetry in a problem is presented.
Some sophisticated thermal analysis tools have been provided and thus this chapter contains a large amount of information.
Take the time to understand all of the capabilities of the tools available here. This will enable you to make informed
decisions regarding how to model the thermal radiation phenomena at hand and choose the appropriate tools for the
analysis.
You must understand the concept of radiation enclosure, Radiation Enclosure Concept, 25. If you wish to model materials
or media with wavelength dependent properties, then Surface Orientation in Patran, 31 must be understood. Specifying
Radiation Boundary Conditions Using Patran Reference Manual (VFAC Boundary Condition), 38 deals with basic radiative
boundary conditions, while Advanced Features of the VFAC Boundary Condition, 42 deals with move advanced features
that enable modeling of participating media, radiation to ambient nodes, and methods for reducing CPU time required for
a Viewfactor analysis.
If you are also responsible for the accompanying Patran Thermal analysis, then Patran Thermal TEMPLATEDAT Files for
Surface Property Description, 52 andCompatibility Requirements for Model and VFAC Templates, 65 regarding the
TEMPLATEDAT files and VFAC templates are strongly recommended. Be cautious using symmetry in thermal radiation
problems, since the thermal radiation boundary conditions have subtle ways of making what appears to be a symmetric
problem actually nonsymmetric. However, if you must make use of symmetry, Symmetry as Applied to the Model and
Viewfactor Radiation Exchange, 67 should be thoroughly mastered.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 25
Radiation Enclosure Concept
Definition of Enclosure
For our purposes, an enclosure is a collection of thermally radiating surfaces which have the potential to see each other
(radiate to each other), along with open areas which can potentially be seen by the surfaces and participating media or
ambient nodes associated with these surfaces. From this definition you may infer that there are a large number of
enclosures possible in even a simple model. It is up to you to select appropriate enclosures for the particular thermal
analysis problem at hand. In most cases, appropriate choices of enclosures are natural and obvious from the model
geometry.
Surfaces in different enclosures do not have the potential to radiate to each other. In addition, a surface in one enclosure
does not have the ability to obstruct the view between a pair of surfaces in another enclosure. These properties of
enclosures are exploited in the Viewfactor program to reduce the CPU time required to analyze the viewfactor problem.
Surfaces not in an enclosure need not be considered as potential obstructions for that enclosure. Surface pairs that are not
in the same enclosure need not have calculations done for them.
The enclosures are also used for defining portions of the model over which the viewfactors from one surface to all other
surfaces it sees are summed. These sums have two uses:
1. For diagnostic purposes, and
2. To determine the viewfactor to that portion of the enclosure that is not represented by real surfaces, but instead is
open to space.
The Enclosure ID
Enclosures are made distinct by giving each different one a unique identification number. This ID number is associated
with all of the surfaces in its enclosure. The enclosure ID is assigned in the VFAC LBC form as described in Viewfactor
(p. 125) in the Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis.
Main Index
26 Patran Viewfactor Analysis
Radiation Enclosure Concept
• The upper limit of each waveband on each surface must be the same and
• The wavebands for each surface must be input in the same order in the TEMPLATEDAT file.
Enclosure 1
Figure 3-1 Solid with Hollow Interior and Thermal Radiation in the Interior
Figure 3-2 shows a cross section with two cavities. Each cavity is filled with a different participating media, and thus there
is a different participating media node for each cavity. Two enclosures are needed to keep separate the two different media.
Different enclosure ID numbers are assigned to each cavity.
If the media in each cavity had been the same (or if there had been no participating media), it would have been acceptable
to give both cavities the same enclosure ID. This is not preferred, because the cavity surfaces naturally fall into two groups.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 27
Radiation Enclosure Concept
Any surface in one group cannot see any other surface in the other group. By identifying these group through different
enclosure IDs the CPU time required to analyze the viewfactors will be reduced.
Enclosure 1 Enclosure 2
Figure 3-3 shows an object which is exposed to ambient radiation nodes above the object and below. Due to fortuitous
geometric circumstances in the model, this object could actually be modeled as one enclosure. This is not recommended.
A better approach would be to divide the model into two enclosures. One consists of the upward facing cavity and
surfaces and the second consists of the downward facing cavity and surfaces. The astute reader may also observe that the
model can be properly divided into even more enclosures. Recognize that the horizontal surfaces not in the cavities see
nothing but an ambient node. Thus each of these surfaces could be identified as a unique enclosure. Doing this in a model
where each of these surfaces was divided into many elements would result in substantial saving of CPU time to perform
the viewfactor analysis.
• Ambient Node 1
Enclosure 1 Enclosure 2
• Ambient Node 2
Denotes Thermally Radiating Surface.
Different Arrowheads are Associated
with Different Enclosures.
Main Index
28 Patran Viewfactor Analysis
Radiation Enclosure Concept
Figure 3-3 Example Showing Model with Two Open Cavities which
Naturally Correspond to Two Enclosures
Figure 3-4 shows an example where three enclosures have been identified. Other groupings of the surfaces, media node,
and ambient nodes are possible. The reader who wishes to master the art of identifying enclosures in the thermal analysis
model is urged to devise some other groupings of the surfaces and nodes into enclosures and then ascertain their
correctness for modeling this problem. For the correct enclosure groupings, what are the advantages and disadvantages?
Enclosure 1
Enclosure 3
Enclosure 2
Ambient Node 1 •
Figure 3-5 shows an object made of two different materials, each having different wavelength dependent surface emissivity
properties. This cavity is correctly modeled as one enclosure, but the wavebands in the enclosure must be the composite
of all the waveband transitions for the various materials’ wavebands. Thus, there are six wavebands in this enclosure and
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 29
Radiation Enclosure Concept
each material will have to be described in terms of these six wavebands, not in terms of the two wavebands of surface
one, for example.
Material 1 Material 2
0
λ0 λ3
1
0
λ0 λ1 λ2 λ4 λ5 λ6 = ∞
Wavebands for Enclosure
λ0 λ1 λ2 λ3 λ4 λ5 λ6 = ∞
Main Index
30 Patran Viewfactor Analysis
Radiation Enclosure Concept
Note that the wavebands for enclosure 1 end at lambda sub 4, and the wavebands for enclosures 2 and 3 begin at lambda
sub 4, the transition wavelength between transparency and opaquecy for the partition material.
Semi-Transparent Partition
Material 1 Material 2
λ4
ε1,λ
Wavebands for Material 1
λ0 λ3
λ0 λ2 λ5 λ6 λ7 = ∞
λ4 λ7 = ∞
Wavebands for Enclosure 3
λ4 λ5 λ6 λ7 = ∞
Figure 3-6 Example Showing the Use of Enclosures and Wavebands to Model a Cavity with a Partition
Transparent in One Waveband and Opaque in Another Waveband
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 31
Surface Orientation in Patran
Figure 3-7 Two and Three Dimensional Surfaces with Different Surface Normal Orientations
Viewfactor assumes that all coordinate systems are oriented in a right hand (also known as counterclockwise)
arrangement (i.e., if you place your right hand so that the fingers point from the first coordinate axis to the second
coordinate axis, then the raised thumb points up out of the paper in the positive direction of the third coordinate axis).
To apply this test to cylindrical coordinate systems, the fingers of the right hand should be pointed in the direction of
increasing polar angle. The term “counterclockwise” comes from the fact that for right-handed systems viewed from the
Main Index
32 Patran Viewfactor Analysis
Surface Orientation in Patran
front, the direction of rotation from the first axis (e.g., x-axis), to the second axis (e.g., y-axis), is counterclockwise.
Sketches illustrating these concepts are shown in Figure 3-8.
10 11
9 12
8 1
7 2
6 3
5 4
x y
z (second axis)
θ (polar angle)
r (first axis)
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 33
Surface Orientation in Patran
automatically takes care of this and you do not need to be concerned with it. The relationship of 3-D surface orientation
and node ordering is illustrated in Figure 3-9.
n
Second Node Third Node
Third Node
n
Second Node
Fourth Node
First Node
Figure 3-9 Relationship of Node Order to Surface Normal for 3-D Surfaces
For 2-D (either Cartesian or axisymmetric) models, you must take care to correctly orient the surfaces. The term
“surface” here generically means a boundary of the model. For objects modeled in 2-D space surfaces are represented as
lines. The orientation of these lines in Viewfactor is determined by the order in which their beginning and ending points
are given. You imagine yourself walking in the plane of the model, feet on the plane and on the side determined by the
right-hand orientation. Then as you walk from the beginning point to the ending point of the line, the principle or positive
Main Index
34 Patran Viewfactor Analysis
Surface Orientation in Patran
normal direction is that which the right arm points when extended horizontally. The relationship of node order to normal
direction and this method of determining normal direction for 2-D surfaces (lines) is illustrated in Figure 3-10.
(Z)Y
n Object
Ending Node of
Left Boundary
X(R)
Figure 3-10 Normals for Boundaries of 2-D Objects, Node Ordering and the “Right Arm Rule”
Patran allows you to arbitrarily mix left handed and right handed oriented systems for 2-D entities such as patches and
two-dimensional elements. This is not allowed when using Viewfactor. Since facilities to automatically manage orientation
of 2-D entities are not currently available, you must take care of this task. Failure to do so will result in erroneous 2-D
models. The following three subsections contain information to help manage this task.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 35
Surface Orientation in Patran
with respect to a right-handed system), the C1 parametric direction should point in the counterclockwise direction around
the perimeter of the patch for properly oriented patches.
Right Left
Right
Right
Right
Left
Left
Left
Figure 3-11 Right and Left Handed Oriented Patches and their C1 Parametric Directions
The next test may be used to determine a patch’s orientation. They are not recommended because they do not conform
to the engineering and mathematical standards for surface orientation. These tests are based on the order of the corner
grid IDs for the patch and on the order of the edges of the patch. Patran specifies the corner grid and edge order of right
hand oriented patches to be clockwise, whereas most users will be familiar with the usual counterclockwise orientation.
The patch corner grid ordering may be shown by clicking on geometry in Patran and selecting Action: show, Object:
surface, Method: attribute and selecting the surface. When the spreadsheet comes up, click on the vertices button to see
the corner grids and their order. Look at the graphics window to see if the grids in this order go clockwise around the
patch. If they do, then this is a properly oriented patch.
Main Index
36 Patran Viewfactor Analysis
Surface Orientation in Patran
The ordering of corner grids and edges is shown in Figure 3-12 for various right-handed (properly) and left-handed
(improperly) oriented paths.
2 2 3 4
4 1
3
3
2
1 RIGHT 3 RIGHT
4 3 RIGHT 1
2
4
1
1 4
4
1
3 2 2
4 3 3
2 3 2
1 2 1
4 3
1 2 4 3
1
4
1 4
4
1 4 3 2
2
LEFT
1 LEFT 3 3 1
1 3
2 LEFT
2 3 4 4 1
2 2 3
x Grid Numbers
x Edge Numbers
C1 Parametric Directions
Figure 3-12 Corner Grid and Patch Edge Ordering for Right- and Left-Hand Oriented Patches
The orientation of two-dimensional elements (i.e., quadrilaterals and triangles), may be determined by using the element
verification menu. Since elements are typically much more numerous than patches, take care to properly orient all patches
before beginning to generate elements to ensure that there are no improperly oriented elements.
The commands listed above for determining the element orientation are described fully in the Patran Reference Manual.
Note, however, that the ordering for nodes on a properly oriented element is counterclockwise as is customary in
engineering analysis, and that this is opposite of the ordering of corner grids on a properly oriented patch.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 37
Surface Orientation in Patran
The patch may also be deleted and a new properly oriented patch created in its place, or the patch may be overwritten
with a properly oriented patch with the same patch ID. Please see the Patran Reference Manual for information on the
various patch menus.
Elements may be reversed with the AUTOREVERSE option of the NORMALS submenu of the VERIFY action on finite
elements form. These forms are all described in the Patran Reference Manual. You must exercise caution when reversing
elements since Patran may not correctly transform the boundary conditions associated with an element edge when the
element is reversed. Other data associated with the element may not be transformed correctly either.
Note: You should not reverse any elements which have LBC element properties associated with it.
In most cases, if you have left-handed elements, it is recommended that the Patran finite element entities be deleted. Then
the orientation problems should be corrected at the patch level before any finite element entities are generated.
Form the cross product of the r-axis with the z-axis. Use the right-hand rule with your fingers pointing from the r-
axis to the z-axis and observe the direction of your thumb. Your thumb will point in the direction of the cross product,
either out of the screen or into the screen. If the direction is out of the screen, use right-handed patches and elements.
If the direction is into the screen, use left-handed patches and elements.
Main Index
38 Patran Viewfactor Analysis
Specifying Radiation Boundary Conditions Using Patran Reference Manual (VFAC Boundary Condition)
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 39
Specifying Radiation Boundary Conditions Using Patran Reference Manual (VFAC Boundary
OBSTRUCTION The value of 1, causes the nonobstruction flag to be set. This means to Viewfactor that this surface
is not capable of obstructing the view between any other pair of surfaces in this enclosure,
FLAG including the view between this surface and other surfaces. This facility provides the option to
reduce Viewfactor calculation time by identifying the nonobstructing surfaces in an enclosure.
TOP/BOTTOM The bottom surface flag, “1”, is used when applying VFAC boundary conditions to the bottom
FLAG surface (not edges) of quadrilateral, triangular, or bar elements. In these cases, VFAC DFEGs can
be applied either to the top or bottom, the default being the top. The bottom is selected when the
character “1”is present in the TOP/BOTTOM FLAG data box. The bottom surface flag has no
meaning for solid elements or for the edges of quadrilateral and triangular elements, and is
ignored. The top of a quadrilateral or triangular element is defined by the right-hand rule. For bar
elements, the beam orientation is used. The top of bars points towards the beam orientation, the
bottom points away. See the Patran Reference Manual for more information on beam orientation.
ENCLOSURE Entering the correct enclosure ID is critical to the proper performance of Viewfactor. There is no
way for Patran, Patran Thermal or Viewfactor to check the correctness of the enclosure ID.
ID Exercise extreme care in this regard.
Examples of a Viewfactor LBCs applied to a 2-Dand 3-D model are shown in Figure 3-13 and Figure 3-14, respectively.
13 14 15
7 8
U79,0,0,0 U777,0,0,0
10 11 12
5 6
U79,0,0,0 U777,0,0,0
7 8 9
3 4
U79,0,0,0 U777,0,0,0
4 5 6
1 2
U79,0,0,0 U777,0,0,0
Y
1 2 3
X
Z
Main Index
40 Patran Viewfactor Analysis
Specifying Radiation Boundary Conditions Using Patran Reference Manual (VFAC Boundary Condition)
Z X
U308,0,0,0
ID Element ID
IV Enclosure ID
KC 1
N2 UID
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 41
Specifying Radiation Boundary Conditions Using Patran Reference Manual (VFAC Boundary
Main Index
42 Patran Viewfactor Analysis
Advanced Features of the VFAC Boundary Condition
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 43
Advanced Features of the VFAC Boundary Condition
1
F23 A2
Surface 1
Surface 2
1
F14 A1
1- ε1 1 1- ε3
ε1 A1 F13 A1 ε3 A3
Node 1 Node 3
Thermal Network Resistor (typ)
1
F24 A2 τ24
1- ε2 1- ε4
Node 2 ε2 A2 ε4 A4 Node 4
1 1
F23 A2 τ23 F14 A1 τ14
1 Media 1
F24 A2 (1-τ24) Node F42 A4 (1-τ42)
1 1
F23 A2 (1-τ23) F41 A4 (1-τ41)
Surface 1
Surface 2
1 1
F14 A1 (1-τ14) F32 A3 (1-τ32)
1 1
F13 A1 (1-τ13) F31 A3 (1-τ31)
1- ε1 1- ε3
ε1 A1 1 ε3 A3
Node 1 F13 A1 τ13) Node 3
Figure 3-15 Thermal Resistor Networks With and Without Participating Media
Main Index
44 Patran Viewfactor Analysis
Advanced Features of the VFAC Boundary Condition
Finite Element
Action: Cre-
ate
Object: Node
Method: Edit
Note: The exact location of this node is not important. For clarity, you may want to use a conspicuous node ID number
such as 1000, 9999.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 45
Advanced Features of the VFAC Boundary Condition
Enclosure
Enclosure
Enclosure 2
Ambient
Node 2
Main Index
46 Patran Viewfactor Analysis
Advanced Features of the VFAC Boundary Condition
transmissivity cannot be calculated from Beer’s Law and thus Patran Thermal radiative resistor subtypes 7, 8, 11, and 12
are not permitted in an enclosure with both a participating medium and an ambient node.
1
(1-ΣjF2j) A2 τ2j
1- ε2 1 1- ε4
Node 2 Node 4
ε2 A2 F24 A4 τ24 ε4 A4
1 1
F24 A2(1-τ24) (1-ΣjF2j) A2(1-τ2j)
Surface 1
Surface 2
Media Node Ambient Node
1- ε1 1- ε3
ε1 A1 ε3 A3
Node 1 Node 3
Figure 3-17 A Simple Resistor Network for an Enclosure with Participating Media and an Ambient Node
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 47
Advanced Features of the VFAC Boundary Condition
Upper Plate
Lower Plate
Main Index
48 Patran Viewfactor Analysis
Advanced Features of the VFAC Boundary Condition
identifying convex surfaces and are able to group large numbers of element faces into convex surfaces merely by looking
briefly at the model.
Convex Surface
Figure 3-20 Torus and its Axisymmetric Model with Nonconvex Outer Surface Shaded
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 49
Advanced Features of the VFAC Boundary Condition
Main Index
50 Patran Viewfactor Analysis
Advanced Features of the VFAC Boundary Condition
Figure 3-21 Solid Cylinder Inside Hollow Cylinder with Annular Space
This type of situation can be difficult to correctly identify in more complicated axisymmetric models. You are urged
Surface to exercise caution.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 51
Relationship of VFAC LBC Data to VFINDAT File Data
Main Index
52 Patran Viewfactor Analysis
Patran Thermal TEMPLATEDAT Files for Surface Property Description
i = Waveband index
s = Stefan-Boltsmann constant
nbands = Number of wavebands
F = Black body function from λ i Ó 1 to λ i at temperature T
T1,T2 = Temperatures of surfaces 1 and 2, respectively
R = Effective radiative resistance between surfaces 1 and 2, taking into account possibly
time, temperature, and waveband
t = Time
l = Wave length
An example of spectrally-dependent surface emissivities for two surfaces is plotted in Figure 3-22. Also shown are the
approximate wavebands and constant waveband properties that might be used to represent the surface properties of these
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 53
Patran Thermal TEMPLATEDAT Files for Surface Property Description
two surfaces. The approximating properties are shown as thin dashed lines. Refer to Wavebands and Enclosures, 25 for
a discussion on the need for a consistent set of wavebands throughout an enclosure.
ε1,λ
0
λ
ε2,λ
0
λ
λ0 λ1 λ2 λ3 λ4 λ5 λ6 = ∞
Actual Properties
Waveband Approximation
Six bands are used here to model these emissivities.
The same bands must be used throughout an enclosure.
Patran Thermal’s QTRAN will accept overlapping wavebands and/or inactive or missing regions in the spectrum. This
is both a blessing and a curse. It gives you the latitude to model surface properties with piecewise constant basis functions
and leave out inactive regions of the spectrum from the analysis, but no checking is performed for a nonoverlapping
and/or incomplete spectrum. Thus you must be responsible for the correctness of the waveband model and data.
Main Index
54 Patran Viewfactor Analysis
Patran Thermal TEMPLATEDAT Files for Surface Property Description
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 55
Patran Thermal TEMPLATEDAT Files for Surface Property Description
Main Index
56 Patran Viewfactor Analysis
Patran Thermal TEMPLATEDAT Files for Surface Property Description
This resistor is similar to subtype 2, but the FF and AREA have been combined by multiplication into FA and stored
in DATA1. DATA2 is not used.
Subtype 10 R = 1.0 / ( FA * ( 1.0 - TAU ) )
This resistor is similar to subtype 3. It is to subtype 3 what subtype 9 is to subtype 2.
Subtype 11 R = 1.0 / ( FA * TAU )
This resistor is similar to subtype 7, but the FF and AREA have been combined by multiplication into FA and stored
in DATA1. DATA2 in not used.
Subtype 12 R = 1.0 / ( FA * ( 1.0 - TAU ) )
This resistor is similar to subtype 8. It is to subtype 8 what subtype 11 is to subtype 7.
*****************************************************
MPID4000LCI_TABLEKELVIN 1.0
LINEAR CONSTAT INTERVAL TABLE FOR EMISSIVITY
*SEE FIGURE 3-23 FOR A GRAPH OF THIS PROPERTY
MDATA100.0
MDATA500.0
MDATA0.1
MDATA0.1
MDATA0.9
MDATA0.9
/
******************************************************
*****************************************************
MPID3000TABLETIME1.0
TABLE FOR TIME DEPENDENT EMISSIVITY
*SEE FIGURE 3-24 FOR A GRAPH OF THIS PROPERTY
MDATA0.00.5
MDATA0.10.5
MDATA100.00.95
MDATA200.00.95
/
******************************************************
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 57
Patran Thermal TEMPLATEDAT Files for Surface Property Description
1.0
0.8
EMISSIVITY
0.6
0.4
0.2
0
0 400 800 1200 1600
TEMPERATURE
1.0
0.8
EMISSIVITY
0.6
0.4
0.2
0
0 50 100 150 200
TIME
Finite Element
Action: Create
Object: Material Property
Method: General
Main Index
58 Patran Viewfactor Analysis
Patran Thermal TEMPLATEDAT Files for Surface Property Description
Click on Input Data, then the desired Patran Thermal material function (e.g., "mpid_linr_tabl" will bring up the input data
for a tabular input).
Note: Make sure you have selected Patran Thermal as the analysis preference.
The number of data lines following the header line must be exactly the number of nbands, except that if the nbands field
is blank or zero there must be exactly one data line following. Comments may also be placed at the end of header or data
lines by placing a semicolon after the last data field on the line.
Some example header lines are:
VFAC 99
which specifies that this is VFAC template 99 and represents a gray material property, and
VFAC 1001 6
which specifies that this is VFAC template 1001 and represents a material with 6 wavebands.
The data lines contain eight fields each. The fields are separated by one or more spaces or by commas. The first field,
CONSTANT_EPSILON, is the only required field. Trailing blank fields may be omitted. Blank fields between nonblank
fields are not permitted and will be ignored, thus corrupting the user’s data. The fields are:
CONSTANT_EPSILON, CONSTANT_TAU, EMPID, TMPID, LAMBDA1, LAMBDA2, KFLAG, COLLAPSE
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 59
Patran Thermal TEMPLATEDAT Files for Surface Property Description
Main Index
60 Patran Viewfactor Analysis
Patran Thermal TEMPLATEDAT Files for Surface Property Description
KFLAG This optional field signals whether the transmissivity is evaluated directly (KFLAG = 0),
either from the constant value or from the MPID referenced in TMPID, or the transmissivity
is evaluated using Beer’s Law and an extinction coefficient evaluated from either the
constant value or from the MPID referenced by TMPID. The default KFLAG value is 0 and
the data must be integer. Beer’s Law may be stated as:
The main advantage of using COLLAPSE to collapse radiosity nodes is that this will result
in a much smaller number of radiation resistors in the model. The effect of using
COLLAPSE for small resistor networks is shown in Figure 3-25. The effect is more
pronounced for larger networks or for 3-D networks. A smaller number of resistors usually
means that the thermal analysis will proceed faster. In the best cases, the number of radiation
resistors may be reduced by about a factor of four for 2-D Cartesian or axisymmetric models
and by about a factor of 16 for 3-D models.
The main advantage of using COLLAPSE to collapse radiosity nodes is that this will result
in a much smaller number of radiation resistors in the model. The effect of using
COLLAPSE for small resistor networks is shown in Figure 3-25. The effect is more
pronounced for larger networks or for 3-D networks. A smaller number of resistors usually
means that the thermal analysis will proceed faster. In the best cases, the number of radiation
resistors may be reduced by about a factor of 4 for 2-D Cartesian or axisymmetric models
and by about a factor of 16 for 3-D models.
Our experience is that the loss of accuracy is quite small for fine meshes and lower
temperatures. The user may wish to try the examples in Example Thermal Radiation
Problems, 11, using the COLLAPSE field modeling techniques. Other existing models may
also be rerun using the new COLLAPSE flag. Then the results can be compared with
previous results and provide the user with a basis for deciding when to use or not use the
COLLAPSE feature.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 61
Patran Thermal TEMPLATEDAT Files for Surface Property Description
The COLLAPSE is applied on a template by template basis and is applied separately to each individual waveband in the
template. This versatility gives the user full control over which surface will have their corresponding radiosity nodes
collapsed. In order to collapse the radiosity nodes on one surface, but not on another surface of the same material, the
user will assign two different template IDs (TIDs), to the two surfaces. Then in the VFAC templates, specifying the
COLLAPSE_ID for each surface will determine whether the radiosity nodes made for that surface are collapsed.
Main Index
62 Patran Viewfactor Analysis
Patran Thermal TEMPLATEDAT Files for Surface Property Description
This VFAC template will be referenced whenever a surface which was VFAC LBCed with UID 99 is referenced. This
template defines a gray surface (nbands defaults to 0) and a constant emissivity of 0.89 and a transparent media (default
value of 1.0 for TAU).
************************************************************************
*Example VFAC Template 1
*
*KeywordTIDnbands
*
VFAC99
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
*
0.89
*
************************************************************************
The following template also describes a gray surface, but this time there is a participating media also with a constant
transmissivity of 0.95.
************************************************************************
*Example VFAC Template 2
*
*KeywordTIDnbands
*
VFAC10010
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
*
0.890.95
*
************************************************************************
This is a slightly more complicated template. It is still for a gray surface, but now the emissivity is defined by the material
property with MPID 4000.
************************************************************************
*Example VFAC Template 3
*
*KeywordTIDnbands
*
VFAC117
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
*
0.00.954000
*
************************************************************************
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 63
Patran Thermal TEMPLATEDAT Files for Surface Property Description
The following template defines both the emissivity and transmissivity in terms of material property data records
identified by MPIDs (EMPID and TMPID). Since the TMPID is negative, it will be evaluated as a function of time.
************************************************************************
*Example VFAC Template 4
*
*KeywordTIDnbands
*
VFAC1098
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
*
0.00.04000-3000
*
************************************************************************
The next template has the KFLAG set to one, and thus needs all of the preceding data on the line defined (recall that
embedded blank fields are not allowed). This template is similar to the previous one, except that the transmissivity will
be evaluated by Beer’s Law and the extinction coefficient will be determined from the time dependent material property
definition in MPID 3000.
************************************************************************
*Example VFAC Template 5
*
*KeywordTIDnbands
*
VFAC897
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
*
0.00.04000-30000.00.01
*
************************************************************************
The next example shows the previous example without the supporting comments and spaces. Clearly the previous
example is easier to read and we recommend that some standard and clear format be followed by the user.
************************************************************************
*Example VFAC Template 6
*
VFAC897
0.0,0.0,4000,-3000,0.0,0.0,1
*
************************************************************************
Main Index
64 Patran Viewfactor Analysis
Patran Thermal TEMPLATEDAT Files for Surface Property Description
The following template is for a surface with three wavebands, the first from 0.0 to 2.0 microns, the second from 2.0 to 5.0
microns, and the third from 5.0 to 1.0E6 microns (approximately infinity for wavelengths). Each waveband defines the
properties in a different way and serves to exemplify the versatility of the wavebands and VFAC templates.
************************************************************************
*Example VFAC Template 7
*
*KeywordTIDnbands
VFAC8973
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
0.890.00-30000.02.0
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
0.0.0.04000-30002.05.01
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
0.981.0005.01.0E6
*
************************************************************************
The following templates show the use of the COLLAPSE_ID. Note that when a COLLAPSE_ID is given, the other fields
of the template must be filled in with appropriate or default values as placeholders.
************************************************************************
*Example VFAC Template 8
*
*KeywordTIDnbands
VFAC392
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
0.000.0000.03.000
*
*EPSILONTAUEMPIDTMPIDLAMBDA1LAMBDA2KFLAGCOLLAPSE
0.000.0003.01.0E602
*
************************************************************************
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 65
Compatibility Requirements for Model and VFAC Templates
• If there are multiple wavebands, then this condition must hold for each waveband. Note also that by the previous
requirement on wavebands in the enclosure that the number of wavebands for every pair of surfaces which can
see each other is equal.
Main Index
66 Patran Viewfactor Analysis
Compatibility Requirements for Model and VFAC Templates
If you plan or want to be able to use the KFLAG set equal to one option, then do not use ambient environment nodes,
AMBNOD, in the model. Instead, model the ambient environment as surfaces at the ambient temperature.
If you plan or want to be able to model participating media, include the participating media node, MEDNOD, in the model.
There is no harm if it is not used, but it will be there when it is needed.
Take care when planning the enclosures and participating media nodes, MEDNOD, to ensure that all surface pairs in an
enclosure which can see each other have the same MEDNOD.
The above suggestions are the most important, as failure to follow them may require that the viewfactors be recalculated
and this is the most computationally expensive part of the Viewfactor analysis.
The requirements for the equality of the CONSTANT_TAU, TMPID, LAMBDA1, LAMBDA2, and KFLAG between
surface pairs which can see each other in an enclosure is not so troublesome if violated. It can be corrected by changing
the VFAC templates but does not in general require recalculating the viewfactors. Still, careful planning is the best
prevention. If there are two or more enclosures, the user may wish to use different VFAC templates for the same material
in the different enclosures. This will give the user greater latitude in modeling different, but simultaneous, phenomena in
the different enclosures.
If a constant value for transmissivity, CONSTANT_TAU, is used, it must be the same for all surfaces in an enclosure which
can see each other.
The TMPID must be the same for all surfaces in an enclosure which can see each other.
The KFLAG must be the same for all surfaces in an enclosure which can see each other.
If the KFLAG is zero, then the CONSTANT_TAU or TMPID data must be for transmissivity data directly. If the KFLAG
is one, then the CONSTANT_TAU or TMPID data must be for extinction coefficient data to be used in Beer’s Law.
The beginning and ending wavelengths for each waveband in the enclosure must be in the same order and must be equal
for all surfaces in an enclosure which can see each other.
Given these restrictions on the data in an enclosure, the user may wish to model the same material in each different
enclosure with different UIDs so that for example it may be represented with different VFAC templates in each different
enclosure. This involves some additional work, but greatly extends the flexibility and capabilities of the model.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 67
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
Main Index
68 Patran Viewfactor Analysis
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 69
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
Symmetry Line
Axis
Main Index
70 Patran Viewfactor Analysis
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
Symmetric Image
After Second Reflection Second
Symmetry
Line
First Symmetry Line
X
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 71
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
2
6
Symmetric
Image
Reflection
Plane
4
6 2 Object
Rotation Axis
Original Object
Symmetric
Images
Main Index
72 Patran Viewfactor Analysis
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
Symmetric Image
After First Reflection
Second
Reflection
Plane
Symmetric Images
After Second
Reflection
Original Obje
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 73
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
RZ (Axisymmetric) Space
Object
Center Line
Symmetry Line
Symmetric Image
Main Index
74 Patran Viewfactor Analysis
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
Symmetry Line
3' 3
2' 2
1' 1'
The lower semicircular outer boundary of the outer hollow cylinder receives a nonuniform heat flux as shown by the length
of the arrows. Energy is transferred from the inner surface of the hollow cylinder to the solid cylinder by thermal radiation.
Although the geometry is axisymmetric, the heat flux boundary condition is not. The heat flux boundary condition and the
geometry together are symmetric about a vertical line through the center of the model. Unfortunately, the radiation
boundary conditions are not symmetric about this line as can be seen by examining the view from point 1 to points 2 and
2' (or many other pairs of points).
Normally, this lack of symmetry either would not be noticed by the analyst and an incorrect model created or the entire
object in 2-D would be modeled. Viewfactor, through its symmetry operator, will allow the user to model this object as its
symmetric right or left half, thus reducing the size of the Patran Thermal analysis by half.
To handle the nonsymmetry of the radiative boundary conditions, the user must tell Viewfactor, through use of the
symmetry operators, to take into account the symmetric image of the model when calculating viewfactors and making
Patran Thermal radiation resistors. In this case, this would be done by specifying a symmetric reflection about a line
coincident with the vertical symmetry line.
Instructions on how to enter the symmetry operators into the Patran model will be given at the end of this section. See
Entering Viewfactor Symmetry Operations in the Patran Model, 75.
Main Index
Chapter 3: Model Creation for a Thermal Radiation Problem 75
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
replicate it by rotating about the center point by 90 degrees and then reflecting the resulting model and image about a
horizontal line through the cylinder’s center as shown in Figure 3-32.
1'
2
3'
2'
1
3
3''
1''
2'''
3'''
2'''
1'''
The geometry and boundary conditions seemingly appear as we think they should. You might be tempted to define a
Viewfactor rotational symmetry operator and reflection symmetry operator for this problem and proceed with the thermal
analysis using the quarter section model. This, however, would be erroneous.
Upon careful examination of the model the reader can see that, for example, the view from point 1 is not the same as the
view from point 1''. Thus this is not a correct model of the radiative interchange in this model.
Such errors are subtle and difficult to detect. In general, we recommend that symmetry not be used in thermal radiation
models in order to preclude the possibility of such problems.
Main Index
76 Patran Viewfactor Analysis
Symmetry as Applied to the Model and Viewfactor Radiation Exchange
The element property data for rotation about an axis contains the number of times the rotation is to be repeated and the
angle of rotation in degrees. The element input property form is found under Element Properties looks like
Get the Input Properties form under Element Properties.
Finite Element
Action: Create
Object: ID
Type: Rad Sym Bar Rotation
The nodes belonging to the radiation symmetry elements have to be declared as type "I" nodes. To do so one must first
create OD elements at the location of the nodes belonging to the radiation symmetry elements. When the OD elements are
created go to the element properties menu and select dimension: OD, type: Node type and click on the ‘input data’ button
and select ‘information node’ in the ‘node type’ data box. Then select the OD elements created as the application region
and click on ‘apply’. Nodes of type I (ignore) will not be translated by PATQ into the Patran Thermal nodes, but will only
be used by PATQ to generate the Viewfactor symmetry operators.
Main Index
Chapter 4: Preparation for Analysis
Patran Viewfactor Analysis
Main Index
78 Patran Viewfactor Analysis
Introduction
4.1 Introduction
After the model has been created in Patran and output to a neutral file, you can proceed with the next step in the analysis
cycle. This chapter addresses two topics:
1. Translating the Patran neutral file into a file, VFINDAT, which can be read by Viewfactor for analysis, and
2. Creating the Viewfactor program execution control file, VFCTL.
Main Index
Chapter 4: Preparation for Analysis 79
Viewfactor Execution From Patran Thermal
Note: If both Execute Viewfactor Analysis and Execute Thermal Analysis toggles are set, Patran Thermal will wait until
the Viewfactor solution is done before proceeding with the thermal analysis.
Main Index
80 Patran Viewfactor Analysis
PATQ Translation from the Patran Neutral File to the VFINDAT File
4.3 PATQ Translation from the Patran Neutral File to the VFINDAT
File
The MSC Patran Thermal User’s Guide provides more complete information on the Patran Thermal program PATQ. This
Guide is only concerned with the aspects of PATQ which relate to translating a neutral file to a VFINDAT file.
Note: The steps below are automatically performed as a background job when Patran Thermal execution is spawned from
Patran.
Main Index
Chapter 4: Preparation for Analysis 81
PATQ Translation from the Patran Neutral File to the VFINDAT File
Main Index
82 Patran Viewfactor Analysis
PATQ Translation from the Patran Neutral File to the VFINDAT File
Main Index
Chapter 4: Preparation for Analysis 83
PATQ Translation from the Patran Neutral File to the VFINDAT File
Main Index
84 Patran Viewfactor Analysis
PATQ Translation from the Patran Neutral File to the VFINDAT File
There are many different options in the translation process and they cannot all be presented here. The above dialogue is
typical of a PATQ translation. If errors are detected by PATQ, error messages will be written to the terminal screen.
Patran Thermal’s PATQ uses the default file name VFINDAT for the Viewfactor input data file. Viewfactor allows you to
specify all relevant file names and so you may, at your discretion, change the name of the VFINDAT file created by PATQ.
The new name must also be given in the VFCTL file (see VFCTL, the Viewfactor Program Execution Control File, 85.
Main Index
Chapter 4: Preparation for Analysis 85
VFCTL, the Viewfactor Program Execution Control File
Note: For execution spawned from Patran Thermal, this file is automatically created based on input data in the Patran
Thermal Analysis Forms.
Default values are provided automatically for all run control data. You do not need to enter data lines if the default is the
desired value. The default values are given in Keywords in the VFCTL File, 88. The data lines may be placed in any order
and only one occurrence of each keyword is allowed. A complete VFCTL file from a VAX/VMS platform is shown
below. The filenames have been made generic, but the $PATH is not generic.
Invalid keywords cause a fatal error. This prevents a costly Viewfactor execution with invalid data.
Main Index
86 Patran Viewfactor Analysis
VFCTL, the Viewfactor Program Execution Control File
**************************************************************************
*
*BEGINNING OF EXAMPLE VFCTL FILE
*
*The path will be prefixed onto every other file name given below.
*
$PATH:[PHILLIPS.VF.FILES.CYLINDER.CASE1]
*
*The message file will contain text messages from Viewfactor.
*
$MESSAGE_FILE:VFMSG
*
*The status file was designed for restarting the Viewfactor program.
*This capability is not presently supported.
*
$STATUS_FILE:VFRESTARTSTAT
*
*The diagnostic file will contain numerical diagnostic data.
*
$DIAGNOSTIC_FILE:VFDIAG
*
*The title will be placed near the top of various output files to aid in later identification.
*
$TITLE:THIS IS A TEST
*
*The restart file was designed for restarting the Viewfactor program.
*This capability is not presently supported.
*
$RESTART_FILE:VFRESTARTDAT
*
*This is the input data file which typically was created by the Patran Thermal PATQ translator.
*
$IN_DATA:VFINDAT
*
*This is the file containing the VFAC template data.
$TEMPLATE_FILE:TEMPLATEDAT
*
*This is the file containing the raw viewfactor data.SSSS
*
$RAW_DATA:VFRAWDAT
*
*This file contains the Patran Thermal radiation resistors made by Viewfactor.
*
$OUT_DATA:VFRESDAT
*
*This file contains the node definition data for Patran Thermal for the radiosity nodes
*created by Viewfactor.
*
$RAD_NODE_FILE:VFNODEDAT
*
*The value of the run control parameter controls which parts of the Viewfactor program
*will be executed.
*
$RUN_CONTROL:0
Main Index
Chapter 4: Preparation for Analysis 87
VFCTL, the Viewfactor Program Execution Control File
*
*This parameter controls the restart capabilities of Viewfactor.
*Presently only the value 0 is supported (this is not a restart).
*
$RESTART_FLAG:0
*
*This parameter controls the convergence checking in Viewfactor. The
*value of -1.0 causes a default value based on the number of surfaces
*in each enclosure to be calculated.
*
$CONVERGE-1.0
*
*Viewfactors below the zero cutoff value will be set to 0.0
*
$ZERO:0.0
*
*This parameter controls the accuracy of curved surface approximation by
*linear surfaces for obstruction checking.
*
$APPROX_CURVE:0.1
*
*These values determine the maximum order of numerical integration
*quadrature permitted for integration of various quantities.
*
$GAUSS_ORDER:888
*
*These values determine the minimum and maximum number of subdivisions for
*the three-dimensional representation of an axisymmetric surface for the
*purpose of checking for obstructions and calculating viewfactors.
*
$AXISYM_SURFACE:313
*
*This keyword signals the end of the VFCTL file.
*
$EOF:
*
*THIS IS THE END OF THE VFCTL FILE EXAMPLE.
*
**********************************************************************
Main Index
88 Patran Viewfactor Analysis
VFCTL, the Viewfactor Program Execution Control File
$PATH: pathname
Purpose of the Keyword "$PATH:" is to name a path for Viewfactor files. The pathname will be prefixed to all other
filenames used in this particular execution of Viewfactor. This feature is provided so that
long pathnames do not need to be entered with every filename, provided they are common
and the same as that given in pathname. If you adopt a standard convention for filenames
and group different models and cases into directories or paths, then these may be accessed
by Viewfactor merely by changing the pathname in VFCTL. If the pathname is blank, then
nothing will be prefixed to the filenames and your current default directory will be used.
Required or Optional Optional.
Default Value Default is a blank string.
Valid Range Valid pathnames are computer system dependent.
Suggested Values None.
$MESSAGE_FILE: filename
Purpose of the Keyword "$MESSAGE_FILE:" is to name the file that will contain text messages from Viewfactor.
See VFMSG, 101 and VFMSG, the Viewfactor Message File, 103
Required or Optional Optional.
Default Value VFMSG.
Main Index
Chapter 4: Preparation for Analysis 89
VFCTL, the Viewfactor Program Execution Control File
$STATUS_FILE: filename
Purpose of the Keyword "$STATUS_FILE:" is to name the file to be used for restart status data for Viewfactor.
This capability is not presently supported.
Required or Optional Optional.
Default Value VFRESTARTSTAT.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
$DIAGNOSTIC_FILE: filename
Purpose of the Keyword "$DIAGNOSTIC_FILE:" is to name the file that will contain numerical diagnostic data
from Viewfactor. See VFDIAG, 101 and VFDIAG, the Viewfactor Diagnostic Data File, 106.
Required or Optional Optional.
Default Value VFDIAG.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
$TITLE: title
Purpose of the Keyword "$TITLE:" is to identify a character string title that will be output to various files in
Viewfactor to aid in identifying the analysis case to which a file belongs.
Required or Optional Optional.
Default Value Default is a black string.
Valid Range The character string should have less than 80 characters.
Suggested Values None.
$RESTART_FILE: filename
Purpose of the Keyword "$RESTART"_FILE:" is to name the file that will contain data for restarting Viewfactor.
This capability is not presently available.
Required or Optional Optional.
Default Value VFRESTARTDAT.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
$IN_DATA: filename
Purpose of the Keyword "$IN_DATA:" is to name the file that must contain the input data for Viewfactor.
Required or Optional Optional.
Default Value VFINDAT.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
Main Index
90 Patran Viewfactor Analysis
VFCTL, the Viewfactor Program Execution Control File
$TEMPLATE_FILE: filename
Purpose of the Keyword "$TEMPLATE_FILE:" is to name the file that must contain the VFAC templates for this
model.
Required or Optional Optional.
Default Value TEMPLATEDAT.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
$RAW_DATA: filename
Purpose of the Keyword "$RAW_DATA:" is to name the file which will contain the raw viewfactor data.
Viewfactor creates and outputs raw viewfactor data as well as reads in the raw viewfactor
data when making Patran Thermal radiation resistors. See VFRAWDAT, 102.
Required or Optional Optional.
Default Value VFRAWDAT.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
$OUT_DATA: filename
Purpose of the Keyword "$OUT_DATA:" is to name the file which will contain the Patran Thermal radiation
resistor data created by Viewfactor. See VFRESDAT, 102.
Required or Optional Optional.
Default Value VFRESDAT.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
$RAD_NODE_FILE: filename
Purpose of the Keyword "$RAD_NODE_FILE:" is to name the file which will contain the node definition data for
Patran Thermal for radiosity nodes created by Viewfactor. See VFNODEDAT, 102.
Required or Optional Optional.
Default Value VFNODEDAT.
Valid Range Valid filenames are computer system dependent.
Suggested Values None.
Main Index
Chapter 4: Preparation for Analysis 91
VFCTL, the Viewfactor Program Execution Control File
$RUN_CONTROL: value
Purpose of the Keyword "$RUN_CONTROL:" is to set a run control value. The run control value determines the
execution sequence for Viewfactor. It is this parameter that allows the user to calculate
viewfactors before the VFAC templates are ready (set value to 1), calculate or recalculate
the Patran Thermal radiation resistors from existing raw viewfactor data (set value to 2),
or calculate viewfactors and make radiation resistors in the same execution (set value to
0). For additional information, see Viewfactor Data and Program Flow, 16 and Changing
VFCTL, 122.
The valid values of the $RUN_CONTROL: parameter and their effects are:
0 Check data, and if the data checking status = OK, calculate viewfactors and
make radiation resistors.
1 Check data, and if the data checking status = OK, calculate viewfactors only.
2 Calculate radiation resistors only, using existing raw viewfactor data. This
process involves extensive data checking as the calculations are being done and
since no significant CPU time saving is realized, no data checking is done before
the calculations.
100 Check the data for making viewfactors and radiation resistors and then stop. Do
not calculate viewfactors or make resistors.
101 Check the data for making viewfactors and then stop. Do not calculate
viewfactors.
102 Check that the appropriate files are present for making radiation resistors from
raw viewfactor data. Do not make the radiation resistors.
200 Check the data for making viewfactors and radiation resistors. If the data
checking status = OK or the data only generated warning messages, proceed
with the viewfactor calculations and the creation of the radiation resistors. If the
data checking generated an error message, stop.
201 Check the data for making viewfactors only. If the data checking status = OK or
the data only generated warning messages, proceed with the viewfactor
calculations only. If the data checking generated an error message, stop.
1001 Skip the data checking and proceed directly to calculating the viewfactors only.
Main Index
92 Patran Viewfactor Analysis
VFCTL, the Viewfactor Program Execution Control File
$RESTART_FLAG: value
Purpose of the Keyword "$RESTART_FLAG:" is to set the Viewfactor restart flag. The restart flag value controls
restarting Viewfactor. Presently this capability is not supported.
Required or Optional Optional.
Default Value 0.
Valid Range The only valid value is the integer 0.
Suggested Values None.
$CONVERGE: value
Purpose of the Keyword "$CONVERGE:" is to set the parameter that controls convergence checking in
Viewfactor. If the value entered is less than or equal to zero, a convergence criteria is
calculated by Viewfactor based on the number of surfaces in each enclosure. This number
will be recalculated as each enclosure is processed. The formula for convergence criteria
used by Viewfactor to calculate the default value is:
converge_value = 0.01/(number of surfaces in enclosure)0.7.
Required or Optional Optional.
Default Value -1.0.
Valid Range Valid values are real numbers ≤ 1.0 and representable on the computer.
Suggested Values The suggested value is the default value, -1.0. If a faster execution time is desired, at the
cost of lost accuracy, a value around 0.1 may be appropriate. Until you gain some
experience with Viewfactor, it is best to use the default value. The convergence criteria is
not an absolute requirement. You don’t know how fast the numerical scheme converges.
The fact that it appears to have converged over a few iterations is no guarantee that it has
converged. The default values are based on previous user's experience. As you gain
experience you may be able to improve on these default values.
$ZERO: value
Purpose of the Keyword "$ZERO:" is used to establish a cut off value. Viewfactors below the zero cutoff value will
be set to zero. This is a convenient way to eliminate viewfactors and their associated
radiation resistors for viewfactors which are close to zero. You must exercise discretion
here. For example, in a model with 10,000 surfaces, viewfactors smaller than 0.000001
may be very significant. If the value is less than -0.5, then the zero cutoff value will be set
equal to the convergence criteria value. (See $CONVERGE: value, 92.
The program gives the user the ability to not make radiation resistors if the viewfactor
between nodal subareas is less than a user specified cutoff value. The zero cutoff value is
set using the $ZERO: parameter in the VFCTL file.
Required or Optional Optional.
Default Value 0.0.
Main Index
Chapter 4: Preparation for Analysis 93
VFCTL, the Viewfactor Program Execution Control File
Valid Range Valid values are real numbers less than or equal to 1.0.
Suggested Values The default value of 0.0 is highly recommended. The use of numbers greater than the
default convergence criteria value is definitely not recommended.
In general, the use of nonzero cutoff values is not recommended. If you want to use them
anyway, set the zero cutoff value to zero during the calculation of raw viewfactor data and
then set it to the desired cutoff value during the creation of resistors from the raw
viewfactor data. This will give you the flexibility of changing the zero cutoff value
without having to redo the viewfactor calculations. This procedure requires that you
submit Viewfactor twice, once with "$RUN_CONTROL:" set to 1 and $ZERO: set to 0.0
and again with "$RUN_CONTROL:" set to 2 and "$ZERO:" set to the desired cutoff
value.
$APPROX_CURVE: value
Purpose of the Keyword "$APPROX_CURVE:" is to set the parameter that controls the number of subdivisions a
curved surface or line will undergo as it is approximated by plane triangles or straight line
segments. These linear subdivisions are used for obstruction checking. The smaller the
value, the more subdivisions will be required to approximate a curved surface or line. As
more subdivisions are created, the accuracy of the calculations will generally increase and
the CPU time will increase dramatically.
Note: For straight or planar (flat) surfaces this parameter has little
effect since they are already well approximated by linear lines or
planes.
Main Index
94 Patran Viewfactor Analysis
VFCTL, the Viewfactor Program Execution Control File
In general, the larger the parameter value, the more accurate and more CPU costly the
Viewfactor analysis will be. The integration orders jump in larger step sizes as they
increase because, for example, an increase from 39 to 40 has little effect, whereas an
increase from 3 to 4 may have a significant effect.
Required or Optional Optional.
Default Value The default values are 8, 8, and 8.
Valid Range Valid values are integers between and including 3 and 16.
Suggested Values In general, the suggested values are the default values.
The maximum integration order is only used when the numerical integration scheme has
not converged. In most cases, this happens before the maximum integration order is
reached. Thus you only pay for the higher integration orders when they are needed for
accuracy. If you wish to do a test run at less expense than the actual analysis run, the CPU
time may be cut down by reducing the GAUSS_ORDER parameters. In general, you will
make the weighting parameter less than or equal to the other parameters, although this is
not required.
Main Index
Chapter 4: Preparation for Analysis 95
VFCTL, the Viewfactor Program Execution Control File
$EOF:
Purpose of the Keyword "$EOF:" is to signal the end of the VFCTL file.
Required or Optional Optional.
Default Value,
Valid Range, There is no parameter to receive a default value, be checked for validity, or receive a
Suggested Values recommended value.
Main Index
96 Patran Viewfactor Analysis
VFCTL, the Viewfactor Program Execution Control File
A sample VFCTL file is delivered with the Viewfactor program. This file is reproduced here.
Note: The above file corresponds to the defaults set when a Viewfactor job is spawned directly from Patran.
Main Index
Chapter 5: Analysis
Patran Viewfactor Analysis
Analysis
5
Submitting a Viewfactor Job for Analysis 98
Output Created by a Viewfactor Execution 101
Reviewing the Viewfactor Output 103
Main Index
98 Patran Viewfactor Analysis
Submitting a Viewfactor Job for Analysis
$RUN_CONTROL: 0
The following files are required:
VFINDAT
TEMPLATEDAT
The following files are created:
VFRESTARTSTAT
VFRESTARTDAT
VFRAWDAT
VFRESDAT
VFNODEDAT
VFDIAG
VFMSG
Main Index
Chapter 5: Analysis 99
Submitting a Viewfactor Job for Analysis
$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.
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.
Main Index
100 Patran Viewfactor Analysis
Submitting a Viewfactor Job for Analysis
Note: A Viewfactor Submit script is automatically created if execution is spawned from within Patran analysis menu.
Main Index
Chapter 5: Analysis 101
Output Created by a Viewfactor Execution
VFMSG
This file contains messages from Viewfactor to the user. It begins with a header, followed by the title data from the
VFCTL file. Then the control data that was actually used by Viewfactor is echoed to this file. This data may not look
quite the same as the user’s VFCTL file. This is because the format may be different and if you allowed any values to
default, the default values will be displayed.
The rest of the file contains either informative messages on the progress of the Viewfactor analysis or error messages.
Since Viewfactor has been designed to check for many errors and to terminate gracefully on an error condition, the
VFMSG file is the only reliable place to find if an error has occurred.
For the most part, Viewfactor will not abort at the computer operating system level. When it detects an error, it reports
the error to the VFMSG file and terminates execution without triggering any system level errors. Since there is no system
level traceback, the traceback information that Viewfactor outputs to the VFMSG file is very helpful if you need to
discuss a problem with MSC’s technical support staff. VFMSG, the Viewfactor Message File, 103 contains a sample
VFMSG file.
VFDIAG
This file contains primarily numeric diagnostic data. The file begins with the title data from the VFCTL file, followed
by any additional title data from the input data files.
If viewfactors were calculated in this analysis, data is given about the sums of the viewfactors from each surface to every
other surface in the enclosure. Similar data is also given for the nodal subareas on each surface.
This data is grouped by enclosure. Each group of enclosure data begins with the keyword $ENCL: followed by the
enclosure ID number, the number of surfaces in the enclosure, and the number of symmetric images created of this
enclosure. Then for each surface in the enclosure there is a line of data containing the surface ID, the sum of the
viewfactors from this surface to all other surfaces in the enclosure, 1.0 minus this sum, and the sum of all viewfactors
from this surface to other surfaces which were set to zero because they were less than the zero cutoff value ($ZERO:).
Following this line will be the sum of the viewfactors for each nodal subarea on the surface. Thus, there will be the same
number of data items as there are nodes on the surface. These data will have four values per line until all of the nodes on
this surface are used. Currently, none of the element faces supported by Viewfactor have more than four nodes and hence
this data fits on one line. This pattern is repeated for each surface in the enclosure.
After all of the surfaces in the enclosure have been accounted for in the above manner, some statistical data for the
enclosure is given. This data is presented in five columns. The first line of statistical data is for the surfaces as wholes
and the following lines are statistical data for the nodal subareas of the surfaces. The statistical data for the nodal subareas
do not have a sound theoretical basis and should not be taken too seriously. It is, however, the best data available at this
time.
Main Index
102 Patran Viewfactor Analysis
Output Created by a Viewfactor Execution
Column 1: The maximum deviation from unity for the sums of viewfactors from a surface or nodal
subarea surface to all other surfaces or nodal subarea surfaces in the enclosure.
Column 2: The average deviation from unity for the sums of viewfactors for this enclosure.
Column 3: The standard deviation for the above average.
Column 4: The average of the absolute values of the deviations from unity for the sums of
viewfactors in this enclosure.
Column 5: The standard deviation for the above average.
The data for each enclosure is terminated with the $ENDENCL: keyword. If there is more than one enclosure, the above
pattern is repeated for each enclosure.
If Patran Thermal radiation resistors were created by this execution of Viewfactor, the VFMSG file will contain
information on the radiosity nodes, emissivity resistors, and radiation resistors created for each enclosure.
The file is terminated by the keyword $EOF:.
Examples are given in VFDIAG, the Viewfactor Diagnostic Data File, 106.
VFRAWDAT
This is an unformatted (binary) file containing data about the surfaces and raw viewfactor data. Since it is in binary form,
the user may not readily examine its contents. The binary form was chosen because this data file tends to be very large and
the binary form is considerably more compact than the text form.
VFRESDAT
This is also a binary file. It contains data describing the Patran Thermal radiation resistors. This file is typically very large,
hence its binary form. Patran Thermal can translate the binary form of this file to a text form which the user can read, but
it can be a very large file. The procedure for doing this is described in Interface From Viewfactor to Patran Thermal, 111.
This file must be referenced by the Patran Thermal QINDAT file in order for it to be included in the QTRAN thermal
analysis. See Interface From Viewfactor to Patran Thermal, 111.
VFNODEDAT
This file contains the information needed by Patran Thermal to define the additional radiosity nodes created by Viewfactor
for the thermal analysis of the thermal radiation interchange. It contains comment lines which begin with a semicolon. If
any radiosity nodes were created, the file will contain the line
Main Index
Chapter 5: Analysis 103
Reviewing the Viewfactor Output
Main Index
104 Patran Viewfactor Analysis
Reviewing the Viewfactor Output
Main Index
Chapter 5: Analysis 105
Reviewing the Viewfactor Output
The following is an example of a VFMSG file from an unsuccessful Viewfactor execution. The messages contained in
the VFMSG file will be extremely useful for debugging purposes. If you should call one of MSC.Software Corporation
support centers with Viewfactor, they will almost certainly ask you about the messages in your VFMSG file.
Main Index
106 Patran Viewfactor Analysis
Reviewing the Viewfactor Output
Main Index
Chapter 5: Analysis 107
Reviewing the Viewfactor Output
If the enclosure is open, the sums for surfaces which have a view of the opening should be somewhat less than one. In
some simple geometries, you may be able to calculate the view of the opening for some of the surfaces. This number may
be compared with the value of one minus the sum for a very good test of the accuracy of the viewfactor analysis.
For larger problems, the statistical information at the end of each enclosure in the VFDIAG file provides a convenient
summary of the diagnostic data for that enclosure. The nature of this data was explained in VFDIAG, 101. Your own
discretion must be used when evaluating this data.
If you deem the accuracy of the analysis to be inadequate, then this may be remedied by increasing the maximum
integration order, reducing the convergence criteria, and refining the finite element mesh in the model. Unfortunately,
there are no guarantees here and no one particular method can be counted on to work in every situation.
The following is an example of a VFDIAG file. The enclosure here is the interior of a hollow cube. The faces were
modeled with a very coarse mesh and have both triangular and quadrilateral faces. There are 9 surfaces in the model.
Since this is a closed enclosure, we expect the sums of the viewfactors should be very close to one. The diagnostic data
indicates that for the surfaces the sums are very close to one. However, the sums for the nodal subareas tend to deviate
from one by several percent.
You might reduce this error by increasing the integration order, decreasing the convergence criteria, or refining the coarse
mesh in the model.
Main Index
108 Patran Viewfactor Analysis
Reviewing the Viewfactor Output
Main Index
Chapter 6: Post-Analysis
Patran Viewfactor Analysis
Post-Analysis
6
Introduction 110
Interface From Viewfactor to Patran Thermal 111
noteplains on Resistor Values 116
THERMAL Analysis 117
THERMAL Results Postprocessing 118
Main Index
110 Patran Viewfactor Analysis
Introduction
6.1 Introduction
Post-analysis, includes the activities that normally follow a Viewfactor analysis. These activities primarily involve
interfacing to Patran Thermal for subsequent thermal network analysis. This chapter assumes that you have used
Viewfactor to create Patran Thermal radiation resistors and now want to include them in a thermal analysis.
Viewfactor may also be used to calculate viewfactors only and not make Patran Thermal radiation resistors, or be used to
take already existing viewfactor data and combine it with Patran Thermal template file data to produce radiation resistors.
These different modes of operation are determined by the $RUN_CONTROL parameter.
For more information on these different modes of operation, see Description, 13, VFCTL, the Viewfactor Program Execution
Control File, 85, Review Directory for Required Files, 98 and Changing the Surface Template Data After Viewfactors are
Calculated (Ch. 7).
Main Index
Chapter 6: Post-Analysis 111
Interface From Viewfactor to Patran Thermal
Note: The following steps are automatically handled if execution is spawned from within the Patran analysis form.
$INSERT VFNODEDAT
This line must be in the QINDAT DEFNOD section, that is before the $ sign terminating the section and typically after
the $INSERT NODEDAT line.
The VFRESDAT radiation resistor data file should be included in the QTRAN QINDAT, VFMSG, the Viewfactor
Message File, 103: RESISTOR DATA SETS of the QINDAT file. This is done with the line
$INSERT VFRESDAT,RAD
A sample QINDAT file is shown with the parts relevant to the Viewfactor files VFRESDAT and VFNODEDAT shown
in bold. This example was created on a VAX VMS computer platform. If you have a different platform, see your
MSC.Patran Thermal User’s Guide, Volume 1: Thermal/Hydraulic Analysis for the system dependent file names.
Note: The QINDAT file is automatically created when execution is spawned from Patran and is described in the
MSC.Patran Thermal User’s Guide, Volume 1: Thermal/Hydraulic Analysis.
Main Index
112 Patran Viewfactor Analysis
Interface From Viewfactor to Patran Thermal
There are of course many different options in the translation process and they cannot all be presented here. The following
dialogue is typical of a PATQ translation. If errors are detected by PATQ, error messages will be written to the terminal
screen.
Main Index
Chapter 6: Post-Analysis 113
Interface From Viewfactor to Patran Thermal
Main Index
114 Patran Viewfactor Analysis
Interface From Viewfactor to Patran Thermal
Main Index
Chapter 6: Post-Analysis 115
Interface From Viewfactor to Patran Thermal
Main Index
116 Patran Viewfactor Analysis
noteplains on Resistor Values
Main Index
Chapter 6: Post-Analysis 117
THERMAL Analysis
Note: These commands are computer system dependent. They are the standard commands on a VAX/VMS system. If you
have a different system or have customized your installation, then your commands may be different. Refer to the
MSC.Patran Thermal User’s Guide, Volume 1: Thermal/Hydraulic Analysis or your system manager.
Main Index
118 Patran Viewfactor Analysis
THERMAL Results Postprocessing
Main Index
Chapter 7: Changing the Surface Template Data After Viewfactors are Calculated
Patran Viewfactor Analysis
Introduction 120
Compatible VFAC LBC and Template Data 121
New Resistors from Raw Viewfactor Data 122
Main Index
120 Patran Viewfactor Analysis
Introduction
7.1 Introduction
Viewfactor has been carefully designed to segregate the viewfactor calculations (which depend only on the geometry of
the model and are completely independent of the material properties) from that part of the program which creates the
Patran Thermal radiation resistors (by combining the viewfactors and material property data). This gives you the luxury
of calculating the viewfactors once for a given model. Then if you change materials or material properties, you can get the
new Patran Thermal radiation resistors without having to recalculate the viewfactors. The viewfactor calculations typically
take a lot of computer time. This capability provides a large saving in computer time for models in which the radiative
material properties are modeled for various levels of sophistication or for models in which various materials or surface
properties are being evaluated.
Main Index
Chapter 7: Changing the Surface Template Data After Viewfactors are 121
Calculated
Main Index
122 Patran Viewfactor Analysis
New Resistors from Raw Viewfactor Data
If the VFAC templates are changed, then Viewfactor must be rerun to recreate the Patran Thermal radiation resistors and
radiosity nodes.
Note that when you change the VFAC templates you need not recalculate the viewfactors. You only need to recreate the
resistor data. Instructions for running Viewfactor in this mode are given in Compatible VFAC LBC and Template Data, 121.
Once again, remember the compatibility requirements for VFAC LBCs and VFAC templates referred to in the previous
section and Patran Thermal TEMPLATEDAT Files for Surface Property Description, 52.
Changing VFCTL
If you wish to recreate Patran Thermal radiation resistors and radiosity nodes and not recalculate the viewfactors, then the
run control parameter, $RUN_CONTROL:, in the VFCTL file must be set to the value 2.
Main Index
Chapter 8: Theory and Computational Limitations
Patran Viewfactor Analysis
Main Index
124 Patran Viewfactor Analysis
Introduction
8.1 Introduction
The present Viewfactor program makes commercially available advances in the computer calculation of viewfactors and
obstruction for finite element thermal models developed at MSC.Software Corporation. These advances are principally:
1. Improved performance as measured by the product of speed and accuracy in determining obstructed views and
calculating viewfactors, and
2. A viewfactor analysis program designed specifically for finite element modeling.
Main Index
Chapter 8: Theory and Computational Limitations 125
Viewfactor
8.2 Viewfactor
The finite element model for the viewfactor associated with the ith node on surface e to the jth node on surface f is
represented by the following formula:
Nie N if ( r ef • n̂ e ) ( r ef • n̂ f ) dA e dA f
∫ ∫ e ∫ ∫ f ------------------------------------------------------------------------------------------------------------------ -
Fijef Z Ó π
A A r ef 4
-------------------------------------------------------------------------------------------------------------------------------------------------------------- (8-1)
e ⎛
dA e⎞⎟
⎜
∫ ∫ e Ni ⎝ ⎠
A
subject to the restrictions that ref does not intersect any view obstructing surfaces and the product
( r e f • n̂ e ) ( r ef • n̂ f ) is negative, and
e = Surface e ID
f = Surface f ID
i = Node ID on surface e
j = Node ID on surface f
Ae = Surface e area
Af = Surface f area
Primary variable finite element interpolation function associated with the ith
N ie =
node on surface e
Vector from a point on surface e to a point on surface f
r ef =
= Magnitude of a vector
The right-hand side of this equation is evaluated using numerical methods. The numerical integration scheme is
predominantly Gaussian quadrature. The quadrature order may be varied by the Viewfactor analysis program in an
attempt to obtain the desired accuracy. The method for estimating the accuracy of the numerical integration is, of course,
empirical, but seems to work very well. In general, if sufficient accuracy has not been obtained, then the quadrature order
will be increased in an effort to improve the accuracy. The quadrature order is not increased globally throughout the
integration domain, but only in those areas where the program determines the most benefit will result.
Main Index
126 Patran Viewfactor Analysis
Mean Beam Length
exp ( Ó κ r ef ) N ie Nif ( r ef • n̂ e ) ( r ef • n̂ f ) dA e dA f
∫ ∫ ∫ ∫ f ---------------------------------------------------------------------------------------------------------------------------------------------------------- -
π ef 4
I
o ijef Z Ó A e A r
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
e
(8-2)
⎛
⎜ dA e ⎞
⎟
∫ ∫ e Ni ⎝ ⎠
A
subject to the restrictions that ref does not intersect any view obstructing surfaces and the product
( r e f • n̂ e ) ( r ef • n̂ f ) is negative, and
e = Surface e ID
f = Surface f ID
i = Node ID on surface e
j = Node ID on surface f
Ae = Surface e area
Af = Surface f area
k media extinction coefficient
Primary variable finite element interpolation function associated with the ith
N ie =
node on surface e
Vector from a point on surface e to a point on surface f
r ef =
= Magnitude of a vector
For the optically thin media, the exponential function in the above equation may be approximated by:
N ie N if ( r ef • n̂ e ) ( r ef • n̂ f ) dA e dA f
∫ ∫ e ∫ ∫ f ------------------------------------------------------------------------------------------------------------------ -
Rijef Z Ó π
A A r ef 3
-------------------------------------------------------------------------------------------------------------------------------------------------------------- (8-4)
e ⎛ e⎞
⎜ dA ⎟
∫ ∫ e Ni ⎝ ⎠
A
Then in Patran Thermal the exchange factor is approximated by the equation:
I
o ijef Z e xp ( Ó κ R iejf )F ijef (8-5)
In this way the geometry of the model is isolated in the viewfactor and mean beam length quantities. The material
properties, such as the extinction coefficient, may be time and temperature dependent functions in Patran Thermal without
requiring recalculation of the viewfactor and mean beam length. This results in great saving of computer processing time.
Main Index
Chapter 8: Theory and Computational Limitations 127
Mean Beam Length
The assumptions made for the participating media model in Viewfactor and Patran Thermal are as follows:
1. The media is isothermal;
2. The media is in equilibrium with its internal energy;
3. The media extinction coefficient is not a function of position;
4. The optical thickness is small enough that the linear approximation of the exponential function is reasonable and
the media is only weakly interacting with itself.
Main Index
128 Patran Viewfactor Analysis
Obstructions
8.4 Obstructions
It is understood that the finite element discretization of the model geometry represents the finest geometric detail available
in the model. Therefore, surfaces are not subdivided beyond the nodal subareas for obstruction checking. This restriction
on obstruction checking may be viewed as a bit too severe. Different schemes have been tried. The error introduced by this
discretization of the obstruction checking process was compared with the error introduced in the viewfactors by the finite
element discretization. Considering the cost in computer execution time for a finer obstruction discretization, it was better
to limit the obstruction checking to nodal subareas.
You have control over the accuracy of the obstruction test in the usual way that accuracy in a finite element model is
controlled (i. e., by refining the finite element mesh). Thus, if more accuracy is needed in the obstruction checking, you
should refine the finite element mesh in the regions where greater accuracy is desired.
Main Index
Chapter 8: Theory and Computational Limitations 129
Computational Limitations
Spatial Resolution
The obstruction checking algorithm in Viewfactor is unable to detect potential obstructions which are very near one of
the surfaces for which the view between is being checked for obstructions. Here “very near” means that the distance from
the potential obstruction to one of the surfaces in the viewing pair is less than about one five-thousandth of the distance
between the pair of viewing surfaces. This situation is shown schematically in Figure 8-1.
Obstruction
Surface 1
Surface 2
<1 Unit
Distance
Extreme Scales
Models which have very large or very small numbers for their dimensions will cause an arithmetic overflow or underflow
condition to occur in Viewfactor. The approximate limits at which this occurs depends on the dimensionality of the
model. For the 2-D XY model, the limits are approximately the square root of the largest and smallest numbers
representable in the default FORTRAN single precision variable. For the 2-D RZ axisymmetric model, these limits are
approximately the cube root of the largest and smallest numbers representable in the default FORTRAN single precision
variable. For the 3-D XYZ model, these limits are approximately the fourth root of the largest and smallest numbers
Main Index
130 Patran Viewfactor Analysis
Computational Limitations
representable in the default FORTRAN single precision variable. If the user’s model has dimensions which exceed these
upper or lower limits it will be necessary to scale the model by a suitable factor in order to avoid arithmetic overflow or
underflow in Viewfactor. Viewfactor does not check for overflow and underflow conditions, since for most users this will
not be an issue.
Main Index
Chapter 9: Data File Specifications
Patran Viewfactor Analysis
Main Index
132 Patran Viewfactor Analysis
Introduction
9.1 Introduction
A computer programmer may wish to write an interface to the Viewfactor data files. These data file specifications are
intended to provide the information necessary. Unless you wish to examine the contents of these files, you don’t need to
be concerned with this chapter.
Main Index
Chapter 9: Data File Specifications 133
VFINDAT (Input Data File)
Examples
Here are two examples of model input files:
Main Index
134 Patran Viewfactor Analysis
VFINDAT (Input Data File)
Example 1
*Sample VFINDAT file.
$TITLE: TEST DATA SET 003
* DIMCOD NNODE1 NENCL1 MXNODN
$SIZE: 2 6 1 10
* NSYMOB
$SYM: 1
1.0 0.0 0.0
2.0 0.0 0.0
2.0 2.0 0.0
0.0 0.0 0.0
0.0 0.0 0.0
$ENDSYM:
$NODES:
1 0.0 0.0 0.0
2 1.0 0.0 0.0
3 1.0 1.0 0.0
4 0.0 1.0
9 0.6 0.6 0.0
10 1.6 0.6
$ENDNODES:
* ENCLID NSURF1
$ENCL: 1 4
1 7 1 2 2 1 0
0 0 1001 0 0 0 1
1.5 2.5
1 2
2 7 1 2 2 1 0
0 0 1001 0 0 0 1
1.5 2.5
2 3
3 7 1 2 2 1 0
0 0 1001 0 0 0 1
1.5 2.5
3 4
4 7 1 2 2 1 0
0 0 1001 0 0 0 1
1.5 2.5
4 1
$ENDENCL:
$EOF:
Main Index
Chapter 9: Data File Specifications 135
VFINDAT (Input Data File)
Example 2
*Sample VFINDAT file.
$TITLE: TEST DATA SET 001
* DIMCOD NNODE1 NENCL1 MXNODN
$SIZE: 3 12 2 12
* NSYMOB
$SYM: 0
$ENDSYM:
$NODES:
1 0.0 0.0 0.0
2 1.0 0.0 0.0
3 1.0 1.0 0.0
4 0.0 1.0 0.0
5 0.0 0.0 1.0
6 1.0 0.0 1.0
7 1.0 1.0 1.0
8 0.0 1.0 1.0
9 0.1 0.6 0.5
10 1.1 0.6 0.5
11 1.1 1.6 0.5
12 0.1 1.6 0.5
$ENDNODES:
* Beginning of first enclosure data.
* ENCLID NSURF1
$ENCL: 1 3
1 16 1 2 4 1 0
0 0 1001 0 0 0 1
1.5 2.5
1 2 3 4
2 16 1 2 4 1 0
0 0 1001 0 0 0 1
1.5 2.5
5 8 7 6
3 16 1 2 4 1 0
0 0 1001 0 0 0 1
1.5 2.5
1 5 6 2
$ENDENCL:
* Beginning of second enclosure data.
* ENCLID NSURF1
$ENCL: 17 2
5 16 1 2 4 1 0
0 0 1001 0 0 0 1
1.5 2.5
3 2 6 7
6 16 1 2 4 1 0
0 0 1001 0 0 0 1
1.5 2.5
1 4 8 5
$ENDENCL:
$EOF:_
Main Index
136 Patran Viewfactor Analysis
VFINDAT (Input Data File)
Detailed Descriptions
$TITLE
The first noncomment line must be:
$TITLE: title
Multiple $TITLE: lines are allowed, but they must all occur before the $SIZE: line. Comments between multiple $TITLE:
lines are allowed.
$SIZE
The $SIZE: card must be the next noncomment line. One and only one $SIZE: line is allowed. The format is:
Parameter Description
DimCode Code identifying geometric space of the model,
-2= Axisymmetric RZ,
2= 2-D XY,
3= 3-D XYZ;
#Node Number of nodes in this model (before symmetry operations);
#Encl Number of enclosures in this model (before symmetry operations);
MaxNod# Maximum node ID referenced in the model (before symmetry operations).
Parameter Description
#SymObj Number of symmetry objects defining symmetry operations for this model. The present maximum
allowed value is 4.
Immediately following and with no interspersed comments is the symmetry object numeric data, which
is read by:
Depending on the value of Type, the data for each symmetry object has different meanings.
Main Index
Chapter 9: Data File Specifications 137
VFINDAT (Input Data File)
For IFIX( Type ) = 1 this is a reflection in 2-D XY or RZ space about a line. The line is defined by
two distinct points, (X1,Y1) and (X2,Y2), on the line All other subarray elements should be set to 0.0.
For IFIX( Type ) = 2 this is a reflection in 3-D XYZ space about a plane defined by three distinct
points, (X1,Y1,Z1), (X2,Y2,Z2), and (X3,Y3,Z3), all on the plane and not colinear. All other subarray
elements should be set to 0.0.
For IFIX( Type ) = 3, this is a rotation about an axis and is valid in 2-D XY and 3-D XYZ spaces. The
positive axis of rotation by the right-hand rule is the vector from (X1,Y1,Z1) to (X2,Y2,Z2) and should
have nonzero length. For 2-D XY space, this axis must be perpendicular to the XY-plane. The model
will be replicated #Rot times by successively rotating #Rot times the model existing before any of these
rotations (but including that created by previous symmetry operations) Rot_Angle degrees about the
axis of rotation. All other subarray elements should be set to 0.0.
All other values of IFIX(Type) result in a fatal error in P/VF. Only certain combinations of symmetry
object types are valid. The valid combinations depend on the model space, as identified by DimCode.
In general, symmetry object validity is not checked by P/VF.
For 2-D RZ space (DimCode = -2), the only valid symmetry object is Type = 1 (line) and this line
must be perpendicular to the Z-axis. Only one such symmetry object is permitted in 2-D RZ space.
For 2-D XY space (DimCode = 2), only types 1 (line) and 3 (rotation) are valid. Not more than one
type 3 object is permitted. Not more than two type 1 objects are permitted. Type 1 objects should be in
the XY-plane. Type 3 objects should be perpendicular to the XY-plane. If there are two type 1 objects,
they should be mutually perpendicular.
For 3-D XYZ space (DimCode = 3), only symmetry object types 2 (plane) and 3 (rotation) are valid.
Not more than one type 3 object is permitted. Not more than three type 2 objects are permitted. Two or
more type 2 objects must be mutually perpendicular.
Comments may follow the symmetry object data, but may not occur between the $SYM: keyword line
and the end of the symmetry object numeric data.
The next required keyword line is $ENDSYM:. This line contains no other data. If there are no
symmetry objects, the $SymObj is zero and the required data is:
$SYM: 0
$ENDSYM:
Main Index
138 Patran Viewfactor Analysis
VFINDAT (Input Data File)
Parameter Description
EnclID The ID number of this enclosure.
#Surf Number of surfaces in this enclosure.
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:
( 7 ( I10 ) ), ( SurAtt( J ), J = 1, MaxAtt )
Parameter Description
MaxAtt Maximum number of surface attributes supported = 14;
SurAtt Array of surface attributes whose elements are:
This pattern is repeated for each surface in the enclosure. Comments may follow the last line of the last surface data.
The next keyword line is $ENDENCL: with no data.
Main Index
Chapter 9: Data File Specifications 139
VFINDAT (Input Data File)
The pattern:
is repeated for any additional enclosures. The number of enclosure data sets should equal the #Encl data from the $SIZE:
line. This is not a fatal error here since discrepancies will not be detected until the enclosures have been processed
(viewfactors calculated). A warning message will be issued and attempts to create resistors for the viewfactor data may
have undesirable results.
$EOF
The last keyword line is $EOF: with no data. Comments may follow the $EOF: line.
Main Index
140 Patran Viewfactor Analysis
VFRAWDAT (Raw Viewfactor Data)
VFRAWDAT==::[{(Nchar)(Comment_String)}]*
{(Nchar)(Title_String)}
[
[{(Nchar)(Comment_String)}]*
{(Nchar)(Title_String)}]
]*
[{(Nchar)(Comment_String)}]*
{(Nchar)(Size_String)}
[{(Nchar)(Comment_String)}]*
{(Nchar)(Symmetry_String)}
[{(Symmetry_Data)}]*Number_Symmetry_Objects
[{(Nchar)(Comment_String)}]*
{(Nchar)(End_Symmetry_String)}
[{(Nchar)(Comment_String)}]*
{(Nchar)(Begin_Node_Data_String)}
[
[{Node_Data_Record}]*Symmetry_Multiplier
*Number_Nodes
[{(Nchar)(Comment_String)}]*
{(Nchar)(End_Node_Data_String)}
[
[{(Nchar)(Comment_String)}]*
{(Nchar)(Begin_Enclosure_String)}
{(Number_User_ID)}
[{(User_ID)}]*Number_User_ID
[
[{(Surface_Data)}]*Symmetry_Multiplier
]*Number_Surfaces
[
[
[{(Surface_Pair_Record)}
[{(View_Factor_Data)}]*If_Can_See
]*Symmetry_Multiplier
]*Upper_Number_Surfaces
{(Sum_View_Factor_Data)}
]*Number_Surfaces
[{(Nchar)(Comment_String)}]*
{(Nchar)(End_Enclosure_String)}
]*Number_Enclosures
[{(Nchar)(Comment_String)}]*
{(Nchar)(End_File_String)}
(EOF)
Main Index
Chapter 9: Data File Specifications 141
VFRAWDAT (Raw Viewfactor Data)
Parameter Description
Nchar Integer number of characters in the following character string, less than 132.
Comment_String Character string beginning with the blank character or the * character.
Title_String Character string beginning with the characters $TITLE: and followed by optional title
characters. Maximum length is 80 characters.
Size_String Character string beginning with the characters $SIZE: and containing the following data in the
(A6,4X,4I10) format: Dimension_Code, Number_Nodes, Number_Enclosures, and
Max_Node_ID.
Dimension_Code
Main Index
142 Patran Viewfactor Analysis
VFRAWDAT (Raw Viewfactor Data)
Parameter Description
SURDAT - SURATT number four reals, see the description of surface data in the
VFINDAT file specification.
SURDAT - SURATT number four reals, see the description of surface data in the VFINDAT
file specification.
SURNOD - SURATT number five integers giving the nodes on this surface and in the order
specified for the corresponding Patran Plus elements.
SURARA - SURATT number five plus one reals giving the surface area and the nodal subareas
for this surface.
LFTHND - Logical, true is surface has left handed orientation.
Surface_Pair_ (Surface_E_Index)(Surface_F_Index)(Symmetry_Index)
Record (Subdivision_Index)(Number_Subdivision)(Can_See_Flag)
Surface_E_Index - Integer index to the first surface in the pair.
Surface_F_Index - Integer index to the second surface in the pair.
Symmetry_Index - Integer index to the symmetric image of the second surface.
Subdivision_Index - Integer index to the surface subdivision, not currently used.
Number_Subdivision - Integer number of subdivisions of the surface, not currently used.
Can_See_Flag - Logical, set true if View_Factor_Data is to follow.
If_Can_See Not a formal item in the VFRAWDAT file. It is used to indicate the number of
View_Factor_Data records that should follow. If_Can_See is set to one if Can_See_Flag is true
and set to zero otherwise.
View_Factor_Data [
(Nodal_Can_See)(Nodal_View_Factor).
(Nodal_Mean_Beam_Length).
]*Number_Nodes_Surface_E.
]*Number_Nodes_Surface_F.
Nodal_Can_See - Logical that node on surface E can see node on surface F.
Nodal_View_Factor - Real value of the viewfactor from nodal subarea on surface E to nodal
subarea on surface F.
Nodal_Mean_Beam_Length - Real value of the mean beam length from nodal subarea on
surface E to nodal subarea on surface F.
Number_Nodes_Surface_E - SURATT number five for surface E.
Number_Nodes_Surface_F - SURATT number five for surface F.
Upper_Number_ Number_Surfaces minus the current outer repeat structure index minus one. This provides the
Surfaces upper triangular portion of the surface pair matrix as the part for which the VFRAWDAT file
contains data.
Sum_View_Factor_ (SUMSUR)(SUMONE)(SUMZRO)(SUMNOD).
Data
SUMSUR - Real value containing the sum of the viewfactors from this surface to all other
surfaces in this enclosure.
SUMONE - Real value equal to one minus SUMSUR.
SUMZRO - Real value containing the sum of all viewfactors from this surface to all other
surfaces which were set to zero by virtue of being less than the zero cutoff value.
SUMNOD 7- [Real value containing the sum of the viewfactors from this nodal subarea on
surface E to all other nodal subareas on all other surfaces in this enclosure]*.
Number_Nodes_Surface_E.
Main Index
Chapter 9: Data File Specifications 143
VFRAWDAT (Raw Viewfactor Data)
Parameter Description
End_Enclosure_ Character string containing the characters $ENDENCL:
String
End_File_String Character string containing the characters $EOF:
EOF FORTRAN ENDFILE marker.
Character FORTRAN CHARACTER*(*) Type with length less than 132 characters.
Logical FORTRAN default LOGICAL Type.
Integer FORTRAN default INTEGER Type.
Real FORTRAN default REAL Type.
Main Index
144 Patran Viewfactor Analysis
VFRESDAT (Resistor Data)
Main Index
Chapter 9: Data File Specifications 145
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).
Main Index
146 Patran Viewfactor Analysis
VFDIAG (Diagnostic Data)
Examples
Here are two examples of model diagnostic files:
Example 1
$TITLE: PDA Viewfactor VER. 2.3 7-JUN-88 16:14:05
$TITLE: PARALLEL SEMIINFINITE PLATES OPEN TO LEFT AND RIGHT.
$TITLE: PARALLEL PLATES, SIMPLE, FINE, LINEAR HEAT AT NODES.
$TITLE: 28-MAR-88 08:30:09 2.2K-X
$ENCL: 1 18 1
1 0.8375167847E+00 0.1624832153E+00 0.0000000000E+00
0.8469786048E+00 0.8280547857E+00
2 0.7995740771E+00 0.2004259229E+00 0.0000000000E+00
0.8067734241E+00 0.7923747301E+00
3 0.7514496446E+00 0.2485503554E+00 0.0000000000E+00
0.7604730725E+00 0.7424262762E+00
4 0.6918253303E+00 0.3081746697E+00 0.0000000000E+00
0.7027459145E+00 0.6809046268E+00
5 0.6208980680E+00 0.3791019320E+00 0.0000000000E+00
0.6335698366E+00 0.6082264185E+00
6 0.5413827300E+00 0.4586172700E+00 0.0000000000E+00
0.5551127791E+00 0.5276526213E+00
7 0.8375174403E+00 0.1624825597E+00 0.0000000000E+00
0.8280556202E+00 0.8469793200E+00
8 0.7995739579E+00 0.2004260421E+00 0.0000000000E+00
0.7923744321E+00 0.8067733645E+00
9 0.7514500618E+00 0.2485499382E+00 0.0000000000E+00
0.7424264550E+00 0.7604734898E+00
10 0.6918258667E+00 0.3081741333E+00 0.0000000000E+00
0.6809051633E+00 0.7027463317E+00
11 0.6208983064E+00 0.3791016936E+00 0.0000000000E+00
0.6082265377E+00 0.6335700154E+00
12 0.5413829088E+00 0.4586170912E+00 0.0000000000E+00
0.5276528001E+00 0.5551129580E+00
13 0.6211041212E+00 0.3788958788E+00 0.0000000000E+00
0.6090478897E+00 0.6331601143E+00
14 0.5795320272E+00 0.4204679728E+00 0.0000000000E+00
0.5738914013E+00 0.5851726532E+00
15 0.5567277074E+00 0.4432722926E+00 0.0000000000E+00
0.5546888113E+00 0.5587666035E+00
16 0.5567269325E+00 0.4432730675E+00 0.0000000000E+00
0.5587658286E+00 0.5546880364E+00
17 0.5795311928E+00 0.4204688072E+00 0.0000000000E+00
0.5851718783E+00 0.5738904476E+00
18 0.6211042404E+00 0.3788957596E+00 0.0000000000E+00
0.6331602335E+00 0.6090482473E+00
0.4586173E+00 0.3333322E+00 0.1052845E+00 0.3333322E+00 0.1052845E+00
0.4723472E+00 0.3333322E+00 0.1057708E+00 0.3333322E+00 0.1057708E+00
0.4723474E+00 0.3333322E+00 0.1057709E+00 0.3333322E+00 0.1057709E+00
$ENDENCL:
$EOF:
Main Index
Chapter 9: Data File Specifications 147
VFDIAG (Diagnostic Data)
Example 2
$TITLE: PDA Viewfactor VER. 2.3 7-JUN-88 16:14:05
$TITLE: THIS IS A TEST.
$TITLE: TEST DATA SET 001
$ENCL: 1 9 1
1 0.1000062227E+01 -0.6222724915E-04 0.0000000000E+00
0.9988046288E+00 0.1027215719E+01 0.9741664529E+00
2 0.1000062227E+01 -0.6222724915E-04 0.0000000000E+00
0.1011101127E+01 0.1010952711E+01 0.9781325459E+00
3 0.1000062227E+01 -0.6222724915E-04 0.0000000000E+00
0.1046023250E+01 0.9557061195E+00 0.9984572530E+00
4 0.1000062227E+01 -0.6222724915E-04 0.0000000000E+00
0.1070914149E+01 0.9665873647E+00 0.9626849890E+00
5 0.1000062227E+01 -0.6222724915E-04 0.0000000000E+00
0.9566107392E+00 0.1043834686E+01 0.9997408986E+00
6 0.1000062227E+01 -0.6222724915E-04 0.0000000000E+00
0.1043245673E+01 0.9702598453E+00 0.9866808653E+00
7 0.1000062346E+01 -0.6234645844E-04 0.0000000000E+00
0.9536437988E+00 0.9969801307E+00 0.1027588487E+01 0.1022036433E+01
8 0.1000062346E+01 -0.6234645844E-04 0.0000000000E+00
0.1031251073E+01 0.9417309761E+00 0.9850846529E+00 0.1042182207E+01
9 0.1000062346E+01 -0.6234645844E-04 0.0000000000E+00
0.9940649271E+00 0.9654292464E+00 0.1021910191E+01 0.1018844128E+01
0.6234646E-04 -0.6226698E-04 0.5960464E-07 0.6226698E-04 0.5960464E-07
0.7091415E-01 -0.1173993E-01 0.4022554E-01 0.3326791E-01 0.2297935E-01
0.5826902E-01 0.1347813E-01 0.3483813E-01 0.3170105E-01 0.1695543E-01
0.3731501E-01 0.7283741E-02 0.2151740E-01 0.1828345E-01 0.1210838E-01
0.4218221E-01 -0.9229196E-02 0.1522104E-01 0.9229196E-02 0.1522104E-01
$ENDENCL:
$EOF:
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.
Main Index
148 Patran Viewfactor Analysis
VFDIAG (Diagnostic Data)
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.
$EOF
The last keyword line is $EOF: with no data. Comments may follow the $EOF: line.
Main Index
Chapter 9: Data File Specifications 149
TEMPLATEDAT (Surface Pointer Data)
VFAC Template==::[{(Comment)}]*
{(VFAC Template Header)}
[[{(Comment)}]*
{(VFAC Template Data)}]*MAX(1,nbands)
Comment==::((;)|(*))[(anything)]
VFAC Template Header
==::[(del)](VFAC)(del) (TID)[((del)(nbands)
[((del)|(;))[(anything)]])|([(del)][(;)[(anything)]](CRLF)
and the length of the VFAC Template Header must be less than or equal to 80 characters.
VFAC Template Data
==::[(del)](epsilon)[(del)[(tau)[(del)[(empid)[(del)[(tmpid)
[(del)[(lambda1)(del)(lambda2)[(del)[(kflag)[(del)[(collapse)
[((del)|(;))[(anything)
]]]]]]]]]]]]]]
[[(del)](;)[(anything)]]
(CRLF)
and the length of the VFAC Template Data must be less than or equal to 80 characters.
Parameter Description
del (,|blank)[(blank)*]
VFAC VFAC|'VFAC
V V|v
F F|f
A A|a
C C|c
TID positive integer
nbands non-negative integer, default = 0
anything any character string representable on the machine
CRLF carriage return line feed
epsilon real
tau real, default = 1.0
empid integer, default = 0
tmpid integer, default = 0
lambda1 real, default = 0.0
lambda2 real, default = 0.0
kflag integer, default = 0
collapse non-negative integer, default = 0
Main Index
150 Patran Viewfactor Analysis
TEMPLATEDAT (Surface Pointer Data)
real Real number representable on the machine in default real type variable and having 20 or less
digits, including +, -, ., E, etc. Default format is G20.10
integer Integer number representable on the machine in default integer type variable and having 20 or
less digits, including +, -, etc.
In addition to the above form requirements, only certain combinations of data values are valid. These are determined by
the following tests:
1. If nbands equals 0 and either lambda1 not equal to 0.0 or lambda2 not equal to 0.0, then this is an error.
2. If nbands greater than 0 and either lambda1 greater than or equal to lambda2 or lambda 1 less than 0.0, then this is
an error.
3. If kflag is not equal to 0 or 1, then this is an error.
4. If empid equals 0 and either epsilon is less than or equal to 0.0 or epsilon is greater than 1.0, then this is an error.
5. If empid is not equal to 0 and epsilon is not equal to 0.0, then this is an error.
6. If tmpid equals 0 and kflag equals 0 and either tau is less than or equal to 0.0 or tau is greater than 1.0, then this is
an error.
7. If tmpid equals 0 and kflag equals 1 and tau is less than 0.0, then this is an error.
8. If tmpid is not equal to 0 and tau is not equal to 0.0, then this is an error.
Additionally, an error will occur in Viewfactor if tmpid is not equal to 0, and there is not a MEDNOD available with the
referenced surface or if kflag equals 1, and an AMBNOD is associated with the reverenced surface.
Main Index
Chapter 9: Data File Specifications 151
VFNODEDAT (Radiosity Node Lists)
Main Index
152 Patran Viewfactor Analysis
VFNODEDAT (Radiosity Node Lists)
Main Index
Chapter 10: Rules for Radiation Resistors
Patran Viewfactor Analysis
Main Index
Chapter 10: Rules for Radiation Resistors 154
Introduction
10.1 Introduction
Viewfactor uses rules to determine which Patran Thermal radiation resistors to make. Which resistors are made depends
on the data in the VFAC Templates and VFRAWDAT file. This chapter describes these rules. Restrictions on the valid
ranges of data in the VFAC Templates is described in the previous chapter in the section on the VFAC Template data
specification, VFRAWDAT (Raw Viewfactor Data), 140. These will not be repeated here.
Main Index
Chapter 10: Rules for Radiation Resistors 155
General Rules for Radiation Resistors
Main Index
Chapter 10: Rules for Radiation Resistors 156
Rules for Emissivity Resistors
Main Index
Chapter 10: Rules for Radiation Resistors 157
Rules for Radiosity Resistors
Main Index
Chapter 10: Rules for Radiation Resistors 158
Rules for Radiosity Resistors
Main Index
Chapter A: Typical Errors and Probable Causes for Viewfactor Errors
Patran Viewfactor Analysis
Purpose 2
Main Index
2 Patran Viewfactor Analysis
Purpose
A.1 Purpose
Viewfactor performs extensive error checking and reporting. It utilizes an error message generator which creates error
messages as needed from phrases stored in memory. In general, these error messages provide more information than we
could supply with a reasonable number of error codes. Error messages, if any, will be found in the VFMSG file, along with
a traceback of the subroutine calling sequence leading to the error condition. This traceback is provided because
Viewfactor was designed to terminate normally, even under error conditions. It is the only way for us to know the program
status associated with ^an error.
Some typical errors and their probable causes are:
File Errors These occur when an expected file is not present or available to the program, or a file
to be created is already present. The solution is to make the expected file available or
to remove or rename the file already present. The files referenced may also be changed
by altering the names given in the VFCTL file.
Format Errors This means the data in a file is not in an acceptable format. This usually occurs with the
TEMPLATEDAT file since this is usually the only data file which the user must build
using the system editor.
UID/TID Errors Reference UIDs are not available in the VFAC TIDs. This error is corrected by adding
the appropriate VFAC TID records to the TEMPLATEDAT file.
Surface The properties assigned by the VFAC DFEG data and VFAC Template data to a pair of
Incompatibility surfaces which can see each other in an enclosure are not compatible. For example, the
Errors surfaces might have a different number of wavebands assigned to each. For additional
information, you can refer to Compatibility Requirements for Model and
VFAC Templates, 65 and Introduction, 120 which address surface compatibility.
Note: Please refer back to Submitting a Viewfactor Job for Analysis, 98 and recheck each item called
out for review prior to submitting a Viewfactor job.
Main Index
Chapter B: Quick Reference Guide to Viewfactor
Patran Viewfactor Analysis
Main Index
4 Patran Viewfactor Analysis
Purpose
B.1 Purpose
The general procedure for performing a thermal radiation analysis is:
Parameter Description
MEDNOD Participating media node if any Flag for top or bottom of shell.
AMBNOD Ambient or space node.
The surfaces on which the VFAC boundary conditions are applied are defined under Application Region.
The VFAC Template in the Patran Thermal TEMPLATEDAT file has the form:
VFAC, TID, nbands
epsilon, tau, empid, tmpid, lambda1, lambda2, kflag, collapse
Parameter Description
tau Real, Optional, Default = 1.0, Participating media transmissivity (kflag = 0) or extinction
coefficient (kflag = 1).
empid Integer, Optional, Default = 0, Emissivity material property ID.
kflag Integer, Optional, Default = 0, Flag that tau or tmpid refer to transmissivity (kflag = 1) or to
extinction coefficient (kflag = 1).
Main Index
Chapter B: Quick Reference Guide to Viewfactor 5
Purpose
Parameter Description
collapse Integer, Optional, Default = 0, ID to control the collapsing of radiosity nodes associated with
a surface node.
The line,
epsilon, tau, empid, tmpid, lambda1, lambda2, kflag, collapse
must be repeated for each of the nbands in the template and once for nbands = 0.
The Viewfactor command line is:
VSUBMIT VFCTL
Note: This command is automatically issued when execution is spawned from within Patran.
Main Index
6 Patran Viewfactor Analysis
Purpose
The VFCTL file contains information to control the execution of Viewfactor. If no filename is given, a default VFCTL file
on your system will be used. This default file may have been altered on your system. The default VFCTL file supplied
with Viewfactor is:
Note: The above parameters have been defaulted in the Analysis form, Viewfactor Solution Parameters.
Main Index
Chapter C: Memory Requirements for Viewfactor Execution
Patran Viewfactor Analysis
Purpose 8
Main Index
8 Patran Viewfactor Analysis
Purpose
C.1 Purpose
Viewfactor has fixed memory requirements for about 820 K bytes on the VAX 8600. In addition to this memory,
Viewfactor calculates the amount of memory needed based on the number of nodes in the model, number of surfaces in
the current enclosure, dimensionality of the model, number of symmetric images and number and size of the VFAC
templates.
The memory requirement for calculating viewfactors also depends on the number of potentially obstructing surfaces in the
enclosure and on a few other parameters in a complicated manner. Therefore, we will only give an upper bound on the
memory requirement. The memory required, in bytes, to calculate viewfactors will be less than approximately the value
of the expression:
The memory requirement for converting viewfactors into Patran Thermal radiation resistors
depends on the number of resistors to be created in an enclosure. The virtual memory system will
request enough memory to hold all of the resistors created in an enclosure before any of the
resistors have been merged. Since the number of resistors created depends on the viewfactors
calculated, we do not know in advance how much memory will be required.
Viewfactor was designed to access as much memory as needed through the computer’s virtual
memory system. Viewfactor will handle as large of problem as there is virtual memory available
for it to use. Also note that the memory requirements are linear with respect to the number of
surfaces in each enclosure and also linear with respect to the number of nodes in the model. Thus,
in general, computer memory will not be the limiting resource for viewfactor analysis with
Viewfactor. However, a large amount of memory may be needed for sorting and merging the
resistors made after the viewfactor calculations.
NVFAC Number of VFAC templates found in the TEMPLATEDAT file.
TOTBND total number of bands, or VFAC template data records (not header record found in the
TEMPLATEDAT file.
NUID Number of distinct UIDs (User IDs) in the current enclosure.
Viewfactor was designed to access as much memory as needed through the computer‘s virtual memory; it will handle as
large of problem as there is virtual memory available for it to use. Also note that the memory requirements are linear with
respect to the number of surfaces in each enclosure and with respect to the number of nodes in the model. Thus, in general,
computer memory will not be the limiting resource for viewfactor analysis with Viewfactor.
Main Index
Chapter D: Machine-Specific File Names for Viewfactor
Patran Viewfactor Analysis
Purpose 10
Main Index
10 Patran Viewfactor Analysis
Purpose
D.1 Purpose
This document uses generic filenames. The generic names may be translated to machine specific names by use of the
following table.
Main Index
Chapter E: Example Thermal Radiation Problems
Patran Viewfactor Analysis
Purpose 12
Problem 1 - Steady-State Radiative Boundary Conditions 13
Problem 2 - Parallel Semi-Infinite Plates 32
Problem 3 - Heated Reaction Chamber 35
Main Index
12 Patran Viewfactor Analysis
Purpose
E.1 Purpose
These examples are simple problems designed to demonstrate the thermal radiation analysis process. The first example,
steady-state radiative boundary conditions, is a two-enclosure radiative model. The second, parallel semi-infinite plates,
is an idealized situation for which the correct thermal solution is known. The third example, more representative of a real
world problem, models the interior of a reaction chamber.
In the first example, a step-by-step model definition is given, including figures showing the Patran forms. For the
subsequent examples, to avoid repeating the forms, only the significant model data is given.
Main Index
Chapter E: Example Thermal Radiation Problems 13
Problem 1 - Steady-State Radiative Boundary Conditions
Objectives
In this lesson you will perform the following tasks:
• Construct a 2D model that incorporates two enclosures.
• Define separate radiative boundary conditions for gray body and wavelength-dependent radiation within the
enclosures.
• Perform the Steady-State thermal analysis and postprocess the analysis results with Patran’s Result tools.
Model Description
In this lesson you will construct a model with two separate radiation enclosures: one for gray body radiation and the other
for wavelength-dependent radiation. No material (e.g., air) will be defined in the enclosure; therefore, only Radiation
heat transfer can transfer heat energy across the enclosures. In the enclosure where it is assumed that the surfaces are
gray, the emissivity will be constant regardless of the surface temperatures. The other enclosure will incorporate
wavelength-dependent radiation which is a significant extension of the gray body theory. Normal radiosity is divided into
discrete frequency bands with emissivity and transmissivity assumed to be gray within these frequency bands.
o
1500 C (fixed)
Iron
0.5
2.0
o Node 1000
0 C (fixed) o
T=200 C (fixed)
Enclosure Emissivity Information:
Main Index
14 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
Exercise Procedure
1. Start Patran and create a New Database named, exercise_13.db.
2. Set the Tolerance to Default and the Analysis Code to THERMAL Vol. 2-Viewfactor Analysis.
3. To create the geometry of the enclosure model clicking on the Geometry toggle in the main form. Set the Action,
Object, and Method respectively to Construct, Patch, and XYZ. Change the Vector and Origin Coordinate Lists
to <0.3, 0.5, 0.0> and [0, 0, 0] respectively. Click on the Apply button to create the patch that
represents the bottom left region of the model.
Before creating the next piece of the model set the Display Lines to zero.
To create the next region of the model change the Vector Coordinate List to <0.5, 0.5, 0> click in the Origin
Coordinate List, and select Point 4 in the viewport.
Using the above construction technique complete the remaining portion of the model’s geometry.
Your completed patch geometry should look similar to that shown below.
4. Next, you will mesh the 13 patches using the ISO mesher.
Main Index
Chapter E: Example Thermal Radiation Problems 15
Problem 1 - Steady-State Radiative Boundary Conditions
Click on the Finite Elements Toggle in the main form. Change the Object to Mesh. Specify a Global Edge Length of
0.16666 for the QUAD 4 elements. The completed Finite Elements form and meshed model are shown below for your
reference.
Finite Elements
Action: Create
Object: Mesh
Type: Surface
Output Ids
Node Id List
1
Element Id List
1
Element Topology
Quad4
Quad5
Quad8
Mesher
IsoMesh Paver
IsoMesh Parameters...
Surface List
Surface 1:13
-Apply-
Main Index
16 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
To simplify the visual image of your model, turn off all entity labels. Your model should now look like the one shown
below.
5. To equivalence your model, change the Finite Element form’s Action, Object, and Type respectively to
Equivalence, All, and Tolerance Cube. Click on the Apply button to equivalence the finite elements.
6. The model’s Enclosure 2 (hole on the right-hand side) will contain a medium that will participate in the radiation
heat transfer occurring throughout that enclosure.
Main Index
Chapter E: Example Thermal Radiation Problems 17
Problem 1 - Steady-State Radiative Boundary Conditions
To thermally represent the participating medium, create a Node within the enclosure. Use 1000 as its ID and create the
node so that it is not associated with the model’s geometry. Use the Select a Screen Position option in the select menu to
select a point inside Enclosure 2. Your completed Finite Elements form should look similar to the one shown below.
Finite Elements
Action: Create
Object: Node
Method: Edit
Node Id List
1000
Auto Execute
Node Location List
[1.364971 0.836337 0.00
-Apply-
Main Index
18 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
To better visualize the Node locations, set their radius to 6 pixels. Your model should now look like the one shown below.
7. You will now create the required boundary conditions for your model.
Main Index
Chapter E: Example Thermal Radiation Problems 19
Problem 1 - Steady-State Radiative Boundary Conditions
Existing Sets
Add Remove
Application Region
Spatial Fields
Node 1000
New Set Name
Temp_Participating_medi
Input Data...
Select Application Region...
OK Reset
OK
-Apply-
Next, assign fixed temperatures of 1500°C and 0°C respectively to the top and bottom geometry edges of the model.
Use T_top and T_bottom for their respective New Set Names. The completed forms are shown below for your reference.
Main Index
20 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
Input Data...
Select Application Region...
OK Reset OK
-Apply-
Main Index
Chapter E: Example Thermal Radiation Problems 21
Problem 1 - Steady-State Radiative Boundary Conditions
Input Data...
Select Application Region...
OK Reset OK
-Apply-
103 203
102 104 202 204
101 201
Main Index
22 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
Enclosure ID 1 1 1 1
Enclosure ID 2 2 2 2
You will now complete the Viewfactor definitions by entering the Emissivity and Transmissivity information into the
template.dat file. Create a separate x-window shell and make a subdirectory in the directory you are running Patran. Use
your current Patran database name for this subdirectory name. Change to that subdirectory, open and edit a file named
template.dat. Next, enter the required VFAC commands to define the Emissivity and Transmissivity for Enclosures
1 and 2. The syntax of the command is:
Main Index
Chapter E: Example Thermal Radiation Problems 23
Problem 1 - Steady-State Radiative Boundary Conditions
Each term of the command is defined in Chapter 3 of the MSC Patran Thermal User’s Guide. Shown below is a table
that lists the required information for the two VFAC commands and the template.dat file created with this information
for your reference.
TID NBANDS e t εid τid λ1 λ2 K flag Collapse
100 0 0.9 1 0 0 0 0 0 1
200 2 0.9 0.4 0 0 0 5 0 1
0.2 0.4 0 0 5 1E6 0 1
Your model with its applied boundary conditions should now look like the one shown below.
8. Before you set up and run the thermal analysis you must first define the Element Properties for the models Iron
material.
To do this, click on the Element Props toggle in the main form. When the form appears set its Action, Dimension, and
Type option menus respectively to Create, 2D, and Thermal 2D. Enter Iron, for the New Set Name and then click on
the Input Properties… button. Enter 18 in the Material Name databox and then click on the OK button to close the
Main Index
24 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
form. Next, click in the Select Members box and select all the models Patches in the viewport. Finally click on the Apply
button in the Element Properties form. The completed forms are shown below for your reference.
Element Properties
Action: Create
Input Properties
Dimension: 2D 2D
Type: Thermal 2D Property Name Value Value Type
Application Region
Material Property Sets
Select Members
Add Remove
Application Region
OK
-Apply-
Main Index
Chapter E: Example Thermal Radiation Problems 25
Problem 1 - Steady-State Radiative Boundary Conditions
button. In the Select Viewfactor Solution frame, select the 0, Viewfactors --> Resistors option. Click on the OK button
to close the form.
OK Defaults Cancel
Main Index
26 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
In the Analysis form, click on the Solution Parameters… button. In the P⁄Thermal Solution Parameters form, set the
Calculation Temperature Scale to Celsius and select 0, Standard Solution for the Solver Option. Click on the OK button
to close the P/Thermal Solution Parameters form.
Convergence Parameters...
Iteration Parameters...
Relaxation Parameters...
OK Defaults Cancel
In the Analysis form, click on the Output Requests… button. In the P⁄Thermal Output Request form, set the Units Scale
for Output Temperatures to Celsius. Click on the Print Intervals Controls… button. When the P⁄Thermal Print Intervals
Main Index
Chapter E: Example Thermal Radiation Problems 27
Problem 1 - Steady-State Radiative Boundary Conditions
Control form appears, set the Initial Print Interval to 5. This will cause P/Thermal to print out solution information every
5 intervals. Click on the OK button in both forms.
Diagnostic Output...
OK Defaults Cancel
Main Index
28 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
11. Click on the Results toggle in the Top Menu Bar. When the Results form appears display the temperature
distribution across the model. Your model should now look like the one shown below.
As expected the temperature distribution is not horizontally symmetrical due to the different radiation boundary conditions
in each enclosure.
12. Temperature contours can be created and the temperature at each node can be determined by creating Contour and
Cursor tools.
Main Index
Chapter E: Example Thermal Radiation Problems 29
Problem 1 - Steady-State Radiative Boundary Conditions
To do this, set the Action and Object, to Create and Contour, respectively. Click on the Results Selection… button and
select 1.1 Temperature, (nodal) from the Contour Results List Box. Click on the OK button to close the from. Click on
the Apply to create the Temperature Contours. Your model should now look similar the one shown below.
To create Cursor tool change the Object to Cursor and then click on the Results Selection… button. Again select 1.1-
Temperature, (nodal) in the Cursor Results list and click on OK to close the form. Click on the Apply button to create
the Cursor Tool. When the Cursor Tool form appears click on the Apply button. Next, click somewhere on the model.
Main Index
30 Patran Viewfactor Analysis
Problem 1 - Steady-State Radiative Boundary Conditions
You should see the temperature of the Node nearest to the mouse cursor printed on the model and in the Cursor Results
form. Your model should now look similar to the one shown below.
Main Index
Chapter E: Example Thermal Radiation Problems 31
Problem 1 - Steady-State Radiative Boundary Conditions
An example Cursor Results form and its corresponding temperature locations are shown below for your reference.
Main Index
32 Patran Viewfactor Analysis
Problem 2 - Parallel Semi-Infinite Plates
Patch 2
Patch 1
By appropriate specification of boundary conditions, we will create symmetry in the heat flux from the plates to the
ambient environment from the openings to the left and right. Only the facing surfaces of the plates will be able to radiate
thermal energy. All other surfaces will be perfectly insulated. Also, the plates will be thin and good insulators themselves.
Thus, other modes of heat transfer, such as conduction and convection, may be neglected. A heat flux varying along the
width of each plate will be imposed on the radiating face of each plate. The variation in heat flux from left to right on the
bottom plate’s face will be the same as the variation from right to left on the top plate’s face. In this example, we will use
a linear ramp variation.
The plates will radiate to each other and to the ambient environment at the left and right. By symmetry arguments, the total
energy radiated to the ambient environment on the left and on the right should be equal. By conservation of energy their
sum must equal the heat flux applied to the plates’ surfaces.
As in the previous example, we will model one of the openings to the ambient environment as an ambient surface. Note
that this ambient surface is not connected to the plates. The other opening in the enclosure to the ambient environment will
be modeled with an ambient node.
Note that each surface, the top plate, the bottom plate, and the ambient surface, is convex. The material with MPID 693
used for this problem is a mica brick. The model files for this example were delivered with Patran and should be available
on your computer system by typing ‘get_view’ and selecting the directory ‘pplate’. For assistance in locating these files,
Main Index
Chapter E: Example Thermal Radiation Problems 33
Problem 2 - Parallel Semi-Infinite Plates
please contact your system administrator. You may wish to experiment with other geometric dimensions, heat fluxes, and
ambient temperatures.
A Patran Thermal TEMPLATEDAT file is needed. You might use the one from the previous example, editing the
comments. A TEMPLATEDAT file is shown below.
TEMPLATEDAT File
MID 693 69301 69301 69301 69304 69305 0
* SURFACE PROPERTIES OF THE PARALLEL PLATES, PATCHES 1 AND 2
VFAC 11 0
0.8
* SURFACE PROPERTIES OF THE AMBIENT SURFACE, PATCH 3
VFAC 12 0
1.0
Likewise a Patran Thermal MATDAT file is needed. Use the MATDAT file from the previous example. Copy that file to
the present directory for this problem. Otherwise you will need to create a new MATDAT file. The resulting Patran model
is translated into Patran Thermal data files and Viewfactor input data files by clicking Apply on the Analysis menu. Be
sure to choose the X-Y pick for the dimensionality of the problem under Translation Parameters.
Remember to check the VFMSG file for error messages when the Viewfactor analysis is completed. The VFDIAG file
from this analysis is shown below. Since this is not a closed enclosure, the viewfactors to each surface do not sum to one.
The ambitious user may wish to calculate the views from various surfaces to the opening between the plates and compare
these calculated values to the one minus sum values in the VFDIAG file.
VFDIAG File
$TITLE: PDA Viewfactor VER. 2.5 4-APR-91 17:18:55
$TITLE: PARALLEL SEMI-INFINITE PLATES OPEN TO THE LEFT AND RIGHT.
$TITLE: PARALLEL PLATES, SIMPLE, FINE, LINEAR HEAT AT NODES.
Main Index
34 Patran Viewfactor Analysis
Problem 2 - Parallel Semi-Infinite Plates
$QTRAN
Finally, you will want to look at the Patran Thermal output data in the QOUTDAT file. Use the system editor to find the
first occurrence of the string '1TIME'. Note the system heat balance. This is approximately the imposed heat flux to the
plates’ surfaces. Page down through the data to node 1000, the ambient node. Note that the heat flux at this node is
approximately half of the imposed heat flux as expected. Sum up the heat fluxes to the ambient surface and note that this
sum is approximately half of the imposed total heat flux. The nodes numbered above 1000 are the radiosity nodes created
by Viewfactor.
This is a simple problem and you may wish to try numerous variations on it, such as refining the mesh, changing the
convergence criteria, changing the double area parameter of the $GAUSS_ORDER, changing the imposed heat flux,
changing the ambient environment temperature, specifying the plate surface temperatures, and entering more complicated
descriptions of the radiative surface properties.
Main Index
Chapter E: Example Thermal Radiation Problems 35
Problem 3 - Heated Reaction Chamber
TEMPLATEDAT File
MID 365 36501 36501 36501 36504 36505 36506
*
VFAC 365 0
0.8 1.0 0 0 0 0 0 1
The material template ID 365 is for the high-strength steel used for the vessel walls and the VFAC template 365 is for
the interior surfaces of the vessel. The template gives the emissivity as a constant value of 0.8. No other radiation property
data is given in this case since this is a simple model.
Main Index
36 Patran Viewfactor Analysis
Problem 3 - Heated Reaction Chamber
Likewise, a Patran Thermal MATDAT file is needed. We have created a file by using our system editor and extracting the
data from the material property data file for MKS units supplied with the Patran Thermal module in the
THERMAL$DIR:[LIBRARY] directory as MPID.MKS. Our MATDAT file is shown below.
MATDAT File
MPID 36501 CONSTANT KELVIN 1.0
STEEL, ULTRA HIGH STRENGTH TYPE 300-M --> Thermal Conductivity (W/(m*Sec*K))
References: 1
Data Quality: EXCELLENT
MDATA 5.77806E+01
/
MPID 36504 CONSTANT KELVIN 1.0
STEEL, ULTRA HIGH STRENGTH TYPE 300-M --> Density (Kg/m**3)
References: 1
Data Quality: EXCELLENT
MDATA 7.84000E+03
/
MPID 36505 CONSTANT KELVIN 1.0
STEEL, ULTRA HIGH STRENGTH TYPE 300-M --> Specific Heat (J/(Kg*K))
References: 1
Data Quality: EXCELLENT
MDATA 4.47324E+02
/
MPID 36506 PHASE KELVIN 1.0
STEEL, ULTRA HIGH STRENGTH TYPE 300-M --> Latent Heat (J/Kg)
References: 1
Data Quality: EXCELLENT
MDATA 1.77315E+03 1.51190E+05
/
The resulting Patran model is now translated into thermal input data files and Viewfactor input data files by clicking on
Apply from the Patran Analysis menu.
This viewfactor analysis takes about 900 CPU seconds on a VAX 8600, so be forewarned that this job will require a
significant amount of computer time and you may not wish to spend your computer resources running this example
problem. Output for this analysis has been included with the Viewfactor delivery and is available on your system.
Remember to check the VFMSG file for error messages when the Viewfactor analysis is done. The last 40 lines of the
VFDIAG file from this analysis is shown below. Since the interior of the chamber is a closed radiation enclosure, we expect
the sums of viewfactors from any surface to all other surfaces to be one, or at least very close to one (after taking into
account computer and numerical approximations and discretization errors during obstructed view checking). From the
diagnostic data file, VFDIAG, we observe that the maximum deviation from one for these sums is about 0.03 and the
average deviation is about 0.01. Both of these values are reasonable for a 108 surface enclosure.
Main Index
Chapter E: Example Thermal Radiation Problems 37
Problem 3 - Heated Reaction Chamber
VFDIAG File
$TITLE: PDA VIEWFACTOR VER. 2.5 4-APR-91 17:58:55
$TITLE: HEATED REACTION CHAMBER WITH SIDE CHAMBER.
$TITLE: EXAMPLE PROBLEM, REACTION CHAMBER, 3D, ABOUT 110 ELEMENTS.
$TITLE: 4-APR-91 17:44:28 2.5
$ENCL: 1 108 1
1 0.9969453812E+00 0.3054618835E-02 0.0000000000E+00
0.1003143072E+01 0.1001876235E+01 0.9858158231E+00
2 0.9985128045E+00 0.1487195492E-02 0.0000000000E+00
0.1004488468E+01 0.9986609221E+00 0.9923893809E+00
3 0.9980445504E+00 0.1955449581E-02 0.0000000000E+00
0.9956341982E+00 0.1000977635E+01 0.1001693606E+01 0.9938086867E+00
4 0.9978431463E+00 0.2156853676E-02 0.0000000000E+00
0.9944566488E+00 0.1001591563E+01 0.1000043273E+01 0.9952377677E+00
5 0.9988200068E+00 0.1179993153E-02 0.0000000000E+00
0.1005183816E+01 0.9964703321E+00 0.9948055148E+00
6 0.9989739060E+00 0.1026093960E-02 0.0000000000E+00
0.1002386332E+01 0.9964384437E+00 0.9980962276E+00
7 0.9983404279E+00 0.1659572124E-02 0.0000000000E+00
0.9980260730E+00 0.1000427961E+01 0.9992659688E+00
Under Solution, type select Viewfactor Analysis and make sure the option is for steady state, option 3.
A few minor modifications need to be made to the Patran Analysis form.
Under Viewfactor Solution Parameters, change the title to: Viewfactor EXAMPLE PROBLEM CHAMBER.
Under Solution Parameters, set EPSISS to1.0000000000d-03.
Main Index
38 Patran Viewfactor Analysis
Problem 3 - Heated Reaction Chamber
Under Output Requests, Diagnostic Output, set all of the toggles off, especially the radiation resistors to avoid receiving
printout for tens of thousands of radiation resistors.
Under Solution Parameters, run control, set the initial temperature to 300 K.
The thermal analysis is spawned when Apply is selected on the Analysis menu. The analysis will take much longer than
for a similar model without any radiative interchange. When the radiative interchange is modeled in this example, nearly
every nodal subarea on the interior surface of the vessel is connected to nearly every other nodal subarea on the interior
surface by means of radiation resistors. Thus the resistor network which QTRAN must solve has many times more resistors
than a similar model without radiation coupling. Also, the heat transfer across the radiative resistors is highly nonlinear.
This further increases the time required for QTRAN to solve the network equations. The QTRAN thermal network analysis
will require approximately 6000 CPU seconds on a VAX 8600.
You may not wish to spend your computer resources running this example problem. Output for this analysis has been
included with the Viewfactor delivery and should be available on your system.
When the analysis is done, the following results may be read into the Patran database under the Analysis menu with the
Action set to Read Results. The results can be visualized with any of the visualization tools under Results.
Finally, you will want to look at the Patran Thermal output data in the QOUTDAT file. Use the system editor to find the
first occurrence of the string '1TIME'. Note the system heat balance. This is approximately the imposed heat flux to the
chamber’s bottom cap. Also note that although the temperatures are converged to high accuracy, the total system heat
balance is not nearly so accurate. This illustrates the significance of the fourth power temperature dependence for radiant
energy exchange. If accurate heat flows are required for a thermal analysis of a high temperature radiation environment,
then very accurate temperatures must in general be calculated. The nodes numbered above 2000 are the radiosity nodes
created by Viewfactor.
Main Index
jp`Kc~íáÖìÉ=nìáÅâ=pí~êí=dìáÇÉ
Index
Viewfactor Analysis
Symbols errors, 1
$APPROX_CURVE, 93 file, 2
V i e w f format, 2
a c t o r
$AXISYM_SURFACE, 95
A n a l y $CONVERGE, 92 surface incompatibility, 2
s i s UID/TID, 2
$DIAGNOSTIC_FILE, 89
$ENDNODES, 137 execution modes, 18
$ENDSYM, 136 mode 1, 18
$EOF, 95 mode 2, 19
$GAUSS_ORDER, 94 mode 3, 19
$IN_DATA, 89
$MESSAGE_FILE, 88 F
$NODES, 137 file errors, 2
$OUT_DATA, 90 filenames
$PATH, 88 generic, 10
$RAD_NODE_FILE, 90 machine specific, 10
$RAW_DATA, 90 finite element analysis, 3
$RESTART_FILE, 89 format errors, 2
$RESTART_FLAG, 92
$RUN_CONTROL, 91
$SIZE, 136
H
heated reaction chamber, 35
$STATUS_FILE, 89
$SYM, 136
$TEMPLATE_FILE, 90 I
$TITLE, 89, 136 input data file, 133
$ZERO, 92
M
A material property
ambient radiation node, 44 definition, 122
analysis, 98 material property ID, 56
analysis cycle, 8, 20 memory requirements, 8
axisymmetric Model, 48 model diagnostic file
example, 146, 147
model input file
C example, 133
compatibility, 65
MPID, 56
computational limitations, 129
MSC.Patran THERMAL, 2, 3, 13, 21, 52
convex surface, 47, 48
D N
nomenclature, 9
diagnostic data, 145
diffuse surfaces, 3
O
obstruction, 128
E
emissivity resistors
rules, 156 P
enclosure, 25, 26 parallel semi-infinite plates, 32
enclosure ID, 25 PATQ, 80, 111
post-analysis, 110
postprocessing, 118
Main Index
40 Viewfactor Analysis
S
steady-state radiative boundary conditions, 13
surface incompatibility errors, 2
surface orientation, 24, 31, 34, 36
surface pointer data, 149
symmetry, 67, 74
in 2-D XY Space, 68
in 3-D XY Space, 70
purpose, 67
symmetry operations, 67
T
TEMPLATEDAT, 14, 149
examples, 61
thermal analysis, 117
thermal radiation, 3, 20
example problem, 13, 32, 35
thermal radiation analysis, 4
thermal radiation modeling, 67, 74
torus, 48
U
UID/TID errors, 2
V
VFAC, 20
VFAC LBC, 38
VFAC template, 58
VFCONTROL, 18
VFCTL, 17, 21, 85, 122, 6
default, 6
sample file, 96
VFDIAG, 15, 101, 107, 145
example file, 107
Main Index