Patran 2008 r1 Thermal User's Guide Volume 1: Thermal/Hydraulic Analysis

Patran 2008 r1

Thermal User’s GuideVolume 1: Thermal/Hydraulic Analysis

Worldwide Webwww.mscsoftware.com

DisclaimerThis 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*2008R1*Z*THM*Z* DC-USR

Corporate Europe Asia Pacific

MSC.Software Corporation2 MacArthur PlaceSanta Ana, CA 92707 USATelephone: (800) 345-2078Fax: (714) 784-4056

MSC.Software GmbHAm Moosfeld 1381829 Munich, GermanyTelephone: (49) (89) 43 19 87 0Fax: (49) (89) 43 61 71 6

MSC.Software Japan Ltd.Shinjuku First West 8F23-7 Nishi Shinjuku1-Chome, Shinjuku-Ku Tokyo 160-0023, JAPANTelephone: (81) (3)-6911-1200Fax: (81) (3)-6911-1201

C o n t e n t sMSC Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

1 IntroductionPurpose 2

Features and Capabilities 3

Integration with MSC Patran 12

2 Getting StartedObjectives 14

Model Description 15Exercise Procedure 15Temperature Boundary Conditions 25Nodal Heat Source Boundary Condition 29Convective Heat Transfer Boundary Condition 30

3 Building A ModelIntroduction to Building a Model 38

Geometry Modeling 41

Fields Form 42Fields Create 42

Material Library 48

Element Properties 53Element Properties Form 54Properties Show Material Orientations 57

Input Properties 58Input Properties Form 58

Loads and Boundary Conditions 105Loads and Boundary Conditions Form 105Object Tables 120

MSC Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

ii

Load Cases 126

4 Module OperationPreference Files 128

Reference Notes 129Set up 129Model Creation 129Materials 135Element Properties 135Load Cases 135Analysis (job submittal) 135Results Verification 136Results Display 137

5 Running an AnalysisReview of the Analysis Application 140

Analysis Form 141Restart File 141Translation Parameters 142Solution Type 143Solution Parameters 144Output Request 153Submit Options 161

Delete 163

Template Generator 164Template File Data Form 164Read 172Template Entries Spreadsheet 173

Thermal Tools 175

Plot View Factors 183

6 Reading ResultsOverview of Results Import 198

File Menu Import 199Import Form 199

iiiCONTENTS

Analysis Form 201

7 Thermal/Hydraulic TheoryNetwork Methods 204The Thermal Network 204Conduction Networks 205Convection Networks 208Gray Body Radiation Networks 210Wavelength Dependent Radiation Networks 211Advection Networks 211Heat and Temperature Source Networks 213Flow Networks 213

Numerical Analysis Techniques 216QTRAN’s Predictor-Corrector Algorithm 216SNPSOR Algorithm 218Convergence Acceleration Schemes 218Convergence Criteria and Error Estimation 220System Energy Balance 221Table Interpolation Schemes 221Phase Change Algorithm 222Element to Resistor/Capacitor Translation 223

8 Thermal/Hydraulic Input DeckOverview 226

QTRAN Input Data File (QINDAT) 227

QTRAN Run Control Parameters and Node Number Declarations 229Title Data 229Input Data Echo Option 229Temperature Scale and Time Units Definition 230Transient/Steady-State Run Option Selection and Solver Selection 231Iteration Limit Parameters 234Control Parameters 236Auxiliary Print Options 247Maximum Time Step Control 253Node Definitions 254Print Control 259

Material Properties 263MPID Number, Function Type, Temperature Scale, Factor and Label 263


iv

Material Property Data 268

Network Construction 276Thermal Resistor Assignments 276Capacitor Data 320

Boundary Conditions 322Microfunction Data 322Heat Source/Sink Macrofunction Definition 325Temperature Control Macrofunctions 327Mass Flow Rate Control Macrofunctions 329Pressure Control Macrofunctions 331Initially Fixed Nodes 333Nodal Classification Changes 334Initial Globally-Assigned Temperatures, Heat Sources, Mass Flow Rate, and Variable Gravity Fields 335Individual Assignments of Initial Temperatures and Pressures 337Individual Assignments of Constant Nodal Heat Sources and Mass Flow Rates

338

9 Convection LibraryConvection Configurations 342Parameter Definitions 344Configuration 1 347Configuration 2 350Configuration 3 353Configuration 4 356Configuration 5 358Configuration 6 360Configuration 7 361Configuration 8 363Configuration 9 365Configuration 10 367Configuration 11 368Configuration 12 370Configuration 13 372Configuration 14 375Configuration 15 378Configuration 16 380Configuration 17 382Configuration 18 386Configuration 19 389Configuration 20 392

vCONTENTS

Configuration 21 395Configuration 22 398Configuration 23 402Configuration 24 405Configuration 25 407Configuration 26 409Configuration 27 411Configuration 28 413Configuration 29 414Configuration 30 415Configuration 31 416Configuration 32 416Configuration 33 419Configuration 34 420Configuration 35 421Configuration 36 422Configuration 37 423Configuration 38 427Configuration 39 428Configuration 40 429Configuration 41 431Configuration 42 433Configuration 43 435Configurations 44-999 437Configurations 1000+ 437

10 Microfunction LibraryMicrofunction Library 440Microfunction Format 441Microfunction Options 442Option 1 - Constant 442Option 2 - Power Series 442Option 3 - Sine Wave 443Option 4 - Square Wave 444Option 5 - Step Function 445Option 6 - Ramp Function 446Option 7 - Exponential Function 447Option 8 - Linear Interpolation of a Data Table 448Option 9 - Hermite Polynomial Interpolation of a Data Table 449Option 10 - Repeating Waveform - Linearly Interpolated Data Table 450Option 11 - Repeating Waveform - Hermite Interpolated Data Table 451Option 12 - Natural Logarithm Option 452


vi

Option 13 - Base 10 Logarithm Option 453Option 14 - Blackbody Radiation Fraction Option 454Option 15 - Flip/Flop Option 455Option 16 - Dead Band 456Option 17 - Straight Line 457Option 18 - Indexed Linear Interpolation of a Data Table 458Option 19 - Indexed Hermite Polynomial Interpolation of a Data Table 459Option 20 - Indexed Repeating Waveform - Linearly Interpolated Data Table 460Option 21 - Indexed Repeating Waveform - Hermite Interpolated Data Table 461Option 22 - Repeating Flip/Flop Option 462Option 1000+ - User-Coded Functions 463

11 User-Supplied RoutinesUser-Supplied Subroutines 466

COMMONBLK Definitions 468common.blk 468common.char 469common.dims 469common.int 471common.logc 476common.real 478

ULIBFOR Contents - Example User-Supplied Subroutines 484

Example User-Supplied Routines 536ULOOP7FOR File Listing 536UMICROFOR File Listing 540

QTRAN Arrays 545

12 Support Scripts and CodesPurpose 568

QINDAT File Listing 569

QSTAT - QTRAN STATUS 592

viiCONTENTS

A ReferencesReferences 600

B Mid Templates Supplied in Templatebin and TemplatetxtMaterials References, Classification, Quality Code and Index 602

C PATQ Preference ProgramOverview 662PATQ Main Menu Picks 662PATQ Utility Menu Picks 671

Template File (TEMPLATEDAT) 685MID Templates 686MACRO Templates 687CONV Templates 690VFAC Templates 692VTRA Templates 696VNEV Templates 698FLUID Templates 700Example Template File 703

PATQ Limitations 707

MSC Patran Thermal Execution 708PATQ Files 710VIEW FACTOR Files 718QTRAN Files 718

Translation of MSC Patran Thermal Input to SINDA 720Introduction to the SINDA Utility from MSC Patran Thermal 720Creating the SINDA Input File 720The MODELSIN File 727The APPENDSIN File 746

Using TRASYS Translator 754Translation of MSC Patran Thermal View Factors to TRASYS 754Translating MSC Patran Thermal Model to TRASYS Input 754TRASYS Output to MSC Patran Thermal Input 756

Using NEVADA Translator 760Translation of MSC Patran Thermal View Factors to NEVADA 760Translating MSC Patran Thermal Model to NEVADA Input 761


viii

NEVADA Output to MSC Patran Thermal Input 763

D Example ProblemsOverview 766

Example Problem Number 1--Steady State Conduction Problem 767Introduction 767

Example Problem Number 2--Transient Conduction Problem 768Introduction 768

Example Problem Number 3--3-D Iron Cube Problem 770Introduction 770

Example Problem Number 4--Nonlinear Convection Problem 771Introduction 771

Example Problem Number 5--Nonlinear Temperature and Heat Source Boundary Conditions 773

Introduction 773

Example Problem Number 6--Steady State Radiation 774Introduction 774Key Concept 774

Example Problem Number 7--Sample of Advection/Convection Coupling 776

Introduction 776Goal 776Given 776Find 776

Example Problem Number 8--Sample of User Routines 778Introduction 778Goal 778Given 778

Example Problem Number 9--Solution of a “Stiff” THERMAL Problem with the Direct Solver 780

Introduction 780

Example Problem Number 10--Translate MSC.Patran Thermal Input to SINDA Input 781

Introduction 781Key Concept 781

ixCONTENTS

Problem Number 11--Solution of a Hydraulic Problem 783Introduction 783


x

Chapter 1: IntroductionPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

1 Introduction

Purpose 2

Features and Capabilities 3

Integration with Patran 12

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisPurpose

2

PurposePatran Thermal is a automated thermal modeling and analysis system for the solution of steady-state and transient problems. It is a fully-integrated analysis preference in Patran, providing an easy to use forms setup environment that guides the user to perform a successful thermal analysis. Patran Thermal has built-in viewfactor and flow network programs that use the same Patran finite element model, eliminating duplicate modeling. Patran Thermal features a large temperature-dependent materials library, extensive built-in functions and a convection correlations library. User subroutines can be added in the initial problem setup to meet the requirements of specialized applications.

3Chapter 1: IntroductionFeatures and Capabilities

Features and Capabilities

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisFeatures and Capabilities

4


Analysis Capabilities

• Steady-state solution• Transient solution• Coupled thermal/fluids solutions• Conduction heat transfer:

• Across regular boundaries• Across irregular boundaries• Through heavily skewed meshes

• Convection heat transfer:• Constant or variable film coefficient• Library of 57 embedded convection film

correlationsGeometrical configurationsLaminar and turbulent flows with calculated transitionsNatural and forced convectionPool boiling and condensationContact resistance with interstitial fluid

• User supplied correlations• Convection elements

• Radiation heat transfer:• Built-in viewfactor program• Gray and wavelength-dependent

radiosity networks• Participating media• Time- and temperature-dependent

emissivity and transmissivity

• 3D tetrahedral, wedge and hexahedral elements

• Shell versions of bar, tri, and quad elements

• Material properties:• Constant, time- and temperature-

dependent• Directionally dependent• Definitions through 13 evaluation

functions• User supplied subroutines• Unlimited phase changes

• 1000 member materials library• Thermal conductivity• Specific heat• Density• Latent heats• Querying capabilities through

Patran Materials• Viewfactor program:

• Fully integrated into Patran Thermal

• Uses the same Patran model• 2D and 3D Cartesian coordinate

viewfactors • Axisymmetric coordinate

viewfactors• Multiple symmetry support:

reflections across a plane or linerotation "n" times by "x" degrees about an arbitrary axis

• Finite element support:Linear quadrilateral faces (Hex, Wedge, Quad, etc.)


6

• Dynamic radiation viewfactors• Advection heat transfer:

• Variable mass flow energy balance• Flow networks:

• Multiple parallel, series flow paths• Coupled to thermal solution • Pump, turbine, gravity head

Linear triangular faces (Tets, Wedges, Tri, etc.)Linear bar faces for 2D x/y elementsLinear bar faces for axisymmetric elements

• Obstruction checking• Flagging of convex surfaces and non-

obstructions• Multiple enclosures• Ambient node• Viewfactors reusable when material

properties change• Adaptive integration order for improved

accuracy and reduced CPU time• Collapsed radiation network option• Diagnostic data

• Head loss in pipes, valves, bends, tees, orifices, check valves, plenums

• Variable fluid properties• Specified or calculated friction factor

(Moody's equation)

Modeling Capabilities

• Element library:• 2D 3D and RZ bar elements• 2D, 3D and RZ triangular elements• 2D, 3D and RZ quadrilateral elements

• Direct geometry access from supported CAD systems

• or Patran geometry creation• Automatic meshing• Apply thermal boundary conditions

to geometry or FEM• Flexibility in selection of

application regions at a point, within a volume, along an edge, across a face, through a solid or by enveloping the complete model in a spatial field

• Non-spatial fields for time and temperature dependent boundary conditions definitions

• On-line context sensitive and topical help

• Ability to share analysis model and results with other Patran solver-applications


• Patran Thermal Specific:• Analysis environment selected

through an analysis preference• Thermal material and element

properties forms• Thermal microfunctions input data

forms• Solution parameters forms with

appropriate defaults• Problem setup and execution

control• Complete Patran Thermal User’s

Guide online

TRASYS and NEVADA Interface

• Ability to output geometry and material properties to TRASYS and NEVADA

• Ability to translate orbital fluxes and radiation couplings as input to Patran Thermal

• Supports TRASYS articulating components

SINDA Deck Capabilities

• SINDA 85 format• SINDA/G (BCD) format • Ready-to-run SINDA deck

• Includes radiation resistors generated by viewfactor program

• Material properties automatically loaded into Array Data

• Complete Constants Data and Execution blocks


8

• Thermal boundary conditions:• Time- and temperature-dependent point

heat sources• Time- and temperature-dependent

volumetric heat sources• Time- and temperature-dependent surface

heat fluxes• Fixed or variable nodal temperatures• Radiant surface properties• 21-microfunction library for time- or

temperature-dependent boundary conditions

• User supplied subroutines• Selectable physical units and output• Unrestricted node numbering scheme• Unlimited problem size (hardware limited only)• STEP-TAS translator (SUN only)

Solution Features

• Solution algorithms:• Unconditionally stable implicit predictor/

corrector method (Hughes)• Explicit method (Euler)• Strongly Nonlinear Point Successive Over

Relaxation equation solver for implicit transient or steady-state calculations

• Direct solver and combined direct/ iterative solutions

• User-controlled parameters for fast solutions of nearly linear problems

• Solution techniques:• Optional automatic selection of implicit or

explicit solution on a node-by-node and time step-by-time step basis

• Automatically calculates and updates convergence acceleration parameters for iterative solutions

• MSC Institute offers the PAT 312 P/THERMAL class. Please call for a class schedule.

• Documentation• Patran Thermal User’s Guide (on-

line)• Viewfactor code User’s Guide (on-

line)• Deliverables

• CD-ROM containing all required files necessary to load and run Patran Thermal, plus example problems

• User documentation• Complete installation instructions


• Convergence based on estimated maximum temperature error

• Optional automatic modification of calculation time step

• Restart option

User Preference

• Patran Specific:• Intuitive forms driven interface


10

• Exact FE to RC network translation based on same method as Patran Thermal

• No reverse translator required for post-processing with Patran

Results Evaluation Capabilities

• Results read and stored in Patran model database • Results evaluation with Patran's extensive post-

processing capabilities:• Contour and fringe display• Time vs. temperature plots• Isosurface plots

• Animation of results Output information:• Nodal temperatures at selectable time

points• Maximum explicit time step per node per

selected time point• Net element heat fluxes at selectable time

steps• Nodal heat sources and convection

coefficients at selectable time steps• Detailed time history of selected nodes• Optional program calculated parameters

including conduction, convection, radiation and advection resistors, capacitors and heat

• Temperatures may be automatically applied as loads in other solver-applications

Configuration Requirements

• General requirements and configuration information

• FORTRAN compiler required


• Optimum memory configuration varies with problem size and complexity. Consult your local Patran representative for your particular configuration and application needs as well as for supported computer systems

• Approximate memory requirements • Dynamically optimizes data array size

prior to execution

Support and Deliverables

• Hotline support Training:

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisIntegration with Patran

12

Integration with PatranPatran Thermal is a preference selection in Patran for creating a model to be analyzed by Patran Thermal, the Patran thermal analysis module. The thermal model can be created and submitted directly from Patran. Analysis results can then be read into the Patran database for postprocessing with the various Patran tools or for sharing the results with other Patran applications.

When the Patran Thermal preference is set, forms specific to input data required by the Patran Thermal module will appear under Loads/BCs, Element Properties, Materials, and Analysis. The User Preference consists of the following:

• Element properties forms for defining properties of the elements in the model such as material, shell thickness, etc.

• Loads/BCs forms for defining Temperature, Convection, Heat Flux, Volumetric Heat, View factors, Pressure (hydraulic) and Mass Flow boundary conditions.

• Analysis form for defining solution type, parameters and job control.• Materials form for defining material properties.• General fields for defining Non-Spatial and Material Property functions.

If Full Run is set, the Apply selection in the Analysis form will create the appropriate interface files and execute the solver. The interface files created include:

• A neutral file• The analysis control files qin.dat and vf.ctl• The script input for executing the model patq.inp• The material properties file mat.dat• The field definition file micro.dat

Patran Thermal is designed to support the functionality in P/THERMAL 2.6, including the View factor code, the new coupled thermal/hydraulic networks and creation of a SINDA input deck. Overall, users will find Patran Thermal a much easier to use product without sacrificing the powerful capabilities of P/THERMAL.

Note: Append files may be included in the same directory as the Patran database which will be automatically added to each job submitted from the Analysis form. The supported append files are: mat.dat.apnd, micro.dat.apnd, template.dat.apnd, and convec.dat.apnd.

Chapter 2: Getting StartedPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

2 Getting Started

Objectives 14

Model Description 15

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisObjectives

14

ObjectivesThis getting started tutorial goes through the basic steps in creating a Patran Thermal model, submitting the analysis, and visualizing the results.

• Build a two-dimensional thermal model in Patran (Geometry and Finite Elements).• Apply temperature, heat flux, nodal heat source, and convective boundary conditions.• Apply elements properties. • Create a run-ready analysis deck and spawn a thermal batch job.

Postprocess the results.

Important: For more information about module operation, with step-by-step instructions for various types of thermal applications, see Reference Notes, 129.

15Chapter 2: Getting StartedModel Description

Model DescriptionIn this exercise you will determine the steady-state temperature distribution in a 1m by 1m Aluminum slab. The slab will be modeled in two dimensions. The loads and boundary conditions you will apply to the model are shown in the figure below.

Exercise ProcedureAccessing PatranStep 1: In your xterm window, type patran to start Patran.

You should see various status messages being printed in the xterm window. After a short time, the following Patran main form will appear.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisModel Description

16

Initially, all selections within the main form are ghosted except the File selection. Typically when an option does not pertain to the task you are performing, Patran ghosts that selection to make it easier for you to choose the viable options. For example, move the cursor to the File selection in the main form and click the left mouse button. In the pull-down menu that appears (also shown below), the operations that do not pertain to manipulating databases are ghosted, since the first thing you must do when starting Patran is access a database.

Next, select New from the pull-down menu.

To create a new database, type the name exercise_1.db under New Database Name, and click OK. In a short time, you should see your graphics viewport open.


Let’s stop for a moment to discuss the icons located in the main form. Notice the Patran Heartbeat in the upper right-hand corner of the main form.


18

The Heartbeat changes color to inform the user of Patran’s status.

If the Heartbeat is green, Patran is waiting for you to enter a command.

If the Heartbeat is blue, Patran is busy with an operation, but it can be interrupted by clicking on the Patran Hand. The operation of the Hand is similar to “control” C (interrupt task).

If the Heartbeat is red, Patran is busy with an operation and cannot be interrupted. Typing or mouse selections at this time will be ignored.

There are two more buttons in the upper right-hand corner of the main form. One is the Refresh button (the paint brush) and the other is the Undo button (the eraser).


ort the

n

t is the

Step 2: After the database is opened, a New Model Preferences form will appear. Select the Default Tolerance and change the Analysis Code to Patran Thermal. The completed form is shown below for your reference.

Click on the OK button to close that form.

Selecting Patran Thermal causes Patran to customize the user interface forms to include terminology pertaining to the Patran Thermal code.

Step 3: You will now create a patch that will represent the geometry of the plate. Click on the Geometry toggle in the main form. When the Geometry form appears, set it to Create, Surface, and XYZ.

The Refresh button repaints the model. After you delete something from the viewpor pull menus over the viewport, the model might need repainting. If it does, press Refresh icon.The Undo button can be used to undo most commands. Only the previous operatiocan be undone by the Undo button.

The Interrupt button is used to stop Patran from completing the process in which iworking. You can only use it when the heartbeat is blue. It will ask you to confirm interruption.


20

The form’s default settings will create a 1 x 1 patch at the default global coordinate origin. Click on Apply to create the patch. Your Geometry form and patch model should now look like the ones shown below.

To turn on labels click on the Show Label icon. Use the Label Control icon to select specific labels.

The number of geometric display lines can be changed on the Display -> Geometry and specifying the number of lines desired.

Step 4: To create the finite element model, click on the Elements toggle in the main form. Set the Action, Object, and Type pull-down options to Create, Mesh, and Surface. To mesh the patch with a 5x5 mesh density (i.e., 4x4 elements), change the Global Edge Length to 0.25.

Select the Quad4 Element Topology. Since the patch you have created has four sides, choose IsoMesh Mesher option.

When a surface has more than 4 edges, you must use the Paver Mesher option or you can decompose the n-sided surface into subsurfaces containing no more than 4 edges and use the IsoMesher.


Click in the Surface List databox at the bottom of the Finite Elements form. Select Surface 1 and click on Apply to create the finite element mesh. Your completed Finite Elements form and model should look like the ones shown below. Node 999 is created later.

Step 5: You will now define the model’s Element Properties. Click on the Properties toggle in the main form.

When the Element Properties form appears set the Action, Dimension, and Type option menus, to Create, 2D, and Thermal 2D. Enter the Property Set Name, Prop1.

Next, click on the Input Properties button. When the Input Properties form appears, you will see the Material Name, Material Orientation-X, Material Orientation-Y, and Material Orientation-Z databoxes. For this exercise, you will use the Patran Thermal material database. Aluminum is the first material that occurs in the database (Material ID, MID=1). To use the Aluminum Material, type 1 in the Material Name databox. The material is isotropic; therefore, no directional data (material orientation angles) will be input to the form. The Element Properties and Input Properties forms are shown below for your reference.


22

Click on the OK button to close the Input Properties form.

You will now apply the element properties to your model. Click the Select Members listbox. At the bottom of the screen, a select menu will appear. The icons represent selection filters that allow you to assign the element properties to the geometry (left icon) or the finite elements (right icon). Since the Dimension is set to 2D, you can select a surface or face of a solid if you apply the properties to the geometry, or surface elements (e.g., triangle, quad) if you apply the properties to the finite element model (FEM). Select Surface 1 with mouse and click on the Add button to add this surface as the chosen application region.


Click on the Apply button to create and assign the Element Properties to the model.

Step 6: In this step you will create a finite element node, next to, but not on your model. The node will represent the model’s surrounding environment. In a later step, you will assign the environmental (ambient) temperature to the node. This temperature is needed for the convective film coefficient definition. Click on the Elements toggle in the main form. Set the Action, Object, and Type option menus to Create, Node, and Edit. Change the Node ID List to 999. This number is the ID of the next node to be created.


24

Next, set the Associate with Geometry button off and click in the Node Location List databox. In the select menu, highlight the right most icon, which allows you to select an arbitrary screen position. Click in the graphics window at a position, next to, but not on the model to specify the position of Node 999. Click on the Apply button to create the node. The completed Finite Element form and model are shown below for your reference.


Step 7: You will now assign the thermal boundary conditions for the model.

Temperature Boundary ConditionsClick on the Loads/BCs toggle in the main form. When the Loads/Boundary Conditions form appears set the Action, Object and Type, respectively to Create, Temperature (P/Thermal), and Nodal. Set the Option menu to Fixed.

Enter Temp1 as the New Set Name for this boundary condition. Click on the Input Data button, enter a temperature of 300. The completed Input Data form is shown below.


26

Click on the OK button to close the form. Next, click on the Select Application Region button. When the Select Application Region form appears, set the Geometry Filter to Geometry and click in the Select Geometry Entities databox. In the select menu, highlight the curve icon since you will now apply the temperature to the left vertical edge of the patch. Click on the left vertical edge of the patch and Surface 1.1 will appear in the Select Geometry Entities box. Add this selection to the Application Region box. The completed form is shown below.


Click on the OK button to close the form. Click on the Apply button to create the temperature boundary condition. Your model should now look similar to the one below.


28

To apply the ambient temperature to Node 999, create a new temperature set named Temp2 with the Option menu again set to Fixed. Enter a temperature of 300 in the Input Data form and click on the OK button. In the Select Application Region, choose the FEM Geometry Filter. Click in the Select Nodes databox and select Node 999 in the viewport. Add this node to the Application Region and click on the OK button. The completed forms are shown below for your reference.


Finally, click on the Apply button in the Loads/Boundary Conditions form to create the second temperature boundary condition.

Nodal Heat Source Boundary ConditionChange the Object pull-down menu on the Loads/Boundary Conditions form to Heating (PThermal). Change the Option menu to Nodal Source. Enter a New Set Name, Nodal_Heat, and input 1000 for the heat source value. Do not input a value for the Template ID. This value is used to identify a user-defined macro function that can be used to define a varying heat source. Assign the heat source to the center node of your model (Node 13). The completed forms are shown below for your reference. Click the Apply button to create the boundary condition.


30

Convective Heat Transfer Boundary ConditionSet the Object and Type option menus on the Loads⁄Boundary Conditions form to Convection (Patran Thermal) and Element Uniform. Set the Option menu to Use Correlations. Enter the New Set Name, Convection, and change the Target Element Type to 2D. Click on the Input Data button and enter 13.5 for the Convection Coefficient and specify the Fluid Node ID as Node 999. Click on the OK button to close the Input Data form. Next, click on the Select Application Region button, set the Geometry Filter to Geometry and highlight the edge icon. Apply the convection boundary condition to the right vertical edge (Edge 3) of the surface. The completed forms are shown below for your reference.


Step 8: You are now finished defining your analysis model. In this step, you will submit the job for analysis.

Click on the Analysis toggle on the main form. In the Analysis form that appears. The job name is assigned the database name and the job description references the session file used to create the model at the time of construction. Go ahead and change these to something more meaningful if desired. Click on the Translation Parameters button. The following Patran Thermal Translation Parameters form will appear.


32

The default model dimensionality is 2D and the file to extract undefined materials is mpidmks.bin. To use these default settings, click on the OK button at the bottom of the form. You will also use the default setting found in the Solution Type, Solution Parameters, Output Requests, and Submit Options forms. If you would like to inspect these forms, feel free to do so but do not change the default settings.

To submit the analysis run, click on the Apply button at the bottom of the Analysis form. Patran Thermal will create the jobname directory (exercise_1 if you did not change it) and spawn the Patran Thermal job.

Patran Thermal will create a subdirectory with the job name exercise_1 containing the data files, message files and the results file for this analysis. If you would like to check the status, open a new window and look at the contents of the exercise_1/patq.msg.01 file. If there is a stat.bin file present, you can check the progress of the solution convergence by typing in this shell the command:

% qstat


By selecting Thermal Tools as the action on the analysis menu, you can obtain an interactive XY plot of the convergence status as the job is being executed.

Step 9: After the job is complete (this job takes less than a minute), change the Action pull-down option menu on the top of the Analysis form to Read Results. Next, click on the Select Results file button. When the Select File form appears, select the subdirectory for the job just submitted by double clicking the appropriate path:

... ./exercise_1/*.nrf*

Update the Available Files list by clicking on the Filter button. Highlight the file, nr0.nrf.01, in the Available Files list. Your edited Select File form should now look like the one shown below.


Step 10: A result template file is necessary to define the nodal results being read back into PATRAN. One is created and placed in the same subdirectory that job was executed thus it is not necessary to select one. If it is desired to use something other than the originally created default do the following. The Select Rslt Template File button in the Analysis form. Move the Files scroll button to the bottom and select the pthermal_nod_T.res_tmpl results template file. The form is shown below for your reference.


34


Finally, click on the Apply button on the bottom of the Analysis form to cause Patran to read in the analysis results.

Step 11: To display the temperature distribution across the aluminum plate, click on the Results button in the main form.

When the Results Display form appears and the only results case will be highlighted. Select the result it is desired to plot and click on the Apply button to render the plot. Your temperature distribution should now look similar to the one shown below.


36

Chapter 3: Building A ModelPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

3 Building A Model

Introduction to Building a Model 38

Geometry Modeling 41

Fields Form 42

Material Library 48

Element Properties 53

Input Properties 58

Loads and Boundary Conditions 105

Load Cases 126

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisIntroduction to Building a Model

38

Introduction to Building a ModelThere are many aspects to building a finite element analysis model. In several cases, the forms used to create the finite element data are dependent on the selected analysis code and analysis type. Other parts of the model are created using standard forms.

Under Preferences, on the Patran main form, is a selection for Analysis. Analysis Settings defines the intended analysis code which is to be used for this model.

The Analysis Code Selection may be changed at any time during model creation. As much data as possible will be converted if the analysis code is changed, after the modeling process has already begun. The setting of this option defines what will be presented to the user, in several areas, during the subsequent modeling steps. For more details, see Analysis Form (Ch. 5) in the Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis.

39Chapter 3: Building A ModelIntroduction to Building a Model

Overall Analysis StructurePatran Thermal produces files that are compatible with the P/THERMAL solver. This includes a neutral file, the analysis control files qin.dat and vf.ctl, and the script for executing the model patq.inp. The script can be executed locally from within Patran, producing the input data files and invoking the solver. Alternately, the files may be moved to a different platform where P/THERMAL resides for execution. With P/THERMAL, multiple jobs can be created from the same Patran database. The model files will appear in subdirectories named with the jobname that was entered in the Analysis form.

For a model whose boundary conditions do not point to a template ID and which references a material in the P/THERMAL materials library (971-members), Patran Thermal can create the model, submit it for execution, and postprocess results directly from Patran, without having to invoke the text editor. In general, the user will only have to utilize the text editor if the model has time/temperature dependent BCs, view factors, or require user subroutines.

Material DefinitionIn this release of Patran Thermal, materials must be specified as a number (e.g., 18 or m:18) or by a name (e.g., steel). The materials set is created when the number or name is entered in the Element Properties form. The material number refers to a material ID in the template.dat file. If a definition is not found in the local template corresponding to the material number and the material number is in the range 1 to 971, P/THERMAL will use the MID Template delivered with the solver and load the temperature dependent material properties. The material IDs associated with the database delivered with the module can be found in Mid Templates Supplied in Templatebin and Templatetxt (App. B) in the Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisIntroduction to Building a Model

40

If a material is specified in the element properties form by a name, the names are added to the Material Sets and will be numbered at translation time sequentially in the order they were created. For example, if the materials set created by defining materials under Element Properties are given the names Zirconium, Steel and Carbon-Felt, they will be assigned MID numbers 1, 2 and 3, respectively. These MIDs must be further defined in the MID Template since these materials do not correspond to the MID templates supplied with the module.

Important: Do not mix material names and material numbers.

41Chapter 3: Building A ModelGeometry Modeling

Geometry ModelingBuilding the geometry for a thermal model with Patran is nearly identical to the procedure that is used to build a structural model, and in many cases the geometry can be shared between these two applications. As in other Patran applications, geometry can be directly accessed through Working with Files (Ch. 4) in the Patran Reference Manual (SGM), or created with the Create Actions (Ch. 4) in the Geometry Modeling - Reference Manual Part 2. Besides the part being modeled, occasionally additional geometry is required in the thermal model to represent the advection and hydraulics network, or for use in specifying symmetry planes for the Viewfactor code.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisFields Form

42

Fields FormThe Fields form will appear when the Fields toggle, located on the Patran application switch, is chosen. The selections made on the Materials menu will determine which material form appears.

The following pages give an introduction to the Fields form, and details of all the fields definitions supported by the Patran Thermal Application Preference.

The functions on the Fields menu are listed and described below in the order in which they appear on the menu.

Fields CreateThe Fields form is used to create Spatial, Non Spatial and Material Property fields.

Action Object Options Create... • Spatial PCL Function

Tabular Input

General

FEM• Material Property General• Non Spatial General

Note: Non -Spatial/Tabular Input Fields are not supported by Patran Thermal.

43Chapter 3: Building A ModelFields Form

Material Property/General FieldsThis form is used to compose the function defining a General Field. The only Function Term Type for Patran Thermal is Patran Functions.

Caution: The field is not created until Apply is selected. Wait for the new field name to appear in the Existing Fields databox after selecting Apply.


44

Define Material Property

This form is used to enter all the appropriate data to define the material property. The form header displays what kind of function was selected. At the top of the form the mathematical expression (if appropriate) and a description of the function is displayed. Material Property Fields show up as selectable fields in the listbox in the Materials Input Data form. They can also be referenced in external files such as template.dat or in user-routines by the MPID number given on this form. When a Patran Thermal job is submitted, the data entered on this form is written to the mat.dat file in the <jobname> sub-directory.

Caution: This button works only for terms which are functions (terms preceded by an integer prefix). Attempting to modify terms which are functions in the text box via the keyboard will result in an error.

Note: Although Material Property/Tabular Input is supported by Patran Thermal for defining Materials, the General Method provides more flexibility such as temperature units conversions and is the recommended approach.


Non Spatial/General FieldsThis form is used to compose the function defining a General field. The only Function Term Type for Patran Thermal is Patran Functions. Non-Spatial/General Fields are referenced by MACRO templates (p. 685) in the external file template.dat (currently they cannot be assigned from the Patran session). When a Patran Thermal job is submitted, the data entered on this form is written to the micro.dat file in the <jobname> sub-directory.


46

Define Non Spatial

This form is used to enter all the microfunction data to define a Non Spatial field. The form, header displays what kind of microfunction was selected. At the top of the form the function is displayed graphically or in a mathematical expression (if appropriate), and a description of the microfunction is given.

Caution: This button works only for terms which are functions (terms preceded by an integer prefix). Attempting to modify terms which are functions in the text box via the keyboard will result in an error.

Note: Patran Thermal does not support Non-Spatial/Tabular Fields. Use only Non-Spatial/General Fields.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisMaterial Library

48

Material LibraryPatran Thermal provides three ways to define material properties:

• Define the material properties under Materials/Manual Input/Thermal Properties constituative model. The properties data is entered as values which can be a constant, or a time or temperature dependent field.

• Reference Patran Thermal’s 971-member library of materials delivered with Patran Thermal. This Materials Library (p. 602) contains temperature dependent properties in units of SI, Inch-Lbm-Seconds, Foot-Lbm-Hours, and Centimeter-Gram-Seconds. To access the materials library, use an MID number between 1 and 971 for the Material Name, and do not define any Input Properties. The materials database in the desired units is selected in the Analysis/ Translation Parameters Form. The Patran Thermal materials library can also be accessed with the Material Selector method if Patran Material Selector is available.

• If the material properties data exists in a <jobname>/mat.dat file or local mat.dat.apnd file, they can be referenced under Materials/Manual Input/Thermal Templates constituative model. The Input Data entered are the Material Property IDs (MPID) that correspond to the mat.dat or mat.dat.apnd file. Patran Thermal will automatically create the template.dat file, residing in the jobname subdirectory with the MPIDs pointers into the mat.dat file.

Material forms appear when the Materials toggle is chosen.

This form appears when Materials is selected on the main menu. The Materials form is used to provide options to create the various Patran Thermal materials.

Important: Do not mix material names (“Stainless”) and material numbers (“1”) in the model if referencing the Patran Thermal Material Library. A material name such as Cres.347 will be interpreted as MID 347.

49Chapter 3: Building A ModelMaterial Library

Important:Do not mix material names (“Stainless”) and material numbers (“1”) in the model. A Material Name such as Cres.347 will be interpreted as MID 347.


50

Patran Thermal Properties

The properties list under Property Name can be input as a number or can be selected from the Material Property fields created under the Fields menu. These thermal properties are translated into a mat.dat file (residing in the <jobname> subdirectory).

All Material Property defined in the Fields menu will be translated to the mat.dat file. Also, any material properties constant data entered in the Materials Input Data form is written to the mat.dat file.

If a number has been specified for the material name, it will be used by Patran Thermal as the MID and the material property will have a suffix added to it for the MPID. If a name is used to define the material, the next available MID (plus an offset of 1000 to prevent conflicts with the Patran Thermal materials database) will be used. An MID template is automatically created in the template.dat file located in the <jobname> subdirectory for all the materials defined from within Patran.

If a mat.dat.apnd or template.dat.appd. file is found in the directory where Patran is being executed, it will be appended to the corresponding file in the <jobname> subdirectory. This is an effective way of incorporating auxiliary data to the job being submitted. Care must be taken not to create conflicts between appended files and those generated by Patran.

Object Method OptionIsotropic

3D Orthotropic

Manual Input Patran Thermal Properties

Caution: A material name such as cres.345 will be interpreted as MID 345. Do not mix an MID number (e.g., 1) and a name (e.g., stainless) in the same database.

51Chapter 3: Building A ModelMaterial Library

Patran Thermal Templates

The following form is used to input the Material Property IDs for the thermal properties.

Important:When the analysis is submitted, Patran Thermal will automatically create the necessary entries in the <jobname>/template.dat and mat.dat files.

Object Method OptionIsotropic

3D Orthotropic

Manual Input Patran Thermal Templates


52

Important:When the analysis is submitted, Patran Thermal will automatically create the necessary MID template entry in the <jobname>/template.dat file.

53Element Properties

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

Element PropertiesBy choosing the Element Properties toggle, located on the application switch for Patran, an Element Properties form will appear. When creating element properties, several option menus are available. The selections made in these option menus will determine which element property form is presented, and ultimately, which Patran Thermal element will be created.

The standard Patran Finite Element methods are used for generating elements in the thermal model. The elements supported by Patran Thermal are detailed in the following subsections. Only linear elements are currently supported by Patran Thermal. These include linear bars, triangles, quadrilaterals, tetrahedrons, wedges, and hexahedrons.

Conductive elements must have a material ID (MID) or material name assigned. This Patran MID number corresponds to a material property template.

Material orientation angle information may be optionally assigned for 2-D and 3-D elements. The material angles are referred to as Axis-1ROT, Axis-2ROT, and Axis-3ROT. These angles may be specified relative to the global system, an alternate coordinate system, or the elemental coordinate system. The material orientation system and angular values are used to transform the orientation of the element material's principal axes system relative to the global X, Y, and Z system. For a rectangular coordinate system, the material's principal axes system is rotated within the specified coordinate frame first about the X, then about the new Y axis after XROT, and finally about the new Z axes by angular values of XROT, YROT, and ZROT degrees. These angles may reference a spatial field. Similarly, in the case of a cylindrical coordinate system the rotations are about R, T, and Z. In referencing a cylindrical coordinate system, the default for an orthotropic material is Kxx along axis-1 (Radial), Kyy along axis-2 (Theta) and Kzz along axis-3 (Z).

Note that 2-D Cartesian elements rotate only about the Z-axis, while 2-D axisymmetric elements rotate about an axis given as the cross product of the R and Z axes. Orthotropic material orientation can be visualized under the Element Properties Show action. Examples of element properties definitions for orthotropic materials orientations are included under the 2-D shell and 3-D solid element properties definition forms.

The Element Property forms are also used to supply element thickness information for 2-D shell elements (bars) and 3-D shell elements (triangles and quadrilaterals), as well as providing Geometric Property (GP) data for convective quadrilateral elements. More specific information is given in the following subsections.

The following pages give an introduction to the Element Properties form, followed by the details of all the element property definitions supported by Patran Thermal.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisElement Properties

54

Element Properties FormWhen Element Properties application is selected on the Patran main form, the form below is displayed. Option menus on this form are used to determine which Patran Thermal element types are to be created and which property forms are to be displayed. The individual property forms are documented later in this section. The full functionality of the Element Properties form is documented in the Patran Reference Manual. See Element Properties Application (Ch. 3) in the Patran Reference Manual.


The following table shows the allowable selections for all option menus for Patran Thermal.

Dimension Type Option 1 Option 20D • Node Type1D • Conduction bar • Bar with capacitance

• Bar w/o capacitance• Scaled Bar Element• 3D Conduction Bar

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisElement Properties

56

• Scaled 3D Conduction Bar• Conductor

• Advection bar• Flow network bar • Flow network pipe • Constant Mtrl Prop

• Const Mtrl Props w/moody curve

• Variable Mtrl Props• Turbine element• Pump element• Check valve element• Head loss element• Plenum element

• Radiation symmetry bar

• Axisymmetric Bar • Full 360 Rotation• Specified Degs of Rotation

• Rad sym bar Reflection

• Thermal 2D Bar• 2D • Shell • Shell

• Scaled Shell Element• Thermal 2D• Thermal

Axisymmetric• Full 360 Rotation• Specified Degs of Rotation

• Radiation symmetry tri

• Convective Quad• 3D • Thermal 3D Solid • FE hex, tet, wedge

• Finite diff hex• Scaled FE hex,tet,wedge

• Convective Hex/Wedge

Dimension Type Option 1 Option 2


Properties Show Material OrientationsThe material orientations that will be passed to Patran Thermal can be visualized under Properties Show action.

Note: The displayed labels can be set under the main menu Display- Load/BC/Elem Prop

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisInput Properties

58

Input Properties

Input Properties Form

Node TypeThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This is a point element used to define the type of node.

Bar ElementsPatran Thermal uses bar elements for the following purposes:

Analysis Type Dimension Type Option(s) TopologiesThermal 0D Node type none Point

Note: This 0D element replaces the functionality of type “F” and “I” nodes in PATRAN 2.5.

59Input Properties

• Conduction with capacitance generation• Conduction without capacitance generation• 3D Conductors without orientation• Conductors with specified values• Advection• Specifying radiation symmetry conditions for the VIEWFACTOR code

2-D Thermal Conductive Bar ElementsIn 2-D Cartesian (X-Y) space, conductive bars actually represent 2-D shell elements Figure 4-1. The shell elements are by definition (and in accordance with standard finite element practice) assumed to be of unit depth in the Z direction. Using the 2-D bar elements as “shells” allows them to be used in conjunction with surface area boundary conditions such as convection, radiation, and heat fluxes. 2-D Cartesian elements must be built in the Patran X-Y plane.

Conduction bars will generate conductive resistors between the two-end nodes of the bar and will also generate capacitors for each node. These bars must be element property data consisting of the following:

• MID Template for the bar material• Thickness at node 1 of the bar • Thickness at node 2 of the bar

Figure 4-1 2-D Cartesian (X-Y) Element Demonstrating Unit Depth in the Z Direction

The two thickness values allow for a linear variation of thickness along the bar axis. The average thickness is used (along with the assumption of unit depth along the Z-axis) to compute an effective cross-sectional area for the thermal resistors, and the distance between the bar nodes is used to compute


60

an effective length. Capacitance volumes are computed based on the linear variation of thickness assumption coupled with the half-length of the bar.

Conduction bar elements, without capacitance for 2-D Cartesian models, are similar, except that no capacitors are generated.

Conductive bar elements will be interpreted as 2-D Cartesian when the Model Dimensionality has been specified as 2-D Plane Geometry under Analysis/ Translation Parameters.

Conduction BarThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This bar element is used to define conduction heat transfer.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Conduction Bar Bar with capacitance

Bar without capacitance

Scaled Bar Element

3D Conduction Bar

Scaled 3D Conduction Bar

Conductor

Bar/2

61Input Properties

Advection BarAdvection is the transport of heat energy by a mass flow stream. Advection bars generate advective resistors and no capacitors. These data items consist of the following:

• CPMPID for specific heat material property ID (Cp)

• A constant mass flow rate or mass flow rate multiplier (MDOTC) • An optional MPID that may be used to specify variable mass flow rates

If no MPID number is given for the variable mass flow rate, the constant MDOTC will be taken as the constant mass flow rate for the advective bar and for the resulting QTRAN advective resistors. If the optional MPID number for a variable mass flow rate is also given, then the MDOTC value is used as a scale factor and the effective mass flow rate is computed from the product of the MPID's value and MDOTC.

Mass flow is considered positive in the direction of element node 1 to element node 2, and negative from element node 2 to element node 1.


62

This form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This bar element is used to define the flow of a fluid when the mass flow rate is known.

Note: Advection moves energy from one node to another and quasi steady state is implicit in this formulation. If transient analysis is to be performed, conduction bars need to be assigned parallel to the advection bars so the internal energy in each fluid node is properly modelled.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Advection Bar none Bar/2

Note: The MPID is an integer number referring to a user-defined MPID in the mat.dat file or to a Material Property/General Fields, 43 with this MPID number in the Input Data Form.

63Input Properties

Flow Network Bar-PipeFlow networks transport head energy by a mass flow stream. The mass flow rates are computed by Patran Thermal in flow network resistors, unlike advective resistors where mass flow rates are input by the user. Flow network bars generate “one way” flow resistors and no capacitors. These elements must be assigned element properties and the data field varies with the option selected for the element (tube, pump, turbine, check valve, plenum, etc.). These options and the correspondent data fields are given below.


This is a Flow Network Bar used for the hydraulics analysis.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Flow network

barFlow network pipe/Constant property pipe

Constant property pipe with moody curve

Variable property pipe

Bar/2


64

Input required for the various options available for Flow Network Pipe.

Property NameOption Description

Constant Property with Moody Curve Variable Property[TID] Supply a non-zero dummy TID value. Pointer to FLUID Template

ID in template.dat.IOPT Enter a 1. Enter a 2. Enter a 3.[Pipe diameter] Hydraulic diameter of the flow passage defined as 4*CSArea/wetted

perimeter. (For a circular cross section, hydraulic diameter=physical diameter). If diameter is not specified, it will be calculated using the cross-sectional area and wetted perimeter specified below.

[Pipe c.s. area] Cross-section area of the flow passage. If not specified it will be calculated assuming a circular cross section and specified diameter.

[Pipe perimeter] Wetted perimeter of the flow passage. If it is not specified, it is calculated assuming a circular cross section.

65Input Properties

[Pipe length] The length of the bar element. If it is not specified, it will be calculated as the straight line distance between the end nodes of the bar element.

[Pipe roughness] Surface roughness of the tube or the flow passage.[Head loss coeff] Head loss coefficient to account for minor

losses in the flow network, e.g., losses in bends, tees, valves, sudden expansion/contractions, etc.

A scale factor to the MPID_LOSS_COEF material property in the FLUID Template.

[Fluid density]

[Fluid viscosity]

[Specific Heat]

Specific weight (F/L3), dynamic viscosity (M/LT) and specific heat of the fluid flowing through the network. Must be consistent with the units that are used to solve the thermal problem. If applicable to the system of units, Patran Thermal will convert specific weight to mass-density based on the ICCALC flag.

Fluid density (MPID_RHO), viscosity (MPID_MU) and specific heat (MPID_CP) are defined in the FLUID template.*

[Friction factor]* Friction factor used to calculate the head loss due to flow.

[not present for this option]. Patran Thermal will compute the friction factor from Moody’s chart.

Scale factor to the MPID_F material property defined in the FLUID template.

Note: A zero MPID_F activates the Moody equation.

[Coeff thermal expansion]

Coefficient of thermal expansion used in calculation of buoyancy head.

note: Gravitational constant and direction is specified under Hydraulic Run Control Parameters.

Thermal expansion coefficient is defined with an MPID_BETA material property in FLUID template. *

* a dummy value must be entered for these parameters.


Constant Property with Moody Curve Variable Property


66

Template Definition For Option 3

Flow Network Bar-TurbineThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This element is used to define a turbine in a flow network.

FLUID TID #MPID's IOPTMPID_RHO MPID_MU MPID_CPMPID_LOSS_COEFF MPID_BETA MPID_F

FLUID Template record type.TID User template ID. A nonzero value which couples the Element Property

record to the information referenced in the template file.MPID_RHO Material property ID which references the specific weight of the fluid flowing

through the flow network (units of F/L3). Specific weight must be consistent with the units that are used to solve the thermal problem. If applicable to the system of units, Patran Thermal will convert specific weight to mass-density based on the ICCALC flag.

MPID_MU Material property ID which references the dynamic viscosity of the fluid flowing through the network (units = M/LT).

MPID_CP Material property ID which references the specific heat of the fluid flowing through the network.

MPID_LOSS_COEFF

Material property ID which defines a variable Head Loss Coefficient

MPID_BETA Material property ID which references the coefficient of thermal expansion used in calculating the buoyancy head (g * HBETA * DT).

MPID_F Material property ID which references the friction factor used to calculate the head loss due to flow in a tube. If not specified, friction factor is calculated with Moody's equation.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Flow network bar Turbine element Bar/2

67Input Properties

Input required for the options available for Turbine.

Property Name

Option Description

Constant Property Variable Property

[TID] Supply a non-zero dummy TID value.

Pointer to FLUID Template ID in template.dat.

IOPT Enter a 6. Enter a 7.


68

Template Definition for Option 7

[Fluid density]

[Fluid viscosity]

[Specific Heat]


Fluid density (MPID_RHO), viscosity (MPID_MU) and specific heat (MPID_CP) are defined in the FLUID template. A dummy value must be entered on the form.

[Turbine head] Constant turbine head, cannot go positive.

Turbine head is defined with an MPID_HEAD material property in the FLUID template. The independent variable for head can be time or flowrate. A dummy value must be entered on this form.

Note: For head vs flowrate, select the independent variable ITSCALE in the MPID as “temperature” in the same units as solution temperature units, ICCALC flag.

Property Name

Option Description


FLUID TID #MPID's IOPTMPID_RHO MPID_MU MPID_CPMPID_HEAD

FLUID Template record type.TID User template ID. A nonzero value which couples the Element Property record to the

information referenced in the template file.MPID_RHO Material property ID which references the specific weight of the fluid flowing


69Input Properties

Flow Network Bar-PumpThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This element is used to define a pump in a flow network.



MPID_HEAD Turbine head as function of time or flow rate.

Note: Turbine head can be a function of time or flow rate. For independent variable of flow rate, build the MPID as if it were “temperature” dependent in the same ITSCAL units as the solution temperature units, ICCALC.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Flow network bar Pump element Bar/2


70

Input required for the options available for Pump.


Constant Property Variable Property[TID] Supply a non-zero dummy

TID value.Pointer to FLUID Template ID in template.dat.

IOPT Enter a 4.+ Enter a 5.

71Input Properties

[Fluid density]

[Fluid viscosity]

[Specific Heat]


Fluid density (MPID_RHO), viscosity (MPID_MU) and specific heat (MPID_CP) are defined in the FLUID template. A dummy value must be entered on the form.

[Turbine head] Constant pump head, cannot go negative.

Pump head is defined with an MPID_HEAD material property in the FLUID template. The independent variable for head can be time or flowrate. A dummy value must be entered on this form.

Note: For head vs flowrate, select the independent variable ITSCALE in the MPID as “temperature” in the same units as solution temperature units, ICCALC flag.




72


Flow Network Bar-Check ValveThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This element defines a check valve in the flow network. A flow reversal would close the valve.

FLUID TID MPID's IOPTMPID_RHO MPID_MU MPID_CPMPID_HEAD

FLUID Template record type.TID User template ID. A nonzero value which couples the Element Property record

to the information referenced in the template file.MPID_RHO Material property ID which references the specific weight of the fluid flowing




MPID_HEAD Pump head as function of time or flow rate.

Note: Pump head can be a function of time or flow rate. For independent variable of flow rate, build the MPID as if it were “temperature” dependent in the same ITSCAL units as the solution temperature units, ICCALC.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Flow network bar Check Valve element Bar/2

73Input Properties

This is a list of data input available for creating the flow network bar element, which were not shown on the previous page. Use the scroll bars to view these properties.

Option 9, CHECK VALVE, constant physical and material properties for fluid flow in a tube. One way flow. If the fluid flow is not from NODE1 to NODE2, the diameter becomes zero (0.0). Friction factor is evaluated by Patran Thermal using Moody’s equation.

Property Name Description[Pipe roughness] Enter pipe roughness.[Head loss coeff] Enter the head loss coefficient. This can represent head loss in pipe

bends, valves, fittings, etc.[Fluid density]

[Fluid viscosity]

[Specific Heat]

Enter the constant fluid density, viscosity, specific head. If the fluid density or viscosity or specific heat are not constants, they have to be defined with MPIDs in the template and the data input on this form is ignored. However, some dummy data has to be entered.

[Coeff thermal expansion] Enter coefficient of thermal expansion.


74

Option 10, CHECK VALVE, constant physical and variable material properties for fluid flow in a tube. One way flow. If the fluid flow is not from NODE1 to NODE2, the diameter becomes zero ( 0.0 ). Material properties defined with MPID's. Requires template definition.

TID A dummy ID, not used by Patran Thermal flow network. Supply a nonzero dummy TID. No template record required.

IOPT The option chosen for the flow bar element. IOPT = 9.DIAM A hydraulic diameter of the flow passage defined as 4 * CSArea / wetted

perimeter. (For a circular cross section hydraulic diameter = physical diameter.) If diameter is not specified, it will be calculated using the cross sectional area and wetted perimeter.

CSAA Cross sectional area of the flow passage. If it is not specified, it will be calculated assuming a circular cross sectional and specified diameter.

PERIM Wetted perimeter of the flow passage. If it is not specified, it is calculated assuming a circular cross section.

LENGTH The length of the bar element. If it is not specified, it will be calculated as the straight line distance between the end nodes of the bar element.

ROUGHNESS Surface roughness of the tube or the flow passage.LOSS_COEFF Head loss coefficient to account for minor losses in the flow network, e.g. losses

in bends, tees, values, sudden expansion/contraction, etc.DENSITY The specific weight of the fluid flowing through the flow network (units of

F/L3). Specific weight must be consistent with the units that are used to solve the thermal problem. If applicable to the system of units, Patran Thermal will convert specific weight to mass-density based on the ICCALC flag.

VISCOSITY Dynamic viscosity of the fluid flowing through the network (units = M/LT).SPECIFIC_HEAT Specific heat of the fluid flowing through the network.HBETA Is the coefficient of THERMAL expansion used in calculation of buoyancy head

(g * HBETA * DT).

75Input Properties

.

Template Definition:

TID User template ID. A nonzero value which couples the PFEG record to the information referenced in the template file.



CSAA Cross sectional area of the flow passage. If it is not specified, it will be calculated assuming a circular cross sectional and specified diameter.

PERIM Wetted perimeter of the flow passage. If it is not specified, it is calculated assuming a circular cross section.


ROUGHNESS Surface roughness of the tube or the flow passage.LOSS_COEFF Head loss coefficient to account for minor losses in the flow network, e.g., losses

in bends, tees, values, sudden expansion/contraction, etc. This loss coefficient becomes a scale factor and is used as a multiplier to the value return from the MPID_LOSS_COEFF material property.

FLUID TID MPID's IOPTMPID_RHO MPID_MU MPID_CPMPID_LOSS_COEFF MPID_BETA MPID_F


record to the information referenced in the template file.MPID_RHO Material property ID which references the specific weight of the fluid

flowing through the flow network (units of F/L3). Specific weight must be consistent with the units that are used to solve the thermal problem. If applicable to the system of units, Patran Thermal will convert specific weight to mass-density based on the ICCALC flag.




76


This is a head loss element used to define the losses in a flow network (e.g., losses in orifices, valves, bend, tees, etc.).

MPID_BETA Material property ID which references the coefficient of THERMAL expansion used in calculating the buoyancy head (g * HBETA * DT).

MPID_F Material property ID which references the friction factor used to calculate the head loss due to flow in a tube. If a MPID_F is not specified, the friction factor is calculated using Patran Thermal's Moody equation.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Flow network bar Head loss element Bar/2

77Input Properties

.

Option 8, LOSS ELEMENT or CONTROL VALVE, variable parameters for fluid flow in a tube. Parameters input in the Element Property form will be used as scale factors applied to the material property evaluations obtained for the MPIDs defined. Requires template definition.


78


TID User template ID. A nonzero value which couples the Element Property record to the information referenced in the template file.




ROUGHNESS Surface roughness of the tube or the flow passage.LOSS_COEFF Head loss coefficient to account for minor losses in the flow network, e.g. losses

in bends, tees, values, sudden expansion/contraction, etc. This loss coefficient becomes a scale factor and is used as a multiplier to the value returned from the MPID_LOSS_COEFF material property.

FLUID TID #MPID's IOPTMPID_DIAMMPID_RHO MPID_MU MPID_CPMPID_EPS MPID_LOSS_COEFF MPID_BETA MPID_F


record to the information referenced in the template file.MPID_DIAM Material property ID which defines a diameter. This can be used to define

variable geometry as a function of time or temperature.MPID_RHO Material property ID which references the specific weight of the fluid flowing

through the flow network (units of F/L3). Specific weight is consistent with the units that are used to solve the thermal problem. If applicable to the system of units, Patran Thermal will convert specific weight to mass-density based on the ICCALC flag.



MPID_EPS Material property ID which references the tubing roughness.

79Input Properties

Flow Network Bar-PlenumThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This is a plenum element used in a flow network to define a large reservoir.

MPID_LOSS_COEF Material property ID which references the loss coefficient. Could be used to model the change in loss coefficient of a global valve which has different openings as a function of time.

MPID_BETA Material property ID which references the coefficient of thermal expansion used in calculating the buoyancy head (g * HBETA * DT).

MPID_F Material property ID which references the friction factor used to calculate the head loss due to flow in a tube.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Flow network bar Plenum element Bar/2


80

Option 11, PLENUM, constant physical and material properties. Conditions across a plenum element are unaffected by flow. The head can be altered by gravity.

Option 12, PLENUM, variable material properties. Conditions across a plenum element are unaffected by flow. The head can be altered by gravity. Material properties defined with MPIDs. Requires template definition.

TID A dummy ID, not used by Patran Thermal flow network. Supply a nonzero dummy TID. No template record required.

IOPT The option chosen for the flow bar element. IOPT = 11.DENSITY The specific weight of the fluid flowing through the flow network (units of

F/L3). Specific weight must be consistent with the units that are used to solve the thermal problem. *Hydraulic networks prefer a mass density and the units conversion is performed internally based on the ICCALC flag.

VISCOSITY Dynamic viscosity of the fluid flowing through the network (units = M/LT).SPECIFIC_HEAT Specific heat of the fluid flowing through the network.

81Input Properties

.

Template Definition:

Radiation Symmetry Bar RotationRadiation symmetry elements are used to communicate to the thermal radiation viewfactor code that a radiation symmetry condition exists. Such a condition implies that your Patran element surfaces which have radiation boundary conditions should either be reflected across a plane or else rotated about an axis (see Figure 4-2, Figure 4-3, Figure 4-6, and Figure 4-4). As shown in Figure 4-2, Figure 4-3, and Figure 4-4, the Patran Thermal system uses bar elements to denote reflections in 2-D (X-Y and R-Z) as well as rotational symmetry in 2-D and 3-D X-Y geometry.

Radiation symmetry elements in R-Z models always denote reflection about a plane parallel to the R axis.

Radiation symmetry elements in 2-D X-Y space without Element Property data always denote reflection across a plane.

Radiation symmetry elements in 2-D X-Y or 3-D X-Y-Z space always denote rotational symmetry, with the model being rotated a number of times by an angular increment (see Figure 4-4). The data for these rotational symmetry elements include (1) the number of rotations and (2) the angular increment for each successive rotation.

The nodes on these symmetry bars must have OD elements with Node Type of Information. Type I nodes are not passed through to the Solver during the translation process. This allows radiation symmetry elements to be built and their associated nodes do not participate in the thermal analysis calculations.

TID User template ID. A nonzero value which couples the PFEG record to the information referenced in the template file.

IOPT The option chosen for the flow bar element. IOPT=12.

FLUID TID #MPID's IOPTMPID_RHO MPID_MU MPID_CP

FLUID Template record type.TID User template ID. A nonzero value which couples the Element Property record

to the information referenced in the template file.MPID_RHO Material property ID which references the specific weight of the fluid flowing





82

These rotational symmetry bar elements data consist of the number of incremental rotations followed by the angular increment for each rotation. Since this model is 2-D X-Y, the bar must be parallel to the Z-axis. In 3-D X-Y-Z, the bar may be arbitrarily oriented. Rotational symmetry bars are illegal for 2-D R-Z models.

Figure 4-2 2-D Cartesian (X-Y) Reflective Symmetry Bar Element

83Input Properties

Figure 4-3 2-D, Axisymmetric (R-Z) Reflective Symmetry Bar Element

Note: For R-Z problems, radiation symmetry bars must be parallel to the R Axis.


84

Figure 4-4 Rotational Radiation Symmetry Bar Element (shown here by the circle-and crosshairs as being parallel to the Z-axis)

This form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied. This bar element is used to define radiation reflection symmetry. Input properties are not needed for this bar element.

This bar element is used to define radiation rotation symmetry.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Radiation symmetry bar rotation None Bar/2

85Input Properties

Axisymmetric BarIf the model is an R-Z-axisymmetric model, the bar elements are also treated as 2-D shell elements with surface areas for convection, radiation, and heat flux boundary conditions (see Figure 4-5). The bars (or shells) are assumed to be rotated 360° about the Z-axis. Any of Patran's X, Y, or Z-axis can be selected as the Z-axis (the axis of symmetry) by making the selection under Analysis/Translation Parameters.

As with the 2-D Cartesian bar elements, you must define element properties with a material and two thickness values (thickness at node 1 and thickness at node 2).


86

Figure 4-5 2-D Axisymmetric (R-Z) Bar Element Demonstrating Rotation About the Z-Axis


This bar element is used to define thin axisymmetric shells.

Analysis Type Dimension Type Option(s) TopologiesThermal 1D Axisymmetric Bar Full 360 Deg Rotation

Specified Deg of RotationBar/2

Note: This element property definition requires setting model dimensionality to axisymmetric geometry and selecting the radial and centerline axes under the Analysis, Translation Parameters.

87Input Properties

Thermal Shell

Triangular ElementsPatran Thermal supports 3-node linear triangular elements in either 2-D or 3-D Cartesian (X-Y or X-Y-Z) geometry or in 2-D axisymmetric (R-Z) geometry. 2-D Cartesian X-Y models must be built in the Patran X-Y plane. Whether the model dimensionality is 2-D X-Y, 2-D R-Z, or 3-D X-Y-Z is declared under Analysis/ Translation Parameters. Patran cannot tell the difference between any of these coordinate systems.

Allowed triangular elements include the following:

• 2-D X-Y conduction triangles• 2-D R-Z conduction triangles• 3-D X-Y-Z conduction triangles • 3-D X-Y-Z radiation symmetry triangles

The 2-D X-Y triangles are assumed to be of unit thickness in the Z direction. The 2-D R-Z triangles are assumed to be rotated through 360 degrees. The 3-D X-Y-Z conductive triangles (3-D shell elements) may be oriented at any angle and must have thickness data at each node. 2-D triangular elements do not use any thickness data.

For 3-D conductive triangular shell elements, all three orientation angles may be supplied, as well as the three thickness values.


88

Quadrilateral ElementsPatran Thermal supports 4-node quadrilateral elements in the following geometries:

• 2-D Cartesian X-Y geometry• 2-D axisymmetric R-Z, which to Patran is still X-Y geometry • 3-D Cartesian X-Y-Z geometry

2-D Cartesian X-Y models must be built in the Patran X-Y plane. 2-D axisymmetric R-Z models may be built in any plane defined by two Patran axes, e.g., X-Y, Y-Z, X-Z. The dimensionality of the model; i.e., 2-D X-Y, 2-D R-Z, or 3-D X-Y-Z is defined under Analysis/Translation Parameters.

The 2-D X-Y quadrilaterals are assumed to be of unit thickness, the 2-D R-Z quadrilaterals are assumed to be rotated through 360 degrees, and the 3-D X-Y-Z quadrilateral shell elements must be given thickness data.

Both 2-D Cartesian and 3-D shell elements support boundary conditions applied through their edges.


This form applies to quad and tri shell elements and require thickness definitions.

Analysis Type Dimension Type Option(s) TopologiesThermal 2D Shell Shell

Scaled Shell Element

Quad/4, Tri/3

89Input Properties

Example 1: Thermal Shell - CID Option

Rotations reference a cylindrical coordinate system.


90

Example 2: Thermal Shell - Elemental Option

Rotations reference the elemental coordinate system (Nastran definition).

91Input Properties

Thermal 2DThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.


92

This form applies to 2D elements. In Patran Thermal, they are treated as unit depth.

Thermal Axisymmetric - Full 360 Degree RotationThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

Analysis Type Dimension Type Option(s) TopologiesThermal 2D Thermal 2D None Quad/4, Tri/3

Important:This element property definition requires setting model dimensionality to 2D Plane.

93Input Properties

This form applies to axisymmetric quad and tri elements.

Thermal Axisymmetric - Specified Degrees of RotationThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied

Analysis Type Dimension Type Option(s) TopologiesThermal 2D Thermal Axisymmetric Full 360 Deg Quad/4, Tri/3

Note: This element property definition requires setting model dimensionality to axisymmetric geometry and selecting the radial and centerline axes under Analysis, Translation Parameters.


94

.

This form is typically used when modeling a mixed Axisymmetric and 3D model. It applies to axisymmetric quad and tri elements.

Radiation Symmetry TriNo input properties required.

The 3-D symmetry triangular element shown in Figure 4-6 happens to lie in the X-Y Plane. This is not required for 3-D symmetry triangular elements. Radiating element surfaces will be reflected across the

Analysis Type Dimension Type Option(s) TopologiesThermal 2D Thermal

AxisymmetricSpecified Degs Quad/4, Tri/3

Important:This element property definition requires setting model dimensionality to axisymmetric geometry and selecting the radial and centerline axes under Analysis, Translation Parameters. The axisymmetric elements must lie on the plane and the 3D component must lie in the first quadrant.

95Input Properties

plane defined by the triangular element. Nodes on these symmetry triangular elements must have OD elements with Node Type “Information.” These nodes will not participate in the thermal analysis calculations.

Figure 4-6 3-D Symmetry Triangular Element

Convective QuadConvective quadrilateral elements may be used to apply convective boundary conditions to 2-D X-Y or 2-D R-Z models (see Figure 4-7). The advantage of using convective quadrilateral elements as opposed to the CONV LBC form occurs when a spatial variation of fluid temperature along a fluid-surface interface occurs, and it is necessary to model the fluid as a series of nodes paralleling the surface.

The shaded elements in Figure 4-7 represent convective quadrilateral elements. These elements may be used to apply convective boundary conditions to surfaces where the fluid temperature is to be represented by a series of fluid nodes. The data for convective quadrilateral elements consist of the CONV template TID number, followed by as many GP values (geometric properties) needed to supply from Patran. The remaining GP values will be taken, as with the CONV LBC form, from the CONV template.


96

Figure 4-7 Axisymmetric Cylinder with Convective Quadrilateral Elements Attached

Typically, the fluid nodes are chained together with advective bar elements to model the energy being carried along on the mass flow stream. The fluid nodes determine which nodes should have convective resistors generated between them to apply the correct convective boundary conditions for the model.

Convective quadrilaterals must have at least one fluid node associated with each element. Note that if a convective quadrilateral element has fewer than two surface thermal nodes, there is no surface area associated with the element and hence no convective resistors will be generated for the element. This typically occurs at convex corners.


This is a convective quad element used to define convective heat transfer between solid and fluid. No cross resistors are generated for convective quad elements.

Analysis Type Dimension Type Option(s) TopologiesThermal 2D Convective Quad Quad/4

97Input Properties

Thermal 3D SolidPatran Thermal supports 4-node tetrahedral elements for conduction in 3-D Cartesian coordinates. Patran Thermal also supports 6-node wedge elements for conduction in 3-D Cartesian coordinates.

Hexahedral ElementsPatran Thermal supports 8-node hexahedral elements for conduction in 3-D Cartesian coordinates. FE Hex elements generate conductive resistors and capacitors using a finite element formulation. Finite Diff Hex elements generate conductive resistors and capacitors using a finite element formulation on skewed or orthotropic elements and a finite difference formulation on rectangular isotropic elements. The advantage of this approach is that models typically run somewhat faster than the pure finite element models with virtually no loss of accuracy.



98

This form applies to three-dimensional, isoparametric solid elements.

Thermal 3D Solid/Finite Diff HexThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

This form applies to finite difference orthogonal hex elements.

Analysis Type Dimension Type Option(s) TopologiesThermal 3D Thermal 3D Solid FE hex,tet,wedge Hex/8, Tet/4,

Wedge/6

Analysis Type Dimension Type Option(s) TopologiesThermal 3D Thermal 3D Solid Finite diff hex Hex/8

99Input Properties

Thermal 3D Solid/Scaled Finite Element Hex, Tet, WedgeThis form appears when the Input Properties button is selected on the Element Properties form and the following options have been applied.

Note: If a name is entered, the next available MID number will be assigned for use by Patran Thermal.

Important:Do not mix material names and MID references in the same model.


100

This form is typically used for mixed axisymmetric and 3D models. The axisymmetric portion is treated as a 360-degree rotation and the 3D elements are applied a multiplying factor to scale the capacitance and surface area by the number of times the 3D component repeats.

Analysis Type Dimension Type Option(s) TopologiesThermal 3D Thermal 3D Solid Scaled FE

hex,tet,wedge Hex/8, Tet/4, Wedge/6

101Input Properties

Convective Hex/Wedge

Convective HexConvective hexahedral elements can be used to generate convective resistors between Convective Fluid nodes and Thermal Surface nodes (see Figure 4-8). Any one face of a Convective hexahedral element may be defined by type Fluid nodes, but the remaining 4 nodes must be type Thermal.


102

Figure 4-8 Example of Legal Convective Hex Elements

These elements can also be used to specify contact coefficients (contact resistance) between surfaces.

Convective WedgePatran Thermal supports convective wedge elements. These elements can be used to generate convective resistors between Fluid nodes and Thermal solid nodes. Valid convective wedge elements are shown in Figure 4-9.

As can be seen in Figure 4-9, any one triangular face may have all type F nodes, or the degenerate edge (nodes 1 and 4) may be type F nodes. Any other arrangement is illegal. These elements can also be used to define contact resistances. These elements must be given Element Properties consisting of a CONV Template ID pointer and appropriate geometric parameters for the chosen configuration.

103Input Properties

Figure 4-9 Convective Wedge Elements showing usage of Node Type “Fluid” to designate which face will be considered the Thermal Surface


These are convective hex/wedge elements used to define convective heat transfer between solid and fluid. No cross resistors are generated for convective hex/wedge elements.

Analysis Type Dimension Type Option(s) TopologiesThermal 3D Convective Hex/Wedge None Hex/8,

Wedge/6


104

105Loads and Boundary Conditions

Loads and Boundary ConditionsThe Loads and Boundary Conditions form appears when the Loads ⁄BCs toggle, located on the Patran main form, is chosen. The selections on this form will determine which Loads and Boundary Condition forms will appear, and ultimately, which Patran Thermal loads and boundary conditions will be created.

The following page gives an introduction to the Loads and Boundary Conditions forms, followed by details of the loads and boundary conditions supported by the Patran Thermal Solver.

Loads and Boundary Conditions FormThe Loads and Boundary Conditions form is used to create Patran Thermal loads and boundary conditions. For more information, see Loads and Boundary Conditions Form (p. 27) in the Patran Reference Manual.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisLoads and Boundary Conditions

106

The following table outlines the options when the Analysis Type is set to Thermal.


Object Type Option• Temperature (PThermal) • Nodal • Fixed

• Time Table• Coupled• Initial• Template

• Heating (PThermal) • Element Uniform• Element Variable

• Flux, Fixed

• Element Uniform • Flux, Time Table• Flux, Temperature Table

• Element Uniform• Element Variable

• Template, Fluxes • Template, Volumetric Heat

• Nodal • Template, Nodal Source• Element Variable • Flux, Spatial Field (Time)

• Convection • Element Uniform• Element Variable

• Fixed Coefficient

• Element Uniform • Time Table• Temperature Table

• Element Uniform• Element Variable• Element Variable

• Template Convection•

• Spatial Field (Time)• Radiation • Element Uniform

• Element Variable• Ambient Node

• Element Uniform• Element Variable

• Gap Radiation•

• Element Uniform • Template ViewFactors• Element Uniform • Spacecraft, STEP_TAS


108

The following specifies the defined variables which are used to specify the Boundary Condition ID. By using the variable name the specific ID can be assigned in a define statement and only needs changing at one location in any special PCL one may write using the defined boundary conditions.

• Pressure • Nodal • Fixed• Time Table• Initial• Template

• Mass Flow • Nodal • Fixed• Time Table• Initial• Template

Object Option LBC ID Variable Name• Temperature

(PThermal)• Fixed• Time Table• Coupled• Initial• Template

• LBC_PTH_TEMP_TIME_TABL_ID• LBC_PTHERMAL_TEMP_FIXD_ID• LBC_PTHERMAL_TEMP_COUP_ID• LBC_PTHERMAL_TEMP_INIT_ID• LBC_PTHERMAL_TEMP_TMPL_ID

• Heating (PThermal)

• Flux, Fixed • LBC_PTH_HEAT_FLUX_FIXD_ID• Flux, Time Table• Flux, Temperature Table

• LBC_PTH_HEAT_FLUX_TIME_TABL_ID• LBC_PTH_HEAT_FLUX_TEMP_TABL_ID

• Template, Fluxes • Template, Volumetric

Heat

• LBC_PTHERMAL_HEAT_TMPL_FLUX_ID• LBC_PTHERMAL_HEAT_TMPL_VOLH_ID

• Template, Nodal Source • LBC_PTHERMAL_HEAT_TMPL_NODS_ID• Flux, Spatial Field (Time) • LBC_VAR_PTH_FIELD_NAME

• Convection • Fixed Coefficient • LBC_PTH_CONV_FIXD_ID• Time Table• Temperature Table

• LBC_PTH_CONV_TIME_TABL_ID• LBC_PTH_CONV_TEMP_TABL_ID

• Template Convection • LBC_PTHERMAL_CONV_TMPL_ID• Spatial Field (Time) • LBC_VAR_PTH_FIELD_NAME

Object Type Option


• Radiation • Ambient Node• Gap Radiation• Template ViewFactors• Spacecraft, STEP_TAS

• LBC_PTH_RADI_AMBN_ID• LBC_PTHERMAL_RADI_GAP_ID• LBC_PTHERMAL_RADI_TMPL_ID• LBC_PTH_RADI_STAS_ID

• Pressure • Fixed• Time Table• Initial• Template

• LBC_PTHERMAL_PRES_FIXD_ID• LBC_PTH_PRES_TIME_TABL_ID• LBC_PTHERMAL_PRES_TMPL_ID• LBC_PTHERMAL_PRES_INIT_ID

• Mass Flow • Fixed• Time Table• Initial• Template

• LBC_PTHERMAL_MDOT_FIXD_ID• LBC_PTH_MDOT_TIME_TABL_ID• LBC_PTH_MDOT_GEN_FUNC_ID• LBC_PTHERMAL_MDOT_INIT_ID

Object Option LBC ID Variable Name


110

The actual LBC IDs are defined in the following table.

LBC ID LBC Load Type• 51 • Temperature (PThermal)[Fixed]• 52 • Temperature (PThermal)[Time Table]• 54 • Temperature (PThermal)[Coupled]• 55 • Temperature (PThermal)[Initial]• 56 • Temperature (PThermal)[Template]• 60 • Heating (PThermal)[]Flux, Fixed• 61 • Heating (PThermal)[Flux, Time Table]• 62 • Heating (PThermal)[Flux, Temperature Table]• 67 • Heating (PThermal)[Template, Fluxes]• 68 • Heating (PThermal)[Template, Volumetric Heat]• 69 • Heating (PThermal)[Template, Nodal Source]• 70 • Heating (PThermal)[Flux, Spatial Field(Time)] • 101 • Convection (PThermal)[Fixed Coefficient]• 102 • Convection (PThermal)[Time Table]• 103 • Convection (PThermal)[Temperature Table]• 105 • Convection (PThermal)[Template, Convection]• 107 • Convection (PThermal)[Spatial Field(Time)] • 109 • Radiation (PThermal)[Ambient Node]• 110 • Radiation (PThermal)[Gap Radiation]• 112 • Radiation (PThermal)[Template, View Factors]• 113 • Radiation (PThermal)[Spacecraft, STEP_TAS]• 116 • Pressure (PThermal)[Fixed]• 117 • Pressure (PThermal)[Time Table]• 119 • Pressure (PThermal)[Initial]• 120 • Pressure (PThermal)[Template]• 124 • Mass Flow Rate (PThermal)[Fixed]• 125 • Mass Flow Rate (PThermal)[Time Table]• 127 • Mass Flow Rate (PThermal)[Initial]• 128 • Mass Flow Rate (PThermal)[Template]


Input DataThis subordinate form appears when the Input Data button is selected and Static is the Load Case Type selection (the only Load Case selection currently supported). For Patran Thermal boundary conditions are not specified separately for steady state and transient conditions which are defined in the analysis

Object Option LBC ID• Temperature (PThermal) • Fixed

• Time Table• Coupled• Initial• Template

• 51• 52• 54• 55• 56

• Heating (PThermal) • Flux, Fixed• Flux, Time Table• Flux, Temperature Table• Template, Fluxes • Template, Volumetric Heat• Template, Nodal Source• Flux, Spatial Field (Time)

• 60• 61• 62• 67• 68• 69• 70

• Convection • Fixed Coefficient• Time Table• Temperature Table• Template Convection• Spatial Field (Time)

• 101• 102• 103• 105• 107

• Radiation • Ambient Node• Gap Radiation• Template ViewFactors• Spacecraft, STEP_TAS

• 109• 110• 112• 113

• Pressure • Fixed• Time Table• Initial• Template

• 116• 117• 119• 120

• Mass Flow • Fixed• Time Table• Initial• Template

• 124• 125• 127• 128


112

form. Thus the distinction between static and dynamic load case has no meaning. The information contained on this form will vary according to the selected Object.

All boundary condition options which do not contain the word “Template” involve direct translation and the information is not written to the neutral file. All the boundary condition information is complete within the Patran model and does not require any supplementary information to complete the input to the solution module. However, all options which contain the word “Template” translate information passed through the neutral file and many case requires additional information which is defined through a template file. The actual translation is done external to Patran. This template file can be built independently or with the template builder available in the analysis menu.

Defined below is a typical form for Convection (PThermal) as the Object and Fixed Coefficient as the Option.


Spatial Fields

Select Application Region


114

All of the non-template convection options have two selection regions for determining where the convection boundary condition is to be applied (Application Region) and the corresponding fluid node (Coupling Region).

Time TableInput Data form when Time Table option is selected.


Fixed OptionFollowing are the input forms for the convection template option.


116

Non Fixed Option


Gap RadiationGap Radiation is used for all radiation between entities is not strongly influence by view factor considerations.


118

General RadiationGeneral Radiation considerations are calculated with P/VIEWFACTOR. The boundary conditions are defined through enclosure IDs and template information. Each enclosure is treated as a separate entity but may have several boundary conditions associated with it. Each material is identified by its own Template ID and different surface characteristics can be further separated by different boundary conditions.


Template DefinitionsFor variable boundary conditions, Patran Thermal uses a pointer system called a Template ID to reference more data contained in an auxiliary file. This external file is named template.dat.apnd and is created using forms on the analysis menu or the system editor in the same directory level as the Patran database. When a job is submitted from Patran, the template.dat.apnd file (if it exists) will be appended to the template.dat file created automatically in the sub-directory with the Job Name.

In the current release of Patran Thermal, Template IDs are required for all boundary conditions with “Template” in the option name. The following table shows boundary condition data types, Template Name and applicable field types.


120

Object TablesOn the input data form, there are areas where the load data values are defined. The data fields presented depend on the selected Object and Type. In some cases, the data fields also depend on the selected Target Element Type. These Object Tables list and define the various input data which pertain to a specific selected object:

LBC Type of Data Template Required Fields Referenced

• Temperature • Constant or Spatial Field • •

• Time dependent • MACRO (p. 687) • Non-Spatial/General

• Heating • Constant or Spatial Field • •

• Time or Temperature • MACRO (p. 687) • Non-Spatial/General

• Convection • Constant or Spatial Field • •

• Time or Temperature • CONV (p. 690)

Note: Use Config 29 • Material Prop/General

• Correlations Library • CONV (p. 690) • Material Prop/General

• Radiation • Viewfactor code data • VFAC (p. 692) • Material Prop/General

• TRASYS Preference • VTRA (p. 696) •

• NEVADA Preference • VNEV (p. 698) •

• Pressure • Constant or Spatial Field • •


• Mass Flow • Constant or Spatial Field • •



Temperature (PThermal)

Object Type OptionTemperature Nodal Fixed

Input Data DescriptionTemperature Temperature (value or spatial field) that remains fixed in the

analysis.

Object Type OptionTemperature Nodal Time Table

Input Data DescriptionName Micro Function name that Table will be stored under in the general fields.Description Definition of Table.Time

Temperature

Data pairs which define a bounded linear table which specifies temperature as a function of time.

Object Type OptionTemperature Nodal Initial

Input Data DescriptionTemperature Initial temperature (value or spatial field). If the entire model has the same

initial temperature, set the global value under Analysis/Solution_Parameters/Run control Parameters.

Object Type OptionTemperature Nodal Coupled


122

Input Data Description<No Input Data> Usage: This option only uses Select Application Regions to define the

primary application region and the companion region that will be thermally coupled. This option can be used to couple topologically non-congruent meshes, to model cyclical symmetry or to tie nodes in mixed 3D and axisymmetric models. The entities will be coupled based on a Selection order or Closest Approach, as chosen. To maintain accurate transient effects, the thermal capacitance of the node in the companion region will include the capacitance of the node in the primary application region.


Convection (PThermal)

Object Type OptionTemperature Nodal Template

Input Data DescriptionTemperature Scale factor on temperature returned from template evaluation.Template ID Positive template ID points into template.dat file.

Object Type Target OptionConvection Element Uniform

Element Variable 1D, 2D, 3D Template, Convection

Input Data DescriptionConvection Coefficient Convective heat transfer coefficient or a geometric property if

template ID is used.Convection Template ID Positive integer, points convection template in template.dat file.Fluid Node ID The node ID to which the head is convected.

Object Type Target OptionConvection Element Uniform

Element Variable

1D, 2D, 3D

Nodal,1D,2D,3D

Fixed Coefficient

Input Data DescriptionConvection Coefficient Heat transfer coefficient (constant or spatial field). Correlations

library not allowed in this option. The corresponding area for convection will be based on application region 1 entities. This boundary condition is useful for connecting dissimilar meshes with thermal resistance in between or for tying a surface to a fluid stream.

Convection between regions can be applied to 1D elements for 2D thermal or axisymmetric elements. Currently not supported for 1D elements in 3D space.

Note: Filter must be the same (either Geometry or FEM) on both application regions.


124

Heat Flux

Nodal Heat

Volumetric Heat

Pressure

Object Type Target OptionHeating Element Uniform

Element Variable

1D, 2D, 3D Template, Fluxes

Input Data DescriptionHeat Flux Heat flux value or a scale factor if template ID is used.Template ID Positive integer, points heat macro in template.dat file.

Object Type OptionHeating Nodal Template, Nodal Source

Input Data DescriptionHeat Source Nodal heat source or a scale factor if template ID is used.Template ID Positive integer, points macro in template.dat file.

Object Type Target OptionHeating Element Uniform

Element Variable

1D, 2D, 3D Template, Volumetric Heat

Input Data DescriptionHeat Source Volumetric heat source or scale factor if template ID is used.Template ID Positive integer, points macro in template.dat file.

Object Type OptionPressure Nodal Template, Fixed, Initial

Input Data DescriptionPressure Nodal pressure or scale factor if template ID is used.Template ID Positive integer, points pmacro in template.dat file.


Mass Flow

Radiation (PThermal)

Viewfactor

Object Type OptionMass Flow Nodal Template,

Fixed,

Initial

Input Data DescriptionMass Flow Rate Nodal mass flow node or scale factor is template ID is used.Template ID Positive integer, points mmacro in template.dat file.

Object Type Target OptionRadiation (PThermal) Element Uniform

Element Variable

1D, 2D, 3D

Nodal, 1D, 2D, 3D

Gap Radiation

Input Data DescriptionSurface 1 Emissivity Emissivity value or spatial field for application region 1. Surface 2 Emissivity Emissivity value or spatial field for companion region 2 (default = 1).Form Factor Viewfactor value applied to the radiation couplings (default = 1).

Note: Filter must be the same (either Geometry or FEM) on both application regions.

Object Type Target OptionRadiation Element Uniform 1D, 2D, 3D Viewfactor

Input Data DescriptionEnclosed ID Enter radiation enclosure ID.Template ID Positive Integer points to VFAC, VTRA or VNEV data in template .dat

file.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisLoad Cases

126

Load CasesPatran Thermal does not currently support Load Cases. All the boundary conditions must be entered in the Default load case for both steady state and transient runs. This load case is automatically selected when the analysis is submitted from the Analysis Form.

Note: Use of Load Cases in the Patran Thermal model can cause unexpected results.

Chapter 4: Module OperationPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

4 Module Operation

Preference Files 128

Reference Notes 129

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisPreference Files

128

Preference FilesIf Full Run is set, the Apply selection in the Analysis form will create the appropriate interface files and execute the solver. The interface files created include:

• A neutral file• The analysis control files qin.dat and vf.ctl• The script for executing the model patq.inp• The material property file mat.dat and template.dat• The field definition file micro.dat

The user has control of which files are created and how the execution is to proceed through the parameters in the Submit Options form. These submit parameters have been defaulted for new jobs. With Patran Thermal, multiple jobs can be created from the same Patran database. The model files will appear in subdirectories named with the jobname that was entered in the Analysis form.

Patran Thermal is designed to support the functionality in P/THERMAL including the View factor code, the coupled thermal/hydraulic networks, creation of a SINDA input deck, both forward and reverse translation of enclosure tria and quad surfaces to the TRASYS and NEVADA codes.

129Chapter 4: Module OperationReference Notes

Reference NotesThese notes are a supplement to the PAT 312 Patran Thermal class and are intended to answer the most commonly asked Patran Thermal questions.

Set up1. The FORTRAN & C programming languages must be loaded on the workstation that will be used

for running the thermal solution (not required for the Patran SINDA translator). 2. The environmental variable PATH must include the location of FORTRAN 77 (F77), CPP

compilers and related libraries. Type echo $PATH in the UNIX window to verify the PATH variable.

3. Copy the file p3epilog.pcl from the Patran installation directory to your home directory. Every time you enter Patran, an additional pull down menu called “Shareware-Thermal Tools” will be available to simplify building and verifying Patran Thermal models. This can be accomplished as follows:% cd

% cp <inst_dir>/patran3/shareware/msc/unsupported/utilities/p3epilog.pcl.

where <inst_dir> is the installation directory for your Patran executables.

Model Creation

Loads & Boundary Conditions

Temperature Varying with TimeYou will be specifying the temperature variation as a Non Spatial Field as follows:

Select the Fields Button.

Set the Action-Object-Method to Create-Non Spatial-General respectively.

Enter a field name that describes this boundary condition in the Field Name databox.

Select the Input Data button.

To enter a table of time vs. temperature data, set the Select Function Term to mfid_indx_linr_tabl which stands for microfunction of indexed linear table.

Enter a Micro Function ID (MFID) to a number that you will reference in the template.dat MACRO template. You can modify the default number to a number that matches the MACRO number you will use in the Loads/BCs form.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisReference Notes

130

Fill out the spreadsheet of Independent Variable (time) vs. Dependent Variable (temperature) data. Select OK and Apply.

Select the Loads/BCs Button.

Set the Action-Object-Type to Create-Temperature(PThermal)-Nodal.

Set the Option to Variable.


Input Temperature Scale Factor of “1” and enter a Template ID of 1 for your first varying temperature boundary condition.

Enter the desired node(s) in the Select Application Region subform and select Apply.

In the same directory where the database exists, create a file called template.dat.apnd. All information in this file will be copied to the template.dat file in the job name subdirectory when the job has been submitted.

Enter the following information into the template.dat.apnd file:

MACRO 1 1 0 0 1.01

where the “1” following the keyword MACRO refers to the template ID that you entered in the Loads/BCs Input Data form. The “1.0” is a scale factor for the temperatures and the “1” on the second line refers to the microfunction ID that you specified in the Micro Function ID (MFID) databox in the Fields form.

If you have two time varying boundary conditions, then you would add two additional lines as follows:

MACRO 2 1 0 0 1.02

Note that comment cards in this file begin with the character “*”.

See class problem number 5 for an example of this process.

Heat Varying with TimeThe heat application is very similar to the “Temperature Varying with Time” application described above.

Variable heat input can be in the form of nodal heat source, volumetric heat flux, and heat flux.

You will be specifying the heat variation as a Non Spatial Field as follows:

Select the Fields Button.

Set the Action-Object-Method to Create-Non Spatial-General respectively.

Enter a field name that describes this boundary condition in the Field Name databox.



To enter a table of time vs. temperature data, set the Select Function Term to mfid_linr_indx_table which stands for microfunction of linear indexed table.

Enter a Micro Function ID (MFID) to a number that you will reference in the template.dat.apnd MACRO template. You can modify the default number to a number (3 for example) that matches the MACRO number you will use in the Loads/BCs form.

Fill out the spreadsheet of Independent Variable (time) vs. Dependent Variable (heat) data.

Select the Loads/BCs Button.

Set the Action-Object-Type to either

Create-Heating(PThermal)-Nodal.Set the Option menu to either Nodal Source, Fluxes, or Volumetric Generation.

Select the Target Element Type as appropriate.


Input Loads/BC Scale Factor “1” and enter a Template ID of 3 (arbitrary) for a varying heat boundary condition.

Enter the desired node(s) (or element(s) for Flux and Volumetric Generation) in the Select Application Region subform and select Apply.

In the same directory where the database exists, create (or open) a file called template.dat.apnd. All information in this file will be copied to the template.dat file in the job name subdirectory when the job has been submitted.


MACRO 3 1 0 0 1.03

where the “3” following the keyword MACRO refers to the template ID that you entered in the Loads/BCs Input Data form. The “1.0” is a scale factor for the temperatures and the “3” on the second line refers to the microfunction ID that you specified in the Micro Function ID (MFID) databox in the Fields form.

If you have two time varying boundary conditions, then you would add two additional lines as follows:

MACRO 4 1 0 0 1.04


Total Heat ApplicationTo apply a known amount of heat to a region of elements, use the Shareware pull down menu, and select Total Heat. Use the Per Area option if the heat is applied evenly over the element faces and use Per Volume if the heat is to be spread out evenly throughout the solid element (Tet/ Wedge/ Hex).


132

Convection Varying with Time or TemperatureSelect the Loads/BCs button and set the Action-Object-Type to Create-Convection(PThermal)-Element Uniform. Set the Option to Use Correlations. This option give the user the choice of using correlations (or a table as in this case).

Enter a New Set Name that describes this boundary condition. Set the Target Element Type to 2D for plate elements or 3D for solid element faces.

Leave the Loads/BC Set Scale Factor at 1 (this is not a convection coefficient scale factor!). Leave the Convection Coefficient blank. This is a scale factor to the table of convection coefficients vs. time or temperature. Input a Convection Template ID value (1 for example). This is a pointer to the template.dat.apnd file. Enter the Fluid Node ID and select OK. Select Application Region, select the FEM button and select the desired elements. Select OK & then Apply.




The “CONV” is a keyword for convection templates. The first “1” is the template id supplied in the Loads/BCs Input Data form. “29” denotes the convection configuration for time or temperature varying convection as described in the documentation. “0” denotes the number of geometric properties (GPs) supplied by this template, and the last “1” is the number of MPIDs for the configuration. This MPID is given on the next line & is arbitrarily given the number “5001”.

The number of GP values defined by the template is zero in this case because the correlation only requires the nodal subarea which is supplied by Patran and PATQ during the translation process.

In the same directory where the database and template.dat.apnd file exist, create (or open) a file called “mat.dat.apnd”. All information in this file will be copied to the “mat.dat” file in the job name subdirectory when the job has been submitted.

Enter the table into the “mat.dat.apnd” file as follows:

*CONV TID# config # # of GPs # of MPIDsCONV 1 29 0 15001


The MPID is a keyword for material property id. The “5001” refers back to the “5001” given in the template.dat.apnd file. “ITABLE” denotes that this is an indexed table which means that Patran Thermal starts the search in this table where it left off in the last time step and is therefore faster than the “TABLE”.

Any input other than “MDATA” or “/” after an MPID keyword is assumed to be a comment. For this example, the “Convection Coefficient (Btu/hr-ft^2-F) as a function of Time (seconds)” is a comment that describes this table.

The “/” is required at the end of each MPID input.

To input this table of convection coefficient as a function of temperature, use the keywords “Fahrenheit,” “Rankine”, “Celsius”, or “Kelvin” in place of the keyword “Time”.

Contact ConductanceSelect the Loads/BCs button and set the Action-Object-Type to Create-Convection(PThermal)-Element Uniform. Set the Option to Between Regions. When selecting the Application Region, set the Order to Closest Approach. To create contact conductance between two geometric solid faces that contact each other in the Patran model, both application regions should be element based (such as setting Region 2 to 3D). If Nodal is selected for Region 2, and a surface or face of a solid geometric entity is selected, Patran will fill the listboxes with the nodes from both contacting faces even if only one face is selected (an error will flag this when selecting the Analysis Apply button).

RadiationPCL that creates the radiation boundary condition and eliminates the need for editing the “template.dat.apnd” file for viewfactor templates exists and will be included on the Shareware pulldown menu as described above.

or

Select the Loads/BCs button and set the Action-Object-Type to Create-Radiation (PThermal)-Element Uniform. Set the Option to View Factors

MPID 5001 ITABLE Time 1.0Convection Coefficient (Btu/hr-ft^2-F) as a function of Time (seconds)

MDATA 0. .9MDATA 1. 1.1MDATA 1.5 1.15MDATA 2.0 1.4MDATA 4.0 1.8/


134

Enter a New Set Name that describes this boundary condition. Set the Target Element Type to 2D for plate elements or 3D for solid element faces.


Leave the Loads/BC Set Scale Factor at 1 (this is not a viewfactor scale factor!). Input a viewfactor Template ID value (1 for example). This is a pointer to the template.dat.apnd file. Leave the Participating Media Node databox empty. If your model is not completely enclosed, enter the ambient node into the Ambient Node Id databox. Viewfactors that do not see any portion of your model will see the temperature of this node (fixed or variable). The viewfactor code will not attempt to calculate viewfactors for all elements with the same Convex Set Id (any integer number). The Obstruction Flag databox is another CPU saving feature that can be left empty. The default viewfactor direction will be applied in the element normal direction. Under the Finite Elements Verify-Element-Normal form, arrows can be displayed in the element normal direction. If the opposite direction is desired, Enter “1” in the Top/Bottom Flag databox to apply the viewfactor boundary condition in the bottom direction. In order to have radiation off of both faces of a plate element, two viewfactor applications must be applied, one with the Top/Bottom Flag empty (or set to “0”), and the other with the flag set to “1”. The last databox is the Enclosure Id. Only viewfactors with the same Enclosure Id have the possibility of seeing each other.

Select Application Region, select the FEM button and select the desired elements. Select OK & then Apply.



Note that comment cards in this file begin with the character “*”

“VFAC” is a keyword to signify viewfactor template. The first “1” is the template id that you supplied in the Loads/BCs Input Data form. Assuming you are not performing spectral analysis (emissivity varying with wavelength), then the"# of bands” is zero.

The second line (of non-comment input) starts with the emissivity. This is the only required input for this line. The “collapse” flag at the end of this line is beneficial in reducing the size of your radiation network by up to a factor of 16. The “tau” is the transmissivity and is set to “1” unless you have a participating media. The “emis. MPID” is the material property ID for variable emissivity. Set this to zero for fixed emissivity. The same is true for “tau MPID”. Since this is not a spectral problem, “band1”, “band2”, and “kflag” are set to “0”. All element viewfactors with the same “collapse” flag ID will be condensed.

*VFAC TID # # bandsVFAC 1 0*emissivity tau emis. MPID tau MPID band # 1 band # 2 kflag collapse

flag0.8 1 0 0 0 0 0 1


Materials

Varying with TemperatureIf you wish to use the materials from the Patran Thermal library, use the Shareware-Thermal Tools pull down menu item P/Thermal Materials List. Input the name of the material of interest, such as “alu” to get a listing of all materials in the Patran Thermal material library that contain the characters “alu”. To use this material in your model, you may skip the Materials form entirely and input this material ID in the Element Properties, Input Data form in the Material listbox

To input your own materials that vary with temperature, Select the Fields button from the main menu, and set the Action-Object-Method to Create Material Property General. Enter a descriptive name for this field, and select Input Data. Select the desired option for you field. For a table, select mpid_indx_linr_tabl. Now you can enter a table of temperature versus material property (i.e. conductivity, etc.). Be sure to select Apply after completing input for each table

This information will get written to your jobname directory into a new mat.dat file when you submit your job.

All other material properties can be input from the Materials form selected from the main form.

Element PropertiesFor 3 dimensional models (vary in x, y, and z), be sure to use the Action-Dimension-Type of Create-2D-Shell for plate elements (quads or trias). Release 1.4 no longer requires the input of four thickness values for each corner.

For the case where a model is 2 dimensional (all of model is constructed in x-y plane) and is assumed to have unit depth thickness in the z-direction, use the Action-Dimension-Type of Create-2D-Thermal 2D for plate elements. Since unit depth is assumed, no input of element thickness is input.

Load CasesLoad cases are not supported for Patran Thermal. Create all of the loads and boundary conditions in the default loadcase.

Analysis (job submittal)Select Analysis from the main menu. Be sure to correctly specify the model dimensionality in the Solution Type menu. 2D assumes that all of your model is in the x-y plane and that you have unit depth in the z direction. For models which have bar elements with cross sectional area, plate elements with thickness, and/or solid elements, use the 3D selection. See Element Properties, 53.

If you are resubmitting you analysis, and you wish to reuse the settings you had from your last run, select a previous job from the Available Jobs listbox in the Analysis form. You can then modify any setting you wish before you select the Apply button.


136

Results Verification

Job Submittal StatusTo verify that your job submittal was successful, examine the patq.msg files and look for error messages. If you are running a viewfactor job, you can check the status by examining the vf.msg message file.

Note that the shareware pull down menu has a Translation Status option that examines the contents of the patq.msg file for you.

Temperature ConvergenceIn the jobname directory, enter the command qstat or qstat -b. qstat will give the status of your job while (and after) it's running. Check to make sure that the temperature change between iterations is decreasing and is approaching 1.e-05 for convergence with the default parameters. If your model has not converged after 1999 iterations (the default maximum allowable for steady state as displayed by qstat), verify that your material properties are correct. Note that the convergence criteria is based on the slope of the model convergence and not a simple iterative delta in temperature.

The Patran Thermal Tools pulldown menu has a Thermal Convergence Status option that makes x-y plots of the convergence status. Be sure to use the Clear button when finished viewing these plots to clear the windows for the next time you wish to check the status.

Total Heat InputAt the UNIX window in the jobname directory, enter the UNIX command:

% ls qout*

The highest version of qout.dat.* is the most recent output file. Verify that the total heat you intended to input to the model matches the value of TOTAL HEAT SOURCE INPUT ENERGY displayed from the UNIX command:

% grep HEAT qout.dat.#

where # is the highest value of qout.dat in your directory.

Total System Heat BalanceFrom the same “grep” command given above, be sure that the value of SYSTEM HEAT BALANCE is small relative to the TOTAL HEAT SOURCE INPUT ENERGY (less than 1% is a common rule of thumb) for steady state analyses.

Nodal Heat BalanceBefore submitting your job, select Output Requests from the Analysis form. Select the Nodal Results Type button, and select all 8 of the output options. When you post process your results, you will have the net nodal heat flux at each node. If you create a new group without the boundary nodes, your fringe plot should be very close to zero for all nodes. If all of you values are exactly 0, then you probably did not set


the output requests form to include all eight output options. You can resubmit the job for one iteration to get a new result file.

Results DisplayFrom the jobname directory, enter the UNIX command:

% ls -rt nr*

to get a listing of the nodal result files in reverse time order. The last file should be read in for a steady state analysis. This command is important as the following example illustrates.

Run 1: Material properties were input in meters instead of millimeters for one of the materials. The job never converges and give output files every 500 iterations; nr0.nrf.1, nr1.nrf.1, nr2.nrf.1, nr3.nrf.1.

Run 2: Material property corrected and job converges in 27 iterations resulting in nr0.nrf.2.

Then the Analysis form is selected and the Action is set to Read Results, Select Results File. After selecting the jobname directory, which will filter on the nr* files, the last one listed is nr3.nrf.1 (from UNIX alphanumeric sorting). However, the nr0.nrf.2 file should be selected if the most recent result is desired.

Next, select the Select Rslt Template File button, scroll towards the bottom and pick the last pthermal result template (pthermal_nod_T.res_tmpl) and select apply. This result template allows for all 8 result values that may have optionally been selected within the Output Requests-Nodal Results File Format form before the job was submitted. If only temperature was requested in the output files (default) then the remaining values of net nodal heat flux, etc. will be zero.

Select Results and display the fringe plot.


138

Chapter 5: Running an AnalysisPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

5 Running an Analysis

Review of the Analysis Application 140

Analysis Form 141

Delete 163

Template Generator 164

Thermal Tools 175

Plot View Factors 183

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisReview of the Analysis Application

140

Review of the Analysis ApplicationBy choosing the Analysis application, located on the Patran main form, the Analysis form will appear. When performing an analysis, several option menus are available. The selections made in this Analysis form will determine which option menu is presented, and ultimately, which Patran Thermal analysis will be performed.

141Chapter 5: Running an AnalysisAnalysis Form

Analysis FormThis form is used to set up the parameters for the analysis, and will submit the job to the Patran Thermal solver.

Restart FilePthermal can be restarted with initial temperatures based on a nodal results file from a previous execution. If a nodal results file is specified it will be used to define initial temperatures for the new run. If it is desired to continue with a given file numbering sequence, it can be specified. The time of the restart file will be the new time associated with the current analysis unless the user defines a new time. The

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisAnalysis Form

142

restart case will ignore the temperature specifications unless one flags that the initial temperatures are to over write the restart temperatures.The new initial temperatures can be for any of the nodes.

Translation ParametersThis subordinate form appears when the Translation Parameters button is selected on the Analysis form.


Solution TypeThis subordinate form appears when the Solution Type button is selected on the Analysis form.


144

Solution ParametersThis subordinate form appears when the Solution Parameters button is selected on the Analysis form.


Run Control ParametersThis subordinate form appears when the Run Control Parameters button is selected on the Solution Parameters form.

This subordinate form appears when the Maximum Time Step button is selected on the Run Control Parameters form.


146

This subordinate form appears when the Maximum Time Step button is selected on the Run Control Parameters form.


Convergence ParametersThis subordinate form appears when the Convergence Parameters button is selected on the Solution Parameters form.


148

Iteration ParametersThis subordinate form appears when the Iteration Parameters button is selected on the Solution Parameters form.


Relaxation ParametersThis subordinate form appears when the Relaxation Parameters button is selected on the Solution Parameters form.


150

(Hydraulic) Run Control ParametersThis subordinate form appears when the (Hydraulic) Run Control Parameters button is selected on the Solution Parameters form.


(View Factor) Run Control ParametersThis subordinate form appears when the (View Factor) Run Control Parameters button is selected on the Solution Parameters form.


152

(View Factor) Linkage FilesThis subordinate form appears when the (View Factor) Linkage Files button is selected on the Solution Parameters form.


Output RequestThis subordinate form appears when the Output Request button is selected on the Analysis form.


154

Print Interval ParametersThis subordinate form appears when the Print Interval Controls button is selected on the Output Request form.


Nodal Results File FormatThis subordinate form appears when the Nodal Results File Format button is selected on the Output Request form.


156

Result Template LabelsResults templates based on the selected output parameters will be created, put is the execution subdirectory and used as defaults to load the results back into PATRAN. The user can edit the labels that will be used to create the template file.Defaults are selected from the temperature options used for the


output and calculation temperatures and the default material properties to be used. Only labels that were selected for output entities can be edited and written to the results template file.

Print Block DefinitionThis subordinate form appears when the Print Block Definition button is selected on the Output Request form.


158

Plot Block DefinitionThis subordinate form appears when the Plot Block Definition button is selected on the Output Request form.


Diagnostic OutputThis subordinate form appears when the Diagnostic Output button is selected on the Output Request form.


160

SINDA Input Deck FormatThis subordinate form appears when the SINDA Input Deck Format button is selected on the Output Request form.


Submit OptionsThis subordinate form appears when the Submit Options button is selected on the Analysis form.


162

163Chapter 5: Running an AnalysisDelete

DeleteThis form is available when the Action on the Analysis form is set to Delete. This can be used to delete jobs from the database, revert a job to default values or create a new job starting with the default values.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisTemplate Generator

164

Template GeneratorThis form appears when the Action is set to Build Template on the Analysis form.

Template File Data FormThe Template File Data form is accessed from the Analysis form and enables the user to create the template file entries (MID, MACRO, CONV, VFAC, FLUID, VTRA and VNEV).

The following Actions are supported:

• Create - Allows the user to create a template file entry. The user selects the type of template entry to be created (i.e., Object), fills in the appropriate definition data and selects the Apply button. After a template entry has been defined, the user may view the data in the template spreadsheet form (from the Display Spreadsheet toggle) and may (optionally) write the data to a file from that form.

• Modify - Allows the user to modify an existing template file entry. The user selects the template entry to be modified (i.e., Object and Defined Entry), changes the appropriate data and selects the Apply button.

• Read - The Read action allows the user to read an existing template file (.dat or .apnd) into Patran. Existing entries may subsequently be modified or new entries created as outlined above.

• Delete - Entries may be removed from the template file spreadsheet by selecting the template type (Object menu) and ID (from the listbox) and selecting the Apply button.

Note that the actions listed above affect the entries in the template file spreadsheet. No file output is produced until the user selects the Write File button on the spreadsheet form at which time all entries in the spreadsheet are output to the desired file.

165Chapter 5: Running an AnalysisTemplate Generator

MID


166

MACRO


CONV


168

VFAC


VFAC (Non Wavelength Dependent)Used to indicate viewfactor information associated with the VFAC template.


170

VFAC (Wavelength Dependent)Used to indicate spectrally dependent radiation information associated with the VFAC template. Setting the Wavelength Dependent toggle results in the display of the Advanced Options Data form. In this form, the user indicates the number of wavebands associated with the template entry and then proceeds by filling in the spreadsheet for the required data (see LBC section for more information).

The spreadsheet is completed by entering data for the highlighted cell in the input databox (located underneath the No. Wavebands databox). Once the spreadsheet values have been supplied, the Apply button (Template File Data form) is hit to complete the definition of the VFAC entry.


FLUID


172

ReadThe Read action allows the user to read in existing template data from an external file. The extension of the template file (either .apnd or .dat) is indicated by setting the Template File Type switch. The Template File… button is used to specify the name of the template file to be imported. Once the Apply button has been hit the template entries are placed in the template file spreadsheet for viewing.

If the Sort Entries toggle is set to ON, the template entries are sorted first by type (i.e., all MID, MACRO, CONV, etc. entries are placed together) and then by ID within each type (i.e., MID 5, MID 10, MID 25, etc.).


Template Entries SpreadsheetSelecting the Display Spreadsheet toggle, results in the display of the Template Entries form. This form contains a spreadsheet where all the currently defined template data may be viewed and also provides widgets to operate on that data.


174

The contents of a spreadsheet cell may be modified by selecting the cell and changing the contents of the Input Data databox. A comment line is indicated by placing a * in the first character of the first cell of a row (note: all other cells in that row will be ignored in this case). The comment text follows the asterisk. Clicking on any cell will result in the contents of the cell being displayed under the spreadsheet. This allows for viewing of long text comment strings.

Toward the bottom of the spreadsheet, information labels indicating the number and type of defined template entries are displayed.

The Write File button allows the user to write the spreadsheet contents to an external file. A file may be appended or a new file generated (Note: It is recommended to import a template file, add/modify entries and then export a new file rather than append to an existing file.) by selecting the Append File/New File switch above the Write File button. Once the Write File button has been selected, the user will be prompted for the filename to write to; selecting the OK button results in file output.

All spreadsheet contents may be cleared using the Clear button. This action is irreversible (the user is prompted to verify that this was the intended action) in that once the spreadsheet is cleared, the entries may not be retrieved but must be recreated from scratch or imported from an external file.

175Chapter 5: Running an AnalysisThermal Tools

Thermal ToolsSeveral of the PCL shareware tools for Pthermal have been moved to Pthermal’s Analysis Form when the action selected is Thermal Tools. Most of these function perform just as they did in the past except for the convenience of getting to them.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisThermal Tools

176

Pthermal Results ReaderThe Results Reader allows the user to see and select specific results files based on the type of results, file extension and various selection methods. The automatically created template files associated with the specific results will be used if it exist. Specific user template files can be used if the user so selects.


Pthermal Job StatusThe Job Status allows the user to get a plot of the convergence status to be obtain during execution or after the job has completed. This will access the stat.bin file extracting the results and making a XY plot of the convergence factor and relaxation factor versus the iteration number for both transient and steady state runs.


178

Total Heat per AreaThe Total Heat per Area allows the user to specify a total heating load over a given area. The user specifies the heating and then follows it up with the element 2D surfaces or 3D faces that the heating is to be distributed over. The proper flux is then determined and a heat flux boundary condition is applied to each of the nodal subareas. Later the user can edit the boundary condition through the normal Loads/BCs forms.


Total Heat per VolumeThe Total Heat per Volume allows the user to specify a total heating load that is to be applied over some group of 3D elements evenly. The total heat load is specified and the group of 3D elements it is to be distributed over is selected and the proper volumetric heat flux is determined. The resultant boundary condition can be edited through the normal Loads/BCs forms.


180

Temperature InterpolationThe temperature interpolation function does????


Node Modified by FieldOne can modify the node location or field by a given offset or by using a scalar function. All modification must be done in the global co-ordinate system.


182

183Chapter 5: Running an AnalysisPlot View Factors

Plot View FactorsPthermal creates a binary view factor data file that contains all raw information related to the view factors between each surface in a given enclosure.The view factors are calculated based on the subnodal representation of each element.This data can be extracted and put in text data files that will enable the user to determine relative view factor data between any surface or group of surfaces. The subsequent data then loses the finer view factor information associated with the subnodal area; however, this is only for examination purposes. The radiation network used in the calculations still reflects the subnodal refinement. This operation is not automatic and requires interactive operation by the users. There is a sequence of operations the user needs to follow to create and investigate the calculated view factors. The first time through the user must Create VF Data Files for the desired enclosure. To plot the view factors, groups will be created that have surfaces related to each enclosure with the Create Enclosure Surfaces button. Each time before creating a plot, first select the controls associated with a given enclosure through the Define/Get VF Plot Controls. Only post the group with the desired enclosure information and define the view factor groups with Plot View Factors.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisPlot View Factors

184

Create VF Data FilesThe Pthermal view factor raw data file contains too much information and is not in a form that is convenient to create arbitrary view factor information and plot it. Six text files are created that contains information that the user can examine and is in a form that can easily be used to create view factors for any user selected grouping. These files will have a user defined prefix which is usually the same as the job name directory. Appended to this is the enclosure ID while the final suffix denotes the type of file. All files have data only with no header information. Each file type is defined below.

Control file .cntr

The control file contains a single record with:

1. Enclosure ID


2. Number of Surfaces3. Dimension Code4. Surface Offset5. Maximum Surface ID6. Maximum Number of Nodes per Surface

This information applies to one enclosure and will become initial values for subsequent enclosures. The dimension code is defined ( p 143 view factor manual ). The surface offset is adjusted such that a surface ID can be easily identified. The maximum surface ID will be used as the seed offset for the next enclosure.

Correspondence File .cors

The correspondence file contains information that relates each surface to element and node data related to the model. For each surface there are two records.

The first record contains:

1. Surface ID1. Element ID1. Element Face ID1. Surface Configuration1. Number of Nodes

The second record contains:

1. Node ID’s for this surface

Surface Area .area

This file contains the surface area of each surface. Each record contains:

1. Surface ID1. Surface Area

Residual View Factor .vfsp

The value of each view factor in a closed enclosure should be one. The thermal module uses the view factors as calculated rather than make adjustments to have each one summing to one. It is felt that numerical calculation would over predict as well as under predict so over the whole enclosure numerical error would cancel better than attempting to make each one have exact closure on one. Also, any leaks in an enclosure would let energy escape the enclosure is included as part of the residual. By plotting the residuals one can see the errors or get the view factor to space. The residual file contains:

1. Surface ID1. One minus the Sum of View Factor - ( 1.0 - Fi )


186

View Factor Matrix .mtrx

A file is created in which for each surface the product of the surface area and the view factor to every other surface is specified. This is the information that sequentially is used by the user to create plots from one view factor group to another. All information associated with each surface is written as a single record

1. Surface ID(i), ( AiFij for j from surface i to number of surfaces

View Factor .vfij

A file is created in which for each surface the view factor to every other surface is specified. This can be examined to determine the view factor from any surface to any other surface; however, this file is not used in any subsequent view factor calculations. All information associated with each surface is written as a single record

1. Surface ID(i), ( Fij for j from surface i to number of surfaceThe form to extract these files is shown below. The sequence of operations are to select a raw view factor data file, validate the file selection and then create the view factor data files. If the raw data file selected the validation operation will produce an error message rather than letting one to continue.:


Define/Get VF Plot ControlsWhenever the user is going to create a set of view factor plots they must define the enclosure desired and specify some identifier that will be associated with each set of view factor plots. This is done through the Plot Controls form. Each enclosure has a set of files associated with it for plot creation. This file identifies the enclosure and information necessary to size arrays etc. for the view factor calculations. The desired control file is selected from the Select VF Plot Control File Name and then the needed data is loaded through the Get VF Plot Controls.

Create Enclosure SurfacesFor convenience and so users can isolate different parts of the model, a separate group is defined with a set of surfaces corresponding to each enclosure. This group should be all that is posted when one is plotting various view factors. After one has finished examining the view factors and this information will no longer be needed and can be deleted.


188

Post Enclosure GroupTo simplify looking at radiation surfaces one should only post the surfaces in the enclosure being examined. Using the Group -> Post form select the surface group.


Plot View FactorsThe plot view factors form allows the user to group of surfaces in a from-to grouping they desire to obtain view factors between. An option is available to create a file with a summary of the data just plotted.


190

Plotting the ResultsThe element results in the database can be plotted through the Results -> Create -> Fringe forms.

1. First select the results case one desires to examine.2. Determine the type of plot you desire. The view factors are from a selected group to each

individual element in the to group. Thus the most meaningful is probably the Element Fill since the calculated view factor is the weighted sum of each subnodal view factor. If discrete contours are desired the element values are evaluated for all elements associated with each node.


3. The Domain should be set to None if the element file is to be used so that the true view factor for each element is plotted. If the contour plots are desired set the Domain to All Entities if the continuous option is used.

The fringe selection forms are shown below.

Following are some examples of view factor plots. The example is two parallel plates one unit on a side and 0.6 units apart. For this case the view factor to space is greater than it is to the other plate for each element.


192

A plot from a single surface to all other surfaces is shown below in the element file mode. Note that the sum of all view factors is from the single surface to all other surfaces is included in the title.


The same plot is shown below in a discrete/smooth format.


194

A sample of the output is shown below. The surface list for each group is defined in the output. The total surface area for the from surface and the resulting view factor between the groups is defined. A second set of area and view factor is shown. This is the total surface area of all elements in the enclosure and the sum of all view factor area products in the enclosure. For a totally enclosed system the total sum for area and area view factor product should be one. The individual view factor from the “from group” to each individual surface is output. A partial table is shown below. The Surface ID that is defined by radiating surface with the given offset and its corresponding element ID for the view factor specified in the first column. The next surfaces continues incrementing by one for the next columns on that given row. There is no break on a row if the numbering has gaps. For example surface 1121 begins with element 121.5 (where .5 indicates the top of a surface) begins in the first column. Element 210.6 is shown in the second column, but the element ID is not consistent with the surface ID until the next row. The file below is only representative and does not include all columns or rows.


196

Chapter 6: Reading ResultsPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

6 Reading Results

Overview of Results Import 198

File Menu Import 199

Analysis Form 201

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisOverview of Results Import

198

Overview of Results ImportPatran Thermal can import results through either of two approaches. The first approach is through the Import option of the File menu under the Patran main form. The second approach is through the Read Results option on the Analysis form under the Analysis application. Both approaches require the Analysis Preferences to be set for Patran Thermal to create the proper analysis specific forms.

Once the analysis results are imported into the database, they become part of the database unless specifically deleted. Multiple results files can be imported into the same database.

199Chapter 6: Reading ResultsFile Menu Import

File Menu ImportPatran can import Patran Thermal results through the File menu Import option.

When the Import option is selected and Analysis Preferences is set to Patran Thermal, the analysis specific Import form appears. See Import Form, 199 for more information.

Import FormWhen results are imported in this manner, the entire file is input into the database. If selective results types are desired in the database, then the Analysis Form, 201 Read Results approach must be used.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisFile Menu Import

200

201Chapter 6: Reading ResultsAnalysis Form

Analysis FormThe Read Results Analysis form can be used to read results from a Patran Thermal analysis by setting the Action to Read Result.


202

Chapter 7: Thermal/Hydraulic TheoryPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

7 Thermal/Hydraulic Theory

Network Methods 204

Numerical Analysis Techniques 216

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisNetwork Methods

204

Network MethodsThis section provides an introduction to network concepts, techniques, and terminology. Network analog methods are discussed for thermal problems which involve conduction, convection, gray-body radiation, wavelength-dependent radiation, advection (mass flow), heat sources, or temperature sources. Recommendations for certain problem types are also presented.

The Thermal NetworkThermal analysts have for some time been trained to formulate heat transfer problems in terms of thermal networks which are analogous to resistor-capacitor electrical networks. The basic formula for current flow across an electrical resistor is:

(7-1)

where I is current, E is voltage, and R is electrical resistance.

In heat transfer, the analogous equation for heat flow across a thermal resistor is:

(7-2)

For transient current or heat flows, flow into an electrical or thermal capacitor must be included. For current flow I into an electrical capacitor, the equation is:

(7-3)

where C is the value of the electrical capacitor and dE/dt is the time derivative of the voltage across the capacitor. In heat transfer, the analogous equation for heat flow into a thermal capacitor is:

(7-4)

The value of C in this equation is taken from:

(7-5)

where:

ρ = =density of the material associated with the node,

V = =volume associated with the node, and

Cp = =specific heat of the material associated with the node.

I 1 2→[ ] E 1[ ] E 2[ ]–( )R

------------------------------------=

Q 1 2→[ ] T 1[ ] T 2[ ]–( )R

------------------------------------=

I dEdt------- * C=

Q dTdt------- * C=

C ρ * V * CP=

205Chapter 7: Thermal/Hydraulic TheoryNetwork Methods

The parallels between electrical and heat transfer equations have led to the development of the thermal network concept. The remainder of this section defines more completely thermal network concepts, especially as they apply to the QTRAN thermal network program. QTRAN has taken the conventional thermal network concepts and has added to them vis-a-vis wavelength-dependent thermal radiation resistors, the three-node convective resistors, LaGrange cubic finite element resistors, and others. For those who are more comfortable with finite element concepts, it might be easier to think of a thermal resistor as a 1-D finite element. Another viewpoint is to simply think of the thermal resistors as computational molecules or numerical models, especially where normal thermal resistor concepts do not strictly apply (e.g., the three-node convective resistors and wavelength- dependent resistors).

Conduction NetworksThis section briefly outlines the fundamentals of the electrical network analog approach for conduction networks. It includes multidimensional transient and steady-state network models and the associated mathematical relations which govern them.

Steady State Cartesian ConductionSteady-state heat conduction networks in Cartesian coordinates will be the first network model discussed in this section due to their relative simplicity. Steady- state networks in general do not require thermal capacitors and are simple to derive from first principle considerations. Remember, however, that the conductive network is simply another method of arriving at a finite difference approximation to the problem. This implies that many of the numerical considerations which apply to more classical finite difference or finite element discretization schemes will also apply to thermal networks. There are two major reasons for resorting to a thermal network as the method of solving a problem: (1) the ease with which various combinations of boundary conditions may be handled as compared to the more classical finite difference or finite element schemes and (2) computational efficiency for large, strongly nonlinear problems. Network methods in general will allow more flexibility for the user (indeed, the finite element method may be thought of as a very powerful subset of the more general thermal network approach).

1-D conduction is the cornerstone for both 2-D and 3-D conduction. For starters, a Cartesian 1-D conductive resistor is defined as follows:

(7-6)

and the heat conducted from node 1 to node 2 is computed from the following expression:

(7-7)

Note: One convenient feature concerning thermal capacitors is that one node of the capacitor is always “grounded.” This contrasts with electrical capacitors, where an electrical capacitor may be connected to two separate voltage nodes and is not necessarily grounded. This forced grounding of thermal capacitors simplifies thermal networks and thermal network calculations (relative to electrical networks) considerably.

R Lengthk * Area( )

-------------------------------=

Q 1 2→[ ] T 1[ ] T 2[ ]–( )R

------------------------------------=


206

where:

Transient ConductionTransient conduction involves the added complications of capacitors, where a single capacitor value is defined as follows:

If the node in question lies at a material interface, it may be convenient to assign one capacitor to the node for each material at the interface. The heat equation being solved for transient conduction at a given node [i] is then seen to be:

(7-8)

which states the sum of all the capacitances multiplied by the time derivative of node [i] is equal to all of the heat flows across all resistances into the node.

(7-9)

While the maximum stable time step in the system does not affect QTRAN’s stability, it may have an effect on the execution time. In general, the smaller the stable time step the more time a given problem

Length distance between nodes 1 and 2

k thermal conductivity of the material

Area effective cross-sectional area between the two nodes through which heat is allowed to flow

Note: The conductance, G, is the reciprocal of the resistor value, R. For one dimension, a conduction problem consists merely of a string of conductive resistors going from node to node. For 2-D and 3-D, a conduction problem consists of a network of these resistors going from node to node in all three dimensions.

C the capacitor value

ρ the material density

Cp the material specific heat

C ρ= Volume Cp⋅ ⋅

C i n,[ ]dT i[ ]n 1=

all

∑T j[ ] T i[ ]–

R i j,[ ]---------------------------- dt

j 1=

all

∑=

Important:Since QTRAN uses implicit integration, stability considerations are not required. However, the maximum stable time steps for an explicit forward Euler algorithm would be given by the following expression:

dt maximum stable explicit[ ]

C K[ ]K 1=

all

∑

G i j,[ ]j i=

all

∑

--------------------------=


may take to execute. A network with tiny stable time steps tends to generate stiff systems of equations which are more difficult to solve than non-stiff systems. However, a network whose nodes have predominantly small stable time steps will also give better resolution in the time domain to fast transients, especially at very early times in the simulation. A rule of thumb for the mesh spacing (which directly affects the explicit stable time step) is to compute the approximate mesh spacing from the following formula:

(7-10)

This is an extremely approximate formula and you can typically violate it by a factor of several. If violated by orders of magnitude, however, the results may be in serious error. The formula given can be arrived at from several approaches. One approach is to look at the most significant term of a 1-D conduction solution which is an infinite series. Another approach is to look at response times and decay rates of exponentially damped dynamic systems. Try it out and see what results are obtained. Review past analyses that have been performed and compare the mesh spacing to this criteria.

Although this mesh spacing criteria is important in regions undergoing rapid change, this criteria can typically be grossly violated in regions where the transient is very mild.

Conduction in Cylindrical and Spherical GeometriesCylindrical, spherical, polar, triangular, skew, or other networks all use the same underlying principles as Cartesian meshes for both steady-state and transient runs. However, there are special formulas for the conductive resistance in these coordinate systems that must be used to account for the differences in effective cross-sectional areas. For hollow cylinders and a 360-degree circumference, the effective conductive resistance is as follows:

(7-11)

And, for spheres:

(7-12)

approximate average mesh spacing in regions of rapid change

thermal diffusivity

earliest time point of interest (e.g., first print dump for a transient problem

dxα * time i[ ]

5----------------------------<

dx

α kρ Cp⋅⟨ ⟩

---------------------=

t ime i[ ]

R cylinder[ ] 1n (R outer[ ] R inner[ ])⁄2 * π * k * Length

------------------------------------------------------------------=

R sphere[ ] R outer[ ] R inner[ ]–4 * π * R outer[ ] * R inner[ ] * k---------------------------------------------------------------------------------------=


208

Conduction with Phase ChangesHeat conduction with phase change introduces an extra term into the network capacitors. Specifically, the capacitors must now be able to properly account for latent heat effects at a given temperature as well as the normal specific heat effects. Furthermore, to be perfectly general a code must be able to account for multiple phase change temperatures and latent heat effects within each capacitor. In addition, simultaneous phase changes at multiple nodes with the transition direction going in either direction (e.g., either melting or freezing) must be allowed.

To be mathematically ideal, at least some phase changes are supposed to occur at a single temperature, not over a temperature band. This causes the internal energy of a material undergoing a phase transition to cease being a function of temperature. This can cause some rather significant numerical headaches, and the introduction of a narrow phase transition temperature range (say, 0.1 to 1.0 degrees in width) will not usually significantly affect the answers to most problems. The introduction of this artificial phase transition range has the benefit of causing the internal energy to be a function of temperature at all points, and this is a great advantage from a computational standpoint.

The advantage of smearing this phase change over a very narrow band is not, however, enough of an advantage to allow even QTRAN’s SNPSOR algorithm to converge if it relied only upon Newton’s Second Order Method. The “S” shape that the phase transition introduces into the nodal heat flow rate curve is a classic way to kill Newton’s methods. QTRAN, however, detects when the old time step’s temperature and the new time step’s temperature straddle or intrude into a phase transition region. At these times and for only those nodes involved, QTRAN’s SNPSOR algorithm reverts to a bisection algorithm technique which is immune to “S” curve effects. Thus, the SNPSOR algorithm remains convergent even for implicitly solved phase transition problems.

It is also possible to solve some problems involving phase transitions over a large temperature range by putting a bump into the specific heat curve and then being careful not to allow large temperature changes in a single time step. This has the advantage of sometimes being much faster than the built-in phase change algorithm, but it also carries some risk with regard to accuracy.

Phase transition problems tend to consume considerably more CPU time than normal problems. It is, therefore, an advantage to specify that a problem does not involve phase changes if it is known a-priori that this is the case. This is done by specifying 0 for all capacitor PHIDs. When using PATQ to translate a Patran neutral file, specify 0 for the PHID on all MID templates.

Convection NetworksConvection networks can be a source of great anxiety. They tend to embody an empirical convection coefficient h in the convective resistors, and the formulas used to compute this h value are usually highly

R[outer] outer radius of cylindrical or spherical section

R[inner] inner radius of cylindrical or spherical section

k thermal conductivity of the material

Length length of the cylindrical section


complex. Transition regimes also frequently exist, where the empirical correlation used for a particular configuration may be a function of Reynolds, Grashoff, Rayleigh, Prandtl, Graetz, and add infinitum number ranges.

For example, the pipe flow configuration in QTRAN uses five different correlations with seven factorial transition regimes based on everything from Reynolds number ranges to viscosity ratio ranges. Also, since the correlations are not in general continuous through the transition regimes, interpolation must be used when in a transition regime to maintain continuity and avoid numerical convergence problems. Further complications arise when mass flow through tubes or packed beds occur, as three temperatures are then needed. The following sections expand on these concepts.

Ordinary 2-Node Convection Thermal ResistorsThe majority of the QTRAN convection configurations are in keeping with the conventional thermal resistor concept in that there are two nodes associated with each resistor. The conventional convective resistance is given by the following expression:

(7-13)

where:

R is the thermal resistance, h is the convection coefficient, and Area is the surface area from which heat is being convected. The heat flow across the resistor is then given by:

(7-14)

The tricky detail of this operation, of course, is to compute an h value for the resistance expression. In general, empirical correlations must be relied upon. These correlations are usually somewhat tedious to evaluate, since they themselves are in general a function of temperature and/or temperature difference. Furthermore, each correlation is usually only applicable to a range of dimensionless parameters, and hence these parameters must be evaluated to determine which correlation to use for a given configuration. The result is a very painful (if done by hand) iterative solution for even a relatively simple convection problem.

QTRAN alleviates the pain somewhat by offering a convection library from which the user may select any one of 37 configurations which are in turn supported by 61 correlations (several generic correlations also exist). QTRAN will automatically and dynamically select the appropriate correlation for both the configuration type and the dimensionless parameter range for the resistor. A catalogue of available configurations is contained in Convection Library (Ch. 9) along with a catalogue of supporting correlations. All correlations are fully documented and referenced such that the user may easily locate the references from which the correlations were taken.

Special 3-Node Convection Thermal ResistorsAs stated previously, the majority of the QTRAN convection configurations are in keeping with the conventional thermal resistor concept in that two temperature nodes are associated with each resistor. However, certain configurations (i.e., configurations CFIG = 1, 2, 21, and 25) require the association of

R 1h * Area( )

----------------------------=

Q 1 2→[ ] T 1[ ] T 2[ ]–( )R

------------------------------------=


210

a third temperature node with the convective resistor. Configurations CFIG = 1, 2, and 21 are pipe flow configurations and CFIG = 25 is a flow through porous media configuration. For all four configurations, three temperature values are needed. The three temperatures needed are:

1. a wall (or media) temperature2. an upstream temperature 3. a downstream temperature

It is at this point that the computational hydrodynamics concept of “upwind differencing” must be introduced. Upwind differencing is a numerical technique that is used to maintain stability for a numerical solution which involves advection. Simply stated, upwind differencing assumes that information (in this case, heat) is carried only from upstream to downstream. Information (or heat) is never carried from downstream to upstream. The impact of upwind differencing on the three-node convective resistors is that the upstream node NEVER gains or loses heat through the convective resistor so long as the flow velocity associated with the resistor remains positive.

Thus, it is seen that all heat transfer through the three-node convective resistors occurs between the wall (or media) node and the downstream node. The upstream node is used solely as a reference temperature node for LMTD calculations (if appropriate) so long as the flow velocity is positive. The LMTD is used for those flow configurations for which it is appropriate, and a differential between the wall temperature and the average bulk fluid temperature is used for other configurations.

From this discussion, it is obvious to the casual observer that the three-node convective resistors do not account for advective heat transfer (i.e., the heat carried along on the mass flow). In order to complete a thermal model involving a three-node convective resistor, it is frequently necessary (depending on the boundary conditions of the problem) to use an advection resistor to properly account for the heat balance.

Another point that may not be quite so obvious is that the three-node convective resistors may not be directly used to compute entrance temperatures given that the wall (or media) and exit temperatures are known. Remember that the heat transfer to the upstream node is not a function of a the three-node convective resistor since the upstream node is used only as a reference temperature. The upstream node temperature must be taken from boundary conditions or else calculated from other thermal resistor, capacitor, and heat source influences.

Gray Body Radiation NetworksGray body radiation networks also differ slightly from the normal thermal resistor concept in that the potential across the radiative resistor is evaluated as σ * T 4, where σ is the Stefan-Boltzmann constant.

QTRAN automatically uses the σ * T 4 potential when evaluating gray-body resistors, and hence the difference between radiative and conductive resistors is essentially transparent to the user. Note that the σ * T 4 potential is also applicable to non-surface radiosity nodes such as are encountered in gray networks.

Note: There is no current way of assigning 3-noded convective resistors from Patran. To use any of the 3-noded configurations, they will have to be assigned manually.


The formula for radiative heat transfer used in thermal networks in QTRAN is as follows:

(7-15)

The formula for R is dependent upon whether R is a surface resistor, a view factor resistor with or without a participating media, and so on. The actual formulation of the specific resistor types is defined after Table 8-1 and Table 8-2 for gray body and wavelength dependent radiation respectively.

For more information on radiative networks, consult any radiative heat transfer book that describes the network approach. See Ref. 6. in Appendix A.

The gap radiation creates radiation coupling without the radiosity network or performing form factor calculations. Some assumption inherent in the formulation are that the area radiating is large relative to the distance between the radiating surfaces. A form factor may be included, but if it is significantly less than one, consideration should be given to using the radiosity network and calculating the appropriate form factors. Type 5 radiation resistors are used thus the emissivities must be constant. Type 5 resistor are constant and are treated internally as conductances. The last major assumption is that the two surfaces radiating to each other are of equal value. Since a form factor is included, small variation can be compensated for by adjusting emissivity or form factor values. The radiation conductance is determined with (7-16)

(7-16)

Wavelength Dependent Radiation NetworksWavelength-dependent thermal radiation networks are a rather significant extension of the gray-body radiation network theory. In essence, the normal radiosity network is divided up into discrete frequency bands such that the emissivities, transmissivities, and absorptivities of the radiating materials can be assumed to be gray within each frequency band. For each frequency band that is used, a distinct but frequently parallel radiosity network is generated between the radiating surfaces and participating media. Each frequency band network is typically coupled to any of the other bands only at the surfaces of the radiating materials or at participating media nodes. This treatment allows reflections from dissimilar surfaces to be handled correctly, and is directly analogous to the multigroup treatment used in certain high-energy physics codes. This approach does not assume an average emissivity over the entire spectrum (e.g., the Air Force Weapons Lab’s “TRAP” code), but instead inherently allows emissivities, absorptivities, and transmissivities to be functions of frequency band, temperature, and/or time.

Advection NetworksAdvection occurs whenever some quantity is carried along on a mass flow stream. For example, if hot fluid enters a container, heat (energy) is carried with the fluid into the container. Similarly, if a cold fluid enters a hot container, cold (or negative energy) is carried with the fluid into the container. This transfer of positive or negative energy by mass flow must be accounted for when doing thermal simulations if

Q 1 2→[ ] σ * T 1[ ]4 T 2[ ]4–( )

R-----------------------------------------------------=

C 1R---- A1F12

A11

ε1------ 1

ε2------ 1

F12----------- 2.0–+ +

------------------------------------------------------= = =


212

such mass flows exist. The mathematical equation for the heat added to node [i] by such a mass flow stream is as follows:

Q [1→2]=MDOT * Cp * ( T[1] - T[2] ) (7-17)

One facet of numerical stability should be mentioned at this point because of its influence on advective resistors. It is necessary to limit the transport of energy by advective resistors to one direction only for the purposes of the QTRAN program. Specifically, energy is carried by advective resistors only from the upstream node to the downstream node (which node is upstream or downstream is determined by the sign of the MDOT mass flow term). This scheme is immediately seen to be equivalent to one-sided or “upwind” differencing which is a common practice among numerical fluid flow analysts, and is commonly used because of its stability enhancing characteristics.

By introducing upwind differencing, we can guarantee that the system of equations has a stable solution. This does not mean, however, that the SNPSOR algorithm in QTRAN can always solve the system of equations. This is due to the point iterative nature of the SNPSOR algorithm. As long as the system of equations is diagonally dominant, point iterative schemes tend to work very well. However, the introduction of advection tends to weaken this diagonal dominance. As the diagonal dominance weakens, point iterative methods have more and more difficulty converging, until they eventually fail. One way of aiding convergence (at the expense of speed) is to under-relax. With a small enough relaxation parameter, a solution will usually converge. However, be aware that CPU times increase rapidly as the relaxation parameter approaches 0.0.

The user has the option of applying the relaxation parameters to the entire system of equations, by node group types, or on a node by node basis. To under relax, apply the under relaxation only to the advection nodes by using a relaxation multiplier less than one. Apply this to the advection nodes. This will direct the under relaxation only to those nodes that need to be under relaxed and still give some flexibility, by allowing the solution module to search for an optimum relaxation parameter.

Q [1→2] the amount of energy transported by the mass flow from node #1 to node #2

MDOT the mass rate of flow from node #1 to node #2

Cp the specific heat of the flowing mass

Note: QTRAN evaluates the specific heat as the integration between the temperatures of node #1 and node #2 using the temperature increment defined by CPDELT.

T [1] the temperature of node #1 (upstream node)

T [2] the temperature of node #2 (downstream node)


Heat and Temperature Source NetworksIn virtually all thermal problems either temperature sources or heat sources exist. A temperature source is defined to be simply an externally controlled boundary temperature. A heat source is defined to be anything that contributes heat to the network, not including the resistors and capacitors.

QTRAN MicrofunctionsMicrofunctions are a unique QTRAN feature. Frequently, there is a need to apply very complicated temperature or heat sources that may consist of tabular data, sines or cosines, exponentials, constants, or terms which may or may not be multiplied together or divided by one another. QTRAN lets each discrete component of a complicated temperature or heat source be defined as a “microfunction”. Once all of these component microfunctions have been defined, then a library is available from which to build the more complicated functions (macrofunctions) that are needed for temperature or heat sources. Many macrofunctions are allowed to reference the same microfunction. Thus, for a very complicated tabular data microfunction, it is only necessary to build it once and then reference it as many times as needed. Other microfunctions can then be used to multiply or scale this complicated microfunction. Currently, the argument of a microfunction can be either time, temperature, a temperature difference, a temperature average, or a σ * (T[1] 4 - T[2] 4) radiation potential. If the radiation potential is specified, QTRAN will convert the T[1] and T[2] values to degrees absolute before computing the radiation potential value.

QTRAN MacrofunctionsAs stated above, a macrofunction consists of one or more microfunctions that are either multiplied or divided by one another. Quite complicated macrofunctions can be expressed in this manner. Note that, when building temperature or heat sources, it is quite allowable to assign more than one macrofunction to the same node. Multiple macrofunctions assigned to the same node are simply added together to compute the final source value.

Flow NetworksThis section briefly outlines the fundamentals of fluid flow networks and the associated equations.

One Dimensional Flow NetworkFlow networks are incorporated into the Patran Thermal system to analyze the complex fluid flow system coupled with the heat transfer problem. The analysis is focused on average flow parameters, like mass flow rate, and pressure. Users requiring a detailed analysis of the flow field have to resort to CFD solvers.

Assumptions: 1. The flow is assumed to be incompressible single phase with no viscous heat effects.2. Physical and material properties are assumed constant over the element; however, they can vary

from element to element and can be temperature and/or time dependent.3. Flow is assumed to be steady-state or quasi-steady (steady state at each transient point).

The pressure drop in a fluid flowing in a duct from point I to J can be expressed as:


214

(7-18)

casting equation 1 in terms of mass flow rate.

(7-19)

(7-20)

linearizing the above equation.

(7-21)

or:

adding the head losses in flow with the loss coefficient, K.

(7-22)

Adding gravity and pump/turbine heads, the basic equation in matrix form can be written as:

(7-23)

P Static pressure in the duct

r Fluid mass density

f Moody friction factor

V Fluid mean velocity

D Hydraulic diameter of the flow passage

L Length of flow passage from node I to node J

PI PJ– ΔP ρ f L V2

2D--------------------------= =

PI Pj– ΔP ρ f L . m· 2

ρ2A2------------ . 1

2D-------= =

m· A2ρfLD

. PI - PJ=

m· A2ρfLD

. 1PI - PJ

------------------------ PI - PJ( )=

m· flow resistance * PI - PJ( )=

Flow resistance A2ρ

fLD----- K+

. || PI - PJ |

-------------------------------=

Kp[ ] P[ ] m·[ ] Heads[ ]+=


The flow resistance is a function of pressure; therefore, the problem is nonlinear and an iterative procedure is required for solution. The resistances are computed, assembled and the matrix equations are solved for nodal pressures.

Pressure conductivity matrix

Nodal static pressure

Fluid mass flow rate

Kp

P

m·

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisNumerical Analysis Techniques

216

Numerical Analysis TechniquesThis section describes some of the numerical methods used by QTRAN which may be of interest to the user. These methods include QTRAN’s predictor-corrector algorithm which is used for transient calculations, the Strongly Nonlinear Point Successive Over Relaxation (SNPSOR) point iterative solution algorithm which is used to solve the systems of nonlinear equations which are posed by implicit transient integration or by steady-state calculations, convergence acceleration schemes used by the SNPSOR algorithm, table interpolation schemes, the phase change algorithm used by QTRAN, and the finite element to resistor/capacitor translation algorithm.

QTRAN’s Predictor-Corrector AlgorithmQTRAN uses a predictor-corrector algorithm for transient problems. This algorithm uses a first order predictor with a second order corrector equation. Details are presented in the following sections.

QTRAN’s Predictor EquationQTRAN currently uses simple linear extrapolation in the time domain to predict the future value of a node’s temperature.

QTRAN’s Corrector EquationA family of one-step algorithms has been developed by Hughes (see Ref. 1. in Appendix A) and are claimed to be unconditionally stable for nonlinear type of problems.

QTRAN’s Modified Hughes Equation:

(7-24)

If the heat absorbed into the capacitor is treated as merely another heat flow, the left hand side of this equation can be moved to the right side and presented as:

(7-25)

where the value of T[t+β*dt] is taken as:

(7-26)

Furthermore, since t and T[i,(t)] may be assumed known and hence constant, using the corrector equation to integrate with respect to time may be seen to be equivalent to finding a value of T[i,(t+dt)] that zeros the following function:

(7-27)

T i t dt+( ),[ ] T i t( ),[ ]–dt

----------------------------------------------------------- SUM i = 1 all,[ ] Q i T, t β *dt+[ ][ ]{ }SUM i = 1 all,[ ] C i T ct β *dt+[ ],[ ]{ }-------------------------------------------------------------------------------------------------=

0 SUM i = 1 all,[ ] Q i T i t β *dt+( ),[ ],[ ]{ }=

T i t β*dt+( ),[ ] T i t,[ ] * 1 β–( ) T i t dt+( ),[ ] * β+=

0 SUM i = 1 all,[ ] Q i T t β *dt+[ ],[ ]{ }=

217Chapter 7: Thermal/Hydraulic TheoryNumerical Analysis Techniques

Optimum Explicit/Implicit Weighting FactorThe corrector algorithm of the previous section uses a weighting factor β which is used to determine the amount of “implicitness” that will be used for the formula. As per Ref. 2. in Appendix A, it is possible to choose this factor β such that fourth order or higher spatial accuracy can be achieved. For a 1-D problem, the method of choosing β is detailed as follows:

(7-28)

(7-29)

(7-30)

QTRAN currently offers this basic scheme as an optional adaptive weighting algorithm. A significant feature of QTRAN’s adaptive explicit/implicit weighting scheme is a lower cut-off value for the Fourier Modulus. If the Fourier Modulus is such that the current time step being used by QTRAN is less than 0.35 of the stable time step for a given node, that node is then integrated with β = 0.0 (totally explicit). This can speed up calculations very significantly.

T[i] the temperature at node “i” being integrated with respect to time

t current time at which T[i] is known

dt current integration time step

b Hughes integration algorithm explicit/implicit weighting factor

SUM[i=1,all] { Q[i,T] } total heat flow rate into node “i” from all other resistors and/or heat sources. Flow into the node is based on the temperatures at time = t + β * dt for resistor heat flows and temperature-dependent heat sources. Time-dependent heat sources are based simply on time = t + dt

C[i] ρ * V * Cp, where ρ is the density of the capacitor’s materials, V is the volume associated with the capacitor, and Cp is the capacitor’s specific heat. C[i] is evaluated at a temperature of T[i,(t+β*dt)]

dtstableΣCΣG--------=

R dtdtstable------------------=

R 0.35≤( )β 0=

β 3R 1–6R

----------------=

else

β MAX β 0.0,( )=

if


218

SNPSOR AlgorithmQTRAN uses a Strongly Nonlinear Point Successive Over Relaxation (SNPSOR) equation solving algorithm which is a diagonalized hybrid of Newton’s First Order Method and Newton’s Second Order Method when solving the systems of equations generated by a thermal network. Many nonlinear computer programs use a linear point iterative technique such as Gauss-Seidel coupled with successive over relaxation (SOR). Such an algorithm will frequently prove to be satisfactory. However, this algorithm can run into difficulties if the equation system is strongly nonlinear as is the case with “hot” thermal radiation problems where temperatures of 2000+ C may be encountered. When linear SOR algorithms encounter these problems, under relaxation is usually used to force convergence. However, this under relaxation will usually cause convergence to be unacceptably slow and will frequently adversely affect accuracy due to premature convergence.

An approach to the problem is to use a hybrid of Newton’s First Order Method and Newton’s Second Order Method. Newton’s First Order Method is essentially the same as using the first two terms of a Taylor series to estimate a function's zero, while Newton’s Second Order Method uses the first three terms to estimate the zero. Unfortunately, Newton’s Second Order Method requires three function evaluations per iteration if it is to be used. Furthermore, the Second Order Method is generally prohibitively costly and wasteful on conduction problems since conductive heat transfer is generally very close to being linear (First Order). It should also be noted that conduction dominated nodes are generally the most numerous in large thermal system networks. The approach used by QTRAN is a hybrid of the First Order and Second Order methods. Specifically, second derivatives are not calculated for conduction terms (i.e., conductive resistors are assumed to be linear within a given iteration and their contribution to the node’s First derivative is simply the sum of the resistor’s reciprocal values (conductances)). All other heat contributions to a node (e.g., capacitances, convective resistors, radiative resistors, mass flow resistors, and heat sources are assumed to be nonlinear and hence Second derivatives are calculated for these terms). Conductive resistor heat flows (which are generally the most numerous) are therefore calculated only once per iteration while other heat flows are calculated three times per iteration. The result is a rapid yet solidly convergent algorithm capable of both rapid computation for conduction problems and reliable convergence for the strongly nonlinear problems. For more information concerning Newton’s Second Order Method, see Ref. 3. in Appendix A.

While the hybrid Newton’s method works great for most problems, there are a few classes of problems that present pathological cases for failing any Newton’s method. These are the classic “S” shaped curves, and phase transition problems introduce exactly this type of “S” shape into the nodal heat flow rate curve. Fortunately, QTRAN can detect a phase transition and will shift to a bisection method for any node currently undergoing a phase transition. Bisection methods are relatively slow, but they are immune to the “S” shaped curves.

Convergence Acceleration SchemesQTRAN currently offers the user the option of selecting either a fixed or an adaptive over-relaxation scheme. In addition, a single over-relaxation parameter may be applied to the entire system of equations, or groups of relaxation parameters may be applied to groups of nodes dependent on the type of node and boundary conditions present, or individual relaxation parameters can be applied to each individual node. The following discussion applies to which-ever method of application is selected. Over-relaxation


schemes can speed the solution of elliptic problems by a factor of over 30 for many problems which are commonly encountered. Numerical experiments by the author with QTRAN’s adaptive relaxation algorithm (i.e., QTRAN estimates and continuously updates the relaxation parameter for the adaptive algorithm) have shown that the adaptive algorithm is over twice as fast as the optimal fixed over- relaxation algorithm for many transient problems. QTRAN’s adaptive relaxation algorithm has also proven to be quite successful in estimating the optimal relaxation parameter for steady- state problems. Special note should be made that over-relaxation (not under relaxation) can be used even with the “hot” thermal radiation problems. QTRAN’s SNPSOR algorithm does not (in general) force the user to resort to under-relaxation to gain a sufficient radius of convergence (with the possible exception of a few sublinear problems), whereas codes relying on linear SOR solvers frequently do.

QTRAN’s relaxation parameter estimation algorithm is based on the convergence rate R of the iterative solution, where R is calculated from:

(7-31)

where:

E[i-1] is the largest iterative delta (positive or negative) at the i-1'th iteration, and E[i] is the largest iterative delta (positive or negative) at the i'th iteration. In the limit as the iteration count i goes to infinity, the following formula (see eq. 3-83, 3-113, and 3-116 of Ref. 10. in Appendix A) may be used to estimate the relaxation parameter (assuming that the eigenvalues of the iteration matrix based on the current relaxation parameter have not yet become complex).

(7-32)

(7-33)

if

else

endif

RELAXmaximum is the maximum allowed relaxation parameter which can be set by the user. The theoretical maximum value is 2.0 and the code limits it to a value of 1.999. RELAXdamp is a damper on the rate of increase of the relaxation parameter. As with other applications of numerical analysis, this parameter does not have a theoretical basis, but numerical license allows for its interjection. This parameter tends to prevent the over-relaxation parameter from going beyond its optimum value.

R E i[ ]E i 1–[ ]--------------------=

AR RELAXcurrent 1–+( )

RELAXcurrent-------------------------------------------------------------=

B A A×R

--------------=

B 1.0≤( ) then RELAXnew RELAXcurrent=

C square root 1.0 B–( )=

D RELAXdamp2.0

1.0 C+------------------ RELAXcurrent–=

RELAXnew MIN RELAXnew RELAXmaximum,( )=


220

As stated previously, this algorithm works fairly well as long as i approaches infinity and the eigenvalues of the iteration matrix have not become complex. However, i never approaches infinity in practice and eigenvalues frequently become complex.

QTRAN approaches the i going to infinity problem by recognizing that what one is really after is to simply get a “good” estimate of the convergence rate R in some averaged sense. Specifically, R will frequently change values drastically in early iterations for a given time step or for a steady-state problem, and also after the relaxation parameter has been updated. What one wants to do is simply wait for the R value to stabilize before updating the estimate of R. This can be easily done by simply requiring that, for a finite number of iterations (say (3) iterations): (1) R be less than 1.0, (2) that the sign of the iterative delta’s are constant, and (3) that the value of RELAXcurrent has not been updated more recently than (4) iterations ago. If these three conditions are met, you can assume that the value of R[i] is approaching the asymptotic limit of R[infinity].

One minor complication to all of this is that the above algorithm for calculating RELAXnew is valid only as long as the eigenvalues of the iteration matrix do not become complex (this was alluded to earlier). For more information, see Ref. 9. in Appendix A. This brings up two major problems: (1) how does one know when the eigenvalues have gone complex, and (2) what to do then, since there is no theory for predicting the optimal relaxation parameter for a system with complex eigenvalues. The answer lies in purely empirical numerical engineering.

First, one observable fact is that the largest iterative delta’s E[i] have a tendency to oscillate in sign (+ and -) once the eigenvalues have gone complex (they can change sign at other times too, but the E[i] will frequently oscillate continuously with complex eigenvalues). Second, the cause of complex eigenvalues is usually that the value of RELAXcurrent is greater than RELAXoptimum for the equation system being solved (although you have no way of knowing how much greater). However, since an oscillating sign is an indication that RELAXcurrent is too large, QTRAN simply subtracts 0.01 from the value of RELAXcurrent each time that the sign of E[i-1]/E[i] changes. Eventually, the value of RELAXcurrent is reduced back to near RELAXoptimum. It is also worth knowing that from a practical consideration, RELAXcurrent needs only to be within about 0.002 of RELAXoptimum in order to be “exact”.

Finally, the value of RELAXcurrent is limited so that 0.01 <= RELAXcurrent <= 1.999.

Convergence Criteria and Error EstimationQTRAN does not base its convergence tests solely upon the iterative delta E[i] as do most other commercial codes. Instead, the test performed is based upon the E[i] value plus the historical convergence rate R. The formula for the convergence test is as follows:

Thermal/Hydraulic Input Deck (Ch. 8)

if

EPSI convergence criteria (QTRANs EPSISS or EPSIT values from=

Factor 1.0 1.0 max RELAX current 1.0, min 0.999 R,( )–( )–( )⁄=


else

end if

This basic formula can be derived from the equations presented in Convergence Acceleration Schemes, 218 along with a formula used to compute the sum of an infinite series.

Energy balance is often used as a convergence criteria but it is not used as a criteria in QTRAN even though it is printed out.

The energy balance in the QTRAN output is equal to the energy stored during a time step for transient problems and is zero for steady-state problems. If advection is present, then the energy balance will include the net energy carried into and out of the problem by the flowing fluid. When examining the energy balance for the system, it should be compared to the total energy flow in the system. If the system energy balance was 1100 when a zero was expected, it would be a large number; however, if it were compared to the total system energy which may be 1.1 x 1012, then the 1100 for the system energy balance becomes a small number.

System Energy BalanceThe System Energy Balance (QSB) reported by QOUT.DAT is defined as:

where, QNF is the combined net heat flows on all nodes including the boundary nodes and QS is the heat fluxes by applied Heating or macro functions. In cases where the heat flow is driven by boundary nodes, the system energy balance is simply the sum of all net heat flow rates on every node (including the boundary nodes) as reported in QOUT.DAT. The system energy balance may be higher than the control volume heat balance (heat entering the system minus heat leaving the system) since it also reflects the numerical tolerances on the calculated nodes. As such, it provides a more realistic picture of the uncertainty.

Table Interpolation SchemesQTRAN currently uses three distinct table interpolation schemes. These schemes are detailed in the following sections.

Linear InterpolationThis is the simplest table algorithm used by QTRAN and involves simple linear interpolation between table data points. Linear extrapolation is used when data is requested that lies outside of the X-Y data provided by the user.

E i[ ] Factor⋅ EPSI<( )then convergence has occurred

keep iteratin

QSB QNF QS–=


222

Hermite Polynomial InterpolationThis is a slightly more complex algorithm that resembles cubic spline interpolation in nature. The exact computational process involves the determination of the tabular function’s first derivatives at table interval boundaries. Using the first two derivative values and the function’s values at an interval’s boundaries, a cubic equation can be derived and used for interpolation within the interval. Since neighboring intervals also use first derivatives when calculating their cubic equations, it is seen that these tabular functions maintain continuity of slope (first derivatives) from interval to interval as well as maintaining continuity of value (linear interpolation maintains continuity of value from interval to interval, but not continuity of slope). Hermite Polynomial Interpolation can thus be used to provide a “smooth” tabular function if the user desires. Quadratic extrapolation is performed if the value lies outside of the tabular data.

Linear Computed Interval InterpolationQTRAN also offers Linear Computed Interval (LCI) interpolation for library material property evaluations. This linear table algorithm is an extraordinarily rapid linear interpolation scheme. A table property value is returned using only two multiplication and two addition operations. No interval search is required when LCI is used. Extrapolation is performed if the value lies outside of the tabular data.

Phase Change AlgorithmThe phase change algorithm used by QTRAN accurately models latent heats by adding an artificial temperature-dependence function into the capacitor’s specific heat curve. This has the effect of taking the latent heat and spreading it out over a very narrow (user specified) temperature region. This has the advantage of maintaining a capacitor’s energy content as a function of temperature and is done for numerical and coding convenience. It is similar in function to putting a “spike” into the specific heat curve to account for latent heat effects. However, unlike some other codes which use such “spikes”, QTRAN knows exactly where these “spikes” are in the temperature/enthalpy curve and there is no possibility that QTRAN can jump over them or miss a part of the spike (and hence erroneously fail to calculate the latent heat effects properly) as some other codes can. This technique has no restrictions whatsoever in terms of whether the user runs explicit, implicit, or some weighted average. Many codes add restrictions of this type for phase change models, but not QTRAN.

There is currently no coded limit to the number of phase regions that may be assigned to any capacitor in the system, nor is there any limit to the number of times that a given capacitor may transition from one phase to another. This also includes phase direction reversal prior to the complete melting, freezing, etc., of a node. There is also no limit to the number of nodes which may be simultaneously undergoing a phase transition.

Material properties may be varied in a near step-function manner at phase transition temperatures. While QTRAN does not perform convective calculations when a material has changed phase, it does assume that conduction continues to be a heat transfer mechanism. It is thus seen that QTRAN is able to continue with heat transfer calculations after a phase transition has occurred, subject to the assumption that an appropriate value for the thermal conductivity of the newphase region is used


.

Element to Resistor/Capacitor TranslationThe QTRAN thermal analysis package includes a routine in PATQ to translate finite element data to resistor/capacitor data for the following finite elements:

1. Linear 2-D Bar Elements (2-D Shells)2. Linear 3-D Bar Elements3. Linear Cartesian and Cylindrical Triangles (2-D)4. Linear Isoparametric Cartesian and Cylindrical Quadrilaterals (2-D)5. Linear Simplex Tetrahedrons (3-D)6. Linear Isoparametric Wedges (3-D)7. Linear Isoparametric Hexahedrons (3-D)8. Linear Isoparametric Triangular Shells (3-D)9. Linear Isoparametric Quadrilateral Shells (3-D)

PATQ program reads in finite element data for these element types and then constructs a mathematically exact resistor/capacitor representation. The network is NOT an approximation, but instead includes all finite element cross-derivative terms and any other increased accuracy that is inherent to a finite element discretization scheme using a lumped capacitance matrix. Such a translation program is highly desirable from the standpoint of being able to take advantage of the excellent finite element solids modeling packages that exist, and also from the standpoint of accuracy for skewed meshes (many finite difference schemes introduce an intolerable 0th order error for Laplacian difference operators when the mesh being used is skewed). It is also highly desirable from the standpoint that finite element formulations inherently allow for arbitrarily oriented anisotropic materials (e.g., composites), while many finite difference codes cannot perform analyses on anisotropic materials unless the material axes are by chance lined up with the mesh directions.

While the finite element based approach generates a mathematically exact resistor/capacitor representation, the resulting areas and lengths have no physical significance. The lumped capacitance network solver used in QTRAN is able to solve both finite difference and finite element based resistor/capacitor networks either separately or simultaneously. Finite difference based resistor/capacitors may be appended to the PATQ translated model by including them in the appropriate input files (i.e., CONDUCDAT, CAPDAT, etc.).

Note: A restriction to the phase change algorithm is that no capacitor is allowed to undergo more than one phase transition per time step.


224

Chapter 8: Thermal/Hydraulic Input DeckPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

8 Thermal/Hydraulic Input Deck

Overview 226

QTRAN Input Data File (QINDAT) 227

QTRAN Run Control Parameters and Node Number Declarations 229

Material Properties 263

Network Construction 276

Boundary Conditions 322

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisOverview

226

OverviewThis chapter is divided into five major sections which contain all of the information necessary for assembling the QTRAN input data file QINDAT. The functions of the five sections are detailed as follows:

• Overview--Input Data File• Run Control Parameters and Node Number Declarations • Material Properties and Phase Change Sets• Thermal Resistors and Capacitors• Boundary Conditions

227Chapter 8: Thermal/Hydraulic Input DeckQTRAN Input Data File (QINDAT)

QTRAN Input Data File (QINDAT)QTRAN Input Date File (QINDAT) is used as a command file by the Patran Thermal system. PATQ will supply bulk data files created from the PATRAN Plus model which are referenced by the QINDAT file with $INSERT commands. This greatly reduces the size of the QINDAT file, allowing a relatively small (usually about 60-70 significant data lines) command file for QTRAN. An example QINDAT file is provided with the Patran Thermal delivery and in QINDAT File Listing, 569. This file is heavily commented to make it easier to locate and understand the various input data file parameters that are normally placed in QINDAT. Section references in the QINDAT file refer to the input sections discussed in this chapter.

If QTRAN detects a data mismatch when reading the input data file, QTRAN will print out the image and number of the input data file line that was being read when the error was detected. This feature can greatly ease the debugging of an input data file. After encountering such an error, QTRAN will terminate program execution normally. QTRAN uses a free format input data file structure, so there is no concern about getting data in correct columns. Most data lines begin with keywords such as MDATA for material property data, CAP for capacitor data, etc. These keywords allow QTRAN to verify that what it is currently reading at a particular part of the data file is what it should be reading. Although the data is free format, the order in which the data is entered is very tightly controlled. All keywords specified in the QINDAT file must be input in the order encountered in this chapter. New keywords have been added for the enhancements in Patran Thermal. The QINDAT file can be obtained from the STARTUP directory with the GET_QTRAN command which will provide a sample input file indicating keyword order dependence. This is done for a number of reasons, including CPU efficiency. The most important reason why QTRAN input data is in fixed order format, however, is that it guarantees that each QTRAN input file (QINDAT) will look approximately the same without having important control parameters buried somewhere where a later user may not expect them to be found. With a fixed order format, it is easier to look for a particular parameter if it needs changing.

To insert comment lines anywhere in the input data file to document the input data, begin the line with an asterisk (*) or semicolon (;) in column 1. QTRAN will ignore any input data file line that begins with an asterisk or semicolon. QTRAN will also treat a semicolon as an end-of-line terminator, so that comments may be placed to the right of a semicolon. These comments can be valuable for documenting input data files for later reference.

QTRAN also offers the following commands that may be embedded in the input data file:

$RESTART filename next_nnn TIME OVRWFL

This command is used to restart a calculation. If this command is to be used, it must be the first noncomment line in a QINDAT file. This command causes QTRAN to read a QTRAN nodal results file cp10 as a restart file. Since QTRAN creates nodal results files with the name NRnnnNRF, the parameter next_nnn allows the nnn value to be specified for the next NRnnnNRF file that QTRAN will generate after being restarted. For example, a $RESTART command may look as follows: TIME is a value that will be used as initial time for the subsequent run rather than the time from the restart file. OVRWFL is an over write flag that allows specified initial temperatures to replace temperatures specified in the nodal results file.

$RESTART NR127.NRF 200 0.0 1

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisQTRAN Input Data File (QINDAT)

228

This command would cause QTRAN to read in NR127.NRF as a restart file. The next NRnnnNRF file that QTRAN generates will be named NR200.NRF. QTRAN reads the time and temperatures from the NRnnnNRF file. The time overrides TSTART and the temperatures override any TEMP data. If a TIME has been defined on the restart card, it overrides all other times and is used for TSTART to continue the run.

Defining the over write flag OVRWFL with something greater than zero will cause any temperatures specified in the TEMPDAT file to over write those specified in the restart file. This allows the user to change either initial of fixed temperatures from those specified by the restart conditions. The temperature over write is performed before the user restart function URSTRT is called. URSTRT is always the final restart operation.

$INSERT filename

Inserts the file cp10 into the input data file stream at this point. Nesting of $INSERT commands is permitted. The depth of file nesting is currently limited to ten deep. This command must begin in column one of any line in the input data file and there must be exactly one space between $INSERT and the file name.

$ECHO_ON or $ECHO_OFF

Enables or disables, respectively, the printing of input data file information into the output data file at the point where the $ECHO_ON or $ECHO_OFF command is encountered. These commands must begin in column 1 of any line in the input data file.

$STATUS

Sends the remainder of the input data file line to the status file. This can be used to keep track of QTRAN when large data files have been prepared, or to debug input data files.

$TRACE_ON or $TRACE_OFF

Commands QTRAN to send each line of the input data file to the status file as it is read. This is used primarily for debugging purposes.

Note: The RESTART capability only works with binary nodal result files. If the NRFORM flag has been set to 1 so as to generate ASCII nodal result files, the Patran utility, READER, must be used to convert the ASCII file to the binary equivalent prior to restarting QTRAN.

229Chapter 8: Thermal/Hydraulic Input DeckQTRAN Run Control Parameters and Node Number Declarations

QTRAN Run Control Parameters and Node Number DeclarationsThis section shows how to enter run control parameters and node numbers. The run control parameters do not specifically describe the thermal network, but are instead parameters which are used to control QTRAN’s behavior while solving the problem (e.g., start time, stop time, etc.). The parameters and options are listed below.

1. Printout Titles or Labels (p. 229)2. Input Data File Echoing (p. 229)3. Temperature Scale and Time Units Definitions (p. 230)4. Transient/Steady-State Run Option Selection (p. 231)5. Iteration Limit Controls (p. 234)6. Initial Time Step, Starting Time, Stopping Time, Time Step Multipliers, Convergence Rate

Criteria, Derivative Perturbation Parameter, Relaxation Parameters, Explicit/Implicit Ratio Control, Phase Change Temperature Band, Maximum Allowed Temperature Change per Iteration, Stefan-Boltzmann Constant, and Discontinuous Macrofunction Flag (p. 236)

7. Resistor/Capacitor/Heat Source Data Output (p. 247)8. Maximum Allowed Time Step Control (p. 253)9. Node Number Declarations (p. 254)

10. Print Control (p. 259)

Title DataThe title data are alphanumeric character strings (80 characters total) that are used as a text description (title) for the QTRAN output file. QTRAN will continue to read the input file and will continue to treat the data as title data until it encounters a dollar sign ($) in column 1.

Remember that if the character string begins with an asterisk (*) or semicolon (;) in column 1, QTRAN will treat the line as a comment line and will not include the line in the title data. This is consistent with the QTRAN convention of using an asterisk in column 1 to denote an input data file comment line.

Input Data Echo Option

Examples IECHO YIECHO N

IECHO(keyword) IECHO

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisQTRAN Run Control Parameters and Node Number Declarations

230

Temperature Scale and Time Units Definition

Examples ISCALE KICCALC RTLABEL SECONDS

Two temperature scales must be specified: one that will be used to present the output file data (ISCALE) and one that will be used for calculations (ICCALC). The temperature scales for ISCALE and ICCALC may be identical. In addition, a 10 character label for the simulation time units must be specified. This label (TLABEL) will be printed out with the results of all steady-state or transient runs. It is not used for anything else, and may be left blank.

Parameter DescriptionIECHO A parameter that specifies whether or not the input data is to be echoed into the

output file. The convention is as follows:N-- No Echo

Y-- EchoNotice: This option may be overridden by using the $ECHYO_ON or $ECHO_OFF commands. If the $ECHO commands are used, they must begin in column 1 of the input data file. There is no limit to the number of these $ECHO commands that may be used, and they may be used on any line of the input data file. These commands are especially useful for selectively suppressing the echo of the QINDAT file into the QOUTDAT.

ISCALE(keyword) ISCALEICCALC(keyword) ICCALCTLABEL(keyword) TLABEL


Transient/Steady-State Run Option Selection and Solver Selection

Hydraulic Network Option and Solver Selection

codeindent10HIOPT 0 2 1

or

HIOPT 1 2 10

or

HIOPT 2 2 4

Parameter DescriptionISCALE Alphabetic entry that corresponds to the output temperature scale to be used.

Regardless of the temperature scale being used to perform the calculations, the temperatures may be output in Celsius, Fahrenheit, Kelvin, or Rankine by entering the appropriate character for ISCALE. The convention is as follows:C-- Celsius

F-- Fahrenheit

K-- Kelvin

R-- RankineICCALC Alphabetic entry that corresponds to the temperature scale to be used to perform

all calculations (e.g., evaluation of temperature-dependent properties, evaluation of temperature dependent heat source/sink functions). The same temperature scale codes that are shown above for ISCALE are used for ICCALC.

Regardless of the scale specified for ICCALC, thermal radiation problems will automatically use correct absolute temperature scales when evaluating heat flows across thermal radiation resistors. Specifically, if ICCALC is specified as C, QTRAN will use K when evaluating the potentials of 6 * T4 at each end of the thermal radiation resistor and will use R if ICCALC was specified as F. Resistor material properties will still be evaluated using the scale specified by ICCALC.

TLABEL A 10 character entry that corresponds to the time units that are being used for the simulation (e.g., seconds, minutes, hours, fortnights, etc.). TLABEL is not used for any internal units conversions or anything else except that the 10 characters will be printed out after TIME values with the output data. TLABEL may be left blank.

HIPOT (keyword) HIOPT HSOL NTBHUP


232

Thermal Network Option and Solver Selection

codeindent10IOPT 5 0 0

or

IOPT 3 1 10

or

IOPT 3 2 1 8

or

IOPT 2 0 5

Parameter DescriptionHIOPT Run-option parameter selects one of the following three options:

0 - No flow network solution.

1 - Flow network solution only.

2 - Flow network coupled to the thermal solution.

All hydraulic solutions are quasi steady-state. If a transient run is being made, whenever the hydraulic solution is executed it will be a steady-state solution with the thermal conditions at the beginning of the hydraulic solution being used for the flow network evaluation.

HSOL Parameter that selects a solution option default SOL is 2 (Direct solver option). Currently, the only direct solution option SOL=2 is supported.

NTBHUP Usage is dependent on the thermal option selected. If a steady-state thermal solution is being executed, then the hydraulic network solution is recomputed every NTBHUP thermal iterations. For a transient thermal solution, the hydraulic solution is updated every NTBHUP time steps. The hydraulic solution is highly nonlinear and can require significant computer resources. By computing mass flow rates (hydraulic network solution) less often, the overall solution is speeded up without any significant loss of accuracy as long as the flow properties (viscosity, density, etc.) are not a strong function of temperature.

There is a strong coupling between the hydraulic and thermal solutions if buoyancy is included in the hydraulic solution. In this case the two solutions should be updated every iteration by setting NTBHUP to 1.

IOPT (keyword) IOPT SOL NITBUP MFLIPF


Parameter DescriptionIOPT Run-option parameter that selects one of the following six calculation sequences

(see Section 5.2.6 for an explanation of TSTART and TSTOP):A data check only. Input data will be read and echoed, but no calculations will be performed.

A transient run from initial conditions.

A transient run after initial-steady state calculations have been performed. All time dependent functions are calculated for the initial steady-state calculation using time = TSTART.

A steady-state run only. Time-dependent functions will be evaluated using time = TSTART.

A transient run from initial conditions, followed by a steady-state run from the final conditions. Time-dependent functions will be evaluated using time = TSTOP.

A steady-state run with the time-dependent functions for the steady-state run evaluated at time = TSTART, followed by a transient run, followed by a final steady- state run with the time-dependent functions evaluated at time = TSTOP.

SOL Parameter that chooses a thermal solution option.Standard SNPSOR solution algorithm, default.

Modified SNPSOR algorithm. The modified SNPSOR algorithm precomputes the values of the conductive resistors, and updates them every NITBUP iterations. By computing the conductive resistors less often, the solution is typically speeded up without any significant loss of accuracy as long as the thermal conductivity associated with the resistors is not rapidly changing.Direct solver using Choleskis method. The direct solver is coupled with the standard SNPSOR solution which is always executed after a direct solution to verify that all nonlinearities have been resolved. How many SNPSOR solutions are performed before a direct solution is repeated is controlled by NITBUP. The direct solver cannot be used with problems that include phase change. Also, the direct solver does not provide the advantages for transient cases compared to the gains that can be made with steady-state problems. Care should be exercised with transient cases that the time steps do not become so large that history effects will be lost even on those cases where boundary conditions and properties are constant. The direct solver is best suited to linear problems which have small bandwidths on the extremely stiff problem.


234

Iteration Limit Parameters

Examples IMAX 36

NITBUP The Number of Iterations Between Updates. What is updated is dependent on the solution option. If the standard solution is used (SOL = 0), then all nodes that may have been eliminated from the solution because they satisfied the second transient convergence criteria (EPSIT2) are included in the solution every NITBUP iteration. All nodes are evaluated after the solution has converged to guarantee that they are within the desired convergence tolerance. A value between IMIN / 2 and IMIN is recommended. The default value is 1000. This value has no effect for a standard solution, steady- state case. For the modified solution (SOL = 1), NITBUP is the frequency that the conductive resistors are update for both the steady-state and transient solutions. The best value for NITBUP is, of course, problem dependent. For many transient problems, it is sufficient to update the conductive resistors only once per time step, to specify a NITBUP value greater than the value of IMAX (IMAX is the maximum number of iterations allowed per time step). Note that no matter what value is given to NITBUP, QTRAN will automatically recompute the conductive resistor values at the beginning of each time step. For steady-state problems, experimentation with your specific problem is the rule of the day. Values of NITBUP between 10 and 100 are usually appropriate. The default NITBUP value is 0 (update every iteration). If the direct solver is used (SOL = 2), the NITBUP determines how many standard solutions (SNPSOR algorithm) are executed before another direct solution is performed. If material properties and boundary conditions are constant or are weak functions of temperature, the direct solution should be able to calculate the exact answer in one or with very few iterations. In these cases, the NITBUP value should be one. If there are strong nonlinearities involved, such as high temperature radiation boundary conditions, then it is best to do several SNPSOR solutions before doing another direct solution. This gives very sensitive parts of the problem a chance to relax using a much faster solution method while still using a direct solution to carry along the stiff portions of the problem that require many SNPSOR type iterations. For the highly nonlinear case, NITBUP values between 5 and 10 are appropriate.

MFLIPF The maximum number of over all solutions flip flops by the maximum temperature error before a bisection of all nodes is performed. The error must be less than three orders of magnitude of the allowable error about zero before it is considered a flip/flop condition. (Default value is 8.)

IMAX (keyword) IMAX

IMIN(keyword) IMINIMAXSS(keyword) IMAXSS IMAXHSISSDMP(keyword) ISSDMP


IMIN 9IMAXSS 2000 500ISSDMP 2000

Note: IMAX and IMIN values have an effect on both the accuracy and the run time of a transient solution. If IMAX and IMIN are very small, QTRAN will take generally smaller time steps than if IMAX and IMIN were large. The smaller time steps increase accuracy for problems involving hard transients at the expense of larger CPU times. Large values of IMAX and IMIN (e.g., “large” might be 100 and 50 for IMAX and IMIN, respectively) will generally result in smaller CPU time requirements, but certain details of hard transients may be blurred. If the problem involves only mild transients with no step function heat or temperature sources, larger values of IMAX and IMIN can usually be used with little danger. If the problem involves a very hard transient problem with many detailed perturbation events that are desired to be captured, use IMAX and IMIN values near the defaults of 30 and 8, respectively. The default values of 20 and 8 are considered “safe” or conservative values, while values of 100 and 50 (or larger) are considered more aggressive. Also, the IMAX value should be larger than IMIN by enough to permit convergence on the first iterations after the time step is increased. This is to prevent increasing the time step, but then decreasing it the next time step because the new time increment did not converge in IMAX iterations.


236

Control Parameters

Parameter DescriptionIMAX Maximum number of iterations allowed for any given time step during transient

runs. If the number of iterations exceeds IMAX without converging, the time step is decreased and convergence is attempted again. This will be repeated until convergence occurs with less than or equal to IMAX iterations. If zero is entered, QTRAN will supply a default value of 36.

IMIN Minimum desired number of iterations required to achieve convergence on any given time step for transient runs. If the number of iterations does not equal or exceed IMIN iterations before convergence, the time step size is increased for the next integration step. If zero is entered for IMIN, QTRAN will supply a default value of 9. IMIN should be less than or equal to IMAX.

IMAXSS Maximum number of iterations allowed for steady state calculations. If QTRAN does not achieve convergence within IMAXSS iterations, a message which states that convergence failed will be printed along with the current values of temperatures and heat fluxes. The program then terminates. If a zero is entered for IMAXSS, QTRAN will supply a default value of 2000.

IMAXHS Maximum number of iterations allowed for the steady state hydraulic calculations.ISSDMP Number of steady-state iterations between print dumps. When a steady-state run is

underway, QTRAN will print the results every ISSDMP iterations until the problem has converged. If zero is entered for ISSDMP, QTRAN will supply a default value of 2000.

DT(keyword) DT DTMINTSTART(keyword) TSTARTTSTOP(keyword) TSTOPTSFMIN(keyword) TSFMINTSFMAX(keyword) TSFMAXHYEPIS(keyword) HYEPIS HYHDEP HYMDEP HYPREPEPSISS(keyword) EPSISSEPSIT(keyword) EPSIT EPSIT2PERTUR(keyword) PERTURRELAXS(keyword) RELAXS IFSRLXRLXSAT(keyword) RLXSAM RLXSAD RLXSAURLXSRT(keyword) RLXSRM RLXSRD RLXSRURLXSHT(keyword) RLXSHM RLXSHD RLXSHURLXSCT(keyword) RLXSCM RLXSCD RLXSCURLXSST(keyword) RLXSSM RLXSSD RLXSSU


RELAXT(keyword) RELAXT IFTRLX

RLXTAT(keyword) RLXTAM RLXTAD RLXTAU

RLXTRT(keyword) RLXTRM RLXTRD RLXTRURLXTHT(keyword) RLXTHM RLXTHD RLXTHURLXTCT(keyword) RLXTCM RLXTCD RLXTCURLXTST(keyword) RLXTSM RLXTSD RLXTSUBETA(keyword) BETA BETMIN BETMAXDELMAX(keyword) DELMAX MINTMP MAXTMPPCBAND(keyword) PCBAND CPDELTGRAVTY(keyword) GRAVTY GO, GX, GY, GZSBC(keyword) SBCDCMF(keyword) DCMF


238

Examples

This section allows the initial time step (DT) to be defined, starting time (TSTART), stopping time (TSTOP), time step multipliers (TSFMIN and TSFMAX), steady-state and transient convergence rate criteria (EPSISS, EPSIT, and EPSIT2), the perturbation parameter used for Newton’s Second-Order Method (PERTUR), the relaxation parameters used for accelerating iteration convergence (RELAXS and RELAXT), the explicit/implicit ratio control variable (BETA), the maximum allowed temperature change per iteration (DELMAX), the phase change temperature band over which phase change energies are smeared (PCBAND), the specific heat curve integration step size (CPDELT), the Stefan-Boltzmann thermal radiation constant (SBC), and the Discontinuous Macrofunction Flag (DCMF).

DT 1.0D-04TSTART 0.0D+00TSTOP 1.0D+02TSFMIN 0.6D+00TSFMAX 2.0D+00HYEPIS 1.0D-04 1.0D-04 1.0D-04 1.0D-04EPSISS 1.0D-03EPSIT 1.0D-04 1.0D-07PERTUR 5.0D-02RELAXS 1.0D+00 1RLXSAT 1.99 0.80 1.0RLXSRT 1.99 0.92 1.0RLXSHT 1.999 0.94 1.0RLXSCT 1.999 0.95 1.0RLXSST 1.999 0.95 1.0RELAXT 1.0D+00 1RLXTAT 1.99 0.80 1.0RLXTRT 1.99 0.92 1.0RLXTHT 1.999 0.94 1.0RLXTCT 1.999 0.95 1.0RLXTST 1.999 0.95 1.0BETA 1.0D+00 0.0 1.0DELMAX 1.0D+03 -1.0D+30 1.0D+30PCBAND 1.0D+00 1000.0GRAVTY 9.81 0.0 0.0 9.81SBC 0.0D+00DCMF 1


Parameter DescriptionDT Initial time step used for transient calculations. DT will usually be adjusted during the

course of a transient run by QTRAN to take advantage of easily followed transients or to ensure accuracy during more difficult transients. If 0.0 is entered for DT, QTRAN will set DT to a nonzero but very small number (e.g., 1.0E-30). This is not recommended, but one should not be afraid to start with small time steps to give QTRAN the opportunity to follow a strong transient. For example, if the initial value of DT was set to 1.0D-4, it would take 16 calculation intervals to grow to 1.0 if the growth factor on the time step was 1.8 and the transient was mild enough to enable a time step of 1.0 units. If the initial value of DT was 1.0D-5 or 1.0D-6, it would only take 20 or 24 calculation intervals respectively to reach a DT value of 1.0.

The time step, DT, must be greater than 1.0E-10 * TSTOP. If a problem requires a time step smaller than this, it is probably best broken into multiple parts with restarts and corresponding adjustments to the IMIN and IMAX parameters to fit the regions of the problem that require the small and large time steps.

DTMIN The minimum allowed time step to be used for any calculation interval. Default is 1.0E-30. This value should be changed only as a last resort to get a difficult problem to run or when the user wants to force fixed time points regardless of errors that may be introduced because of lags in response to a given boundary condition.

TSTART Starting time used for transient runs. It is also used to evaluate time-dependent functions if initial steady-state calculations are being performed.

TSTOP Stop time for the program run. It is also used to evaluate time-dependent functions if a steady-state run is being performed after a transient run.

TSFMIN Time step multiplier that is used to decrease the time step size in case convergence has failed after more than IMAX (see Section 5.2.5) number of iterations. TSFMIN should normally be between 0.0 and 1.0. A recommended value is TSFMIN = 0.6. To run with a constant time step, simply set TSFMIN and TSFMAX (see following TSFMAX definition) to 1.0.


240

TSFMAX Time step multiplier that is used to increase the time step size in case convergence has occurred in less than IMIN (see Section 5.2.5) number of iterations. TSFMAX will not increase the time step size to a value greater than DTMAX (see Section 5.2.8.1). TSFMAX should normally have a value greater than 1.0. A suggested value is TSFMAX = 1.8, but a larger value may be used to allow a rapid increase in the time step, or use a smaller value to limit the perturbation to the system when time steps are increased. To run with a constant time step, simply set both TSFMIN (see previous TSFMIN definition) and TSFMAX to 1.0. The IMIN, IMAX, TSFMIN, and TFSMAX parameters all work together. Care should be taken so not to get into the condition that the DT increment is increased too much so that it will be decreased in the next time step. The product of TSFMIN and TSFMAX should be greater than one so that the problem will experience some increase in time step even if the time step is cut down in the next calculation increment.

HYEPIS Convergence criteria used by flow network solver. Static pressure, head differential across an element (pressure + gravity head + buoyancy head, etc.) and mass flow rates have to converge within HYEPIS before the flow solution is declared converged. HYEPIS is an absolute value and is used for all three parameters being checked. Care should be exercised in selecting this value to be sure that unit and the range of values are properly represented. The mass flow rate typically will be a much smaller value than the pressure and selecting a value consistent with the pressure will have no direct effect on the mass flow rate convergence criteria; however, if the convergence criteria was selected to operate on the mass flow rate, it would probably be too restrictive to enable convergence of the differential head.

HYHDEP Convergence criteria used by the flow network solver as an independent check on the head differential across an element.

HYMDEP Convergence criteria used by the flow network solver as an independent check on the mass flow rate at each hydraulic node.

HYPREP Convergence criteria used by the flow network solver as an independent check on the pressure at each hydraulic node.

EPSISS Steady-state convergence criteria that is used by QTRAN. This value is the estimated maximum error of the worst (least converged) node in the system, and is NOT an iterative delta as used by many codes. For example, to converge to the nearest 0.001 degrees, enter 0.001 for EPSISS and QTRAN will iterate until its estimate of the error of the worst node in the system is 0.001. Note that this convergence criteria is typically 10 to 100 times more severe than the criteria used in codes which rely on an iterating delta. For example, a value of 0.001 for EPSISS is frequently equivalent to a CINDA convergence criteria of at least 0.0001 to 0.00001. It should be especially noted that while EPSISS is directly related to the system error, the iterative delta convergence schemes (such as are used in CINDA) are truly only related to the convergence rate of a particular problem and not to the problem error. It is best to conservatively run with EPSISS = 0.0001 and obtain good results; however, with EPSISS = 0.1, reasonable answers on many problems may be obtained.


EPSIT Transient convergence criteria that is used by QTRAN (see EPSISS above). A recommended value is EPSIT = 0.0001. Experience seems to indicate that this is a very good value for most problems. Larger values of EPSIT do not make transient problems run as much faster as you might think, and smaller values seem to be overkill. The idea seems to be that you need to converge a system of equations to within the truncation error of the basic time integration scheme. Convergence beyond this truncation error is probably an exercise in fooling yourself. Conversely, if the problem fails to converge to within the truncation error of the integration scheme, the residual noise (error) in the solution seems to hinder the predictor equation to the point where the poorer predicted temperatures slow things down more than was gained by the looser convergence criteria.

EPSIT2 Optional modification to the transient convergence criteria. It can be thought of as a “cut-out” convergence criteria that can be used to speed convergence. Specifically, for transient problems, QTRAN will compare each nodes iterative error to EPSIT2. If that node’s last iterative error was less than EPSIT2, that node is cut out of the iteration sequence for the remainder of the time step. This allows QTRAN to iterate only on those nodes that are still changing significantly. Please note that the EPSIT2 value should be SIGNIFICANTLY smaller (at lease two or three orders of magnitude) than the EPSIT value. Remember, a large number of very small changes can add up over a period of time, so make sure that EPSIT2 is significantly smaller than EPSIT. The default value for EPSIT2 is 0.0 (this gives the standard QTRAN SNPSOR algorithm).

PERTUR Perturbation parameter that is used to evaluate derivatives for Newton’s Second-Order Method used by QTRAN. PERTUR corresponds directly to the traditional dx that is used in classical central difference schemes to evaluate derivatives. In this case, PERTUR is used to evaluate both 1st-Order and 2nd-Order derivatives. If the value of PERTUR is grossly too large, the error in the evaluation of the derivatives may cause convergence to be slow. Conversely, if the value of PERTUR is too small (especially for radiation calculations), the perturbations caused by PERTUR may be so small that they are swallowed by round-off error, causing the derivatives to be evaluated as zero and subsequent nonconvergence. If this problem occurs, you should experiment with different PERTUR values. A recommended PERTUR value is 0.01. Smaller values may be used for mass flow and convection problems, while “hot” radiation problems of several thousand degrees Kelvin may require values of 1.0 or greater. A value that is too large or too small may also cause steady-state convergence to fail. In general, problems that are fairly linear in the temperature variable (i.e., temperature-independent material properties and convection correlations with no radiative nodes) are relatively insensitive to larger values of the PERTUR parameter and will tolerate small PERTUR values. Problems that are strongly nonlinear in the temperature variable (e.g., hot radiation problems) are generally more sensitive to the size of the PERTUR variable and may not tolerate extremely small PERTUR values due to the round-off phenomenon. Note that despite all of the above warnings, PERTUR values of 0.1 to 0.01 rarely fail in practice.


242

RELAXS Steady-state relaxation parameter. RELAXS is used only for steady-state calculations, and its sole function is to speed convergence (i.e., to reduce the number of iterations required for convergence to a certain accuracy). The absolute value of RELAXS should be between, but not including, 0.0 and 2.0. Positive values invoke QTRAN’s adaptive relaxation algorithm, whereas negative values of RELAXS inhibit the adaptive algorithm. Normally, the value entered for RELAXS should be +1.0, thus allowing QTRAN’s adaptive relaxation algorithm to function. Values with magnitudes greater than 2.0 will cause the algorithm to diverge, while values with magnitudes less than 1.0 may increase the radius of convergence at the expense of the convergence rate. If the adaptive algorithm is enabled, QTRAN begins iterations with your RELAXS value as the initial guess of the relaxation parameter. It is better to guess low at this value because QTRAN’s adaptive algorithm will converge more quickly to the optimal value from below than from above. Furthermore, if the initial guess at the temperature distribution is very poor (and this is typically the case), a value of RELAXS = +1.0 will allow QTRAN to smooth the system slightly before using over relaxation.This smoothing is sometimes necessary for strongly nonlinear systems in order to achieve convergence. The total amount of work required for a steady-state solution is extremely dependent on this parameter. It is not unusual for an optimally over-relaxed problem to run in 1/30th the time of a nonreligious (RELAXS = -1.0) problem. QTRAN’s adaptive algorithm takes the guesswork out of what this value should be.


IFSRLX A flag that indicates how the relaxation parameters are to be applied to the system of equations being solved. Three options are available. If the IFSRLX=0 option is used, then the relaxation parameter applies to all nodes in the system equally. All nodes are searched each time step, the maximum error is determined, and the relaxation and convergence factors are determined based on the maximum error of the system regardless as to what type of boundary condition is applied to the node. The IFSRLX=1 option applies relaxation and convergence factors based on the type of node and boundary condition that is present at the node. A hierarchy is established as to the type of boundary condition present at the node. This order is from advection, radiation, convection down to conduction. If any node has advection applied, then the advection relaxation parameters will apply even if there is also radiation and or convection at the same node. Advection can destroy the diagonal dominance of the matrix and as such it may be desirable to set the relaxation parameters to force under relaxation for these nodes so that the circle of converge of the problem can be increased. Similarly, the radiation nodes will probably be the most likely to exhibit large fluctuations, therefore, it is not desirable for the relaxation parameters to increase as rapidly for these nodes as for the nodes that exhibit straight conduction. This option, which allows for these groupings, is the recommended option. The third option, IFSRLX=2, is to have the relaxation parameters calculated on a node-by-node basis. This option will usually give the tightest converged solution. The convergence factor is also calculated individually for each node and a node that may not have the largest error could be changing slower than the node that had the greatest error. Thus, the convergence factor could be much larger. The system error is the product of the iteration error and the convergence factor. As a result, the system error determined on a node-by-node basis could be greater than that determined for the system or group methods. The error criteria can probably be relaxed, if the node-by-node relaxation option is used compared to the group or system option.

RLXSAM Maximum steady-state relaxation parameter that is to be used with all advection nodes. Values input must be greater than 1.0 and less than 2.0

Notice: The relaxation variables discussed below and their association to the input file, Keyword, is shown in the Control Parameters, 236.

RLXSAD Advection steady-state relaxation damping factor. Based on several conditions, the relaxation parameters are recalculated. The new relaxation parameters are compared to the old values and the actual amount of change is reduced according to the damping multiplier. For example, suppose that the new relaxation factor was calculated to be 1.860 and the old one was 1.0. If the damping factor was 0.95, then the actual relaxation factor defined at this calculation step would be 1.817. In the early stages of a solution, the iterative delta is probably the largest. This may be the time that it is not desirable to over relax, particularly with advection. By using small damping factors, the degree of over relaxation is reduced but will be allowed to approach its optimum value as the solution continues and is usually when the solution is better behaved. In problems where advection is causing convergence problems, it may be desirable to reduce this parameter to 0.05.


244

RLXSAU Steady-state multiplier used with all advection nodes. All multipliers are applied by type of node and boundary conditions regardless of the application option that is specified. This parameter is used to implement under relaxation. The relaxation parameter will always be calculated between the values of 1.0 and 2.0, but when they are applied to the iterative delta, the RLXSAU multiplier is included. Thus, if the relaxation parameter was 1.8 and the multiplier 0.3, the effective relaxation parameter would be 0.54 or an under relaxed state. Under-relaxation or multipliers less than 1.0 should only be used in those cases where the node-by-node application of the relaxations parameters has failed to yield convergence. Note that the relaxation parameters specified in the output or status file reflect the multipliers and are only applied to the actual temperature change.

RLXSRM Maximum steady-state radiation relaxation value allowed.RLXSRD Steady-state radiation relaxation damping factor.RLXSRU Steady-state radiation relaxation factor multiplier.RLXSHM Maximum steady-state convection relaxation value allowed.RLXSHD Steady-state convection relaxation damping factor.RLXSHU Steady-state convection relaxation factor multiplier.RLXSCM Maximum steady-state conduction relaxation value allowed.RLXSCD Steady-state conduction relaxation damping factor.RLXSCU Steady-state conduction relaxation factor multiplier.RLXSSM Maximum steady-state system relaxation value allowed.RLXSSD Steady-state system relaxation damping factor.RLXSSU Steady-state system relaxation factor multiplier.RELAXT Transient solution relaxation parameter which is similar to the previous RELAXS

parameter. RELAXT is used only for transient calculations. QTRAN’s adaptive relaxation algorithm may be selected in the same manner as RELAXS, and for transient calculations may easily half the solution time when compared to a fixed relaxation scheme. Whenever the time step changes in magnitude, or after a direct solution, the relaxation parameter is reset to 1.0. All the associated relaxation parameters that were discussed for the steady-state case can be applied independently to the transient part of the solution. These parameters are listed below.

IFTRLX A flag that indicates how the relaxation parameters are to be applied to the system of equations being solved. Three options are available. If the IFTRLX=0 option is used, then the relaxation parameter applies to all nodes in the system equally. The IFTRLX=1 option applies relaxation and convergence factors based on the type of node and boundary condition that is present at the node. The third option, IFTRLX=2, is to have the relaxation parameters calculated on a node-by-node basis.

RLXTAM Maximum transient relaxation parameter that is to be used with all advection nodes.RLXTAD Advection transient relaxation damping factor.RLXTAU Transient multiplier used with all advection nodes.


RLXTRM Maximum transient radiation relaxation value allowed.RLXTRD Transient radiation relaxation damping factor.RLXTRU Transient radiation relaxation factor multiplier.RLXTHM Maximum transient convection relaxation value allowed.RLXTHD Transient convection relaxation damping factor.RLXTHU Transient convection relaxation factor multiplier.RLXTCM Maximum transient conduction relaxation value allowed.RLXTCD Transient conduction relaxation damping factor.RLXTCU Transient conduction relaxation factor multiplier.RLXTSM Maximum transient system relaxation value allowed.RLXTSD Transient system relaxation damping factor.RL XTSU Transient system relaxation factor multiplier.BETA Explicit/implicit ratio variable that is used to control the amount of explicitness and

implicitness of transient integration solutions. If β is negative, QTRAN’s optimizing algorithm is disabled and the value that you entered for β will be used for all nodes which have capacitors assigned to them (zero capacitance nodes are not integrated, but are instead computed directly). A value of β = 0.0 yields a fully-explicit solution (forward Euler method), β = -1.0 yields a fully-implicit solution (backward Euler method), and anything in between yields a weighted average. If the recommended value β = +1.0 is used (or any positive number significantly greater than zero), QTRAN computes its own optimized value for β on a node-by-node basis. The optimized value also means that some nodes are at times run completely explicitly, and this mixture of explicit/implicit integration has yielded speed increases of 3 to 4 on some test problems. Also note that if a node is undergoing a phase change, the node is automatically integrated fully implicitly for the duration of the phase change activity of that node. Note that except for performing comparison benchmark tests of the algorithms, always run with β = 1.0. No case has yet been found where this has proven to be a problem. There seems to be no motivation to run with any other β value except possibly to verify that QTRAN’s implicit algorithm actually works. Solution accuracy and run times are normally fairly independent of the β value chosen, as long as a b value is chosen by you or by QTRAN that results in a stable solution.

BETMIN Minimum allowable value of the β parameter. This gives more control over the degree of explicitness or implicitness desired. Explicit solutions are stable if linear properties are present, but even for this case, the transient may exhibit oscillations. If the material properties are highly nonlinear, limit the explicit calculations. By specifying a BETMIN, the nodes that are run explicitly can be limited while allowing the explicit/implicit weighting function to do its optimization.

BETMAX Maximum allowable value of the β parameter.


246

DELMAX Maximum allowed temperature change per iteration. If an iterative temperature change is calculated with a larger magnitude than DELMAX, the sign is kept but the magnitude is limited to DELMAX. If 0.0 is entered for DELMAX, a default value of DELMAX = 1000.0 will be used. DELMAX is used as a last-ditch effort to help force convergence to occur for the extremely rare problems for which QTRAN’s SNPSOR algorithm may otherwise fail. Normally, use the default value for DELMAX of 1000.0 by entering a 0.0 for DELMAX.

MINTMP Minimum allowed temperature of a problem. In some cases, especially after strong perturbation in boundary conditions, explicit calculations or initial prediction can extrapolate the solution to unreasonable values. By specifying minimum and maximum values for the solution, any node whose value is extended beyond the limits of the solution will be declared to be solved by fully implicit means and the new guess in node temperature will be MINTMP. Care must be exercised that the value of MINTMP is not within the limits that can be expected for normal numerical oscillation of the solution.

MAXTMP Maximum allowed temperature of a solution.PCBAND Temperature interval over which phase changes will be smeared. If set to 0.0 or less, a

value of 1.0 degrees will be used. The smaller the value of PCBAND that is used, the more accurate the answer will be at the expense of more computation. Phase change begins at the phase change temperature minus PCBAND and is completed at the phase change temperature plus PCBAND. Phase change begins at the phase change temperature minus PCBAND and is completed at the phase change temperature plus the PCBAND.

CPDELT Temperature integration step size used to evaluate an integrated average of the specific heat across a time step. If the specific heat is highly variable (e.g., a spike or other discontinuity exists in the Cp vs. temperature curve), set CPDELT to a fraction of the width of the spike. The calculated temperature change during a time step is divided by CPDELT to determine the number of points that the specific heat is to be evaluated. The specific heat is the average of all evaluations at each temperature point determined by CPDELT and is evaluated independently for each node, at each iteration for each time step. If CPDELT is greater than the temperature change, two points - the beginning and resultant temperature - will be used each time step to determine the specific heat. This is the default if CPDELT is left blank.

GRAVTY Gravitational constant used with turbine, pump head calculation and for required internal units conversions. The default value is dependent on the ICCALC option. If Metric or an English temperature is specified, 9.80665 meters / second / second or 32.1741 feet / second /second respectively is used.

GX Positive value indicates that gravity is working against a positive x direction. Default is 0.0.

GY Positive value indicates that gravity is working against a positive y direction. Default is 0.0.

GZ Positive value indicates that gravity is working against a positive z direction. Default is 0.0.


Auxiliary Print Options

Resistor Heat Flow Print Option

ExampleIRQFLO 1 1 1 1 1 1 1 1 1

SBC Stefan-Boltzmann thermal radiation constant. If SBC is entered as zero, QTRAN will set SBC to 5.6696D-08 W / (m2-K4) if ICCALC is in degrees K or C, and to 0.1712D-08 Btu/(hr-ft2-R4) if ICCALC is in degrees R or F.

DCMF Discontinuous Macrofunction Flag. If set to 0, there is no effect. If set to 1, DCMF alerts QTRAN’s transient integration algorithm that one or more macrofunctions may be severely discontinuous in nature. QTRAN then uses a β value of 1.0 for nodes with macrofunctions assigned to them. Using β = 1.0 allows the transient integration algorithm to notice sharp discontinuities in dT/dt that occur in the middle or end of a time step and then forces QTRAN to use smaller time steps in the neighborhood of such a discontinuity.

IRQFLO (keyword) RQFLO(1...9)


248

Nodal Results File Format Option

ExampleNRFORM 0

Parameter DescriptionIRQFLO Allows print/no print options to be selected for resistor, capacitor, and heat source

macrofunction data in the system. Setting IRQFLO(i) to 1 causes QTRAN to print data for the i'th entry in the following list, while any other value causes no data to be printed for that item. The data is printed at the end of a steady state run, or at each print interval for a transient run. This data includes such things as resistor heat flow, conductance, capacitance, material property data, and others. The list of IDMNRF(i) items is as follows:

IRQFLO(1) --Conduction Resistors

IRQFLO(2) -- Convective Resistors

IRQFLO(3)--Gray Radiative Resistors

IRQFLO(4) -- Wavelength-Dependent Resistors

IRQFLO(5) -- Advective Resistors

IRQFLO(6) -- Capacitors

IRQFLO(7) -- Heat Source Macrofunctions

IRQFLO(8) -- Hydraulic Advection Resistors

IRQFLO(9) -- Hydraulic Capacitors

Since there can be a large amount of data (especially conductive and radiative resistor data), you normally should be selective about the volume of information that is requested.

NRFORM (keyword) NRFORM


Nodal Results File Print Options

ExampleIDMNRF 1 0 0 0 0 0 0 0 1 1 0 0 1 0 1 1 1 1

Parameter DescriptionNRFORM Format of the nodal results file.

0. Binary nodal results files.

1. ASCII nodal results files.

The flag that tells QTRAN whether to output the nodal results file is ASCII or binary. NRFORM=0 will give a binary file (default). NRFORM=1 will generate a text file.

IDMNRF (keyword) DMNRF(1...18)


250

Parameter DescriptionIDMNRF Allows which items are to be put in the nodal results files. The first eight items plus

fifteenth through the nineteenth into the nodal results files with the prefix designation NRnnn, ninth and tenth go to NPnnn type files, and the eleventh through the fourteenth go into NHnnn type files. The list of IDMNRF(i) items is as follows:

0. Denotes that parameter is not written to the results file.

1. Denotes that parameter is written to the results file.

IDMNRF(1)--Temperatures

IDMNRF(2)--Net nodal heat flow

IDMNRF(3)--Explicit stable time step

IDMNRF(4)--QMACRO function heat input

IDMNRF(5)--QBASE heat input to each node

IDMNRF(6)--Total heat input to each node

IDMNRF(7)--Temperature error

IDMNRF(8)--Average convective heat transfer coefficient

IDMNRF(9)--Nodal pressure from hydraulic solution

IDMNRF(10)--Net mass flow rate from hydraulic solution

IDMNRF(11)--Mass flow rate in hydraulic element

IDMNRF(12)--Differential head in hydraulic element

IDMNRF(13)--Fluid velocity in hydraulic element

IDMNRF(14)--Volumetric flow rate in hydraulic element

IDMNRF(15)--Applied Heat Flux

IDMNRF(16)--Convective Heat Flux - Note that the heat flux summary for plotting is only associated with the application region. The area is unknown or may not exist for the coupled node.


IDMNRF(17)--Radiate Heat Flux - As with convection the radiation for plotting is only associated with the application region. If one is working with an enclosure, specify a surface emissivity of 0.9999 to represent black bodies to get an accurate measure of what is happeniIDMNRF(15)--Applied Heat Fluxng at the surface.

IDMNRF(18)--Net Total Heat Flux

IDMNRF(19)--Surface Recession

IDMNRF(20)--Surface Recession Rate


252

Flag that determines what record gets put in the nodal results file. IDNMRF=0 implies that the record will not go to the nrf file while IDMNRF=1 implies that the record will be put out in the nodal results file. If all items are flagged, the following columns would represent the data in the different nodal results files:

NRnnn Column 1 Temperature

Column 2 Net nodal heat flow

Column 3 Explicit stable time step

Column 4 QMACRO function heat input

Column 5 Qbase heat input into each node

Column 6 Total heat input into each node

Column 7 Temperature error

Column 8 Average convection heat transfer coefficient

Column 9 Applied heat flux

Column 10 Convective heat flux

Column 11 Radiate heat flux

Column 12 Net total heat flux

Column 13 Surface Recession

Column 14 Surface Recession RateNPnnn Column 1 Pressure at a given node from the hydraulic solution

Column 2 Mass flow rate at a given node from hydraulic solutionNHnnn Column 1 Mass flow rate in hydraulic element

Column 2 Differential head in hydraulic element

Column 3 Fluid velocity in hydraulic element

Column 4 Volume flow rate in hydraulic element


Maximum Time Step ControlThis section allows maximum time step data to be entered. Initial Maximum Time Step, 253 is used to enter the initial maximum allowed time step and Maximum Allowable Time Step Adjustments, 253 may be used to alter this value at user-selected times during a transient run.

Initial Maximum Time Step

ExampleDTMAX 1.0D+01 100.0

This example sets the maximum allowed time step to 10.0 for the thermal solution and 100.0 seconds for the hydraulic solution.

Maximum Allowable Time Step Adjustments

ExampleDTMAXA 7.0D+00 5 200

This sets the new DTMAX value to 7.0 at time = 5.0 for the thermal solution and while setting a new DTMAXH value of 200 for the hydraulic solution.

QTRAN allows the value of the maximum allowable time step (DTMAX) to be adjusted at arbitrary times in a transient simulation if desired. The values of DTMAXA(I,1), DTMAXA(I,2), and DTMAXA(I,3) are entered as an ordered group, where DTMAXA(I,1), DTMAXA(I,2), and DTMAXA(I,3) are defined as follows

DTMAX (keyword) DTMAX DTMAXH

Parameter DescriptionDTMAX Initial maximum value of the time step allowable for transient calculations, regardless of

the number of iterations given for the IMIN parameter (see Iteration Limit Parameters, 234). The time step used for integration will not exceed the value of DTMAX that is set. However, the value of DTMAX can be adjusted (see Maximum Allowable Time Step Adjustments, 253) during a transient run.

DTMAXH Initial maximum value of the time step allowable for hydraulic calculations. The maximum time allowed to lapse before the hydraulic solution is updated. This is used in conjunction with the NTBHUP parameter to control when new hydraulic calculations are performed. The time and counter are both indexed at the time a new hydraulic solution is calculated with the next update determined by whichever parameter is tripped next.

DTMAXA (keyword) DTMAXA(I,1) DTMAXA(I,2) DTMAXA(I,3)


254

:

Node DefinitionsQTRAN requires that each node referenced in Network Construction, 276 and Boundary Conditions, 322 must be declared by assigning it a node number in this section. This section explains how to enter data to declare node numbers for the thermal network. Node numbers need not be consecutive, but they must be greater than zero. If a reference to a node is made in these two sections that was not declared, QTRAN will print an error message in the output data file that identifies the undeclared node number and will then terminate execution.

Node numbers are declared by entering a node number declaration block. Each block defines a starting node number, an ending node number, and a node number increment within the block (exactly like a FORTRAN do-loop). As many blocks may be entered as are needed to define the nodes. When no more blocks are to be entered, simply enter a dollar sign ($) in column 1 of the input data file. The block variables are defined as follows:

Hydraulic Node Number Declarations

Two groups of node numbers are declared-hydraulic and thermal. The hydraulic nodes have all the same properties and attributes of the thermal nodes, but have additional properties. Hydraulic nodes have pressure, mass flow rate, and other properties associated with them that are necessary to calculate fluid flow through a set of fluid elements that define various flow characteristics. As a result of the PATQ translation (menu pick 2), those declarations are placed in the PNODEDAT file.

Parameter DescriptionDTMAXA(I,1) I'th new value of DTMAX that you want to define.DTMAXA(I,2) I'th time at which the value of DTMAX is to be reset to the new value specified

by DTMAXA(I,1). As many pairs of DTMAXA data as needed may be entered.

Values defined for DTMAXA groups will force QTRAN to end a time step and to begin a new time step at the DTMAXA(I,2) values.

DTMAXA(I,3) I'th new value of DTMAXH that is to be defined.

When all DTMAXA data is entered, enter a dollar sign ($) in column 1 of the input data file. After all of the DTMAXA data is entered, enter the dollar sign ($) in column 1 and proceed to Node Definitions, 254.

Note: This data is normally generated with PATQ menu pick 2.

DEFPND (keyword) DEFPND(1...3)

Note: All hydraulic nodes must be defined before the thermal nodes are defined. It is not necessary that the node numbers be less than the thermal node number, but they must be defined first in this section of the QTRAN input.


ExampleDEFPND 10 100 1

This example defines nodes 10 through 100 in increments of 1.

Thermal Node Number Declarations

As a result of the PATQ translation (menu pick 2), these declarations are placed in the NODEDAT file or the VFNODEDAT file for VIEW FACTOR nodes (menu pick 3).

ExampleDEFNOD 110 410 2

This example defines nodes 110 through 410 in increments of 2.

Parameter DescriptionDEFPND(1) Starting node number of the block.DEFPND(2) Ending node number of the block. This value should be consistent with the value of

DEFPND(1) and DEFPND(3) (again, exactly like a FORTRAN do-loop) or it may not be assigned. For example, if DEFPND(1)=1, DEFPND(2)=4, and DEFPND(3)=2, the assigned node numbers will be 1 and 3. While this is probably not what the user would have intended, this will be the result. A correct set of values, for example, might be DEFPND(1)=20, DEFPND(2)=30, and DEFPND(3)=2. This would declare node numbers 20, 22, 24, 26, 28, and 30.

DEFAULT OPTION: If DEFPND(2) is entered as zero (0), QTRAN will set DEFPND(2) to the value of DEFPND(1).

DEFPND(3) Node number increment of the block. If DEFPND(3) is given as 0, a value of 1 will be assumed. Negative values of DEFPND(3) are allowed.

To declare single nodes, simply use the same value of DEFPND(2) that is used for DEFPND(1) (the single node number being declared) with a value of 0, 1, or blank for DEFPND(3). Alternatively, using the default options for DEFPND(2) and DEFPND(3), simply enter the node number being declared for DEFPND(1) and leave DEFPND(2) and DEFPND(3) as blank or zero.

Node number declarations are a user convenience. They allow modification of a given network by adding or subtracting nodes at will without having to completely renumber all of the nodes in the model. They also allow node numbers to be assigned to different regions of the model for clarity (e.g., nodes 100-199 to region 1, nodes 200-299 to region 2, nodes 1000-9999 to radiosity nodes, etc.), or any other scheme that may be conceived.

DEFNOD (keyword) DEFNOD(1...3)


256

Note: Although node numbers may be entered in any order and “holes” may be left in the node number scheme, very large problems will have a CPU time penalty for this during the initialization phase only (not during the analysis phase). For very large problems it is cheaper to have the nodes numbered 1 through N sequentially. The reason for this is that every node number that is declared here is reassigned an internal node number reference by QTRAN. This is done for storage efficiency as well as CPU efficiency. Every reference to one of the node numbers by a resistor, heat source, etc., involves a “look up” operation by QTRAN (during the initialization phase only) to see what the internal node number is for the node number referenced by the resistor, heat source, etc. This “look up” operation first checks to see if, by chance, the internal node number is the same as the nodal number. If it is, no search is necessary. If it is not, QTRAN has to look through the list of node number references until it finds the nodal number. If thousands of nodes are involved, this can take some time (but again, this is done only during the initialization phase and NOT during the calculations).


Temperature Coupling Nodes

Temperature coupling is a means of equivalencing boundary, regions or independent nodes without them having to be congruent and still retain their original identity. This can be used to perform cyclic redundancy calculations, couple surfaces together which have different material properties where different mesh densities are desired or couple different types of networks together. For example an axisymmetric region can be coupled to a three dimensional region without making any geometric assumption regarding the transition between the regions. The only assumption is that the temperatures would be the same.

For example, where it was desired to have a transition between the axisymmetric and three-dimensional regions, the region where the circumferential temperature gradient vanished would be the coupling region. If regions between different materials were coupled the surface with the lowest conductivity would be the application node and the high conductivity region would be the coupled or node the application node would be coupled to. Here the assumption would be that the high conductivity material would dominate the temperature gradient along the common interface.

Parameter DescriptionDEFNOD(1) Starting node number of the block.DEFNOD(2) Ending node number of the block. This value should be consistent with the value of

DEFNOD(1) and DEFNOD(3) (again, exactly like a FORTRAN do-loop) or it may not be assigned. For example, if DEFNOD(1)=1, DEFNOD(2)=4, and DEFNOD(3)=2, the assigned node numbers will be 1 and 3. While this is probably not what the user would have intended, this will be the result. A correct set of values, for example, might be DEFNOD(1)=20, DEFNOD(2)=30, and DEFNOD(3)=2. This would declare node numbers 20, 22, 24, 26, 28, and 30.

DEFAULT OPTION: If DEFNOD(2) is entered as zero (0), QTRAN will set DEFNOD(2) to the value of DEFNOD(1).

DEFNOD(3) Node number increment of the block. If DEFNOD(3) is given as 0, a value of 1 will be assumed. Negative values of DEFNOD(3) are allowed.

To declare single nodes, simply use the same value of DEFNOD(2) that you use for DEFNOD(1) (the single node number being declared) with a value of 0, 1, or blank for DEFNOD(3). Alternatively, using the default options for DEFNOD(2) and DEFNOD(3), simply enter the node number being declared for DEFNOD(1) and leave DEFNOD(2) and DEFNOD(3) as blank or zero. Node number declarations are a user convenience. They allow modification of a given network by adding or subtracting nodes at will without having to completely renumber all of the nodes in the model. They also allow node numbers to be assigned to different regions of the model for clarity (e.g., nodes 100-199 to region 1, nodes 200-299 to region 2, nodes 1000-9999 to radiosity nodes, etc.), or any other scheme that may be conceived.

TCOUPL (keyword) TCPLND TCPLCN


258

Internally what happens is all capacitors and resistor that have a temperature coupling node are replaced by the coupling node. If a resistor has the same node ID for both identifiers it is removed from the calculation sequence. At each output request the temperature coupling application node temperature is replaced by the temperature coupling node’s temperature, thus the model retains its original geometric characteristics for all post processing.

ExampleTCOUPL 110 410

In this example all internal references to node 110 are replaced with node 410 and all temperature output for 110 will be assigned the temperature value of node 410.

Node Location Declarations

As a result of the PATQ translation (menu pick 2) these declarations are placed in the NODXYZDAT file.

ExampleNODXYZ 1 1.01122D+0 3.33121D-1 2.22222D+1

This example shows that node 1 has an x, y, z coordinate of 1.01122, 0.333121, and 22.2222 respectively.

Parameter DescriptionTCPLND Temperature coupled node. The node that will be replaced in the solution by the

temperature coupling node.TCPLCN Temperature coupling node. This is the node that the coupled temperature will be

equivalenced to for solution purposes. This node’s temperature will be assigned to the coupled node for output purposes.

NODXYZ (keyword) NODEID NODEX NODEY NODEZ


Print ControlThis section explains how to enter print interval data. Below describes how to enter an initial output print interval; Print Interval Adjustments, 259 describes how to enter data to alter this value during the course of a transient run; and Nodal Print Block Definitions, 260 describes how to specify which nodal temperatures will be printed as output data.

Initial Output Print Interval

ExampleTPRINT 1.0D+01

This example sets the print interval to 1.0D+01 seconds.

Print Interval Adjustments

ExamplePRINTA 10.0 5.0PRINTA 100.0 1000.0PRINTA -4.0 1501.0

This will cause a new print interval of 10.0 at time = 5.0 and another new print interval of 100.0 at time = 1000.0. Print dumps will also be made at 5.0 and 1000.0. The negative print interval at time 1501 will force the output times to be on even multiples of the print increment. The 1501 print staging will yield

Parameter DescriptionNODEID User node ID that the x, y, z node locations are to be applied. The node locations are

stored internally in the same order that the node temperatures are defined. Thus all internal node index references are consistent with the node locations defined in this block. It is not necessary to input all node locations, only those that are to be used in the analysis. When no more data is to be entered in the node locations block, simply put a dollar sign ($) in column 1.

NODEX Node x location in a global Cartesian coordinate system. NODEY Node y location in a global Cartesian coordinate system.NODEZ Node z location in a global Cartesian coordinate system.

TPRINT (keyword) TPRINT

Parameter DescriptionTPRINT Initial time interval between successive output data printings for transient

calculations. The print-time interval may be modified (see Print Interval Adjustments, 259) during a transient run.

PRINTA (keyword) PRINTA(I,1) and PRINTA(I,2)


260

printout at 1500 second which is a result of the normal print increment of 100 at the previous staged time, plus a print dump at time 1501 which is forced at all print staging times, plus a print out at time 1504 because the print was forced to be on even multiples of the print increment. All further print dumps will be at multiples of 4.0 time units.

QTRAN allows the value of the output print interval to be adjusted during the course of the simulation. The values of PRINTA(I,1) and PRINTA(I,2) are entered as an ordered pair. PRINTA(I,1) and PRINTA(I,2) are defined below.

Nodal Print Block Definitions

ExamplePBLOCK 2 20 2 ; (Print even nodes 2 - 20 in the QOUTDAT file)

This will cause the even node numbers from 2 to 20 to be printed out. The comment to the right of the semicolon will be ignored by QTRAN.

PBLOCK(1), PBLOCK(2), and PBLOCK(3) allow the starting node number to be specified, the ending node number, and the node number increment, respectively, of a Print Block (group of nodes whose temperature values are to be printed).

QTRAN will continue to read data for Print Blocks until a dollar sign ($) is encountered in column 1 of the input data file. If no entries are made in this section, QTRAN will print temperatures for all nodes in the system. As many Print Block definitions may be entered in the QINDAT file.

Parameter DescriptionPRINTA(I,1) New print interval value for output during a transient simulation. Negative values

force the output to be on multiples of the print interval.PRINTA(I,2) Time at which the new print interval will be initiated, and the time at which a print

dump will be made.

As many pairs of PRINTA data may be entered as needed. Data entered for PRINTA pairs will force QTRAN to end a time step and to begin a new time step on any time values entered for PRINTA(I,2). When all PRINTA data pairs have been entered, enter a dollar sign ($) in column 1 of the input data file and proceed to Nodal Print Block Definitions, 260. If no PRINTA data is needed, enter a dollar sign ($) in column 1 and proceed to Nodal Print Block Definitions, 260.

PBLOCK (keyword) PBLOCK(1...3)

Note: This command has no effect on the nodal results files generated directly by QTRAN.


Nodal Plot Block Definitions

ExampleIPLTBK 2 20 2 ; (Write even nodes 2 - 20 to the QPLOTDAT file)

This will cause results data for the even node numbers from 2 to 20 to be written to the QPLOTDAT file. The comment to the right of the semicolon will be ignored by QTRAN.

IPLTBK(1), IPLTBK(2), and IPLTBK(3) allow the starting node number to be specified, the ending node number, and the node number increment, respectively, of a Plot Block (group of nodes whose temperature values are to be written to the plot file).

QTRAN will continue to read data for Plot Blocks until a dollar sign ($) is encountered in column 1 of the input data file. If no entries are made in this section, QTRAN will open or create a plot file. As many Plot Block definitions may be entered in the QINDAT file.

Parameter DescriptionPBLOCK(1) Used to specify the first node number of a Print Block. For example, to print node

numbers 15-23 for the nodal Print Block, PBLOCK(1) should have the value of 15.PBLOCK(2) Used to specify the last node number of the Print Block. For example, to print node

numbers 15-23 for the Print Block, the value of PBLOCK(2) should be 23.

DEFAULT: If a 0 or blank is entered for PBLOCK(2) and PBLOCK(3), QTRAN will set PBLOCK(2) to the value entered for PBLOCK(1) and will set PBLOCK(3) to 1.

PBLOCK(3) Used to specify the node number increment for the print block. For example, to print all node numbers from 15-23, the value of PBLOCK(3) should be 1. Negative values of PBLOCK(3) are allowed and may be used if needed.

DEFAULT: If a 0 or blank is entered for PBLOCK(3), QTRAN will set PBLOCK(3) to 1.

To specify single nodes as a Print Block, enter the same value for PBLOCK(2) as was entered for PBLOCK(1), or you may enter both PBLOCK(2) and PBLOCK(3) as zero or blank.

IPLTBK (keyword) IPLTBK(1...3)


262

The Plot FileThe format of the resultant binary plot file, which has the default name QPLOTDAT, is as follows:

At the beginning of each file, a single record is written that contains three character variables each 80-characters in length. This is a header record that contains title information and indicates when the file was created.

The output for each time point follows the header until the end of the file. Each time point output consists of two records. The first record has three variables, time, a double precision variable; number of nodes, an integer; and a logical flag which is true, if steady state results follow, and is false, if the data is from a transient time step. The second record contains data pairs for each node specified. The first variable is an integer specifying the actual node number with a double-precision variable that defines the temperature.

Parameter DescriptionIPLTBK(1) Used to specify the first node number of a Plot Block. For example, plot node

numbers 15-23 for the nodal Plot Block, IPLTBK(1) should have the value of 15.IPLTBK(2) Used to specify the last node number of the Plot Block. For example, to plot node

numbers 15-23 for the Plot Block, the value of IPLTBK(2) should be 23.IPLTBK(3) DEFAULT: If a 0 or blank is entered for IPLTBK(2) and IPLTBK(3), QTRAN will

set IPLTBK(2) to the value entered for IPLTBK(1) and will set IPLTBK(3) to 1.

Used to specify the node number increment for the Plot block. For example, plot all node numbers from 15-23, the value of IPLTBK(3) should be 1. Negative values of IPLTBK(3) are allowed and may be used if needed.

DEFAULT: If a 0 or blank is entered for IPLTBK(3), QTRAN will set IPLTBK(3) to 1.

To specify single nodes as a Plot Block, enter the same value for IPLTBK(2) as was entered for IPLTBK(1), or enter both IPLTBK(2) and IPLTBK(3) as zero or blank.

263Chapter 8: Thermal/Hydraulic Input DeckMaterial Properties

Material PropertiesThis section is used to define material properties to QTRAN, including properties which are to be assigned after phase changes have occurred.

Use the procedure shown below to define a material property.

1. Enter all data for the material property from MPID Number, Function Type, Temperature Scale, Factor and Label, 263. This information specifies the material property identification (MPID) number, defines the function type that will be used to evaluate the material property, the temperature scale conversions necessary (if tabular or power series evaluations are to be performed), a scaling factor, and text line labels that will be used to document the material property in the printout.

2. Enter all Material Property Data, 268. This section is used to enter x-y table data, coefficient/exponent data for a power series evaluation, data for use in a Sutherland equation, values for constant material properties, or phase change data sets. When all data has been entered, enter a slash (/) in column 1 of the next input data file line and continue on to Step (3).

3. If no more material properties are to be entered, enter a dollar sign ($) in column 1 of the next input data file line and proceed on to Network Construction, 276. If more material properties are to be defined, return to Step (1) and continue with this procedure until all material property data has been entered for this section.

MPID Number, Function Type, Temperature Scale, Factor and Label

ExampleMPID 1234 T Fahrenheit 2.0D+00Zinc Oxide Thermal Conductivity

This declares that material property ID number 1234 will be a linear table input in degrees Fahrenheit (only the first character of ITSCAL is significant) and that the material property values in the table will be scaled by a factor of 2.0D+00. The material property label is “Zinc Oxide Thermal Conductivity.”

When the MPID, IEVAL, ITSCAL, FACTOR, and LABEL data have been entered, proceed to Material Property Data, 268 to finish defining the material property.

Note: This data is normally extracted from the MPIDMKSBIN, MPIDIPSBIN, MPIDFPHBIN or MPIDCGS material property databases via PATQ menu pick 4 or placed in the MATDAT file by the user.

MPID (keyword) MPID IEVAL ITSCAL NODEZ [LABEL]

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisMaterial Properties

264

Parameter DescriptionMPID Material Property Identification Number (MPID) that is assigned to each material

property. This MPID number will then be used to reference the material property in Network Construction, 276 as part of the thermal resistor and capacitor data. MPID numbers must be greater than 0 when defined in this section.

IEVAL Material property evaluation code that denotes whether the material property is to be evaluated as a constant, table, power series, Sutherland equation, Bingham equation, reciprocal relation, straight line, arbitrary order polynomial, phase change data set, or user-supplied subroutine. The allowed evaluations are listed below. Note that only the first character of the IEVAL string is typically significant, so T, Table, and Table_Data are equivalent. There are exceptions. For example the power series evaluation and the phase change data sets. For these two characters must be supplied (i.e., PO for power series or PH for phase change data sets). If the IEVAL character string contains blanks, it must be enclosed in single quotes. The MDATA1 and MDATA2 values are input constants that are specified in Material Property Data, 268.


A - The material property is an arbitrary order polynomial of the following form (MDATA2 values are ignored):

P(T) = MDATA1(1) + MDATA1(2) * T1 + MDATA1(3) * T2 + ... + MDATA1(N)

* T(N-1)

B - This property is the viscosity of fresh water at normal pressures, and the viscosity is to be calculated using the Bingham equation (see Ref. 4, p. 665). The units will be N-s/m2 if the calculations are performed in Celsius or Kelvin, and lbm/ft-s if the calculations are performed in Fahrenheit or Rankine.

C - The material property is a constant.

D - Description. Provides a way to pass text information through material properties to user routines

DV - Dependent Variable material properties are used in conjunction with an independent variable material property. Particularly useful if several functions have the same independent variable significant. Not only does one have a savings in space but the evaluation for subsequent dependent values is faster.

H - The data forms a tabular function that is to be interpolated using Hermite polynomials or extrapolated using a quadratic polynomial. The Hermite polynomial is a cubic, and is used only for interpolation. The Hermite polynomials insure that the function and the slope are continuous from interval to interval within the data table. Quadratic interpolation is used on the first and last interval of the table. At least three data pairs must be defined to use this option. See MDATA1/MDATA2 in Material Property Data, 268.

ID - Independent variable provide the independent variable so that interpolation factors can be defined for a series of dependent variable routines that reference it. Two interpolation options are available, one is a linear table and the other is a logarithmic table. The data and operation of the table is the same as the indexed linear table.

IH - The data forms an indexed tabular function that is to be interpolated using Hermite polynomials or extrapolated using a quadratic polynomial. The difference between the index hermite and the hermite interpolation is that the index hermite begins its search for valid table position based on the last exit from the table. This can yield significant time improvements.


266

L - The data forms a tabular function that is to be linearly interpolated or extrapolated. The temperature intervals of the table are equally spaced. The table is interpolated or extrapolated based on a Linear Computed Interval (LCI) algorithm. This is the fastest of QTRAN's table interpolation algorithms. A minimum of two property values must be defined to use this option. See MDATA1 in Material Property Data, 268.M - The data is used to form a straight line of the following form:

P(T) = MDATA1(1) * T + MDATA2(1)

Optical Thermal - Radiation variables that can be translated for interfacing to external radiation codes. Used by the STEP TAS interface.

PE - The data forms are indexed tabular functions which is linear interpolated. the independent variable is normalized by the period which is the difference between the maximum and minimum values specified for the independent variable.

PH - The data will be evaluated as a phase change data set, with each MDATA1/MDATA2 data pair corresponding to a phase transition temperature (MDATA1), and a latent heat (MDATA2).

PO - The data will be evaluated as a power series of the form:

P(T) = MDATA1(1) * TMDATA2(1) + ...

+ MDATA1(N) * TMDATA2(N)


R - The data will be evaluated as a reciprocal function, i.e.:

S - The data will be evaluated as a Sutherland equation. Sutherland equations are commonly used for liquid and gas material properties such as viscosities and thermal conductivities. A Sutherland equation is defined as follows:

where:

P[T] = property value at temperature T;P[o] = property value at reference temperature T[o]; andS = Sutherland constant for the particular material.For more information about Sutherland equations, see Ref. 4. in Appendix A, and also later in this section.

T - Data forms a tabular function that is to be linearly interpolated or extrapolated. A minimum of two data pairs must be defined to use this option. See MDATA1/MDATA2 in Material Property Data, 268.

IT - Data forms an indexed tabular function that is to be linearly interpolated or extrapolated. This is identical to the tabular function except the table is entered at the position that it was previously exited.U - Data given for MDATA1(1) will be used to specify a specific user-supplied subroutine option. When a U is specified for IEVAL, QTRAN will call user-supplied subroutine UPROP to get a property value. The value given for MDATA1(1) may be used to select a specific suboption (e.g., a whole family of user-supplied algorithms may exist in subroutine UPROP and MDATA1(1) may be used as an algorithm option identifier).

Notice: The scale factor for this evaluation option is read but not used.ITSCAL Temperature scale for which the tabular input data is valid (all other conversion

routines ignore ITSCAL). QTRAN will automatically convert data tables from other temperature scales into the temperature scale defined for calculations (see ICCALC, (p. 230)). For example, if calculations are being performed in Kelvin (i.e., ICCALC = K in Temperature Scale and Time Units Definition, 230 but the material property data available is in Celsius, QTRAN will convert this table to Kelvin before use if ITSCAL is entered as C. Note that only the first character of the ITSCAL character string is significant, so “F” and “Fahrenheit” are equivalent.

P T( ) 1MDATA1 1( ) * T MDATA2 1( )+( )( )

------------------------------------------------------------------------------------------------=

P T( )P o[ ]------------ T( )1.5

T o[ ]( )1.5---------------------- * T o[ ] S+( )

T S+( )--------------------------=


268

Material Property Data

MDATA1 and MDATA2 are material property data pairs and are entered for the various evaluation algorithms.

ExampleMDATA 2.0 5.0

This defines an MDATA1 value of 2.0 and an MDATA2 value of 5.0. Depending upon the evaluation option selected (IEVAL parameter), the 2.0 and 5.0 may be used in various ways. See below for more specific information.

Table data may be converted to or from any of the following temperature scales:

F--Fahrenheit

C--Celsius

K--Kelvin

R--Rankine

T--Time If T (for time) is given for ITSCAL, no table conversions will occur. The “material property” is then evaluated as a time dependent function, regardless of the IEVAL option selected.

FACTOR A scaling factor that is used to easily scale a material property’s values. The value entered for FACTOR is used to multiply the property data. If a number whose absolute value is less than 1.E-18 is entered for FACTOR, FACTOR will be assigned a value of 1.0. In addition to scaling for parameterization runs, FACTOR may also be used to change units systems conveniently.

Notice: FACTOR applies to all material property evaluation options EXCEPT the BINGHAM fresh water viscosity equation and the user-supplied subroutine option. For these options, FACTOR is read but is not used.

LABEL One or more 80-character identification labels that will be read by the program and printed with the echoed input data. These labels identify material properties for your convenience, but the labels are not used by QTRAN. These labels allow short messages to be printed (e.g., NITROGEN VISCOSITY) with the material property data to facilitate documentation. As many lines of label data as desired may be entered (anything between the MPID line and the terminating / character that does not start with the keyword MDATA will be treated as a label).

MDATA (keyword) MDATA1 MDATA2


ARBITRARY-ORDER POLYNOMIALEnter the polynomial coefficients into the MDATA1 array. MDATA2 data will be ignored. The MDATA1 data will be used in the following fashion for the polynomial:

P(T) = MDATA1(1) + MDATA1(2) * T + MDATA1(3) *

T2 + ... + MDATA1(N) * T(N-1)

Example MPID 17 Arbitrary-Polynomial Celsius 1.0Example Arbitrary Order Polynomial DefinitionMDATA 1.0MDATA 1.3MDATA -0.3/

This example defines the polynomial

P(T) = 1.0 + 1.3 * T - 0.3 * T2

for MPID 17 with a scale factor of 1.0. It declares that the polynomial is valid in degrees Celsius. The value of T used will be in degrees Celsius.

BINGHAMDo not enter any parameters for a Bingham equation evaluation. The correct Bingham equation parameters are already stored in QTRAN.

ExampleMPID 23 Bingham Kelvin 1.0Bingham Fresh Water Viscosity Equation/

This example defines MPID 23 to be the Bingham freshwater viscosity equation.

CONSTANTEnter the constant’s value as MDATA1(1).

Example MPID 47 Constant Kelvin 1.0Constant Material Property DefinitionMDATA 1.2345/

This material property definition defines MPID 47 to be a constant with a value of 1.2345. The scale factor is 1.0, and the temperature scale definition of Kelvin is ignored.


270

H AND T TABLE INTERPOLATION OPTIONSData for the H and T data evaluation options are entered as ordered pairs from the lowest temperature values to the highest temperature values as follows:

MDATA1(1...N) = Temperature valuesMDATA2(1...N) = Corresponding property values

Example MPID 3 Table Fahrenheit 1.0Example Linear Table Property DefinitionMDATA0.027.0MDATA100.029.4MDATA173.055.2MDATA2000.087.3/

This material property definition has temperatures of 0.0, 100.0, 173.0, and 2000.0 Fahrenheit and property values of 27.0, 29.4, 55.2, and 87.3. It declares that it is a linear irregular interval table property with a scale factor of 1.0 and an MPID number of 3.

codeindent10MPID 4 Hermite Fahrenheit 23.79E-03Example Linear Table Property DefinitionMDATA0.027.0MDATA100.029.4MDATA173.055.2/

This material property definition has temperatures of 0.0, 100.0, and 173.0 Fahrenheit and property values of 27.0, 29.4, and 55.2. It declares that it is a Hermite Polynomial irregular interval table property with a scale factor of 23.79E-03 and an MPID number of 4.

IH AND IT TABLE INTERPOLATION OPTIONSThese options are identical to the H and T option defined previously except the tables are entered at the location (index) that they were previously exited. Data for the IH and IT data evaluation options are entered as ordered pairs from the lowest temperature values to the highest temperature values as follows:

MDATA1(1...N) = Temperature valuesMDATA2(1...N) = Corresponding property values

Example MPID 3 ITable Fahrenheit 1.0Example Linear Table Property DefinitionMDATA0.027.0MDATA100.029.4

Note: At least two data pairs must be entered for the T option, and at least three data pairs for the H option.


MDATA173.055.2MDATA2000.087.3/

This material property definition has temperatures of 0.0, 100.0, 173.0, and 2000.0 Fahrenheit and property values of 27.0, 29.4, 55.2, and 87.3. It declares that it is an indexed linear irregular interval table property with a scale factor of 1.0 and an MPID number of 3.

ExampleMPID 4 IHermite Fahrenheit 23.79E-03Example Linear Table Property DefinitionMDATA0.027.0MDATA100.029.4MDATA173.055.2MDATA2000.087.3/

This material property definition has temperatures of 0.0, 100.0, 173.0, and 2000.0 Fahrenheit and property values of 27.0, 29.4, 55.2, and 87.3. It declares that it is an index Hermite Polynomial irregular interval table property with a scale factor of 23.79E-03 and an MPID number of 4.

L (LINEAR COMPUTED INTERVAL TABLE EVALUATION)Data for the LCI option is entered as shown below. Note that the LCI option is the preferred table interpolation option because it is much faster than any other table interpolation algorithm in QTRAN.

ExampleMPID 7 LCI K 1.0Example LCI table property.MDATA0.0 ; Base TemperatureMDATA100.0;Temperature IncrementMDATA23.7;Property Value at 0.0 KMDATA 29.9;Property Value at 100.0 KMDATA 25.3;Property Value at 200.0 KMDATA17.2;Property Value at 300.0 KMDATA0.7;Property Value at 400.0 KMDATA0.7;Property Value at 500.0 K/

Note: At least two data pairs must be entered for the IT option and at least three data pairs for the IH option.

MDATA1(1) Lowest temperature in the tabulated property dataMDATA1(2) Temperature interval assumed between all property entriesMDATA1(3...N) The table property values, beginning at the lowest temperature property value and

proceeding to the highest temperature property value in the LCI table. At least two property values must be entered

MDATA2 values are ignored and should be left blank


272

This material property definition declares that MPID 7 is an LCI equal interval linear table with a base temperature of 0.0 K and a temperature increment of 100.0 K. The property values given are 23.7, 29.9, 25.3, 17.2, 0.7, and 0.7 with a scale factor of 1.0.

Please note that according to QTRAN convention, anything to the right of a semicolon (;) is an optional comment and hence is ignored.

STRAIGHT LINEThe straight line will evaluate the MDATA1 and MDATA2 values that you enter exactly as follows:

P(T) = MDATA1(1) * T + MDATA2(1)

ExampleMPID 32 M K 1.0Example Straight Line Material PropertyMDATA 0.17 117.9/

This material property definition declares that MPID 9 is a straight line of the form:

P(T) = 0.17 * T + 117.9

with T valid for degrees Kelvin and with a scale factor of 1.0. The evaluation option (IEVAL) was given as a character string surrounded by single quote marks, 'M (Straight Line)'. Only the first character, M, is significant.

PEriodic DataThis option provides a mean of defining a repeating waveform which is linearly interpolated between data points. The minimum and maximum independent variable values which defines an interval used to normalize the input independent variable value so that interpolation is always between the minimum and maximum value specified.

MDATA1 (1...N) = Independent variable valuesMDATA2(1...N) = Corresponding property values

ExampleMPID 104621 PEriodic Time 1.4MDATA60.0122.MDATA71.0212.MDATA76.51400.MDATA92.0220./

In the above example, the property will repeat every 32 time units following a linear interpolation. Note by the example discontinuities are allowed between the beginning and ending of a period.


PHASE CHANGE DATAThe phase change data option allows you to input phase transition temperature-latent heat data pairs. Each MDATA1 value is a phase transition temperature, and each MDATA2 value is the corresponding latent heat.

As many MDATA1 / MDATA2 pairs as necessary may be used for the model (there is no coded limit). These pairs must be input in ascending temperature order. For accuracy, it is also necessary that no single node should undergo more than one phase transition per time step.

ExamplesMPID 1023 PHase Change Data Kelvin 1.0Example #1 Phase Change Data SetMDATA600.01024.9; T=600,H=1024.9/MPID 1 PH Rankine 1.1Example #2 Phase Change Data SetMDATA763.941.97E+06;T1=763.94,H1=1.97E+06MDATA948.72.0E+05; T2=948.7, H2=2.00E+0541/

POWER SERIESThe power series will evaluate the MDATA1 and MDATA2 values that are entered exactly as follows:

P(T) = MDATA1(1) * TMDATA2(1) + ... MDATA1(N) * TMDATA2(N)

ExampleMPID 49 Power Series Rankine 1.0Example Power Series Material Property DefinitionMDATA1.2-0.4MDATA7.30.1MDATA1.0E+012.0/

This example material property definition declares that MPID 49 is a power series function of the form:

P(T) = 1.2 * T(-0.4) + 7.3 * T0.1

+ 1.0E+01 * T2.0

where T is valid for degrees Rankine. A scale factor of 1.0 is declared.

RECIPROCAL FUNCTIONThe Reciprocal function will evaluate the MDATA1 and MDATA2 values that are entered exactly as follows:

ExampleMPID 10 'Reciprocal Function' Celsius 1.0

P T( ) 1MDATA1 1( ) * T MDATA2 1( )+( )-------------------------------------------------------------------------------------------=


274

Example Reciprocal Function Material PropertyMDATA1.0273.15/

This material property definition declares that MPID 10 is a Reciprocal function of the form:

with T valid for degrees Celsius and with a scale factor of 1.0. The evaluation option (IEVAL) was given as a character string surrounded by single quote marks, 'Reciprocal Function'. Only the first character, R, is significant. A common use of this type of material property is to define bulk coefficients of expansion for ideal gases (1/T absolute).

SUTHERLANDEnter the Sutherland equation data as follows:

where:

ExampleMPID 78 Sutherland Kelvin 1.1Example Sutherland Equation Material PropertyMDATA0.78.9;P[o] and T[o].MDATA23.9; S./

This example material property definition declares that a Sutherland equation of the form:

where T is valid for degrees Kelvin. Note that anything right of the semicolons in the example is an optional comment and may be omitted.

USER-SUPPLIED SUBROUTINE

The user-supplied subroutine option will use both MDATA1 and MDATA2. The MDATA data pairs will be passed to the user-supplied subroutine and may be used there as an option identifier, or for any other purpose that the user wishes.

ExampleMPID 88 U K 1.0

MDATA1(1) P(0)

MDATA2(1) T(0)

MDATA1(2) S

P T( ) 11.0 * T 273.15+( )-----------------------------------------------=

P T( )P 0( )------------ T1.5

T 0( )1.5----------------- T 0( ) S+

T S+---------------------+=

T( )0.7-------- T1.5( )

8.91.5( )------------------ * 8.9 23.9+( )

T 23.9+( )------------------------------=


Example User-Supplied Subroutine Material PropertyMDATA 2/

This example declares that MPID 88 will reference a user-supplied subroutine. The MDATA value of 2 may be used by that routine for any purpose needed, including using the MDATA value as an option to determine a particular algorithm for evaluation. The user-supplied routine may in fact contain several evaluation options. See User-Supplied Subroutines (Ch. 11) for more information.

When all MDATA1-MDATA2 data have been entered (if any) for a material property, enter a slash (/) in column 1 of the input data file. To enter data for another material property, return to MPID Number, Function Type, Temperature Scale, Factor and Label, 263.

When all of the material properties have been defined, enter a dollar sign ($) in column 1 of the input data file and proceed to Network Construction, 276.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisNetwork Construction

276

Network ConstructionThis section describes how to define the thermal network to QTRAN. All resistors and capacitors will be defined in this section. The parameters and options controlled by input are listed below.

1. Thermal Resistor Assignments.2. Nodal Capacitance Data.

Thermal Resistor AssignmentsThis section describes how to enter the thermal resistor data that will be used to describe a given problem. The allowed resistor types are identified as follows:

To enter a data set for any given thermal resistor type, proceed to the appropriate section in any arbitrary order, enter all required data for the resistor, and then proceed to the next resistor to be defined. When all of the resistor information has been entered for the problem, place a dollar sign ($) in column one of the input data file and proceed to Capacitor Data, 320.

Conductive Resistor Data

This sections describes how to enter data that describe single conductive resistors. To define a conductive resistor, follow the procedure outlined below.

Enter all data for the resistor from this section. This data defines the resistor as a conduction resistor, defines the nodal connectivity of the resistor, defines the resistor as one-way or two-way (two-way is the normal usage), identifies the material property to be used for thermal conductivity, and defines the effective length/area data for the resistor.

Note: PATQ normally generates all of the resistor and capacitor data automatically via menu pick 2.

C - Conductive Resistor (p. 276)H - Convective Resistor (p. 280)R - Radiative Resistor (p. 283)W - Wavelength-Dependent Radiative Resistor (p. 291)L - Automatic 1-D Conduction MeshGeneration (p. 300)A - Advective Resistor (p. 305)F - Hydraulic Resistor (p. 306)

RES -TYPE NODE1 NODE2 MPID LENGTH AREA

277Chapter 8: Thermal/Hydraulic Input DeckNetwork Construction

If no more thermal resistor data of any kind is to be entered, enter a dollar sign ($) in column 1 of the input data file and proceed to Capacitor Data, 320. As a result for the PATQ translation (menu pick 2) these declarations are placed in the CONDUCDAT file. If more thermal resistors are to be defined, proceed to the appropriate section ((p. 276) to (p. 306)) and continue with resistor data input.

Example

This defines a conductive resistor between nodes 4 and 7 with a thermal conductivity MPID of 23, a length of 1.4, and an area of 23.7.

C 4 7 23 1.4 23.7


278

Parameter DescriptionRES-TYPE An alpha character that defines the resistor type. In this case, RES-TYPE is

entered as C to identify a conductive resistor.NODE1 Node 1 of the conductive resistor.NODE2 Node 2 of the conductive resistor.

Notice: You may specify these resistors as one-way resistors if you wish. This means that they may be made to transmit heat in one direction but not in the other. If you wish to do this, input the node that you do not wish heat to flow to as a negative number. Heat will then be allowed to flow from the negative node to the positive node, but not from the positive node to the negative node.

MPID The MPID number of the material property that is to be used to calculate the thermal conductivity of the resistor. See MPID Number, Function Type, Temperature Scale, Factor and Label, 263. To define a time-dependent thermal conductivity, enter MPID as the negative of the MPID to be used.

LENGTH Length of the conductive resistor.


AREA Cross-sectional area associated with flux through the conductive resistor.

For Cartesian conductive resistors, the thermal resistance for such a resistor is given by the following expression:

where R is the resistor value, Length is the distance between nodes, k is the thermal conductivity, and Area is the cross-sectional area available for heat to flow through between the nodes. This expression may be factored and rewritten in the following form, which separates the geometric data and the thermal conductivity as follows:

where CSF is a conduction shape factor.

For non-Cartesian resistors, you may enter the analogous values for Length (LENGTH) and Area (AREA) that will result in the calculation of the appropriate CSF for your non-Cartesian resistor. For example, the resistance of a cylindrical wall is given by the expression:

R Lengthk * Area( )

----------------------------=

R 1k---⎝ ⎠

⎛ ⎞ * LengthArea

-------------------⎝ ⎠⎛ ⎞ 1

k---⎝ ⎠

⎛ ⎞ * CSF= =

R : n R 2[ ]R 1[ ]------------⎝ ⎠

⎛ ⎞ * 12 * PI * L c[ ]--------------------------------------=


280

Convective Resistor DataThe following sections are used to define convective resistors. As a result of the PATQ translation (menu pick 2), these declarations are placed in the CONVECDAT file. The procedure that you will use to define a convective resistor is explained below.

1. To enter all data for the convective resistor see Convective Resistor Header Data, 281. This data identifies the resistor as a convective resistor, defines the resistor node numbers, and defines the resistor configuration (which must be selected from the convective resistor catalogue in Convection Configurations (Ch. 9)).

2. Enter the data for the resistor for Convective Resistor Geometric Properties, 281. This data defines all Geometric Properties (GP) such as characteristic lengths, surface areas, and fluid free-stream velocities. See Convection Library (Ch. 9) for more information about specific resistor configurations and the required GP data for each configuration.

3. Enter all data for the resistor for Convective Resistor Material Properties, 282. This data is used to identify which of the material properties that you defined in MPID Number, Function Type, Temperature Scale, Factor and Label, 263 will be used to define this convective resistor. See Convection Configurations (Ch. 9) for more information about specific resistor configurations and the required MPID data for each configuration.

4. When all of the thermal resistors are defined, place a dollar sign ($) in column 1 of the input data file and proceed to Capacitor Data, 320. To define another thermal resistor, proceed to the resistor data section ((p. 276) to (p. 306)) that applies to the next resistor to be defined.

where:

R[1] = inner radius of the cylindrical section you are modeling,

R[2] = outer radius of the cylindrical section you are modeling,

PI = usual quantity related to circles (3.1415 etc.),

L[c] = length of the cylindrical section you are modeling, and

k = material’s thermal conductivity.

Thus, a correct and equivalent method to enter this resistor’s value is to let

AREA = 1.000

and to let

This yields a correct CSF value, which is the only information that is of mathematical significance.

Length : n R 2[ ]R 1[ ]------------⎝ ⎠

⎛ ⎞ * 12 * PI * L c[ ]--------------------------------------=


Convective Resistor Header Data

This section allows a given thermal resistor to be identified as a convective resistor, to define its node numbers, and to specify the resistor configuration.

Example H 1 3 0 14

This heads the resistor data for a convective resistor between nodes 1 and 3 (no third node), and specifies convection configuration number 14.

Convective Resistor Geometric Properties

Example24.723.20.014.829.915.618.9/

This enters 7 GP values of 24.7, 23.2, 0.0, 14.8, 29.9, 15.6, and 18.9, in that order using free format input.

RES -TYPE NODE1 NODE2 NODE3 CFIG

Parameter DescriptionRES-TYPE An alpha character that defines the resistor type. In this case, RES-TYPE is entered

as H to identify a convective resistor.NODE1 Node 1 of the convective resistor.NODE2 Node 2 of the convective resistor.NODE3 Node 3 of the convective resistor. Although most convective resistors have only two

node numbers, certain of the convective resistors require that you define three nodes. If the convective resistor that is being defined requires only two nodes, enter a zero for the NODE3 value.

CFIG Convective resistor configuration identification number, where configuration is defined as the class of convection correlations that would be used for a given problem. For example, flat plates would be one type of resistor configuration, and flow across horizontal cylinders would be another configuration type. For specifics, consult the convective resistor catalogue in Convection Library (Ch. 9) for available configurations. Allowed CFIG values are 1 to 37 inclusive, in addition to numbers greater than or equal to 1000. CFIG values of 1000+ are used to refer to user-supplied convection configuration subroutine.

RES -GP(1) GP(2) GP(n)


282

Convective Resistor Material Properties

Example

This declares MPID values of 1, 7, 4, 6, 15, and 23.

Example Convective Resistor DefinitionThe following is an example of a complete convective resistor definition.

ExampleH 23 45 0 14

1.23 9.8 15/ 45 72 88 99 1024/

This QTRAN input data defines a configuration 14 convective resistor between nodes 23 and 45. The GP values are 1.23, 9.8, and 15. The MPID numbers are 45, 72, 88, 99 and 1024.

Parameter DescriptionGP Convective resistor’s Geometric Properties such as length, diameter, surface area,

or gravitational constants. The exact meaning of each GP value varies for each configuration. See Convective Resistor Header Data, 281. Consult Convection Library (Ch. 9) for specific configurations and GP meanings. QTRAN will continue reading GP values until it encounters a slash (/) in column 1 of the input data file. The procedure for entering GP values is to enter all GP values followed by an input data file line with a slash in column 1. It should be noted that any number GP values may be placed on an 80 character line, or multiple lines may be used. The maintaining of the order is the important consideration. Proceed on to Convective Resistor Material Properties, 282.

MPID(1) MPID(2) MPID(n)

1 7 4 6 15 23

Parameter DescriptionMPID Material property identification numbers for the convective resistor. See MPID

Number, Function Type, Temperature Scale, Factor and Label, 263 for more information. For specifics, consult the convective resistor catalogue in Chapter 6. The material properties that correspond to each MPID entry are listed for each configuration in the catalogue. When done entering MPID values, enter a slash (/) in column 1 of the next line of the input data file.


Gray Radiative Resistor Data

The following two sections allow gray or black-body thermal radiation resistors to be identified to QTRAN. These resistors can be either variable or constant and are allowed to be functions of time or temperature but not wavelength. QTRAN will use σ * T4 as the potential across these thermal resistors in accordance with normal network conventions, and the value of T used will be an absolute temperature. If calculations are being performed in degrees Fahrenheit (that is, if ICCALC was defined as F in Temperature Scale and Time Units Definition, 230), Rankine will be used for T. If calculations are being performed in Celsius (that is, if ICCALC was defined as C), Kelvin will be used for T. This convention will be used even if the temperature nodes to which the resistor is connected is a view factor radiosity node rather than a surface temperature node. As a result of the PATQ translation (menu pick 2) and VIEW FACTOR execution (menu pick 3), these declarations are placed in the VFRESDAT file. The procedure used to define a gray thermal radiation resistor is explained below.

1. Enter all data for the gray thermal radiation resistor for Gray Type Specification, Node Assignments, and MPID, 283. This data identifies the resistor as a gray thermal radiation resistor, defines the resistor nodal connectivity, defines the resistor subtype, and identifies the material property MPID numbers for emissivity or transmissivity.

2. Enter the data for the resistor for Gray Radiative Resistor View factors, Areas, and Distances, 288. This data defines the view factor and/or surface area associated with the resistor as well as the view factor distance, if appropriate.

3. To terminate the definition of a thermal resistor of any type, place a dollar sign ($) in column one of the input data file and proceed to Capacitor Data, 320. To define another thermal resistor, proceed to the resistor data section ((p. 276) to (p. 306)) that applies to the next resistor to be defined.

Gray Type Specification, Node Assignments, and MPID

This section describes how to identify a given thermal resistor as a black-body/gray-body radiative resistor and to define the resistor node numbers. These resistors conduct heat according to the following relation:

where σ is the Stefan-Boltzmann constant, T[1] and T[2] are the temperatures of nodes 1 and 2 of the resistor in degrees absolute (QTRAN will perform the conversion to degrees absolute no matter which temperature scale is being used for calculations), and R is the value of the radiative resistor.

ExampleR 1 3 4 2 15

This defines a gray radiative resistor between nodes 1 and 3 with the transmissivity evaluated at the temperature of node 4, resistor subtype 2, and the transmissivity evaluated from MPID 15.

RES -TYPE NODE1 NODE2 NODE3 SUB-TYPE MPID

Q 1-->2[ ] σ * T 1[ ]4 T 2[ ]4–( )

R------------------------------------------------------=


284

The following table is a brief summary of resistor node assignments.

Parameter DescriptionRES-TYPE A character that defines the resistor type. In this case, RES-TYPE is entered as R to

identify a gray thermal radiation resistor.NODE1 Node 1 of the radiative resistor.NODE2 Node 2 of the radiative resistor.NODE3 Node 3 of the radiative resistor (if applicable). If input as zero, it will be set to

NODE1. If a resistor subtype does not require a NODE3 value, enter a 0 for NODE3.

Table 8-1 Gray Thermal Radiation Resistor Node Assignments

Resistor Subtype Node 1 Node 2 Node 3

1 Non-Black Surface Radiosity N/A

2 Radiosity Radiosity PM

3 PM Radiosity PM

4 Any Any N/A

5 Any Any N/A

6 Any Any N/A


8 PM Radiosity PM


10 PM Radiosity PM


12 PM Radiosity PM

13 Any Any N/A

14 Any Any N/A

15 Any Any N/A

N/A = Not applicable - no entry is necessary for Node 3.

PM = Participating Media - the node should be assigned participating media (e.g., participating gas) temperature node.


SUB-TYPE This is the resistor subtype, where:

Subtype: 1

This resistor type is used between a gray surface and a radiosity node, with an emissivity that is taken from a material property (MPID).

Subtype: 2

This resistor type is used between radiosity nodes, and with a time or temperature dependent participating media whose transmissivity is taken directly from a material property (MPID).

Subtype: 3

This resistor type is used between a radiosity node and a participating media node. The view factor is between the surface i and the gas (or other participating media node). The transmissivity of the gas (or participating media) is taken from a material property.

Subtype: 4

This resistor type may be used anywhere that material properties are constant. It would normally be used as a view factor resistor between radiosity nodes, but the F and A values are entered as simple constants and hence could be anything appropriate for a radiative resistor of this formulation. Since there is no data for transmissivity, the transmissivity of the resistor is implicitly assumed to be 1.0.

Subtype: 5

This resistor type may be used anywhere that material properties are constant. It would normally be used as a view factor resistor between two radiosity nodes, but the F value is a simple constant and hence could be anything appropriate for a radiative resistor of this formulation.

Note: This resistor type is used when a minimum of calculations are desired, thus for this type only the reciprocal of the resistance is input.

Subtype: 6

This resistor type may be used as a surface resistor, with the value given for e being the emissivity. This resistor subtype may be used anywhere the emissivity is constant. Because the emissivity is assumed to be constant, it is faster to evaluate than Subtype 1.

Subtype: 7

R 1 e–e * A----------------=

R 1F i j,[ ] * A i[ ] * τ gas[ ]----------------------------------------------------------------=

R 1F i gas,[ ] * A i[ ] * 1 τ gas[ ]–( )---------------------------------------------------------------------------------------=

R 1F i j,[ ] * A i[ ]------------------------------------=

R 1F---=

R 1 e–e * A----------------=

R 1F i j,[ ] * A i[ ] * τ gas[ ]----------------------------------------------------------------=


286

This resistor type is used between radiosity nodes. τ is calculated from an extinction coefficient identified by the resistor’s MPID and from a view factor distance. Specifically, τ[gas] = EXP(-S * P), where S is the view factor distance and P is the extinction coefficient calculated from the material property (MPID) of the resistor.

Subtype: 8

This resistor type is used between a radiosity node and a participating media node. τ is calculated from an extinction coefficient identified by the resistor’s MPID and from a view factor distance. The transmissivity value τ is calculated in the same manner as for Subtype 7.

Subtype: 9

This resistor type is used between radiosity nodes, and with a temperature dependent participating media whose transmissivity is taken directly from a material property (MPID). This is the same as Subtype 2, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

Subtype: 10

This resistor type is used between a radiosity node and a participating media node. The view factor is between the surface i and the gas (or other participating media node). The transmissivity of the gas (or participating media) is taken from a material property. This is the same as Subtype 3, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

Subtype: 11

This resistor type is used between radiosity nodes. τ is calculated from an extinction coefficient identified by the resistor's MPID and from a view factor distance. Specifically, τ[gas] = EXP(-S * P), where S is the view factor distance and P is the extinction coefficient calculated from the material property (MPID) of the resistor. This is the same as Subtype 7, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

R 1F i gas,[ ] * A i[ ] * 1 τ gas[ ]–( )---------------------------------------------------------------------------------------=

R 1AF i j,[ ] * τ gas[ ]-----------------------------------------------=

R 1AF i gas,[ ] * 1 τ gas[ ]–( )----------------------------------------------------------------------=

R 1AF i j,[ ] * t gas[ ]----------------------------------------------=


Subtype: 12

This resistor type is used between a radiosity node and a participating media node. τ is calculated from an extinction coefficient identified by the resistor’s MPID and from a view factor distance. The transmissivity value τ is calculated in the same manner as for Subtype 7. This is the same as Subtype 8, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

In the equations above:

R = is the value of the gray thermal radiation resistor,

e = is the gray emissivity of a radiating surface,

A = is the surface area of the radiating surface,

F = s the surface’s view factor,

AF = is the product of the surface's area and the view (subtypes 9-12) factor, and

τ[gas] = is the transmissivity of the participating media.

Subtype: 13

This resistor type may be used between any nodes. The F[i,j] term is defined by a material property (MPID) whose independent variable is either time or the temperature of the i-th node in calculation units. This is normally used to define dynamic viewfactor and thus would couple radiation between radiosity nodes. However, if both surfaces have constant emissivities then the F term can be thought of as a script F which includes any non black characteristics. The area term is a constant for this evaluation. Since there is no data for transmissivity, the transmissivity of the resistor is implicitly assumed to be 1.0. If diagnostic output is requested the F[i,j] term is output as an emissivity value.

Subtype: 14

This resistor type may be between used any nodes. The AF[i,j] term is defined by a material property (MPID) whose independent variable is either time or the temperature of the i-th node in calculation units. This is normally used to define dynamic viewfactor and thus would couple radiation between radiosity nodes. However, if both surfaces have constant emissivities then the AF term becomes a script F which includes any non black characteristics. The area term is a constant for this evaluation. Since there is no data for transmissivity, the transmissivity of the resistor is implicitly assumed to be 1.0. If diagnostic output is requested the F[i,j] term is output as an emissivity value. Although the area term is not used, it can be specified for reference purposes and is assumed to be the area of the i-th node.

R 1AF i gas,[ ] * 1 τ gas[ ]–( )----------------------------------------------------------------------=

R 1F i j,[ ] * A i[ ]------------------------------------=

R 1AF i j,[ ]----------------------=


288

Gray Radiative Resistor View factors, Areas, and Distances

codeindent100.73118 43.2 15.7

This defines a VIEW FACTOR value of 0.73118, AREA = 43.2, and VFDIST = 15.7.

Examples of Gray Radiative ResistorsThe following are examples of various gray radiative resistors for QTRAN.

MPID Emissivity or Transmissivity MPID number. MPID should be zero for resistor Subtype 4, Subtype 5, or Subtype 6.

Subtype: 15

The variable gap resistor is between two surfaces where both emissivities are defined by a material property even if one is a constant. Since the form factor will be one for this equation to be valid as used, it is not necessary to input a form factor, one will be assumed.

VIEW FACTOR AREA VFDIST

Parameter DescriptionVIEW FACTOR

Radiative resistor’s view factor (Subtype 2, Subtype 3, Subtype 7, and Subtype 8) is one of two constants multiplied together to compute the resistor’s value (Subtype 4), the product of the resistor area and the view factor (Subtype 9 through Subtype 12), the reciprocal of resistor’s value (Subtype 5), or is the resistor’s emissivity (Subtype 6 only). VIEW FACTOR may not be left blank for any of the subtypes. A numeric value must be entered (i.e., enter a 0 if VIEW FACTOR is not applicable to the resistor subtype, e.g., Subtype 1).

AREA Surface area associated with the radiative resistor (Subtype 1 through Subtype 3 and Subtype 6 through Subtype 8), or else is simply one of two constants multiplied together to compute the resistor’s value (Subtype 4), it could also be ignored (or left blank) for Subtype 5 and Subtype 9 through Subtype 12.

VFDIST View factor distance used with an extinction coefficient to calculate transmissivity for resistor Subtype 7, Subtype 8, Subtype 11, and Subtype 12. VFDIST is ignored for the other resistor subtypes and may be left blank.

R A1

e1------⎝ ⎠

⎛ ⎞ 1e2------⎝ ⎠

⎛ ⎞ 1F12---------- 2.0–+ +⎝ ⎠

⎛ ⎞--------------------------------------------------------------------=


Subtype: 1 R11201102345

0.021.73Defines a gray resistor between surface node 11 and radiosity node 2. MPID 102345 will be used to calculate the temperature-dependent emissivity. The view factor field is given as 0.0 and will be ignored by QTRAN (but must be there as a spacer), and the surface area is given as 21.73.Subtype: 2 R212399245

0.012415.78Defines a gray radiative resistor between radiosity nodes 21 and 23. The temperature of node 99 and MPID 45 will be used to compute the participating media transmissivity. The view factor is given as 0.0124 and the surface area for the resistor is given as 15.78.Subtype: 3 R141514388

0.01240.187Defines a gray radiative resistor between participating media node 14 and radiosity node 15. The transmissivity will be calculated from material property 88 using the temperature of node 14 (given as both NODE1 and NODE3 here). The view factor is given as 0.0124 and the surface area is given as 0.187.Subtype: 4 R7778040

0.8923.78Defines a gray radiative resistor between nodes 77 and 78. Nodes 77 and 78 may be any type of radiation network node (surface, radiosity, or participating media). The view factor value (or first constant) is given as 0.89 and the surface area (or second constant) is given as 23.78.Subtype: 5 R888991050

89.76Defines a gray radiative resistor between nodes 88 and 8991. The input value is 89.76, which is the reciprocal of the resistance.Subtype: 6 R1019060

7.890E-01 23.889Defines a gray radiative resistor between nodes 101 and 9. The constant emissivity has been given as 7.890E-01 and the surface area has been given as 23.889.Subtype: 7 R667767789089

0.0012385.7761.045E+02Defines a gray radiative resistor between radiosity nodes 66 and 77. The temperature of node 67 will be used with MPID 89089 to calculate an extinction coefficient. The view factor has been given as 0.00123, the surface area as 85.776, and the view factor distance as 1.045E+02.


290

Subtype: 8 R655656082525

0.128.9E+0284.88E+03Defines a gray radiative resistor between participating media node 655 and radiosity node 656. The temperature of node 655 will be used to calculate the extinction coefficient since NODE3 was entered as 0. The MPID of the extinction coefficient is 2525. The view factor is given as 0.12, the surface area as 8.9E+02, and the view factor distance as 84.88E+03.Subtype: 9 R212399945

0.0124Defines a gray radiative resistor between radiosity nodes 21 and 23. The temperature of node 99 and MPID 45 will be used to compute the participating media transmissivity. The product of the surface area and the view factor is given as 0.0124.Subtype: 10 R1415l141088

0.0124Defines a gray radiative resistor between participating media node 14 and radiosity node 15. The transmissivity will be calculated from material property 88 using the temperature of node 14 (given as both NODE1 and NODE3 here). The product of the surface area and the view factor is given as 0.0124.Subtype: 11 R6677671189089

0.001230.01.045E+02Defines a gray radiative resistor between radiosity nodes 66 and 77. The temperature of node 67 will be used with MPID 89089 to calculate an extinction coefficient. The product of the surface area and the view factor has been given as 0.00123, the AREA parameter (not used for this resistor subtype, but still necessary as a placeholder) has been given as 0.0, and the view factor distance as 1.045E+02.Subtype: 12 R6556560122525

0.12084.88E+03Defines a gray radiative resistor between participating media node 655 and radiosity node 656. The temperature of node 655 will be used to calculate the extinction coefficient since NODE3 was entered as 0. The MPID of the extinction coefficient is 2525. The product of the surface area and the view factor is given as 0.12, the AREA parameter (not used for this resistor subtype, but necessary as a placeholder) is given as 0.0, and the view factor distance as 84.88E+03.Subtype: 13 R26627701335721

0.0044.4Defines a gray radiative resistor between nodes 266 and 277. Although time will usually be the independent variable for material properties with this option, if temperature is the independent variable, node 266 will be used to calculate view factor or script F. The view factor has been given as 0.0 value as a place holder. The surface area is 44.4. If the independent variable is temperature for MPID 35721 it must be specified in calculation units.


Wavelength-Dependent Radiative Resistors

Type, Nodes, Subtype, MPID, Distance, 292, View factor, Area, and Wave band Definitions, 296 and Example Wavelength-Dependent Radiative Resistors, 297 describe how to input data for QTRAN’s wavelength-dependent thermal radiation resistors. These resistors account for wavelength, temperature and time dependent surface emissivities, and for wavelength, temperature, or time dependent transmissivities of participating media (e.g., optically thin gases). Thermal networks of this type can be constructed from any of the resistor subtypes described in Type, Nodes, Subtype, MPID, Distance, 292. As a result of the PATQ translation (menu pick 2) and VIEW FACTOR execution (menu pick 3), these declarations are placed in the VFRESDAT file.

To define a wavelength-dependent radiative resistor, use the following procedure.

1. Enter all data for the wave band resistor for Type, Nodes, Subtype, MPID, Distance, 292. This data identifies the resistor as a wavelength, temperature and/or time dependent thermal radiation resistor, defines the resistor’s nodal connectivity, the resistor subtype, the material property (to be used for emissivity (e), transmissivity (τ), or the extinction coefficient), and also defines the view factor distance to be used with the extinction coefficient (for resistor Subtypes 7, 8, 11 and 12 only).

2. Enter all data for the resistor for View factor, Area, and Wave band Definitions, 296. This data defines the resistor’s view factor, constant emissivity, constant transmissivity (if applicable), surface area, and wave band.

3. When all the thermal resistors are defined, place a dollar sign ($) in column 1 of the input data file and proceed to Capacitor Data, 320. To define another resistor, proceed to the resistor data section (Thermal Resistor Assignments, 276 ) that applies to the next resistor to be defined.

Subtype: 14 R36637701455721

0.0055.5Defines a gray radiative resistor between nodes 366 and 377. Although time will usually be the independent variable for material properties with this option, if temperature is the independent variable, node 366 will be used to calculate view factor or script F. The view factor has been given as 0.0 value as a place holder. The surface area of 55.5 is not used in determining the resistor value but can be specified for reference purposes. If the independent variable is temperature for MPID 55721 it must be specified in calculation units.Subtype: 15 R 444 222 0 15 123417

100316 0.2468 100416This defines a gray radiative resistor between noes 444 and 222 with form factor MPID defined as 123417. Most cases this will be 0 and the default form factor of 1.0 will be used. The emissivity on surface 1 is defined by material property ( MPID 100316), the surface area is 0.2468 units squared and the MPID for the second surface material property is 100416. This option is only available for gray body radiation.


292

The potential used for calculating the heat flow across wavelength-dependent resistors is not the usual σ

* T4 used for gray radiative resistors. Instead, the potential that is used is FRAC * σ * T4, where FRAC is a number between 0.0 and 1.0 and is a fractional multiplier that represents the amount of energy in the wave band η-1 to η-2 for which the resistor is valid. The net rate of heat from node 1 to node 2 is thus seen to be given by the following expression:

FRAC[1] is the fraction of the black-body radiation potential to be found between η-1 and η-2 at temperature T[1], and FRAC[2] is the fraction for T[2]. Strictly speaking, there is no way to incorporate the value of FRAC[1] and FRAC[2] into the R value. This has been a fairly common mistake for many users of other existing thermal programs in the past.

Type, Nodes, Subtype, MPID, Distance

ExampleW 10 20 30 2 15 23.7

This declares that a wavelength-dependent resistor is connected to nodes 10 and 20, that the transmissivity will be evaluated according to the temperature of node 30, the resistor subtype is 2, the MPID number for the resistor is 15, and the distance between surfaces is 23.7.

The following table is a brief summary of resistor node assignments.

RES -TYPE NODE1 NODE2 NODE3 SUBTYPE MFID VFDIST

Parameter DescriptionRES-TYPE A character that defines the resistor type. In this case, RES-TYPE is entered as W to

identify a wavelength and temperature or time dependent thermal radiation resistor.NODE1 Node 1 of the wavelength and temperature or time-dependent thermal radiation

resistor. For resistor Subtype 1, NODE1 should be a surface node. For Subtype 2, NODE1 should be a radiosity node. For Subtype 3, NODE1 should be a participating media node (e.g., a gas temperature node). The temperature of NODE1 is used to evaluate the temperature-dependent wave band emissivity (E) for Subtype 1.

NODE2 Node 2 of the wavelength and temperature or time-dependent thermal radiation resistor. NODE2 must be a radiosity node, participating media node, or black-body node for all of the resistor subtypes.

NODE3 Node 3 of the wavelength and temperature or time-dependent thermal radiation resistor. NODE3 is used only as a reference temperature for computing the participating media temperature-dependent wave band transmissivity (t). If input as zero, it will be set to NODE1. If a resistor subtype does not require a NODE3 value, enter a 0 for NODE3.

Q 1-->2[ ] σ * FRAC 1[ ] * T 14[ ] FRAC 2[ ] * T 2[ ]4–( )

R-----------------------------------------------------------------------------------------------------------------------------=


Table 8-2 Wavelength Dependent Radiation Resistor Node Assignments

Resistor Subtype Node 1 Node 2 Node 3

1 Non-Black Surface Radiosity N/A


3 PM Radiosity PM

4 Any Any N/A

5 Any Any N/A

6 Any Any N/A


8 PM Radiosity PM


10 PM Radiosity PM


12 PM Radiosity PM

13 Any Any N/A

14 Any Any N/A

N/A = Not applicable - no entry is necessary for Node.

PM = Participating Media - the node should be assigned participating media (e.g., participating gas) temperature node.


294

SUB-TYPE This is the resistor subtype, where:

Subtype: 1

This resistor type is used between a gray surface and a radiosity node, with an emissivity that is taken from a material property (MPID).

Subtype: 2

This resistor type is used between radiosity nodes, and with a time or temperature dependent participating media whose transmissivity is taken directly from a material property (MPID).

Subtype: 3

This resistor type is used between a radiosity node and a participating media node. The view factor is between the surface i and the gas (or other participating media node). The transmissivity of the gas (or participating media) is taken from a material property.

Subtype: 4

This resistor type may be used anywhere that material properties are constant. It would normally be used as a view factor resistor between radiosity nodes, but the F and A values are entered as simple constants and hence could be anything appropriate for a radiative resistor of this formulation. Since there is no data for transmissivity, the transmissivity of the resistor is implicitly assumed to be 1.0.

Subtype: 5

This resistor type may be used anywhere that material properties are constant. It would normally be used as a view factor resistor between two radiosity nodes, but the F value is a simple constant and hence could be anything appropriate for a radiative resistor of this formulation.

Important: This resistor type is used when a minimum of calculations are desired, thus for this type only the reciprocal of the resistance is input.

Subtype: 6

This resistor type may be used as a surface resistor, with the value given for e being the emissivity. This resistor subtype may be used anywhere the emissivity is constant. Because the emissivity is assumed to be constant, it is faster to evaluate than Subtype 1.

Subtype: 7

R 1 e–e * A----------------=

R 1F i j,[ ] * A i[ ] * τ gas[ ]----------------------------------------------------------------=

R 1F i gas,[ ] * A i[ ] * 1 τ gas[ ]–( )---------------------------------------------------------------------------------------=

R 1F i j,[ ] * A i[ ]------------------------------------=

R 1F---=

R 1 e–e * A----------------=

R 1F i j,[ ] * A i[ ] * τ gas[ ]----------------------------------------------------------------=


This resistor type is used between radiosity nodes. τ is calculated from an extinction coefficient identified by the resistors MPID and from a view factor distance. Specifically, τ[gas] = EXP(-S * P), where S is the view factor distance and P is the extinction coefficient calculated from the material property (MPID) of the resistor.

Subtype: 8

This resistor type is used between a radiosity node and a participating media node. τ is calculated from an extinction coefficient identified by the resistor’s MPID and from a view factor distance. The transmissivity value τ is calculated in the same manner as for Subtype 7 above.

Subtype: 9

This resistor type is used between radiosity nodes, and with a temperature dependent participating media whose transmissivity is taken directly from a material property (MPID). This is the same as Subtype 2, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

Subtype: 10

This resistor type is used between a radiosity node and a participating media node. The view factor is between the surface i and the gas (or other participating media node). The transmissivity of the gas (or participating media) is taken from a material property. This is the same as Subtype 3, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

Subtype: 11

This resistor type is used between radiosity nodes. τ is calculated from an extinction coefficient identified by the resistor’s MPID and from a view factor distance. Specifically, τ[gas] = EXP(-S * P), where S is the view factor distance and P is the extinction coefficient calculated from the material property (MPID) of the resistor. This is the same as Subtype 7, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

Subtype: 12

This resistor type is used between a radiosity node and a participating media node. τ is calculated from an extinction coefficient identified by the resistor’s MPID and from a view factor distance. The transmissivity value τ is calculated in the same manner as for Subtype 7. This is the same as Subtype 8, except that F[i,j] and A[i] have been combined as AF[i,j] for computational efficiency.

Subtype: 13

R 1F i gas,[ ] * A i[ ] * 1 τ gas[ ]–( )---------------------------------------------------------------------------------------=

R 1AF i j,[ ] * τ gas[ ]-----------------------------------------------=

R 1AF i gas,[ ] * 1 t gas[ ]–( )---------------------------------------------------------------------=

R 1AF i j,[ ] * t gas[ ]----------------------------------------------=

R 1AF i gas,[ ] * 1 t gas[ ]–( )---------------------------------------------------------------------=

R 1F i j,[ ] * A i[ ]------------------------------------=


296

View factor, Area, and Wave band Definitions

Example0.0 14.7 1.1 3.3

This enters a VIEW FACTOR value of 0.0, an AREA value of 14.7, a η-1 value of 1.1 microns, and a η-2 value of 3.3 microns.

This resistor type may be used between any nodes. The F[i,j] term is defined by a material property (MPID) whose independent variable is either time or the temperature of the i-th node in calculation units. This is normally used to define dynamic viewfactor and thus would couple radiation between radiosity nodes. However, if both surfaces have constant emissivities then the F term can be thought of as a script F which includes any non black characteristics. The area term is a constant for this evaluation. Since there is no data for transmissivity, the transmissivity of the resistor is implicitly assumed to be 1.0. If diagnostic output is requested the F[i,j] term is output as an emissivity value.

Subtype: 14

This resistor type may be used between any nodes. The AF[i,j] term is defined by a material property (MPID) whose independent variable is either time or the temperature of the i-th node in calculation units. This is normally used to define dynamic viewfactor and thus would couple radiation between radiosity nodes. However, if both surfaces have constant emissivities then the AF term becomes a script F which includes any non black characteristics. The area term is a constant for this evaluation. Since there is no data for transmissivity, the transmissivity of the resistor is implicitly assumed to be 1.0. If diagnostic output is requested the F[i,j] term is output as an emissivity value. Although the area term is not used, it can be specified for reference purposes and is assumed to be the area of the i-th node.

MPID This is the material property identification (MPID Number, Function Type, Temperature Scale, Factor and Label, 263 number that is used here to identify the emissivity or transmissivity of the wavelength and temperature or time-dependent radiative resistor.

VFDIST This is the View factor Distance, used for resistor Subtypes 7, 8, 11 and 12, along with the material property identified with MPID to compute a transmissivity for the resistor. For Subtypes 7, 8, 11, and 12, MPID is assumed to identify a material property that will be used as an extinction coefficient. The transmissivity Tau is then computed as τ = EXP( -VFDIST * k ), where k is the extinction coefficient calculated from an MPID.

VIEW FACTOR AREA η1 η-2

R 1AF i j,[ ]----------------------=


Example Wavelength-Dependent Radiative ResistorsThe following are examples of various wavelength-dependent radiative resistors for QTRAN.

Parameter DescriptionVIEW FACTOR

Wavelength and temperature-dependent resistor’s view factor for Subtypes 2, 3, 7, 8, 11, and 12, constant emissivity (Subtype 6), constant transmissivity (Subtype 4), reciprocal of the resistor’s value (Subtype 5), or the product of the resistor area and the view factor (Subtypes 9-12). VIEW FACTOR is ignored for resistor Subtype 1. If defining resistor Subtype 1, enter a zero for VIEW FACTOR.

AREA Surface area associated with the wavelength and temperature or time dependent thermal radiation resistor. Area should be entered as 0.0 for Subtypes 9-12.

η-1 Shortest wavelength of the wave band interval for which the wavelength and temperature or time-dependent resistor is to be used. h-1 should be entered in units of micrometers only.

η-2 Longest wavelength of the wave band interval for which the wavelength and temperature or time dependent resistor is to be used. h-2 should be entered in units of micrometers only.


298

Subtype: 1 W 11 2 0 1 102345

0.0 21.73Defines a resistor between surface node 11 and radiosity node 2. MPID 102345 will be used to calculate the temperature dependent emissivity. The view factor field is given as 0.0 and will be ignored by QTRAN (but must be there as a spacer), and the surface area is given as 21.73. The wave band is defined to lie between 0.0 and 5.0 microns.Subtype: 2 W 21 23 99 2 45

0.0124 15.78 5.0 9.8Defines a radiative resistor between radiosity nodes 21 and 23. The temperature of node 99 and MPID 45 will be used to compute the participating media transmissivity. The view factor is given as 0.0124 and the surface area for the resistor is given as 15.78. The wave band is given as 5.0 to 9.8 microns.Subtype: 3 W 14 15 14 3 88

0.01240.1870.130.89Defines radiative resistor between participating media node 14 and radiosity node 15. The transmissivity will be calculated from material property 88 using the temperature of node 14 (given as both NODE1 and NODE3 here). The view factor is given as 0.0124 and the surface area is given as 0.187. The wave band is defined to be between 0.13 and 0.89 microns.Subtype: 4 W 77 78 0 4 0

0.8923.789.81.0E+10Defines a gray radiative resistor between nodes 77 and 78. Nodes 77 and 78 may be any type of radiation network node (surface, radiosity, or participating media). The view factor value (or first constant) is given as 0.89 and the surface area (or second constant) is given as 23.78. The wave band is defined to be between 9.8 and 1.0E+10 microns.Subtype: 5 W888991050

89.760.01.28.9Defines a radiative resistor between nodes 88 and 8991. The input value is 89.76, which is the reciprocal of the resistance. The AREA value of 0.0 is entered as a required spacer between the VIEW FACTOR value and the LAMBDA-1 value. The wave band is defined to be between 1.2 and 8.9 microns.Subtype: 6 W1019060

7.890E-0123.8891.0E-011.2E+01Defines a radiative resistor between nodes 101 and 9. The constant emissivity has been given as 7.890E-01 and the surface area has been given as 23.889. The wave band has been defined to be between 1.0E-01 and 1.2E+01 microns.


Subtype: 7 W6677677890891.045E+02

0.0012385.7760.05.7Defines a radiative resistor between radiosity nodes 66 and 77. The temperature of node 67 will be used with MPID 89089 to calculate an extinction coefficient. The view factor has been given as 0.00123, the surface area as 85.776, and the view factor distance as 1.045E+02. The wave band has been defined to be between 0.0 and 5.7 microns.Subtype: 8 W65565608252584.88E+03

0.128.9E+021.28.9Defines a radiative resistor between participating media node 655 and radiosity node 656. The temperature of node 655 will be used to calculate the extinction coefficient since NODE3 was entered as 0. The MPID of the extinction coefficient is 2525. The view factor is given as 0.12, the surface area as 8.9E+02, and the view factor distance as 84.88E+03. The wave band has been defined to be between 1.2 and 8.9 microns.Subtype: 9 W212399945

0.01240.05.09.8Defines a radiative resistor between radiosity nodes 21 and 23. The temperature of node 99 and MPID 45 will be used to compute the participating media transmissivity. The area view factor product is given as 0.0124 and the AREA parameter (not used by this resistor subtype) as 0.0. The wave band is given as 5.0 to 9.8 microns.Subtype: 10 W1415141088

0.01240.00.130.89Defines a radiative resistor between participating media node 14 and radiosity node 15. The transmissivity will be calculated from material property 88 using the temperature of node 14 (given as both NODE1 and NODE3 here). The area view factor product is given as 0.0124 and the AREA parameter (not used by this resistor subtype) as 0.0. The wave band is defined to be between 0.13 and 0.89 microns.Subtype: 11 W66776711890891.045E+02

0.001230.00.05.7Defines a radiative resistor between radiosity nodes 66 and 77. The temperature of node 67 will be used with MPID 89089 to calculate an extinction coefficient. The view factor has been given as 0.00123; the AREA parameter (not used by this resistor subtype) as 0.0; and the view factor distance as 1.045E+02. The wave band has been defined to be between 0.0 and 5.7 microns.Subtype: 12 W655656012252584.88E+03

0.12084.88E+03


300

Automatic 1-D Mesh Generation

Resistor Type, Nodes, MPIDs, Subtype, and PHIDs, 301 and Mesh Geometric Parameters, 303 allow you to enter data for the 1-D conduction automatic mesh generators in QTRAN. The following procedure can be used to automatically generate a 1-D conduction mesh without using Patran.

1. Enter the information for Resistor Type, Nodes, MPIDs, Subtype, and PHIDs, 301. This section identifies the data set as a 1-D mesh generation data set, identifies the starting and ending node numbers of the mesh section and the node number increment to be used between successive nodes. This section also identifies the material properties to be used for the resistors and capacitors of the mesh section and the mesh geometry subtype (Cartesian, polar, etc.), and the phase change set (PHID set) to be used with the mesh section (if any).

2. Enter the information for Mesh Geometric Parameters, 303. This section specifies the geometric parameters of the mesh.

3. When all the thermal resistors are defined, enter a dollar sign ($) in column 1 of the input data file and proceed to Capacitor Data, 320. To define more resistors, proceed to the appropriate section (p. 276) to (p. 306) and continue entering thermal resistor data.

Defines a radiative resistor between participating media node 655 and radiosity node 656. The temperature of node 655 will be used to calculate the extinction coefficient since NODE3 was entered as 0. The MPID of the extinction coefficient is 2525. The area view factor product is given as 0.12; the AREA parameter (not used by this resistor subtype) as 0.0; and the view factor distance as 84.88E+03. The wave band has been defined to be between 1.2 and 8.9 microns.Subtype: 13 W21123101310

0.087.651.219.8Defines a radiative resistor between nodes 211 and 231. MPID 10 will be used to specify the view factor. The view factor is given as 0.0 only as a place holder and the surface area for the resistor is given as 87.65. The wave band is given as 1.2 to 91.8 microns. The temperature of node 211 will be used if the viewfactor is temperature dependent and the material property must be specified in calculation units. Time is the most probable independent variable for this subtype.Subtype: 14 W111131014100

0.033.330.21.1Defines a radiative resistor between nodes 111 and 131. MPID 100 will be used to specify the view factor area product. The view factor is given as 0.0 only as a place holder and the surface area of 33.33 is for reference only. Some value must be specified as a place holder but it is not used to define the resistor. The wave band is given as 0.2 to 1.1 microns. The temperature of node 111 will be used if the viewfactor is temperature dependent and the material property must be specified in calculation units. Time is the most probable independent variable for this subtype.


Resistor Type, Nodes, MPIDs, Subtype, and PHIDs

ExampleL 7 20 1 2 3 4 3 0

This begins a 1-D mesh generation data set between nodes 7 and 20 by increments of 1 with MPID numbers of 2, 3, and 4 for conductivity, density, and specific heat (respectively), mesh Subtype 3 (polar), and PHID of 0 (this means no phase change MPID will be assigned).

Note: This data must be input manually. It cannot be generated by Patran and PATQ. It is preferable that these declarations are placed in the QINDAT file. But they may be placed in any file that is referenced by an $INSERT FILE_NAME command in the QINDAT file inside of the resistor definition block only.

RES -TYPE NODE_1 NODE_N NODE_INC K_MPID

RHO_MPID CP_MPID SUBTYPE PHID


302

Parameter DescriptionRES-TYPE Character that defines the resistor type. In this case, RES-TYPE is entered as L to

identify a 1-D automatic mesh generation data set.NODE_1 First node, or starting node, for the 1-D automatically generated mesh section.NODE_N Last node, or ending node, for the 1-D automatically generated mesh section.NODE_INC Node number increment for the mesh and may be either positive or negative. For

example, if NODE_1 = 1 and NODE_N = 7 and NODE_INC = 2, the node numbers of the mesh will be 1, 3, 5, and 7. If NODE_1 = 10 and NODE_N = 6 and NODE_INC = -2, the node numbers will be 10, 8, and 6.

K_MPID Material property identification number for the thermal conductivity of the mesh section. See MPID Number, Function Type, Temperature Scale, Factor and Label, 263.

RHO_MPID Material property identification number for the density of the mesh section. See MPID Number, Function Type, Temperature Scale, Factor and Label, 263.

CP_MPID Material property identification number for the specific heat of the mesh section. See MPID Number, Function Type, Temperature Scale, Factor and Label, 263.

SUBTYPE Mesh subtype, where:

1. Equally-spaced Cartesian meshes, constant lengths, areas, and volumes (P1 is not used) should be entered as zero or left blank. See Mesh Geometric Parameters, 303. The first and last capacitor volumes are 1/2 of the interior capacitor volumes.

2. Geometric mesh, where each resistor length is scaled geometrically. Constant areas and geometrically scaled volumes are used.The length formula used for this mesh type is

L[n] = LENGTH * B(P1(n - 1))


Mesh Geometric Parameters

Example 1.02.03.0

This enters a value of 1.0 for LENGTH, 2.0 for AREA, 3.0 for P1.

where:

LENGTH is the spacing between the first and second node, P1 is a point packing factor, n is the number of the resistor in the one-dimensional system, and L[n] is the length of the n'th resistor.

The length of the first resistor (LENGTH) is related to the total slab length and the number of nodes to be used as follows:

LENGTH = RCLI

Important:The number of resistors is one less than the number of nodes, LSLAB is the total thickness of the slab being analyzed, and RCLI is a unit thickness which is the distance between the first two nodes, or the thickness of the first resistor which is input to QTRAN as the variable LENGTH.

3. Polar mesh.4. Spherical mesh.5. LaGrange Cubic Finite Element Cartesian mesh.

Important:The resistors generated by this technique are purely mathematical in nature and do not have a physical significance. For example, a number of the resistors generated will have negative area/length ratios that do not make any physical sense. However, they are quite correct and do yield highly accurate results (i.e., they should approach 6th order accuracy). Do not be alarmed by the generation of negative resistors whenever finite element data is transformed into resistor data. The capacitor volumes, on the other hand, should always be positive.

PHID Phase change MPID to be associated with the capacitors contained in the automatically generated mesh section. See Material Properties, 263.

LENGTH AREA P1

RCLI LSLAB * P1 1.0–( )

P1 NODES 1.0–( ) 1.0–( )----------------------------------------------------------------------------------------------------=


304

Parameter DescriptionLENGTH Distance between nodes in the mesh section. For SUBTYPE = 2, this is the distance

between the first two nodes of this mesh section where all other distances for SUBTYPE = 2 meshes are set as follows:

For SUBTYPE = 2 ONLY:

L[n] = LENGTH * P1(n - 1),

where:

L[n] is the length of the n'th resistor.The length of the first resistor (LENGTH) is related to the total slab length and the number of nodes to be used as follows:

LENGTH = RCLI

Important:The number of resistors is one less than the number of nodes, LSLAB is the total thickness of the slab being analyzed, and RCLI is a unit thickness which is the distance between the first two nodes, or the thickness of the first resistor which is input to QTRAN as the variable LENGTH.

AREA Cross-sectional area of the mesh section for SUBTYPE = 1, 2, or 5. AREA is ignored for SUBTYPE = 3 or 4. Note that Subtypes 3 and 4 assume a full cylinder or full sphere, respectively.

P1 Mesh parameter 1 (ignored for SUBTYPE = 1 or 5).

For SUBTYPE = 2, P1 is used to gradually increase the mesh spacing so that the distances between nodes and the length L(n) for the n'th resistor is:

L(n) = LENGTH * [ P1 (n - 1)

]

For SUBTYPE = 3 or 4, P1 is the radial distance between the first node of the mesh section and the origin of the cylindrical or spherical coordinate system.

When defining mesh type (SUBTYPE) 5, note that the starting and ending nodes and node number increment must be compatible with 4-node finite elements. For example, if there are N elements in the mesh section there will be N * 3+1 nodes associated with that section. Any other arrangement will cause an erroneous mesh to be generated.

RCLI LSLAB * P1 1.0–( )

P1 NODES 1.0–( ) 1.0–( )----------------------------------------------------------------------------------------------------=


Advective Resistor Data

This section describes how to define data for an advective resistor. Advective resistors are required when it is necessary to model the energy carried along with a mass stream that is entering a given capacitor’s volume. The heat flow relation is

Q[1-->2] = MASS_FLOW * Cp * (T[1] - T[2])

where the specific heat is based on the effective average value integrated between temperatures T[1] and T[2], and based on a flow of temperature step defined by CPDII5, and MASS_FLOW is the mass rate of flow. Because difference schemes for this type of calculation are generally restricted to one-sided upwind or donor cell schemes due to stability considerations, heat will be carried only to the downstream node and not to the upstream node. Node 1 is the upstream node if the mass flow rate is positive, and Node 2 is the upstream node if the mass flow rate should become negative. As a result of the PATQ translation (menu pick 2), these declarations are placed in the RESDAT file.

To add an advective resistor to the model, simply enter the resistor data as shown in the following examples. When all the thermal resistors are defined, enter a dollar sign ($) in column 1 of the input data file and proceed to Capacitor Data, 320. To define more resistors, proceed to the appropriate Section (p. 276) to (p. 306) and continue to enter thermal resistor data.

Example 1A117 2314.724

Example 1 defines an advective resistor between node 1 (upstream) and node 17 (downstream) with a specific heat evaluated according to MPID 23 and a mass flow rate given by the product of 14.7 and the value of material property 24.

Example 2A 21 23 23 15.2

Example 2 defines an advective resistor between node 21 (upstream) and node 22 (downstream) with the specific heat evaluated according to MPID 23 and with a constant mass flow rate of 15.2.

The advective resistor data items (RES-TYPE, NODE1, NODE2, CP_MPID,MASS_FLOW_CONSTANT, and MASS_FLOW_ MPID) are defined below.

RES -TYPE NODE1 NODE2 CP_MPID MASS_FLOW_CONSTANT

MASS_FLOW_MPID


306

Hydraulic Resistor DataHydraulic resistors model energy carried from one location to another like the advective resistor; however, unlike the advective resistors where the mass flow rate of the fluid is specified, a fluid network is established and solved to determine the fluid flow rates. Several types of fluid resistors can be coupled together to form the hydraulic network. The mathematical nature of these fluid resistors are explained in One Dimensional Flow Network, 213. As a result of the PATQ translation (menu pick 2), these declarations are placed in the FRESDAT file. The procedure used to define a hydraulic resistor is explained below.

1. Enter all data for the hydraulic resistor for Hydraulic Resistor Header Data, 307. This data identifies the resistor as a hydraulic resistor, defines the resistor node numbers, and defines the resistor configuration.

Parameter DescriptionRES-TYPE Character that defines the resistor type. In this case, RES_TYPE is

entered as A to identify an advective resistor.NODE1 Node 1 of the advection resistor. NODE1 is the upstream or upwind

node of the advective resistor if the mass flow rate is positive.NODE2 Node 2 of the advection resistor. NODE2 is the downstream or

downwind node of the advective resistor if the mass flow rate is positive.

CP_MPID Material property identification number for the specific heat of the mass that is flowing for this resistor. See MPID Number, Function Type, Temperature Scale, Factor and Label, 263.

MASS_FLOW_CONSTANT Constant mass rate of flow for this resistor if no MASS_FLOW_MPID is given. If a MASS_FLOW_MPID is given, this value will scale the value returned by the “material property” referenced by the MASS_FLOW_MPID.

MASS_FLOW_MPID Material property which will be used to compute a time or temperature-dependent flow rate. If no MPID is given for MASS_FLOW_MPID, the MASS_FLOW_CONSTANT is used for the flow rate. If MASS_FLOW_MPID is given, the value of the material property referenced by this MPID will be multiplied by MASS_FLOW_CONSTANT to compute a mass flow rate.

Heat is allowed to flow only from the upstream node to the downstream node in accordance with stable upwind differencing schemes. If the mass flow is specified as a negative number, the upstream and downstream nodes are reversed and heat flow will be from NODE2 to NODE1.


2. Enter the data for the resistor for Hydraulic Resistor Geometric Properties, 308. This data defines all Geometric Properties (GP) such as characteristic diameter, cross-sectional areas, and distance fluid travels etc. The number of entries is dependent on the fluid resistor type.

3. Enter all data for the Hydraulic Resistor Material Properties, 309. This data is used to identify where the material properties that are required for specific resistor configurations are to be found.

4. When all the thermal resistors are defined, place a dollar sign ($) in column 1 of the input data file and proceed to Capacitor Data, 320. To define another thermal resistor, proceed to the resistor data section (p. 276) to (p. 306) that applies to the next resistor that you wish to define.

Hydraulic Resistor Header Data

This section describes how to identify a given thermal resistor as a fluid resistor, to define its node numbers, and to specify the resistor fluid configuration.

Example 1F 1 17 3

Example 1 defines a hydraulic resistor between node 1 (upstream) and node 17 (downstream). Hydraulic configuration 3 will be used to interpret the meaning of the geometric parameters and material property ID’s specified.

Example 2F 21 22 10

Example 2 defines a hydraulic resistor between node 21 (upstream) and node 22 (downstream) with hydraulic configuration 10 used to interpret the meaning of the geometric parameters and material property IDs specified.

RES -TYPE NODE1 NODE2 FCFIG


308

Hydraulic Resistor Geometric Properties

Example24.7 23.2 0.0 14.8 29.915.6 18.9/

Parameter DescriptionRES-TYPE Character that defines the resistor type. In this case, RES_TYPE is entered as F to

identify a hydraulic resistor.NODE1 Node 1 of the hydraulic resistor. NODE1 is the upstream or upwind node of the

hydraulic resistor if the mass flow rate is positive.NODE2 Node 2 of the hydraulic resistor. NODE2 is the downstream or downwind node of

the hydraulic resistor if the mass flow rate is positive.FCFIG Fluid configuration for this hydraulic resistor. The configuration denotes the type of

fluid resistor and how the geometric properties are to be interpreted and what the material properties are to designate. Valid entries are between 1 and 12.

Table 8-3 Hydraulic Resistor FCFIG Options

FCFIG Subtype Description1 Tubing with constant physical and material properties.

2 Tubing with constant physical and material properties with friction factor evaluated by Patran Thermal Moody equation.

3 Tubing with constant physical and variable material properties.

4 Constant pump head.

5 Variable pump head.

6 Constant turbine head.

7 Variable turbine head.

8 Loss resistor or control value.

9 Check value with constant geometry and material properties.

10 Check value with constant physical and variable material properties.

11 Plenum resistor with constant properties.

12 Plenum resistor with variable material properties.

GP(1) GP(2) ... GP(n)


This enters 7 GP values of 24.7, 23.2, 0.0, 14.8, 29.9, 15.6, and 18.9, in that order using free format input.

Hydraulic Resistor Material Properties

Example1 7 4 615 23/

This declares MPID values of 1, 7, 4, 6, 15, and 23.

Hydraulic Resistor OptionsThe geometric parameters and material properties for each fluid configuration are:

FCFIG = 1, Tubing with constant physical and material properties

Parameter DescriptionGP Hydraulic resistor’s Geometric Properties such as length, diameter, cross-

sectional area, or gravitational constants. The exact meaning of each GP value varies for each configuration. QTRAN will continue reading GP values until it encounters a slash (/) in column 1 of the input data file. The procedure for entering GP values is to enter all GP values followed by an input data file line with a slash in column 1. Proceed on to Hydraulic Resistor Material Properties, 309.

When GP values at the end of the required list are zero, they need not be input. All intermediate zeroes must be included as placeholders.

MPID(1) MPID(2) ... MPID(n)

Parameter DescriptionMPID Material Property Identification numbers for the hydraulic resistors. See MPID

Number, Function Type, Temperature Scale, Factor and Label, 263. Material properties include the fluid density, viscosity, and specific heat plus other flow parameters that can be a function of time or temperature such as loss coefficients, friction factors, pump head, etc. The material properties that correspond to each MPID entry are listed for each fluid configuration option in the following option definition section. After all MPID values have been entered, simply enter a slash (/) in column one of the next line of the input data file.

When MPID values at the end of the required list are zero, they need not be input. All intermediate zeroes must be included as placeholders.


310

.

where:

• Hydraulic_Diameter is a cross-sectional area divided by the wetted perimeter. Internally a circular cross section is assumed for any calculation which relate area and diameter.

• Cross_Sectional_Area is the area that supports the flowing fluid.• Length is the total travel of the fluid within a resistor. This does not have to be equal to the

distance between the beginning and end of a resistor. One example would be a coiled tubing in which the inlet and outlet are very close but the actual distance the fluid travels is much greater than the distance between the inlet and outlet of the coil.

• DX is the displacement of NODE2 relative to NODE1 in the X global axis direction. This distance is used to determine gravitational head changes.

• DY is the displacement of NODE2 relative to NODE1 in the Y global axis direction. This distance is used to determine gravitational head changes.

• DZ is the displacement of NODE2 relative to NODE1 in the Z global axis direction. This distance is used to determine gravitational head changes.

• Density is the density of the fluid flowing. Units of specific weight are used to be consistent with the thermal solution. Internal units conversion to mass density are performed as necessary.

• Viscosity is the dynamic viscosity of the fluid.• Specific_Heat is of the fluid.• Surface_Roughness is the characteristic roughness of the tubing.• Loss_Coefficient for determining added head loss due to added flow restrictions such as

constrictions, orifices, vanes, bends, etc.• Friction_Factor is used to calculate head loss due to the viscous effect of the fluid flowing in a

tube.• Buoyancy is the gravitational head created by the temperature gradient working against a

gravitational field. Buoyancy can be modeled as the reciprocal of the compressibility factor.• There are no material properties defined.

Hydraulic_Diameter, Cross_Sectional_Area, Length,DX, DY, DZ, Density, Viscosity, Specific_Heat,Surface_Roughness, Loss_Coefficient, Friction_Factor,Buoyancy//


FCFIG = 2, Tubing with constant physical and material properties with friction factor evaluated by Patran Thermal Moody equation.

• Hydraulic_Diameter is cross-sectional area divided by the wetted perimeter. Internally a circular cross section is assumed for any calculation which relate area and diameter.








contractions, orifices, vanes, bends, etc.• Buoyancy is the gravitational head created by the temperature gradient working against a


Hydraulic_Diameter, Cross_Sectional_Area, Length,DX, DY, DZ, Density, Viscosity, Specific_Heat,Surface_Roughness, Loss_Coefficient, Buoyancy//


312

FCFIG = 3, Tubing with constant physical and variable material properties.

• Hydraulic_Diameter is the cross-sectional area divided by the wetted perimeter. Internally a circular cross section is assumed for any calculation which relate area and diameter.






• Surface_Roughness is the characteristic roughness of the tubing.• Loss_Coefficient for determining added head loss due to added flow restrictions such as

contractions, orifices, vanes, bends, etc. This value is used as a scale factor on the material property value specified by MPID_LOSS_COEFF.

• Friction_Factor is used to calculate head loss due to the viscous effect of the fluid flowing in a tube. This value is used as a scale factor on the material property value specified by MPID_F.

• MPID_RHO is the time or temperature dependent density of the fluid and is defined as a material property. Units of specific weight are used to be consistent with the thermal solution. Internal units conversion to mass density are performed as necessary.

• MPID_MU is the time or temperature-dependent viscosity of the fluid and is defined as a material property.

• MPID_CP is the time or temperature-dependent specific heat of the fluid and is defined as a material property.

• MPID_LOSS_COEFF is the time or temperature-dependent loss coefficient operating on the fluid and is defined as a material property.

Hydraulic_Diameter, Cross_Sectional_Area, Length,DX, DY, DZ, Surface_Roughness, Loss_Coefficient, Friction_Factor//MPID_RHO MPID_MU MPID_CPMPID_LOSS_COEFF MPID_BETA MPID_F/


• MPID_BETA is the time or temperature-dependent buoyancy term and is defined as a material property. It represents the gravitational head created by the temperature gradient working against a gravitational field. Buoyancy can be modeled as the reciprocal of the compressibility factor.

• MPID_F is the time or temperature-dependent friction factor used to calculate head loss due to the viscous effect of the fluid flowing in a tube and is defined as a material property. If this value is zero, it is calculated by Patran Thermal using the built-in Moody equations.

FCFIG = 4, Constant Pump Head.

where:

• Density of the fluid flowing. Units of specific weight are used to be consistent with the thermal solution. Internal units conversion to mass density are performed as necessary.

• Viscosity is the dynamic viscosity of the fluid.• Specific_Heat of the fluid.• Pump_Head - The pump head must always be positive.• There are no material properties defined.

FCFIG = 5, Variable Pump Head.

where:

• MPID_RHO is the time or temperature-dependent density of the fluid and is defined as a material property. Units of specific weight are used to be consistent with the thermal solution. Internal units conversion to mass density are performed as necessary.



• MPID_HEAD is the time or temperature-dependent head operating on the fluid and is defined as a material property. The pump head must always be positive.

Density, Viscosity, Specific_Heat,Pump_Head//

/MPID_RHO MPID_MU MPID_CPMPID_HEAD/


314

FCFIG = 6, Constant Turbine Head.

where:

• Density of the fluid flowing. Units of specific weight are used to be consistent with the thermal solution. Internal units conversion to mass density are performed as necessary.

• Viscosity is the dynamic viscosity of the fluid.• Specific_Heat of the fluid.• Turbine_Head - The turbine head must always be negative.• There are no material properties defined.

FCFIG = 7, Variable Turbine Head.

where:




• MPID_HEAD is the time or temperature-dependent head operating on a turbine by the fluid and is defined as a material property. The turbine head must always be negative.

Density, Viscosity, Specific_Heat,Turbine_Head//

/MPID_RHO MPID_MU MPID_CPMPID_HEAD/


FCFIG = 8, Loss Resistor or Control Valve.

where:

• Hydraulic_Diameter is the cross-sectional area divided by the wetted perimeter. Internally a circular cross section is assumed for any calculation which relate area and diameter. This is used as a scale factor for the variable diameter specified by MPID_DIAM.






• Surface_Roughness is the characteristic roughness of the tubing. Variable roughnesses are allowed and this entry is a scale factor used in conjunction with the material property MPID_EPS.

• Loss_Coefficient for determining added head loss due to added flow restrictions such as contractions, orifices, vanes, bends, etc. This value is used as a scale factor on the material property value specified by MPID_LOSS_COEFF.

• Friction_Factor is used to calculate head loss do to the viscous effect of the fluid flowing in a tube. This value is used as a scale factor on the material property value specified by MPID_F.


Hydraulic_Diameter, Cross_Sectional_Area, Length,DX, DY, DZ,Surface_Roughness, Loss_Coefficient, Friction_Factor/MPID_DIAMMPID_RHO MPID_MU MPID_CPMPID_EPS MPID_LOSS_COEFF MPID_BETAMPID_F/


316



• MPID_EPS is the time or temperature-dependent roughness coefficient operating on the fluid and is defined as a material property.



• MPID_F is the time or temperature-dependent friction factor used to calculate head loss due to the viscous effect of the fluid flowing in a tube and is defined as a material property. If this value is zero, it is calculated by Patran Thermal using the built-in Moody equations.

FCFIG = 9, Check Valve with Constant Geometry and Material Properties.

where:

• Hydraulic_Diameter is the cross-sectional area divided by the wetted perimeter. Internally a circular cross section is assumed for any calculation which relate area and diameter. If the fluid is not flowing from NODE1 to NODE2, the diameter of the valve is made zero, shutting off the flow.






Hydraulic_Diameter, Cross_Sectional_Area, Length,DX, DY, DZ,Density, Viscosity, Specific_Heat,Surface_Roughness, Loss_Coefficient, Buoyancy//




contractions, orifices, vanes, bends, etc.• Buoyancy is the gravitational head created by the temperature gradient working against a


FCFIG = 10, Check Valve with Constant Physical and Variable Material Properties.

where:

• Hydraulic_Diameter is the cross-sectional area divided by the wetted perimeter. Internally a circular cross section is assumed for any calculation which relate area and diameter. If the flow is not positive from NODE1 to NODE2, the diameter is reduced to zero to stop the flow through this resistor.






• Surface_Roughness is the characteristic roughness of the tubing.

Hydraulic_Diameter, Cross_Sectional_Area, Length,DX, DY, DZ,Surface_Roughness, Loss_Coefficient, Buoyancy/MPID_RHO MPID_MU MPID_CPMPID_LOSS_COEFF MPID_BETA MPID_F/


318

• Loss_Coefficient for determining added head loss due to added flow restrictions such as contractions, orifices, vanes, bends, etc. This value is used as a scale factor on the material property value specified by MPID_LOSS_COEFF.






• MPID_F is the time or temperature-dependent friction factor used to calculate head loss due to the viscous effect of the fluid flowing in a tube and is defined as a material property. If this value is zero, it is calculated by Patran Thermal using the built in Moody equations.

FCFIG = 11, Plenum Resistor with Constant Properties.

where:





• Viscosity is the dynamic viscosity of the fluid.• Specific_Heat is of the fluid.• There are no material properties defined.

DX, DY, DZ,Density, Viscosity, Specific_Heat//


FCFIG = 12, Plenum Resistor with Variable Material Properties.

where:







Example Hydraulic Resistor DefinitionsThe following is an example of a complete hydraulic resistor definition.

Example

This QTRAN input data defines a fluid configuration 3 hydraulic resistor with fluid flowing from nodes 1 to node 2. The GP values are: diameter = 0.1, cross- sectional area = 7.853983e-3, the resistor length is 10.0 which is the same as the resistor displacement in the global x axis. The resistor displacement in the y and z axis is 0.0. The tubing surface roughness is 0.0002 and the resistor has a loss coefficient scale factor of 1.0. Friction factor scale factor is not supplied and a MPID_F material property is supplied, thus

DX, DY, DZ,/MPID_RHO MPID_MU MPID_CP/

F 1 2 3 1.0000000E-01 7.8539830E-03 1.0000000E+01

1.0000000E+01 0.0000000E+00 0.0000000E+00 1.9999999E-04 1.0000000E+00 0.0000000E+00

/ 1 2 3 4 6 5 /


320

a 1.0 is implied. If the MPID_F were 0 or not supplied, the friction factor would be calculated by Patran Thermal. The MPID numbers of 1, 2, and 3 define the density, viscosity, and specific heat material properties. The loss coefficient, buoyancy, and friction factor material properties are 4, 6, and 5 respectively.

Capacitor Data

This section allows nodal capacitances (volumes and material property identification numbers (MPIDs)) for density, specific heats, and Phase Identification (PHID) data sets (see Material Properties, 263) to be assigned to individual nodes. When all of the information necessary for the thermal simulation for this section is entered, put a dollar sign ($) in column 1 of the input data file and go on to Microfunction Data, 322.

The capacitor values in this section will be placed in parallel with any capacitors generated by the automatic mesh generators. As a result of the PATQ translation (menu pick 2), these declarations are placed in the CAPDAT file.

ExampleCAP 1 23 24 15.7E-05 0

This assigns a capacitor to node 1 with a density from MPID 23, a specific heat from MPID 24, a volume of 15.7E-05, and a PHID (phase change MPID data set) of 0 (none).

CAP (keyword) NODE RHO CP VOL PHID


Parameter DescriptionNODE) Node with which the capacitance is associated.RHO) Identification number assigned to the material property that will be used for the

density of this node. See Material Properties, 263.CP Identification number assigned to the material property that will be used for the

specific heat of this node. See Material Properties, 263. VOL Volume associated with this capacitor.PHID MPID phase change data set (see Material Properties, 263) that will be used in

calculating any potential phase change effects associated with this capacitor. If no PHID set is to be assigned to this capacitor, simply enter a zero.

These five values must be entered for each nodal capacitance that is assigned, one capacitance set at a time. For example, first enter the keyword CAP followed by the values of NODE, RHO, CP, VOL, and PHID for one node, then enter another five values for the next node, and so on until all values necessary for the thermal simulation have been entered. When all values have been input, enter a dollar sign ($) in column 1 of the input data file and proceed to Boundary Conditions, 322.To perform steady-state calculations only, and if the QGLOBL global heat source of Initially Fixed Nodes, 333 is zero, ignore the nodal capacitance data because it will not be used for these calculations. Capacitance data is used only for transient calculations, or when the QGLOBL per-unit-volume global heat source is to be invoked.

If no capacitance data is assigned to a node during a transient simulation, QTRAN will assume that this node is an algebraic or arithmetic node that is always in a steady- state equilibrium with its surrounding nodes. This can be useful when implementing certain types of boundary conditions such as interfaces of material boundaries or other zero-capacitance boundary nodes.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisBoundary Conditions

322

Boundary ConditionsThis section is used to implement boundary conditions for the problem. The parameters and options controlled by boundary conditions input are listed below.

Microfunction DataThis describes how QTRAN microfunctions are defined that in turn will be used to compose QTRAN macrofunctions (macro functions are used for variable nodal heat sources and temperature controls). The procedure used for defining QTRAN microfunctions is described below:

1. Enter all microfunction data for MFID, Independent Variable, and Function Type, 323. This data defines the microfunction ID number (MFID), specifies the independent variable of the microfunction (e.g., time, temperature, Δ temperature or average temperature, or Δ radiosity), and gives the microfunction library option (see the function catalogue of Microfunction Library (Ch. 10), for available function options).

2. Enter all microfunction data for Microfunction Parameters or Data Tables, 324. This is the necessary tabular data or parameter data used with the microfunction library option to totally define the microfunction. When all of the parameter or tabular data is entered, enter a slash (/) in column one of the input data file.

3. When all of the microfunctions have been defined enter a dollar sign ($) in column one of the input data file and proceed to Heat Source/Sink Macrofunction Definition, 325. If you wish to define more microfunctions, return to Step 1 of this procedure and continue until all necessary microfunctions have been defined.

Microfunction Data (p. 322)Heat Source Macrofunction (QMACRO) Data

(p. 325)

Temperature Control Macrofunction (TMACRO) Data

(p. 327)

Mass Flow Rate Control Macrofunction (MMACRO) Data

(p. 329)

Pressure Control Macrofunction (PMACRO) Data

(p. 331)

Initially Fixed Nodes (p. 333)Nodal Classification Change (p. 334)Initial Globally Initialized Temperatures, Pressure and Heat Sources

(p. 335)

Individual Assignments of Initial Temperatures and Pressures

(p. 337)

Individual Assignments of Constant Nodal Heat Sources and Mass Flow Rates

(p. 338)

323Chapter 8: Thermal/Hydraulic Input DeckBoundary Conditions

MFID, Independent Variable, and Function Type

Example MICRO 27 0 9

This begins a microfunction data packet for MFID 27, with 0 (time) as the argument, and option 9 (Hermite table) as the function type.

Note: This data is not generated by Patran or PATQ. Use the system editor to generate this data. This data is normally put in the file MICRODAT.

MICRO(keyword) MFID ARGUMENT OPTION


324

Microfunction Parameters or Data Tables

ExampleMICDAT 1.0 2.0 3.0 15.0/

The example defines parameters P(1) to P(4) as 1.0, 2.0, 3.0, and 15.0, respectively. The / declares that this is the end of the parameter data. How the parameters are used is dependent upon the microfunction option.

Parameter DescriptionMFID Microfunction Identification number. Each microfunction must be

assigned a unique MFID number greater than zero. This MFID number will be referenced by the macrofunctions, see (p. 325) through (p. 331), in the same manner as a material property ID number (MPID) is referenced by resistors and capacitors. This referencing scheme allows the same microfunction to be used in many different macrofunctions.

ARGUMENT Identifies the microfunction independent variable as time, temperature (T), Δ T, or a radiosity difference according to the following argument code:

T[1] and T[2] are converted to absolute temperatures (i.e., Kelvin or Rankine, depending on the value of ICCALC) prior to raising them to the 4th power. This is done ONLY for ARGUMENT = 3.

OPTION Identifies the Function Library option that has been selected. For more information, consult the Microfunction Library (Ch. 10). If the Function Library option number is input as a negative number of the option number (e.g., specify option 2 as option -2), QTRAN will use the reciprocal of the function. For example, SIN(X) would be evaluated as 1/SIN(X).

MICDAT(keyword) MICDAT(1...n)

0 -- t (time)1 -- T (temperature)2 -- ΔT = T[1] - T[2] (temperature

difference)3 -- σ * (T[1]4 - T[2]4) (radiosity difference)

4 -- (average temperature)Tbar T 1[ ] T 2[ ]+( )

2-----------------------------------=


Example

This example defines tabular data for a tabular microfunction. Note that there is only one data pair per line. How the data pairs will be used is dependent upon the microfunction option.

Heat Source/Sink Macrofunction DefinitionThe following sections allow the heat source/sink macrofunctions to be defined. This is done by arithmetically combining one or more of the microfunctions defined in Microfunction Data, 322. The procedure used to define a heat source/sink macrofunction is described below.

1. Enter all data for the macrofunction. See Heat Source/Sink Macrofunction Data, 326. This information identifies the node number of the macrofunction heat source/sink input, the number of microfunctions that make up the arithmetic string, and the node number(s) whose temperature is to be used as the independent variable for any of the microfunctions that are temperature-dependent.

2. Enter all data for the macrofunction. See Building the Macrofunction from Microfunctions, 327. This information consists of identifying which microfunctions are to be combined arithmetically to form the macrofunction.

3. When all of the heat source/sink macrofunctions have been entered, enter a dollar sign ($) in column 1 of the input data file and proceed to Temperature Control Macrofunctions, 327. To define more heat source/sink macrofunctions, return to Step 1 of this procedure and continue until all heat source/sink macrofunctions have been defined.

MICDAT 0.0 22.7MICDAT 100.4 88.9MICDAT 40.8 23.9MICDAT 200.9 84.7/

Parameter DescriptionMICDAT Data that is used to define a specific microfunction. QTRAN now expects to read

parameters or tabular data pairs, depending upon the Function Library option that you selected. If parameters are input, put as many parameters on each line as desired (but at least 1). If tabular data is entered, put 2 and only 2 table entries on each line. Each line must begin with the keyword MICDAT. The data is all free format input. Linear tables require a minimum of two data pairs, whereas Hermite tables require at least three data pairs.

When all of the parameters or table data pairs have been entered, enter a slash (/) in column 1. To define more microfunctions, loop back to MFID, Independent Variable, and Function Type, 323 and continue defining microfunctions until done. When no more microfunctions are to be defined, simply enter a dollar sign ($) in column 1 and proceed on to Heat Source/Sink Macrofunction Definition, 325.


326

As many heat source/sink macrofunctions may be assigned to any node. If more than one macrofunction is assigned to a node, the node receives the summed output of the macrofunctions. Because a macrofunction consists of microfunctions that are multiplied (or divided) by each other, it is allowed to effectively add or multiply functions to arrive at the desired heat source/sink functional form. Division is also possible, because microfunctions can be defined as the reciprocal of any option contained in the Microfunction Library (Ch. 10) by placing a negative sign in front of the specified option. Microfunctions can also be effectively used as arguments of other microfunctions to specify any nodal temperature as the argument for the temperature-dependent microfunctions of a macrofunction, and to specify nodal temperatures themselves by using temperature control macrofunctions. Note that User-Coded microfunctions are yet another method of applying exotic boundary conditions. See User-Supplied Subroutines (Ch. 11).

Heat Source/Sink Macrofunction Data

Example QMACRO 1 2 1 7 23.174

The example declares that a QMACROfunction data set is being assigned to node 1, is built from 2 microfunctions, that node number 1 is the first temperature node and node number 7 is the second temperature node to be referenced for temperature-dependent microfunction arguments, and that a scale factor of 23.174 is to be applied to the QMACROfunction.

Note: QMACRO functions are normally generated by PATQ menu pick two and placed in the file QMACRODAT.

QMACRO(keyword) NODE MICRO_COUNT NODE1 NODE2 FACTOR


Building the Macrofunction from Microfunctions

Example1 5 7

The example declares that MFIDs 1, 5, and 7 will be used to form the QMACROfunction. The QMACROfunction will have already declared that there will be (3) MFIDs to read.

Temperature Control MacrofunctionsThis section allows the temperature control macrofunctions to be defined. This is done by arithmetically combining one or more of the microfunctions defined in Microfunction Data, 322. The procedure used to define a temperature control macrofunction is described below.

Parameter DescriptionNODE Node number to which the macrofunction heat source is assigned.MICRO_COUNT Number of microfunctions that will be used to construct the macrofunction.NODE1 Node number of the temperature that will be used as the T[1] independent

variable for the microfunctions, assuming the specified temperature on the microfunction input data as the independent variable. See Microfunction Data, 322. If any microfunctions are defined to be functions of D temperature or to be functions of a radiation potential difference (see MFID, Independent Variable, and Function Type, 323), NODE1 will correspond to T[1] when QTRAN computes the DT, radiation potential difference, or Tbar. If no microfunctions use temperature, D temperature, a radiation potential difference or Tbar as an independent variable, a 0 may be entered for NODE1. A 0 value for NODE1 will cause QTRAN to substitute the value of NODE for NODE1.

NODE2 Node number corresponding to T[2] of the microfunction arguments if using D T, a radiation potential difference, or Tbar as the independent variable for a microfunction. If no microfunctions use D T, radiation potential differences, or Tbar, a 0 may be entered for NODE2. A 0 value for NODE2 will cause QTRAN to substitute the value of NODE for NODE2.

FACTOR A scaling factor for the macrofunction. The value for the macrofunction will be scaled by multiplying it by FACTOR.

MFID(1...n)

Parameter DescriptionMFID(1...n) Identification numbers (MFIDs) of the microfunctions that will be used to form

the macrofunction. See Microfunction Data, 322. All microfunctions given will be multiplied and the product, scaled by factor, will be used as the macrofunction input. No keyword precedes the MFID numbers.


328

1. Enter all data for the macrofunction. See Temperature Control Macrofunction Data, 328. This information identifies the node number of the macrofunction temperature control input, the number of microfunctions that make up the arithmetic string, and the node number(s) whose temperature is to be used as the independent variable for any of the microfunctions that are temperature dependent.

2. Enter all data for the macrofunction. Construction of the Macrofunction from Microfunctions, 329. This information identifies which microfunctions are to be combined arithmetically to form the macrofunction.

3. When all of the temperature control macrofunctions have been defined, enter a dollar sign ($) in column 1 of the input data file and proceed to Mass Flow Rate Control Macrofunctions, 329. To define more temperature control macrofunctions, return to Step 1 of this procedure and continue until all temperature control macrofunctions have been defined.

As many temperature control macrofunctions as desired may be assigned to any node. If more than one macrofunction is assigned to a node, the node receives the summed output of the macrofunctions. It is allowed to effectively add or multiply microfunctions to arrive at the desired temperature control functional form because a macrofunction consists of microfunctions that are multiplied (or divided) together. Division is also possible because microfunctions can be defined as the reciprocal of any option contained in the Microfunction Library (Ch. 10), by placing a negative sign in front of the specified option. Microfunctions can also be effectively used as arguments of other microfunctions to specify any nodal temperature as the argument for the temperature-dependent microfunctions of a macrofunction, and to specify nodal temperatures themselves by using temperature control macrofunctions.

Temperature Control Macrofunction Data

Example TMACRO 1 2 1 7 23.174

The example declares that a TMACROfunction data set is being assigned to node 1, is built from 2 microfunctions, that node number 1 is the first temperature node and node number 7 is the second temperature node to be referenced for temperature-dependent microfunction arguments, and that a scale factor of 23.174 is to be applied to the TMACROfunction.

Note: This data is normally generated with PATQ menu pick 2 and placed in the file TMACRODAT.

TMACRO(keyword) NODE MICRO_COUNT NODE1 NODE2 FACTOR


Construction of the Macrofunction from Microfunctions

codeindent101 5 7

The example declares that MFIDs 1, 5, and 7 will be used to form the TMACROfunction. The TMACROfunction that uses this data will have had the MICRO_COUNT variable given as 3..

Mass Flow Rate Control MacrofunctionsThis section allows the mass flow rate control macrofunctions to be defined. This is done by arithmetically combining one or more of the microfunctions defined in Microfunction Data, 322. The procedure used to define a mass flow rate control macrofunction is described below.

Parameter DescriptionNODE Node number that the macrofunction will control.MICRO_COUNT Number of microfunctions that will be used to construct the macrofunction.NODE1 Node number of the temperature that will be used as the T[1] independent

variable for the microfunctions, assuming that the specified temperature is independent for one or more of the microfunctions used for this macrofunction. See Microfunction Data, 322. If any microfunctions are defined to be functions of DT, radiation potential difference or Tbar (see MFID, Independent Variable, and Function Type, 323, NODE1 will correspond to T[1] when QTRAN computes the DT or radiation potential difference. If no microfunctions use temperature, DT or a radiation potential difference as an independent variable, a 0 may be entered for NODE1. A 0 entered for NODE 1 will cause QTRAN to use NODE for NODE1.

NODE2 Node number corresponding to T[2] if you wish to use D T, a radiation potential difference, or Tbar as the independent variable for a microfunction. If no microfunctions use temperatures as arguments, a 0 may be entered for NODE2. A 0 entered for NODE2 will cause QTRAN to use NODE for NODE2.


MFID(1...n)


the temperature control macrofunction. See Microfunction Data, 322. All microfunctions given will be multiplied and the product, scaled by FACTOR, will be used as the macrofunction input.


330

1. Enter all data for the macrofunction. See Mass Flow Rate Control Macrofunction Data, 330. This information identifies the node number of the macrofunction mass flow rate control input, the number of microfunctions that make up the arithmetic string, and the node number(s) whose pressure is to be used as the independent variable for any of the microfunctions that are pressure dependent.

2. Enter all data for the macrofunction. See Construction of the Macrofunction from Microfunctions, 331. This information identifies which microfunctions are to be combined arithmetically to form the macrofunction.

3. When all of the mass flow rate control macrofunctions have been defined, enter a dollar sign ($) in column 1 of the input data file and proceed to Pressure Control Macrofunctions, 331. To define more mass flow rate control macrofunctions, return to Step 1 of this procedure and continue until all mass flow rate control macrofunctions have been defined.

As many mass flow rate control macrofunctions as desired may be assigned to any node. If more than one macrofunction is assigned to a node, the node receives the summed output of the macrofunctions. It is allowed to effectively add or multiply microfunctions to arrive at the desired mass flow rate control functional form because a macrofunction consists of microfunctions that are multiplied (or divided) together. Division is also possible because microfunctions can be defined as the reciprocal of any option contained in the Function Library in Section 6.2 by placing a negative sign in front of the specified option. Microfunctions can also be effectively used as arguments of other microfunctions to specify as the argument for the pressure-dependent microfunctions of a macrofunction, and to specify nodal temperatures themselves by using temperature control macrofunctions.

Mass Flow Rate Control Macrofunction Data

Example MMACRO 1 2 1 7 23.174

The example declares that a MMACROfunction data set is being assigned to node 1, is built from 2 microfunctions, that node number 1 is the first pressure node and node number 7 is the second pressure node to be referenced for pressure dependent microfunction arguments, and that a scale factor of 23.174 is to be applied to the MMACROfunction

Note: This data is normally generated with PATQ menu pick 2 and placed in the file MMACRODAT.

MMACRO(keyword) NODE MICRO_COUNT NODE1 NODE2 FACTOR


.


Example1 5 7

The example declares that MFIDs 1, 5, and 7 will be used to form the MMACROfunction. The MMACROfunction that uses this data will have had the MICRO_COUNT variable given as 3..

Pressure Control MacrofunctionsThis section allows the pressure control macrofunctions to be defined. This is done by arithmetically combining one or more of the microfunctions defined in Microfunction Data, 322. The procedure used to define a pressure control macrofunction is described below.

1. Enter all data for the macrofunction. See Pressure Control Macrofunction Data, 332. This information identifies the node number of the macrofunction pressure control input, the number of microfunctions that make up the arithmetic string, and the node number(s) whose pressure is to be used as the independent variable for any of the microfunctions that are pressure dependent.

Parameter DescriptionNODE Node number that the macrofunction will control.MICRO_COUNT Number of microfunctions that will be used to construct the macrofunction.NODE1 Node number of the pressure that will be used as the P[1] independent variable

for the microfunctions, assuming the specified pressure is independent for one or more of the microfunctions used for this macrofunction. See Microfunction Data, 322. If any microfunctions are defined to be functions of DP or Pbar (see MFID, Independent Variable, and Function Type, 323), NODE1 will correspond to P[1] when QTRAN computes the DP. If no microfunctions use pressure or DP, a 0 may be entered for NODE1. A 0 entered for NODE1 will cause QTRAN to use NODE for NODE1.

NODE2 Node number corresponding to P[2] if D P or Pbar is used as the independent variable for a microfunction. If no microfunctions use pressures as arguments, a 0 may be entered for NODE2. A 0 entered for NODE2 will cause QTRAN to use NODE for NODE2.


MFID(1...n)


the mass flow rate control macrofunction. See Microfunction Data, 322. All microfunctions given will be multiplied and the product, scaled by FACTOR, will be used as the macrofunction input.


332

2. Enter all data for the macrofunction. See Construction of the Macrofunction from Microfunctions, 333. This information identifies which microfunctions are to be combined arithmetically to form the macrofunction.

3. When all pressure control macrofunctions are defined, enter a dollar sign ($) in column one of the input data file and proceed to Initially Fixed Nodes, 333. To define more pressure control macrofunctions, return to Step 1 of this procedure and continue until all pressure control macrofunctions have been defined.

As many pressure control macrofunctions as desired may be assigned to any node. If more than one macrofunction is assigned to a node, the node receives the summed output of the macrofunctions. This allows the user to add or multiply microfunctions to arrive at the desired pressure control functional form because a macrofunction consists of microfunctions that are multiplied (or divided) together. Division is also possible because microfunctions can be defined as the reciprocal of any option contained in the Microfunction Library (Ch. 10) by placing a negative sign in front of the specified option. Microfunctions can also be effectively used as arguments of other microfunctions to specify any nodal pressure as the argument for the pressure-dependent microfunctions of a macrofunction, and to specify nodal pressures themselves by using pressure control macrofunctions.

Pressure Control Macrofunction Data

Example PMACRO 1 2 1 7 23.174

The example declares that a PMACROfunction data set is being assigned to node 1, is built from 2 microfunctions, that node number 1 is the first pressure node and node number 7 is the second pressure node to be referenced for pressure dependent microfunction arguments, and that a scale factor of 23.174 is to be applied to the PMACROfunction.

Note: This data is normally generated with PATQ menu pick two and placed in the file PMACRODAT.

PMACRO(keyword) NODE MICRO_COUNT NODE1 NODE2 FACTOR



Example1 5 7

The example declares that MFIDs 1, 5, and 7 will be used to form the PMACROfunction. The PMACROfunction that uses this data will have had the MICRO_COUNT variable given as 3.

Initially Fixed NodesThis section allows temperature and pressure nodes to be fixed (a fixed node does not change value during the simulation). To change the fixed/non-fixed classification of temperature nodes as needed see Nodal Classification Changes, 334. When all data necessary for the thermal simulation has been entered for Initially Fixed Nodes, 333, enter a dollar sign ($) in column 1 and continue on to Nodal Classification Changes, 334.

Parameter DescriptionNODE Node number that the macrofunction will control.MICRO_COUNT Number of microfunctions that will be used to construct the macrofunction.NODE1 Node number of the pressure that will be used as the P[1] independent variable

for the microfunctions, assuming the specified pressure is independent for one or more of the microfunctions used for this macrofunction. See Microfunction Data, 322. If any microfunctions are defined to be functions of DP or Pbar (see MFID, Independent Variable, and Function Type, 323), NODE1 will correspond to P[1] when QTRAN computes the DP. If no microfunctions use pressure or DP, a 0 may be entered for NODE1. A 0 entered for NODE1 will cause QTRAN to use NODE for NODE1.

NODE2 Node number corresponding to P[2] if D P or Pbar is used as the independent variable for a microfunction. If no microfunctions use pressures as arguments, a 0 may be entered for NODE2. A 0 entered for NODE2 will cause QTRAN to use NODE for NODE2.


MFID(1...n)


the pressure control macrofunction. See Microfunction Data, 322. All microfunctions given will be multiplied and the product, scaled by FACTOR, will be used as the macrofunction input.


334

Fixed Temperature Nodes

ExampleTFIX 1001

The example declares that node 1001 is a fixed node.

Fixed Pressure Nodes

ExamplePFIX 222PFIX 1001

The example declares that node 222 and 1001 are fixed pressure nodes. The same node can be fixed in both temperature and pressure. The assignment of fixed temperatures and pressures is problem-dependent and one has no requirements imposed on the other.

Nodal Classification Changes

This section allows changes to be made to the fixed/non/macrofunction controlled classification of a node. The classification of a node can be changed as many times as desired. When all data necessary for the thermal simulation has been entered for Nodal Classification Changes, 334, enter a dollar sign ($) in column 1 of the input data file and continue on to the next section.

Example CFIX 1 23.7 2

The example declares that node 1 will change classification at time 23.7 from whatever it was to CLASS = 2, TMACRO function controlled.

Important:This data is normally generated from PATQ menu pick two and placed in the file TFIXDAT for fixed temperature nodes and PFIXDAT for fixed pressure nodes.

TFIX(keyword) TFIX

Parameter DescriptionTFIX Temperature node being designated as fixed.

PFIX(keyword) PFIX

Parameter DescriptionPFIX Pressure node being designated as fixed.

CFIX(keyword) NODE TIME CLASS


Initial Globally-Assigned Temperatures, Heat Sources, Mass Flow Rate, and Variable Gravity Fields

This section allows the system’s initial temperatures pressures, mass flow rate and/or heat sources to be globally initialized for convenience only. Assign individual initial nodal temperatures (p. 337) and

Parameter DescriptionNODE Node number to which the classification change is to be made.TIME Time at which the classification change is to occur.CLASS New classification value that will be assigned to node NODE at time TIME.

Allowed CLASS values are described below.

0⎯ Nodal temperature is calculated. (This is the default value of all nodes.)

1⎯ Nodal temperature is fixed.

2⎯ Nodal temperature is to be controlled by macrofunctions. See Temperature Control Macrofunctions, 327. Changing the CLASS code to 2 is one way to turn on a temperature control macrofunction, while changing the CLASS code to any other value would cut out the macrofunction. For example, if CLASS is changed to 1, the nodal temperature would become fixed and the temperature control macrofunction would be turned off. If a temperature control macrofunction is assigned to a node in Temperature Control Macrofunctions, 327, QTRAN will automatically assign a CLASS code of 2 to the node. If necessary, this can be overridden by changing the classification of the node before the simulation start time TSTART. See Control Parameters, 236, or by initially fixing the node. See Initially Fixed Nodes, 333. Each node classification can be changed as often as desired.

Notice: This data is not generated by Patran or PATQ. Use the system editor to generate this data. Normally, this data is inserted directly into the QINDAT file.

TINITL(keyword) TINITL TSCALE

PINITL(keyword) PINITL

MPIDGH(keyword) MPIDGH MPIDGX MPIDGY MPIDGZ

MGLOBL(keyword) MGLOBL

QGLOBL(keyword) QGLOBL


336

individual constant nodal heat sources in (p. 338). Note that temperature control macrofunctions (Material Properties, 263) will normally override the TINITL data. Exceptions to this override are listed as follows:

1. The node is declared to be fixed (see Initially Fixed Nodes, 333. In this case, the value given by TINITL will be assigned to the node until such time as the node’s classification is changed via Nodal Classification Changes, 334.

2. The node has its classification changed (see Nodal Classification Changes, 334 prior to the start of the simulation so that the node is fixed (class = 1) or free (class = 0) instead of macrofunction controlled (class = 2).

Examples

The example assigns a global initial temperature of 247.5 Kelvin to all nodes, an initial pressure of all hydraulic nodes of 101325.0, and a global per-unit-volume heat source to all nodes of 0.0.

TINITL 247.5 KelvinPINITL 101325.0QGLOBL 0.0


Individual Assignments of Initial Temperatures and Pressures

Parameter DescriptionTINITL Initial temperature that is globally assigned to all nodes in the system. To define

initial temperatures that vary from node to node, see Individual Assignments of Initial Temperatures and Pressures, 337.

TSCALE Temperature scale code R, F, C, K, or blank that specifies what units TINITL is in. If blank, TINITL is assumed to be in the same temperature scale that you specified in Temperature Scale and Time Units Definition, 230 for ICCALC. TSCALE is entered on the same data line as TINITL, following TINITL. Only the first letter of TSCALE is significant.

PINITL Globally assigns an initial pressure PINITL to all the flow network nodes.MPI DGH Gravity Head material property ID which is used to define a variable gravity

head.MPIDGX Material property ID which defines the variable gravity field that is aligned with

the x-global axis.MPIDGY Material property ID which defines the variable gravity field that is aligned with

the y-global axis.MPIDGZ Material property ID which defines the variable gravity field that is aligned with

the z-global axis.MGLOBL A globally assigned mass flow rate for the hydraulic network. The mass flow rate

is calculated for the network; however, if an initial estimate of the mass flow rate is available, it should be input to speed the rate of convergence.

QGLOBL A globally applied constant heat source. This heat source will be applied to every node in the system on a per-unit-volume basis, and is additive to any macrofunction defined heat sources that you will define in Heat Source/Sink Macrofunction Definition, 325. The value entered for QGLOBL will be multiplied by the volume entered for each nodal capacitance that will be entered in Thermal Resistor Assignments, 276 (via 1-D automatic mesh generation) or Capacitor Data, 320 (capacitors) and this product will be used as a nodal heat source contribution.

Notice: QGLOBL is a PER-UNIT-VOLUME heat source, whereas the individual nodal heat sources applied by macrofunctions ((p. 325)) or constant heat sources (p. 335) are not. This data is not generated by Patran or PATQ. Use the system editor to generate this data. Normally this data is placed directly into the QINDAT file.

TEMP(keyword) NODE TEMP TSCALE

PRESS(keyword) NODE PRESS


338

This section allows initial temperatures or pressures to be assigned for individual system nodes dependent on the keyword. Specify the node number NODE and the initial temperature of the node TEMP as an ordered pair for each node until all nodes have been entered. If the TSCALE parameter is not included, the temperature is assumed to be in the units of ICCALC. Pressures are input as a data pair of node number and pressure with the keyword PRESS. When the data entry for this section has been completed, enter a dollar sign ($) in Column 1 and proceed to Individual Assignments of Constant Nodal Heat Sources and Mass Flow Rates, 338.

Example

The example assigns a temperature of 1443.7 Rankine to node number 157. A pressure of 17.43 was assigned to node 344.

Individual Assignments of Constant Nodal Heat Sources and Mass Flow Rates

This section allows constant heat sources to be assigned to individual system nodes or mass flow rates to individual hydraulic nodes. Specify the node number NODE and the constant heat source value QVALUE or mass flow rate MDVALUE for the node as an ordered pair for each node depending on the keyword until all such constant nodal data has been entered. When data entry for this section has been completed, enter a dollar sign ($) in column one and the input data file is finished. Please note that this section is used only for CONSTANT nodal heat sources. The heat sources applied by this section cannot

Important:This data is normally generated by PATQ via menu pick 2 and placed in the file TEMPDAT for temperature assignments and PRESSDAT for pressure assignments.

TEMP 157 1443.7 Rankine

PRESS 344 17.43

Parameter DescriptionNODE Node number whose temperature is to be initialized.TEMP Initial temperature being assigned for node number NODE.TSCALE Temperature scale code R, F, C, K, or blank for TEMP. If blank, TEMP is

assumed to be in the units specified by ICCALC. See Temperature Scale and Time Units Definition, 230. Only the first character of TSCALE is significant.

NODE Node number whose pressure is to be initialized.PRESS Initial pressure being assigned for node number NODE.

QBASE(keyword) NODE QVALUE

MDBASE(keyword) NODE MDVALUE


be changed or modified in any way by any other control parameters in the program (although they could be modified by user-supplied subroutines). The heat source macrofunctions should normally be used for variable heat sources. See Heat Source/Sink Macrofunction Definition, 325. For cases where constant nodal heat sources are appropriate, this section is less cumbersome to use than the heat source macrofunction section, and the CPU requirements are substantially less for this section's data. Heat sources are additive with any QMACRO function and QGLOBL heat sources that may have been applied to the same nodes.

Example

The example assigns a constant heat source of 1443.7 to node number 15 and assigns a constant mass flow rate of 0.07 to node 20..

Important:If more than one QBASE or MDBASE value is assigned to a node, the values are summed.This data is normally generated by PATQ via menu pick two and placed in the file QBASEDAT for heat source assignments and MDBASEDAT for mass flow rate assignments.

QBASE 15 1443.7

MDBASE 20 0.07

Parameter DescriptionNODE Node number which has a constant heat source applied.QVALUE The constant heat source value.NODE Node number which has a constant mass flow rate applied.MDVALUE The constant mass flow rate. Remember that specific weight is used to define

flow rates and internal units conversions are performed for the English system of units.


340

Chapter 9: Convection LibraryPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

9 Convection Library

Convection Configurations 342

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisConvection Configurations

342

Convection ConfigurationsThis section is a catalogue of various convection configurations that are available in the QTRAN program. A configuration is defined here to be a given class of convection correlations and not to be confused with Patran element configuration codes. For example, forced convection over flat plates would be one configuration, while natural convection for horizontal cylinders would be another configuration. There are 31 specific configurations and 6 generic configurations currently in the QTRAN library. There are 61 separate convection correlations that are used to support these configurations. When selecting a configuration that is applicable to a given convective resistor, QTRAN automatically selects the appropriate convection correlation for the calculated parameter range (e.g., Rayleigh number ranges, Reynolds number ranges, Prandtl number ranges). If no correlation is available for the calculated parameter range, QTRAN will select the most suitable correlation and print a warning message in the QOUTDAT file. In most cases, QTRAN will not terminate execution. However, for some correlations, such as inclined plates, an erroneous plate angle will cause program termination and an error message. Configurations are selected by specifying the configuration number for the CFIG data entry. See Convective Resistor Header Data (Ch. 8).

Most convective resistors will have only two nodes. However, some special resistors (e.g., flow through tubes) require three nodes (i.e., an upstream or entrance node, a downstream or exit node, and a wall node). These are listed explicitly as node numbers in the configuration description.

There are two classes of properties used as input for the convective resistors. The first class of properties are geometric properties (GP). These are properties which are not allowed to be temperature-dependent, and in general are properties such as characteristic lengths, areas, and inclination angles. However, other properties such as gravitational constants are also defined to be GP properties.

MPID numbers (see MPID Number, Function Type, Temperature Scale, Factor and Label (Ch. 8)) must be specified for the MPID data entry. See Convective Resistor Material Properties (Ch. 8). The MPID values identify which material properties are to be used for the resistor.

The convection Loads/BC is explained in Loads and Boundary Conditions Form, 105. The CONV template format (in the TEMPLATEDAT file) which associates the TID specified in the convection LBC, with the convection configuration (CFIG), geometric properties (GPs) and appropriate MPIDs is discussed in CONV Templates, 690.

Convection correlations are listed with each convective configuration. References for each correlation's source material are provided at the beginning of each correlation's entry.

The following parameter definitions apply to the convection correlations supplied for each convective configuration. More parameter definitions are available with some of the correlations. A listing of the available convection configurations is given below:

343Chapter 9: Convection LibraryConvection Configurations

Configuration Description 1 Forced Convection, Smooth Isothermal Tubes

2 Smooth Tubes, Constant Heat Flux, Forced Convection

3 Flat Plates, Forced Convection

4 Circular Tube in Cross Flow, Forced Convection

5 Square Tube in Cross Flow, Stagnation Point at Tube Corner, Gas Only, Forced Convection

6 Square Tube, Cross Flow, Stagnation Point at Mid-Side, Gas Only, Forced Convection

7 Hexagonal Tube, Cross Flow, Stagnation Point at Edge, Gas Only, Forced Convection

8 Hexagonal Tube, Cross Flow, Stagnation Point at Mid-Side, Gas Only, Forced Convection

9 Vertical Plate in Horizontal Flow, Gas Only, Forced Convection

10 Flow Around a Sphere, Gas Only, Forced Convection

11 Flow Around a Sphere, Oil and Water Only, Forced Convection

12 Staggered Tube Banks Consisting of Ten or More Rows, Single Phase Flow, Forced Convection

13 Isothermal Vertical, Horizontal, or Inclined Flat Plates, Natural Convection

14 Rectangular Blocks, Natural Convection

15 Horizontal Cylinders, Natural Convection

16 Sphere, Natural Convection

17 Enclosed Spaces Between Flat Plates, Natural Convection

18 Annular Space Between Concentric Spheres, Natural Convection

19 Vertical or Inclined Surface, Uniform Heat Flux, Natural Convection

20 Vertical Enclosed Space, Uniform Heat Flux, Natural Convection

21 Combined Natural and Forced Convection in Horizontal Tubes

22 Filmwise Condensation on a Vertical Surface

23 Filmwise Condensation on a Horizontal Tube

24 Pool Boiling

25 Forced Convection Through Packed Beds

26 Generic Natural Convection, H=H(TDIFF)

27 Generic Natural Convection, H=H(Gr, Pr)

28 Generic Forced Convection

29 Generic H Value, H = H(TBAR) or H(time)


344

Parameter DefinitionsTable 9-1 Symbols

30 Generic H Value, H = H(TDIFF)

31 Constant H Value

32 Rotating Disk

33 Forced Convection, Smooth Isothermal Tubes

34 Smooth Tubes, Constant Heat Flux, Turbulent Flow, Forced Convection

35 Combined Natural and Forced Convection in Horizontal Tubes

36 Forced Convection Through Packed Beds

37 Contact Resistance with an Interstitial Fluid

38 Generic Forced Convection with Variable Velocity

39 Correlation 63 Generic H Value, H = H(Tb) * GP(2)

40 Generic H Value, H = H(Tb) * GP - Ignore Area

41 Generic Forced Convection with Viscosity Correction

42 Generic Forced Convection with Temperature Correction 43 Local Flat Plate Heating, Forced Convection44-999 Reserved (not currently used)

1000+ User Supplied

Configuration Description


A = ratio of bed surface area to bed volume. See Correlation 52 Forced Convection Through a Packed Bed (Ref. 8 in Appendix A), 407 and Correlation 53 Forced Convection Through a Packed Bed (Ref. 8 in Appendix A), 408.

a = diffusivity,

As = surface area.

Cp = constant pressure specific heat.

CSF = experimental constant for Correlation 50 Filmwise Condensation on Horizontal Tube (Ref. 6 in Appendix A), 403. See Ref. 6 in Appendix A.

D = diameter.

EPSI = fluid/tube void fraction for Correlation 21 Vertical Plate in Horizontal Flow, Forced Convection (Ref. 6 in Appendix A), 366. See Ref. 6 in Appendix A.

g = gravitational constant.

Go = mass flux. See Correlation 52 Forced Convection Through a Packed Bed (Ref. 8 in Appendix A), 407 and Correlation 53 Forced Convection Through a Packed Bed (Ref. 8 in Appendix A), 408.

Gr =Grashof number,

Gz = Graetz number,

H = convective heat transfer coefficient.

Hfg = enthalpy of phase change.

k = thermal conductivity of fluid.

Ke = equivalent thermal conductivity of convective region.

L = length.

LMTD = log mean temperature difference.

μm = viscosity, usually at free-stream temperature.

kρcp---------

gβL3 Tw T∞–( )ρ2

μ2-----------------------------------------------

Re( ) Pr( ) DL----⎝ ⎠

⎛ ⎞

ΔTo ΔTL–( )

lΔToΔTL----------⎝ ⎠

⎛ ⎞--------------------------------

T3 T2–( )

lT1T2

T1 T3–------------------⎝ ⎠

⎛ ⎞--------------------------


346

μB = viscosity at fluid bulk temperature.

μf = viscosity at film temperature.

μf = viscosity of liquid.

μw = viscosity, usually at wall temperature.

Nu = Nusselt Number,

f = angle, in radians.

Pr = Prandtl number,

y = particle shape factor. See Correlation 52 Forced Convection Through a Packed Bed (Ref. 8 in Appendix A), 407 and Correlation 53 Forced Convection Through a Packed Bed (Ref. 8 in Appendix A), 408.

Ra = Rayleigh number, Gr Pr.

Re = Reynolds number,

ρv = density of liquid.

ρv = density of vapor.

S = empirical liquid constant for Correlation 50 Filmwise Condensation on Horizontal Tube (Ref. 6 in Appendix A), 403S = 1.0 for water; S = 1.7 for all other liquids.

TB = temperature of bulk fluid.

Tf = temperature of film, average of bulk and wall

Tw = temperature of wall.

ΔTo = T1 - T2

ΔTL = T1 - T3

hDk

-------

Cp μk

----------

ρVDμ

------------


Configuration 1

Forced Convection, Smooth Isothermal Tubes

Figure 9-1

Node Number 1 = tube/element inside wall temperature, .

2 = fluid entrance temperature, .

3 = fluid exit temperature, .

GP*

*GP1 is provided by Patran; GP2 and GP3 can be optionally provided in the Convection Loads/BC Convection Coefficient input databox.

.

1 = tube/element inside surface area, .

2 = distance from upstream tube/element section to the tube inlet, .

3 = distance from downstream tube/element section to the tube inlet, .

4 = tube/element inside diameter, .

5 =average fluid velocity, .

MPID 1 = fluid density, .

2 = fluid absolute viscosity, .

3 = fluid specific heat, .

4 = fluid thermal conductivity, k.

T1

T2

T3

As

x=Li

x=Lf

Di

v·

ρ

μ

cP


348

Correlations for Configuration 1

Correlation 1Smooth Tubes, Fully Developed Turbulent Flow (Ref. 6 in Appendix A)(Used for heating the fluid)

Evaluate properties at arithmetic mean bulk temperature, except for which is evaluated at the wall temperature. Use LMTD for calculation of “Q”.

Correlation 2Smooth Isothermal Tubes, Turbulent Flow (Ref. 6 in Appendix A)(Used for cooling the fluid)

Evaluate properties at arithmetic mean bulk temperature, except for μw which is evaluated at the wall temperature. Use LMTD for calculation of “Q”.

0.08 μμw-------- 40.0< <

5.E+03 < Re < 1.25E + 05

2.0 < Pr < 140.0

μW

F 1.01.82 * log10 Re( ) 1.64–( )2

------------------------------------------------------------------=

F8 F8---=

H kDi-----⎝ ⎠

⎛ ⎞ F8 * Re * Pr1.07 12.7 * F8 * Pr2 3⁄ 1.0–( )+----------------------------------------------------------------------------------------- μ

μw------⎝ ⎠

⎛ ⎞ 0.11=

Q H * As * LMTD=

0.08 μμw------ 40.0< <

5.E + 03 < Re < 1.25E + 05

2.0 < Pr < 140.0·

F 1.01.82 * log10 Re( ) 1.64–( )2

------------------------------------------------------------------=

F8 F8---=

H kDi-----⎝ ⎠

⎛ ⎞ F8 * Re * Pr1.07 12.7 * F8 * Pr2 3⁄ 1.0–( )+----------------------------------------------------------------------------------------- μ

μw------⎝ ⎠

⎛ ⎞ 0.25=

Q H * As * LMTD=


Correlation 3Smooth Isothermal Tubes, Laminar Flow (Ref. 6 in Appendix A)Re < 2000

Evaluate properties at arithmetic mean bulk temperature. Use LMTD to calculate “Q”.

Correlation 4Liquid Metals, Smooth Tubes, Turbulent Flow (Ref. 6 in Appendix A)

Use LMTD to calculate “Q”.

Correlation 5Smooth Isothermal Tubes, Turbulent Flow (Ref. 6 in Appendix A)

This equation will be used when other smooth tube, constant wall temperature correlations are out of their respective Pr and tl number ranges (i.e., 0.05 < Pr < 2.0).

Evaluate properties at mean bulk temperature, with the exception of the wall viscosity. Use LMTD to calculate “Q”.

Transitional RegionFor Reynolds numbers between 2000 and 5000, a linear interpolation between the laminar and turbulent functions is used.

H kDi-----⎝ ⎠

⎛ ⎞3.66 0.0668 *

DL---- * Re * Pr+

1.0 0.04 * DL---- * Re * Pr⎝ ⎠

⎛ ⎞ 2 3⁄+

------------------------------------------------------------------------------=

Q H * As * LMTD=

(Re * Pr) > 1000

H kDi-----⎝ ⎠

⎛ ⎞ 5.0 0.025 * Re * Pr( )0.8+( )=

Q H * As * LMTD=

H 0.027 *k

Di-----⎝ ⎠

⎛ ⎞ Re0.8* Pr1 3⁄ μ

μw------⎝ ⎠

⎛ ⎞ 0.14=

Q H * As * LMTD=


350

Configuration 2

Smooth Tubes, Constant Heat Flux, Forced Convection




GP* 1 = tube/element inside surface area, .

2 = distance from upstream tube/element section to the tube inlet, .

3 = distance from downstream tube/element section to the tube inlet, .

4 = tube/element inside diameter, .






T1

T2

T3

As

x=Li

x=Lf

Di

v

ρ

μ

cp


Figure 9-2


Correlation 6Liquid Metals, Smooth Tubes, Turbulent Flow, Constant Heat Flux (Ref. 6 in Appendix A)

Correlation 7Smooth Tubes, Turbulent Flow, Constant Heat Flux (Ref. 6 in Appendix A)

Evaluate properties at arithmetic mean bulk temperature. Use LMTD to calculate “Q”.


3.6E + 03 < Re < 9.05E + 05

1E + 02 < (Re *Pr) < 1.E + 04

H kDi-----⎝ ⎠

⎛ ⎞ * 4.82 0.0185 * Re * Pr( )0.827+( )=

Q H * As * LMTD=

(2300 < Re)

(0.05 < Pr)

F 1.01.82 * log10 Re( ) 1.64–( )2

------------------------------------------------------------------=

F8 F8---=


352

Correlation 8Smooth Tubes, Laminar Flow, Constant Heat Flux (Rohsenow & Hartnett, Handbook of Heat Transfer)

Properties are evaluated at arithmetic mean bulk temperature. The h value returned will be an integrated average of the H values along the tube length. Four sample points will be taken, and an averaging scheme analogous to Simpson’s 3/8ths rule for integration will then be used. Use the LMTD to calculate “Q”.

X1 is the distance between the upstream end of the tube section and the tube entrance. X2 is the distance between the downstream end of the tube section and the tube entrance. DXP is one third the length of the tube section being modeled.

Compute the x-value distances at four sample points. For consistency, the 4 “X” values will be stored in “XPLUS” variables, i.e. (XPLUS1, XPLUS2, XPLUS3, and XPLUS4). XPLUS1 will be the distance between the tube entrance and the upstream end of the tube section. XPLUS4 is the distance between the tube entrance and the downstream end of this tube section. XPLUS2 and XPLUS3 are spaced evenly so as to divide the tube section being modeled into thirds. Subroutine NUSLT8 will then convert these distances into the XPLUS values as used in Rohsenow and Hartnett.

XPLUS1 = X1

XPLUS4 = X2

XPLUS2 = XPLUS1 + DXP

XPLUS3 = XPLUS2 + DXP

Compute the h values at the (4) sample points along the tube length.

CALL NUSLT8(H1, K, D, XPLUS1, Re, Pr)




Use a weighted average of the H values along the tube length. The weighting scheme is that used for Simpson’s 3/8ths rule for integrating ordinary differential equations.

H kDi-----⎝ ⎠

⎛ ⎞ F8 * Re * Pr1.07 12.7 * F8 * Pr2 3⁄ 1.0–( )+-----------------------------------------------------------------------------------------=

Q H * As * LMTD=

(Re < 2300)

DXP X2 X1–( )3.0

--------------------------=

H=(H1+3.0*(H2+H3+H4)*0.125


Configuration 3

Flat Plates, Forced Convection


354

Figure 9-3


Correlation 9Flat Plate Forced Convection, Laminar Flow (Ref. 6 in Appendix A)

Reynolds number is based on plate length. Use to calculate “Q”.

Node Number 1 = plate/element surface temperature, .

2 = free-stream fluid temperature, .

GP*


1 = plate/element surface area, /element.

2 = shortest distance from the plate/element’s surface area to the plate’s leading edge, .

3 = longest distance from the plate/element’s surface area to the plate’s leading edge, .

4 =free-stream fluid velocity, .





T1

T2

As

x=Li

x=Lf

v

ρ

μ

cp

TWALL TFLUID–


Correlation 10Flat Plate Forced Convection, Turbulent Flow (Ref. 6 in Appendix A)2.0E+05 < Re < 5.5E+6

0.7 < Pr < 380.0

Use for “small” temperature differences. Reynolds number is based on plate length. Use to calculate “Q”. Properties are calculated at free stream temperature.

H kL---⎝ ⎠

⎛ ⎞ 0.664 * Re * Pr1 3⁄=

Q = H * As*B(Tw Tf )–

0.26 μμw------ 3.5< <

TWALL TFLUID–

H kL---⎝ ⎠

⎛ ⎞ 0.036 * Re0.8 * Pr0.43 17400.0–( ) 297.0 * Pr1 3⁄+( )=

Q = H * As*B(Tw Tf )–


356

Configuration 4

Circular Tube in Cross Flow, Forced Convection

Figure 9-4


Correlation 11Circular Tube in Cross Flow, Forced Convection (Ref. 6 in Appendix A)

Reynolds number based upon tube diameter. Used for both gases and liquids.

Node Number 1 = tube outside wall temperature, .

2 = fluid free-stream temperature, .

GP*


1 = tube/outside surface area, .

2 = tube/outside diameter, D.3 =

fluid free-stream velocity, .





T1

T2

As

v

ρ

μ

cp

0.4 < Re < 4.0)



Reynolds number based upon tube diameter. All properties based upon film temperature unless otherwise noted. Used for both gases and liquids.







H kD----⎝ ⎠

⎛ ⎞ 0.989 * Re0.33 * Pr1 3⁄=

Q = H * As* (Tw Tf )–

4.0 < Re < 40.0)

H kD----⎝ ⎠

⎛ ⎞ 0.911 * Re0.385 * Pr1 3⁄=

Q = H * As* (Tw Tf )–

40.0 < Re < 4000.0)

H kD----⎝ ⎠

⎛ ⎞ 0.683 * Re0.486 * Pr1 3⁄=

Q = H * As* (Tw Tf )–

4000.0 < Re < 40,000.0( )

H kD----⎝ ⎠

⎛ ⎞ 0.193 * Re0.618 * Pr1 3⁄=

Q = H * As* (Tw Tf )–

(4.0E+04< Re < 4.0E+05)

H kD----⎝ ⎠

⎛ ⎞ 0.0266 * Re0.805 * Pr1 3⁄=


358

Configuration 5

Square Tube in Cross Flow, Stagnation Point at Tube Corner, Gas Only, Forced Convection

Figure 9-5


2 = gas free-stream temperature, .

GP*


1 = tubes outside surface area, .

2 = length of square tube's diagonal, D.3 =

gas free-stream velocity, .

MPID 1 = gas density, .

2 = gas absolute viscosity, .

3 = gas specific heat, .

4 = gas thermal conductivity, k.

Q = H * As* (Tw Tf )–

T1

T2

As

v

ρ

μ

cp



Correlation 16Square Tube in Cross Flow, Stagnation Point at Corner of Tube, Forced Convection (Ref. 6 in Appendix A)(5.0E+03 < Re < 1.0E+05)

Reynolds number based on length of square’s diagonal. All properties based upon film temperature unless otherwise noted. Used for gases only.

H kD----⎝ ⎠

⎛ ⎞ 0.0246 * Re0.588 * Pr1 3⁄=

Q = H * As* (Tw Tf )–


360

Configuration 6

Square Tube, Cross Flow, Stagnation Point at Mid-Side, Gas Only, Forced Convection

Figure 9-6


Correlation 17Square Tube in Cross Flow, Stagnation Point at Mid-Side, Forced Convection (Ref. 6 in Appendix A) (5.0E+03 < Re < 1.0E+05)



GP*



2 = length of one side of tube’s square, D.3 =






T1

T2

As

v

ρ

μ

cp


Reynolds number based upon length of one side of square. All properties based upon film temperature unless otherwise noted. Used for gases only.

Configuration 7

Hexagonal Tube, Cross Flow, Stagnation Point at Edge, Gas Only, Forced Convection

Figure 9-7

Node Number 1 = tube outside tube wall temperature, .


GP*



2 = distance between parallel sides, L.3 =






H kD----⎝ ⎠

⎛ ⎞ 0.102 * Re0.675 * Pr1 3⁄=

Q = H * As* (Tw Tf )–

T1

T2

As

v

ρ

μ

cp


362


Correlation 18Hexagonal Tube in Cross Flow, Stagnation Point at Edge, Forced Convection (Ref. 6 in Appendix A)(5.0E+03 < Re < 1.0E+05)

Reynolds number based on distance between parallel sides. All properties based upon film temperature unless otherwise noted. Used for gases only.

H kL---⎝ ⎠

⎛ ⎞ 0.153 * Re0.638 * Pr1 3⁄=

Q = H * As* (Tw Tf )–


Configuration 8

Hexagonal Tube, Cross Flow, Stagnation Point at Mid-Side, Gas Only, Forced Convection

Figure 9-8



GP*



2 = distance between parallel sides, L.3 =






T1

T2

As

v

ρ

μ

cp


364


Correlation 19Hexagonal Tube in Cross Flow, Stagnation Point on One Side, Convection (Ref. 6 in Appendix A)(5.0E+03 < Re < 1.95E+04)


Correlation 20Hexagonal Tube in Cross Flow, Stagnation Point on One Side, Forced Convection (Ref. 6 in Appendix A)(1.95E+04 < Re < 1.0E+05)


H kL---⎝ ⎠

⎛ ⎞ 0.16 * Re0.638 * Pr1 3⁄=

Q = H * As* (Tw Tf )–

H kL---⎝ ⎠

⎛ ⎞ 0.0385 * Re0.782 * Pr1 3⁄=

Q = H * As* (Tw Tf )–


Configuration 9

Vertical Plate in Horizontal Flow, Gas Only, Forced Convection

Figure 9-9

Node Number 1 = plate surface temperature, .


GP*


1 = plate/element surface area, .

2 = shortest distance from element to plate’s edge, .

3 = longest distance from element to plate’s edge, .

4 =gas free-stream velocity, .





T1

T2

As

x=Li

x=Lf

v

ρ

μ

cp


366


Correlation 21Vertical Plate in Horizontal Flow, Forced Convection (Ref. 6 in Appendix A)(4.0E+03 < Re < 1.5E+04)

Reynolds number based on height of plate. All properties based upon film temperature unless otherwise noted. Used for gases only.

H kL---⎝ ⎠

⎛ ⎞ 0.228 * Re0.731 * Pr1 3⁄=

Q = H * As* (Tw Tf )–


Configuration 10

Flow Around a Sphere, Gas Only, Forced Convection

Figure 9-10


Correlation 22Flow Around a Sphere, Forced Convection (Ref. 6 in Appendix A)(17.0 < Re < 7.0E+05)

Reynolds number based upon sphere diameter. All properties based upon film temperature unless otherwise noted. Used for gases only.

Node Number 1 = sphere wall temperature, .


GP*


1 = sphere’s surface area, .

2 = sphere diameter, .

3 = gas free-stream velocity, .




T1

T2

As

Do

v

ρ

μ


368

Configuration 11

Flow Around a Sphere, Oil and Water Only, Forced Convection

Figure 9-11

Node Number 1 = sphere wall temperature, .


GP*



2 = sphere diameter, .

3 =fluid free-stream velocity, .





H kDo------⎝ ⎠

⎛ ⎞ 0.37 * Re0.6=

Q = H * As* (Tw Tf )–

T1

T2

As

Do

v

ρ

μ

cp



Correlation 23Flow Around a Sphere, Forced Convection (Ref. 6 in Appendix A)(1.0 < Re < 2.0E+05)

Reynolds number based upon sphere diameter. All properties based upon film temperature unless otherwise noted. Used for oil and water only. μw is the viscosity evaluated at the wall temperature.

H kDo------⎝ ⎠

⎛ ⎞ 1.2 0.53 * Re0.54

+( )*Pr0.3 μ

μw------⎝ ⎠

⎛ ⎞ 0.25=

Q = H * As* (Tw Tf )–


370

Configuration 12

Staggered Tube Banks Consisting of Ten or More Rows, Single Phase Flow, Forced Convection

Figure 9-12

Node Number 1 = tube wall temperatures, T.2 = fluid free-stream temperatures, .

GP*


1 = tube's elements outside surface area, .

2 = tube outside diameter, D.3 =

fluid free-stream velocity, .

4 = void fraction (area of flow with tubes divided by area of flow without tubes).MPID 1 = fluid density, .




T2

As

v

ρ

μ

cp



Correlation 24Staggered Tube Banks Consisting of Ten or More Rows, Single Phase Flow, Forced Convection (Ref. 6 in Appendix A)100.0 < Re < 1.0E+05

0.7 < Pr < 760.0

EPSI < 0.65

EPSI = void fraction (area of flow with tubes/area of flow without tubes)

UAVERAGE = average fluid velocity

Fluid properties evaluated at bulk mean temperature.

= viscosity of the fluid at the wall temperature

0.18μBULK

μw---------------- 4.3< <

Re3.0 * ρ * D * Uaverage( )

2.0 * μBULK * 1.0 EPSI–( )-----------------------------------------------------------------------=

μw

H kD----⎝ ⎠

⎛ ⎞ 0.5 * Re0.5 0.2 * Re2 3⁄+( ) * Pr1 3⁄ μ

μw------⎝ ⎠

⎛ ⎞ 0.14=

Q = H * As* (Tw Tf )–


372

Configuration 13

Isothermal Vertical, Horizontal, or Inclined Flat Plates, Natural Convection


2 = fluid temperature, .

GP* 1 = plate/element's surface area, .

2 = for vertical or inclined plates, shortest distance between the plate/element’s surface area and the plate’s edge where the boundary layer thickness is zero. For example, on a heated vertical plate exposed to a relatively cooler gas, the buoyancy driven convective flow will be upward and hence the boundary layer is of zero thickness at the plate’s bottom edge. You would then enter the shortest distance between the plate/elements area and the bottom edge of the plate, . For horizontal plates, this value is the surface area divided by the plate perimeter.

3 = ignored for horizontal plates. For vertical and inclined plates, this is the longest distance to the plate’s edge where the boundary layer thickness is zero, .

4 = plate inclination angle PHI in degrees. implies the plate is vertical. implies the plate is horizontal and facing upward. implies the plate is horizontal and facing downward.

must be between -90 and +90. The only correlation in the library for inclined plate is for the hot surfaces down or cold surfaces up.

5 =gravitational constant, .



3 = fluid coefficient of thermal expansion, .



T1

T2

As

x=Li( )

x=Lf

φ 0=

φ 90=

φ 90–=

φ

g

ρ

μ

β

cp


Figure 9-13


Correlation 25Isothermal Vertical Plates, Natural Convection (Ref. 6 in Appendix A)Ra < 1.0E+09

Rayleigh number based upon plate height.

All properties based upon film temperature.

Correlation 26Isothermal Vertical Plates, Natural Convection (Ref. 6 in Appendix A)1.E+09 < Ra

Rayleigh number based upon plate height.



H kL---⎝ ⎠

⎛ ⎞ 0.68 0.670 * Ra0.25

1.0 0.492Pr

-------------⎝ ⎠⎛ ⎞ 9 16⁄

+4 9⁄

----------------------------------------------------------+

⎝ ⎠⎜ ⎟⎜ ⎟⎜ ⎟⎛ ⎞

=

Q = H * As* (Tw Tf )–


374

Correlation 27Hot Horizontal Plate Facing Upward (or Cold Horizontal Plate Facing Downward), Natural Convection (Ref. 6 in Appendix A)2.6E+04 < Ra < 1.0E+07

L = surface area / perimeter


Correlation 28Hot Horizontal Plate Facing Upward (or Cold Horizontal Plate Facing Downward), Natural Convection (Ref. 6 in Appendix A)1.0E+07 < Ra < 3.0E+10



Correlation 29Hot Horizontal Plate Facing Downward (or Cold Horizontal Plate Facing Upward), Natural Convection (Ref. 6 in Appendix A)3.0E+05 < Ra < 3.0E+10



Correlation 30Inclined Surfaces, Natural Convection (Hot Surface Facing Downward or Cold Surface Facing Upward) (Ref. 6 in Appendix A)

H kL---⎝ ⎠

⎛ ⎞ 0.825 0.387 * Ra1 6⁄

1.0 0.492Pr

-------------⎝ ⎠⎛ ⎞ 9 16⁄

+8 27⁄

------------------------------------------------------------+

⎝ ⎠⎜ ⎟⎜ ⎟⎜ ⎟⎛ ⎞ 2

=

Q = H * As* (Tw Tf )–

H kL---⎝ ⎠

⎛ ⎞ 0.54 * Ra0.25=

Q = H * As* (Tw Tf )–

H kL---⎝ ⎠

⎛ ⎞ 0.15 * Ra1 3⁄=

Q = H * As* (Tw Tf )–

H kL---⎝ ⎠

⎛ ⎞ 0.27 * Ra0.25=

Q = H * As* (Tw Tf )–

1.0E+05 < Ra * COS(φ ) 1.0E+11<


L = plate length

= angle of plate inclination from the vertical

All properties based upon film temperature. For laminar regions, use correlations (Ref. 6 in Appendix A). Extend correlation using the vertical surface correlations (Ref. 14 in Appendix A).

Note: the first if statement below should be put with the above equation and then everything lined up and this statement deleted. I don’t know how to do that.

Configuration 14Rectangular Blocks, Natural Convection

φ

H kL---⎝ ⎠

⎛ ⎞ 0.56 Ra * cos φ( )( )0.25=

H kL---⎝ ⎠

⎛ ⎞ 0.021 Ra * cos φ( )( )0.4 if Ra * φ( )cos 3.1E9<if Ra * φ( )cos 3.1E9≥

=

Q = H * As* (Tw Tf )–


376

Figure 9-14

Node Number 1 = block surface temperature, .


GP*

*GP1 is provided by Patran.

1 = block’s surface area, .


3 = characteristic length L, where:

L = F(LH * LV,LH + LV)and:LH = the longer of the two horizontal dimensions.LV = the vertical dimension.






T1

T2

As

g

L = LH * LVLH LV+----------------------

ρ

μ

β

cp



Correlation 31Rectangular Blocks, Natural Convection (Ref. 6 in Appendix A)1.0E+04 < Ra < 1.0E+09

LH = the longer of the two horizontal dimensions.

LV = the vertical dimension.


L = LH * LVLH LV+----------------------

H = kL---⎝ ⎠

⎛ ⎞ * 0.55 * Ra0.25

Q = H * As* (Tw Tf )–


378

Configuration 15

Horizontal Cylinders, Natural Convection

Figure 9-15


Correlation 32Horizontal Cylinders, Natural Convection (Ref. 6 in Appendix A)1.0E+04 < Ra < 1.0E+09

Node Number 1 = cylinder outside surface temperature, .


GP*


1 = cylinder’s outside surface area, .


3 = cylinder outside diameter, D.MPID 1 = fluid density, .





T1

T2

As

g

ρ

μ

β

cp


D = cylinder diameter


Correlation 33Horizontal Cylinders, Natural Convection (Ref. 6 in Appendix A)1.0E+09 < Ra < 1.0E+12

D = cylinder diameter


H = kD----⎝ ⎠

⎛ ⎞ * 0.53 * Ra13---

Q = H * As* (Tw Tf )–

H = kD----⎝ ⎠

⎛ ⎞ * 0.13 * Ra1 3⁄

Q = H * As* (Tw Tf )–


380

Configuration 16

Sphere, Natural Convection

Figure 9-16


Correlation 34Sphere, Natural Convection (Ref. 6 in Appendix A)1.0E+00 < Ra < 1.0E+05

D. = sphere diameter


Node Number 1 = sphere surface temperature, .


GP*




3 = sphere diameter, D.MPID 1 = fluid density, .





T1

T2

As

g

ρ

μ

β

cp

H = kD----⎝ ⎠

⎛ ⎞ * 2.0 0.43+ * Ra0.25( )


Q = H * As* (Tw Tf )–


382

Configuration 17

Enclosed Spaces Between Flat Plates, Natural Convection

Figure 9-17

Node Number 1 = top plate, low or surface temperature, .

2 = bottom plate, upper surface temperature, .

GP*


1 = plate/element’s surface area that is exposed to the enclosed space, .

2 = enclosed space inclination angle PHI in degrees.implies that the enclosed space is horizontal.

implies that the space is vertical.


4 = length of the enclosed space, L.5 = distance between the flat plates, D.






T1

T2

As

φ 0=

φ = + or -90

g

ρ

μ

β

cp



Correlation 35Enclosed Vertical Space, Natural Convection (Ref. 2 in Appendix A)2.0E+04 < Gr < 2.0E+05

L = plate height

D = space between plates (normal distance)

Gr number based upon D

All properties based upon average of surface temperatures.

Correlation 36Enclosed Vertical Space, Natural Convection (Ref. 7 in Appendix A)2.0E+05 < Gr < 1.1E+07

L = plate height


Gr number based upon D


Correlation 37Enclosed Horizontal Space, Natural Convection, Hot Plate on Bottom, Cold Plate on Top, (Ref. 6 in Appendix A)6.0E+06 < Ra < 1.0E+08


Ra number based upon D


Definit ion : QAs----- Ke *

T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Ke 0.18 * k * Gr0.25 DL----⎝ ⎠

⎛ ⎞ 1 9⁄=


T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Ke 0.065 * k * Gr1 3⁄ DL----⎝ ⎠

⎛ ⎞ 1 9⁄=


T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Ke kD----⎝ ⎠

⎛ ⎞ 0.104 * Ra0.305 * Pr0.084=


384

Correlation 38Enclosed Horizontal Space, Natural Convection, Cold Plate on Bottom, Hot Plate on Top, (Ref. 6 in Appendix A)0 < Gr < 2000

All proprieties based upon average of surface temperatures.

Correlation 39Inclined Spaces Between Flat Plates, Natural Convection, Hot Plate on Top and Cold Plate on Bottom, (Ref. 6 in Appendix A)0.0 < φ < 90.0

1.0E+03 < Ra < 1.0E+06

2.0E+04 < Gr < 2.0E+05

= angle inclined from the horizontal.

Ra number based on D.

Gr number based on D.

D = distance between plates.

L = length of plates.

All properties based upon average of plate temperatures.

Correlation 40Inclined Spaces Between Flat Plates, Natural Convection Hot Plate on Top and Cold Plate on Bottom, (Ref. 6 in Appendix A)0.0 < Ra < 1.0E+06

2.0E+05 < Gr < 1.1E+07

= angle inclined from the horizontal.




L = length of plates.

H kD----⎝ ⎠

⎛ ⎞=

Q = H * As* (Tw Tf )–

φ


T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Ke k * 1.0 0.18 * Gr0.25 DL----⎝ ⎠

⎛ ⎞ 1 9⁄1.0–⎝ ⎠

⎛ ⎞ SIN ABS φ( )( )+=

φ


All properties based upon average of plate temperatures.


T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Ke k * 1.0 0.065 * Gr1 3⁄ DL----⎝ ⎠

⎛ ⎞ 1 9⁄1.0–⎝ ⎠

⎛ ⎞ SIN ABS φ( )( )+=


386

Configuration 18

Annular Space Between Concentric Spheres, Natural Convection

Node Number 1 = outer sphere surface temperature, .

2 = inner sphere surface temperature, .

GP* 1 = surface area, of inner diameter of larger sphere, .

2 = radius at the location of the resistor surface area.3 = gap (distance between spheres), D.4 = radius of the inner sphere, .







T1

T2

As

Ri

g

ρ

μ

β

cp


Figure 9-18


Correlation 41Annular Space Between Concentric Spheres, Natural Convection (Ref. 6 in Appendix A)1.2E+02 < Ra < 1.1E+09

0.7 < Pr < 4148.0

D = distance between spheres (difference in radii)

= outer radius =

= inner radius

= Surface Area

= Surface Heat Flex


Ro Ri D+

Ri

As

Qs


388

All properties based on average of surface temperatures.

Rag * β * D4 * ρ * T1 T2–( )

μ α Ri------------------------------------------------------------------- * D

Ri-----⎝ ⎠

⎛ ⎞=


T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Q 4 * π * Ke * Ri * Ro *T1 T2–

Ro Ri–------------------=

Ke = k * 0.228 * Ra0.226

H QsAs * T1 T2–( )------------------------------------=

Q = H * As* (T1 T2 )–


Configuration 19

Vertical or Inclined Surface, Uniform Heat Flux, Natural Convection



GP* 1 = plate/element’s surface area, .

2 = shortest distance between plate/element’s surface area and the surface edge whose boundary layer thickness is zero,

3 = longest distance between plate/element’s surface area and the surface edge whose boundary layer thickness is zero, .

4 = plate inclination angle in degrees from the horizontal. The value of must be such that 0 < < 90, inclusive.


6 = estimated applied heat flux. QTRAN will constantly update this value to reflect the actual heat flux applied to the surface. QTRAN will use your input value only as an initial guess at the heat flux. Zero is an allowed guess, q.






T1

T2

As

x=Li

x=Lf

φ φ

φ

g

ρ

μ

β

cp


390

Figure 9-19


Correlation 42Uniform Heat Flux, Vertical and Inclined Surface, Natural Convection(Ref. 6 in Appendix A)1.0E+05 < Ra < 1.0E+11

Ra number based on L.

L = plate length, in boundary layer flow direction.

= plate angle from the horizontal.

All properties based on film temperatures.

Correlation 43Uniform Heat Flux, Vertical and Inclined Surface, Natural Convection(Ref. 6 in Appendix A)2.0E+13 < Ra < 1.0E+16


φ

Ra g * β * ρ * L4 * Qk * μ * α * As

-----------------------------------------------=

H kL---⎝ ⎠

⎛ ⎞ * 0.60 * Ra * SIN φ( )[ ]0.20=

Q = H * As* (Tw Tf )–


Ra number based on L.

L = plate length, in boundary layer flow direction.

= plate angle from the horizontal.

All properties based on film temperatures.

φ

Ra g * β * ρ * L4 * Qk * μ * α * As

-----------------------------------------------=

H kL---⎝ ⎠

⎛ ⎞ * 0.568 Ra * SIN φ( )[ ]0.22=

Q = H * As* (Tw Tf )–


392

Configuration 20

Vertical Enclosed Space, Uniform Heat Flux, Natural Convection

Node Number 1 = plate 1’s surface temperature (arbitrary), .

2 = plate 2’s surface temperature (arbitrary), .

GP* 1 = plate/element’s surface area that is exposed to the enclosed space, .


3 = perpendicular distance between plates, D.4 = height of the enclosed space, .

5 = estimated applied heat flux. QTRAN will constantly update this value to reflect the actual heat flux applied to the surface. QTRAN will use your input value only as an initial guess at the heat flux q. Zero is an allowed guess.






T1

T2

As

g

Lc

ρ

μ

β

cp


Figure 9-20


Correlation 44Uniform Heat Flux, Vertical Enclosed Space, Natural Convection (Ref. 6 in Appendix A)1.0E+04 < Ra < 3.0E+06

1.0 < Pr < 2.0E+04

Lc = space height.





10.0 LcD----- 40.0< <


T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Ke k * 0.42 * Ra0.25 * Pr0.012 * DLc-----⎝ ⎠

⎛ ⎞ 0.30=


394

Correlation 45Uniform Heat Flux, Vertical Enclosed Space, Natural Convection (Ref. 6 in Appendix A)1.0E+06 < Ra < 1.0E+09

1.0 < Pr < 20.0

= space height.




1.0 LcD----- 40.0< <

Lc


T1 T2–

D------------------⎝ ⎠

⎛ ⎞=

Ke k * 0.046 * Ra1 3§=


Configuration 21

Combined Natural and Forced Convection in Horizontal Tubes




GP* 1 = tube/element’s surface area on inside of tube, .

2 = shortest distance between element’s fluid exit area and the tube inlet, .

3 = longest distance between element’s fluid exit area and the tube inlet, .



6 = tube inside diameter, D.MPID 1 = fluid density, .





T1

T2

T3

As

x=Li

x=Lf

g

v

ρ

μ

β

cp


396

Figure 9-21


Correlation 46Combined Natural and Forced Convection In Horizontal Tubes, Laminar Flow (Ref. 6 in Appendix A)


D = tube diameter.

= viscosity evaluated at fluid bulk temperature.

= viscosity evaluated at wall temperature.

All properties evaluated at film temperature.


GrRe2--------- >> 1.0

Gz Graetz number Re * Pr * DLc-----= =

μB

μw

H kD----⎝ ⎠

⎛ ⎞ *1.75 *μBμw------⎝ ⎠

⎛ ⎞0.14

* Gz 0.012 * Gz * Gr1 3⁄( )4 3⁄

+[ ]1 3⁄

=

Q = H * As* LMTD


Correlation 47Combined Natural and Forced Convection In Horizontal Tubes, Turbulent Flow (Ref. 6 in Appendix A)


D = tube diameter.

= tube length.

All properties evaluated at film temperature.

GrRe2--------- << 1.0( )

Lc

H kD----⎝ ⎠

⎛ ⎞ *4.69 * Re0.27 * Pr0.21 * Gr0.07 DLc-----⎝ ⎠

⎛ ⎞ 0.36=

Q = H * As* LMTD


398

Configuration 22

Filmwise Condensation on a Vertical Surface


2 = vapor temperature, .

GP* 1 = plate/element’s surface area, .

2 = shortest distance between plate/element’s surface area and the top edge of the vertical surface, .

3 = longest distance between plate/element’s surface area and the top edge of the vertical surface, .

4 = wetted perimeter of plate/element surface, p.5 = mass flow rate of condensate, .


7 = vapor saturation temperature, .

MPID 1 = liquid density, l

2 = vapor density,

3 = liquid absolute viscosity, l

4 = phase change enthalpy, ,

5 = liquid thermal conductivity, kl

T1

T2

As

x=Li

x=Lf

MDOT

g

Tsat

ζ

ζν

μ

hfg


Figure 9-22


Correlation 48Filmwise Condensation on Vertical Surface, Horizontal Tubes, Turbulent Flow (Ref. 6 in Appendix A)Re < 1800


Re = ρ * U * Lμ--- 4 *

MDOTP * μ---------------⎝ ⎠

⎛ ⎞=


400

Correlation 49Filmwise Condensation on Vertical Surface, Turbulent Flow (Ref. 6 in Appendix A )(1800. < Re)

Liquid density.

U Average film velocity.L

Liquid viscosity.

Mass rate of condensate flow.

P Wetted perimeter.Liquid conductivity.

Enthalpy of phase change.

Gravitational constant.

L Surface height.Vapor density.

Saturation temperature.

Wall temperature.

Liquid density.

U Average film velocity.L

Liquid viscosity.

Mass rate of condensate flow.

ρl

4 * cross-sectional areawetted perimeter

-----------------------------------------------

μ l

MDOT

k l

hfg

g

ρV

Tsat

Tw

H = 43--- * k3 *

ρ * ρ ρv–( ) * g * hfg4.0 * μ * Tsat Tw–( ) * L---------------------------------------------------------------

0.25

Q = H * As* (T1 T2 )–

Re = ρ * U * Lμ--- 4 *

MDOTP * μ---------------⎝ ⎠

⎛ ⎞=

ρl

4 * cross-sectional areawetted perimeter

-----------------------------------------------

μ l

MDOT


P Wetted perimeter.Liquid conductivity.



L Surface height.Vapor density.


Wall temperature.

k l

hfg

g

ρV

Tsat

Tw

H = 0.0077 * Re0.4 *k3 * ρ * ρ ρv–( ) * g

μ2----------------------------------------------------

1 3⁄

Q = H * As* (T1 T2 )–


402

Configuration 23

Filmwise Condensation on a Horizontal Tube

Figure 9-23

Node Number 1 = tube/element outside wall temperature, .

2 = vapor temperature, .

GP*


1 = tube/elements outside surface area .


3 = vapor saturation temperature, .

4 = tube outside diameter, .

MPID 1 = liquid density,

2 = vapor density,

3 = liquid absolute viscosity,

4 = phase change enthalpy,

5 = liquid thermal conductivity, kl

T1

T2

As

g

Tsat

Do

ρl

ρv

μl

hfg



Correlation 50Filmwise Condensation on Horizontal Tube (Ref. 6 in Appendix A)


404

Liquid conductivity.

Liquid density.

Vapor density.



Liquid viscosity.


Wall temperature.

Tube diameter.

H

Q

k l

ρl

ρV

g

hfg

μ l

Tsat

Tw

Do

0.73 *kl *ρ * ρ ρ v–( ) * g * hfg

μ * Tsat Tw–( ) * Do------------------------------------------------------------------

0.25

H * As* (T1 T2 )–


Configuration 24

Pool Boiling


Correlation 51

Node Number 1 = inside wall temperature, .


GP*


1 = liquid contact surface area, .

2 = CSF (experimental constant).

3 = S (liquid constant).S[water] = 1.0S[other liquids] = 1.7

4 = saturation temperature, .

MPID 1 = liquid specific heat, c

2 = phase change enthalpy, .

3 = liquid absolute viscosity,

4 = liquid surface tension,

5 = liquid density,

6 = vapor density,

7 = liquid thermal conductivity kl

T1

T2

As

Pool Boiling Liquid/Surface Combination Factor

Surface Combination CSFWater-Nickel 0.0060Water-Platinum 0.0130Water-Copper 0.0130Water-Brass 0.0060CC1[4]-Copper 0.0130Benzene-Chromium 0.0100n-pentane-Chromium 0.0150Ethyl alcohol-Chromium 0.0027Isopropyl alcohol-Copper 0.002535% K[2]CO[3]-Copper 0.005450% K[2]CO[3]-Copper 0.0027-butyl alcohol-Copper 0.0030

Tsat

ρl

hfs

μl

vl

ρl

ρν


406

Pool Boiling (Ref. 6 in Appendix A)

Figure 9-24

Specific heat of liquid.


CSF Experimental constant (see Ref. 6 in Appendix A).Liquid viscosity.

Surface tension at vapor-liquid interface.

S Liquid constant; 1.0 for water; 1.7 for all other liquids.Saturation temperature.

Wall temperature.

Q

DIFF

Cp l

hfg

μ l

σ

Tsat

Tw

H * A* (Tw Tsat )–

ABS(Tw Tsat )–

H = Cpl * DIFF

hfg * Prs * CSF---------------------------------------

⎝ ⎠⎜ ⎟⎛ ⎞ 3

* μl * hfg

DIFF * σ

l

ρl ρv–( )--------------------------

-------------------------------------------------

Q = H * As* B(T1 T2 )–


Configuration 25

Forced Convection Through Packed Beds

Figure 9-25


Correlation 52Forced Convection Through a Packed Bed (Ref. 8 in Appendix A)(Re < 50)

Node Number 1 = bed temperature, .



GP*

*GP1 is provided by Patran; GP2 can be optionally provided in the Convection Loads/BC Convection Coefficient input databox.

1 = bed surface area, .

2 = ratio of bed surface area to bed volume, A.3 = mass flux (mass flow/unit cross-sectional area of bed), .

4 = particle shape factor, .

MPID 1 = fluid absolute viscosity, .



T1

T2

T3

As

Go

ψ

μ

Cp


408

Correlation 53Forced Convection Through a Packed Bed (Ref. 8 in Appendix A)(Re > 50)

Fluid specific heat at bulk temperature.

Mass flux rate.

A ratio = surface area/volume of bedy Particle shape factor, as follows:

1.00 (spheres)0.91 (cylinders)0.86 (flakes)0.79 (raschig rings)0.67 (partition rings)0.80 (berl saddles)Absolute viscosity at film temperature.

Pr Prandtl number at film temperature.Re

H

Q =

Cp

Go

μFILM

Reynolds number GoA * μFILM * ψ( )

------------------------------------------=

0.91 * ψ * Cp Go

Re0.51 * Pr2 3⁄---------------------------------------------

H * As* LMTD


Configuration 26

Generic Natural Convection, H=H(TDIFF)

Fluid specific heat at bulk temperature.

Mass flux rate.

A ratio = surface area/volume of bedy Particle shape factor, as follows:

1.00 (spheres)0.91 (cylinders)0.86 (flakes)0.79 (raschig rings)0.67 (partition rings)0.80 (berl saddles)Absolute viscosity at film temperature.

Pr Prandtl number at film temperature.Re

H

Q

Node Number 1 = element surface temperature, .


GP* 1 = element’s surface area, .

2 = generic convection correlation coefficient, GP (2).3 = generic convection correlation exponent, GP (3).

MPID (Not used)

Cp

Go

μFILM

Reynolds number GoA * μFILM * ψ( )

---------------------------------------------=

0.61 * ψ * Cp Go

Re0.41 * Pr2 3⁄---------------------------------------------

H * As* LMTD

T1

T2

As


410

Figure 9-26


Correlation 54Generic Natural Convection


H=GP(2) * ABS(T1 T2)GP3–

Q = H * As* (T1 T2 )–


Configuration 27

Generic Natural Convection, H=H(Gr, Pr)

Figure 9-27



GP*


1 = element’s surface area, .


3 = characteristic length, .

4 = coefficient for convective equation, GP (4).5 = Grashoff number exponent, GP (5).6 = Prandtl number exponent, GP (6).



3 = fluid coefficient of expansion, .



T1

T2

As

g

Lc

ρ

μ

β

Cp


412


Correlation 55Generic Natural Convection

H = GP(4) * GrGP(5)*PrGP(6)

Q = H * As* (T1 T2 )–


Configuration 28

Generic Forced Convection

Figure 9-28



GP*



2 = characteristic length used for Reynolds number, .

3 =fluid free stream velocity, .

4 = coefficient for correlation, GP (4).5 = Prandtl number exponent, GP (5).6 = Reynolds number exponent, GP (6).





T1

T2

As

Lc

v

ρ

μ

Cp


414


Correlation 56Generic Forced Convection

Configuration 29

Generic H Value, H = H(TBAR) or H(time)

Figure 9-29



GP*



MPID 1 = H value (entered as a material property). This value is evaluated as a function of the average of the two nodes' temperatures. If the MPID is flagged with time as the independent variable, it will be used instead of the average temperature.

H = GP(4) * PrGP(5)*ReGP(6)

Q = H * As* (T1 T2 )–

T1

T2

As



Correlation 57Generic H Value, H = H(tbar)

Configuration 30

Generic H Value, H = H(TDIFF)

Figure 9-30


Correlation 58Generic H Value, H = H(TDIFF)



GP*



MPID 1 = H value (entered as a material property). This value is evaluated as a function of the absolute value of the temperature difference of the two nodal temperatures.

H = H TBAR( ) , TBART1 T2+( )

2-----------------------=

Q = H * As* (T1 T2 )–

T1

T2

As

H = H TDIFF( ) , TDIFF ABS T2 T1–( )=


416

Configuration 31

Constant H Value

Figure 9-31


Correlation 59Generic Constant H ValueH = GP(2)

Configuration 32

Rotating Disk



GP*



2 = constant H value.MPID (Not used)

Q = H * As* (T1 T2 )–

T1

T2

As

Q = H * As* (T1 T2 )–


Figure 9-32


Correlation 60Rotating Disk

Node Number 1 = disk element surface temperature, .


GP*



2 = element’s resistor’s surface area inner radius.3 = element’s resistor’s surface area outer radius.




4 = fluid thermal conductivity, k.5 = disk rotation speed, radians/time, .

T1

T2

As

ρ

μ

Cp

ω

r = ri ro+( ) 2⁄

V = ω * r


418

(Reynolds Number)

Pr = Cp * μ/k (Prandtl Number)

Re = ρ * V * r μ⁄

H = 0.0267 * kr--⎝ ⎠

⎛ ⎞ * Pr0.6 * Re0.8

Q2 1→ H*As* T2 T1–( )=


Configuration 33

Forced Convection, Smooth Isothermal Tubes

Figure 9-33



GP*


1 = tube/element’s inside surface area.2 = distance from upstream tube section to the tube inlet, .

3 = distance from downstream tube section to the tube inlet, .

4 = tube inner diameter, .




4 = fluid thermal conductivity, k.5 =

average fluid velocity, .

T1

T2

x Li=

x Lf=

Di

ρ

μ

Cp

v

Note: This configuration is identical to Configuration 1, 347 and its accompanying correlations, except that it requires only 2-noded resistors and uses DT instead of an LMTD.


420

Configuration 34

Smooth Tubes, Constant Heat Flux, Turbulent Flow, Forced Convection

Figure 9-34



GP*


1 = tube/element’s inside surface area, .

2 = distance from upstream tube section to the tube inlet, .


4 = tube inside diameter, .






T11

T2

As

x Li=

x Lf=

Di

ρ

μ

Cp

v



Configuration 35

Combined Natural and Forced Convection in Horizontal Tubes

Figure 9-35

Node Number 1 = tube inside wall temperature, .


GP*


1 = tube/element’s inside surface area, .

2 = distance from upstream tube section to the tube inlet, .



5 = tube inside diameter, D.MPID 1 = fluid density, .






T1

T2

As

x Li=

x Lf=

g

ρ

μ

β

Cp

v


422

Configuration 36

Forced Convection Through Packed Beds

Figure 9-36


Node Number 1 = bed temperature, .


GP*


1 = bed surface area, .

2 = ratio of bed surface area to bed volume, A.3 = particle shape factor, .

MPID 1 = fluid absolute viscosity, .


3 = fluid thermal conductivity, k.4 = mass flux (mass flow/unit cross-sectional area of bed), .

T1

T2

As

ψ

μ

Cp

Go

Note: This configuration is identical to Configuration 25, 407 and its accompanying correlations, except that it requires only 2-noded resistors and uses DT instead of an LMTD. In addition, this configuration allows the mass flux to be a variable rather than a constant as is the case with Configuration 25, 407.


Configuration 37

Contact Resistance with an Interstitial Fluid


Correlation 61Contact Resistance

Configuration 37 originally was based on Ref. 12 in Appendix A. With Version 8, the correlation has been redone based on the original work defined in Ref. 13 in Appendix A. The ability to input fluid pressure was added to the correlation.

This correlation which defined the total conductance between two surfaces is assumed to be the sum of two mutually independent conductances-the component through the interstitial fluid and that through the contacting area.

These are dependent on the contact area and equivalent fluid thicknesses which in correlation are correlated to fluid characteristics and material properties.

Node Number 1 = surface temperature of surface 1, .

2 = surface temperature of surface 2, .

GP*


1 = element’s surface area, A.2 = rms roughness (meters) of surface ,

3 = rms roughness (meters) of surface ,

4 = mean free path at 15 and 1 atm, .

5 = temperature jump ratio

6 = scale factor (usually 1.0), F.MPID 1 = interstitial fluid thermal conductivity

2 = thermal conductivity surface #1

3 = thermal conductivity surface #2

4 = contact pressure (Pascals), .

5 = strength of surface #1 or surface #2, whichever is softest (Pascals), .

6 = fluid pressure, (Pascals), .

T1

T2

T1 σ1

T2 σ2

°C Λ0

2 lΛ0------

wm K–-------------- , kf .

wm K–-------------- , k1 .

wm K–-------------- , k2 .

Pc

σs

pf

hc hf hm+=


424

The fluid conductance is defined by its conductance and the fluid equivalent thickness.

where:

Data has been correlated over a wide range by the following expression:

where the dimensionless quantities are defined:

where:

It is often difficult to pinpoint a value for the accommodation coefficient and this reference provides a table for some gases. It should be noted that the mean free paths quoted in this reference are at best 50% higher than many other references, but are provided to be consistent with the reference the correlation was developed in.

Fluid thermal conductivity.

Equivalent fluid thickness.

the maximum distance between surfaces and as a first approximation can be taken as twice the mean roughness of each surface.

l temperature jump distance and based on molecular-kinetic concepts and is defined:

where a = accommodation coefficient and = fluid molecules’ mean free path.

hfkfδe-----=

kf

δe

Y = 103

------ 10X------ 4

X--- 4 1

X3------ 3

X2------ 2

X---+ +⎝ ⎠

⎛ ⎞ ln 1 X+( )–+ +

Yδmaxδe

----------=

Xδmax2 l

----------=

δmax

δmax 2 σ1 σ2+( )

l 2 a–a

------------⎝ ⎠⎛ ⎞=

2Pr-----⎝ ⎠

⎛ ⎞ Cp Cv⁄Cp Cv 1+( )⁄--------------------------------⎝ ⎠

⎛ ⎞ Λ

Λ


The mean free path is directly proportional to absolute temperature and inversely proportional to pressure. The corrections for actual conditions is adjusted with the following relation:

where all the reference values are related to 15 and 1 atmosphere. All fluid material properties are evaluated at the average temperature of the surface nodes. Appropriate adjustment in the temperature from the internal calculation units to units consistent with the correlation are done automatically; however, all quantities must be in SI units

= 288.15 K

= 101325 Pa

The second part of the conductance is that through the material which is in contact. This is dependent on the contact pressure and material strength to define the effective area of conductance. The correlation for this term is

This equation is valid for relative contact pressure to strength ratios in the order of 0.025 and temperatures below 0.3 of the fusion point. For higher or prolonged loads at elevated temperatures, creep must be considered which increases the interface conductance.

The coefficient C is a function of the rms roughness of each surface.

Table 9-2 Gas Constants at 15oC and 760 TorrGas a 2l/Air 0.83 9.6 x 10-8 4.6Hydrogen 0.20 16.0 x 10-8 22.1Helium 0.38 28.5 x 10-8 14.8Argon 0.85 10.0 x 10-8 5.1

P contact pressure, Pascals, .

strength of the softest material, Pascals, .

effective thermal conductivity of the material combination.

Λ0 m Λ0

Λ ΛoTTo------⎝ ⎠

⎛ ⎞ PoPf-----⎝ ⎠

⎛ ⎞=

°C

To

Po

hm 8000kmC Pc3 σs-----------⎝ ⎠

⎛ ⎞0.86

=

Pa

σs Pa

km

km 2 * k1 * k2k1 k2+

----------------------------


426

The final conductance involves a scale factor which can provide desired adjustments due to additional knowledge about the surfaces or for units adjustment because some aspects of the correlation are dependent on the SI unit’s system.

The resultant heat transfer is

where the area is equated based on the geometric node where the contact coupling is applied.

C = 1.0 if >

if < <

if <

σ1 σ2+( ) 30 10 6–×

C 30 10 6–×σ1 σ2+

-----------------------⎝ ⎠⎜ ⎟⎛ ⎞

1 3⁄

=10 10 6–× σ1 σ2+( ) 30 10 6–×

C 14.42 10 6–×= σ1 σ2+( ) 10 10 6–×

Note: The 14.42 is an adjustment from what was defined in the reference in order to provide a continuous function.

h hc * F=

Q1 2⇒ h * A * T1 T2–( )=


Configuration 38

Generic Forced Convection with Variable Velocity

Figure 9-37



GP*





4 = coefficient for correlation, GP (4).5 = Prandtl number exponent, GP (5).6 = Reynolds number exponent, GP (6).




4 = fluid thermal conductivity, k.5 = fluid velocity, variable dependence.

T1

T2

As

Lc

v

ρ

μ

Cp


428


Correlation 62Generic Forced Convection with Variable Velocity

Fluid velocity is the product of GP(2) and MPID(5) evaluation. The independent variable for velocity evaluation is either the bulk fluid temperature or time.

H = k / Lc * GP(4) * PrGP(5) * ReGP(6)

Configuration 39

Generic H Value, H = H(Tb) * GP

Figure 9-38



GP*



2 = Heat Transfer Coefficient Scale factor.MPID 1 = Heat Transfer Coefficient Variable Definition.

Q H * As* T1 T– 2( )=

T1

T2

As



Correlation 63Generic H Value, H = H(Tb) * GP(2)

Heat transfer coefficient is the product of GP(2) and MPID(1) evaluation. The independent variable for the variable evaluation is either the bulk fluid temperature or time.

H = H(Tb) * GP(2)

Configuration 40

Generic H Value, H = H(Tb) * GP - Ignore Area

Figure 9-39



GP*



2 = Heat Transfer Coefficient Scale factor.MPID 1 = Heat Transfer Coefficient Variable Definition.

Q H * As* T1 T– 2( )=

T1

T2

As


430


Correlation 63Generic H Value, H = H(Tb) * GP(2)

Heat transfer coefficient is the product of GP(2) and MPID(1) evaluation. The independent variable for the variable evaluation is either the bulk fluid temperature or time. Although the surface area is defined, it is not used to determine the heat flux.

H = H(Tb) * GP(2)

Q H * T1 T– 2( )=


Configuration 41

Generic Forced Convection with Viscosity Correction



GP*





4 = coefficient for correlation, GP (4).5 = Prandtl number exponent, GP (5).6 = Reynolds number exponent, GP (6).7 = Viscosity Exponent if heating fluid, GP(7).8 = Viscosity Exponent if cooling fluid, GP(8).




4 = fluid thermal conductivity, k.5 = fluid velocity, variable dependence

T1

T2

As

Lc

v

ρ

μ

Cp


432

Figure 9-40


Correlation 64Generic Forced Convection with Viscosity Correction when Heating fluid.


Correlation 65Generic Forced Convection with Viscosity Correction when Cooling fluid.


H = k/Lc * GP(4) * PrGP(5)* ReGP(6)* μB μw⁄( )GP(7)

Q H * As* T1 T– 2( )=

H = k/Lc * GP(4) * PrGP(5)* ReGP(6)* μB μw⁄( )GP(8)

Q H * As* T1 T– 2( )=


Configuration 42

Generic Forced Convection with Temperature Correction



GP*





4 = coefficient for correlation, GP (4).5 = Prandtl number exponent, GP (5).6 = Reynolds number exponent, GP (6).7 = Temperature Exponent if heating fluid, GP(7).8 = Temperature Exponent if cooling fluid, GP(8).




4 = fluid thermal conductivity, k.5 = fluid velocity, variable dependence.

T1

T2

As

Lc

v

ρ

μ

Cp


434

Figure 9-41


Correlation 66Generic Forced Convection with Temperature Correction when Heating fluid.


Correlation 67Generic Forced Convection with Viscosity Correction when Cooling fluid.


H = k / Lc * GP 4( ) * PrGP 5( ) * ReGP 6( ) * TwTb--------⎝ ⎠

⎛ ⎞ GP 7( )

Q H * As* T1 T– 2( )=

H = k / Lc * GP 4( ) * PrGP 5( ) * ReGP 6( ) * TwTb--------⎝ ⎠

⎛ ⎞ GP 8( )

Q H * As* T1 T– 2( )=


Configuration 43

Local Flat Plates, Forced Convection

Figure 9-42

Velocity is the product of velocity scale factor and the variable velocity material property. All temperature dependent material properties are evaluated at the film temperature.

Correlations for Configuration 43Local Flat Plate Forced Convection, Laminar Flow


2 = free-stream fluid temperature, .

GP*


1 = plate/element surface area, /element.

2 = distance to the plate’s leading edge, .

3 = free-stream fluid velocity, x=L scale factor.MPID 1 = fluid density, .



4 = fluid thermal conductivity, k.5 = variable fluid velocity.

T1

T2

As

x=Li

ρ

μ

cp


436

Correlation 68 (Ref. 11 in Appendix A)



All other cases, but valid for

Local Flat Plate Forced Convection, Turbulent Flow



If Reynolds number between laminar and turbulent limits, a linear interpolation between the laminar and turbulent values is used.

Re 2.0 E 5+<

Pr 0.05<

H kL---⎝ ⎠

⎛ ⎞ * 0.565 * Re * Pr=

0.6 Pr 50.0<<

H kL---⎝ ⎠

⎛ ⎞ * 0.332 * Re * Pr1 3⁄=

Re * Pr 100>

H kL---⎝ ⎠

⎛ ⎞ 0.338 * Re * Pr1 3⁄

1 0.0468Pr

----------------+⎝ ⎠⎛ ⎞ 2 3⁄ 1 4⁄

------------------------------------------------------

⎩ ⎭⎪ ⎪⎨ ⎬⎪ ⎪⎧ ⎫

=

Re 5.0 E 5+>

5.0 E 5 Re 1.0E7<<+

Cf 0.0592 Re 1 5⁄–=

Re 107>

Cf0.37

log10Re( )2.584-----------------------------------=

H kL---⎝ ⎠

⎛ ⎞12--- * Cf * Re * Pr

1.0 5 12--- * Cf Pr 1.0–( ) 1n 1.0 5

6--- Pr 1–( )++

⎩ ⎭⎨ ⎬⎧ ⎫

+

----------------------------------------------------------------------------------------------------------------------------------⋅=


Configurations 44-999

Reserved (not currently used)These configuration numbers are reserved for future expansion of the QTRAN convection correlation library.

Configurations 1000+

User SuppliedThese configuration numbers are reserved for User-Coded convection configurations that may be incorporated into subroutine UHVAL. The calling sequence for UHVAL is as follows:

SUBROUTINE UHVAL (ICFIG, IRESIS, COEFF, EXPO, MPID, GP, T1, T2, GVALH, Q, LOGP, J1, J2, J3, J4, J6)

An example UHVAL subroutine is included in the QTRAN package with excellent internal documentation. Refer to it before attempting to write your own.

The arguments for UHVAL are defined as follows:

Q H * As * T1 T2–( )=


438

:

Values Passed to the User

Values Passed by You, Required by QTRAN

INTEGER ICFIG, IRESIS, MPID, J1, J2, J3, J4, J6LOGICAL LOGPREAL*8 COEFF, EXPO,GP, T1, T2, GVALH, Q

ICFIG Configuration type (CFIG value). This value will always come to be as 1000 or greater. Use the ICFIG integer to choose between one or more of the convection configurations.

IRESIS The convective resistor number whose heat flow is being calculated. This integer is used to point into the correct row of the GP and MPID arrays.

COEFF Material Property Data.EXPO Material Property Data.MPID MPIDs assigned by the user to the convective resistor.GP Geometric Property data assigned by the user to the convective resistor.T1 Temperature of node 1.T2 Temperature of node 2.LOGP If LOGP = .TRUE., the routine is being called to dump any resistor data to the output

file.J1-J4, J6 Dimensions for the COEFF, EXPO, MPID and GP arrays.

GVALH The “conductance” of the resistor, equal to the product of the h value and the resistor area.

Q Heat flow from node 1 to node 2 through the resistor.

Chapter 10: Microfunction LibraryPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

10 Microfunction Library

Microfunction Library 440

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisMicrofunction Library

440

Microfunction LibraryThe following is a catalogue of the microfunctions that are available in the QTRAN Microfunction Library, as well as an explanation of the various input parameters which are required for each microfunction. Briefly, the microfunctions which are available are:

1. Constant2. Power Series3. Sine Wave4. Square Wave5. Step6. Ramp7. Exponential8. Linear Interpolation of a User-Input Data Table9. Hermite Polynomial Interpolation of a User-Input Data Table, with Quadratic Interpolation

Etrapolation at the Data Table End-Points10. Repeating Waveform: Linearly Interpolated Data Table11. Repeating Waveform: Hermite Polynomial Interpolated Data Table12. Natural Logarithm13. Base 10 Logarithm14. Blackbody Radiation (this function determines the fraction of blackbody radiant energy that lies

between two wavelengths)15. Flip/Flop16. Dead Band (this function allows for hysteresis effects)17. Straight Line18. Indexed Linear Interpolation of a User-Input Data Table19. Indexed Hermite Polynomial Interpolation of a User-Input Data Table, with Quadratic

Interpolation/Extrapolation at the Data Table End-Points20. Indexed Repeating Waveform: Linearly Interpolated Data Table21. Indexed Repeating Waveform: Hermite Polynomial Interpolated Data Table

22.Repeating Flip/Flop23-999 Reserved for Future Use (not currently implemented)1000+ User-Coded (a function defined by a user-supplied subroutine UMICRO)

The variable X that is referred to in the following function explanations refers to the independent variable that you specify. As described in Microfunction Data, 322, the independent variable may be either the current time value, the temperature value of any node, the temperature difference between any two nodes, a radiosity difference, or the average temperature of any two nodes.

441Chapter 10: Microfunction LibraryMicrofunction Library

Microfunction Format

MFID, Independent Variable, and Function Type

Example MICRO2709

This begins a microfunction data packet for MFID 27, with 0 (time) as the independent argument, and option 9 (Hermite table) as the function type.

MICRO(keyword) MFID ARGUMENT OPTION

Parameter DescriptionMFID The MicroFunction Identification number. Each microfunction must be assigned

a unique MFID number greater than zero. This MFID number will be referenced by the macrofunctions on (p. 325) through (p. 331) in the same manner as a material property ID number (MPID) is referenced by resistors and capacitors. This referencing scheme allows the same microfunction to be used in many different macrofunctions.

ARGUMENT Identifies the microfunction independent variable as time, temperature (T), D T, radiosity difference or an average temperature according to the following argument code:0--t(time)

1--T(temperature)

2--

3--

Notice: and are converted to absolute temperatures (i.e., Kelvin or Rankine, depending on the value of ICCALC) prior to raising them to the 4th power. This is done ONLY for ARGUMENT = 3.

4-- (average temperature)

OPTION Identifies the Function Library option that has been selected. For more information, consult the Function Library in Microfunction Options, 442. If the Function Library option number is entered as the negative of the option number (e.g., specify option 2 as option -2), QTRAN will use the reciprocal of the function. For example, SIN(X) would be evaluated as (1/SIN(X)).

T=T1 T2 temperature difference( )–Δ

σ * (T14 T2

4 ) radiosity difference( )–

T1 T2

TbarT1 T2+( )

2-------------------------------=


442

Microfunction OptionsEach microfunction option that is available is described below.

Option 1 - ConstantOption 1 is a constant of the following form:

F(X) = P1

where:

P1 is the first MICDAT value entered for the microfunction. See Microfunction Parameters or Data Tables, 324.

For example, suppose microfunction 11 is defined to be a constant with a value of 23.7.

ExampleMICRO1101MICDAT23.7/

Option 2 - Power SeriesOption 2 is a power series of the form:

... +

where:

F(X) = MICDAT(1) * XMICDAT(2)

MICDAT(3) * XMICDAT(4)+

MICDAT(N-1) * XMICDAT(N)


The MICDAT(1...N) are tabular input data that is supplied for the microfunction as outlined in Microfunction Parameters or Data Tables, 324.

For example, suppose microfunction number 12 is defined to be a temperature dependent power series of the following form.

ExampleMICRO1212MICDAT1.21.5MICDAT83.70.3MICDAT0.14.731/

Option 3 - Sine WaveOption 3 is a sine wave input of the form:

where:

P1, P2, P3, and P4 are the MICDAT(1) to MICDAT(4) parameters referred to in Microfunction Parameters or Data Tables, 324. The arguments (P2 * X + P3) are in radians.

For example, suppose microfunction 11 is defined to be a time dependent sine wave of the following form:

ExampleMICRO1103MICDAT23.714.8E+03 -18.7 1.456E+03/

F(X) = 1.2 * X1.5 83.7* X0.3 0.1* X4.731+ +

F(X)=P1 * SIN(P2 * X + P3) + P4

F(X)=23.7 * SIN(14.8E+03 * X - 18.7) +1.456E+03


444

Option 4 - Square WaveOption 4 is a square wave input that is calculated in the following manner:

1. Calculate A, where: A = SIN(MICDAT(3) * X + MICDAT(4))

2. Calculate the square wave value F(X) such that:F(X) = MICDAT(2) if A < 0, and

F(X) = MICDAT(1) if A = 0 or 0 < A,

where:

MICDAT(1...4) are the MICDAT parameters referred to in Microfunction Parameters or Data Tables, 324. The argument of the sine function, (P3 * X + P4), is assumed to be in radians.

For example, suppose that you want to define microfunction 14 to be a time dependent square wave with a frequency of 18.7, a phase angle of 44.7, a maximum value of 0.17 and a minimum value of 0.14.

ExampleMICRO1404MICDAT0.170.1418.744.7/


Option 5 - Step FunctionOption 5 is a step function input that is calculated in the following manner:

1. F(X) = MICDAT(2) if X < MICDAT(1), and2. F(X) = MICDAT(3) if X = MICDAT(1) or MICDAT(1) < X

where:

MICDAT(1...N) correspond to the parameters referred to in Microfunction Parameters or Data Tables, 324.

For example, suppose microfunction 15 is defined to be a step function using temperature difference as the argument (remember that the node temperatures are defined by the calling macrofunction) and that the step function form is as follows:

IF (X < 11.78) THENF(X) = 84.89ELSEF(X) = -77.67ENDIF

Example MICRO1525MICDAT11.7884.89-77.67/


446

Option 6 - Ramp FunctionOption 6 is a ramp function input that is calculated in the following manner:

1. F(X) = MICDAT(3) if X < or = MICDAT(1)1. F(X) = MICDAT(4) if MICDAT(2) < or = X1. F(X) is linearly interpolated between MICDAT(3) and MICDAT(4) if MICDAT(1) < X <

MICDAT(2)where:

MICDAT(1...N) correspond to the parameters referred to in Microfunction Parameters or Data Tables, 324.

For example, suppose microfunction 16 is defined to be a time-dependent ramp function of the following form:

where:

INTERP(10.0, 100.0, 20.0, 200.0, X) was a linear interpolation function.

ExampleMICRO1606MICDAT10.020.0100.0 200.0/

IF (X < or = 10.0) F(X) = 100.0IF (20.0 < or = X) F(X) = 200.IF (10.0 < X < 20.0) F(X) = INTERP(10.0, 100.0, 20.0, 200.0, X)


Option 7 - Exponential FunctionOption 7 is an exponential function of the form:

F(X) = MICDAT(1) * EXP(MICDAT(2) * (X - MICDAT(3)) + MICDAT(4)

where:

MICDAT(1...N) are the parameters referred to in Microfunction Parameters or Data Tables, 324.

For example, suppose microfunction 17 is to be defined to be an exponential function using the radiosity potential difference between two nodes as the argument with the exponential function having the following form:

ExampleMICRO1737MICDAT0.17-23.7-273.150.0/

F(X) = 0.17 * e-23.7* (X+273.15)

Important:Here MICDAT(4) is zero.


448

Option 8 - Linear Interpolation of a Data TableOption 8 results in the linear interpolation of a data table that is supplied and that corresponds directly to the table data referred to in Microfunction Parameters or Data Tables, 324. When ordered pairs of X and F(X) are entered for the MICDAT data, Option 8 will interpolate or extrapolate this data to determine the appropriate value of F(X). The data pairs must be entered in order of increasing values of X. If this is not done, error messages will be written to the output file and the program will terminate.

If Option 8 is used, at least two data pairs must be entered.

For example, suppose microfunction 18 is defined to be a temperature dependent data table of the following form:

ExampleMICRO1818MICDAT0.00.0MICDAT100.0 17.3MICDAT200.084.9MICDAT1000.7987.9/

Temperature (or X) Microfunction Value 0.0

100.0

200.0

1000.7

0.0

17.3

84.9

987.9


Option 9 - Hermite Polynomial Interpolation of a Data TableOption 9 is similar to Option 8 except that Hermite polynomials are used for interpolation wherever possible. Hermite polynomials are not used for the first and last intervals in the table or for extrapolation. Quadratic interpolation/extrapolation is used for these regions. Hermite polynomials guarantee both continuity of value for a function and continuity of slope. Linear interpolation would guarantee only continuity of value.

A table identical to the example can be defined for Option 8 (only using Hermite polynomial interpolation) with the following microfunction data:

Example MICRO1819MICDAT0.00.0MICDAT100.017.3MICDAT200.084.9MICDAT1000.7987.9/

If Option 9 is used, at least three data pairs must be defined.


450

Option 10 - Repeating Waveform - Linearly Interpolated Data TableOption 10 is identical to Option 8 except that no extrapolation from the table is allowed. Instead, the value of X is altered such that it falls between the smallest and largest table values. If the maximum table value of X is XMAX and the minimum table value of X is XMIN, an interval of X may be defined as follows.

INTERVAL = XMAX - XMIN

The value of X is then divided by INTERVAL, and the value of X is set equal to the remainder left by the division. This new value of X will fall between XMIN and XMAX and hence can be interpolated. This algorithm generates a repeating waveform defined by a data table that you enter. This function is especially useful, for example, to simulate solar insulation over a period of days. The heat input can be defined as a 24-hour cycle (repeating waveform) and can be input using Option 10.

For example, suppose that the problem involved a periodic heat source with a triangular pulse, with the base of the triangle at 0.0 heat units and the peak at 100.0 heat units. Suppose further that the triangle is symmetric about time = 50.0. The microfunction data for this function is as follows:

ExampleMICRO20010MICDAT0.00.0MICDAT50.0100.0MICDAT100.00.0/


This particular wave begins at time = 0.0. To cause a phase shift, all you have to do is to change the time values. The function as defined above will repeat the triangular heat pulse every 100.0 seconds.


Option 11 - Repeating Waveform - Hermite Interpolated Data TableOption 11 is a tabular repeating waveform similar to Option 10, except that the tabular waveform is interpolated using Hermite polynomials. Use this option if the function data is relatively smooth and to represent the function with relatively few data points. Option 11 is computationally more expensive than Option 10.

To define a Hermite polynomial interpolated waveform from the following tabular data.

ExampleMICRO21111MICDAT10.010.0MICDAT 50.020.0MICDAT75.00.0MICDAT100.0-10.0/

If Option 11 is used, at least three data pairs must be entered.

Temperature (or X) Microfunction Value10.0

50.0

75.0

100.7

10.0

20.0

0.0

-10.0


452

Option 12 - Natural Logarithm OptionOption 12 is a natural logarithm function that is generated in the following manner:

F(X) = MICDAT(1) * Ln( MICDAT(2) * X + MICDAT(3) ) + MICDAT(4)

where:

MICDAT(1...4) are the parameters referred to in Microfunction Parameters or Data Tables, 324.

When using any log function, exercise care that the argument does not become negative because a log function is undefined for negative arguments. If a log function argument does become negative, your computer will probably detect an arithmetic floating point error and terminate. QTRAN does not check for positive arguments.

For example, to define a time-dependent function of the following form.

ExampleMICRO22012MICDAT17.7E-0417.7 123.41.0E-07/

F(X) = 17.7E-04 * Ln(17.7 * X + 123.4) + 1.0E-07


Option 13 - Base 10 Logarithm OptionOption 13 is identical to Option 12 except that a Base 10 logarithm is used instead of a natural logarithm. The function is defined as:

where:

MICDAT(1...N) are the parameters referred to in Microfunction Parameters or Data Tables, 324.

When using any log function, exercise care that the argument does not become negative, because a log function is undefined for negative arguments. If a log function argument does become negative, the computer will probably detect an arithmetic floating point error and terminate. QTRAN does not check for positive arguments.

For example, to define a time-dependent function of the following form.

Example MICRO23013MICDAT17.7E-0417.7123.41.0E-07/

F(X) = MICDAT(1) * Log 10[ ] MICDAT(2) * X + MICDAT(3)( ) MICDAT(4)+

F(X) = 17.7E-04 * Log[10] 17.7 * X+123.4( ) 1.0E-07+


454

Option 14 - Blackbody Radiation Fraction OptionOption 14 calculates the fraction of a blackbody’s radiant energy that lies between two wavelengths. This fraction is calculated using formulas taken from Ref. in Appendix A, p. 769. The function parameters are defined as follows:

Values for F(X,MICDAT(1),MICDAT(2)) will always be between the values of 0 and 1, inclusive.

The primary use of this microfunction option is to emulate QTRAN’s wavelength-dependent thermal radiation algorithm using a heat source.

Example MICRO101114MICDAT0.20.6/

MICDAT(1) The shortest wavelength of the interval in units of micrometers.MICDAT(2) The longest wavelength of the interval in units of micrometers.

Important:The values of MICDAT(1) and MICDAT(2) must be such that MICDAT(1) < MICDAT(2).


Option 15 - Flip/Flop OptionOption 15 allows a flip/flop function to be implemented of the following form:

IF (MICDAT(1) ð X <MICDAT(2) ) THENF(X) = MICDAT(3)ELSEF(X) = MICDAT(4)ENDIF

where:

The MICDAT(1...4) are the parameters referred to in Microfunction Parameters or Data Tables, 324. This function is typically used for time-dependent heat sources that may be turned on for only a definite period of time. As can be seen, a flip/flop function is really a kind of double step function that is fairly commonly encountered.

For example, to build a model where a heat source of 1000.0 units is turned on at time = 17.8 and turned off again at time = 19.2.

ExampleMICRO25015MICDAT17.819.21000.0 0.0/


456

Option 16 - Dead BandRESTRICTION: This microfunction option may only be used for temperature control macrofunctions. It may not be used for heat source macrofunctions.

With this function, a node’s temperature may be controlled in the following manner:

A common use of this function is a hysteresis switch for thermostats, where the position of the switch (on/off) is dependent not only upon the temperature of a node but also upon the node’s history. For example, consider the following thermostatically controlled heater at node 1.

where:

1. If T1 < 60, heater is turned ON

2. If 80 < T1, heater is turned OFF

3. If 60 < T1 < 80, heater can be either ON or OFF depending upon the temperature history of T1

To build a thermostat, introduce another temperature node T2. T2 will not be a “real” temperature node but will instead be your hysteresis flag. T2’s temperature can be controlled with an Option 16 microfunction, letting the X of this microfunction be T1 and letting the MICDAT(1...4) values be 1.0, 60.0, 0.0, 80.0. Specifically we then have:

1. T2 = 1.0 if T1 < 60.0

2. T2 = 0.0 if T1 > 80.0

IF(MICDAT(2) < X < MICDAT(4) ) then T(X) = T (no change)IF(X < MICDAT(2) ) then T(X) = MICDAT(1)IF(MICDAT(4) < X) then T(X) = MICDAT(3)


3. T2 = unchanged if 60.0 < T1 < 80.0

The thermostat control has been built, next build the heater. This can be done by using microfunction option 17 (straight line) with the independent variable X of this microfunction being T2. For example, to build a 1000-watt heater for node T1, use Option 17 with MICDAT(1) and MICDAT(2) values of 1000.0 and 0.0, respectively, where Option 17 is of the form:

F(X) = MICDAT(1) * X + MICDAT(2)

Since T2 is used for X in the Option 17 microfunction and T2 can only be 1.0 or 0.0 (according the microfunction that controls T2), a complete (though simple) thermostatically controlled heater has been built for node T1.

ExampleMICRO26116MICDAT1.060.00.080.0 /

See Option 17 for an example of a straight line microfunction.

Option 17 - Straight LineOption 17 allows a straight line microfunction to be built of the following form:

F(X) =MICDAT(1) * X + MICDAT(2)

where:

MICDAT(1) and MICDAT(2) are the parameters referred to in Microfunction Parameters or Data Tables, 324.


458

To build a straight line heat source such as the one described for the thermostatically controlled heater in the Option 16 example. This straight line heater has the form:

F(X) = 1000.0 * X + 0.0

ExampleMICRO27117MICDAT1000.00.0/

Option 18 - Indexed Linear Interpolation of a Data TableOption 18 results in the linear interpolation of a data table that is supplied that corresponds directly to the table data referred to in Microfunction Parameters or Data Tables, 324. When ordered pairs of X and F(X) are entered for the MICDAT data, Option 18 will interpolate or extrapolate this data to determine the appropriate value of F(X). The data pairs must be entered in order of increasing values of X. If this is not done, error messages will be written to the output file and the program will terminate. This is identical to Option 8 except the table is entered at the point it last exited in an attempt to speed up execution.

If Option 18 is used at least two data pairs must be entered.

For example, suppose that you wish to define microfunction 28 to be a indexed temperature dependent data table of the following form:


ExampleMICRO28118MICDAT0.00.0MICDAT100.017.3MICDAT200.084.9MICDAT1000.7987.9/

Option 19 - Indexed Hermite Polynomial Interpolation of a Data TableOption 19 is similar to Option 18 except that Hermite polynomials are used for interpolation wherever possible. Hermite polynomials are not used for the first and last intervals in the table or for extrapolation. Quadratic interpolation/extrapolation is used for these regions. Hermite polynomials guarantee both continuity of value for a function and continuity of slope. Linear interpolation would guarantee only continuity of value.

A table identical to the example for Option 9 - Hermite Polynomial Interpolation of a Data Table, 449 can be defined (only using Hermite polynomial interpolation) with the following microfunction data. The only difference between Option 9 and 19 is the indexed table enters the table where it last exited. This is done to improve execution times.


100.0

200.0

1000.7

0.0

17.3

84.9

987.9


460

Example MICRO18 119MICDAT0.00.0MICDAT100.017.3MICDAT200.084.9MICDAT1000.7987.9/


Option 20 - Indexed Repeating Waveform - Linearly Interpolated Data TableOption 20 is identical to Option 18 except that no extrapolation from the table is allowed. Instead, the value of X is altered such that it falls between the smallest and largest table values. If the maximum table value of X is XMAX and the minimum table value of X is XMIN, an interval of X may be defined as follows.

INTERVAL = XMAX - XMIN

The value of X is then divided by INTERVAL, and the value of X is set equal to the remainder left by the division. This new value of X will fall between XMIN and XMAX and hence can be interpolated. This algorithm generates a repeating waveform defined by a data table that you enter. This function is especially useful, for example, to simulate solar insulation over a period of days. The heat input can be defined as a 24-hour cycle (repeating waveform) and can be input using Option 20. The data table is entered at the point that it last exited to help speedup execution.

For example, suppose that you wished to build a periodic heat source with a triangular pulse, with the base of the triangle at 0.0 heat units and the peak at 100.0 heat units. Suppose further that the triangle is symmetric about time = 50.0.

ExampleMICRO 201020MICDAT0.00.0MICDAT50.0100.0


MICDAT100.00.0/

This particular wave begins at time = 0.0. To cause a phase shift, change the time values. The function as defined above will repeat the triangular heat pulse every 100.0 seconds.


Option 21 - Indexed Repeating Waveform - Hermite Interpolated Data TableOption 21 is a tabular repeating waveform similar to Option 20, except that the tabular waveform is interpolated using Hermite polynomials. Use this option if the function data is relatively smooth to represent the function with relatively few data points. Option 21 is computationally more expensive than Option 20. The data table is entered at the point that it last exited in order to speedup execution.

For example; to define a Hermite polynomial interpolated waveform from the tabular data below, use the following microfunction data.

ExampleMICRO123121MICDAT10.010.0MICDAT50.020.0


50.0

75.0

100.0

10.0

20.0

0.0

-10.0


462

MICDAT75.00.0MICDAT100.0-10.0/


Option 22 - Repeating Flip/Flop OptionOption 22 allows a flip/flop function to be implemented of the following form:

IF (MICDAT(2) ≤ X <MICDAT(3) ) THEN

F(X) = MICDAT(5)ELSEF(X) = MICDAT(6)ENDIFPERIOD = MICDAT(4) - MICDAT(1)

where:

The MICDAT(1...5) are the parameters referred to in Microfunction Parameters or Data Tables, 324. This function is typically used for time-dependent heat sources that may be turned on and off for only a definite periods of time. As can be seen, a repeating flip/flop function is really a kind of double step function that can be turned on and off at repeatedly but can have different on and off time periods. The period is P4 - P1.

For example, to build a model where a heat source of 1000.0 units is turned on between 19.2 and 26.4 second and repeated every 22.2 where the cycle begins at 17.8 seconds, the inputs would be as define below.

ExampleMICRO25015


MICDAT17.819.226.440.01000.0 0.0/

Option 1000+ - User-Coded FunctionsOption 1000+ allows unique special case functions to be defined through a user-coded subroutine named UMICRO. A dummy version of subroutine UMICRO may be found in the ULIB.FOR file supplied with Patran Thermal, along with example applications.

Whenever an OPTION number of 1000 or larger is used for a microfunction, QTRAN will call subroutine UMICRO. This allows a library to be built and maintained of a very exotic special case heat source or temperature control functions. With UMICRO, any of the QTRAN parameters or arrays may be accessed, since all arrays and all important parameters are contained in named common blocks.

For example, microfunction 199 could be used to be a time dependent microfunction with the following data:

ExampleMICRO19901000MICDAT0.0273.01.0375.02.0 376.0 100.0 390.0101.0-37.36115.027.0

Any macrofunction in the model that references MFID 199 will now return a value from the user-supplied subroutine UMICRO.


464

Chapter 11: User-Supplied RoutinesPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

11 User-Supplied Routines

User-Supplied Subroutines 466

COMMONBLK Definitions 468

ULIBFOR Contents - Example User-Supplied Subroutines 484

Example User-Supplied Routines 536

QTRAN Arrays 545

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisUser-Supplied Subroutines

466

User-Supplied SubroutinesThis chapter contains subroutines from the ULIBFOR file provided with P/THERMAL. These subroutines are called at various key points in QTRAN’s calculation loop. See Figure 11-1. Any of these routines may be modified and necessary for the analyses. Then compile and link them with QTRAN using the ULIB command provided with P/THERMAL.

Many of these routines refer to a $INSERT file (a file included at compile time) named COMMONBLK. COMMONBLK is a common block file of parameters used by QTRAN. This file is provided with P/THERMAL, and the file has extensive comments describing the various common block parameters. The user should only use the common blocks required for the individual subroutines being written. Each type of variable is defined in separate include files but all are located through the COMMONBLK file. The COMMONBLK_ALL includes individual files. COMMONBLK does NOT include arrays that are in common. Common arrays may be found in the QTRANFOR file. The QTRAN arrays are defined in section 11.5.

The user should check the COMMONBLK, COMMON****,ULIBFOR and sample QTRANFOR files provided in the P3_HOME/p3thermal_files/lib directory to be sure you have the latest versions.

467Chapter 11: User-Supplied RoutinesUser-Supplied Subroutines

Figure 11-1 Top Level QTRAN Flow Diagram

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisCOMMONBLK Definitions

468

COMMONBLK DefinitionsIt is best to only include the variables one needs in a given subroutine. Thus a group of common blocks is supplied. The array common blocks are defined in section 11.5 plus are in your qtran.f file. The various common blocks are shown below and can be found in the P3_HOME/p3thermal_files/examples/qtran/utilities directory. Some common blocks are include statements for other common blocks. All are listed below.

common.basc

C The following is a list of the QTRAN common block variables.CC############################################################################CC Value of common block countersCC CB - 6 Character variablesC IA - 92 Integer arraysC IB -117 Integer variablesC LA - 1 Logical arraysC LB - 17 Logical variableC RA - 77 Real (double precision) arraysC RB -128 Real (double precision) variablesCC#############################################################################CC Include all the basic common block typesC Exclude the character commons. They're only needed for I/O and parsing.C#include "common.intr"#include "common.logc"#include "common.real"#include "common.dims"CC############################################################################

common.blkC The following is a list of the QTRAN common block variables.CC############################################################################CC Value of common block countersCC CB - 6 Character variablesC IA - 92 Integer arraysC IB -117 Integer variablesC LA - 1 Logical arraysC LB - 17 Logical variableC RA - 77 Real (double precision) arraysC RB -128 Real (double precision) variablesCC#############################################################################CC Include all the different common block typesC#include "common.intr"#include "common.char"#include "common.logc"#include "common.real"#include "common.dims"CC############################################################################

469Chapter 11: User-Supplied RoutinesCOMMONBLK Definitions

common.charC The following is a list of the QTRAN character common block variables.CC############################################################################CC Value of common block countersCC CB - 6 Character variablesCC#############################################################################CC CHARACTER*1 ISCALE, ICCALC CHARACTER*10 TLABEL CHARACTER*256 RSTFNM, INPFIL(MAXFIL) CHARACTER*80 TITLE(3)CC############################################################################CC This section is reserved for character variables. The convention isC that all character common blocks will begin with the lettersC "CB".C COMMON / CB1 / ISCALE COMMON / CB2 / ICCALC COMMON / CB3 / TLABEL COMMON / CB4 / RSTFNM COMMON / CB5 / INPFIL COMMON / CB6 / TITLECC Usage:C ISCALE --> temperature scale code for data output.C ICCALC --> temperature scale code for calculations.C TLABEL --> time units label.C RSTFNM --> restart file name (if any).C INPFIL --> input file names.C TITLE --> First 3 lines of title data (if any) from theC QIN.DAT file. This is saved for generating NodalC results files.CC############################################################################

common.dimsC The following are the array dimension control variables.CC############################################################################C dims is the dimensions common block.CC j1 is the maximum number of convective resistors.C j2 is the maximum number of material properties allowed forC each convective resistor, and should be equal to 7.C j3 is the maximum number of material properties allowed for theC thermal system.C ( j4 - 1 ) is the maximum number of material property data pairsC allowed to describe a material property.C j5 is the maximum number of conductive resistors.C j6 is the maximum number of geometric properties allowed to describeC a given convective resistor.C j7 is the maximum number of non-tabular, non-power series


470

C micro-functions allowed in the system.C j8 is the maximum number of variables allowed to define a givenC non-tabular, non-power series micro-function, and shouldC be equal to 4.C j9 is the maximum number of data tables or power series which may beC input to be evaluated for the system micro-functions.C (j10 - 1) is the maximum number of data pairs which may be enteredC for the tabular or power series micro-functions.C (j11 / 2) is the maximum number of conductive resistors allowed inC the system.C (j12 / 2) is the approximate number of convective resistors allowedC in the system. use of 3-node resistors will reduce this maximumC number of convective resistors somewhat.C the formula for j12 is: j12 = n2*2 + n3*3, whereC n2 is the number of 2-node convective resistors and n3 isC number of 3-node convective resistors in the system.C j13 is the maximum number of radiative resistors allowed inC the system.C j14 is the total number of micro-functions allowed in the system.C this total includes both parameter and tabular micro-functions.C j15 is the 2nd "qcard" dimension, and should be equal to 4.C (j16 - 3) is the maximum number of microfunctions which may be combinedC through the arithmetic operations of multiplication or divisionC to form a heat source/sink macrofunction.C j17 is the maximum number of heat source/sink macrofunctions allowedC in the system.C j18 is the maximum number of temperature control macrofunctionsC which may be constructed by multiplying and dividing micro-C functions.C (j19 - 3) is the maximum number of microfunctions which may be combinedC arithmetically through the operations of multiplication andC division to form temperature control macrofunctions.C (j20 / 2) is the maximum number of radiative resistors allowed.C j21 is the maximum number of "tfix" classification changes permitted.C j22 is the maximum number of allowed phase change information sets.C (j23 / 2) is the maximum number of phase changes per capacitor. j23C is the pidpar vector dimension and the 2nd dimension for theC pidset array.C j24 is the pidid vector dimension and should be set equal to j36C if any phase changes in the system are possible, else set to 1.C j25 is the maximum number of gray radiative surface elements.C j26 is related to the maximum number of node numbers associated withC all gray radiative surface elements.C j27 is the 2nd dimension for the TERROR array. It is the number ofC iterative temperature errors that are carried along.C j28 is the maximum number of allowed wavelength dependent radiativeC resistors.C j29 is twice the maximum number of allowed wavelength dependentC radiative resistors, so: j29 = j28 * 2.C j30 is the maximum number of mass flow resistors.C j31 = j30 * 2 (pointer vector dimenson).C j32 = maximum number of dtmax changes + 1.C j33 = 2nd dtmaxa dimension and should be equal to 2.C j34 = maximum number of print interval changes + 1.C j35 = 2nd printa dimension and should be equal to 2.C j36 = maximum number of capacitors allowed in the system.C j37 = maximum number of wavelength dependent radiative surface elements.C j38 = related to the maximum number of wavelength dependent subsurfaceC areas for the wavelength dependent radiative surface elements.C j39 = first index in the user specified relaxation control parametrsC array. Should be 5 for the control groupings given the user.C j40 = 2nd relaxation parameters index, equals 3 for the 3 values inputC j41 = 2nd index in relaxation error array RERROR, equals 3.C This represents the oldest, old and current error.C j42 = 2nd index in relaxation error grouping arrays, equals 6.C This represents the relaxation parameters for each groupC j43 = 2nd index in relaxation error grouping integer arrays, equals 6.C This represents the relaxation parameter indexes and node


C identities for each group.C j44 = Number of hydraulic resistors definedC j45 = Maximum number of geometric properties specified for a hydraulicC resistor.C j46 = Maximum number of material properties specified for a hydraulicC resistor.C j47 = Number of node pointer for the hydraulic resistors (2*j44)C j48 = Number of mass flow rate macro functions definedC j49 = Maximum number of micro functions specified in the mass flow rateC macro functionsC j50 = Number of pressure macro functions defined for the hydraulic networksC j51 = Maximum number of micro functions in the pressure macro functionsC j52 = Maximum number of temperature couplingsC maxp = The array sizes for the hydraulic solution. Equals one more thanC the number of pressure nodes specified for the hydraulic network.C maxt is the maximum number of allowed temperature nodes.C maxtnc = 1 if nc = 0, maxtnc = maxt if nc .ne. 0.C maxtnh = 1 if nh = 0, maxtnh = maxt if nh .ne. 0.C maxtnr = 1 if nr = 0, maxtnr = maxt if nr .ne. 0.C maxtnw = 1 if nw = 0, maxtnw = maxt if nw .ne. 0.C maxtqn = 1 if ifi = 0, maxtqn = maxt if ifi .ne. 0.C maxtnf = 1 if nf = 0, maxtnf = maxt if nf .ne. 0.C m1 = 1 if SOL .ne. 5. Else, m1 = maxt + 1. m1 is the dimensionC of MATRIX, where MATRIX is the augmented matrix used forC qtran's linear gauss elimination routine.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################

common.intC The following is a list of the QTRAN INTEGER common block variables.CC############################################################################CC Value of common block countersCC IA - 92 Integer arraysC IB -117 Integer variablesCC#############################################################################CC Declare the types of the common block variables.CCC (MAXFIL - 1) is the maximum number of nested $INSERT files.


472

C INTEGER MAXFIL INTEGER MAXFCHC PARAMETER ( MAXFIL = 10 ) PARAMETER ( MAXFCH = 256 )C INTEGER IOPT, IMAX, IMIN, IMAXSS, NC, NH, NR, NS, NX, IFI, ITI INTEGER IFIXI, JTP, NF, NW, NCAPS, IST, NTEMPS, IPS, IPT, IS INTEGER NODE, ICPNTR, IHPNTR, IRPNTR, IWPNTR, IQPNTR, IFPNTR INTEGER ICAPPT, DCMF, IENODE, ITER, IIN, IO, STATUS, J, JI, IOPTR INTEGER IRETN, NRF, NWRAD, IFAIL, NRAD, NMID, NPID, NMFID, CPUSEC INTEGER CPUSAV, IBT, IBS, ISSDMP, IGSURF, IGPNTR, IXPNTR, IWSURF INTEGER IPERTR, SOL, NITBUP, NRDUMP, LUDUMP, OWIDTH INTEGER LINNUM(MAXFIL), FILPNT, IRESIS, INNERI, NPLTMP, LUPLOT INTEGER IEMAXE, IFSRLX, IFTRLX, KQMAC, KTMAC, NMAXWD, RRRCNT INTEGER KMMAC, KPMAC INTEGER NRFORM, NRFWID INTEGER NP, NUPNOD, IMMI, IPI, MPIDGH, MPIDGX, MPIDGY, MPIDGZ INTEGER JH, JHI, IMPNTR, IMAXPR, IMAXHE, IMAXME, HIOPT, HSOL INTEGER NTBHUP, HITER, HPITER, NHYCNT, NODEHY, IPPNTR, NPDUMP INTEGER NPFWID, NFFWID INTEGER NTCPL INTEGER FPRTFL, JPRTFL INTEGER IFLIPF, JFLIPF, MFLIPF INTEGER OVRWFL INTEGER MXHPIT!!! INTEGER ICPNT INTEGER HLFDTF INTEGER TOTITR INTEGER INDTPAC INTEGER IRQFLO(9) INTEGER IDMNRF(20)C COMMON / IA73 / IDMNRFCC NOTE: UsageCC IDMNRF -> Flag to indicate what results quantities are to be putC in the nodal results file.CC############################################################################CC This section contains the integer common blocks. The convention isC that all integer common block names will begin with theC letters "IB".C COMMON / IB1 / IOPT COMMON / IB2 / IMAX COMMON / IB3 / IMIN COMMON / IB4 / IMAXSS COMMON / IB5 / ISSDMP COMMON / IB6 / NC COMMON / IB7 / NH COMMON / IB8 / NR COMMON / IB9 / IFI COMMON / IB10 / ITI COMMON / IB11 / IFIXI COMMON / IB12 / JTP COMMON / IB13 / NF COMMON / IB14 / NW COMMON / IB15 / NCAPS COMMON / IB16 / IST COMMON / IB17 / NTEMPS COMMON / IB18 / IBS COMMON / IB19 / IBT COMMON / IB20 / IS


COMMON / IB21 / NODE COMMON / IB22 / ICPNTR COMMON / IB23 / IHPNTR COMMON / IB24 / IRPNTR COMMON / IB25 / IWPNTR COMMON / IB26 / IQPNTR COMMON / IB27 / IFPNTR COMMON / IB28 / ICAPPT COMMON / IB29 / DCMF COMMON / IB30 / IENODE COMMON / IB31 / ITER COMMON / IB32 / IIN COMMON / IB33 / IO COMMON / IB34 / STATUS COMMON / IB35 / J COMMON / IB36 / JI COMMON / IB37 / IOPTR COMMON / IB38 / IRETN COMMON / IB39 / NRF COMMON / IB40 / NWRAD COMMON / IB41 / IFAIL COMMON / IB42 / NRAD COMMON / IB43 / IRQFLO COMMON / IB44 / NMID COMMON / IB45 / NPID COMMON / IB46 / NMFID COMMON / IB47 / CPUSEC COMMON / IB48 / CPUSAV COMMON / IB49 / NS COMMON / IB50 / IGSURF COMMON / IB51 / IGPNTR COMMON / IB52 / IPS COMMON / IB53 / IPT COMMON / IB54 / IXPNTR COMMON / IB55 / IWSURF COMMON / IB56 / NX COMMON / IB57 / IPERTR COMMON / IB58 / SOL COMMON / IB59 / NITBUP COMMON / IB61 / NRDUMP COMMON / IB62 / LUDUMP COMMON / IB63 / OWIDTH COMMON / IB64 / LINNUM COMMON / IB65 / FILPNT COMMON / IB66 / IRESIS COMMON / IB67 / INNERI COMMON / IB68 / NPLTMP COMMON / IB69 / LUPLOT COMMON / IB70 / IEMAXE COMMON / IB71 / IFSRLX COMMON / IB72 / IFTRLX COMMON / IB73 / KQMAC COMMON / IB74 / KTMAC COMMON / IB75 / NMAXWD COMMON / IB76 / RRRCNT COMMON / IB77 / NRFORM COMMON / IB78 / NRFWID COMMON / IB79 / NUPNOD COMMON / IB80 / NP COMMON / IB81 / IMMI COMMON / IB82 / IPI COMMON / IB83 / MPIDGH COMMON / IB84 / MPIDGX COMMON / IB85 / MPIDGY COMMON / IB86 / MPIDGZ COMMON / IB87 / JH COMMON / IB88 / JHI COMMON / IB89 / IMPNTR


474

COMMON / IB90 / IMAXPR COMMON / IB91 / IMAXHE COMMON / IB92 / IMAXME COMMON / IB93 / HIOPT COMMON / IB94 / HSOL COMMON / IB95 / NTBHUP COMMON / IB96 / HITER COMMON / IB97 / HPITER COMMON / IB98 / NHYCNT COMMON / IB99 / NODEHY COMMON / IB100 / IPPNTR COMMON / IB101 / NPDUMP COMMON / IB102 / NPFWID COMMON / IB103 / NFFWID COMMON / IB104 / KMMAC COMMON / IB105 / KPMAC COMMON / IB106 / NTCPL COMMON / IB107 / FPRTFL COMMON / IB108 / JPRTFL COMMON / IB109 / IFLIPF COMMON / IB110 / JFLIPF COMMON / IB111 / MFLIPF COMMON / IB112 / OVRWFL COMMON / IB113 / MXHPIT!!! COMMON / IB114 / ICPNT COMMON / IB115 / HLFDTF COMMON / IB116 / TOTITR COMMON / IB117 / INDTPACC Usage:C IOPT --> run control option.C IMAX --> maximum number of allowed transient iterationsC per time step.C IMIN --> minimum number of preferred transient iterationsC per time step.C IMAXSS --> maximum number of allowed steady state iterations.C ISSDMP --> number of steady state iterations per print dump.C NC --> number of conductive resistors.C NH --> number of convective resistors.C NR --> number of gray radiation resistors.C IFI --> number of QMACROfunctions assigned.C ITI --> number of TMACROfunctions assigned.C IFIXI --> number of nodal fixed/not-fixed/TMACROfunctionC controlled classification changes to be made.C JTP --> phase change flag: = 0 --> no potential phaseC changes in the model, = 1 --> potential phaseC changes exist.C NF --> number of advection resistors.C NW --> number of spectral dependent radiative resistors.C NCAPS --> number of capacitors.C IST --> minimum number of transient iterations betweenC increases in the size of the transient relaxationC parameter.C NTEMPS --> number of nodes.C IBS --> (not used)C IBT --> (not used)C IS --> minimum number of steady state iterations betweenC increases in the size of the steady stateC relaxation parameter.C NODE --> current node being iterated upon (internal nodeC number, not the one the user assigned).C ICPNTR --> conductive resistor pointer variable.C IHPNTR --> convective resistor pointer variable.C IRPNTR --> gray radiative resistor pointer variable.C IWPNTR --> spectral radiative resistor pointer variable.C IQPNTR --> QMACROfunction pointer variable.C IFPNTR --> advection resistor pointer variable.C ICAPPT --> capacitor pointer variable.


C DCMF --> discontinuous macrofunction flag.C IENODE --> internal node number for node with largest error.C ITER --> iteration counter.C IIN --> logical unit number assigned to QIN.DAT.C IO --> logical unit number assigned to QOUT.DAT.C STATUS --> logical unit number assigned to STAT.DAT.C J --> convective resistor configuration number.C JI --> convective resistor being calculated.C IOPTR --> logical unit number for current $INSERT file,C if any. If none, logical unit number for QIN.DAT.C IRETN --> transient iteration flag: = 0 --> new time stepC is about to begin, = 1 --> more transientC iterations are about to occur.C NRF --> advective resistor being calculated.C NWRAD --> spectral radiative resistor being calculated.C IFAIL --> time step expansion flag. Time steps may beC expanded only if IFAIL = 0.C NRAD --> gray radiative resistor being calculated.C IRQFLO()--> 1-d array of flags for resistor/capacitor/qmacroC data print/no-print options.C NMID --> number of material properties defined.C NPID --> number of phase change sets defined.C NMFID --> number of microfunctions defined.C CPUSEC --> current (or last) cpu time, in seconds.C CPUSAV --> starting cpu time (in seconds).C NS --> (not used)C IGSURF --> (not used)C IGPNTR --> (not used)C IPS --> relaxation parameter iteration counter (steadyC state).C IPT --> relaxation parameter iteration counter (transient).C IXPNTR --> (not used)C NX --> (not used)C IPERTR --> this variable is used to signal whether theC heat flow calculation for the resistors/capacitors/C heat sources/etc. is currently based upon T,C T+pertur, or T-pertur. the value of ipertr is setC as follows: ipertr = 0 --> TC ipertr = +1 --> T+perturC ipertr = -1 --> T-perturC SOL --> Solution option, where:C sol = 0 --> standard solutionC = 1 --> quasi-linear conduction resistors.C NITBUP --> For SOL > 0 only, the Number of ITerations BetweenC UPdates of conductive resistors.C NRDUMP --> Nodal results file suffix number.C LUDUMP --> Logical unit number for nodal results files.C OWIDTH --> Number of columns of data to be output to theC QTRAN nodal results files.C LINNUM --> Current line number for each input file.C FILPNT --> File pointer, indexes into the LINNUM and INSFILC arrays to point to the current input file/line numberC data.C IRESIS --> Current conductive or convective resistor beingC calculated.C INNERI --> Inner iteration counter.C NPLTMP --> Number of temperatures to be dumped to the plotC file at each converged calculationC LUPLOT --> Logical unit for plot output fileC IEMAXE --> Node index with the maximum system errorC IFSRLX --> Steady state relaxation option to useC IFTRLX --> Transient relaxation option to useC KTMAC --> Index of the temperature macrofunctionsC KQMAC --> Index of the heat macrofunctionsC KMMAC --> Index of the mass flow rate macrofunctionsC KPMAC --> Index of the pressure macrofunctionsC NMAXWD --> Number of word to be used for incore direct solverC RRRCNT --> Number of time steps or number of time in reset1


476

C NRFORM --> Flag to indicate type of results file outputC NRFWID --> Number of items put in nodal results fileC NUPNOD --> Number of hydraulic nodalsC NP --> Number of hydraluic resistorsC IMMI --> Number of mass flow rate macrofunctionsC IPI --> Number of pressure macrofunctionsC MPIDGH --> Material property for time dependent gravityC MPIDGX --> Material property for time dependent gravityC MPIDGY --> Material property for time dependent gravityC MPIDGZ --> Material property for time dependent gravityC JH --> Hydraulic element option typeC JHI --> Hydraulic element number (index)C IMPNTR --> Index pointer in the mass flow rate pointer tableC IMAXPR --> Index indicating the hydraulic node with maximumC pressure errorC IMAXHE --> Index indicating the hydraulic node with maximumC hydraulic head difference errorC IMAXME --> Index indicating the hydraulic node with maximumC mas flow rate errorC HIOPT --> Hydraulic optionC HSOL --> Hydraulic solution optionC NTBHUP --> Hydraulic counter to control update frequencyC HITER --> Iteration counter between hydraulic updatesC HPITER --> Iteration counter between hydraulic pressure updatesC NHYCNT --> Count of the number of hydraulic solutions that haveC been performed.C NODEHY --> Internal hydraulic node numberC IPPNTR --> Hydraulic resistor pointerC NPDUMP --> Hydraulic results file output counterC NPFWID --> Number of items written to pressure results fileC NFFWID --> Number of items written to hydraulic linkage fileC NTCPL --> Number of temperature couplings to be madeC FPRTFL --> Flag to force a print out at this timeC JPRTFL --> Flag to indicate that a print out occurred on theC previous time stepC IFLIPF --> Count of how many times the maximum iterativeC Temperature error has consecutively reversed itselfC JFLIPF --> Count of how many times the full bisection hasC been used this iterationC MFLIPF --> Maximum number of temperature reversals allowedC before a model wide bisection iteration is performedC OVRWFL --> Over Write Flag used with restarts that indicateC the information related to temperature initializationC is to be used to replace the information specifiedC in the restart file.C MXHPIT --> maximum number of allowed iterations for theC hydraulic pressure solution.C ICPNT --> Internal pointer to the capacitor being evaluatedC HLFDTF --> Flag that the time step has been halved as it C approaches a print time.C TOTITR --> Total number of iteration performed during a C solution including those that did not converge.C INDTPA --> Index into the PRINTA array for active values.CC############################################################################

common.logcC The following is a list of the QTRAN logical common block variables.CC############################################################################


CC Value of common block countersCC LA - 1 Logical arraysC LB - 17 Logical variableCC#############################################################################CC Declare the types of the common block variables.C LOGICAL STEADY, ALGBRA, LOGP, CVFLAG, DTFLAG, INNER, TRACE, $ RSTART, LEXIT, IHCVFL, LABORT, LNGSTA, LPRTHY, 2 PNRFLG, PNPFLG, PNFFLGCC############################################################################CC This section is reserved for logical variables. The convention isC that all logical variable common blocks will have commonC block names beginning with the letters "LB".C COMMON / LB1 / STEADY COMMON / LB2 / ALGBRA COMMON / LB3 / LOGP COMMON / LB4 / CVFLAG COMMON / LB5 / DTFLAG COMMON / LB6 / INNER COMMON / LB7 / TRACE COMMON / LB8 / RSTART COMMON / LB9 / LEXITC*C* COMMON / LB10 / WSTDYS COMMON / LB11 / IHCVFL COMMON / LB12 / LABORT COMMON / LB13 / LNGSTA COMMON / LB14 / LPRTHY COMMON / LB15 / PNRFLG COMMON / LB16 / PNPFLG COMMON / LB17 / PNFFLGCC Usage:C STEADY --> steady state run flag. If .true., a steady stateC run is in progress. If .false., a transientC run is in progress.C ALGBRA --> algebraic node iteration flag. If .true., theC current iteration being performed will involveC only those nodes without capacitors. If .false.,C the iteration will involve all nodes.C LOGP --> logical print/no-print flag used during data inputC and also during resistor heat flow data outputC after print dumps. If .false., no data printed.C If .true., data is printed.C CVFLAG --> convergence flag. If .true., the steady state orC transient iterations have converged. If .false.,C convergence is incomplete.C DTFLAG --> time step change flag.C C INNER --> inner iteration loop flag. If .true., a phaseC change is occurring and the bisection algorithmC is iterating on the node changing phase.C TRACE --> status file trace flag. If .true., all input dataC file lines are printed to the status file.C RSTART --> restart flag, = .false. = normal run from initialC conditions (default), = .true. = read the qin.datC file, then read the RSTART.DMP file and restartC from the conditions stored in RSTART.DMP.C LEXIT --> Exit flag, when true it indicates that theC transient solution has finished and there are noC more analysis desired.C WSTDYS --> Logical flag that indicates if the last calculation


478

C was steady stateC IHCVFL --> Flag that indicates that the network has converged,C now go back a recalculate all explicit node orC reevaluate resistors if the weakly nonlinearC solution is used.C LABORT --> Flag to indicate that the job is to be terminatedC and an output file is created at this pointC LNGSTA --> Flag to indicate that long or continuous statusC file are to be created for transient runsCC LPRTHY --> Flag to indicate that a hydraulic solution has beenC calculated and should be printed at the next printC conditionCC PNRFLG --> Flag indicating that nodal results file is writtenCC PNPFLG --> Flag indicating that pressure nodal results file C is written for the hydraulic nodesCC PNFFLG --> Flag indicating that hydraulic linkage file C is written for the hydraulic networkCC############################################################################

common.realC The following is a list of the QTRAN real common block variables.CC############################################################################CC Value of common block countersCC RA - 77 Real (double precision) arraysC RB -128 Real (double precision) variablesCC#############################################################################CC Declare the types of the common block variables.C double_precision TIME, DT, TSTART, TSTOP, TPRINT, EPSISS, EPSIT, $ PERTUR, PERTU2, PERTSQ, DTMAX, RELAX, RELAXS, RELAXT, $ TSFMIN, TSFMAX, BETAEX, BETAIM, DTOLD, EFACT, QGLOBL, $ SBC, SMALL, TINY, HUGE, QVECTP, QVECTM, GSUM, GVALC, $ BETA, PCBAND, DELMAX, DTP, ERROR, Q, T1, T2, T3, GVALH, $ CLOCK, EOLDST, ERROLD, DTPRED, CP, BALNCE, Q12, Q21, GVAL, $ QWAVE, QGRAY, EMISS, TAU, QSURF, GVALS, QSURFT, GVALT, $ TTMAC, FOLD, DELT, F11, F22, RMFLOW, EPSIT2, TSAVE, CPDELT, $ QINPUT, DTMIN, H, MINTMP, MAXTMP, BETMIN, BETMAX double_precision PINITL, MGLOBL, GH, GX, GY, GZ, HYBETA, HDIAM, 1 HCSAA, HDLEN, HDX, HDY, HDZ, HPRHO, HPRHOE, HMU, HNU, HCP, 2 HEPS, HLOSCF, HFF, HWDOT, HREYN, HQFLOW, HHX, HHY, HHZ, 3 HHXREF, HHYREF, HHZREF, HDPHED, HP1, HP2, HDTEMP, HPHEAD, 4 PI, GRAVTY, BTINY, HPERRM, HMERRM, HERRMX, HYEPIS, DTMAXH, 5 HYTIME, HYOTIM, HUNITS double_precision RSTIME double_precision HYHDEP, HYMDEP, HYPREP!!! double_precision TNODE double_precision SUMQ double_precision SUMCNV double_precision SUMRAD double_precision CLKDTMCC############################################################################


CC This section is reserved for all real common blocks. The conventionC is that all real common block names will begin with theC letters "RB".C COMMON / RB1 / TIME COMMON / RB2 / DT COMMON / RB3 / TSTART COMMON / RB4 / TSTOP COMMON / RB5 / TPRINT COMMON / RB6 / EPSISS COMMON / RB7 / EPSIT COMMON / RB8 / PERTUR COMMON / RB9 / PERTU2 COMMON / RB10 / PERTSQ COMMON / RB11 / DTMAX COMMON / RB12 / RELAX COMMON / RB13 / RELAXS COMMON / RB14 / RELAXT COMMON / RB15 / TSFMIN COMMON / RB16 / TSFMAX COMMON / RB17 / BETAEX COMMON / RB18 / BETAIM COMMON / RB19 / DTOLD COMMON / RB20 / EFACT COMMON / RB21 / QGLOBL COMMON / RB22 / SBC COMMON / RB23 / SMALL COMMON / RB24 / TINY COMMON / RB25 / HUGE COMMON / RB26 / QVECTP COMMON / RB27 / QVECTM COMMON / RB28 / GSUM COMMON / RB29 / GVALC COMMON / RB30 / BETA COMMON / RB31 / PCBAND COMMON / RB32 / DELMAX COMMON / RB33 / ERROR COMMON / RB34 / DTP COMMON / RB35 / Q COMMON / RB36 / T1 COMMON / RB37 / T2 COMMON / RB38 / T3 COMMON / RB39 / GVALH COMMON / RB40 / CLOCK COMMON / RB41 / EOLDST COMMON / RB42 / ERROLD COMMON / RB43 / DTPRED COMMON / RB44 / CP COMMON / RB45 / BALNCE COMMON / RB46 / Q12 COMMON / RB47 / Q21 COMMON / RB48 / GVAL COMMON / RB49 / QWAVE COMMON / RB50 / QGRAY COMMON / RB51 / EMISS COMMON / RB52 / TAU COMMON / RB53 / QSURF COMMON / RB54 / GVALS COMMON / RB55 / QSURFT COMMON / RB56 / GVALT COMMON / RB57 / TTMAC COMMON / RB58 / DELT COMMON / RB59 / FOLD COMMON / RB60 / F11 COMMON / RB61 / F22 COMMON / RB62 / RMFLOW COMMON / RB63 / EPSIT2


480

COMMON / RB64 / TSAVE COMMON / RB65 / CPDELT COMMON / RB67 / QINPUT COMMON / RB68 / DTMIN COMMON / RB69 / H COMMON / RB70 / MINTMP COMMON / RB71 / MAXTMP COMMON / RB72 / BETMIN COMMON / RB73 / BETMAX COMMON / RB74 / PINITL COMMON / RB75 / MGLOBL COMMON / RB76 / GH COMMON / RB77 / GX COMMON / RB78 / GY COMMON / RB79 / GZ COMMON / RB80 / HYBETA COMMON / RB81 / HDIAM COMMON / RB82 / HCSAA COMMON / RB83 / HDLEN COMMON / RB84 / HDX COMMON / RB85 / HDY COMMON / RB86 / HDZ COMMON / RB87 / HPRHO COMMON / RB88 / HPRHOE COMMON / RB89 / HMU COMMON / RB90 / HNU COMMON / RB91 / HCP COMMON / RB92 / HEPS COMMON / RB93 / HLOSCF COMMON / RB94 / HFF COMMON / RB95 / HWDOT COMMON / RB96 / HREYN COMMON / RB97 / HQFLOW COMMON / RB98 / HHX COMMON / RB99 / HHY COMMON / RB100 / HHZ COMMON / RB101 / HHXREF COMMON / RB102 / HHYREF COMMON / RB103 / HHZREF COMMON / RB104 / HDPHED COMMON / RB105 / HP1 COMMON / RB106 / HP2 COMMON / RB107 / HDTEMP COMMON / RB108 / HPHEAD COMMON / RB109 / PI COMMON / RB110 / GRAVTY COMMON / RB111 / BTINY COMMON / RB112 / HPERRM COMMON / RB113 / HMERRM COMMON / RB114 / HERRMX COMMON / RB115 / HYEPIS COMMON / RB116 / DTMAXH COMMON / RB117 / HYTIME COMMON / RB118 / HYOTIM COMMON / RB119 / HUNITS COMMON / RB120 / RSTIME COMMON / RB121 / HYHDEP COMMON / RB122 / HYMDEP COMMON / RB123 / HYPREP!!! COMMON / RB124 / TNODE COMMON / RB125 / SUMQ COMMON / RB126 / SUMCNV COMMON / RB127 / SUMRAD COMMON / RB128 / CLKDTMCC Usage:C TIME --> chronometer's readingC DT --> current time step


C TSTART --> simulation start timeC TSTOP --> simulation stop timeC EPSISS --> steady state convergence criterionC EPSIT --> transient convergence criterionC PERTUR --> perturbation parameterC PERTU2 --> 2 * PERTURC PERTSQ --> PERTUR * PERTURC DTMAX --> maximum allowed value of the time step, DTC RELAX --> current relaxation parameterC RELAXS --> steady state relaxation parameterC RELAXT --> transient relaxation parameterC TSFMIN --> time step factor for decreasing the time stepC TSFMAX --> time step factor for increasing the time stepC BETAEX --> explicit integration weighting factorC BETAIM --> implicit integration weighting factorC (note: BETAEX + BETAIM = 1.0)C DTOLD --> "old" time step valueC EFACT --> error factor (used to convert iterative deltaC into an estimated error)C QGLOBL --> constant per-unit-volume heat flux valueC SBC --> stephan-boltzman constantC SMALL --> a small value (~0.001)C TINY --> a near zero value (~1.E-30)C HUGE --> a very large value (~1.E+30)C QVECTP --> the heat flow into a node at T+PERTURC QVECTM --> the heat flow into a node at T-PERTURC GSUM --> summation of conductances for a nodeC GVALC --> summation of conductive resistor conductances forC a nodeC BETA --> user-input explicit/implicit weighting parameterC PCBAND --> phase change bandC DELMAX --> largest allowed iterative deltaC ERROR --> largest iterative deltaC DTP --> temporary time step variableC Q --> heat flow rateC T1 --> temperature at node 1 of resistorC T2 --> temperature at node 2 of resistorC T3 --> temperature at node 3 of resistorC GVALH --> conductance of convective resistorC CLOCK --> time at which next print dump will occurC EOLDST --> iterative delta (oldest)C ERROLD --> iterative delta (old)C DTPRED --> time step used for predictor equationC CP --> specific heat valueC BALNCE --> energy balanceC Q12 --> heat flow from resistor node 1 to node 2C Q21 --> heat flow from resistor node 2 to node 1C GVAL --> conductance of current resistorC QWAVE --> heat flow across spectral resistorC EMISS --> emissivity of radiative resistorC TAU --> transmissivity of radiative resistorC QSURF --> not usedC GVALS --> not usedC QSURFT --> not usedC GVALT --> not usedC TTMAC --> TMACROfunction "old" temperature value.C DELT --> phase change bisection method's interval size.C FOLD --> phase change bisection method's last nodalC heat flow value.C F11 --> Fraction of energy between lambda1-lambda2 for nodeC 1 of spectral resistors.C F22 --> Fraction of energy between lambda1-lambda2 for nodeC 2 of spectral resistors.C RMFLOW --> Mass flow rate set by advective resistors inC subroutine AFLOW.C EPSIT2 --> Transient iteration "cut-out" criteria.C TSAVE --> Temporary saved node temperature, usedC during transient phase change inner iterations.


482

C CPDELT --> Delta Temperature used for the integral of C Cp * dT. This can be used if an extremely rapidC variation of Cp with respect to Temperature isC expected, e.g., phase change problems.C QINPUT --> Total of all Q sources (QMACRO's + QBASE's).C DTMIN --> Minimum allowed time step for transient runs.C H --> Convection CoefficientC MINTMP --> Minimum allowed temperature calculated.C MAXTMP --> Maximum allowed temperature calculated.C BETMIN --> Minimum explicit/implicit weighting factorC BETMAX --> Maximum explicit/implicit weighting factorC PINITL --> Initial pressure for hydraulic networkC MGLOBL --> Globally assigned mass flow rate for hydraulic netC GH --> Gravity head used for pumps C GX --> Gravity in the principle x-axis directionC GY --> Gravity in the principle y-axis directionC GZ --> Gravity in the principle z-axis directionC HYBETA --> Compressibility term for hydraulic bounancyC HDIAM --> Hydraulic diameterC HCSAA --> Hydraulic crossectional areaC HDLEN --> Hydraulic length of elementC HHDX --> Hydraulic length of element along x axisC HHDY --> Hydraulic length of element along y axisC HHDZ --> Hydraulic length of element along z axisC HPRHO --> Hydraulic fluid density at nodeC HPRHOE --> Hydraulic fluid density of elementC HMU --> Hydraulic fluid viscosityC HNU --> Hydraulic fluid kinematic viscosityC HCP --> Hydraulic fluid specific heatC HEPS --> Hydraulic surface roughness of pipe elementsC HLOSCF --> Hydraulic loss coefficient of elementC HFF --> Hydraulic friction factorC HWDOT --> Hydraulic mass flow rateC HREYN --> Hydraulic Reynolds NumberC HQFLOW --> Hydraulic volumetric flow rateC HHX --> Hydraulic head along x axisC HHY --> Hydraulic head along y axisC HHZ --> Hydraulic head along z axisC HHXREF --> Hydraulic head reference along x axisC HHYREF --> Hydraulic head reference along y axisC HHZREF --> Hydraulic head reference along z axisC HDPHED --> Hydraulic head differential in elementC HP1 --> Hydraulic static pressure at node 1C HP2 --> Hydraulic static pressure at node 2C HDTEMP --> Temperature difference across hydraulic elementC HPHEAD --> Pump headC PI --> PI (3.14159....)C GRAVTY --> Gravity acceleration used in units conversionsC BTINY --> A big tiny value ( 1.0D-18 )C HPERRM --> Maximum ratio of iterative delta in static pressureC HMERRM --> Maximum ratio of iterative delta in mass flow rateC HERRMX --> Maximum ratio of iterative delta in hyraulic headC HYEPIS --> Maximum allowed ratio of hyraulic iterative deltaC DTMAXH --> Hyraulic time stepC HYTIME --> Hyraulic time for next updateC HYOTIM --> Time that last hyraulic solution was performedC HUNITS --> Units conversion value used for the hydraulicsC RSTIME --> Restart timeC HYHDEP --> Maximum allowed ratio of hyraulic iterative deltaC for the Hydraulic Dynamic HeadC HYMDEP --> Maximum allowed ratio of hyraulic iterative deltaC for the Hydraulic Mass Flow Rate ( MDOT )C HYPREP --> Maximum allowed ratio of hyraulic iterative deltaC for the Hydraulic PressureC TNODE --> Time-weighted temperature value used to evaluateC properties for capacitors.C CLKDTM --> Clock time for print stagging of Maximum time stepC


C############################################################################

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisULIBFOR Contents - Example User-Supplied Subroutines

484

ULIBFOR Contents - Example User-Supplied Subroutines

C############################################################################C #C This file contains dummy subroutines that can be altered by the user #C and included with the QTRAN thermal analysis module. These #C routines are called at key entry points in the calculation #C loop as well as during initialization phases, reading of the #C input data file, etc. The routines included are: #C #C ROUTINES: #C #C #C UAFLOW --> Called from AFLOW when a user material property has #C been specified for an advection conductor #C #C UCCPAC --> Called from CCAPAC when a user material property has #C beeb defined for either the capacitor density or #C specific heat. Even if the user properties are dummies #C to flag a user defined capacitance determination, the #C UPROP value must pass a value that will allow a #C capacitor evaluation prior to the user defining it. #C #C UCNDUC --> Called from CONDUC when a user material property has #C been defined for the thermal conductivity. Even if the #C user properties are dummies to flag a user defined #C conductance determination, the UPROP value must pass a #C value that will allow conductor evaluation prior to the #C user defining it. #C #C UEXITQ --> Called whenever EXITQ is called. This is just #C before the standard output routine qtran.dat is closed. #C Is called during error conditions as well as normal #C exits. The UFNSHD routine will be call just before #C this but only for normal exits. #C #C UFNSHD --> Called at the completion of a solution cycle when #C crunch is going to be exited. #C #C UHVAL --> Called from QTRAN subroutine CONV0, this #C subroutine is called whenever the user specifies #C a convection configuration type of 1000 or #C greater. This allows the user to build and #C maintain custom convection configurations. #C #C UINIT1 --> Called from QTRAN subroutine INIT1, this #C subroutine may be used to initialize any system #C arrays provided by the user. UINIT1 is called #C prior to reading in any input data. #C #C UINIT2 --> Called from QTRAN subroutine INIT2, this #C subroutine may be used to set up pointer tables #C or anything else that may need to be done after #C reading in the input data file(s). #C #C UINPUT --> Called from QTRAN subroutine INPUT, this #C subroutine may be used to read in customized #C data not normally found in QTRAN's input data #C file. It is called after QTRAN's normal input #C data has been read in. #C #C ULOOP1 --> Called from QTRAN subroutine RESET1, this #C subroutine may be used to perform any necessary #C housekeeping or calculations prior to beginning #C a steady state run or a transient time step. #

485Chapter 11: User-Supplied RoutinesULIBFOR Contents - Example User-Supplied Subroutines

C #C ULOOP2 --> Called from QTRAN subroutine RESET2, this #C subroutine may be used to perform any necessary #C housekeeping or calculations prior to beginning #C an iteration for either steady state or #C transient runs. #C #C ULOOP3 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called at the beginning of #C calculations for each node for each iteration. #C Custom resistor types are one example of things #C that might be appropriate for ULOOP3. #C #C ULOOP4 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called at the end of calculations #C for each node for each iteration immediately #C after the temperature for that node has been #C updated. #C #C ULOOP5 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called at the end of each #C steady state or transient iteration. This #C routine can be used to perform auxiliary #C calculations that must be performed in parallel #C with the thermal calculations, e.g., fluid flow #C calculations, mass transport calculations, or #C anything else that is appropriate. #C #C ULOOP6 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called only after a steady state #C calculation has converged. #C #C ULOOP7 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called after each transient time #C step. #C #C UMCRPR --> Same as UMICRO call except the material property #C parameters are passed as well. This enables the user #C directly use material properties without having to #C provide wrappers to properly define the dimensions #C #C UMICRO --> Called from QTRAN subroutine FLIB, this #C subroutine is called whenever the user specifies #C a microfunction option of 1000 or greater. This #C allows the user to build and maintain custom #C heat source or temperature boundary condition #C functions that are too exotic to be covered by #C any of the existing QTRAN microfunctions. #C #C UOUTPT --> Called from QTRAN subroutine QFLOW, this #C subroutine may be used to print out customized #C data immediately after the temperature data is #C printed out for either transient or steady state #C runs. UOUTPT data is printed out prior to the #C resistor data. #C #C UPCPAC --> Called from CCAPAC when a user material property has #C beeb defined for either the capacitor density or #C specific heat. Even if the user properties are dummies #C to flag a user defined capacitance determination, the #C UPROP value must pass a value that will allow a #C capacitor evaluation prior to the user defining it. #C This routine is for users to be able to define and #C control the phase change energy. #C #C UPLOT --> Called from CRUNCH after every converged #C transient or steady state solution. #C Specific plot information could be created and #


486

C written to a file here. #C #C UPRNTC --> Called from QTRAN subroutine TPSET, this #C subroutine will inform the users if a print had #C occured on the previous time step. It can be #C used by the user to force a print at the current #C time step. #C #C UPROP --> Called from QTRAN subroutine PROPS, this #C subroutine is called whenever the user specifies #C a material property evaluation option (IEVAL) of #C U (User-Coded). This allows the user to build #C and maintain a library of custom material #C property subroutines for very exotic materials #C or applications not covered by any of QTRAN's #C pre-coded material property evaluation options. #C #C URADAT --> Called from RADIAT. Allows the user to modify #C radiation conductors; however, they must have some #C way to identify the conductor to change. Either by #C type, node IDs, material properties or some #C combination of them. #C #C URSTRT --> Called from QTRAN subroutine GETRST if QTRAN #C is resuming execution from a restart file. #C #C USOL --> Called from QTRAN subroutine CRUNCH if the #C QTRAN solution option SOL = 1000. You may #C then invoke any solution system you wish. #C QTRAN's solvers will be bypassed. Execution #C passes through CRUNCH to RESET1, then USOL, #C and then SSTATE or TRANS, depending upon whether #C the problem being run is steady state or #C transient. #C #C UWAVER --> Called from WAVER. Allows the user to modify #C radiation conductors; however, they must have some #C way to identify the conductor to change. Either by #C type, node IDs, material properties or some #C combination of them. Same as URADAT except this is for #C wavelength dependent radiation. #C #C #C NOTE: PATRAN CUSTOMERS MAY MODIFY THE ROUTINES IN THIS FILE #C IN ANY MANNER THEY SEE FIT. HOWEVER, IT IS UP TO THE #C CUSTOMERS TO MAINTAIN ANY SUCH MODIFICATIONS. PDA #C ENGINEERING WILL NOT BE RESPONSIBLE FOR THE #C CONSEQUENCES INCURRED DUE TO THE MODIFICATION OF THESE #C ROUTINES. #C #C############################################################################CC############################################################################CC############################################################################C #C S U B R O U T I N E A F L O W #C #C############################################################################C SUBROUTINE UAFLOW( RMDOT, ICPFLO, COEFF, EXPO )CC############################################################################CC This user subroutine can be used by the user to compute theC mass flow resistor heat flows.CC nrf is the heat flow resistor i.d. number.


C rmdot is the vector that stores the mass flow rate data.C icpflo is the vector that stores the specific heat material propertyC i.d. number for the flow resistor.C coeff and expo are the material property arrays for subroutine props.C t1 is the temperature of node #1 of the flow resistor.C t2 is the temperature of node #2 of the flow resistor.C q12 is the heat flow from node #1 to node #2 of the resistor.C q21 is the heat flow from node #2 to node #1 of the resistor.C since "upwind" differencing is used, one of the two heatC flows will always be zero (the upstream node will neverC have heat flowing to it from the downstream node.)C rmflow is the computed mass flow rate.CCC##############################################################################CC > > > > > MODIFICATION HISTORY < < < < <CC Modification: Calculate the energy transferred as the difference inC the energy state at the two end points rather than the averageC movement between the two points.C By: Haddock Date: 5 February 1991CC Modification: Energy state at the end points must be integratedC from the base reference state. If we are only interested inC energy movement, then we can integrate between the two points.C By: Haddock Date: 13 February 1992CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################C double_precision T1 double_precision T2 double_precision CP double_precision Q12 double_precision Q21 double_precision GVAL double_precision RMFLOWC INTEGER NRFC COMMON / IB39 / NRF


488

C COMMON / RB36 / T1 COMMON / RB37 / T2 COMMON / RB44 / CP COMMON / RB46 / Q12 COMMON / RB47 / Q21 COMMON / RB48 / GVAL COMMON / RB62 / RMFLOWCC############################################################################C define call list variablesC INTEGER ICPFLO( J30, 2 )C double_precision RMDOT(*), COEFF( J3, J4 ), EXPO( J3, J4 )CC############################################################################C Declare the local variables.C double_precision RM1, RM2, DIFFT double_precision CPEVAL double_precision PROPSCC############################################################################C Declare external functionsC EXTERNAL CPEVAL EXTERNAL PROPSCC############################################################################CC Check the flow direction, and then calculate the appropriate heatC flow from the upstream node to the downstream node asC follows:C (1) compute the specific heat value CPC (2) compute the conductance GVAL = mass flow rate * CPC (3) compute the heat flow from the upstream node to theC downstream node, and then set the heat flow from theC downstream node to the upstream node to zeroCC############################################################################C!C CP = CPEVAL( T1, T2, COEFF, EXPO, ICPFLO(NRF,1) )C!C RMFLOW = RMDOT(NRF)C!C IF(ICPFLO(NRF,2).NE.0) THENC!C RM1 = RMFLOW * PROPS( COEFF, EXPO, T1, ICPFLO(NRF,2) )!C RM2 = RMFLOW * PROPS( COEFF, EXPO, T2, ICPFLO(NRF,2) )!C RMFLOW = ( RM1 + RM2 ) * 0.5D+00!C ENDIFC!C GVAL = ABS( RMFLOW * CP )C!C DIFFT = ( T1 - T2 )C!C IF(RMFLOW.GE.0.D+00) THEN!C Q12 = GVAL * DIFFT!C Q21 = 0.0D+00!C ELSE!C Q21 = GVAL * (-DIFFT)!C Q12 = 0.0D+00!C ENDIFCC############################################################################C RETURN


ENDCC############################################################################C #C S U B R O U T I N E U C C P A C #C #C############################################################################C SUBROUTINE UCCPAC( CT, CSUM, C, CP, CM, 1 ICPNT, CNPNT, CPROP, CRHO, CVOL, 2 ICP, IRHO, COEFF, EXPO, IPERTR, 3 OT, TNODE, TP, TM, 4 T, TPLUSP, TMNUSP, 5 TDIFF, TDIFFP, TDIFFM )CC############################################################################C #C This subroutine performs all capacitance when a user defined #C property has be defined. #C #C############################################################################CCC declare the subroutine arguments, where:c ct --> thermal capacity of this capacitor.c csum --> sum of all capacitances to this node.c c --> capacitance energy at new temperature.c cp --> capacitance energy at plus perturbed temperature.c cm --> capacitance energy at minu sperturbed temperature.c icpnt --> index to capacitor in cnpnt array.c cnpnt --> array containing the capacitor i.d. numbers for eachc node. all zeros are packed out.c cprop --> array of specific heat mid numbers for each capacitor.c crho --> array of density mid numbers for each capacitor.c cvol --> array containing capacitor volumes.c icp --> specific heat material property type.c irho --> density material property type.c coeff --> material property data array.c expo --> material property data array.c ipertr --> perturbation flag.c ot --> old temperature value.c tnode --> weighted new temperature.c tp --> weighted new temperature and plus perturbation.c tm --> weighted new temperature and minus perturbation.c t --> new temperature value.c tplusp --> new temperature value plus perturb.c tmnusp --> new temperature value minus perturb.c tdiff --> temperature change.c tdiffp --> temperature change plus perturb.c tdiffm --> temperature change minus perturb.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXP


490

C COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the arrays.C DOUBLE PRECISION CP DOUBLE PRECISION TNODE DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 ) DOUBLE PRECISION CVOL(*)C INTEGER IPERTR INTEGER ICPNT INTEGER CNPNT(*), CPROP(*), CRHO(*)CC############################################################################CC Some common blocksCC*C*RLH INTEGER ICMPIDC*C*RLH INTEGER IRMPIDC*C*RLH INTEGER MPIDC*C*RLH INTEGER MIDCC*C*RLH COMMON / IA45 / MID(1)CCC############################################################################CC Declare the local variables.C DOUBLE PRECISION CSUM, C, TP, TM, TDIFF DOUBLE PRECISION TDIFFP, TDIFFM, CT, OT, T DOUBLE PRECISION CM DOUBLE PRECISION TPLUSP, TMNUSP DOUBLE PRECISION CPEVAL, PROPS DOUBLE PRECISION LCP DOUBLE PRECISION LRHOC INTEGER ICP, IRHOCC*C*RLH DOUBLE PRECISION LOCTCC############################################################################C Declare external functionsCC*C*RLH EXTERNAL CPEVAL, PROPSCC#######################################################################CCC-----------------------------------------------------------------------C! Note: If a user defined heat capacity or density has been defined! as a user defined material property, then the uprops routine has! been called and the heat capacity was determined with the ! following procedure. If the uprop for the given uprop is a! dummy only to flag a user defined heat capacity, then the user! can recalculate the heat capacity or mark appropriate modifications.C


C#######################################################################CC this section is for non-phase change behavior. computeC the nodal capacitance energy, where:C c = cp * rho * vol * dT. then do the same thingC for the perturbed temperature values. note thatC the C, CP, and CM variables will store the sum ofC all capacitance heat flows for the node. theC variable csum will store the sum of all nodalC capacitances, and will be used for computingC explicit stable time steps.CC*C*RLH ICMPID = MID( ICP )C*C*RLH IRMPID = MID( IRHO )CC*C*RLH IF( ICMPID .EQ. 303105 .OR. ICMPID .EQ. 370705 .OR.C*C*RLH 1 IRMPID .EQ. 303104 .OR. IRMPID .EQ. 370704 ) THENCC*C*RLH IF( IPERTR .EQ. 0 ) THENCC............................................................................! Evaluate at temperature T!C*C*RLH LOCT = TCC*C*RLH ELSE IF( IPERTR .EQ. 1 ) THENCC............................................................................! Evaluate at temperature plus perturbed temperature.!C*C*RLH LOCT = TPLUSPCC*C*RLH ELSE IF( IPERTR .LE. -1 ) THENCC............................................................................! Evaluate at temperature minus perturbed temperature.CC*C*RLH LOCT = TMNUSPCC*C*RLH END IFCC*C*RLH IF( ICMPID .EQ. 303105 .OR. ICMPID .EQ. 370705 ) THENCC*C*RLH LCP = EXPO( ICP, 2 )CC*C*RLH ELSECC*C*RLH LCP = CPEVAL( OT, LOCT, COEFF, EXPO, ICP )CC*C*RLH END IFCC*C*RLH IF( IRMPID .EQ. 303104 .OR. IRMPID .EQ. 370704 ) THENCC*C*RLH LRHO = EXPO( IRHO, 2 )CC*C*RLH ELSECC*C*RLH LRHO = PROPS( COEFF, EXPO, TNODE, IRHO )CC*C*RLH END IFCC*C*RLH IF( IPERTR .EQ. 0 ) THENCC............................................................................! Evaluate at temperature T!C*C*RLH CT = LCP * CVOL(ICPNT) * LRHOC


492

C*C*RLH ELSE IF( IPERTR .EQ. 1 ) THENCC............................................................................! Evaluate at temperature plus perturbed temperature.!C*C*RLH CT = LCP * CVOL(ICPNT) * LRHOCC*C*RLH ELSE IF( IPERTR .LE. -1 ) THENCC............................................................................! Evaluate at temperature minus perturbed temperature.CC*C*RLH CT = LCP * CVOL(ICPNT) * LRHOCC*C*RLH END IFCC*C*RLH END IFCC############################################################################C RETURN ENDCC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,CC compute q conducted from node 1 to node 2 (qc).CC*C*RLH QC = GVAL * ( T1 - T2 )CC*C*RLH END IFCC Other options can be defined for different sections of the code.CC****************************************************************************C RETURN ENDCC############################################################################C #C S U B R O U T I N E U E X I T Q #C #C############################################################################C SUBROUTINE UEXITQCC............................................................................CC UEXITQ --> Called whenever EXITQ is called. This is justC before the standard output routine qtran.dat is closed.C Is called during error conditions as well as normalC exits. The UFNSHD routine will be call just beforeC this but only for normal exits.CC############################################################################C IMPLICIT NONECC############################################################################CC............................................................................C RETURN ENDCCC############################################################################C #


C S U B R O U T I N E U F N S H D #C #C############################################################################C SUBROUTINE UFNSHDCC............................................................................CC UFNSHD --> Called at the completion of a solution cycle whenC crunch is going to be exited.CC############################################################################C IMPLICIT NONECC############################################################################CC............................................................................C RETURN ENDCCCC############################################################################C #C PATRAN Customers May Modify This Routine In Any Manner They See Fit. #C However, It Is The Customer's Responsibility To Maintain Any Such #C Modifications. PDA Engineering Will Not Be Responsible For The #C Consequences Incurred Due To The Modification Of This Routine. #C #C############################################################################C #C S U B R O U T I N E U H V A L #C #C############################################################################C SUBROUTINE UHVAL( ICFIG, IRESIS, COEFF, EXPO, JPROP, GP, T1, T2, $ GVALH, Q, LOGP, J1, J2, J3, J4, J6 )CC############################################################################CC This subroutine is meant to be used as an example routine for thoseC hardy souls who feel the urge to write their own User-CodedC convection configuration library.CC############################################################################C IMPLICIT NONECC############################################################################CC ARGUMENTS:CC icfig --> configuration type of resistorC iresis --> convective resistor i.d. numberC coeff --> material property data arrayC expo --> material property data arrayC jprop --> list of MPID numbers assigned to convective resistorsC gp --> list of geometric property data assigned toC convective resistorsC t1 --> temperature of node #1 of the convective resistorC (in degrees ICCALC)C t2 --> temperature of node #2 of the convective resistorC (also in degrees ICCALC)C gvalh --> "conductance" of the resistor ( product of h * Area )C q --> heat flow from node 1 to node 2C logp --> resistor data print flag. if .true., resistor data


494

C is requested to be printed. if .false., no requestC has been made.C j1-j6 --> array dimensionsCC############################################################################CC Declare the arrays.C INTEGER J1, J2, J3, J4, J6C INTEGER JPROP(J1,J2)C DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 ), GP( J1, J6 )CC############################################################################CC Declare the other arguments.C LOGICAL LOGPC INTEGER ICFIG, IRESISC DOUBLE PRECISION T1, T2, GVALH, QCC############################################################################CC Declare the logical unit number and its common block for the outputC file.C INTEGER IOC COMMON / IB33 / IOCC############################################################################CC Declare the common block for the film coefficient H. You must be sureC to calculate the value of the convective film coefficient and store itC in the common block variable H. This value will then be used whenC computing the average nodal H value which is placed in the nodalC results files and which can be used for post-processing.C DOUBLE PRECISION HC COMMON / RB69 / HCC############################################################################C #C The preceeding is standard boiler plate for subroutine UHVAL and #C should ALWAYS be included exactly as is. #C #C############################################################################C #C The following shows how to set up 3 seperate configurations, and is #C entirely optional. The following guidelines do apply, #C however: #C (1) ALWAYS return GVALH as the product of h * Area. #C Failure to do this will result in driving the #C SNPSOR equation solver off the deep end. #C (2) ALWAYS return Q as the heat transfer from node 1 #C to node 2, i.e., Q = h * Area * ( T1 - T2 ) #C (3) ALWAYS calculate and store the film coefficient #C in the common block variable H. #C #C############################################################################CC Declare the local variables.CC*C INTEGER CONFIG


CC*C DOUBLE PRECISION AREA, RHO, MU, K, CP, EXPAN, TBAR, TFILM,C*C $ DTEMP, G, L, PR, RA, HLOW, RAL, HHIGHC*C DOUBLE PRECISION PROPSC*CC*C EXTERNAL PROPSCC############################################################################CC Set up the logic to choose between user-supplied configurationsC 1000, 1001, and 1002. The computed go-to's are frequentlyC significantly faster than nested if-then-else structuresC for large lists. The computed go-to structure below mayC easily be expanded to handle many more configurations. TheC logic assumes that you have decided to use user-suppliedC configurations 1000, 1001, and 1002. The first thing doneC is to subtract 999 from the ICFIG configuration value. ThusC if ICFIG = 1000, CONFIG will be set to 1. The go-to will thenC branch to stmt number 1000. The other configurations areC handled identically, as is obvious from the following coding.CC Note that while all coding is currently in this routine, it is easyC (and better practice) to modularize each configuration intoC its own subroutine, e.g., UHVAL1, UHVAL2, etc., which wouldC then by called by this master routine UHVAL. UHVAL would thenC contain nothing but the selection logical (the computed go-to)C and calls to your list of routines.CC*C CONFIG = ICFIG - 999CC*C GO TO (1000,1001,1002),CONFIGCC############################################################################CC Set up the target statement label for configuration 1000.CC*C 1000 CONTINUECC This configuration is going to be identical to QTRAN libraryC configuration number 31, "Generic Constant H Value."CC Get the resistor surface area. This we have decided to store asC Geometric Property number 1. Geometric properties for thisC resistor (number IRESIS) will be stored in the IRESIS'th rowC of the GP array. GP #1 will be in GP(IRESIS,1), GP #2 willC be in GP(IRESIS,2), etc.CC*C AREA = GP(IRESIS,1)CC............................................................................CC Get the resistor h value. This we have decided to store asC Geometric Property number 2.CC*C H = GP(IRESIS,2)CC............................................................................CC Compute the conductance. This is a requirement and its value willC be returned to the calling routine.CC*C GVALH = H * AREACC............................................................................CC Compute the heat transfer from node 1 to node 2. This is a requirementC and its value will be returned to the calling routine.C


496

C*C Q = GVALH * ( T1 - T2 )CC............................................................................CC Check to see if resistor data is being printed out. If not, return.C If so, write out the h value and area.CC*C IF(.NOT.LOGP) RETURNCC............................................................................CC The following two QTRAN subroutines print out the h value andC resistor area very easily.CC*C CALL HOUT( H )C*C CALL AREAO( AREA )CC............................................................................CC Return to the calling routine.CC*C RETURNCC############################################################################CC Set up the target statement label for configuration 1001.CC*C 1001 CONTINUECC This configuration will be identical to configuration number 29,C "Generic Variable H value, H = H(TBAR)." For this property,C it is assumed that the h value is to be taken directly fromC the material property specified by JPROP #1.CC First, get the TBAR value.CC*C TBAR = ( T1 + T2 ) / 2.0D+00CC............................................................................CC Second, get the JPROP #1 number. This will be stored in the JPROPC array as JPROP(IRESIS,1). JPROP #2 would be stored inC JPROP(IRESIS,2), and so on. Normally, MPID numbers are storedC in the JPROP array. We will therefore call JPROP #1 by theC name MPID.CC*C MPID = JPROP(IRESIS,1)CC............................................................................CC Third, get the h value. This is done by a call to QTRAN subroutineC PROPS. PROPS is used to evaluate all of QTRAN's materialC property values. NOTE: If MPID is negative, subroutine PROPSC will ignore it and will use the current TIME value as theC evaluation argument. Since you are doing the coding,C you may of course use any argument that you wish.CC*C H = PROPS( COEFF, EXPO, TBAR, MPID )CC............................................................................CC Fourth, get the surface area for the resistor. This is assumed toC have been entered as GP #1, although you of course may enterC it as any GP value that you wish (or get it from anywhereC else that you are able to).CC*C AREA = GP(IRESIS,1)C


C............................................................................CC Compute the conductance ( h * Area ).CC*C GVALH = H * AREACC............................................................................CC Compute the heat transferred from node 1 to node 2.CC*C Q = GVALH * ( T1 - T2 )CC............................................................................CC Check to see if resistor data is being printed out. If not, return.C If so, write out the h value and area.CC*C IF(.NOT.LOGP) RETURNCC............................................................................CC The following two QTRAN subroutines print out the h value andC resistor area very easily.CC*C CALL HOUT( H )C*C CALL AREAO( AREA )CC............................................................................CC Return to the calling routine.CC*C RETURNCC############################################################################CC Set up the target statement label for configuration 1002.CC*C 1002 CONTINUECC Now that we're done with the warm-up exercises, let's do a semi-seriousC convection configuration. Let's assume that:CC h = GP#5 { Rayleigh < 1.5E+05 }CC h = (GP#2) * Rayleigh**(GP#3) * Prandtl ** (GP#4) { otherwise }CC First, compute the necessary material properties.CC Assume: density = jprop #1C viscosity = jprop #2C coeffecient of expansion = jprop #3C specific heat = jprop #4C conductivity = jprop #5CC Compute the film temperature.CC*C TFILM = ( T1 + T2 ) * 0.5D+00CC Calculate the fluid properties. Since negative values forC material properties would likely make our calculationsC blow up (as would a zero value), we will protect ourselvesC just a little bit and take the absolute value of the materialC properties and then fudge them by 1.0D-10 (the D exponentC implies double precision).CC*C AREA = GP( IRESIS, 1 )CC*C RHO = DABS( PROPS( COEFF, EXPO, TFILM, JPROP(IRESIS,1)) ) +


498

C*C $ 1.D-10C*C MU = DABS( PROPS( COEFF, EXPO, TFILM, JPROP(IRESIS,2)) ) +C*C $ 1.D-10C*C EXPAN = DABS( PROPS( COEFF, EXPO, TFILM, JPROP(IRESIS,3)) ) +C*C $ 1.D-10C*C CP = DABS( PROPS( COEFF, EXPO, TFILM, JPROP(IRESIS,4)) ) +C*C $ 1.D-10C*C K = DABS( PROPS( COEFF, EXPO, TFILM, JPROP(IRESIS,5)) ) +C*C $ 1.D-10CC............................................................................CC Calculate the Prandtl number.CC*C PR = MU * CP / KCC............................................................................CC Calculate the Rayleigh number.CC First, get the gravitational constant entered as GP #6. Then getC the characteristic length L used by the Rayleigh number.C GP #7 will be the shortest distance between the resistor areaC and the surface edge whose boundary layer thickness is zero,C and GP #8 will be the longest distance between the resistorC area and the same edge. Note that adding GP #7 and GP #8 isC one way of placing the resistor surface at the center of anC artificially constructed effective characteristic length.C This assumes that h(L) varies linearly from h(0) to h(L),C and is a first order approximation only. Although not aC particularly tremendous approximation, it does limit correctlyC when GP #7 = 0 and GP #8 = L and it is a whole lot better thanC simply assuming that h is constant across the whole convectiveC surface. There are better ways, but this way is especiallyC easy.CC*C G = GP(IRESIS,6)C*C L = GP(IRESIS,7) + GP(IRESIS,8)CC Compute the temperature difference between the surface and the freeC stream fluid.CC*C DTEMP = DABS( T1 - T2 ) + 1.0D-10CC*C RA = DABS( G * EXPAN * ( RHO * RHO ) * ( L * L * L ) * DTEMP /C*C $ ( MU * MU ) * PR ) + 1.0D-10CC............................................................................CC We now have a Rayleigh number. Check to see if we are in range ofC the first correlation or the second.C NOTE: Most iterative codes (QTRAN included) do not appreciate stepC function discontinuities such as would be generated by aC transition NUMBER. We will therefore use an arbitraryC transition RANGE. What this means is that instead of usingC the transition number of 1.5E+05, we will smear the transitionC arbitrarily over the range of 1.3E+05 to 1.7E+05. Since stepC function discontinuities do not really occur anyway (laminarC to turbulent transitions really do occur over a range) there isC even some physical justification for this.CC First, calculate both the low range and the high range h values.CC*C HLOW = GP(IRESIS,5)CC , , , , , , , , , , , , , , , , , , , , , , , , ,CC Limit the RA value to the range of the high correlation. This is done


C for two reasons. One, it limits the correlation to a validC Rayleigh number range. Two, it provides us with anC interpolation point for the transition range. If the lowerC correlation were not a constant, we would have performed theC same type of limiting operation with it.CC*C RAL = DMAX1( RA, 1.7D+05)CC*C HHIGH = GP(IRESIS,2) * RAL ** GP(IRESIS,3) * PR ** GP(IRESIS,4)CC , , , , , , , , , , , , , , , , , , , , , , , , ,CC Next, check to see if we are in the low range, high range, orC transition regime. If we are in the transition regime,C we will interpolate. This can all be done transparently byC simply calling QTRAN subroutine INTERP. The calling sequenceC for INTERP is:CC CALL INTERP( low_transition_range, low_h_value,C $ high_transition_range, high_h_value,C $ Rayleigh (or whatever), returned_h_value )CC INTERP does more than just interpolate. If the RayleighC number is below the low_transition_range, INTERP will returnC the low_h_value. If above the high_transition_range, INTERPC will return the high_h_value. INTERP can obviously be usedC in the same manner for Reynolds number, Prandtl number, andC other transition range calculations.CC*C CALL INTERP( 1.3D+05, HLOW, 1.7D+05, HHIGH, RA, H )CC............................................................................CC Compute the conductance.CC*C GVALH = H * GP(IRESIS,1)CC............................................................................CC Compute the heat transferred from node #1 to node #2.CC*C Q = GVALH * ( T1 - T2 )CC............................................................................CC Check to see if resistor data is being printed out. If not, return.C If so, write out the h value and area.CC*C IF( .NOT.LOGP ) RETURNCC............................................................................CC The two QTRAN subroutines HOUT and AREAO print out the h value andC resistor area very easily. You may also write out any otherC data that you wish, such as Rayleigh number, Prandtl number,C etc.CC*C CALL HOUT( H )CC*C WRITE(IO,1) MU, CP, K, PRC*C 1 FORMAT(' Viscosity:',T20,1PD20.10/' Specific Heat:',T20,D20.10/C*C $' Conductivity:',T20,D20.10 / 'Prandtl No.:', T20, D20.10 )CC*C WRITE(IO,2) RHO, TFILM, G, EXPAN, RAC*C 2 FORMAT(' Density:',T20,1PD20.10/' Film Temp:',T20,D20.10/C*C $' Grav Constant:',T20,D20.10/' Coeff Expan:',T20,D20.10 /C*C $' Rayleigh:', T20, D20.10 )C


500

C*C CALL AREAO( AREA )CC............................................................................CC Return to the calling routine.C RETURNCC############################################################################C ENDCC############################################################################C #C S U B R O U T I N E U I N I T 1 #C #C############################################################################C SUBROUTINE UINIT1CC............................................................................CC UINIT1 --> Called from QTRAN subroutine INIT1, thisC subroutine may be used to initialize any systemC arrays provided by the user. UINIT1 is calledC prior to reading in any input data.CC############################################################################C IMPLICIT NONECC############################################################################CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U I N I T 2 #C #C############################################################################C SUBROUTINE UINIT2CC............................................................................CC UINIT2 --> Called from QTRAN subroutine INIT2, thisC subroutine may be used to set up pointer tablesC or anything else that may need to be done afterC reading in the input data file(s).CC############################################################################C IMPLICIT NONECC############################################################################CC Load the dimension definitions - ( from common.dims )C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43,


$ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXP

CC............................................................................CCC............................................................................CC RETURN ENDC############################################################################C #C This file contains dummy subroutines that can be altered by the user #C and included with the QTRAN thermal analysis module. These #C routines are called at key entry points in the calculation #C loop as well as during initialization phases, reading of the #C input data file, etc. The routines included are: #C #C ROUTINES: #C #C UINPUT --> Called from QTRAN subroutine INPUT, this #C subroutine may be used to read in customized #C data not normally found in QTRAN's input data #C file. It is called after QTRAN's normal input #C data has been read in. #C #C UOUTPT --> Called from QTRAN subroutine QFLOW, this #C subroutine may be used to print out customized #C data immediately after the temperature data is #C printed out for either transient or steady state #C runs. UOUTPT data is printed out prior to the #C resistor data. #C #C UINIT1 --> Called from QTRAN subroutine INIT1, this #C subroutine may be used to initialize any system #C arrays provided by the user. UINIT1 is called #C prior to reading in any input data. #C #C UINIT2 --> Called from QTRAN subroutine INIT2, this #C subroutine may be used to set up pointer tables #C or anything else that may need to be done after #C reading in the input data file(s). #C #C ULOOP1 --> Called from QTRAN subroutine RESET1, this #C subroutine may be used to perform any necessary #C housekeeping or calculations prior to beginning #C a steady state run or a transient time step. #C #C ULOOP2 --> Called from QTRAN subroutine RESET2, this #C subroutine may be used to perform any necessary #C housekeeping or calculations prior to beginning #C an iteration for either steady state or #C transient runs. #C #C ULOOP3 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called at the beginning of #


502

C calculations for each node for each iteration. #C Custom resistor types are one example of things #C that might be appropriate for ULOOP3. #C #C ULOOP4 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called at the end of calculations #C for each node for each iteration immediately #C after the temperature for that node has been #C updated. #C #C ULOOP5 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called at the end of each #C steady state or transient iteration. This #C routine can be used to perform auxiliary #C calculations that must be performed in parallel #C with the thermal calculations, e.g., fluid flow #C calculations, mass transport calculations, or #C anything else that is appropriate. #C #C ULOOP6 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called only after a steady state #C calculation has converged. #C #C ULOOP7 --> Called from QTRAN subroutine CRUNCH, this #C subroutine is called after each transient time #C step. #C #C UHVAL --> Called from QTRAN subroutine CONV0, this #C subroutine is called whenever the user specifies #C a convection configuration type of 1000 or #C greater. This allows the user to build and #C maintain custom convection configurations. #C #C UMICRO --> Called from QTRAN subroutine FLIB, this #C subroutine is called whenever the user specifies #C a microfunction option of 1000 or greater. This #C allows the user to build and maintain custom #C heat source or temperature boundary condition #C functions that are too exotic to be covered by #C any of the existing QTRAN microfunctions. #C #C UPROP --> Called from QTRAN subroutine PROPS, this #C subroutine is called whenever the user specifies #C a material property evaluation option (IEVAL) of #C U (User-Coded). This allows the user to build #C and maintain a library of custom material #C property subroutines for very exotic materials #C or applications not covered by any of QTRAN's #C pre-coded material property evaluation options. #C #C URSTRT --> Called from QTRAN subroutine GETRST if QTRAN #C is resuming execution from a restart file. #C #C USOL --> Called from QTRAN subroutine CRUNCH if the #C QTRAN solution option SOL = 1000. You may #C then invoke any solution system you wish. #C QTRAN's solvers will be bypassed. Execution #C passes through CRUNCH to RESET1, then USOL, #C and then SSTATE or TRANS, depending upon whether #C the problem being run is steady state or #C transient. #C *C UPLOT --> Called from CRUNCH after every converged *C transient or steady state solution. *C Specific plot information could be created and *C written to a file here. *C #C NOTE: PATRAN CUSTOMERS MAY MODIFY THE ROUTINES IN THIS FILE #


C IN ANY MANNER THEY SEE FIT. HOWEVER, IT IS UP TO THE #C CUSTOMERS TO MAINTAIN ANY SUCH MODIFICATIONS. PDA #C ENGINEERING WILL NOT BE RESPONSIBLE FOR THE #C CONSEQUENCES INCURRED DUE TO THE MODIFICATION OF THESE #C ROUTINES. #C #C############################################################################C############################################################################C############################################################################C #C S U B R O U T I N E U I N P U T #C #C############################################################################C SUBROUTINE UINPUT( IINU, IOU, LNUM )CC............................................................................CC UINPUT --> Called from QTRAN subroutine INPUT, thisC subroutine may be used to read in customizedC data not normally found in QTRAN's input dataC file. It is called after QTRAN's normal inputC data has been read in.CC ARGUMENTS:C IINU --> logical unit number for QTRAN's input data file.C IOU --> logical unit number for QTRAN's output data file.C LNUM --> line number of QTRAN's input data file whenC this routine was called. It is suggested thatC the user keep track of line numbers in the inputC data file so that when an error is encounteredC you can write a diagnostic message to the outputC and/or status files informing the user which lineC number the error occurred on.CC############################################################################C IMPLICIT NONECC############################################################################C INTEGER IINU, IOU, LNUMCC............................................................................CC Any read statements that you wish to use may be included in thisC section of the routine in ANSI standard Fortran.CC You will have to set up your own common blocks to store this data in,C since no data can be passed back to QTRAN or any of yourC user-supplied routines through the argument list of thisC subroutine. For example, suppose that you wanted to read dataC into a group of arrays called UA1, UA2, and UA3. The methodC of doing this is as follows:CC {1} Set up common blocks for each array.C {2} Read in the data into each of these arrays.C {3} Return to the calling routine.CC Example code for this is as follows. Note that the code isC commented out. Also, assume for the moment that each arrayC is 100 elements long.CC............................................................................CC Declare the common blocks and arrays.CC INTEGER MAXBLK


504

CC PARAMETER ( MAXBLK = 100 )CC DOUBLE PRECISION UA1, UA2, UA3CC COMMON / UB1 / UA1( MAXBLK )C COMMON / UB2 / UA2( MAXBLK )C COMMON / UB3 / UA3( MAXBLK )CC INTEGER ICC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,CC Read in MAXBLK lines of UA1, UA2, and UA3 data.CC DO 1 I=1,MAXBLKC READ( IINU, 2, ERR=900, END=999 ) UA1(I), UA2(I), UA3(I)C 2 FORMAT( 3G20.10 )C LNUM = LNUM + 1C 1 CONTINUECC Return to the calling routine.CC RETURNCC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,CC 900 CONTINUECC This section would be for when a format error was encountered.C Write out an error message and quit.CC WRITE( IOU, 901 ) LNUMCC 901 FORMAT(//' ***>>> ERROR <<<***'//C $' An error has occurred while reading in data for User-Supplied'/C $' subroutine UINPUT. The error occurred on line number',I10,'.'/C $/' ***>>> EXECUTION TERMINATING <<<***'//)CC CALL EXITQCC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,CC 999 CONTINUECC This section would be for when an unexpected end-of-file occurredC while trying to read in the data. Write out an error messageC and quit.CC WRITE( IOU, 998 ) LNUMC WRITE( IOU, 998 ) LNUMCC 998 FORMAT(//' ***>>> ERROR <<<***'//C $' An unexpected END-OF-FILE occurred while reading in data in'/C $' User-Supplied subroutine UINPUT. The error occurred on line'/C $' number',I10,'.'//' ***>>> EXECUTION TERMINATING <<<***'//)CC CALL EXITQCC............................................................................C ENDCC############################################################################C #C S U B R O U T I N E U L O O P 1 #C #C############################################################################


C SUBROUTINE ULOOP1( COEFF, EXPO )CC............................................................................CC ULOOP1 --> Called from QTRAN subroutine RESET1, thisC subroutine may be used to perform any necessaryC housekeeping or calculations prior to beginningC a steady state run or a transient time step.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the argumentsC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )CC############################################################################CCC............................................................................CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U L O O P 2 #C #C############################################################################C SUBROUTINE ULOOP2( COEFF, EXPO )CC............................................................................CC ULOOP2 --> Called from QTRAN subroutine RESET2, thisC subroutine may be used to perform any necessaryC housekeeping or calculations prior to beginning


506

C an iteration for either steady state orC transient runs.CCC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the argumentsC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )CC############################################################################CC............................................................................CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U L O O P 3 #C #C############################################################################C SUBROUTINE ULOOP3( COEFF, EXPO )CC............................................................................CC ULOOP3 --> Called from QTRAN subroutine CRUNCH, thisC subroutine is called at the beginning ofC calculations for each node for each iteration.C Custom resistor types are one example of thingsC that might be appropriate for ULOOP3.CC############################################################################C IMPLICIT NONEC


C############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the argumentsC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )CC############################################################################CCC............................................................................CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U L O O P 4 #C #C############################################################################C SUBROUTINE ULOOP4( COEFF, EXPO )CC............................................................................CC ULOOP4 --> Called from QTRAN subroutine CRUNCH, thisC subroutine is called at the end of calculationsC for each node for each iteration immediatelyC after the temperature for that node has beenC updated.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18,


508

$ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the argumentsC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )CC############################################################################CCC............................................................................CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U L O O P 5 #C #C############################################################################C SUBROUTINE ULOOP5( COEFF, EXPO )CC............................................................................CC ULOOP5 --> Called from QTRAN subroutine CRUNCH, thisC subroutine is called at the end of eachC steady state or transient iteration. ThisC routine can be used to perform auxiliaryC calculations that must be performed in parallelC with the thermal calculations, e.g., fluid flowC calculations, mass transport calculations, orC anything else that is appropriate.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52,


$ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the argumentsC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )CC############################################################################CCC............................................................................CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U L O O P 6 #C #C############################################################################C SUBROUTINE ULOOP6( COEFF, EXPO )CC............................................................................CC ULOOP6 --> Called from QTRAN subroutine CRUNCH, thisC subroutine is called only after a steady stateC calculation has converged.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52,


510

$ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the argumentsC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )CC############################################################################CCC............................................................................CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U L O O P 7 #C #C############################################################################C SUBROUTINE ULOOP7( COEFF, EXPO )CC............................................................................CC ULOOP7 --> Called from QTRAN subroutine CRUNCH, thisC subroutine is called after each transient timeC step.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the argumentsC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )C


C############################################################################CCC............................................................................CC............................................................................C RETURN ENDC If greater, adjust TMAX30.CC*C TMAX30 = MAX( TEMPS(NODE), TMAX30 )CC If the maximum temperature is greater than or equal to 1000,C set the microfunction value to 723.15.CC*C IF( TMAX30 .GE. 1000.0 ) VAL = 723.15CC*C ENDIFCC############################################################################C RETURN ENDCCC############################################################################C #C S U B R O U T I N E U M C R P R #C #C############################################################################C SUBROUTINE UMCRPR( X, MICRO, IFUNC, VAL, P, TX, TY, COEFF, EXPO )CC############################################################################CC this subroutine calculates the microfunction value and returns itC in argument "val" for microfunction "micro". The evaluationC option is passed to UMICRO as IFUNC. X is the independentC variable specified by the calling macro function.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare the arguments.C INCLUDE 'common.dims'C INTEGER MICRO, IFUNCC DOUBLE PRECISION VAL, X DOUBLE PRECISION P( J7, J8 ), TX( J9, J10 ), TY( J9, J10 ) DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 )C*C DOUBLE PRECISION PROPSC*CC*C EXTERNAL PROPSCC############################################################################CC This routine is the same as UMICRO except the arguments have been C added that allow the user to access material properties in C addition to the micro functions. The following is an example ofC a call to properties. The user will have to figure out how toC acquire the proper MPID's.C


512

C PROPS is used to evaluate all of QTRAN's materialC property values. NOTE: If MPID is negative, subroutine PROPSC will ignore it and will use the current TIME value as theC evaluation argument. Since you are doing the coding,C you may of course use any argument that you wish.CC*C SOMTHG = PROPS( COEFF, EXPO, TBAR, MPID )CC You may fill this area in with any computational algorithm that youC desire. If you wish access to QTRAN's arrays for some reason,C I suggest that you look at QTRAN's main module and referenceC these arrays through the common blocks set up in the mainC module. This should prove rather trivial. Note that the node C number that this microfunction is going to be applied to is C available as:CC Node_number = IALIAS(NODE),C where Node_number will be the number that you used in the inputC data file. The value of NODE is actually QTRAN's internalC reference to the packed node numbers stored in IALIAS.C For example, suppose that the 23rd node number defined wasC node number 10070. Then IALIAS(23) will contain the valueC of 10070. For internal computational purposes for QTRAN,C this is NODE 23. The value of the NODE being processed whenC this microfunction is called is available through the loopC parameters common block above.CC In a similar manner, the microfunction I.D. number is stored inC MFID(MICRO).CC If you need to use local variables whose values must be saved betweenC calls to this routine, I suggest that you place these variablesC in a local common block, e.g., suppose that you need an arrayC for storing maximum and minimum temperature values. TheC following common block could be used (without the "C" inC column 1, of course):CC COMMON / LOCAL1 / TEMPMX(maxt), TEMPMN(maxt)CC where "maxt" is available from the "DIMS" common block aboveC and happens to be the maximum number of nodes for which theC problem is currently dimensioned. Exact values of "maxt"C or other dimensions are available from the main programC module.CC############################################################################CC Consider the following hypothetical microfunction application. YouC have a need to apply a heat source to two nodes if their maximumC temperature exceeds 1000 degrees in whatever units you specifiedC for temperature with the ICCALC variable. The nodes that areC to have heat sources applied are nodes 15 and 30. It is furtherC specified that the heat sources for the two nodes have differentC values. The following programming shows how to do this.CC CAUTION: If your Fortran compiler does not automaticallyC initialize variables to zero, you may need toC add initialization code for your "common"C variables in either a BLOCK DATA subroutine orC in the MAIN program module.CC............................................................................CC Declare the common blocks for the IALIAS and TEMPS arrays.CC Dimensions for following array are defined in QTRAN.FORCC COMMON / IA17 / IFLIST( J17, J16 )


C COMMON / IA19 / ITLIST( J18, J19 )CC*C DOUBLE PRECISION TEMPSC*CC*C INTEGER IFLIST, ITLIST, IALIAS, NODE, KQMAC, KTMACC*CC*C COMMON / IA17 / IFLIST( 10, 5 )C*C COMMON / IA19 / ITLIST( 7, 5 )C*C COMMON / IA25 / IALIAS(1)C*C COMMON / IB21 / NODEC*C COMMON / IB73 / KQMACC*C COMMON / IB74 / KTMACC*C COMMON / RA16 / TEMPS(1)CC CAUTION: You should really dimension IALIAS and TEMPS correctlyC instead of using the dummy dimensions of "1". However,C since this is purely for demonstration purposes....C Correct dimensions are available in the MAIN module.CC............................................................................CC Set up a common block to save the maximum temperatures for nodes 15 &C 30.CC*C DOUBLE PRECISION TMAX15, TMAX30C*CC*C INTEGER NODEA, NODE1, NODE2C*CC*C COMMON / LOCAL1 / TMAX15, TMAX30CC............................................................................CC Get the node number that the microfunction is applied to.CC*C TMAX15 = 15.0C*C TMAX30 = 30.0C*C NODNUM = ABS( IALIAS( NODE ) )C*C IF( KTMAC .GT. 0 ) THENCC TEMPERATURE MICRO FUNCTION IS DEFINED, GET NODES FROM THE IFLIST ARRAYCC*C NODEA = IFLIST( KTMAC, 1)C*C NODE1 = IFLIST( KTMAC, 3)C*C NODE2 = IFLIST( KTMAC, 4)C*C ELSE IF( KQMAC .GT. 0 ) THENC*C NODEA = ITLIST( KTMAC, 1)C*C NODE1 = ITLIST( KTMAC, 3)C*C NODE2 = ITLIST( KTMAC, 4)C*C END IFCC............................................................................CC Check for node 15.CC*C IF (NODEA .LE. 15 ) THENCC Check the nodes temperature against it's maximum temperature.C If greater, adjust TMAX15.CC*C TMAX15 = MAX( TEMPS (NODE ), TMAX15 )CC If the maximum temperature is greater than or equal to 1000,C set the microfunction value to 100.CC*C IF( TMAX15 .GE. 1000.0 ) VAL = 100.0CCC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,


514

CC Check for node 30.CC*C ELSE IF( NODEA .LE. 30 ) THENCC Check the node's temperature against it's maximum temperature.C If greater, adjust TMAX30.CC*C TMAX30 = MAX( TEMPS(NODE), TMAX30 )CC If the maximum temperature is greater than or equal to 1000,C set the microfunction value to 723.15.CC*C IF( TMAX30 .GE. 1000.0 ) VAL = 723.15CC*C ENDIFCC############################################################################C RETURN ENDCC############################################################################C #C S U B R O U T I N E U M I C R O #C #C############################################################################C SUBROUTINE UMICRO( X, MICRO, IFUNC, VAL )CC############################################################################CC this subroutine calculates the microfunction value and returns itC in argument "val" for microfunction "micro". The evaluationC option is passed to UMICRO as IFUNC. X is the independentC variable specified by the calling macro function.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare the arguments.C INTEGER MICRO, IFUNCC DOUBLE PRECISION VAL, XCC############################################################################CC You may fill this area in with any computational algorithm that youC desire. If you wish access to QTRAN's arrays for some reason,C I suggest that you look at QTRAN's main module and referenceC these arrays through the common blocks set up in the mainC module. This should prove rather trivial. Note that the node C number that this microfunction is going to be applied to is C available as:CC Node_number = IALIAS(NODE),C where Node_number will be the number that you used in the inputC data file. The value of NODE is actually QTRAN's internalC reference to the packed node numbers stored in IALIAS.C For example, suppose that the 23rd node number defined wasC node number 10070. Then IALIAS(23) will contain the valueC of 10070. For internal computational purposes for QTRAN,C this is NODE 23. The value of the NODE being processed whenC this microfunction is called is available through the loop


C parameters common block above.CC In a similar manner, the microfunction I.D. number is stored inC MFID(MICRO).CC If you need to use local variables whose values must be saved betweenC calls to this routine, I suggest that you place these variablesC in a local common block, e.g., suppose that you need an arrayC for storing maximum and minimum temperature values. TheC following common block could be used (without the "C" inC column 1, of course):CC COMMON / LOCAL1 / TEMPMX(maxt), TEMPMN(maxt)CC where "maxt" is available from the "DIMS" common block aboveC and happens to be the maximum number of nodes for which theC problem is currently dimensioned. Exact values of "maxt"C or other dimensions are available from the main programC module.CC############################################################################CC Consider the following hypothetical microfunction application. YouC have a need to apply a heat source to two nodes if their maximumC temperature exceeds 1000 degrees in whatever units you specifiedC for temperature with the ICCALC variable. The nodes that areC to have heat sources applied are nodes 15 and 30. It is furtherC specified that the heat sources for the two nodes have differentC values. The following programming shows how to do this.CC CAUTION: If your Fortran compiler does not automaticallyC initialize variables to zero, you may need toC add initialization code for your "common"C variables in either a BLOCK DATA subroutine orC in the MAIN program module.CC............................................................................CC Declare the common blocks for the IALIAS and TEMPS arrays.CC Dimensions for following array are defined in QTRAN.FORCC COMMON / IA17 / IFLIST( J17, J16 )C COMMON / IA19 / ITLIST( J18, J19 )CC*C DOUBLE PRECISION TEMPSC*CC*C INTEGER IFLIST, ITLIST, IALIAS, NODE, KQMAC, KTMACC*CC*C COMMON / IA17 / IFLIST( 10, 5 )C*C COMMON / IA19 / ITLIST( 7, 5 )C*C COMMON / IA25 / IALIAS(1)C*C COMMON / IB21 / NODEC*C COMMON / IB73 / KQMACC*C COMMON / IB74 / KTMACC*C COMMON / RA16 / TEMPS(1)CC CAUTION: You should really dimension IALIAS and TEMPS correctlyC instead of using the dummy dimensions of "1". However,C since this is purely for demonstration purposes....C Correct dimensions are available in the MAIN module.CC............................................................................CC Set up a common block to save the maximum temperatures for nodes 15 &C 30.CC*C DOUBLE PRECISION TMAX15, TMAX30


516

C*CC*C INTEGER NODEA, NODE1, NODE2C*CC*C COMMON / LOCAL1 / TMAX15, TMAX30CC............................................................................CC Get the node number that the microfunction is applied to.CC*C TMAX15 = 15.0C*C TMAX30 = 30.0C*C NODNUM = ABS( IALIAS( NODE ) )C*C IF( KTMAC .GT. 0 ) THENCC TEMPERATURE MICRO FUNCTION IS DEFINED, GET NODES FROM THE IFLIST ARRAYCC*C NODEA = IFLIST( KTMAC, 1)C*C NODE1 = IFLIST( KTMAC, 3)C*C NODE2 = IFLIST( KTMAC, 4)C*C ELSE IF( KQMAC .GT. 0 ) THENC*C NODEA = ITLIST( KTMAC, 1)C*C NODE1 = ITLIST( KTMAC, 3)C*C NODE2 = ITLIST( KTMAC, 4)C*C END IFCC............................................................................CC Check for node 15.CC*C IF (NODEA .LE. 15 ) THENCC Check the nodes temperature against it's maximum temperature.C If greater, adjust TMAX15.CC*C TMAX15 = MAX( TEMPS (NODE ), TMAX15 )CC If the maximum temperature is greater than or equal to 1000,C set the microfunction value to 100.CC*C IF( TMAX15 .GE. 1000.0 ) VAL = 100.0CCC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,CC Check for node 30.CC*C ELSE IF( NODEA .LE. 30 ) THENCC Check the node's temperature against it's maximum temperature.C If greater, adjust TMAX30.CC*C TMAX30 = MAX( TEMPS(NODE), TMAX30 )CC If the maximum temperature is greater than or equal to 1000,C set the microfunction value to 723.15.CC*C IF( TMAX30 .GE. 1000.0 ) VAL = 723.15CC*C ENDIFCC############################################################################C RETURN ENDCC############################################################################C #C S U B R O U T I N E U O U T P T #


C #C############################################################################C SUBROUTINE UOUTPT( IO )CC............................................................................CC UOUTPT --> Called from QTRAN subroutine QFLOW, thisC subroutine may be used to print out customizedC data immediately after the temperature data isC printed out for either transient or steady stateC runs. UOUTPT data is printed out prior to theC resistor data.CC ARGUMENT:C IO --> logical unit number for QTRAN's output data file.CC############################################################################C IMPLICIT NONECC############################################################################C INTEGER IOCC............................................................................CC Any write statements that you wish to use may be included in thisC section of the routine in ANSI standard Fortran.CC As with many of the user-supplied routines, the main method ofC communicating between your user-supplied routines is throughC user-specified common blocks. For example, suppose theC array UA1 contains results data from other user-codedC subroutines. You will have to have built a common blockC containing UA1 already in your other routines. AssumingC that this common block is called UB1 (similar to the exampleC common block for subroutine UINPUT), the remainder of thisC example subroutine (which is commented out) shows an exampleC of how your might go about printing the array data out.CC............................................................................CC Declare the example common block and array.CC INTEGER MAXBLKCC PARAMETER ( MAXBLK = 100 )CC DOUBLE PRECISION UA1CC COMMON / UB1 / UA1( MAXBLK )CC INTEGER ICC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,CC Write out MAXBLK lines of UA1 data.CC WRITE( IO, 1 )C 1 FORMAT( '1USER-SUPPLIED ARRAY UA1 DATA' /C $ ' ----------------------------' //C $11X, 'I', 14X, 'UA1(I)' /C $11X, '-', 14X, '------' )CC DO 2 I = 1, MAXBLKC WRITE( IO, 3 ) I, UA1( I )C 3 FORMAT( 1X, I10, 1PD20.10 )


518

C 2 CONTINUECC , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,CC Return to the calling routine.CC RETURNCC............................................................................C ENDCC############################################################################C #C S U B R O U T I N E U P C P A C #C #C############################################################################C SUBROUTINE UPCPAC( ICPNT, OT, T, TPHASE, QPHASE, COEFF, $ EXPO, CVOL, ICP, IRHO, C, IPHASE, QPHRHV )CC............................................................................CC this subroutine performs any necessary phase change energy balanceC calculations.CC############################################################################C IMPLICIT NONECC############################################################################CC > > > > > MODIFICATION HISTORY < < < < <CCC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare variable in call listC INTEGER IPHASE INTEGER ICPNT INTEGER ICP INTEGER IRHOC double_precision TPHASE


double_precision OT double_precision T double_precision QPHASE double_precision CCC real arrays.C double_precision CVOL(*) double_precision COEFF(J3,J4) double_precision EXPO(J3,J4) double_precision QPHRHVCC****************************************************************************CC Declare external functionsC double_precision PROPS, CPEVAL EXTERNAL PROPS, CPEVALCC############################################################################CC local variables.CC*C*RLH double_precision TDIFFC*C*RLH double_precision T12C*C*RLH double_precision T23C*C*RLH double_precision Q1C*C*RLH double_precision Q2C*C*RLH double_precision Q3C*C*RLH double_precision TP2C*C*RLH double_precision TP3C*C*RLH double_precision FRACC*C*RLH double_precision TBARC*C*RLH double_precision TPCBMC*C*RLH double_precision TPCBPCC############################################################################CC *---------------------------*C | +|C | + |C | + |C t | + |C e | +++++++++++++ |C m | +############# 3 |C p | + ############# |C | + #### #### |C | + #### 2 #### |C | + #### #### |C | + 1 ############# |C | + ############# |C *---------------------------*CC energyCC----------------------------------------------------------------------------CCC Define the temperature at the beginning and end of the phase changeCC*C*RLH TPCBM = TPHASE - PCBANDC*C*RLH TPCBP = TPHASE + PCBANDCC check to see if going up or going down the t/e curve.C if going down (iphase < 0), if going up (iphase >= 0).CC*C*RLH IF( IPHASE .LT. 0 ) THENCC............................................................................


520

CC section 100 is for phase change going down the t/e curve. it assumesC that ot is in region 2 or 3, and that t is in region 1 or 2C of the t/e curve.CC begin the calculations for this section by calculating Q3,C where Q3 is the capacitor stored energy betweenC ot and tphase.CC*C*RLH TDIFF = TPCBP - OTCC*C*RLH IF( TDIFF .GT. 0.D+00 ) THENCC*C*RLH TDIFF = 0.D+00C*C*RLH Q3 = 0.0D+00!C*C*RLH ELSECC*C*RLH T23 = OT + TDIFF * 0.5D+00C*C*RLH Q3 = TDIFF * CVOL(ICPNT) *C*C*RLH $ CPEVAL( OT, TPCBP, COEFF, EXPO, ICP ) *C*C*RLH $ PROPS( COEFF, EXPO, T23, IRHO )!C*C*RLH END IFCC............................................................................CC calculate energy q2, which is the amount of latent heat energyC being released through "freezing".CC*C*RLH TP2 = MIN( TPCBP, OT )C*C*RLH TP3 = MAX( TPCBM, T )C*C*RLH FRAC = ( TP3 - TP2 ) / ( PCBAND * 2.D+00 )C*C*RLH QPHRHV = QPHASE * CVOL(ICPNT) *C*C*RLH 1 PROPS( COEFF, EXPO, TPHASE, IRHO )C*C*RLH Q2 = FRAC * QPHRHVCC Add the normal capacitance effects to Q2.CC*C*RLH TBAR = ( TP2 + TP3 ) * 0.5D+00C*C*RLH Q2 = Q2 + ( TP3 - TP2 ) * CVOL(ICPNT) *C*C*RLH $ CPEVAL( TP2, TP3, COEFF, EXPO, ICP ) *C*C*RLH $ PROPS( COEFF, EXPO, TBAR, IRHO )CC............................................................................CC calculate the energy q1, which is the amount of energy storedC between t and tphase.CC*C*RLH TDIFF = T - TPCBMCC*C*RLH IF( TDIFF .GT. 0.D+00 ) THENCC*C*RLH TDIFF = 0.D+00C*C*RLH Q1 = 0.0D+00!C*C*RLH ELSECC*C*RLH T12 = T - TDIFF * 0.5D+00C*C*RLH Q1 = TDIFF * CVOL(ICPNT) *C*C*RLH $ CPEVAL( TPCBM, T, COEFF, EXPO, ICP ) *C*C*RLH $ PROPS( COEFF, EXPO, T12, IRHO )CC*C*RLH END IFCC............................................................................CC all the potential capacitance effects have now been computed.


C add them to the total nodal capacitance computed soC far, and then return to the calling routine.CC*C*RLH C = C + Q1 + Q2 + Q3CC*C*RLH RETURNCC============================================================================CC*C*RLH ELSECC This section is for phase change going up the t/e curve.CC begin the calculations by calculating Q1, where Q1 is theC capacitor energy stored between ot and tphase.CC*C*RLH TDIFF = TPCBM - OTCC*C*RLH IF( TDIFF .LT. 0.D+00 ) THENCC*C*RLH TDIFF = 0.D+00C*C*RLH Q1 = 0.0D+00!C*C*RLH ELSECC*C*RLH T12 = OT + TDIFF * 0.5D+00C*C*RLH Q1 = TDIFF * CVOL(ICPNT) *C*C*RLH $ CPEVAL( OT, TPCBM, COEFF, EXPO, ICP ) *C*C*RLH $ PROPS( COEFF, EXPO, T12, IRHO )!C*C*RLH END IFCC............................................................................CC calculate energy q2, which is the amount of latent heat beingC absorbed by "melting".CC*C*RLH TP2 = MAX( TPCBM, OT )C*C*RLH TP3 = MIN( TPCBP, T )C*C*RLH FRAC = ( TP3 - TP2 ) / ( PCBAND * 2.D+00 )C*C*RLH QPHRHV = QPHASE * CVOL(ICPNT) *C*C*RLH 1 PROPS( COEFF, EXPO, TPHASE, IRHO )C*C*RLH Q2 = FRAC * QPHRHVCC add the normal capacitance effects to Q2.CC*C*RLH TBAR = ( TP2 + TP3 ) * 0.5D+00CC*C*RLH Q2 = Q2 + ( TP3 - TP2 ) * CVOL(ICPNT) *C*C*RLH $ CPEVAL( TP2, TP3, COEFF, EXPO, ICP ) *C*C*RLH $ PROPS( COEFF, EXPO, TBAR, IRHO )CC............................................................................CC calculate energy q23, which is the amount of energy storedC in the capacitor between t and tphase.CC*C*RLH TDIFF = T - TPCBPCC*C*RLH IF( TDIFF .LT. 0.D+00 ) THENCC*C*RLH TDIFF = 0.D+00C*C*RLH Q3 = 0.0D+00!C*C*RLH ELSECC*C*RLH T23 = T - TDIFF * 0.5D+00C*C*RLH Q3 = TDIFF * CVOL(ICPNT) *


522

C*C*RLH $ CPEVAL( TPCBP, T, COEFF, EXPO, ICP ) *C*C*RLH $ PROPS( COEFF, EXPO, T23, IRHO )!C*C*RLH END IFCC............................................................................CC all the potential capacitance effects have now been computed.C add them to the total nodal capacitance computed so far,C and then return to the calling routine.CC*C*RLH C = C + Q1 + Q2 + Q3CC*C*RLH RETURNCC*C*RLH ENDIFCC############################################################################CC end of subroutine phasorC RETURNC ENDCC############################################################################CC############################################################################C #C S U B R O U T I N E U P L O T #C #C############################################################################C SUBROUTINE UPLOT( TEMPS )CC............................................................................CC UPLOT --> Called from OUTPLT subroutine, thisC subroutine is called after each converged solution.CCC############################################################################C IMPLICIT NONECC############################################################################CC Define dimension statement, included in common blockCC MAXT -> Maximum number of nodesCC............................................................................CC Declare problem dimensions and common block where they are defined.C This is taken from the common.blk file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27,


$ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Define variables in call listCC TEMPS -> Current temperature of nodesC DOUBLE PRECISION TEMPS( MAXT )CC............................................................................CC User operationsCCC............................................................................C RETURN ENDCC############################################################################C #C S U B R O U T I N E U P R N T C #C #C############################################################################C SUBROUTINE UPRNTC( TEMPS, IALIAS )CC############################################################################C #C This routine give the user the ability to set a special print flagC if special conditions are meet. CC############################################################################CC > > > > > MODIFICATION HISTORY < < < < <CC Modification: Add special print conditionsC By: Haddock Date: 22 October 1996CC############################################################################C IMPLICIT NONECC############################################################################CC declare the arrays.C INTEGER FPRTFL, JPRTFLC COMMON / IB107 / FPRTFL COMMON / IB108 / JPRTFLC INTEGER IALIAS(*)CC real arraysC DOUBLE PRECISION TEMPS(*)CC############################################################################C declare the local variables.CC If JPRTFL is 1 then a printout occurred on the previous time step.C To force printout, set FPRTFL to 1.


524

CC############################################################################C RETURN ENDCC############################################################################C #C S U B R O U T I N E U P R O P #C #C############################################################################C SUBROUTINE UPROP( PROP, X, COEFF, EXPO, IPMPID )CC############################################################################CC This subroutine can be modified by the user for the express purposeC of supplying special-coded user-supplied material propertiesC that may be too exotic to be handled by QTRAN's normalC material property library functions. This routine is calledC by QTRAN whenever a material property has been defined withC an evaluation option of U (IEVAL parameter in Section 5.3.1 ofC the input data file).CC Arguments:CC PROP --> value of the material property to be returnedC to QTRAN for use in calculations.CC X --> Temperature normally used to evaluateC the material properties, e.g., temperature ofC a node or average temperature of a conductiveC resistor.CC COEFF()--> Array of MDATA1 values. For this materialC property, the MATA1(i) values are stored asC COEFF(IPMPID,i+1). COEFF(IPMPID,1) containsC the number of MDATA1/MDATA2 data pairs.CC EXPO() --> Array of MDATA2 values. For this materialC property, the MATA2(i) values are stored asC EXPO(IPMPID,i+1). EXPO(IPMPID,1) stores anC evaluation code, which is used to determineC whether the material property is a constant,C a linear data table, etc. (from subroutineC UPROP, this code always specifies "user-supplied").CC IPMPID --> packed material property i.d. This is not the sameC as the MPID number normally entered in Section 5.3.1C of the input data file. IPMPID here corresponds toC the IPMPID'th material property that was defined inC Section 5.3.1. To retrieve the MPID number that youC gave in Section 5.3.1 for this material property,C you must reference the MID array in the followingC manner:CC COMMON / IA45 / MID(1)C MPID = MID( IPMPID )CC You will then have the correct MPID number forC the IPMPID'th material property. It should be notedC that the MPID number is normally not needed forC anything here, although you might wish to haveC access to it in the event that you set up someC error message routines.CC############################################################################C


IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.blk file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Declare the arguments and local variables.C DOUBLE PRECISION PROP, X, COEFF( J3, J4 ), EXPO( J3, J4 )C INTEGER IPMPIDCC*C*RLH INTEGER MPIDC*C*RLH INTEGER MIDCC*C*RLH DOUBLE PRECISION TIMECC*C*RLH COMMON / IA45 / MID(1)CC*C*RLH COMMON / RB1 / TIMECC############################################################################CC The remainder of this subroutine shows an EXAMPLE ONLY of what youC might do if you wished one or more custom material properties.CC Let us suppose that the material property that you wish to define is aC mix of time and temperature.CC############################################################################CC This property section shows how to build a material propertyC evaluation that is a mix of both temperature and time.C Suppose that the form of the material property to beC defined is as follows:CC Property(Temp,Time) = { A + B * Temp } * { C + D * Time }CC The following coding accomplishes this. The assumption is that:CC A = 1.0C B = 2.0C C = 3.0C D = -2.0CC*C PROP = ( 1.0D+00 + 2.0D+00 * X ) *C*C $ ( 3.0D+00 - 2.0D+00 * TIME )


526

CC NOTE: The value of TIME is passed to this routine viaC a named COMMON block which is inserted at theC beginning of this routine. The block's name is:CC############################################################################C! This is an example of how to use user routines to modify resistor values! User material properties have to be used to flag which resistor or! capacitors are to be modified by the user.!C*C*RLH MPID = MID( IPMPID )!C*C*RLH IF( MPID .EQ. 203101 ) THEN! Silver conductivity MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 203104 ) THEN! Silver density MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 203105 ) THEN! Silver specific heat MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 203117 ) THEN! Silver EmissivityC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 270701 ) THEN! Flint Glass Conductivity MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 270704 ) THEN! Flint Glass Density MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 270705 ) THEN! Flint Glass Specific Heat MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 270717 ) THEN! Flint Glass EmissivityC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 303101 ) THEN! Silver conductivity MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 303104 ) THEN! Silver density MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 303105 ) THEN! Silver specific heat MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 303117 ) THEN! Silver EmissivityC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 370701 ) THEN! Flint Glass Conductivity MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 370704 ) THEN! Flint Glass Density MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 370705 ) THEN! Flint Glass Specific Heat MKS unitsC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH ELSE IF( MPID .EQ. 370717 ) THEN! Flint Glass EmissivityC*C*RLH PROP = COEFF( IPMPID, 2 )C*C*RLH END IF! RETURNCC############################################################################CC As you can see, probably the hardest part of this whole exercise was


C wading through my verbage. Good Luck!CC############################################################################C ENDCC############################################################################C #C S U B R O U T I N E U R A D A T #C #C############################################################################C SUBROUTINE URADAT( NRAD, TT1, TT2, TT3, T1SAVE, T2SAVE, 1 COEFF, EXPO, GVAL, QGRAY )CC############################################################################CC This subroutine modifies or calculates the radiant interchange betweenC two gray radiosity nodes as the user desires. The user can defineC determine the resistor type and other information necessary byC defining different common blocks that contain the radiation resistorC information. This routine is called three times for each resistorC evaluation - once with current temeratures and then with the plusC and minus perturbed values. One should keep this in mind if they areC doing integration or other such evaluations during the calculationC cycle.CC Some variables that might be used defined below:CC NRAD = resistor for which the heat flow is to be calculated.C COEFF & EXPO = the system material property arrays which areC used to evaluate emissivities and transmissivities.C TT1 & TT2 = Node temperature in absolute unitsC TT3, T1SAVE & T2SAVE are node temperatures in ICCALC unitsCC Other variables one might wantCC temps = system temperature array.C qgray = heat transmitted from node 1 to node 2 by the gray resistor.C igtype = 1 => r = (1-e)/(e*a)C 2 => r = 1/(f*a*tau)C 3 => r = 1/( f*a*(1-tau) )C 4 => r = 1/(f*a)C 5 => r = 1/(f)C 6 => r = (1-e)/(e*a), e=constantC 7 => r = 1/(f*a*tau), tau from extinction coefficientC 8 => r = 1/( f*a*(1-tau) ), tau from extinction coefficientC where tau is the transmissivity of the participative mediaC and e is the surface emissivity.C (r is the value of the gray radiative resistor).C 9 => r = 1/(f*a*tau)C 10 => r = 1/( f*a*(1-tau) )C 11 => r = 1/(f*a*tau), tau from extinction coefficientC 12 => r = 1/( f*a*(1-tau) ), tau from extinction coefficientCC Note: Subtypes 9-12 have F and A pre-multiplied andC stored in the GSFACT array.CC igprop = material property index for emissivity, transmissivity, orC extinction coefficient.C gsfact is the shape factor.C garea is the surface area.C sbc is the stephan-boltzman constant.C logp = logical print / no-print variable for resistor data.C gdist = view factor distance, used with extinction coefficients.CC############################################################################C


528

IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################C define call list variablesC INTEGER NRADC DOUBLE PRECISION COEFF( J3, J4 ), EXPO( J3, J4 ) DOUBLE PRECISION GVAL DOUBLE PRECISION QGRAY DOUBLE PRECISION TT1 DOUBLE PRECISION TT2 DOUBLE PRECISION TT3 DOUBLE PRECISION T1SAVE DOUBLE PRECISION T2SAVECC############################################################################CC Declare the common block variablesCCC############################################################################CC*C*RLH INTEGER MIDC*C*RLH INTEGER IOC*C*RLH INTEGER IGTYPE C*C*RLH INTEGER IGPROP !C*C*RLH LOGICAL LOGP!C*C*RLH DOUBLE PRECISION SBCC*C*RLH DOUBLE PRECISION EMISSC*C*RLH DOUBLE PRECISION TAUC*C*RLH DOUBLE PRECISION GAREA!!C*C*RLH COMMON / IA14 / IGTYPE( 1 )C*C*RLH COMMON / IA15 / IGPROP( 1 )C*C*RLH COMMON / IA45 / MID( 1 )CC*C*RLH COMMON / IB33 / IO!C*C*RLH COMMON / LB3 / LOGP!C*C*RLH COMMON / RA23 / GAREA( 1 )!


C*C*RLH COMMON / RB22 / SBCC*C*RLH COMMON / RB51 / EMISSC*C*RLH COMMON / RB52 / TAUCC############################################################################C Declare the local variables.CC*C*RLH DOUBLE PRECISION PROPSC*C*RLH DOUBLE PRECISION F12CC*C*RLH INTEGER N3C*C*RLH INTEGER LIPROPC*C*RLH INTEGER MPIDCC############################################################################C Declare external functionsCC*C*RLH EXTERNAL PROPSCC############################################################################CC*C*RLH LIPROP = ABS( IGPROP( NRAD ) )C*C*RLH MPID = MID( LIPROP )CC*C*RLH IF( IGTYPE( NRAD ) .EQ. 13 .AND. ( MPID .EQ. 303117 .OR.C*C*RLH 1 MPID .EQ. 370717 ) ) THENCC this section is for radiative resistors with one surface node.CC calculate the emissivity.CC*C*RLH EMISS = EXPO( LIPROP, 2 )CC............................................................................CC check to see that emiss doesn't blow up the calculation.CC*C*RLH IF( EMISS .GT. 0.9999D+00 ) THENC*C*RLH EMISS = 0.9999D+00C*C*RLH ELSE IF( EMISS .LE. 0.D+00 ) THENC*C*RLH QGRAY = 0.D+00C*C*RLH GOTO 9000C*C*RLH ENDIFCC............................................................................CC calculate the heat transmitted from node 1 to 2.CC*C*RLH GVAL = SBC * ( EMISS * GAREA(NRAD) ) *C*C*RLH $ ( TT1 * TT1 + TT2 * TT2 ) * ABS( TT1 + TT2 )CC*C*RLH QGRAY = GVAL * ( TT1 - TT2 )CC*C*RLH END IFCC############################################################################CCC$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$CC*C*RLH 9000 CONTINUEC RETURNCC############################################################################C ENDC


530

C############################################################################C #C S U B R O U T I N E U R S T R T #C #C############################################################################C SUBROUTINE URSTRTCC............................................................................CC URSTRT --> Called from QTRAN subroutine GETRST, thisC subroutine is called if QTRAN is resumingC execution from a restart file.CC############################################################################C IMPLICIT NONECC############################################################################CCC............................................................................CCC............................................................................CC RETURN ENDCC############################################################################C #C S U B R O U T I N E U S O L #C #C############################################################################C SUBROUTINE USOL( T1RH, T2RH, T3RH, JPROP, JTYPE, RHNPNT, T1RC, $ T2RC, RCPROP, RCNPNT, T1RR, T2RR, T3RR, IGTYPE, IGPROP, GSFACT, $ GAREA, RRNPNT, QCARD, IFLIST, QIPPNT, ITLIST, FIXNUM, FIXVAL, $ TFIX, CPROP, CRHO, RCN, RHN, RRN, QIP, ALPHA, IALIAS, GP, COEFF, $ EXPO, RCAL, P, TX, TY, SETTIM, PIDSET, PIDPAR, PIDID, CVOL, $ TEMPS, QVECT, OTEMPS, T1RW, T2RW, T3RW, IWTYPE, IWPROP, RWNPNT, $ RWN, WSPROP, WLPROP, SFACTR, WAREA, T1RF, T2RF, ICPFLO, RFN, $ RFNPNT, RMDOT, DTMAXA, PRINTA, T1CAPS, CNPNT, CN, MID, PID, $ MFID, QMFACT, TMFACT, QBASE, GDIST, WDIST, $ TERROR, GVALCA, QINMAC, AVNODH, FVAR, GUMTRX, ICNTRL, $ INDRLX, IPRLXC, RLXTBS, RLXTBT, RELAXV, EFACTB, RELAXM, RERROR, $ IRRLXC, $ T1RP, T2RP, PTYPE, PPROP, RPN, RPNPNT, IMLIST, MIP, $ MIPPNT, IPLIST, PFIX, PALIAS, PIALAS, HIALAS, $ PGP, MMFACT, PMFACT, MDBASE, PRHOE, VELOCP, PRHO, $ PRESS, OPRESS, MDOTP, MDOTND, HYCCE, DIFHED, QMDOTP, QBASEF )CC############################################################################C #C This subroutine contains solution option 1000. #C #C############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.blk file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18,


$ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################CC Define variablesC INTEGER ICNTRLCC integer arrays.C INTEGER JPROP( J1, J2 ) INTEGER T1RH(*) INTEGER T2RH(*) INTEGER T3RH(*) INTEGER JTYPE(*) INTEGER RCPROP(*) INTEGER T1RC(*) INTEGER T2RC(*) INTEGER RCNPNT(*) INTEGER RHNPNT(*) INTEGER T1RR(*) INTEGER T2RR(*) INTEGER T3RR(*) INTEGER QCARD( J14, J15 ) INTEGER IFLIST( J17, J16 ) INTEGER QIPPNT(*) INTEGER ITLIST( J18, J19 ) INTEGER RRNPNT(*) INTEGER FIXNUM(*) INTEGER FIXVAL(*) INTEGER T1RW(*) INTEGER T2RW(*) INTEGER T3RW(*) INTEGER IWTYPE(*) INTEGER IWPROP(*) INTEGER RWNPNT(*) INTEGER RWN(*) INTEGER TFIX(*) INTEGER CPROP(*) INTEGER CRHO(*) INTEGER RCN(*) INTEGER RRN(*) INTEGER RHN(*) INTEGER QIP(*) INTEGER T1RF(J30) INTEGER T2RF(J30) INTEGER ICPFLO( J30, 2 ) INTEGER RFN(*) INTEGER RFNPNT(*) INTEGER T1CAPS(*) INTEGER CNPNT(*) INTEGER CN(*) INTEGER PIDPAR(*) INTEGER PIDID(*)


532

INTEGER IALIAS(*) INTEGER MID(*) INTEGER PID(*) INTEGER MFID(*) INTEGER IGTYPE(*) INTEGER IGPROP(*) INTEGER INDRLX( MAXT ) INTEGER IPRLXC( MAXT ) INTEGER IRRLXC( MAXT )CC Hydraulic variablesC INTEGER T1RP ( * ) INTEGER T2RP ( * ) INTEGER PTYPE ( * ) INTEGER PPROP ( J44, J46 ) INTEGER RPN ( * ) INTEGER RPNPNT( * ) INTEGER IMLIST( J48, J49 ) INTEGER MIP ( * ) INTEGER MIPPNT( * ) INTEGER IPLIST( J50, J51 ) INTEGER PFIX ( * ) INTEGER PALIAS( * ) INTEGER PIALAS( * ) INTEGER HIALAS( * )CC............................................................................CC real arrays.C DOUBLE PRECISION ALPHA(*) DOUBLE PRECISION GP( J1, J6 ) DOUBLE PRECISION COEFF( J3, J4 ) DOUBLE PRECISION EXPO( J3, J4 ) DOUBLE PRECISION RCAL(*) DOUBLE PRECISION P(J7,J8) DOUBLE PRECISION TX( J9, J10 ) DOUBLE PRECISION TY( J9, J10 ) DOUBLE PRECISION GSFACT(*) DOUBLE PRECISION GAREA(*) DOUBLE PRECISION SETTIM(*) DOUBLE PRECISION WSPROP(*) DOUBLE PRECISION WLPROP(*) DOUBLE PRECISION SFACTR(*) DOUBLE PRECISION WAREA(*) DOUBLE PRECISION CVOL(*) DOUBLE PRECISION TEMPS(*) DOUBLE PRECISION QVECT(*) DOUBLE PRECISION OTEMPS(*) DOUBLE PRECISION RMDOT(*) DOUBLE PRECISION DTMAXA( J32, J33 ) DOUBLE PRECISION PRINTA( J34, J35 ) DOUBLE PRECISION PIDSET( J22, J23 ) DOUBLE PRECISION QMFACT( J17 ) DOUBLE PRECISION TMFACT( J18 ) DOUBLE PRECISION QBASE( MAXT ) DOUBLE PRECISION GDIST(*) DOUBLE PRECISION WDIST(*) DOUBLE PRECISION TERROR (MAXT, J27 ) DOUBLE PRECISION GVALCA(*) DOUBLE PRECISION QINMAC( MAXT ) DOUBLE PRECISION AVNODH( MAXT ) DOUBLE PRECISION FVAR( MAXT, * ) DOUBLE PRECISION GUMTRX( M1, M1 ) DOUBLE PRECISION RLXTBS( J39, J40) DOUBLE PRECISION RLXTBT( J39, J40) DOUBLE PRECISION RELAXV( MAXT )


DOUBLE PRECISION EFACTB( MAXT ) DOUBLE PRECISION RELAXM( MAXT ) DOUBLE PRECISION RERROR( MAXT, J41 ) DOUBLE PRECISION QBASEF(MAXT)CC hydraulic variablesC DOUBLE PRECISION PGP ( J44, J45 ) DOUBLE PRECISION MMFACT( * ) DOUBLE PRECISION PMFACT( * ) DOUBLE PRECISION MDBASE( * ) DOUBLE PRECISION PRHOE ( * ) DOUBLE PRECISION VELOCP( * ) DOUBLE PRECISION PRHO ( * ) DOUBLE PRECISION OPRESS( * ) DOUBLE PRECISION PRESS ( * ) DOUBLE PRECISION MDOTP ( * ) DOUBLE PRECISION MDOTND(*) DOUBLE PRECISION HYCCE(*) DOUBLE PRECISION DIFHED(*) DOUBLE PRECISION QMDOTP(*)CC############################################################################CC At this point, you must build your solution matrix in whatever formC necessary and solve the resultant system.CC############################################################################C RETURN ENDCC############################################################################C SUBROUTINE UWAVER( NWRAD, TT1, TT2, TT3, T1SAVE, T2SAVE, F1, F2, $ COEFF, EXPO, GVAL, QWAVE )CC############################################################################CC This subroutine calculates the wave length dependent radiationC as defined by the user.CC NWRAD = radiant resistor numberC TT1 = temperature of node 1 in absolute unitsC TT2 = temperature of node 2 in absolute unitsC TT3 = temperature of node 3 in iccalc unitsC T1SAVE = temperature of node 1 in iccalc unitsC T2SAVE = temperature of node 2 in iccalc unitsC F1 = fraction of energy leaving node 1 that falls in theC wave band between ws and wl.C F2 = fraction of energy leaving node 2 that falls in theC wave band between ws and wl.C COEFF & EXPO = the system material property arrays which areC used to evaluate emissivities and transmissivities.C GVAL = conductor valueC QWAVE = heat flux through this radiation resistorCC IWPROP = internal property IDC SFACTS = view factor valueC WDIST = distanceC WAREA = areaCC The property, view factor value, and distance are array to hold that theC user wishes to pass through to their radiation calculations. IWPROPC is defined in the field material property and could be informationC that is passed through to reference other properties or property typeC information. SFACTS and WDIST could be arrays that hold spatialC information. WAREA is the area associated with node 1 and will be


534

C supplied by PATRAN.CC The Gval and QGRAY values must be calculated and passed back to theC calling routine.CC############################################################################C IMPLICIT NONECC############################################################################CC Declare problem dimensions and common block where they are defined.C This is taken from the common.dims file.C INTEGER J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPC COMMON /DIMS/ J1, J2, J3, J4, J5, J6, J7, J8, J9, $ J10, J11, J12, J13, J14, J15, J16, J17, J18, $ J19, J20, J21, J22, J23, J24, J25, J26, J27, $ J28, J29, J30, J31, J32, J33, J34, J35, J36, $ J37, J38, J39, J40, J41, J42, J43, $ J44, J45, J46, J47, J48, J49, J50, J51, J52, $ MAXT, MAXTNC, MAXTNH, MAXTNR, MAXTNW, MAXTQN, $ MAXTNF, M1, MAXPCC############################################################################C define call list variablesC DOUBLE PRECISION TT1 DOUBLE PRECISION TT2 DOUBLE PRECISION TT3 DOUBLE PRECISION T1SAVE DOUBLE PRECISION T2SAVE DOUBLE PRECISION F1 DOUBLE PRECISION F2 DOUBLE PRECISION GVAL DOUBLE PRECISION QWAVE DOUBLE PRECISION COEFF( J3, J4 ) DOUBLE PRECISION EXPO( J3, J4 )C INTEGER NWRADCC############################################################################CC Declare the common variablesCC*C*RLH DOUBLE PRECISION WAREACC*C*RLH DOUBLE PRECISION SBCCC*C*RLH INTEGER IWTYPEC*C*RLH INTEGER IWPROPCC*C*RLH COMMON / IA29 / IWTYPE( 1 )C*C*RLH COMMON / IA30 / IWPROP( 1 )CC*C*RLH COMMON / RA14 / WAREA( 1 )CC*C*RLH COMMON / RB22 / SBCCC############################################################################


C Declare the local variables.CC*C*RLH DOUBLE PRECISION EMISSCC*C*RLH DOUBLE PRECISION PROPSCCC############################################################################C Declare external functionsCC*C*RLH EXTERNAL PROPSCC############################################################################CC*C*RLH IF( IWTYPE( NWRAD ) .EQ. 1 .AND. IWPROP( NWRAD ) .EQ. 100103 ) THENCC Now the user can make the necessary calculation.C The example shown is what could be done to evaluate the functionC ( e * A ) / ( 1 - e ) between a surface and radiosity node.CCC calculate the emissivity.CC*C*RLH EMISS = PROPS( COEFF, EXPO, T1SAVE, IWPROP(NWRAD) )CC............................................................................CC check to see that emiss doesn't blow up the calculation.CC*C*RLH IF( EMISS .GT. 0.9999D+00 ) THEN

C*C*RLH EMISS = 0.9999D+00

C*C*RLH ELSE IF( EMISS .LE. 0.00001D+00 ) THEN

C*C*RLH QWAVE = 0.D+00C*C*RLH GVAL = 0.D+00C*C*RLH RETURN C*C*RLH ENDIFCC............................................................................CC calculate the heat transmitted from node 1 to 2.CC*C*RLH GVAL = SBC * ( EMISS * WAREA(NWRAD) ) / ( 1.D+00 - EMISS ) *C*C*RLH $ ( F1 * F1 * TT1 * TT1 + F2 * F2 * TT2 * TT2 ) *C*C*RLH $ ABS( F1 * TT1 + F2 * TT2 )CC*C*RLH QWAVE = GVAL * ( F1 * TT1 - F2 * TT2 )CC*C*RLH ENDIFCC$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$$C RETURNCC############################################################################C END

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample User-Supplied Routines

536

Example User-Supplied Routines

ULOOP7FOR File Listing(All file names in this listing are generic and may differ slightly for the computer you are using.)

537Chapter 11: User-Supplied RoutinesExample User-Supplied Routines


538


540

UMICROFOR File Listing


542


544

545Chapter 11: User-Supplied RoutinesQTRAN Arrays

QTRAN ArraysThe following is a list of the QTRAN data arrays to which user-supplied subroutines may require access. The variable dimensions for these arrays (e.g., J1, J2, ..., MAXT, etc.) are stored in the DIMS common block and may be found in the COMMONBLK file.

The following arrays are arranged in their order of common block declarations. The IA common blocks are Integer Array common blocks, while the RA common blocks are Real Arrays.

Note: While the documented array structures are valid for QTRAN, recognize that QTRAN is still a living code, and as such the array structures may change from time to time. Also recognize that the publishing of the array structures does not obligate our Hot Line staff to help with basic Fortran language questions. Further recognize that when the basic QTRAN logic is altered with the introduction of user software, it makes support extremely difficult if not impossible. The MSC.Software Corporation will not assume responsibility for software which has been linked to user-supplied subroutines.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisQTRAN Arrays

546

Array Declarations Common BlocksLOGICAL PIVFLG(M1) LA1INTEGER JPROP(J1,J2) IA1INTEGER T1RH(J1) IA2INTEGER T2RH(J1) IA3INTEGER T3RH(J1) IA4INTEGER JTYPE(J1) IA5INTEGER RCPROP(J5) IA6INTEGER T1RC(J5) IA7INTEGER T2RC(J5) IA8INTEGER RCNPNT(J11) IA9INTEGER RHNPNT(J12) IA10INTEGER T1RR(J13) IA11INTEGER T2RR(J13 IA12INTEGER T3RR(J13) IA13INTEGER IGTYPE(J13) IA14INTEGER IGPROP(J13) IA15INTEGER QCARD(J14,J15) IA16INTEGER IFLIST(J17,J16) IA17INTEGER QIPPNT(J17) IA18INTEGER ITLIST(J18,J19) IA19INTEGER RRNPNT(J20) IA20INTEGER FIXNUM(J21) IA21INTEGER FIXVAL(J21) IA22INTEGER PIDPAR(J22) IA23INTEGER PIDID(J24) IA24INTEGER IALIAS(MAXT) IA25INTEGER T1RW(J28) IA26INTEGER T2RW(J28) IA27INTEGER T3RW(J28) IA28INTEGER IWTYPE(J28) IA29 INTEGER IWPROP(J28) IA30 INTEGER RWNPNT(J29) IA31 INTEGER TFIX(MAXT) IA32


INTEGER CPROP(J36) IA33 INTEGER CRHO(J36) IA34 INTEGER RCN(MAXTNC) IA35 INTEGER RHN(MAXTNH) IA36 INTEGER RRN(MAXT) IA37 INTEGER QIP(MAXT) IA38 INTEGER RWN(MAXT) IA39 INTEGER T1RF(J30) IA40 INTEGER T2RF(J30) IA41 INTEGER ICPFLO(J30,2) IA42 INTEGER RFN(MAXT) IA43 INTEGER CN(MAXT) IA44 INTEGER MID(J3) IA45 INTEGER PID(J22) IA46 INTEGER MFID(J14) IA47 INTEGER GSN(MAXT) IA48 INTEGER GSNPNT(J26) IA49 INTEGER ISTYPE(J25) IA50 INTEGER ISEMIS(J25) IA51 INTEGER TSURF(J26) IA52 INTEGER NSURF1(J25) IA53 INTEGER NSURF2(J25) IA54 INTEGER SURPNT(J25) IA55 INTEGER WSN(MAXT) IA56 INTEGER WSNPNT(J26) IA57 INTEGER IWSTYP(J25) IA58 INTEGER IWSMID(J25) IA59 INTEGER TWSURF(J26) IA60 INTEGER NWSRF1(J25) IA61 INTEGER NWSRF2(J25) IA62 INTEGER WSRPNT(J25) IA63 INTEGER RFNPNT(J31) IA64 INTEGER T1CAPS(J36) IA65 INTEGER CNPNT(J36) IA66


548

INTEGER PIVROW(M1) IA67 INTEGER INDRLX(MAXT) IA68 INTEGER IPRLXC(MAXT) IA69 INTEGER IRRLXC(MAXT) IA70 INTEGER IPLTBK(MAXT) IA71 INTEGER IRLXGR(J39,J43) IA72 INTEGER IIDMNRF(8) IA73 INTEGER T1RP(J44) IA74 INTEGER T2RP(J44) IA75 INTEGER PTYPE(J44) IA76 INTEGER PPROP(J44,J46) IA77 INTEGER RPN(MAXP) IA78 INTEGER RPNPNT(J47) IA79 INTEGER IMLIST(J48,J49) IA80 INTEGER MIP(MAXP) IA81 INTEGER MIPPNT(MAXP) IA82 INTEGER IPLIST(J50,J51) IA83 INTEGER PFIX(MAXP) IA84 INTEGER PALIAS(MAXP) IA85 INTEGER PIALAS(MAXP) IA86 INTEGER HIALAS(MMPHI) IA87INTEGER TCPLND (J52) IA88INTEGER TCPLCN (J52) IA89 INTEGER QMAVFG( J17 ) IA90INTEGER GSRFLX( J13 ) IA91INTEGER WSRFLX( J28 ) IA92DOUBLE PRECISION GP(J1,J6) RA1 DOUBLE PRECISION COEFF(J3,J4) RA2 DOUBLE PRECISION EXPO(J3,J4) RA3 DOUBLE PRECISION RCAL(J5) RA4 DOUBLE PRECISION P(J7,J9) RA5 DOUBLE PRECISION TX(J9,J10) RA6 DOUBLE PRECISION TY(J9,J10) RA7 DOUBLE PRECISION GSFACT(J13) RA8


DOUBLE PRECISION SETTIM(J21) RA9 DOUBLE PRECISION PIDSET(J22,J23) RA10DOUBLE PRECISION WSPROP(J28) RA11 DOUBLE PRECISION WLPROP(J28) RA12 DOUBLE PRECISION SFACTR(J28) RA13 DOUBLE PRECISION WAREA(J28) RA14 DOUBLE PRECISION CVOL(J36) RA15 DOUBLE PRECISION TEMPS(MAXT) RA16DOUBLE PRECISION QVECT(MAXT) RA17 DOUBLE PRECISION ALPHA(MAXT) RA18 DOUBLE PRECISION OTEMPS(MAXT) RA19 DOUBLE PRECISION RMDOT(J30) RA20 DOUBLE PRECISION DTMAXA(J32,J33) RA21 DOUBLE PRECISION PRINTA(J34,J35) RA22 DOUBLE PRECISION GAREA(J13) RA23 DOUBLE PRECISION QMFACT(J17) RA24 DOUBLE PRECISION TMFACT(J18) RA25DOUBLE PRECISION QBASE(MAXT) RA26 DOUBLE PRECISION SAREA(J26) RA27 DOUBLE PRECISION SSFACT(J25) RA28 DOUBLE PRECISION VFDIST(J25) RA29 DOUBLE PRECISION GDIST(J13) RA30 DOUBLE PRECISION WDIST(J28) RA31 DOUBLE PRECISION WSAREA(J38) RA32 DOUBLE PRECISION WSFACT(J37) RA33 DOUBLE PRECISION WVFDIS(J37) RA34 DOUBLE PRECISION WSLAM1(J37) RA35 DOUBLE PRECISION WSLAM2(J37) RA36 DOUBLE PRECISION TERROR(MAXT,J27) RA37 DOUBLE PRECISION GVALCA(J5) RA38DOUBLE PRECISION QINMAC(MAXT) RA39DOUBLE PRECISION AVNODH(MAXT) RA40 DOUBLE PRECISION FVAR(MAXT) RA41DOUBLE PRECISION MATRIX(M1,M1) RA42


550

DOUBLE PRECISION XRCRDV(MAXT) RA43 DOUBLE PRECISION YZCRDV(MAXT) RA43 DOUBLE PRECISION ZCORDV(MAXT) RA43 DOUBLE PRECISION RLXTBS(J39,J40) RA44 DOUBLE PRECISION RLXTBT(J39,J40) RA45 DOUBLE PRECISION RELAXV(MAXT) RA46DOUBLE PRECISION EFACTB(MAXT) RA47 DOUBLE PRECISION RELAXM(MAXT) RA48 DOUBLE PRECISION RERROR(MAXT,J41) RA49 DOUBLE PRECISION RLXGRP(J39,J42) RA50 DOUBLE PRECISION PGP(J44,J45) RA51 DOUBLE PRECISION MMFACT(J48) RA52 DOUBLE PRECISION PMFACT(J49) RA53 DOUBLE PRECISION MDBASE(MAXP) RA54 DOUBLE PRECISION MDBASE (MAXP) RA55DOUBLE PRECISION PRHOE(J44) RA56DOUBLE PRECISION VELOCP(MAXP) RA57DOUBLE PRECISION PRO(MAXP) RA58DOUBLE PRECISION OPRESS(MAXP) RA2 DOUBLE PRECISION PRESS(MAXP) RA59DOUBLE PRECISION MDOTP(J44) RA60DOUBLE PRECISION MDOTND(MAXP) RA61DOUBLE PRECISION HYCCE(J44) RA62DOUBLE PRECISION DIFHED(J44) RA63DOUBLE PRECISION OTMXHA(J32) RA64DOUBLE PRECISION QMDOTP(J44) RA65DOUBLE PRECISION CRHOCM( J36 ) RA66DOUBLE PRECISION RHONOD( MXTCMA ) RA67DOUBLE PRECISION QDPYGS( MXTCMA ) RA68DOUBLE PRECISION QMFLUX( MAXT ) RA69DOUBLE PRECISION CNVFLX( MAXT ) RA70DOUBLE PRECISION RADFLX( MAXT ) RA71DOUBLE PRECISION QBASEA( MAXT ) RA72DOUBLE PRECISION QBASEF( MAXT ) RA73


In the following, the arrays have been grouped according to usage.

Node Number Alias Array

INTEGER IALIAS(MAXT)IA25 IALIAS(N) contains the model’s node number for QTRAN’s internal node number N. The sign of IALIAS(N) determines whether the node’s temperature will be printed out in the QOUTDAT file, with a negative sign indicating that it will be printed out and a positive sign indicating that it will not be printed out.

This whole process of “aliased” node numbers is necessary if a code is to allow nonsequential node numbering in the model. QTRAN essentially looks at the node numbers that are used in the model and then condenses out any node numbers which are not used in the model that lie between 1 and the largest node number specified. This adds some unfortunate complexity to the coding, but it allows more flexibility in modeling without incurring unacceptable performance costs.

A useful QTRAN subroutine for determining a QTRAN internal node number for a given model node number is subroutine GETNUM. The calling sequence for GETNUM is as follows:

CALL GETNUM( YNODE, QNODE, IALIAS, NTEMPS, MATCH )where:

INTEGER YNODE, QNODE, IALIAS(MAXT), NTEMPS LOGICAL MATCH

and YNODE is the node number from the model, QNODE is the QTRAN internal node number that QTRAN has assigned to YNODE (QNODE is returned by GETNUM), IALIAS is the node alias array, NTEMPS comes from the COMMONBLK file and is the number of nodes which have been defined in the model, and MATCH is returned as .TRUE. or .FALSE., depending on whether GETNUM was able to match YNODE in the IALIAS array.

DOUBLE PRECISION QMFLAR( MAXT ) RA74DOUBLE PRECISION CNVFAR( MAXT ) RA75DOUBLE PRECISION RADFAR( MAXT ) RA76


552

T1RC(K) and T2RC(K) contain QTRAN’s internal node numbers for conductive resistor K’s nodes 1 and 2. RCPROP(K) contains trains internal MPID number for thermal conductivity for resistor K, and RCAL(K) contains the area/length ratio for conductive resistor K. If solution option 1 (SOL = 1 in the QINDAT file) is being used, GVALCA(K) contains the conductance (kA/L) for resistor K.

RCN(N) contains the number of conductive resistors associated with QTRAN’s internal node N. RCNPNT is a pointer array used by QTRAN to determine which conductive resistors are associated with a particular node, and is used in conjunction with the RCN array. If RCN(1) is 10, the first 10 elements of the RCNPNT are conductive resistors which are associated with QTRAN internal node number 1. The conductive resistors associated with QTRAN internal node number 2 (if any) would be contained in RCNPNT(11) to RCNPNT(10+RCN(2)).

The QTRAN internal node numbers associated with convective resistor K are stored in T1RH(K), T2RH(K), and T3RH(K), and the convective configuration (CFIG value) for convective resistor K is

Conductive Resistor ArraysINTEGER T1RC(J5)

INTEGER T2RC(J5)

NTEGER RCPROP(J5)

DOUBLE PRECISION RCAL(J5)

DOUBLE PRECISION GVALCA(J5)

INTEGER RCN(MAXTNC)

INTEGER RCNPNT(J11)

IA7

IA8

IA6

RA4

RA38

IA35

IA9

Convective Resistor ArraysINTEGER T1RH(J1)

INTEGER T2RH(J1)

INTEGER T3RH(J1)

INTEGER JTYPE(J1)

DOUBLE PRECISION GP(J1,J6)

INTEGER JPROP(J1,J2)

INTEGER RHN(MAXTNH)

INTEGER RHNPNT(J12)

IA2

IA3

IA4

IA5

RA1

IA1

IA36

IA10


stored in JTYPE(K). The GP values for convective resistor K are stored in GP(K,1) through GP(K,J6) while the QTRAN internal MPID numbers for convective resistor K are stored in JPROP(K,1) through JPROP(K,J2).

RHN(N) is the number of convective resistors associated with node N. The RHNPNT array interacts with the RHN array in a manner similar to the conductive resistors and RCN/RCNPNT interactions.

The QTRAN internal node numbers associated with advective resistor K are stored in T1RF(K) and T2RF(K). The QTRAN internal MPID numbers associated with specific heat and with variable mass flow rate for advective resistor K are stored in ICPFLO(K,1) and ICPFLO(K,2), respectively. The constant mass flow rate (or flow rate multiplier) associated with advective resistor K is stored in RMDOT(K).

The RFN and RFNPNT arrays are analogous to the conductive resistor RCN and RCNPNT arrays.

The QTRAN internal node numbers associated with hydraulic resistor K are stored in T1RP(K) and T2RP(K), and the fluid configuration (FCFIG value) for hydraulic resistor K is stored in PTYPE(K). The GP values for hydraulic resistor K are stored in PGP(K,1) through PGP(K,J46) while the QTRAN internal MPID numbers for hydraulic resistor K are stored in PPROP(K,1) through PPROP(K,J46).

Advective Resistor ArraysINTEGER T1RF(J30)

INTEGER T2RF(J30)

INTEGER ICPFLO(J30,2)

DOUBLE PRECISION RMDOT(J30)

INTEGER RFN(MAXT)

INTEGER RFNPNT(J31)

IA40

IA41

IA42

RA20

IA43

IA64

Hydraulic Resistor ArraysINTEGER T1RP(J44)

INTEGER T2RP(J44)

INTEGER PTYPE(J44)

DOUBLE PRECISION PGP(J44,J46)

INTEGER PPROP(J44,J46)

INTEGER RPN(MAXP)

INTEGER RHNPNT(J47)

IA74

IA75

IA76

RA1

IA77

IA78

IA79


554

RPN(N) is the number of hydraulic resistors associated with node N. The RPNPNT array interacts with the RPN array in a manner similar to the conductive resistors and RCN/RCNPNT interactions.

The hydraulic network introduces an additional network that is solved as a separate group of nodes with its own solution procedure separate from the thermal network solution. This imposes some restriction on the node definitions. All hydraulic nodes must be specified before the purely thermal nodes are specified, but there is no restriction on how the nodes are to be numbered. As with gaps in the thermal nodes require an aliasing array to relate user nodes numbers to internal node number, the same is needed for the fluid nodes, plus index to relate internal node numbers to the internal thermal node numbers is required.

PALIAS(N) contains the model node number as specified by the user to the internal node number N. PIALAS(N) contains the internal thermal node number corresponding to the internal fluid node number N. HIALAS(N) contains the internal fluid node number corresponding to the internal thermal node number N.

The QTRAN internal node numbers associated with gray radiative resistor K are stored in T1RR(K), T2RR(K), and T3RR(K). The resistor subtype for gray radiative resistor K is stored in IGTYPE(K), while the QTRAN internal MPID number associated with the resistor (for emissivity, transmissivity, or extinction coefficient) is stored in IGPROP(K). The view factor distance (if any) is stored in GDIST(K), the F value is stored in GSFACT(K), and the A value (if any) is stored in GAREA(K).

INTEGER PALIAS(MAXP)

INTEGER PIALAS(MAXP)

INTEGER HIALAS(MMPHI)

IA85

IA86

IA87

Gray Radiative Resistor ArraysINTEGER T1RR(J13)

INTEGER T2RR(J13)

INTEGER T3RR(J13)

INTEGER IGTYPE(J13)

INTEGER IGPROP(J13)

DOUBLE PRECISION GDIST(J13)

DOUBLE PRECISION GSFACT(J13)

DOUBLE PRECISION GAREA(J13)

INTEGER RRN(MAXT)

INTEGER RRNPNT(J20)

IA11

IA12

IA13

IA14

IA15

RA30

RA8

RA23

IA37

IA20


The RRN and RRNPNT arrays are analogous to the conductive resistor RCN and RCNPNT arrays.

The QTRAN internal node numbers associated with wavelength-dependent radiative resistor K are stored in T1RW(K), T2RW(K), and T3RW(K). The resistor subtype for wavelength-dependent radiative resistor K is stored in IWTYPE(K), while the QTRAN internal MPID number associated with the resistor (for emissivity, transmissivity, or extinction coefficient) is stored in IWPROP(K). The view factor distance (if any) is stored in WDIST(K), the F value is stored in SFACTR(K), and the A value (if any) is stored in WAREA(K). The shortest and longest wavelengths associated with wavelength-dependent radiative resistor K are stored in WSPROP(K) and WLPROP(K), respectively.

The RWN and RWNPNT arrays are analogous to the conductive resistor RCN and RCNPNT arrays.

Wavelength Radiative Resistor ArraysINTEGER T1RW(J28)

INTEGER T2RW(J28)

INTEGER T3RW(J28)

INTEGER IWTYPE(J28)

INTEGER IWPROP(J28)

DOUBLE PRECISION WSPROP(J28)

DOUBLE PRECISION WLPROP(J28)

DOUBLE PRECISION SFACTR(J28)

DOUBLE PRECISION WAREA(J28)

DOUBLE PRECISION WDIST(J28)

INTEGER RWN(MAXT)

INTEGER RWNPNT(J29)

IA26

IA27

IA28

IA29

IA30

RA11

RA12

RA13

RA14

RA31

IA39

IA31


556

The QTRAN internal node number for capacitor K is stored in T1CAPS(K), while the QTRAN internal specific heat, density, and phase change MPID numbers are stored in CPROP(K), CRHO(K), and PIDID(K), respectively. The volume associated with capacitor K is stored in CVOL(K).

The CN and CNPNT arrays are analogous to conductive resistor arrays RCN and RCNPNT.

These arrays are used to store material property data if the MPID defined was NOT a phase change data set (IEVAL not set to PH in the QINDAT file). For these MPID sets, QTRAN stores the MPID numbers into the MID array in the order they appear in the QINDAT or MATDAT files. For QTRAN internal nemophilas change MPID number K, the MPID which is defined for this material is stored in MID(K).

The MDATA1 and MDATA2 values for QTRAN internal MPID K are stored in COEFF(K,2) to COEFF(K,J4) for MDATA1 and in EXPO(K,2) to EXPO(K,J4) for the MDATA2 values. COEFF(K,1) is used to store the number of MDATA1/MDATA2 data pairs, while EXPO(K,1) is used to store a numeric key for the evaluation option IEVAL. Specifically:

Capacitor Data ArraysINTEGER T1CAPS(J36)

INTEGER CPROP(J36)

INTEGER CRHO(J36)

DOUBLE PRECISION CVOL(J36)

INTEGER PIDID(J24)

INTEGER CN(MAXT)

INTEGER CNPNT(J36)

IA65

IA33

IA34

RA15

IA24

IA44

IA66

Non-Phase Change Material Property Data ArraysINTEGER MID(J3)

DOUBLE PRECISION COEFF(J3,J4)

DOUBLE PRECISION EXPO(J3,J4)

IA45

RA2

RA3


These arrays are used to store material property data if the MPID defined WAS a phase change data set (IEVAL set to PH in the QINDAT file). For these MPID sets, QTRAN stores your MPID numbers into the PID array in the order they appear in the QINDAT or MATDAT files. For QTRAN internal phase change MPID number K, the MPID which is defined for this material is stored in PID(K).

The MDATA1 and MDATA2 values for QTRAN internal phase change MPID K are stored in PIDSET(K,1) through PIDSET(K,J23). For phase change set K, the number of MDATA1/MDATA2 data pairs is stored in PIDPAR(K).

EXPO(K,1) 1--> Constant

2--> Table (linear unequal interval)

3--> Hermite table

4 --> Power Series

5--> Sutherland Equation

6--> Bingham Equation

7--> LCI data table

8--> Reciprocal Function

9--> Straight Line

10--> Arbitrary Order Polynomial

11--> User-Supplied Subroutine (UPROPS)

12--> Indexed Linearly Interpolated Table

13--> Indexed Hermite Interpolated Table

Phase Change Material Property Data ArraysINTEGER PID(J22)

INTEGER PIDPAR(J22)

DOUBLE PRECISION PIDSET(J22,J23)

IA46

IA23

RA10


558

MFID(K) contains the microfunction ID number (MFID) for the K'th microfunction which is defined in the QINDAT or MICRODAT files.

QCARD(K,1) contains an argument code for the microfunction which specifies whether the microfunction is to be a function of time, temperature, delta temperature, delta T4, or average temperature. Values are 0, 1, 2, 3, and 4, respectively.

QCARD(K,2) stores the microfunction option number as per Microfunction Library (Ch. 10).

QCARD(K,3) contains the number of parameters or data pairs entered for MDATA1 and MDATA2.

QCARD(K,4) contains a row pointer L into the P or TX/TY arrays where the MDATA values for the microfunction are stored.

For the K'th microfunction, L is stored in QCARD(K,4). The parameters MICDAT1-MICDAT4 are stored in P(L,1) through P(L,4) for those microfunctions which use parameters. For tabular microfunctions, the MICDAT1/MICDAT2 ordered pairs are stored in TX(L,2) -TX(L,J10) for MICDAT1 values and TY(L,2)-TY(L,J10) for MICDAT2 values. TX(L,1) contains the number of MDATA data pairs, and TY(L,1) is not used.

For the K'th QMACROfunction, IFLIST(K,1) contains the QTRAN internal node number to which the heat source is assigned.

IFLIST(K,2) contains the number of microfunctions used to build this QMACROfunction.

IFLIST(K,3) contains the T1 QTRAN internal node number.

Microfunction ArraysINTEGER MFID(J14)

INTEGER QCARD(J14,J15)

DOUBLE PRECISION P(J7,J9)

DOUBLE PRECISION TX(J9,J10)

DOUBLE PRECISION TY(J9,J10)

IA47

IA16

RA5

RA6

RA7

QMACROfunction ArraysINTEGER IFLIST(J17,J16)

DOUBLE PRECISION QMFACT(J17)

INTEGER QIP(MAXT)

INTEGER QIPPNT(J17)

IA17

RA24

IA38

IA18


IFLIST(K,4) contains the T2 QTRAN internal node number.

IFLIST(5)-IFLIST( 4+IFLIST(K,2) ) contains the QTRAN internal microfunction ID's which are used to build this QMACROfunction.

QMFACT(K) contains the scale factor for the K'th QMACROfunction.

QIP and QIPPNT are analogous to the conductive resistor RCN and RCNPNT arrays, respectively.

For the K'th MMACROfunction, IMLIST(K,1) contains the QTRAN internal node number to which the fluid mass flow rate is assigned.

IMLIST(K,2) contains the number of microfunctions used to build this QMACROfunction.

IMLIST(K,3) contains the P1 QTRAN hydraulic internal node number.

IMLIST(K,4) contains the P2 QTRAN hydraulic internal node number.

IMLIST(5)-IPLIST( 4+IMLIST(K,2) ) contains the QTRAN internal microfunction ID's which are used to build this MMACROfunction.

MMFACT(K) contains the scale factor for the K'th MMACROfunction.

MIP and MIPPNT are analogous to the conductive resistor RCN and RCNPNT arrays, respectively.

For the K'th TMACROfunction, ITLIST(K,1) contains the QTRAN internal node number to which the temperature source is assigned.

ITLIST(K,2) contains the number of microfunctions used to build this TMACROfunction.

ITLIST(K,3) contains the T1 QTRAN internal node number.

ITLIST(K,4) contains the T2 QTRAN internal node number.

ITLIST(5)-ITLIST( 4+ITLIST(K,2) ) contains the QTRAN internal microfunction IDs which are used to build this TMACROfunction.

MMACROfunction ArraysINTEGER IMLIST(J48,J49)

INTEGER MIP(MAXP)

INTEGER MIPPNT(MAXP)

DOUBLE PRECISION MMFACT(J48)

IA80

IA81

IA8 2

RA52

TMACROfunction ArraysINTEGER ITLIST(J18,J19)

DOUBLE PRECISION TMFACT(J18)

IA19

RA25


560

TMFACT(K) contains the scale factor for the K'th TMACROfunction.

For the K'th MMACROfunction, IPLIST(K,1) contains the QTRAN internal node number to which the temperature source is assigned.

IPLIST(K,2) contains the number of microfunctions used to build this MMACROfunction.

IPLIST(K,3) contains the P1 QTRAN internal hydraulic node number.

IPLIST(K,4) contains the P2 QTRAN internal node hydraulic number.

IPLIST(5)-IPLIST( 4+IPLIST(K,2) ) contains the QTRAN internal microfunction ID's which are used to build this MMACROfunction.

PMFACT(K) contains the scale factor for the K'th MMACROfunction.

QBASE(N) is the constant nodal heat source value associated with QTRAN internal node number N. Once read from the QINDAT file in subroutine INPUT4, it is never updated by QTRAN. However, it can be modified by any of the User-Supplied subroutines.

MBASE(N) is the constant nodal net mass flow rate value associated with QTRAN internal node number N. Once read from the QINDAT file in subroutine INPUT4, it is never updated by QTRAN. However, it can be modified by any of the User-Supplied subroutines.

PMACROfunction ArraysINTEGER IPLIST(J50,J51)

DOUBLE PRECISION PMFACT(J50)

IA83

RA53

Constant Nodal Heat Source ArraysDOUBLE PRECISION QBASE(MAXT) RA26

Constant Nodal Mass Flow Rate ArraysDOUBLE PRECISION MDBASE(MAXP) RA54


VELOCP is the average velocity at internal hydraulic node. PRHO is the average density at the internal hydraulic node. OPRESS is pressure from the previous interaction at the internal hydraulic node. PRESS is the current pressure at the internal hydraulic node. MDOTND is the net mass flow rate at the internal hydraulic node.

These arrays define parameters that apply to the hydraulic elements rather than results at the node locations. PRHOE is the average fluid density throughout an element. MDOTP is the mass flow rate of fluid flowing in a given hydraulic element. HYCCE is the hydraulic conductance throughout a given element. DIFHED is the difference in static head from one side of a hydraulic element to the other. QMDOTP is the volumetric flow rate of the fluid flowing through a given element.

Nodal Hydraulic/Fluid Flow ArraysDOUBLE PRECISION VELOCP(MAXP)

DOUBLE PRECISION PRHO(MAXP)

DOUBLE PRECISION OPRESS(MAXP)

DOUBLE PRECISION PRESS(MAXP)

DOUBLE PRECISION MDOTND(MAXP)

RA56

RA57

RA58

RA59

RA61

Elemental Hydraulic/Fluid Flow ArraysDOUBLE PRECISION PRHOE(J44)

DOUBLE PRECISION MDOTP(J44)

DOUBLE PRECISION HYCCE(J44)

DOUBLE PRECISION DIFHED(J44)

DOUBLE PRECISION QMDOTP(J44)

RA55

RA60

RA62

RA63

RA65


562

TFIX(N) contains the fixed, not fixed, or TMACROfunction controlled code for node N. The values are 0: for not fixed, 1 for fixed, and 2 for TMACROfunction controlled.

The QINDAT CFIX information is stored in the FIXNUM, SETTIM, and FIXVAL arrays. For the K'th CFIX data line in the QINDAT file, FIXNUM(K) contains the QTRAN internal node number whose TFIX classification is being changed, SETTIM(K) is the time at which the change is to occur, and FIXVAL(K) is the new TFIX control code (see TFIX above) which is 0, 1, or 2.

PFIX(N) contains the fixed or not fixed code for the internal hydraulic node N. The hydraulic fixed flag operates on the fluid pressure. If a Hydraulic node is fixed, the pressure at that node is fixed.

OTEMPS(K) is the temperature of internal node number K at the beginning of a time step for transient runs. It is not used for steady-state runs.

TEMPS(K) is the temperature of internal node number K for steady-state runs. It is also the temperature at time t+dt (the end of the time step) for transient runs.

The temperatures stored in these arrays are in the temperature scale specified by the QINDAT parameter ICCALC.

TERROR(N,1) through TERROR(N,J27) contains the iterative error for QTRAN internal node N for the last J27 iterations. TERROR(N,1) is the most recent iterative error while TERROR(N,J27) is the least recent iterative error. This array is used in conjunction with the EPSIT2 parameter for determining which nodes should continue to be iterated upon.

Node Classification Arrays (Fixed, Not Fixed, etc.)INTEGER TFIX(MAXT)

INTEGER FIXNUM(J21)

DOUBLE PRECISION SETTIM(J21)

INTEGER FIXVAL(J21)

INTEGER PFIX(MAXP)

IA32

IA21

RA9

IA22

IA84

Node Temperature ArraysDOUBLE PRECISION OTEMPS(MAXT)

DOUBLE PRECISION TEMPS(MAXT)

RA19

RA16

Temperature Error ArraysDOUBLE PRECISION TERROR(MAXT,J27) RA37


QVECT(N) is the net nodal heat flow into QTRAN internal node number N, not including the heat flow to/from the capacitors associated with node N. This value is updated in subroutine CCAPAC.

ALPHA(N) is the explicit stable time step associated with QTRAN internal node number N. It is updated in subroutine CCAPAC.

DTMAXA is an array that is used to store the DTMAX adjustments. See QTRAN Run Control Parameters and Node Number Declarations (Ch. 8). The DTMAXA data pairs from the QINDAT file are stored in the DTMAXA array in the order in which they appear in the QINDAT file. DTMAXA(1,1) contains the number of DTMAXA data pairs in the QINDAT file. DTMAXA(1,2) contains a pointer to the next row of the DTMAXA array that will be used to adjust the DTMAX value. DTMAXA(K,1) contains the new DTMAX values, while DTMAXA(K,2) contains the implementation times.

DTMXHA is an array that contains the time step increment for hydraulic solutions. When time gets to the implementation time defined by DTMAXA(K,2), a new fluid time step DTMAXH is defined by DTMXHA(K).

PRINTA is an array that is used to store the TPRINT adjustments. See QTRAN Run Control Parameters and Node Number Declarations (Ch. 8). The PRINTA data pairs from the QINDAT file are stored in the PRINTA array in the order in which they appear in the QINDAT file. PRINTA(1,1) contains the number of PRINTA data pairs in the QINDAT file. PRINTA(1,2) contains a pointer to the next row of the PRINTA array that will be used to adjust the TPRINT value. PRINTA(K,1) contains the new TPRINT values, while PRINTA(K,2) contains the implementation times.

Net Nodal Heat Flow ArrayDOUBLE PRECISION QVECT(MAXT) RA17

Explicit Stable Time Step ArrayDOUBLE PRECISION ALPHA(MAXT) RA18

Time Step Adjustment ArrayDOUBLE PRECISION DTMAXA(J32,J33)

DOUBLE PRECISION DTMXHA(J32)

RA21

RA64

Print Interval Adjustment ArrayDOUBLE PRECISION PRINTA(J34,J35) RA22


564

This array stores the indexes of the node that are defined in the plot output block.

These array are in common block RA43 and contain the node locations in the global coordinate system. The locations are packed in the same order that the nodes were defined in the node definition block.

Note that all three arrays are in the same named common block. This is the same as referencing the values as a doubly dimensioned array XYZCRD( MAXT, 3 ). Since this type of array is loaded by column in Fortran, the unit dimension for the array can not be used to reference the arrays. Either the MAXT value must be input for the specific case being executed, another subroutine called where the MAXT argument is included as one of the parameters passed and included in the declaration statement or only a single dimensioned array is specified and the actual index is calculated. For example, if the single index is used, the index would indicate the x location but MAXT and 2*MAXT would have to be added for the y and z locations respectively.

Another point is that the radial dimension for axisymmetric translation is always in the XRCRDV and the z-axis dimension is always in the YZCRDV arrays regardless of which plane was used to create the model. Thus if a model was created in the zx plane with the z-axis being defined as the radial direction all radial dimension would be in the XRCRDV array and the z-axis dimension which would have been along the x-axis would be in the YZCRDV array.

Plot Block Nodes ArrayINTEGER IPLTBK(MAXT) IA71

Node Locations ArraysDOUBLE PRECISION XRCRDV(MAXT)

DOUBLE PRECISION YZCRDV(MAXT)

DOUBLE PRECISION ZCORDV(MAXT)

RA43

RA43

RA43 DOUBLE PRECISION XYZCRD(MAXT,3)

RA43


These arrays contain information related to calculations and printout of the relaxation parameters. The INDRLX, IPRLXC, and IRRLXC arrays are pointers that indicate the type of relaxation applied to a given node and counters which indicate if the relaxation parameter is to be updated. IRLXGR keeps the node IDs that have the greater iterative delta or system error for each type of node. RLXTBS and RLXTBT contain the relaxation parameters that are input through the QINDAT File. The first index is the node type, advection, radiation, etc. and the second index is the type of parameter: maximum value, damping factor, and multiplying factor. RELAXV is the relaxation parameter used by the specified node, EFACTB is the system error multiplier which is the measure of how quick the node is converging. RELAXM is the relaxation multiplier that is applied at each node. This is how under relaxation is applied. RERROR is the iterative delta associated with each node. The last three values are retained in the array with the first index representing the oldest value. RLXGRP is a summary of the maximum values encountered for each node group. This information is saved for print purposes.

The internal node ID contained in array TCPLND is lumped into internal node ID defined at the same position in array TCPLCN. Although the internal energy balanced is performed as though the TCPLND node is the same as the TCPLCN node, its individuality is retained and is updated after each converged

Relaxation Parameters ArraysINTEGER INDRLX(MAXT)

INTEGER IPRLXC(MAXT)

INTEGER IRRLXC(MAXT)

INTEGER IRLXGR(J39,J43)

DOUBLE PRECISION RLXTBS(J39,J40)

DOUBLE PRECISION RLXTBT(J39,J40)

DOUBLE PRECISION RELAXV(MAXT)

DOUBLE PRECISION EFACTB(MAXT)

DOUBLE PRECISION RELAXM(MAXT)

DOUBLE PRECISION RERROR(MAXT,J41)

DOUBLE PRECISION RLXGRP(J39,J42)

IA68

IA69

IA70

IA72

RA44

RA45

RA46

RA47

RA48

RA49

RA50

Temperature Coupling ArraysINTEGER TCPLND (NTCPL)

INTEGER TCPLCN (NTCPL)

IA88

IA89


566

iteration. NTCPL is the total number of temperature coupling and is defined in common block IB106. The arrays are originally sized with variable J52 which is defined in the DIMS Common Block.

Chapter 12: Support Scripts and CodesPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

12 Support Scripts and Codes

Purpose 568

QINDAT File Listing 569

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisPurpose

568

PurposePatran Thermal is a preference selection in Patran for creating a model to be solved by P/THERMAL, the Patran thermal analysis module. The thermal model can be created and submitted directly from Patran. Analysis results can then be read into the Patran database or postprocessing with the various Patran tools, or for sharing the results with other Patran applications.

When the Patran Thermal preference is set, forms specific to input data required by the P/THERMAL module will appear under Loads/BCs, Element Properties, Materials and Analysis. The User Preference consists of the following:

• Element properties forms for defining properties of the elements in the model such as material.• Loads/BCs forms for defining Temperature, Convection, Heat Flux, Volumetric Heat, View

factors, Pressure (hydraulic) and Mass Flow boundary conditions.• Analysis form for defining solution type, parameters and job control.• Materials form for defining material properties or material templates.

If Full Run is set, the Apply selection in the Analysis form will create the appropriate interface files and execute the solver. The interface files created include:

• A neutral file• The analysis control files qin.dat and vf.ctl• The script for executing the model patq.inp• Materials data file Mat.dat

Patran Thermal is designed to support the functionality in P/THERMAL 2.6A, including the View factor code, the new coupled thermal/hydraulic networks and creation of a SINDA input deck. Overall, users will find Patran Thermal a much easier to use product, without sacrificing the powerful capabilities of P/THERMAL.

569Chapter 12: Support Scripts and CodesQINDAT File Listing

QINDAT File ListingAll file names in this listing are generic and may differ slightly for the computer you are using.

* This is a QTRAN input data file (QIN.DAT). Note that any* line beginning with an asterisk (*) is a comment. Also note that a* semicolon (;) denotes the end of a line so that comments may be placed* to the right of any semicolon. All comments are, of course, optional.* ########################################################################### # Q T R A N - Q T R A N -- Q T R A N -- Q T R A N -- Q T R A N # # Version: 13.1.082 (haddock.v13) # # Release Date: Thu Feb 17 11:14:02 PST 2005 # # Execution Node: blade(0x80fb2476, -2131024778) (SunOS 5.8) # # Execution Date: 17-FEB-2005 # # Execution Time: 13:45:09 # ###########################################################################

################################################### ### COPYRIGHT 1986-2004 BY ### ### MSC.Software CORP. ### ### ALL RIGHTS RESERVED. ### ###################################################******************************************************************** File written from P3** P3 Version: 2005 r2** Database: /users2/haddock/test/v13/pvf_plate/pvfplate01.db** Job Name: pvfplate01a** Job Description** pvfplate01a - heated plate radiating to one 0.6 meters away. ** File Creation Date: 17-Feb-05* File Creation Time: 13:44:48** ******************************************************************** If you wish to restart QTRAN from an existing nodal results file,* you may do so with a $RESTART command. The following $RESTART command* (which is commented out) requests QTRAN to be restarted from nodal* results file NR10.NRF, and to begin new nodal results file names* with "nnn" = 43, where the nodal results files are named NRnnn.NRF.* If a third field is not supplied, then the time from the nodal results* file NR10.NRF will be used as the initial time for the new run. If a* third field is supplied, it will be used as a new initial time for the* new execution. If the newtempflag is not zero then temperatures in the* defined initial temperature block will be used.* Since this $RESTART command is commented out, it will have no effect and* is used here simply as a place keeper for your convenience.***TRASYS_TR $RESTART nr000.nrf 43 newTime newtempflag**TRASYS_DY $RESTART nr000.nrf 43 newTime newtempflag******************************************************************************** Section 5.2.1: Output Labels*Sample master input file. Edit to fit your run requirements$INSERT title.dat * Insert the TITLE.DAT file. This* file will contain the neutral* file title data.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisQINDAT File Listing

570

** Example title data before the $INSERT title.dat command which includes* the title data from a translated PATRAN neutral file.** NOTE: $INSERT records are used throughout the QIN.DAT file to load* blocks of specific types of information at the appropriate* position. If the data or file is not available, the insert* record will have no effect. But, it will serve as a place* holder for future runs.**----------------------------------------------------------------------------*$ ; Terminate title data with a "$".******************************************************************************** Section 5.2.2: Input Data File Echo Option*IECHO Y ; Data Echo? (Y=yes,N=no)* * ***************************************************************************** Section 5.2.3: Temperature Scale Definition*$ECHO_ON*ISCALE K ; Output temperatures in Kelvin.ICCALC K ; Calculate using Kelvin.* Temperature options are R, F, K,* and C.TLABEL SECONDS ; Time units label is "SECONDS".* This is label only, no time units* conversion takes place.** ***************************************************************************** Section 5.2.4: Transient/Steady State Run Option Selection** Options for the hydraulic solution** HIOPT HSOL NTBHUP* ----- ---- ------HIOPT 0 2 200000 ; HIOPT = 0 = No hydraulic network* 1 = Hydraulic network only* 2 = Hydraulic network coupled* to thermal network* HSOL = 2 = Direct solver* NTBHUP = Number of thermal iterations* between hydraulic solutions* for steady state or the* number of time steps before* hydraulic update for* transient calculations.** Options for the thermal solution** IOPT SOL NITBUP MFLIPF* ---- --- ------ ------IOPT 1 0 4 8 ; IOPT = 3 = Steady State* Other IOPT options are:* 0 = data check only* 1 = transient* 2 = SS + Transient* 3 = Steady State (SS)* 4 = Transient + SS* 5 = SS + Transient + SS* SOL = 0 = STANDARD SOLUTION* = 1 = WEAKLY NONLINEAR


* SOLUTION.* = 2 = Direct solution* NITBUP = Number of ITerations* Between conductive* resistor UPdates if* SOL = 1. If SOL = 0,* NITBUP is how frequently* all nodes are updated. If* SOL=2, its the number of* iterative solutions* performed before before* another direct calculation* MFLIPF = Number of flip flops in* the convergence value* before a full bisection* solution is used.** ***************************************************************************** Section 5.2.5: Iteration Limit Parameters*IMAX 36 ; Maximum Iterations per time step.IMIN 9 ; Minimum Iterations per time step.* IMAX should always be greater than IMIN by* a factor of more than 2. If it is* desireable to follow a transient very* close, use value of IMAX = 30, IMIN = 8. * If one doesn't care how close the * transient is followed, then values such as * IMAX = 250, IMIN = 20 could be used.*IMAXSS 2000 2000 ; Maximum number of Steady State Iterations* for the thermal and hydraulic solutions* respectively.ISSDMP 2000 ; Number of Steady State Iterations per * output dump.* ***************************************************************************** Section 5.2.6: Control Parameters*DT 1.000000E-4 1.000000E-30 ; Initial and minimum* allowed time step.*TSTART 0.0000000000D-01 ; Start time.TSTOP 40.0000000000D+00 ; Stop time.*TSFMIN 6.5000000000D-01 ; Shrinking time step factor.TSFMAX 2.0000000000D+00 ; Expanding time step factor.*HYEPIS 1.0000000000D-04 ; Hydraulic convergence criteria*EPSISS 1.0000000000D-03 ; Steady State Convergence Criteria* (in degrees ICCALC).** EPSIT EPSIT2* ---------------- ------EPSIT 1.0000000000D-04 1.0D-07 ; EPSIT is the convergence criteria* (in degrees ICCALC). EPSIT2 is* the iterative delta cutout* criteria in degrees ICCALC. For* transient runs, any node whose* iterative delta is less than EPSIT2* will be removed from the iterative* process, thus conserving CPU time.* EPSIT2 should be several orders of* magnitude less than EPSIT. If* EPSIT2 is entered as blank or 0.0,* all nodes are iterated until the


572

* worst node has converged (this is* a conservative approach).*PERTUR 5.0000000000D-02 ; PERTUR is the perturbation* parameter (degrees ICCALC) for the* Newton's 2nd Order Scheme of the* SNPSOR algorithm. ** RELAXS IFSRLX* ------ ------RELAXS 1.0000000000D+00 1 ; Steady State Relaxation Parameters* and control flag. RELAXS is the* initial relaxation value or a* constant if input as a negative* value. IFSRLX indicates the type* of relaxation values that are to* be calculated.* IFSRLX = 0 (default) System relaxation value which* applies to all nodes is calculated.* IFSRLX = 1 Group relaxation values are calculated.* Seperate relaxation parameters are * determined dependent on the type of * boundary condition (Advection,* radiation, convection or conduction) * at the node.* IFSRLX = 2 Individual relaxation parameters are* determined on a node by node basis.** Steady state relaxation controls** MAXIMUM DAMPER MULTIPLIER* ------- ------ ----------RLXSAT 1.999 0.30 1.00 ; Advection relaxation controlsRLXSRT 1.999 0.80 1.00 ; Radiation relaxation controlsRLXSHT 1.999 0.94 1.00 ; Convection relaxation controlsRLXSCT 1.999 0.95 1.00 ; Conduction relaxation controlsRLXSST 1.999 0.95 1.00 ; System relaxation controls** The relaxation controls apply to specific nodes that have the specific* type of boundary conditions defined. If any node has advection, then* those nodes use the advection controls. If nodes have more than* one type of boundary condition, then the controls with the following* order will apply: advection, radiation, convection and conduction.* System controls apply when only one relaxation parameter is calculated* for the entire system of nodes being analyzed.** MAXIMUM is the upper limit to the relaxation parameter.* Valid values are between 1.0 and 1.999* DAMPER is the factor applied to the increase in the relaxation* parameter. This serves to retard the rate of increase* in the relaxation parameter.* Valid values are between 0.001 and 1.0* MULTIPLIER is a multiplier that is applied to the application of* the relaxation parameter. This is a means of applying* under relaxation to node groups.* Valid values are between 0.001 and 1.0*** RELAXT IFTRLX* ------ ------RELAXT 1.0000000000D+00 1 ; Transient Relaxation Parameters* and control flag. RELAXT is the* initial relaxation value or a* constant if input as a negative* value. IFTRLX indicates the type* of relaxation values that are to* be calculated.* IFTRLX = 0 (default) System relaxation value which


* applies to all nodes is calculated.* IFTRLX = 1 Group relaxation values are calculated.* Seperate relaxation parameters are * determined dependent on the type of * boundary condition (Advection,* radiation, convection or conduction) * at the node.* IFTRLX = 2 Individual relaxation parameters are* determined on a node by node basis.** Transient relaxation controls** MAXIMUM DAMPER MULTIPLIER* ------- ------ ----------RLXTAT 1.999 0.95 1.00 ; Advection relaxation controlsRLXTRT 1.999 0.95 1.00 ; Radiation relaxation controlsRLXTHT 1.999 0.95 1.00 ; Convection relaxation controlsRLXTCT 1.999 0.95 1.00 ; Conduction relaxation controlsRLXTST 1.999 0.95 1.00 ; System relaxation controls*** BETA BETMIN BETMAX* ----- ------ ------BETA 1.0000000000D+00 0.0000D+00 1.0000D+00** BETA is the Explicit/Implicit Ratio * 0.0 = fixed fully explicit;* -1.0 = fixed fully implicit;* > 0.0 = adaptive explicit/implicit.* BETMIN is the minimum BETA value (Default = 0.0)* BETMAX is the maximum BETA value (Default = 1.0)** DELMAX MINTMP MAXTMP* ------ ------ ------DELMAX 1000.0 -1.000D+30 1.000D+30** DELMAX is the Maximum allowed iterative delta.* (DEFAULT = 1000.0)* MINTMP is the Minimum allowable calculated temperature.* (Default = -1.000D+30)* MAXTMP is the Maximum allowable calculated temperature.* (Default = 1.000D+30)** PCBAND CPDELT* ---------------- ------PCBAND 1.0000000000D-00 1000.0 ; PCBAND is the Phase Change Band* width in degrees ICCALC for* problems using QTRAN's standard* phase change algorithm. CPDELT * (if blank or non-zero) is the* temperature integration step over * which the Cp curve will be * evaluated to obtain an integrated * average Cp value for a time step. * If any Cp curves have "spikes", * CPDELT should be set to some * temperature value significantly * smaller (1/5 to 1/10 of the spike* width).** GRAVTY GX GY GZ* ------ -- -- --GRAVTY 0.0, 0.0, 0.0, 0.0** ; Gravitational constant, GX, GY, GZ Gravity * ; field in x, y, and z direction for * ; determination of gravity heads.*


574

SBC 0.0 ; Stephan-Boltzmann Constant* (if 0.0 is entered, SBC will* default according to the ICCALC* temperature scale to either SI* units or to English units).**>>>>>>>> RADIATION <<<<<<<<<<<<<<<<<<<<<<<<<<<** ___ STEFAN-BOLTZMANN CONSTANT ___** SBC 1.7140E-9 ; BTU/HR/FT2/R4* SBC 1.712E-9 ; BTU/HR/FT2/R4 (EXPERIMENTAL)* default for English units* SBC 2.8567E-11 ; BTU/MIN/FT2/R4* SBC 4.7611E-13 ; BTU/SEC/FT2/R4* SBC 1.7993E-8 ; BTU/HR/FT2/K4* SBC 2.9988E-10 ; BTU/MIN/FT2/K4* SBC 4.9980E-12 ; BTU/SEC/FT2/K4* SBC 1.1903E-11 ; BTU/HR/IN2/R4* SBC 3.3063E-15 ; BTU/SEC/IN2/R4* SBC 5.01783E-10 ; WATTS/FT2/R4* SBC 3.4846E-12 ; WATTS/IN2/R4* SBC 5.26753E-9 ; WATTS/FT2/K4* SBC 5.40113E-13 ; WATTS/CM2/R4* SBC 3.6580E-11 ; WATTS/IN2/K4* SBC 5.6699E-12 ; WATTS/CM2/K4* SBC 5.6699E-5 ; ERGS/SEC/CM2/K4* SBC 5.6696E-8 ; WATTS/M2/K4 (EXPERIMENTAL)* default for SI units* SBC 5.6696D-14 ; WATT/mm2/K4** ****************************************************************************DCMF 1 ; DisContinuous Macrofunction Flag* 0 --> off* 1 --> on (discontinuous * macrofunctions may exist).** ***************************************************************************** Section 5.2.7: Resistor/Capacitor/Qmacro Data Print Option** C H R W A Cap Q HA HC* - - - - - --- - -- --IRQFLO 0 0 0 0 0 0 0 0 0**------------------------------------------------------------------------------** Nodal results file format*NRFORM 0 ; = -> 0 Binary file* ; = -> 1 ASCII file**------------------------------------------------------------------------------** Which records are to be put in the nodal results file** 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18* - - - - - - - - - -- -- -- -- -- -- -- -- --*IDMNRF 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0** ; = -> 0 Record is not put in nodal results file* ; = -> 1 Record is put in nodal results file** Entry Number 1 = Temperatures* Entry Number 2 = Net nodal heat flow* Entry Number 3 = Explicit stable time step


* Entry Number 4 = QMACRO function heat input* Entry Number 5 = QBASE heat input to each node* Entry Number 6 = Total heat input to each node* Entry Number 7 = Temperature error* Entry Number 8 = Average convection heat transfer coefficient** Entry Number 9 = Pressure at a given node from the hydraulic solution* Entry Number 10 = Mass flow rate at a given node from the * hydraulic solution** Entry Number 11 = Mass flow rate in hydraulic element* Entry Number 12 = Differential head in hydraulic element* Entry Number 13 = Fluid velocity in hydraulic element* Entry Number 14 = Volume flow rate in hydraulic element** Entry Number 15 = Applied heat flux* Entry Number 16 = Convective heat flux* Entry Number 17 = Radiate heat flux* Entry Number 18 = Total heat flux** ***************************************************************************** Section 5.2.8 Data: Maximum Time Step Controls** Section 5.2.8.1: Initial Maximum Time Step** DTMAX DTMAXH* ----- ------DTMAX 10.0 100.0 ; Initial maximum Thermal and Hydraulic* time steps.** ---------------------------------------------------------------------------** Section 5.2.8.2: Maximum Allowable Time Step Adjustments** New DT Time New HDT* ------ ---- -------*DTMAXA 1.0 14.0 0.8 ; Sets the maximum time step size* to 1.0 at time = 14.0 and the* hydraulic time step becomes 0.8.* The line has been commented* out.** ---------------------------------------------------------------------------*$ ; End DTMAXA input with a "$".** ***************************************************************************** Section 5.2.9 Data: Node Definitions*$INSERT pnode.dat* Pressure nodes that will be used in the* hydraulic flow network calculations.* Hydraulic nodes must be the first nodes * specified.*$INSERT node.dat * Insert the NODE.DAT file. This* file will contain the node numbers* generated by PATRAN and PATQ.*$INSERT vfnode.dat * Insert the VFNODE.DAT file. This* file contains the node numbers* generated by P/VIEWFACTOR.**----------------------------------------------------------------------------


576

*$ ; Terminate the DEFNOD data with a "$".**----------------------------------------------------------------------------*$INSERT tcoupl.dat* Insert the TCOUPL.DAT file. This* file contains the node IDs which are* to be included in the analysis as if* they were part of the companion node.* Node location and identity are preserved.**------------------------------------------------------------------------------*$ ; Terminate with a "$"**----------------------------------------------------------------------------*$INSERT nodxyz.dat* Insert the NODXYZ.DAT file. This* file contains the node locations and* the values are stored according to* their definition of the nodes in the* previous section.**------------------------------------------------------------------------------*$ ; Terminate with a "$"*** ***************************************************************************** Section 5.2.10 Data: Print Controls** Section 5.2.10.1: Initial Output Print Interval*TPRINT 1.0 ; Initial Transient Print Interval.** ---------------------------------------------------------------------------** Section 5.2.10.2: Output Print Interval Adjustments** New TPRINT Time* ---------- ----*PRINTA 0.2 1.1 ; Sets the print interval size* This statement forces an output* at 1.1 eventhough the print * increment is 1.0. The print* interval is changed to 0.2 and* resulting print times would be* 1.1, 1.3, 1.5, 1.7, etc.*PRINTA -0.5 2.3 ; Sets the print interval size* The negative sign on this * statement would force* print at 2.3 and on multiples* of 0.5 there after. For example* 2.3, 2.5, 3.0, etc.*PRINTA 1.0 5.0 ; Sets the print interval size*PRINTA 10.0 10.0 ; Sets the print interval size*PRINTA 50.0 50.0 ; Sets the print interval size* At time 50 the print interval * will be changed to 50.** *$ ; Terminate PRINTA data with a "$".** ---------------------------------------------------------------------------


** Section 5.2.10.3: Nodal Print Block Definitions** NOTE: If no PBLOCK data is specified, the default is* to print out all nodal data. With "PBLOCK 1 1 1" specified as below,* printout of all but node 1 into the QOUT.DAT will be suppressed.* All node data will still be printed out into the nodal results files* generated by QTRAN. **PBLOCK 1 1 1** ---------------------------------------------------------------------------** Section 5.2.10.4: Nodal Plot Block Definitions** NOTE: If no IPLTBK data is specified, the plot file is not opened.* With "IPLTBK 1 3 1" specified only those nodes between 1 and 3* will be output to the plot file after each converged calculation.* Also, only temperature in ICCALC units are output to the file.**IPLTBK 1 3 1*$ ; The print and plot block is terminated with a "$".**############################################################################** Section 5.3: MATERIAL PROPERTY SECTION*$INSERT mat.dat * Insert the material properties* data file MAT.DAT.*$ ; End the material property data Section 5.3 with a "$".**############################################################################** Section 5.4.0: RESISTOR AND CAPACITOR DATA SET DEFINITIONS** Section 5.4.1: Resistor Data Sets**----------------------------------------------------------------------------** This portion of the QIN.DAT file has a number of optional "$STATUS message" * commands. These can be of some help in the event that QTRAN encounters an* error and for some reason you have difficulty in ascertaining where the* error occurred.**----------------------------------------------------------------------------*$STATUS Beginning to read conduc.dat*$INSERT conduc.dat,C ; the ",C" implies a binary file.*$STATUS conduc.dat input finished.**----------------------------------------------------------------------------*$STATUS Beginning to read fres.dat*$INSERT fres.dat ; hydraulic data*$STATUS fres.dat input finished.**----------------------------------------------------------------------------*$STATUS Beginning to read convec.dat*$INSERT convec.dat


578

$INSERT gap_convec.dat ; Gap convection between regions$INSERT ../convec.dat.apnd ; Supplemental resistors defined by the user*$STATUS convec.dat input finished.**----------------------------------------------------------------------------** These commands are used to $INSERT the radiation resistor data generated* by P/VIEWFACTOR.*$STATUS Beginning to read vfres.dat.*$INSERT vfres.dat,RAD ; the ",RAD" inplies a binary file.*$STATUS vfres.dat input finished.***TRASYS_SS $INSERT travrc.dat ; Uncomment the trasys file based on the**TRASYS_TR $INSERT travrc.dat ; type of analysis performed.**TRASYS_DY $INSERT trdynrdk.dat ; SS Steady State, TR Transient**TRASYS_DY $INSERT trcdrc.dat ; DY are for dynamic view factors*$INSERT trarst.dat ; Radiation resistors defined by TRASYS$INSERT nevrst.dat ; Radiation resistors defined by NEVADA$INSERT ambn_rad.dat ; Radiation to an ambient node.$INSERT gap_rad.dat ; Gap radiation between two nodes.$INSERT rad_dir.dat ; Direct translation radiation network.**----------------------------------------------------------------------------*$STATUS Beginning to read res.dat.*$INSERT res.dat*$STATUS res.dat input finished.**----------------------------------------------------------------------------*$ ; Terminate the resistor input with a "$".*$STATUS All resistor data input is complete.** ***************************************************************************** Section 5.4.2: Capacitor Data Sets*$STATUS Beginning to read cap.dat.*$INSERT cap.dat,CAP ; the ",CAP" implies a binary file.$INSERT ../cap.dat.apnd ; Supplemental capacitors defined by the user*$STATUS cap.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the capacitor data input with a "$".*$STATUS All thermal network data has now been successfully input.**############################################################################** Section 5.5.1: Microfunction Definitions*$STATUS Read in the micro.dat file.*$INSERT micro.dat$INSERT micro_st.dat***TRASYS_DY $INSERT tramic.dat ; Uncomment the appropriate file depending


**TRASYS_TR $INSERT tramic.dat ; if it were a transient or dynamic TRASYS $INSERT nevmic.dat ; Time dependent heating defined by NEVADA*$STATUS micro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the microfunction data input with a "$".*$STATUS All microfunction data has now been successfully input.** ***************************************************************************** Section 5.5.2: Heat Source/Sink Macrofunction Definitions*$STATUS Read in the qmacro.dat file.*$INSERT qmacro.dat$INSERT qmacro_dir.dat***TRASYS_DY $INSERT traqma.dat ; Uncomment heat flux file depending if**TRASYS_TR $INSERT traqma.dat ; TRASYS run was transient or dynamic*$INSERT nevqma.dat ; Variable heat load defined by NEVADA*$STATUS qmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the QMACROfunction data with a "$".*$STATUS All QMACROfunction data has now been successfully input.** ***************************************************************************** Section 5.5.3 Data: Temperature Control Macrofunctions*$STATUS Read in the tmacro.dat file.*$INSERT tmacro.dat$INSERT tmacro_dir.dat*$STATUS tmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the TMACROfunction data with a "$".*$STATUS All TMACROfunction data has now been successfully input.** ***************************************************************************** Section 5.5.4 Data: Mass Flow Hydraulic Control Macrofunctions*$STATUS Read in the mmacro.dat file.*$INSERT mmacro.dat$INSERT mmacro_dir.dat*$STATUS mmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the MMACROfunction data with a "$".*$STATUS All MMACROfunction data has now been successfully input.** ***************************************************************************


580

** Section 5.5.5 Data: Pressure Hydraulic Control Macrofunctions*$STATUS Read in the pmacro.dat file.*$INSERT pmacro.dat$INSERT pmacro_dir.dat*$STATUS pmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the PMACROfunction data with a "$".*$STATUS All MMACROfunction data has now been successfully input.** ***************************************************************************** Section 5.5.6 Data: Initially Fixed Nodes*$STATUS Read in the tfix.dat file.*$INSERT tfix.dat *$STATUS tfix.dat input complete.**----------------------------------------------------------------------------** Section 5.5.6 Data: Initially Fixed Pressure Nodes*$STATUS Read in the pfix.dat file.*$INSERT pfix.dat *$STATUS pfix.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the fixed node data with a "$".*$STATUS Fixed node data has now been successfully input.** ***************************************************************************** Section 5.5.7 Data: Nodal Classification Changes** [ None used for this problem. ]*$ ; Terminate CLASSification changes with a "$".** ***************************************************************************** Section 5.5.8 Data: Initial Global Temperature and Heat Source*TINITL 20.0 C ; Globally assign an initial * temperature of 20.0 C *PINITL 101325.0 ; Globally assign an initial * pressure of 101325 nt/m2*MGLOBL 0.0 ; Globally assign an initial * mass flow rate 0.0 kg/sec** MPIDGH MPIDGX MPIDGY MPIDGZ* ------ ------ ------ ------MPIDGH 0 0 0 0** ; Material property IDs which define


* ; variable gravity fields.* ; MPIDGH - Field value used for units* ; conversions m/sec2* ; MPIDGX - Gravity along x-axis* ; MPIDGY - Gravity along y-axis* ; MPIDGZ - Gravity along z-axis*QGLOBL 0.00000000000D+00 ; Globally assign a per-unit-volume* heat flux of 0.0.** ***************************************************************************** Section 5.5.9: Individual Assignments of Initial Temperatures**$STATUS Read in the temp.dat file.*$INSERT temp.dat*$STATUS temp.dat data input complete.**----------------------------------------------------------------------------** Section 5.5.9: Individual Assignments of Initial Pressures*$STATUS Read in the press.dat file.*$INSERT press.dat*$STATUS press.dat data input complete.**----------------------------------------------------------------------------*$ ; Terminate the initial temperature and pressure data with a "$".*$STATUS Initial temperature and pressure data input complete.** ***************************************************************************** Section 5.5.10: Individual Assignments of Constant Heat Sources*$STATUS Beginning to read qbase.dat.*$INSERT qbase.dat $INSERT qbase_dir.dat**TRASYS_SS $INSERT trqbas.dat ; uncomment if this is a steady state* TRASYS run.$INSERT nevbas.dat ; Constant heat load defined by NEVADA*$STATUS qbase.dat data input complete.**----------------------------------------------------------------------------** Section 5.5.10: Individual Assignments of Constant mass flow rate*$STATUS Beginning to read mdbase.dat*$INSERT mdbase.dat*$STATUS mdbase.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the constant heat source and mass flow rate data with a "$".** ***************************************************************************** END OF QIN DATA FILE


582

** ***************************************************************************** User input may follow** ***************************************************************************


584


586

; End the material property data Section 5.3 with a "$".**############################################################################** Section 5.4.0: RESISTOR AND CAPACITOR DATA SET DEFINITIONS** Section 5.4.1: Resistor Data Sets**----------------------------------------------------------------------------


** This portion of the QIN.DAT file has a number of optional "$STATUS message" * commands. These can be of some help in the event that QTRAN encounters an* error and for some reason you have difficulty in ascertaining where the* error occurred.**----------------------------------------------------------------------------*$STATUS Beginning to read conduc.dat*$INSERT conduc.dat,C ; the ",C" implies a binary file.*$STATUS conduc.dat input finished.**----------------------------------------------------------------------------*$STATUS Beginning to read fres.dat*$INSERT fres.dat ; hydraulic data*$STATUS fres.dat input finished.**----------------------------------------------------------------------------*$STATUS Beginning to read convec.dat*$INSERT convec.dat $INSERT gap_convec.dat ; Gap convection between regions$INSERT ../convec.dat.apnd ; Supplemental resistors defined by the user*$STATUS convec.dat input finished.**----------------------------------------------------------------------------** These commands are used to $INSERT the radiation resistor data generated* by P/VIEWFACTOR.*$STATUS Beginning to read vfres.dat.*$INSERT vfres.dat,RAD ; the ",RAD" inplies a binary file.$INSERT trarst.dat ; Radiation resistors defined by TRASYS$INSERT nevrst.dat ; Radiation resistors defined by NEVADA$INSERT gap_rad.dat ; Gap radiation between two nodes.*$STATUS vfres.dat input finished.**----------------------------------------------------------------------------*STATUS Beginning to read res.dat.*$INSERT res.dat*$STATUS res.dat input finished.**----------------------------------------------------------------------------*$ ; Terminate the resistor input with a "$".*$STATUS All resistor data input is complete.** ***************************************************************************** Section 5.4.2: Capacitor Data Sets*$STATUS Beginning to read cap.dat.*$INSERT cap.dat,CAP ; the ",CAP" implies a binary file.$INSERT ../cap.dat.apnd ; Supplemental capacitors defined by the user


588

*$STATUS cap.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the capacitor data input with a "$".*$STATUS All thermal network data has now been successfully input.**############################################################################** Section 5.5.1: Microfunction Definitions*$STATUS Read in the micro.dat file.*$INSERT micro.dat$INSERT tramic.dat ; Time dependent heating defined by TRASYS$INSERT nevmic.dat ; Time dependent heating defined by NEVADA*$STATUS micro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the microfunction data input with a "$".*$STATUS All microfunction data has now been successfully input.** ***************************************************************************** Section 5.5.2: Heat Source/Sink Macrofunction Definitions*$STATUS Read in the qmacro.dat file.*$INSERT qmacro.dat$INSERT traqma.dat ; Variable heat load defined by TRASYS$INSERT nevqma.dat ; Variable heat load defined by NEVADA*$STATUS qmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the QMACROfunction data with a "$".*$STATUS All QMACROfunction data has now been successfully input.** ***************************************************************************** Section 5.5.3 Data: Temperature Control Macrofunctions*$STATUS Read in the tmacro.dat file.*$INSERT tmacro.dat*$STATUS tmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the TMACROfunction data with a "$".*$STATUS All TMACROfunction data has now been successfully input.** ***************************************************************************** Section 5.5.4 Data: Mass Flow Hydraulic Control Macrofunctions*$STATUS Read in the mmacro.dat file.*$INSERT mmacro.dat


*$STATUS mmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the MMACROfunction data with a "$".*$STATUS All MMACROfunction data has now been successfully input.** ***************************************************************************** Section 5.5.5 Data: Pressure Hydraulic Control Macrofunctions*$STATUS Read in the pmacro.dat file.*$INSERT pmacro.dat*$STATUS pmacro.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the PMACROfunction data with a "$".*$STATUS All MMACROfunction data has now been successfully input.** ***************************************************************************** Section 5.5.6 Data: Initially Fixed Nodes*$STATUS Read in the tfix.dat file.

*$INSERT tfix.dat *$STATUS tfix.dat input complete.**----------------------------------------------------------------------------** Section 5.5.6 Data: Initially Fixed Pressure Nodes*$STATUS Read in the pfix.dat file.*$INSERT pfix.dat *$STATUS pfix.dat input complete.**----------------------------------------------------------------------------*$ ; Terminate the fixed node data with a "$".*$STATUS Fixed node data has now been successfully input.** ***************************************************************************** Section 5.5.7 Data: Nodal Classification Changes** [ None used for this problem. ]*$ ; Terminate CLASSification changes with a "$".** ***************************************************************************** Section 5.5.8 Data: Initial Global Temperature and Heat Source*TINITL 20.0 C ; Globally assign an initial * temperature of 20.0 C *PINITL 101325.0 ; Globally assign an initial


590

* pressure of 101325 nt/m2*MGLOBL 0.0 ; Globally assign an initial * mass flow rate 0.0 kg/sec** MPIDGH MPIDGX MPIDGY MPIDGZ* ------ ------ ------ ------MPIDGH 0 0 0 0** ; Material property IDs which define* ; variable gravity fields.* ; MPIDGH - Field value used for units* ; conversions m/sec2* ; MPIDGX - Gravity along x-axis* ; MPIDGY - Gravity along y-axis* ; MPIDGZ - Gravity along z-axis*QGLOBL 0.00000000000D+00 ; Globally assign a per-unit-volume* heat flux of 0.0.** ************************************Section 5.5.9: Individual Assignments of Initial Temperatures**$STATUS Read in the temp.dat file.*$INSERT temp.dat*$STATUS temp.dat data input complete.**----------------------------------------------------------------------------** Section 5.5.9: Individual Assignments of Initial Pressures*$STATUS Read in the press.dat file.*$INSERT press.dat*$STATUS press.dat data input complete.**----------------------------------------------------------------------------*$ ; Terminate the initial temperature and pressure data with a "$".*$STATUS Initial temperature and pressure data input complete.** ***************************************************************************** Section 5.5.10: Individual Assignments of Constant Heat Sources*$STATUS Beginning to read qbase.dat.*$INSERT qbase.dat $INSERT trqbas.dat ; Constant heat load defined by TRASYS$INSERT nevbas.dat ; Constant heat load defined by NEVADA*$STATUS qbase.dat data input complete.**----------------------------------------------------------------------------** Section 5.5.10: Individual Assignments of Constant mass flow rate*$STATUS Beginning to read mdbase.dat*$INSERT mdbase.dat*$STATUS mdbase.dat input complete.*


*----------------------------------------------------------------------------*$ ; Terminate the constant heat source and mass flow rate data with a "$".** ***************************************************************************** END OF QIN DATA FILE** ***************************************************************************

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisQSTAT - QTRAN STATUS

592

QSTAT - QTRAN STATUSQSTAT is a stand alone program that can be executed while QTRAN is being executed or after execution is completed and will yield convergence information associated with the job. Communication between QSTAT and QTRAN is through a statbin file. To prevent both codes from having the file open at the same time they each will drop “hidden” files while it is processing the file. The other code can not access the file until the “hidden” file is deleted.

By typing qstat in the command line while you are in the directory where the job is being executed, a convergence history will be output. For the steady state case all iterations will be output to the current point in the calculation. If a transient analysis is being analyzed the iteration status for the current time step will be displayed. There are a number of command line option that can be used with qstat.

qstat bThe number of iteration can become large and if you are monitoring a job and would like to see the being and ending iterations the B option will limit the output and still the information output and limit it to about 25 lines. The information in the file includes the iteration number, the node ID of the node that had the

largest iterative delta temperature, the maximum iterative delta times its relaxation value, the node temperature and the new relaxation value for the node in question. The iterative delta time the relaxation value is the temperature change that will be applied to the node for the next iteration cycle. The QTRAN cpu time stamp is also included

593Chapter 12: Support Scripts and CodesQSTAT - QTRAN STATUS

qstat tRather than seeing some of the iterations at the being and end of the STATBIN file, the “t” option supplies a limited output for the latest iterations.

qstat c 15If you wish to closely monitor a job, the qstat c option will provide the same output as the “t” option but will give a status report approximately every 1.5 minutes. It will repeat the process 10 times or until the job has finished. If you wish to get more than 10 outputs a second parameter can be specified that defines how many outputs are desired.

qstat sFor transient run you get the same report with the qstat or qstat with the “s” option; however, it only applies to the latest time step as shown below. The status file number is an indication as to how many time steps have been executed to this point. The time listed is the old time. The time variable is not advanced until a converged solution has been obtained thus the actual time represented in the following example is 10 seconds.


594

qstat lAt times it many be desirable to see more than one time point to observe the progression of the time step. The “l” option provides this capability. The STATBIN file will not be reset after each converged solution but will continue to put the convergence status in the file until it is turned off with a qstat s command at which time the STATBIN will revert to the default of a single time step per file. An example of multiple output is shown below.


qstat gOn long running jobs it could be desirable to do more than monitor the progression of the execution. The “g”, “p” and “r” option give the user the ability to interface with the job during execution and allows them to change several of the solution controls. The “g” option will interrupt a job and print a file with these alterable parameters to a file at that time. The execution will continue as soon as it has finished writing the old parameter file. The qstat g command can be issued prior to executing QTRAN if for example it was desired to get the parameters from a restart job.

qstat pThe qstat p allows one to edit an old parameters file or create a new one from default values. Execution of this command enables the user to get a help file with a summary of what can be accomplished with the dynamic series of qstat option.


596

The parameters that can be altered with the “p” option are listed below. While manipulation the parameters with this option the QTRAN problem will continue to run.


qstat rThe command qstat r is a combination of qstat g followed by qstat p. However, in this case the the QTRAN run will be interrupted for as much as 15 minutes wall clock time while you make the changes. After that time the QTRAN run will resume and you can continue modifying the parameters file and submit it later as the same as if you had issued the qstat p command.


598

Appendix A: ReferencesPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

A References

References 600

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisReferences

600

References1. Hughes, Thomas J. R. “Unconditionally Stable Algorithms for Nonlinear Heat Conduction,”

Computer Methods in Applied Mechanics and Engineering, Vol 10, pp. 135-139, North-Holland Publishing Company, 1977.

2. Forsythe, G. E. and Wasow, W. R. Finite Difference Methods for Partial Differential Equations, pp. 119-121, John Wiley & Sons, New York, 1960.

3. James, M. L., Smith, G. M., and Wolford, J. C. Applied Numerical Methods for Digital Computation with FORTRAN and CSMP, 2nd ed., pp. 111-113, IEP - A Dun-Donnelley Publisher, New York, 1977.

4. White, F. M. Viscous Fluid Flow, McGraw-Hill, 1974.5. Siegel, R., and Howell, J. R. Thermal Radiation Heat Transfer, 2nd ed., McGraw-Hill, 1981.6. Karlekar, B. V., and Desmond, R. M. Engineering Heat Transfer, West Publishing Co, 1977.7. Gebhart, B. Heat Transfer, 2nd ed., McGraw-Hill, 1971.8. Bird, R. B., Stewart, W. E., and Lightfoot, E. N. Transport Phenomena, John Wiley & Sons, 1960.9. Hageman, L. A., and Young, D. M. Applied Iterative Methods, Academic Press, New York, 1981.

10. Ames, W. F. Numerical Methods for Partial Differential Equations, 2nd ed., Academic Press, New York, 1977.

11. Champman, A. J. Heat Transfer, 4th ed,.MacMillan Publishing Company, 1984.12. Kraus, A. D., and Bar-Cohen, A. Thermal Analysis and Control of Electronic Equipment, pp. 210-

211, Hemisphere Publishing Corp., 1983.13. Shlyhov, Y.L.. "Calculating Thermal Contact Resistance of Machined Metal Surfaces,"

Teploenergetika, Vol 12, No. 10, pp 79-83, 1965.14. Kreith, Frank, and Bohn, Mark S., Principles of Heat Transfer, 5th ed., PWS Publishing

Company, 1997.

Appendix B: Mid Templates Supplied in Templatebin and TemplatetxtPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

B Mid Templates Supplied in Templatebin and Templatetxt

Materials References, Classification, Quality Code and Index 602

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisMaterials References, Classification, Quality Code and Index

602

Materials References, Classification, Quality Code and Index

REVISED 4/8/69. Ref # MATERIAL PROPERTIES REFERENCES 1 PERRY J H CHEMICAL ENGINEERS HANDBOOK 4TH ED 1963 2 MCADAMS W H HEAT TRANSMISSION 3RD ED 1954 3 " LIQUID METALS HANDBOOK 2ND ED 1952 4 MARKS L S MECHANICAL ENGINEERS HANDBOOK 5TH ED 1951 5 FLEMING P PRIVATE COLLECTION OF PLASTICS DATA 1968 6 " MATERIALS ENGR MATL SELECTOR ISSUE 1967 7 PFEIFER H PRIVATE COLLECTION OF MATERIALS DATA 1968 8 JAMES E PROPERTIES OF CHEMICAL EXPLOSIVES UCRL 14592 1965 9 " ASRE DATA BOOK 10 " AIRPLANE AIR CONDITIONING ENGR DATA 1952 11 " INTERNATIONAL CRITICAL TABLES 1926 12 JOHNSON A I THERMAL CONDUCTIVITY CHART FOR GASES 1954 13 HILSENRATH J TABLES OF THERMAL PROPERTIES OF GASES NBS 564 1955 14 TIPTON C R JR THE REACTOR HANDBOOK 2ND ED VOL 1 1960 15 KUONG J F THERMAL PROPERTIES OF LIQUIDS 1963 16 " THE REACTOR HANDBOOK VOL 3 ENGINEERING 1963 17 " ENGLISH TRANSL OF HANDBUCH DER PHYSIC 1962 18 HOYT S L METAL DATA 1952 19 AVDUYEVSKIY V S FUNDLS OF HEAT TRANSFER IN AV AND RKT ENGR 1962 20 TOULOUKIAN Y S THERMOPHYSICAL PROP OF HIGH TEMP SOLID MATLS 1967 21 " PRELIM REPT ON THE PROP OF LI BE MG AL NBS62971959 22 " TH PROP OF SELD LIGHT ELEMENT CPDS NBS7437 1962 23 KOWALCZYK L S THERMAL COND AND ITS VARN WITH T AND P 1955 24 JOHNSON V J A COMPDM OF PROP OF MATL AT LOW TEMP NBS 1960 25 " JANAF THERMOCHEMICAL TABLES 26 KELLEY K K ENTROPIES OE ELEMENTS AND INORG CPDS BM592 1961 27 WEAST R C HANDBOOK OF CHEMISTRY AND PHYSICS 47TH ED 1966 28 JESTER M PRIVATE COLLECTION OF LIQUID METAL PROPERTIES 1968 29 WICKS C E THERMODYN PROP OF 65 ELEMENTS BU MINES 605 1963 30 PETERS R L MATERIALS DATA NOMOGRAPHS 1965 31 THOMPSON B ENERGY CONTENT VS TEMP FOR D-PU A-PU AND U 32 KELLEY K K ENTHALPY PLOTS DWG K38745 BU MINES 584 1960 33 KELLEY K K BU MINES 371 1939 34 LABER D BMI FINAL REPT ON SANL TASKS 309/032A 401/027 1967 35 " Y-12 DATA SHEETS 36 SCHAUER D WEAPONS MATL DATA BOOK 37 SCHORSCH R H ENGINEERING PROPERTIES OF SELECTED MATLS 1966 38 " MODERN PLASTICS ENCYCLOPEDIA 1968 39 " HANDBOOK OF MOLDED AND EXTR RUBBER GOODYEAR 40 " MACHINE DESIGN REFERENCE ISSUE PLASTICS 1964 41 " METALS HANDBOOK 8TH ED 1961 42 STULL D R THERMODYNAMIC PROPERTIES OF THE ELEMENTS ACS 1956 43 HAMPEL C A RARE METALS HANDBOOK 2ND ED 1961 44 MOYER J PRIVATE COLLECTION OF THERMAL DATA 1968 45 HODGE A W PROP OF HIGH TEMP TI ALLOYS DMIC MEMO 230 1968 46 CARSLAW H JAEGER J CONDUCTION OF HEAT IN SOLIDS 2ND ED OXFORD 1959 47 SMITHELLS C J METALS REFERENCE BOOK 4TH ED VOL 3 1967 48 LYNCH J F RUDERER ENGR PROP OF SEL CERAM MATLS BMI AM CER SOC 1966 49 " PROP OF KENNAMETAL HARD CARBIDE ALLOYS 1963 50 " PROP HANDBOOK CARBOLOY ETC GE MET PROD 1958 51 CLARK S P JR HANDBOOK OF PHYSICAL CONSTANTS GEOL SOC AMER 1966 52 STEPHENS D R MAIMO THE THERMAL COND OF ROCK SALT UCRL 6894-II 1964 53 SEDDON B J PHYS PROP OF PU CERAMIC CPDS TRG1601 1968 54 STORMS E K THE REFRACTORY CARBIDES 196Material: ALUMINUM; References: 20,1,32,34,27,37,42,14,47,51MID 1 101 101 101 104 105 106;; Material: ALUMINUM (LIQUID); References: 2,42,47,14,51MID 2 201 201 201 204 205 206;

603Appendix B: Mid Templates Supplied in Templatebin and TemplatetxtMaterials References, Classification, Quality Code and Index

; Material: ANTIMONY; References: 20,1,32,42,27MID 3 301 301 301 304 305 306;; Material: ANTIMONY (LIQUID); References: 1,47,42,27,20,14MID 4 401 401 401 404 405 406;; Material: ARSENIC, GREY; References: 1,27,41,42MID 5 501 501 501 504 505 506;; Material: BERYLLIUM; References: 20,6,1,32,34,27,36,42MID 6 601 601 601 604 605 606;; Material: BISMUTH; References: 2,1,27,43,41,42,47MID 7 701 701 701 704 705 706;; Material: BISMUTH (LIQUID); References: 1,14,27,43,47MID 8 801 801 801 804 805 806;; Material: CADMIUM; References: 2,1,32,42,43,27,41,47MID 9 901 901 901 904 905 906;; Material: CADMIUM (LIQUID); References: 2,1,32,42,43,27,41,47MID 10 1001 1001 1001 1004 1005 1006;; Material: COBALT; References: 20,27,1,32,43,30,41,42MID 11 1101 1101 1101 1104 1105 1106;; Material: COPPER; References: 20,1,27,32,34,37,42,47MID 12 1201 1201 1201 1204 1205 1206;; Material: GOLD; References: 20,6,1,32,27,42,41,2MID 13 1301 1301 1301 1304 1305 1306;; Material: GOLD (LIQUID); References: 14,20,27,42,43MID 14 1401 1401 1401 1404 1405 1406;; Material: CARBON, DIAMOND GEM QUALITY TYPE 1; References: 1,20,27MID 15 1501 1501 1501 1504 1505 0;; Material: CARBON, GRAPHITE (TYPICAL K); References: 1,2,20,27,32,42,51MID 16 1601 1601 1601 1604 1605 1606;; Material: CARBON, AMORPHOUS (CARBON STOCK); References: 27,1MID 17 1701 1701 1701 1704 1705 1706;; Material: IRON (-51 TO 1537 DEG C); References: 20,1,32,27,42,44,51MID 18 1801 1801 1801 1804 1805 0;; Material: IRON (-273 TO 763 DEG C); References: 20,1,32,27,42,44,51MID 19 1901 1901 1901 1904 1905 0


604

;; Material: IRON (0 TO 3000 DEG C); References: 20,1,32,27,42,44,51MID 20 2001 2001 2001 2004 2005 2006;; Material: LEAD; References: 2,1,32,27,37,42MID 21 2101 2101 2101 2104 2105 2106;; Material: LEAD (LIQUID); References: 1,2,14,27,37,42,43,47MID 22 2201 2201 2201 2204 2205 2206;; Material: MAGNESIUM; References: 20,1,32,27,42MID 23 2301 2301 2301 2304 2305 2306;; Material: MAGNESIUM (LIQUID); References: 1,14,20,27,32,43MID 24 2401 2401 2401 2404 2405 2406;; Material: MANGANESE; References: 20,1,32,27,43,42MID 25 2501 2501 2501 2504 2505 0;; Material: MOLYBDENUM; References: 20,6,1,32,41,43,42,47,14MID 26 2601 2601 2601 2604 2605 2606;; Material: NICKEL; References: 20,2,1,32,37,41,42,51MID 27 2701 2701 2701 2704 2705 2706;; Material: OSMIUM; References: 27,20,42,41MID 28 2801 2801 2801 2804 2805 2806;; Material: PLATINUM; References: 20,1,32,27,41,43,42MID 29 2901 2901 2901 2904 2905 2906;; Material: PLUTONIUM; References: 20,31,3,27,43,42,41,36,44MID 30 3001 3001 3001 3004 3005 3006;; Material: SILVER; References: 20,6,1,27,2,32,42,47,14,43MID 31 3101 3101 3101 3104 3105 3106;; Material: SILVER (LIQUID); References: 27,32,42,43MID 32 3201 3201 3201 3204 3205 3206;; Material: TANTALUM; References: 20,1,27,32,37,43MID 33 3301 3301 3301 3304 3305 3306;; Material: TECHNICIUM; References: 27,42MID 34 3401 3401 3401 3404 3405 3406;; Material: THORIUM; References: 20,32,34,27,37,43,44,41MID 35 3501 3501 3501 3504 3505 3506;; Material: TIN; References: 2,1,27,32,42,41,47MID 36 3601 3601 3601 3604 3605 3606


;; Material: TIN (LIQUID); References: 1,14,27,32,41,42,43MID 37 3701 3701 3701 3704 3705 3706;; Material: TITANIUM; References: 20,27,32,37,42,43,41,1MID 38 3801 3801 3801 3804 3805 3806;; Material: TUNGSTEN; References: 20,1,32,34,27,37,42,41,43MID 39 3901 3901 3901 3904 3905 3906;; Material: URANIUM; References: 20,31,32,36,27,37,42,41,43,44,34MID 40 4001 4001 4001 4004 4005 4006;; Material: ZINC; References: 2,1,32,27,42,20,41,47,51MID 41 4101 4101 4101 4104 4105 4106;; Material: ZINC (LIQUID); References: 14,20,27,32,43,47MID 42 4201 4201 4201 4204 4205 4206;; Material: ZIRCONIUM; References: 20,27,32,37,43,42,41MID 43 4301 4301 4301 4304 4305 4306;; Material: CHROMIUM; References: 20,1,27,32,43,42MID 44 4401 4401 4401 4404 4405 4406;; Material: MERCURY (LIQUID); References: 1,27,28,42,43,47,14MID 45 4501 4501 4501 4504 4505 4506;; Material: INDIUM; References: 1,27,43,30,42,41MID 46 4601 4601 4601 4604 4605 4606;; Material: INDIUM (LIQUID); References: 1,42,43,47MID 47 4701 4701 4701 4704 4705 4706;; Material: LITHIUM; References: 1,27,28,41,43,42,47MID 48 4801 4801 4801 4804 4805 4806;; Material: LITHIUM (LIQUID); References: 1,27,28,41,42,43,47MID 49 4901 4901 4901 4904 4905 4906;; Material: SODIUM; References: 2,1,27,28,41,42,43,51MID 50 5001 5001 5001 5004 5005 5006;; Material: SODIUM (LIQUID); References: 1,14,27,28,42,43,47,51MID 51 5101 5101 5101 5104 5105 5106;; Material: POTASSIUM; References: 1,27,28,42,41,43,51MID 52 5201 5201 5201 5204 5205 5206;; Material: POTASSIUM (LIQUID); References: 14,27,28,43,47,51MID 53 5301 5301 5301 5304 5305 5306


606

;; Material: CESIUM; References: 1,14,27,28,32,43,47MID 54 5401 5401 5401 5404 5405 5406;; Material: CESIUM (LIQUID); References: 14,27,28,32,43,47MID 55 5501 5501 5501 5504 5505 5506;; Material: PALLADIUM; References: 20,41,42,27,43MID 56 5601 5601 5601 5604 5605 5606;; Material: BARIUM; References: 20,27,29,42,43MID 57 5701 5701 5701 5704 5705 5706;; Material: NIOBIUM; References: 20,27,32,43,44,42MID 58 5801 5801 5801 5804 5805 5806;; Material: RHENIUM; References: 27,43,41,42MID 59 5901 5901 5901 5904 5905 5906;; Material: SILICON; References: 20,1,27,41,43,42,48MID 60 6001 6001 6001 6004 6005 6006;; Material: GERMANIUM (INTRINSIC, P-TYPE); References: 20,27,42,43,1,48MID 61 6101 6101 6101 6104 6105 6106;; Material: GERMANIUM (N-TYPE); References: 20,27,42,43,1,48MID 62 6201 6201 6201 6204 6205 6206;; Material: BORON; References: 20,27,30,42,43,48MID 63 6301 6301 6301 6304 6305 6306;; Material: HAFNIUM; References: 20,32,27,42,43,41MID 64 6401 6401 6401 6404 6405 6406;; Material: IRIDIUM; References: 27,41,20,42,43MID 65 6501 6501 6501 6504 6505 6506;; Material: RHODIUM; References: 20,27,43,42,41MID 66 6601 6601 6601 6604 6605 6606;; Material: VANADIUM; References: 20,32,27,41,42,43MID 67 6701 6701 6701 6704 6705 6706;; Material: RUBIDIUM; References: 1,27,28,42,43,47MID 68 6801 6801 6801 6804 6805 6806;; Material: RUBIDIUM (LIQUID); References: 1,14,27,28,43,47MID 69 6901 6901 6901 6904 6905 6906;; Material: STRONTIUM; References: 20,28,42,27MID 70 7001 7001 7001 7004 7005 7006


;; Material: RUTHENIUM; References: 20,42,1,27MID 71 7101 7101 7101 7104 7105 7106;; Material: CALCIUM; References: 27,1,42,43,41MID 72 7201 7201 7201 7204 7205 7206;; Material: GALLIUM; References: 27,42,43,1MID 73 7301 7301 7301 7304 7305 7306;; Material: GALLIUM (LIQUID); References: 1,14,27,43,47MID 74 7401 7401 7401 7404 7405 7406;; Material: IODINE (SOLID); References: 27,42,41,1MID 75 7501 7501 7501 7504 7505 7506;; Material: PHOSPHORUS (WHITE); References: 27MID 76 7601 7601 7601 7604 7605 7606;; Material: SELENIUM (GREY); References: 27,43,42,1MID 77 7701 7701 7701 7704 7705 7706;; Material: SULFUR; References: 27,1,42,30,2,41MID 78 7801 7801 7801 7804 7805 7806;; Material: THALLIUM; References: 41,27,1,42,47MID 79 7901 7901 7901 7904 7905 7906;; Material: THALLIUM (LIQUID); References: 1,14,27,42,43,47MID 80 8001 8001 8001 8004 8005 8006;; Material: SCANDIUM; References: 20,27,41,43MID 81 8101 8101 8101 8104 8105 8106;; Material: YTTRIUM; References: 41,27,1,20,42,43MID 82 8201 8201 8201 8204 8205 8206;; Material: LANTHANUM; References: 41,27,1,20,42MID 83 8301 8301 8301 8304 8305 0;; Material: CERIUM; References: 41,27,20,42MID 84 8401 8401 8401 8404 8405 8406;; Material: PRASEODYMIUM; References: 41,27,20,42MID 85 8501 8501 8501 8504 8505 8506;; Material: NEODYMIUM; References: 41,20,42MID 86 8601 8601 8601 8604 8605 8606;; Material: SAMARIUM; References: 20,27,41,42,43MID 87 8701 8701 8701 8704 8705 8706


608

;; Material: EUROPIUM; References: 20,27,41,43MID 88 8801 8801 8801 8804 8805 8806;; Material: GADOLINIUM; References: 41,27,20,42MID 89 8901 8901 8901 8904 8905 8906;; Material: TERBIUM; References: 20,27,41,42,43MID 90 9001 9001 9001 9004 9005 9006;; Material: DYSPROSIUM; References: 41,27,20,42MID 91 9101 9101 9101 9104 9105 9106;; Material: HOLMIUM; References: 20,27,41,42,43MID 92 9201 9201 9201 9204 9205 9206;; Material: ERBIUM; References: 41,27,20,42MID 93 9301 9301 9301 9304 9305 9306;; Material: THULIUM; References: 20,27,41,42,43MID 94 9401 9401 9401 9404 9405 9406;; Material: YTTERBIUM; References: 20,27,41,42,43MID 95 9501 9501 9501 9504 9505 9506;; Material: LUTETIUM; References: 20,27,41MID 96 9601 9601 9601 9604 9605 9606;; Material: PROMETHIUM; References: 20,27,42MID 97 9701 9701 9701 9704 9705 9706;; Material: ACTINIUM; References: 20,27,42MID 98 9801 9801 9801 9804 9805 9806;; Material: AMERICIUM; References: 20,27MID 99 9901 9901 9901 9904 9905 0;; Material: ASTITINE; References: 42MID 100 10001 10001 10001 10004 10005 10006;; Material: BERKELIUM; References: 27MID 101 10101 10101 10101 10104 10105 0;; Material: CALIFORNIUM; References: MID 102 10201 10201 10201 10204 10205 0;; Material: CURIUM; References: 20,27MID 103 10301 10301 10301 10304 10305 0;; Material: EINSTEINIUM; References: MID 104 10401 10401 10401 10404 10405 0


;; Material: FERMIUM; References: MID 105 10501 10501 10501 10504 10505 0;; Material: FRANCIUM; References: 42MID 106 10601 10601 10601 10604 10605 10606;; Material: MENDELEVIUM; References: MID 107 10701 10701 10701 10704 10705 0;; Material: NEPTUNIUM; References: 20,27MID 108 10801 10801 10801 10804 10805 0;; Material: NOBELIUM; References: MID 109 10901 10901 10901 10904 10905 0;; Material: POLONIUM; References: 20,27MID 110 11001 11001 11001 11004 11005 11006;; Material: PROTACTINIUM; References: 20,27MID 111 11101 11101 11101 11104 11105 11106;; Material: RADIUM; References: 27MID 112 11201 11201 11201 11204 11205 11206;; Material: TELLURIUM; References: 27,20,42,41,1MID 113 11301 11301 11301 11304 11305 11306;; Material: LAWRENCIUM; References: MID 114 11401 11401 11401 11404 11405 0;; Material: ARGON (GAS); References: 27,2,42,41MID 115 11501 11501 11501 11504 11505 0;; Material: CHLORINE (GAS); References: 27,1,42,2MID 116 11601 11601 11601 11604 11605 0;; Material: FLUORINE (GAS); References: 27,42MID 117 11701 11701 11701 11704 11705 0;; Material: HELIUM (GAS); References: 27,1,2,42MID 118 11801 11801 11801 11804 11805 0;; Material: HYDROGEN (GAS); References: 27,2,42,1MID 119 11901 11901 11901 11904 11905 0;; Material: NEON (GAS); References: 27,2,1,42MID 120 12001 12001 12001 12004 12005 0;; Material: NITROGEN (GAS); References: 27,2,42,1MID 121 12101 12101 12101 12104 12105 0


610

;; Material: OXYGEN (GAS); References: 27,42,1,2MID 122 12201 12201 12201 12204 12205 0;; Material: XENON; References: 27,42MID 123 12301 12301 12301 12304 12305 12306;; Material: BROMINE (GAS); References: 27,1,42MID 124 12401 12401 12401 12404 12405 0;; Material: DEUTERIUM; References: 27MID 125 12501 12501 12501 12504 12505 0;; Material: KRYPTON (GAS); References: 27,1,42MID 126 12601 12601 12601 12604 12605 12606;; Material: RADON GAS; References: 27MID 127 12701 12701 12701 12704 12705 0;; Material: TRITIUM GAS; References: MID 128 12801 12801 12801 12804 12805 0;; Material: ALUMINUM ALLOY 7075-T6 (AS RECEIVED); References: 20,41MID 129 12901 12901 12901 12904 12905 12906;; Material: ALUMINUM ALLOY 7075-T6 (ANNEALED); References: 20,41MID 130 13001 13001 13001 13004 13005 13006;; Material: ALUMINUM ALLOYS (AL, MG 2.5-5.0); References: 1,41MID 131 13101 13101 13101 13104 13105 13106;; Material: ALUMINUM ALLOY 7079; References: 37,41MID 132 13201 13201 13201 13204 13205 13206;; Material: ALUMINUM ALLOYS 2024-T4 AND 24S-24 (AR); References: 20,41MID 133 13301 13301 13301 13304 13305 13306;; Material: ALUMINUM ALLOY 2024-5-T4 (ANNEALED); References: 20,41MID 134 13401 13401 13401 13404 13405 13406;; Material: ALUMINUM ALLOY (AL99.0, AVERAGE TRTMT); References: 1,6,14,20,37,41,471,6,14,20,37,41,47MID 135 13501 13501 13501 13504 13505 13506;; Material: ALUMINUM ALLOY (AL96.0, WROT OR ANNLD); References: 1,6,14,20,37,41,47MID 136 13601 13601 13601 13604 13605 13606;; Material: ALUMINUM ALLOY (AL92.0, WROT OR ANNLD); References: 1,6,14,20,37,41,47MID 137 13701 13701 13701 13704 13705 13706;; Material: ALUMINUM ALLOY (AL84.0, WROT OR ANNLD); References: 1,6,14,20,37,41,47MID 138 13801 13801 13801 13804 13805 13806


;; Material: ALUMINUM ALLOY (AL84.0, AVERAGE TRTMT); References: 1,6,14,20,37,41,47MID 139 13901 13901 13901 13904 13905 13906;; Material: ALUMINUM ALLOY (AL90.0, CAST OR TEMPD); References: 1,6,14,20,37,41,47MID 140 14001 14001 14001 14004 14005 14006;; Material: ALUMINUM ALLOY (AL84.0, CAST OR TEMPD); References: 1,6,14,20,37,41,47MID 141 14101 14101 14101 14104 14105 14106;; Material: BRASS, ALUMINUM (CU76, ZN22, AL2); References: 1MID 142 14201 14201 14201 14204 14205 0;; Material: BRASS, CARTRIDGE (CU70, ZN30); References: 1,2,20,41,46MID 143 14301 14301 14301 14304 14305 0;; Material: BRASS, LEADED; References: 6,41MID 144 14401 14401 14401 14404 14405 0;; Material: BRASS, MUNTZ METAL; References: 1,41MID 145 14501 14501 14501 14504 14505 0;; Material: BRASS, RED, CAST (CU85, ZN5, PB5, SN3); References: 1,41MID 146 14601 14601 14601 14604 14605 0;; Material: BRASS, RED, WROUGHT (CU85, ZN15); References: 1,41MID 147 14701 14701 14701 14704 14705 0;; Material: BRASS, TIN (NAVAL AND ADMIRALTY); References: 1,2,41MID 148 14801 14801 14801 14804 14805 0;; Material: BRASS, YELLOW (CU65, ZN35); References: 1,6,41MID 149 14901 14901 14901 14904 14905 0;; Material: BRONZE (CU75, SN25); References: 1,2MID 150 15001 15001 15001 15004 15005 0;; Material: BRONZE, ALUMINUM (CU92, AL8); References: 1,6,41MID 151 15101 15101 15101 15104 15105 0;; Material: BRONZE, ARCHITECTURAL; References: 1,41MID 152 15201 15201 15201 15204 15205 0;; Material: BRONZE, COMMERCIAL; References: 1,2,38,41MID 153 15301 15301 15301 15304 15305 0;; Material: BRONZE, MANGANESE; References: 1,41MID 154 15401 15401 15401 15404 15405 0;; Material: BRONZE, PHOSPHER 10 PERCENT; References: 1,41MID 155 15501 15501 15501 15504 15505 0


612

;; Material: BRONZE, PHOSPHER 5 PERCENT; References: 6,41MID 156 15601 15601 15601 15604 15605 0;; Material: BRONZE, PHOSPHER 1.25 PERCENT; References: 6,41MID 157 15701 15701 15701 15704 15705 0;; Material: BRONZE, SILICON, HIGH; References: 1,6,41MID 158 15801 15801 15801 15804 15805 0;; Material: BRONZE, SILICON, LOW; References: 1,6,41MID 159 15901 15901 15901 15904 15905 0;; Material: BRONZE, TIN (CAST), HIGH LEADED; References: 6,41MID 160 16001 16001 16001 16004 16005 0;; Material: BRONZE, TIN (CAST), LEADED; References: 6MID 161 16101 16101 16101 16104 16105 0;; Material: BERYLLIUM COPPER (CU BAL, BE 0.38-0.55); References: 1MID 162 16201 16201 16201 16204 16205 16206;; Material: BERYLLIUM COPPER (CU BAL, BE1.7-1.9); References: 1,6,41MID 163 16301 16301 16301 16304 16305 16306;; Material: CHROMIUM COPPER (CU BAL, CR0.5); References: 6,20,47MID 164 16401 16401 16401 16404 16405 16406;; Material: COPPER ALLOY NICKEL SILVER (NI 10-20); References: 1,2,6,41,47MID 165 16501 16501 16501 16504 16505 16506;; Material: COPPER GILDING METAL (CU95, ZN5); References: 1,41MID 166 16601 16601 16601 16604 16605 0;; Material: COPPER, WROUGHT (ETP, DHP, TE0.5, PB1); References: 41MID 167 16701 16701 16701 16704 16705 16706;; Material: COPPER ALLOY MANGANIN; References: 2MID 168 16801 16801 16801 16804 16805 0;; Material: COPPER ALLOY (CU99.4, AL0.3, ZR0.27); References: 20MID 169 16901 16901 16901 16904 16905 16906;; Material: COPPER ALLOY (CU90, NI10); References: 1,6,41MID 170 17001 17001 17001 17004 17005 0;; Material: COPPER ALLOY (CU70, NI30); References: 1,6,41MID 171 17101 17101 17101 17104 17105 0;; Material: MAGNESIUM ALLOY AM100A (CASTING); References: 41MID 172 17201 17201 17201 17204 17205 17206


;; Material: MAGNESIUM ALLOY AZ31(X,S) (WROUGHT); References: 14,20,47MID 173 17301 17301 17301 17304 17305 17306;; Material: MAGNESIUM ALLOY AZ31B(P,S) (WROUGHT); References: 1,20,41MID 174 17401 17401 17401 17404 17405 17406;; Material: MAGNESIUM ALLOY AZ61A(X), AZM (WROUGHT); References: 14,41,47MID 175 17501 17501 17501 17504 17505 17506;; Material: MAGNESIUM ALLOY AZ63A(AC,F) (CASTING); References: 14,41MID 176 17601 17601 17601 17604 17605 17606;; Material: MAGNESIUM ALLOY AZ80A(X,FRGD) (WROUGHT); References: 1,20,37,41MID 177 17701 17701 17701 17704 17705 17706;; Material: MAGNESIUM ALLOY AZ81A(T4) (CASTING); References: 41MID 178 17801 17801 17801 17804 17805 17806;; Material: MAGNESIUM ALLOY AZ855(X) (WROUGHT); References: 47MID 179 17901 17901 17901 17904 17905 17906;; Material: MAGNESIUM ALLOY AZ91A,B (DC) (CASTING); References: 1,14,41,47MID 180 18001 18001 18001 18004 18005 18006;; Material: MAGNESIUM ALLOY AZ91C(AC) (CASTING); References: 1,41MID 181 18101 18101 18101 18104 18105 18106;; Material: MAGNESIUM ALLOY AZ92A(AC) (CASTING); References: 1,14,41MID 182 18201 18201 18201 18204 18205 18206;; Material: MAGNESIUM ALLOY A3A (WROUGHT); References: 41MID 183 18301 18301 18301 18304 18305 18306;; Material: MAGNESIUM ALLOY A8(AC OR ST) (CASTING); References: 47MID 184 18401 18401 18401 18404 18405 18406;; Material: MAGNESIUM ALLOY BZ33A(AC,AH) (CASTING); References: 1MID 185 18501 18501 18501 18504 18505 18506;; Material: MAGNESIUM ALLOY EK30A, H812 (CASTING); References: 20,41MID 186 18601 18601 18601 18604 18605 18606;; Material: MAGNESIUM ALLOY EK41A(T5,T6) (CASTING); References: 41MID 187 18701 18701 18701 18704 18705 18706;; Material: MAGNESIUM ALLOY EK33A, H811 (CASTING); References: 20,41MID 188 18801 18801 18801 18804 18805 18806;; Material: MAGNESIUM ALLOY HK31A(H24) (CASTING); References: 1,20,41MID 189 18901 18901 18901 18904 18905 18906


614

;; Material: MAGNESIUM ALLOY HK31A(O) (CASTING); References: 1,20,41MID 190 19001 19001 19001 19004 19005 19006;; Material: MAGNESIUM ALLOY HK31A(T6) (CASTING); References: 1,20,41MID 191 19101 19101 19101 19104 19105 19106;; Material: MAGNESIUM ALLOY HM21A(O,H24) (WROUGHT); References: 41MID 192 19201 19201 19201 19204 19205 19206;; Material: MAGNESIUM ALLOY HM31A (WROUGHT); References: 20,41MID 193 19301 19301 19301 19304 19305 19306;; Material: MAGNESIUM ALLOY HZ32A(AC),ZT1 (CASTING); References: 1,20,41,47MID 194 19401 19401 19401 19404 19405 19406;; Material: MAGNESIUM ALLOY MAGNOX A12(X) (WROUGHT); References: 47MID 195 19501 19501 19501 19504 19505 19506;; Material: MAGNESIUM ALLOY M1(AC) (CASTING); References: 14,47MID 196 19601 19601 19601 19604 19605 19606;; Material: MAGNESIUM ALLOY M1(X,S) (WROUGHT); References: 14,47MID 197 19701 19701 19701 19704 19705 19706;; Material: MAGNESIUM ALLOY M1A (WROUGHT); References: 41MID 198 19801 19801 19801 19804 19805 19806;; Material: MAGNESIUM ALLOY PE (WROUGHT); References: 41MID 199 19901 19901 19901 19904 19905 19906;; Material: MAGNESIUM ALLOY ZA(AC) (CASTING); References: 47MID 200 20001 20001 20001 20004 20005 20006;; Material: MAGNESIUM ALLOY ZE10A(O,H24) (WROUGHT); References: 41MID 201 20101 20101 20101 20104 20105 20106;; Material: MAGNESIUM ALLOY ZE41A(T5,HT) (CASTING); References: 20,41,47MID 202 20201 20201 20201 20204 20205 20206;; Material: MAGNESIUM ALLOY ZH42 (CASTING); References: 41MID 203 20301 20301 20301 20304 20305 20306;; Material: MAGNESIUM ALLOY ZH62A(AC),TZ6 (CASTING); References: 20,41,47MID 204 20401 20401 20401 20404 20405 20406;; Material: MAGNESIUM ALLOY ZK20A (WROUGHT); References: 20,41MID 205 20501 20501 20501 20504 20505 20506;; Material: MAGNESIUM ALLOY ZK51A, H807 (CASTING); References: 20,41,47MID 206 20601 20601 20601 20604 20605 20606


;; Material: MAGNESIUM ALLOY ZK60A,B, ZW6 (CASTING); References: 1,14,20,41,47MID 207 20701 20701 20701 20704 20705 20706;; Material: MAGNESIUM ALLOY ZRE0 (EZ30) (CASTING); References: 20MID 208 20801 20801 20801 20804 20805 20806;; Material: MAGNESIUM ALLOY ZRE1(AA) (CASTING); References: 47MID 209 20901 20901 20901 20904 20905 20906;; Material: MAGNESIUM ALLOY ZTY(X) (HK11) (WROUGHT); References: 20,47MID 210 21001 21001 21001 21004 21005 21006;; Material: MAGNESIUM ALLOY ZW1(X) (ZK11) (WROUGHT); References: 47MID 211 21101 21101 21101 21104 21105 21106;; Material: MAGNESIUM ALLOY ZW3(X) (ZK31) (WROUGHT); References: 47MID 212 21201 21201 21201 21204 21205 21206;; Material: MAGNESIUM ALLOY (MG,AG2.5,CE2,ZR0.6); References: 47MID 213 21301 21301 21301 21304 21305 21306;; Material: MAGNESIUM ALLOY 1959 (MG,CE4.33); References: 20MID 214 21401 21401 21401 21404 21405 21406;; Material: MAGNESIUM ALLOY 1960 (MG,CE6.7); References: 20MID 215 21501 21501 21501 21504 21505 21506;; Material: MAGNESIUM ALLOY 1961 (MG,CE11.85); References: 20MID 216 21601 21601 21601 21604 21605 21606;; Material: MAGNESIUM ALLOY 1964 (MG,CE5,CO2,MN0.8); References: 20MID 217 21701 21701 21701 21704 21705 21706;; Material: MAGNESIUM ALLOY 1992 (MG,CE4.45,CO3); References: 20MID 218 21801 21801 21801 21804 21805 21806;; Material: IRON ALLOY INVAR (FE64, NI36); References: 6,41,47MID 219 21901 21901 21901 21904 21905 21906;; Material: NICKEL ALLOY CALITE N; References: 14MID 220 22001 22001 22001 22004 22005 22006;; Material: NICKEL ALLOY A (NI99.4) (ANNEALED); References: 1,14,20MID 221 22101 22101 22101 22104 22105 22106;; Material: NICKEL ALLOY CHLORIMET 3; References: 14MID 222 22201 22201 22201 22204 22205 22206;; Material: COPPER ALLOY CONSTANTAN (CU55, NI45); References: 1,2,14,41,47MID 223 22301 22301 22301 22304 22305 22306


616

;; Material: NICKEL ALLOY CORROSIST; References: 14MID 224 22401 22401 22401 22404 22405 22406;; Material: NICKEL ALLOY DURANICKEL (AND -R) (SOFT); References: 1,14,47MID 225 22501 22501 22501 22504 22505 22506;; Material: NICKEL ALLOY DURANICKEL (AND -R) (HARD); References: 1,14,47MID 226 22601 22601 22601 22604 22605 22606;; Material: NICKEL ALLOY DURIMET 20 (CAST); References: 1MID 227 22701 22701 22701 22704 22705 22706;; Material: NICKEL ALLOY HASTELLOY A (ANNEALED); References: 1,14,20MID 228 22801 22801 22801 22804 22805 22806;; Material: NICKEL ALLOY HASTELLOY B; References: 1,14,20,41,47MID 229 22901 22901 22901 22904 22905 22906;; Material: NICKEL ALLOY HASTELLOY C; References: 1,14,41,47MID 230 23001 23001 23001 23004 23005 23006;; Material: NICKEL ALLOY HASTELLOY D; References: 1,14,41,47MID 231 23101 23101 23101 23104 23105 23106;; Material: NICKEL ALLOY HASTELLOY N AND INOR-8; References: 20,41MID 232 23201 23201 23201 23204 23205 23206;; Material: NICKEL ALLOY HASTELLOY R-235; References: 1,14,20MID 233 23301 23301 23301 23304 23305 23306;; Material: NICKEL ALLOY HASTELLOY X; References: 1,14,20,41MID 234 23401 23401 23401 23404 23405 23406;; Material: NICKEL ALLOY HY MU 80; References: 14MID 235 23501 23501 23501 23504 23505 23506;; Material: NICKEL ALLOY ILLIUM G; References: 1,14,20,41,47MID 236 23601 23601 23601 23604 23605 23606;; Material: NICKEL ALLOY ILLIUM R; References: 1,14,41,47MID 237 23701 23701 23701 23704 23705 23706;; Material: NICKEL ALLOY INCOLOY; References: 1,14MID 238 23801 23801 23801 23804 23805 23806;; Material: NICKEL ALLOY INCOLOY 901; References: 1,20MID 239 23901 23901 23901 23904 23905 23906;; Material: NICKEL ALLOY INCONEL (CAST); References: 1,14,20,41,47MID 240 24001 24001 24001 24004 24005 24006


;; Material: NICKEL ALLOY INCONEL (CAST); References: 1,14,20,41,47MID 241 24101 24101 24101 24104 24105 24106;; Material: NICKEL ALLOY INCONEL W; References: 1MID 242 24201 24201 24201 24204 24205 24206;; Material: NICKEL ALLOY INCONEL 702 (ANNEALED); References: 1,20MID 243 24301 24301 24301 24304 24305 24306;; Material: NICKEL ALLOY INCONEL X AND X-750; References: 1,20,41MID 244 24401 24401 24401 24404 24405 24406;; Material: NICKEL ALLOY INCONEL 600 (ANNEALED); References: 1,47MID 245 24501 24501 24501 24504 24505 24506;; Material: NICKEL ALLOY INCONEL 700; References: 1,14,20,41MID 246 24601 24601 24601 24604 24605 24606;; Material: NICKEL ALLOY INCONEL 713C (CAST); References: 1,20MID 247 24701 24701 24701 24704 24705 24706;; Material: NICKEL ALLOY MONEL (HOT-ROLLED); References: 1,14,41,44,47MID 248 24801 24801 24801 24804 24805 24806;; Material: NICKEL ALLOY MONEL (COLD-DRAWN); References: 1,14,20,41MID 249 24901 24901 24901 24904 24905 24906;; Material: NICKEL ALLOY MONEL 403 (HOT-ROLLED); References: 1MID 250 25001 25001 25001 25004 25005 25006;; Material: NICKEL ALLOY MONEL (CAST); References: 1,41MID 251 25101 25101 25101 25104 25105 25106;; Material: NICKEL ALLOY MONEL, H (AS CAST); References: 1,41MID 252 25201 25201 25201 25204 25205 25206;; Material: NICKEL ALLOY MONEL WELDABLE ALLOY; References: 1MID 253 25301 25301 25301 25304 25305 25306;; Material: NICKEL ALLOY MONEL, K (ANNEALED); References: 1,14,20,41,44MID 254 25401 25401 25401 25404 25405 25406;; Material: NICKEL ALLOY MONEL, H (CAST, VAR COMP); References: 1,20,41MID 255 25501 25501 25501 25504 25505 25506;; Material: NICKEL ALLOY MONEL, KR (ANNEALED); References: 1,14MID 256 25601 25601 25601 25604 25605 25606;; Material: NICKEL ALLOY MONEL 400; References: 47MID 257 25701 25701 25701 25704 25705 0


618

;; Material: NICKEL ALLOY MONEL, R (HOT-ROLLED); References: 1,20,41MID 258 25801 25801 25801 25804 25805 25806;; Material: NICKEL ALLOY MONEL, S (CAST, ALL COND); References: 1,14,20MID 259 25901 25901 25901 25904 25905 25906;; Material: NICKEL ALLOY M-252 (GE J-1500); References: 20MID 260 26001 26001 26001 26004 26005 26006;; Material: NICKEL ALLOY NICHROME V (NI80, CR 20); References: 1,47MID 261 26101 26101 26101 26104 26105 26106;; Material: NICKEL ALLOY NIMONIC DS; References: 47MID 262 26201 26201 26201 26204 26205 26206;; Material: NICKEL ALLOY NIMONIC 75; References: 1,14,20MID 263 26301 26301 26301 26304 26305 26306;; Material: NICKEL ALLOY NIMONIC 80; References: 1,14,20,41,47MID 264 26401 26401 26401 26404 26405 26406;; Material: NICKEL ALLOY NIMONIC 80A; References: 1,20,41,47MID 265 26501 26501 26501 26504 26505 26506;; Material: NICKEL ALLOY NIMONIC 90; References: 1,14,20,41MID 266 26601 26601 26601 26604 26605 26606;; Material: NICKEL ALLOY NIMONIC 95; References: 20,47MID 267 26701 26701 26701 26704 26705 26706;; Material: NICKEL ALLOY PERMANICKEL; References: 1,14MID 268 26801 26801 26801 26804 26805 26806;; Material: NICKEL ALLOY NIMONIC 105; References: 47MID 269 26901 26901 26901 26904 26905 26906;; Material: NICKEL ALLOY RENE 41; References: 20,41MID 270 27001 27001 27001 27004 27005 27006;; Material: NICKEL ALLOY NIMONIC 100; References: 20MID 271 27101 27101 27101 27104 27105 27106;; Material: NICKEL ALLOY UDIMET 500 (WROUGHT); References: 1,20,41MID 272 27201 27201 27201 27204 27205 27206;; Material: NICKEL ALLOY WASPALLOY; References: 1,20,41MID 273 27301 27301 27301 27304 27305 27306;; Material: NICKEL ALLOY 330 (NI99.55) (ANNEALED); References: 1MID 274 27401 27401 27401 27404 27405 27406


;; Material: NICKEL ALLOY (NI62,CR12,FE26); References: 2,41MID 275 27501 27501 27501 27504 27505 0;; Material: NICKEL ALLOY (NI60,CR16,FE24); References: 41MID 276 27601 27601 27601 27604 27605 0;; Material: NICKEL ALLOY (NI35,CR20,FE45); References: 41MID 277 27701 27701 27701 27704 27705 0;; Material: NICKEL ALLOY (NI99.5) LOW C, 220, 225; References: 1,14MID 278 27801 27801 27801 27804 27805 27806;; Material: NICKEL ALLOY D AND E; References: 1MID 279 27901 27901 27901 27904 27905 27906;; Material: COBALT ALLOY HE-1049; References: 20MID 280 28001 28001 28001 28004 28005 28006;; Material: COBALT ALLOY HS-21 (AS CAST); References: 1,14,20,41MID 281 28101 28101 28101 28104 28105 28106;; Material: COBALT ALLOY HS-21 (AGED); References: 1,14,20,41MID 282 28201 28201 28201 28204 28205 28206;; Material: COBALT ALLOY HS-23; References: 14,20MID 283 28301 28301 28301 28304 28305 28306;; Material: COBALT ALLOY HS-25 (L-605) (WROUGHT); References: 1,14,41MID 284 28401 28401 28401 28404 28405 28406;; Material: COBALT ALLOY HS-27 (AS CAST); References: 14,20MID 285 28501 28501 28501 28504 28505 28506;; Material: COBALT ALLOY HS-30 (422-19) (AS CAST); References: 14,20MID 286 28601 28601 28601 28604 28605 28606;; Material: COBALT ALLOY HS-31 (X-40) (AS CAST); References: 1,14,20,41MID 287 28701 28701 28701 28704 28705 28706;; Material: COBALT ALLOY HS-36 (CAST); References: 1,14,20MID 288 28801 28801 28801 28804 28805 28806;; Material: COBALT ALLOY JESSOP G-32; References: 20MID 289 28901 28901 28901 28904 28905 28906;; Material: COBALT ALLOY J-1570; References: 20MID 290 29001 29001 29001 29004 29005 29006;; Material: COBALT ALLOY K-42B; References: 14MID 291 29101 29101 29101 29104 29105 29106


620

;; Material: COBALT ALLOY MULTIMET (N-155) (WROUGHT); References: 1,14,20,41MID 292 29201 29201 29201 29204 29205 29206;; Material: COBALT ALLOY MULTIMET (N-155) (LOW C); References: 1,14,20,41MID 293 29301 29301 29301 29304 29305 29306;; Material: COBALT ALLOY S-590 (WROUGHT); References: 14,41MID 294 29401 29401 29401 29404 29405 29406;; Material: COBALT ALLOY S-816 (WROUGHT); References: 1,14,20,41MID 295 29501 29501 29501 29504 29505 29506;; Material: COBALT ALLOY V-36 (WROUGHT); References: 41MID 296 29601 29601 29601 29604 29605 29606;; Material: COBALT ALLOY WI-52; References: 20MID 297 29701 29701 29701 29704 29705 29706;; Material: COBALT ALLOY WI-52 (CR COATED SAMPLE); References: 20MID 298 29801 29801 29801 29804 29805 29806;; Material: COBALT ALLOY (CO64,CR30,W6); References: 20MID 299 29901 29901 29901 29904 29905 29906;; Material: TITANIUM ALLOY (TI BAL, AL2, MN2); References: 20MID 300 30001 30001 30001 30004 30005 30006;; Material: TITANIUM ALLOY (TI BAL, AL4, V2, MO1); References: 20MID 301 30101 30101 30101 30104 30105 30106;; Material: TITANIUM ALLOY (TI BAL, AL4, CU2, ZR2); References: 20MID 302 30201 30201 30201 30204 30205 30206;; Material: TITANIUM ALLOY (TI BAL, AL4, V3, MO1.5); References: 20MID 303 30301 30301 30301 30304 30305 30306;; Material: TITANIUM ALLOY (TI BAL, AL4, V1, MO0.6); References: 20MID 304 30401 30401 30401 30404 30405 30406;; Material: TITANIUM ALLOY HYLITE 40 C130AM,RC130B; References: 1,20,41MID 305 30501 30501 30501 30504 30505 30506;; Material: TITANIUM ALLOY HYLITE 50 (IMI550); References: 20,45MID 306 30601 30601 30601 30604 30605 30606;; Material: TITANIUM ALLOY HYLITE 51 (IMI551); References: 45MID 307 30701 30701 30701 30704 30705 30706;; Material: TITANIUM ALLOY (TI BAL, AL4, ZR3.5); References: 20MID 308 30801 30801 30801 30804 30805 30806


;; Material: TITANIUM ALLOY (TI BAL, AL4, CU4, SN2); References: 20MID 309 30901 30901 30901 30904 30905 30906;; Material: TITANIUM ALLOY (TI BAL, AL4, MO3, V1); References: 20MID 310 31001 31001 31001 31004 31005 31006;; Material: TITANIUM ALLOY TI155A (AL5,FE2,CR1,MO1); References: 1,20MID 311 31101 31101 31101 31104 31105 31106;; Material: TITANIUM ALLOY (TI BAL, AL5, SN2.5); References: 41,45MID 312 31201 31201 31201 31204 31205 31206;; Material: TITANIUM ALLOY (TI BAL, AL5, SN5, ZR5); References: 45MID 313 31301 31301 31301 31304 31305 31306;; Material: TITANIUM ALLOY (TI BAL, AL6, V4); References: 20,37,45MID 314 31401 31401 31401 31404 31405 31406;; Material: TITANIUM ALLOY (TI BAL, AL8, MO1, V1); References: 45MID 315 31501 31501 31501 31504 31505 31506;; Material: TITANIUM ALLOY TI150A (CR2.7, FE1.4); References: 20MID 316 31601 31601 31601 31604 31605 31606;; Material: TITANIUM ALLOY (TI BAL, CR3.4, MO2.1); References: 20MID 317 31701 31701 31701 31704 31705 31706;; Material: TITANIUM ALLOY TI140A (FE2, CR2, MO2); References: 20MID 318 31801 31801 31801 31804 31805 31806;; Material: TITANIUM ALLOY C100M (RC130A) (MN7.9); References: 20MID 319 31901 31901 31901 31904 31905 31906;; Material: TITANIUM ALLOY (TI BAL, SN4.8, AL4.5); References: 20MID 320 32001 32001 32001 32004 32005 32006;; Material: TITANIUM ALLOY (TI BAL, SN5.5, AL2); References: 20MID 321 32101 32101 32101 32104 32105 32106;; Material: TITANIUM ALLOY HYLITE 65 (IMI); References: 45MID 322 32201 32201 32201 32204 32205 32206;; Material: TITANIUM ALLOY HYLITE 60 (IMI); References: 20,45MID 323 32301 32301 32301 32304 32305 32306;; Material: TITANIUM ALLOY HYLITE 55 (IMI); References: 20,45MID 324 32401 32401 32401 32404 32405 32406;; Material: TITANIUM ALLOY IMI 680 (SN11, MO4, AL2); References: 45MID 325 32501 32501 32501 32504 32505 32506


622

;; Material: TITANIUM ALLOY IMI 679 (SN11, ZR5, AL2); References: 45MID 326 32601 32601 32601 32604 32605 32606;; Material: TITANIUM ALLOY (TI BAL, V15, AL2.8); References: 20MID 327 32701 32701 32701 32704 32705 32706;; Material: TITANIUM ALLOY (TI BAL, V14, CR10, AL4); References: 20MID 328 32801 32801 32801 32804 32805 32806;; Material: TITANIUM ALLOY (TI BAL, ZR3, AL2); References: 20MID 329 32901 32901 32901 32904 32905 32906;; Material: IRON, GREY CAST, FERRITIC (2.3-3.0 C); References: 1,2,6,20,27,33,46MID 330 33001 33001 33001 33004 33005 33006;; Material: IRON, GREY CAST, FERRITIC (3.2-3.8 C); References: 1,2,6,20,27,33,46MID 331 33101 33101 33101 33104 33105 33106;; Material: IRON, GREY CAST, PEARLITIC (2.3-3.0 C); References: 1,2,6,20,27,33,46MID 332 33201 33201 33201 33204 33205 33206;; Material: IRON, GREY CAST, PEARLITIC (3.0-3.2 C); References: 1,2,6,20,27,33,46MID 333 33301 33301 33301 33304 33305 33306;; Material: IRON, GREY CAST, PEARLITIC (3.4 C); References: 1,2,6,20,27,33,46MID 334 33401 33401 33401 33404 33405 33406;; Material: IRON, GREY CAST, PEARLITIC (3.7-3.8 C); References: 1,2,6,20,27,33,46MID 335 33501 33501 33501 33504 33505 33506;; Material: IRON, GREY CAST, PEARLITIC (4.12 C); References: 1,2,6,20,27,33,46MID 336 33601 33601 33601 33604 33605 33606;; Material: IRON, DUCTILE (0.06 MG); References: 1,6MID 337 33701 33701 33701 33704 33705 33706;; Material: IRON, DUCTILE (MG CONTAINING); References: 1MID 338 33801 33801 33801 33804 33805 33806;; Material: IRON, DUCTILE (MG CONTAINING, HEAT RES); References: 1MID 339 33901 33901 33901 33904 33905 33906;; Material: IRON, NODULAR CAST, FERRITIC BASE; References: 1,2,20MID 340 34001 34001 34001 34004 34005 34006;; Material: IRON, NODULAR CAST, PEARLITIC BASE; References: 1,2,20MID 341 34101 34101 34101 34104 34105 34106;; Material: IRON, NI-HARD TYPES 1 AND 2 (KOVAR); References: 1,20MID 342 34201 34201 34201 34204 34205 34206


;; Material: IRON, NI-RESIST, TYPES 1 AND 2 (CAST); References: 1,20MID 343 34301 34301 34301 34304 34305 34306;; Material: IRON, NI-RESIST, TYPE 3 (CAST); References: 1MID 344 34401 34401 34401 34404 34405 34406;; Material: IRON, NI-RESIST, TYPE 4 (CAST); References: 1MID 345 34501 34501 34501 34504 34505 34506;; Material: IRON, NI-RESIST, TYPE D2 (CAST); References: 1MID 346 34601 34601 34601 34604 34605 34606;; Material: IRON, MALLEABLE (2.5 C); References: 1,6MID 347 34701 34701 34701 34704 34705 0;; Material: IRON, WROUGHT (VARIOUS); References: 1,2,6,27MID 348 34801 34801 34801 34804 34805 34806;; Material: IRON, NI-TENSYLIRON (CAST, HEAT TREAT); References: 1MID 349 34901 34901 34901 34904 34905 34906;; Material: STEEL, ALLOY AND MILD (4130, 4340); References: 6,41,46MID 350 35001 35001 35001 35004 35005 35006;; Material: STEEL, ALLOY, CAST; References: 6MID 351 35101 35101 35101 35104 35105 35106;; Material: STEEL, FREE CUTTING, EUTECTOID; References: 2,4,6,20,41MID 352 35201 35201 35201 35204 35205 35206;; Material: STEEL, CARBON, TYPE 1020 (0.2 - 0.6 C); References: 1,20,37MID 353 35301 35301 35301 35304 35305 35306;; Material: STEEL, HIGH SPEED (M1, M10, M-2, TI); References: 20MID 354 35401 35401 35401 35404 35405 35406;; Material: STEEL, STAINLESS 201 AND 202; References: 1MID 355 35501 35501 35501 35504 35505 35506;; Material: STEEL, STAINLESS (CR 16-26, NI 8-36); References: 1,2,4,6,20,37MID 356 35601 35601 35601 35604 35605 35606;; Material: STEEL, STAINLESS 304; References: 1,4,37MID 357 35701 35701 35701 35704 35705 35706;; Material: STEEL, STAINLESS 321 AND 347; References: 1,2,4,20,37,14MID 358 35801 35801 35801 35804 35805 35806;; Material: STEEL, STAINLESS (CR 12-13, NI 0-3); References: 1,2,4,14,20MID 359 35901 35901 35901 35904 35905 35906


624

;; Material: STEEL, STAINLESS 430, 430F, AND 431; References: 1,2,4,6,20,14MID 360 36001 36001 36001 36004 36005 36006;; Material: STEEL, STAINLESS 446; References: 1,14,20MID 361 36101 36101 36101 36104 36105 36106;; Material: STEEL, STAINLESS 501 AND 502; References: 2,4MID 362 36201 36201 36201 36204 36205 36206;; Material: STEEL, STAINLESS 17-4PH; References: 20,14MID 363 36301 36301 36301 36304 36305 36306;; Material: STEEL, STAINLESS 17-7PH; References: 20,14MID 364 36401 36401 36401 36404 36405 36406;; Material: STEEL, ULTRA HIGH STRENGTH TYPE 300-M; References: 1MID 365 36501 36501 36501 36504 36505 36506;; Material: STEEL, STAINLESS 19-9DL; References: 41MID 366 36601 36601 36601 36604 36605 0;; Material: STEEL, STAINLESS HW (CAST); References: 1MID 367 36701 36701 36701 36704 36705 36706;; Material: STEEL, STAINLESS HU (CAST); References: 1MID 368 36801 36801 36801 36804 36805 36806;; Material: STEEL, STAINLESS HT (CAST); References: 1MID 369 36901 36901 36901 36904 36905 36906;; Material: STEEL, STAINLESS CN-7M (CAST); References: 1MID 370 37001 37001 37001 37004 37005 37006;; Material: STEEL, STAINLESS HF (CAST); References: 1MID 371 37101 37101 37101 37104 37105 37106;; Material: STEEL, STAINLESS HA (CAST); References: 1MID 372 37201 37201 37201 37204 37205 37206;; Material: STEEL, STAINLESS HC, HD (CAST); References: 1MID 373 37301 37301 37301 37304 37305 37306;; Material: STEEL, STAINLESS CA15, CA40 (CAST); References: 1MID 374 37401 37401 37401 37404 37405 37406;; Material: STEEL, STAINLESS CB30, CC50 (CAST); References: 1MID 375 37501 37501 37501 37504 37505 37506;; Material: STEEL, STAINLESS HH, HL, HK (CAST); References: 1MID 376 37601 37601 37601 37604 37605 37606


;; Material: STEEL, STAINLESS HE (CAST); References: 1MID 377 37701 37701 37701 37704 37705 37706;; Material: STEEL, STAINLESS CF (CAST); References: 1MID 378 37801 37801 37801 37804 37805 37806;; Material: STEEL, STAINLESS CK, CH, HI (CAST); References: 1MID 379 37901 37901 37901 37904 37905 37906;; Material: CHROME-NICKEL-IRON SUPERALLOYS; References: 6MID 380 38001 38001 38001 38004 38005 0;; Material: BERYLLIUM ALLOY (BE96.5) (AS RECEIVED); References: 20MID 381 38101 38101 38101 38104 38105 38106;; Material: BERYLLIUM ALLOY (BE96.5) (ANNEALED); References: 20MID 382 38201 38201 38201 38204 38205 38206;; Material: BERYLLIUM ALLOY (BE98.5) (AS RECEIVED); References: 20MID 383 38301 38301 38301 38304 38305 38306;; Material: BERYLLIUM ALLOY (BE98.5) (ANNEALED); References: 20MID 384 38401 38401 38401 38404 38405 38406;; Material: BERYLLIUM ALLOY (BE99.5); References: 20MID 385 38501 38501 38501 38504 38505 38506;; Material: LEAD, ANTIMONIAL (PB, SB 4-6) (HARD); References: 1,6,41MID 386 38601 38601 38601 38604 38605 38606;; Material: LEAD, ANTIMONIAL (PB, SB 8-9); References: 1,6,41MID 387 38701 38701 38701 38704 38705 38706;; Material: INDIUM ALLOY (IN25, SN37.5, PB37.5); References: 36MID 388 38801 38801 38801 38804 38805 38806;; Material: LEAD ALLOY (PB39.2, SN60.8) (SOLDER); References: 34,41MID 389 38901 38901 38901 38904 38905 38906;; Material: LEAD ALLOY (PB50, SN50) (SOLDER); References: 1,41MID 390 39001 39001 39001 39004 39005 39006;; Material: LEAD ALLOY (PB60, SN40) (SOLDER); References: 1,41MID 391 39101 39101 39101 39104 39105 39106;; Material: MOLYBDENUM ALLOY (MO99.5, TI0.5); References: 1,6,41MID 392 39201 39201 39201 39204 39205 39206;; Material: MOLYBDENUM ALLOY (MO BAL, FE 0.25); References: 20MID 393 39301 39301 39301 39304 39305 39306


626

;; Material: MOLYBDENUM ALLOY (MO70, W30); References: 20MID 394 39401 39401 39401 39404 39405 39406;; Material: COLOMBIUM ALLOY (CB61,TA28,W10,ZR0.5); References: 20MID 395 39501 39501 39501 39504 39505 39506;; Material: COLOMBIUM ALLOY (CB85, TI10, ZR5); References: 20MID 396 39601 39601 39601 39604 39605 39606;; Material: COLOMBIUM ALLOY (CB95, TA5); References: 20MID 397 39701 39701 39701 39704 39705 39706;; Material: COLOMBIUM ALLOY (CB80, W15, MO5); References: 20MID 398 39801 39801 39801 39804 39805 39806;; Material: PLUTONIUM ALLOY (DELTA PHASE); References: 20,27,31,44MID 399 39901 39901 39901 39904 39905 39906;; Material: SILVER ALLOYS, STERLING AND COIN; References: 1MID 400 40001 40001 40001 40004 40005 40006;; Material: TANTALUM ALLOY (TA90, W10); References: 20,36MID 401 40101 40101 40101 40104 40105 40106;; Material: TANTALUM ALLOY (TA99.5, NB0.5); References: 20MID 402 40201 40201 40201 40204 40205 40206;; Material: TANTALUM ALLOY (TA98, CU0.7, ZR0.7); References: 20MID 403 40301 40301 40301 40304 40305 40306;; Material: TANTALUM ALLOY (TA62, NB30, V7.5); References: 20MID 404 40401 40401 40401 40404 40405 40406;; Material: TANTALUM ALLOY (TA89, W9, HF2); References: 20MID 405 40501 40501 40501 40504 40505 40506;; Material: TUNGSTEN ALLOY (W75, RE25); References: MID 406 40601 40601 40601 40604 40605 40606;; Material: TUNGSTEN ALLOY (W90, NI6, CU2-4); References: 20MID 407 40701 40701 40701 40704 40705 40706;; Material: MULBERRY (U90, NB7.5, ZR2.5); References: 34,36,37MID 408 40801 40801 40801 40804 40805 40806;; Material: URANIUM ALLOY (U90, MO10); References: 20,35,36MID 409 40901 40901 40901 40904 40905 40906;; Material: URANIUM ALLOY (U82, ZR18); References: 20,34MID 410 41001 41001 41001 41004 41005 41006


;; Material: URANIUM ALLOY (U96, NB4); References: 20,34MID 411 41101 41101 41101 41104 41105 41106;; Material: URANIUM ALLOY (U94.4, CR5.6) (EUTECTIC); References: 20MID 412 41201 41201 41201 41204 41205 41206;; Material: URANIUM ALLOY (U97, FS3); References: 20MID 413 41301 41301 41301 41304 41305 41306;; Material: URANIUM ALLOY (U90, FS10); References: 20MID 414 41401 41401 41401 41404 41405 41406;; Material: URANIUM ALLOY (U93, FS5, ZR2); References: 20MID 415 41501 41501 41501 41504 41505 41506;; Material: URANIUM ALLOY (U98.5, ZR1.5); References: 20MID 416 41601 41601 41601 41604 41605 41606;; Material: URANIUM ALLOY (U95, ZR5); References: 20 3MID 417 41701 41701 41701 41704 41705 41706;; Material: ZILLOY 15; References: 1,6,41MID 418 41801 41801 41801 41804 41805 41806;; Material: ZINC ALLOY ASTM B69; References: 1,6,41,51MID 419 41901 41901 41901 41904 41905 41906;; Material: ZINC-ALUMINUM ALLOY ASTM 23; References: 1,6,41MID 420 42001 42001 42001 42004 42005 42006;; Material: ZINC-ALUMINUM-COPPER ALLOY ASTM 25; References: 1,6,41MID 421 42101 42101 42101 42104 42105 42106;; Material: ZIRCONIUM ALLOYS ZIRCALLOY 2 AND 3; References: 1,6,14MID 422 42201 42201 42201 42204 42205 42206;; Material: ZIRCONIUM ALLOY 3ZI (ZR97,AL1,SN1,MO1); References: 20MID 423 42301 42301 42301 42304 42305 42306;; Material: DANDELION 35; References: 34,36MID 424 42401 42401 42401 42404 42405 0;; Material: ALUMINUM OXIDE (AL2O3) (POLYXTAL 100 D); References: 1,20,27,32,47,48,51MID 425 42501 42501 42501 42504 42505 42506;; Material: ALUMINUM OXIDE (AL2O3) (POLYXTAL, 55 D); References: 1,20,27,32,47,48,51MID 426 42601 42601 42601 42604 42605 42606;; Material: ALUMINUM OXIDE (AL2O3) (SINGLE XTAL); References: 1,20,27,32,47,48,51MID 427 42701 42701 42701 42704 42705 42706


628

;; Material: ALUMINUM OXIDE (AL2O3) (FOAM, D = 0.5); References: 1,20,27,32,47,48,51MID 428 42801 42801 42801 42804 42805 42806;; Material: ALUMINUM OXIDE (AL2O3) (FOAM, D = 1.9); References: 1,20,27,32,47,48,51MID 429 42901 42901 42901 42904 42905 42906;; Material: BERYLLIUM OXIDE (BEO) (96 PC DENS); References: 14,20,27,36,43,44,47,48,51MID 430 43001 43001 43001 43004 43005 43006;; Material: BERYLLIUM OXIDE (BEO) (76 PC DENS); References: 14,20,27,36,43,44,47,48,51MID 431 43101 43101 43101 43104 43105 43106;; Material: CALCIUM OXIDE (CAO) (PRESSED, 91 DENS); References: 1,20,27,47,48,51MID 432 43201 43201 43201 43204 43205 43206;; Material: CARBON DIOXIDE; References: 1,2,27MID 433 43301 43301 43301 43304 43305 43306;; Material: CALCIUM OXIDE (CAO) (PACKED PWD, 50 D); References: 1,20,27,47,48MID 434 43401 43401 43401 43404 43405 43406;; Material: CARBON MONOXIDE; References: 1,27MID 435 43501 43501 43501 43504 43505 43506;; Material: CERIUM OXIDE (CEO2) (PRSD, SNTRD, 86 D); References: 1,20,47MID 436 43601 43601 43601 43604 43605 43606;; Material: COBALT OXIDE (COO); References: 20,27,47,48MID 437 43701 43701 43701 43704 43705 43706;; Material: COPPER OXIDE (CUO) (TENORITE); References: 1,20,27,47,51MID 438 43801 43801 43801 43804 43805 43806;; Material: GADOLINIUM OXIDE (GD2O3) (MONOC) (98 D); References: 20,47,48MID 439 43901 43901 43901 43904 43905 0;; Material: HAFNIUM OXIDE (HFO2) (MONOC) (94 D); References: 20,27,48MID 440 44001 44001 44001 44004 44005 44006;; Material: HEMATITE (FE2O3); References: 1,27,32,47,48,51MID 441 44101 44101 44101 44104 44105 0;; Material: IRON OXIDE (FEO.FE2O3) (MAGNATITE); References: 20,27,47,51MID 442 44201 44201 44201 44204 44205 44206;; Material: LEAD OXIDE (PBO) (YELLOW); References: 1,20,27,32,47MID 443 44301 44301 44301 44304 44305 44306;; Material: MAGNESIUM OXIDE (MGO) (SINGLE CRYSTAL); References: 1,20,27,47,48MID 444 44401 44401 44401 44404 44405 44406


;; Material: MAGNESIUM OXIDE (MGO) (POLYXTAL, 100 D); References: 1,20,27,47,48,51MID 445 44501 44501 44501 44504 44505 44506;; Material: MANGANESE OXIDE (MNO) (SINGLE XTAL); References: 1,27,48MID 446 44601 44601 44601 44604 44605 44606;; Material: MANGANESE OXIDE (MN3O4) (87 PC DENSE); References: 20,27,48,51MID 447 44701 44701 44701 44704 44705 44706;; Material: NICKEL OXIDE (NIO) (SINGLE XTAL); References: 20,27,32,47,48,51MID 448 44801 44801 44801 44804 44805 44806;; Material: NICKEL OXIDE (NIO) (POLYXTAL, 88-100 D); References: 20,27,32,47,48,51MID 449 44901 44901 44901 44904 44905 44906;; Material: NICKEL OXIDE (NIO) (POLYXTAL, 68-74 D); References: 20,27,32,47,48,51MID 450 45001 45001 45001 45004 45005 45006;; Material: NITRIC OXIDE (NO) (GAS); References: 1,27MID 451 45101 45101 45101 45104 45105 0;; Material: FUSED SILICA GLASS; References: 1,20,27,47,511,20,27,47,51MID 452 45201 45201 45201 45204 45205 45206;; Material: QUARTZ CRYSTAL, C AXIS (SIO2); References: 1,2,20,27,37,47,51MID 453 45301 45301 45301 45304 45305 45306;; Material: QUARTZ CRYSTAL, A AXIS (SIO2); References: 1,2,20,27,37,47,51MID 454 45401 45401 45401 45404 45405 45406;; Material: SILICON OXIDE (SIO2) (FOAM, 1 ATM AIR); References: 1,20,27,47MID 455 45501 45501 45501 45504 45505 45506;; Material: SULFUR DIOXIDE (SO2) (GAS); References: 1MID 456 45601 45601 45601 45604 45605 0;; Material: THORIUM OXIDE (THO2) (96-100 PC DENSE); References: 1,20,27,47,48,51MID 457 45701 45701 45701 45704 45705 45706;; Material: TIN OXIDE (SNO2) (93-95 PC DENSE); References: 1,20,27,47,48MID 458 45801 45801 45801 45804 45805 45806;; Material: TITANIUM OXIDE (TIO2) (RUTILE, C AXIS); References: 1,20,27,32,47,48,51MID 459 45901 45901 45901 45904 45905 45906;; Material: TITANIUM OXIDE (TIO2) (RUTILE, A AXIS); References: 1,20,27,32,47,48,51MID 460 46001 46001 46001 46004 46005 46006;; Material: TITANIUM OXIDE (TIO2) (RUTILE, 100 D); References: 1,20,27,32,47,48,51MID 461 46101 46101 46101 46104 46105 46106


630

;; Material: TUNGSTEN OXIDE (WO3) (POLYXTAL. POROUS); References: 20,27,47,48MID 462 46201 46201 46201 46204 46205 46206;; Material: URANIUM OXIDE (UO2) (SINGLE CRYSTAL); References: 20,27,47,48,51MID 463 46301 46301 46301 46304 46305 0;; Material: URANIUM OXIDE (UO2) (POLYXTAL, 97 DENS); References: 20,27,47,48,51MID 464 46401 46401 46401 46404 46405 0;; Material: URANIUM OXIDE (U3O8) (PRSD AT 4200 PSI); References: 1,20,27,47,48MID 465 46501 46501 46501 46504 46505 0;; Material: URANIUM OXIDE (U3O8) (PRSD AT 100 PSI); References: 1,20,27,47,48MID 466 46601 46601 46601 46604 46605 0;; Material: YTTRIUM OXIDE (Y2O3) (96-100 PC DENSE); References: 20,27,47,48MID 467 46701 46701 46701 46704 46705 46706;; Material: ZINC OXIDE (ZNO) (PRSD, FIRED, 100 D); References: 1,20,27,47,48,51MID 468 46801 46801 46801 46804 46805 46806;; Material: ZIRCONIUM OXIDE (ZRO2) (MONOC., 100 D); References: 1,20,27,47,48,51MID 469 46901 46901 46901 46904 46905 46906;; Material: ZIRCONIUM OXIDE (ZRO2 96, CAO 6, 91 D); References: 1,20,27,47,48,51MID 470 47001 47001 47001 47004 47005 47006;; Material: STEAM (H2O) (GAS) (1 ATM); References: 1,2,14,27,46MID 471 47101 47101 47101 47104 47105 47106;; Material: STEAM (H2O) (GAS) (SATD); References: 1,2,14,27,46MID 472 47201 47201 47201 47204 47205 0;; Material: WATER (H2O) (LIQUID); References: 2,14,27,46MID 473 47301 47301 47301 47304 47305 47306;; Material: ICE (H2O) (SOLID); References: 27,46,51MID 474 47401 47401 47401 47404 47405 47406;; Material: DEUTERIUM OXIDE (D2O) (LIQUID); References: 14,27MID 475 47501 47501 47501 47504 47505 47506;; Material: BARIUM TITANATE (BAO.TIO2) (100 D); References: 20,27,48MID 476 47601 47601 47601 47604 47605 0;; Material: BARIUM TITANATE (BAO.TIO2) (SINTERED); References: 20,27,48MID 477 47701 47701 47701 47704 47705 0;; Material: BARIUM TITANATE (BAO.TIO2) (+MN,NB OX); References: 20,27,48MID 478 47801 47801 47801 47804 47805 0


;; Material: CALCIUM TITANATE (CAO.TIO2); References: 20,27,48,51MID 479 47901 47901 47901 47904 47905 0;; Material: COBALT NICKEL OXIDE (46COO.46NIO.8LIO); References: 20,27MID 480 48001 48001 48001 48004 48005 0;; Material: COPPER LITHIUM OXIDE (96CUO.4LIO); References: 20,27MID 481 48101 48101 48101 48104 48105 0;; Material: LITHIUM NICKEL OXIDE (5LIO.95NIO); References: 20,27MID 482 48201 48201 48201 48204 48205 0;; Material: MAGNESIUM ALUMINATE (MGO.AL2O3) (XTAL); References: 20,27,47,48,51MID 483 48301 48301 48301 48304 48305 0;; Material: MAGNESIUM ALUMINATE (MGO.AL2O3) (100 D); References: 20,27,47,48,51MID 484 48401 48401 48401 48404 48405 0;; Material: NICKEL ZINC FERRITE (NI(ZN)O.FE2O3); References: 20MID 485 48501 48501 48501 48504 48505 0;; Material: POTASSIUM CHROMATE (K2O.2CRO3) (S AXIS); References: 1,27MID 486 48601 48601 48601 48604 48605 48606;; Material: POTASSIUM CHROMATE (K2O.2CRO3) (M AXIS); References: 1,27MID 487 48701 48701 48701 48704 48705 48706;; Material: STRONTIUM TITANATE (SRO.TIO2) (100 D); References: 20,48MID 488 48801 48801 48801 48804 48805 0;; Material: STRONTIUM TITANATE (SRO.TIO2) (80 D); References: 20,48MID 489 48901 48901 48901 48904 48905 0;; Material: PLUTONIUM URANIUM OXIDE (PUO2.4UO2) SEE; References: 53MID 490 49001 49001 49001 49004 49005 0;; Material: ZINC FERRITE (ZNO.FE2O3) (PR, FRD, VAC); References: 20,27MID 491 49101 49101 49101 49104 49105 0;; Material: ALUMINUM FLUOSILICATE (TOPAZ) (A-AXIS); References: 27,51MID 492 49201 49201 49201 49204 49205 0;; Material: ALUMINUM FLUOSILICATE (TOPAZ) (C-AXIS); References: 27,51MID 493 49301 49301 49301 49304 49305 0;; Material: ALUMINUM SILICATE (AL2O3.SIO2) (ORTHO); References: 20,27,47,51MID 494 49401 49401 49401 49404 49405 0;; Material: ALUMINUM SILICATE (AL2O3.SIO2) (TRICL); References: 20,27,47,51MID 495 49501 49501 49501 49504 49505 0


632

;; Material: ALUMINUM SILICATE (3AL2O3.2SIO2) (100D); References: 20,27,47,48,51MID 496 49601 49601 49601 49604 49605 0;; Material: BERYL (3BEO.AL2O3.6SIO2); References: 20,27,51MID 497 49701 49701 49701 49704 49705 0;; Material: BETA-SPODUMENE (LI2O.AL2O3.4SIO2) (TET); References: 20,27,51MID 498 49801 49801 49801 49804 49805 0;; Material: CORDIERITE (2MGO.2AL2O3.5SIO2); References: 20,51MID 499 49901 49901 49901 49904 49905 0;; Material: FORSTERITE (2MGO.SIO2) (100 PC DENSE); References: 1,20,27,51MID 500 50001 50001 50001 50004 50005 50006;; Material: MAGNESIUM SILICATE (MGO.SIO2) (COMMERC); References: 1,20,27,51MID 501 50101 50101 50101 50104 50105 0;; Material: ORTHOCLASE (K2O.AL2O3.6SIO2) (CRYSTAL); References: 27,51MID 502 50201 50201 50201 50204 50205 0;; Material: ANALCITE (NA2O.AL2O3.4SIO2.4H2O) (XTAL); References: 27,51MID 503 50301 50301 50301 50304 50305 0;; Material: ZIRCON (ZRO2.SIO2) (SINGLE CRYSTAL); References: 20,27,48,61MID 504 50401 50401 50401 50404 50405 0;; Material: ZIRCONIUM SILICATE (ZRO2.SIO2) (100 D); References: 20,27,48,61MID 505 50501 50501 50501 50504 50505 0;; Material: ALUMINUM NITRIDE (ALN) (PRS AXIS, 98 D); References: 20,27,47,48MID 506 50601 50601 50601 50604 50605 0;; Material: BERYLLIUM NITRIDE (BE3N2) (PRSD 3.4 KB); References: 20,47MID 507 50701 50701 50701 50704 50705 50706;; Material: BORON NITRIDE (BN) (PERP PR AXIS, 95 D); References: 20,27,36,47,48MID 508 50801 50801 50801 50804 50805 0;; Material: BORON NITRIDE (BN) (PRS AXIS, 94 D); References: 20,27,36,47,48MID 509 50901 50901 50901 50904 50905 0;; Material: BORON NITRIDE (BN 97, BN2O3 2) (PERP P); References: 20MID 510 51001 51001 51001 51004 51005 0;; Material: BORON NITRIDE (BN 97, BN2O3 2) (PRS AX); References: 20MID 511 51101 51101 51101 51104 51105 0;; Material: BORON NITRIDE (BN 80, C 20) (PRS AXIS); References: 20MID 512 51201 51201 51201 51204 51205 0


;; Material: CHROMIUM NITRIDE (CRN) (PRSD, 100 PC D); References: 27,47,48MID 513 51301 51301 51301 51304 51305 0;; Material: CHROMIUM NITRIDE (CR2N) (PRSD, 100 D); References: 27,47,48MID 514 51401 51401 51401 51404 51405 0;; Material: HAFNIUM NITRIDE (HFN) (HP STRD 78-92 D); References: 20,27,48MID 515 51501 51501 51501 51504 51505 0;; Material: MOLYBDENUM NITRIDE (MO2N) (PR SRD 100D); References: 47,48MID 516 51601 51601 51601 51604 51605 0;; Material: NIOBIUM NITRIDE (NBN); References: 20,47,48MID 517 51701 51701 51701 51704 51705 0;; Material: NIOBIUM NITRIDE (NB2N); References: 20,47,48MID 518 51801 51801 51801 51804 51805 0;; Material: PLUTONIUM NITRIDE (PUN); References: 27,48,53MID 519 51901 51901 51901 51904 51905 0;; Material: SILICON NITRIDE (SI3N4) (85 PC DENSE); References: 20,27,47,48MID 520 52001 52001 52001 52004 52005 0;; Material: SILICON NITRIDE (SI3N4) (70 PC DENSE); References: 20,27,47,48MID 521 52101 52101 52101 52104 52105 0;; Material: TANTALUM NITRIDE (TAN); References: 20,27,48MID 522 52201 52201 52201 52204 52205 0;; Material: TANTALUM NITRIDE (TA2N); References: 20,27,48MID 523 52301 52301 52301 52304 52305 0;; Material: TITANIUM NITRIDE (TIN) (HP, 70-90 DENS); References: 20,27,47,48MID 524 52401 52401 52401 52404 52405 0;; Material: URANIUM NITRIDE (UN) (HP, 95-98 DENSE); References: 20,27,48,PWAC481-65MID 525 52501 52501 52501 52504 52505 0;; Material: VANADIUM NITRIDE (VN) (PR, STRD, 100 D); References: 20,27,47,48MID 526 52601 52601 52601 52604 52605 0;; Material: ZIRCONIUM NITRIDE (ZRN) (PR SR 88-90 D); References: 20,27,47,48MID 527 52701 52701 52701 52704 52705 0;; Material: ZIRCONIUM NITRIDE (ZRN) (PR SR 93 D); References: 20,27,47,48MID 528 52801 52801 52801 52804 52805 0;; Material: BERYLLIUM CARBIDE (BE2C) (HP OR SNT); References: 14,20,28,47MID 529 52901 52901 52901 52904 52905 52906


634

;; Material: BORON CARBIDE (B4C) (DENSE); References: 20,27,48MID 530 53001 53001 53001 53004 53005 0;; Material: BORON CARBIDE (B4C) (POROUS); References: 20,27,48MID 531 53101 53101 53101 53104 53105 0;; Material: HAFNIUM CARBIDE (HFC); References: 20,27,48,54MID 532 53201 53201 53201 53204 53205 0;; Material: MOLYBDENUM CARBIDE (MO2C); References: 20,27,48MID 533 53301 53301 53301 53304 53305 0;; Material: NIOBIUM CARBIDE (NBC); References: 20,27,48,54MID 534 53401 53401 53401 53404 53405 0;; Material: PLUTONIUM CARBIDE (PUC) (ARCM OR CAST); References: 20,48,53,54MID 535 53501 53501 53501 53504 53505 0;; Material: SILICON CARBIDE (SIC) (SINGLE XTAL); References: 20,27,32,47MID 536 53601 53601 53601 53604 53605 0;; Material: SILICON CARBIDE (SIC) (SINGLE XTAL); References: 20,32,47,48MID 537 53701 53701 53701 53704 53705 0;; Material: SILICON CARBIDE (SIC) (SLF BND, HE ATM); References: 20,27,32,47MID 538 53801 53801 53801 53804 53805 0;; Material: SILICON CARBIDE (SIC) (KT GRADE); References: 20,27,32,47,48MID 539 53901 53901 53901 53904 53905 0;; Material: SILICON CARBIDE (SIC) (CARBOFRAX BRICK); References: 20,27,32,47MID 540 54001 54001 54001 54004 54005 0;; Material: SILICON CARBIDE (SIC) (FRIT BND BRICK); References: 20,27,32,47MID 541 54101 54101 54101 54104 54105 0;; Material: SILICON CARBIDE (SIC) (REXTAL, 80-100D); References: 20,27,32,47,48MID 542 54201 54201 54201 54204 54205 0;; Material: SILICON CARBIDE (SIC) (REXTAL, 65-70D); References: 1,20,27,32,47MID 543 54301 54301 54301 54304 54305 0;; Material: SILICON CARBIDE (SIC) (BRICK AL2O3 1.7); References: 20,27,32,47MID 544 54401 54401 54401 54404 54405 0;; Material: SILICON CARBIDE (SIC) (REFRACTORY D-30); References: 20,27,32,47MID 545 54501 54501 54501 54504 54505 0;; Material: SILICON CARBIDE (SIC) (NITRIDE BONDED); References: 20,32,47,48MID 546 54601 54601 54601 54604 54605 0


;; Material: SILICON CARBIDE (SIC) (FOAM, IN VACUUM); References: 20,32,47MID 547 54701 54701 54701 54704 54705 0;; Material: SILICON CARBIDE (SIC) (POWDER, IN AIR); References: 20,32,47MID 548 54801 54801 54801 54804 54805 0;; Material: SILICON CARBIDE (SIC) (POWDER, IN HE); References: 20,32,47MID 549 54901 54901 54901 54904 54905 0;; Material: TANTALUM CARBIDE (TAC); References: 20,27,48,54MID 550 55001 55001 55001 55004 55005 0;; Material: THORIUM CARBIDE (THC) (80 PC DENSE); References: 20,27,48,54MID 551 55101 55101 55101 55104 55105 0;; Material: THORIUM CARBIDE (THC2) (69 PC DENSE); References: 20,27,48,54MID 552 55201 55201 55201 55204 55205 0;; Material: TITANIUM CARBIDE (TIC) (96 PC DENSE); References: 20,27,47,48,54MID 553 55301 55301 55301 55304 55305 0;; Material: TITANIUM CARBIDE (TIC) (93 PC DENSE); References: 20,27,47,48,54MID 554 55401 55401 55401 55404 55405 0;; Material: TUNGSTEN CARBIDE (WC); References: 20,27,47,48,54MID 555 55501 55501 55501 55504 55505 0;; Material: URANIUM CARBIDE (UC) (ARCM OR CAST,99D); References: 20,48,53,54MID 556 55601 55601 55601 55604 55605 0;; Material: URANIUM CARBIDE (UC) (SINTERED, 90D); References: 20,48,53,54MID 557 55701 55701 55701 55704 55705 0;; Material: URANIUM CARBIDE (UC) (AVG, VAR. TYPES); References: 20,48,53,54MID 558 55801 55801 55801 55804 55805 0;; Material: URANIUM CARBIDE (UC2); References: 20,27,48,54MID 559 55901 55901 55901 55904 55905 0;; Material: VANADIUM CARBIDE (VC); References: 20,27,47,48,54MID 560 56001 56001 56001 56004 56005 0;; Material: ZIRCONIUM CARBIDE (ZRC) (HP OR SNT,94D); References: 20,27,48,54MID 561 56101 56101 56101 56104 56105 0;; Material: BARIUM BORIDE (BAB6); References: 27,48MID 562 56201 56201 56201 56204 56205 0;; Material: BORON SILICIDE (B4SI); References: 27,48MID 563 56301 56301 56301 56304 56305 0


636

;; Material: CALCIUM BORIDE (CAB6); References: 27,48MID 564 56401 56401 56401 56404 56405 0;; Material: HAFNIUM BORIDE (HFB2); References: 20,27,48MID 565 56501 56501 56501 56504 56505 0;; Material: NIOBIUM BORIDE (NBB2) (PRESSED, SNTRD); References: 20,27,48MID 566 56601 56601 56601 56604 56605 0;; Material: YTTRIUM BORIDE (YB6) (98.4 PC DENSE); References: 48MID 567 56701 56701 56701 56704 56705 0;; Material: LANTHANUM BORIDE (LAB6) (99.5 PC DENSE); References: 48MID 568 56801 56801 56801 56804 56805 0;; Material: CERIUM BORIDE (CEB6) (99.0 PC DENSE); References: 48MID 569 56901 56901 56901 56904 56905 0;; Material: PRASEODYMIUM BORIDE (PRB6) (95 PC DENS); References: 48MID 570 57001 57001 57001 57004 57005 0;; Material: NEODYMIUM BORIDE (NDB6) (97.3 PC DENSE); References: 48MID 571 57101 57101 57101 57104 57105 0;; Material: SAMARIUM BORIDE (SMB6) (96.8 PC DENSE); References: 48MID 572 57201 57201 57201 57204 57205 0;; Material: EUROPIUM BORIDE (EUB6) (93.0 PC DENSE); References: 48MID 573 57301 57301 57301 57304 57305 0;; Material: GADOLINIUM BORIDE (GDB6) (95.6 PC DENS); References: 48MID 574 57401 57401 57401 57404 57405 0;; Material: TERBIUM BORIDE (TBB6) (94.3 PC DENSE); References: 48MID 575 57501 57501 57501 57504 57505 0;; Material: YTTERBIUM BORIDE (YBB6) (90.6 PC DENS); References: 48MID 576 57601 57601 57601 57604 57605 0;; Material: TANTALUM BORIDE (TAB) (PSD, SNTR, 85D); References: 20,27,47,48MID 577 57701 57701 57701 57704 57705 0;; Material: TANTALUM BORIDE (TAB2); References: 20,27,47,48MID 578 57801 57801 57801 57804 57805 0;; Material: THORIUM BORIDE (THB4); References: 20,27,48MID 579 57901 57901 57901 57904 57905 0;; Material: THORIUM BORIDE (THB6); References: 20,27,48MID 580 58001 58001 58001 58004 58005 0


;; Material: TITANIUM BORIDE (TIB2) (HP, 95 PC DENS); References: 20,27,47,48MID 581 58101 58101 58101 58104 58105 0;; Material: TUNGSTEN BORIDE (WB); References: 20,27,47,48MID 582 58201 58201 58201 58204 58205 0;; Material: URANIUM BORIDE (UB4); References: 20,48MID 583 58301 58301 58301 58304 58305 0;; Material: VANADIUM BORIDE (VB2); References: 20,27,48MID 584 58401 58401 58401 58404 58405 0;; Material: ZIRCONIUM BORIDE (ZRB2) (HP, 97 PC DEN); References: 20,27,47,48MID 585 58501 58501 58501 58504 58505 0;; Material: MOLYBDENUM BERYLLIDE (MOBE12); References: 20,48MID 586 58601 58601 58601 58604 58605 0;; Material: NIOBIUM BERYLLIDE (NBBE12) (HP, 93-97D); References: 20,48MID 587 58701 58701 58701 58704 58705 0;; Material: NIOBIUM BERYLLIDE (NB2BE17); References: 20,48MID 588 58801 58801 58801 58804 58805 0;; Material: TANTALUM BERYLLIDE (TABE12) (HP); References: 20,48MID 589 58901 58901 58901 58904 58905 58906;; Material: TANTALUM BERYLLIDE (TA2BE17); References: 20,48MID 590 59001 59001 59001 59004 59005 0;; Material: TITANIUM BERYLLIDE (TIBE12) (HP, 95D); References: 20,48MID 591 59101 59101 59101 59104 59105 0;; Material: URANIUM BERYLLIDE (UBE13) (SNTRD, 61D); References: 20,48MID 592 59201 59201 59201 59204 59205 0;; Material: VANADIUM BERYLLIDE (VBE12) (85 PC DENS); References: 20,48MID 593 59301 59301 59301 59304 59305 0;; Material: ZIRCONIUM BERYLLIDE (ZRBE13); References: 20,48MID 594 59401 59401 59401 59404 59405 0;; Material: CERIUM SULFIDE (CES); References: 20,48MID 595 59501 59501 59501 59504 59505 0;; Material: CERIUM SULFIDE (CE2S3); References: 20,48MID 596 59601 59601 59601 59604 59605 0;; Material: IRON SULFIDE (FES2) (SINGLE CRYSTAL); References: 27,47,51MID 597 59701 59701 59701 59704 59705 0


638

;; Material: PLUTONIUM SULFIDE; References: 53MID 598 59801 59801 59801 59804 59805 0;; Material: SAMARIUM SULFIDE (SMS); References: 20,48MID 599 59901 59901 59901 59904 59905 0;; Material: ZINC SULFIDE (ZNS) (CUBIC CRYSTAL); References: 1,27,47,48,51MID 600 60001 60001 60001 60004 60005 60006;; Material: PLUTONIUM PHOSPHIDE (PUP) (90 PC DENSE); References: 53MID 601 60101 60101 60101 60104 60105 0;; Material: CHROMIUM SILICIDE (CRSI2); References: 20,27,48MID 602 60201 60201 60201 60204 60205 0;; Material: COBALT SILICIDE (COS); References: 20,48MID 603 60301 60301 60301 60304 60305 0;; Material: MAGNESIUM SILICIDE (MG2SI); References: 20,27,48MID 604 60401 60401 60401 60404 60405 0;; Material: MANGANESE SILICIDE (MNSI2); References: 20,27,48MID 605 60501 60501 60501 60504 60505 0;; Material: MOLYBDENUM SILICIDE (MOSI2); References: 20,27,48MID 606 60601 60601 60601 60604 60605 0;; Material: NIOBIUM SILICIDE (NBSI2); References: 20,27MID 607 60701 60701 60701 60704 60705 0;; Material: TANTALUM SILICIDE (TASI2); References: 20,27MID 608 60801 60801 60801 60804 60805 0;; Material: TUNGSTEN SILICIDE (WSI2) (HP, 95 DENSE); References: 20,27,48MID 609 60901 60901 60901 60904 60905 0;; Material: URANIUM SILICIDE (U3SI); References: 20,48MID 610 61001 61001 61001 61004 61005 0;; Material: AMMONIUM BROMIDE (NH4BR) (PRSD 8 KB); References: 27,47MID 611 61101 61101 61101 61104 61105 0;; Material: AMMONIUM CHLORIDE (NH4CL) (PRSD 8 KB); References: 27,47MID 612 61201 61201 61201 61204 61205 0;; Material: BARIUM FLUORIDE (BAF2) (SINGLE CRYSTAL); References: 20,27,51MID 613 61301 61301 61301 61304 61305 61306;; Material: CALCIUM FLUORIDE (CAF2) (SINGLE XTAL); References: 1,20,27,47,51MID 614 61401 61401 61401 61404 61405 61406


;; Material: CALCIUM FLUORIDE (CAF2) (MINERAL AGGR); References: 1,20,27,47,51MID 615 61501 61501 61501 61504 61505 61506;; Material: LITHIUM FLUORIDE (LIF) (SINGLE CRYSTAL); References: 1,20,27,47,51MID 616 61601 61601 61601 61604 61605 61606;; Material: LITHIUM FLUORIDE (LIF 96) (PLASTIC BND); References: 1,20,27,47,51MID 617 61701 61701 61701 61704 61705 61706;; Material: MERCURY CHLORIDE (HGCL2) (PRSD 8 KB); References: 1,27,47MID 618 61801 61801 61801 61804 61805 61806;; Material: POTASSIUM BROMIDE (KBR) (PRSD 8 KB); References: 1,27,47MID 619 61901 61901 61901 61904 61905 61906;; Material: POTASSIUM BROMIDE (KBR) (SINGLE XTAL); References: 1,27,47,51MID 620 62001 62001 62001 62004 62005 62006;; Material: POTASSIUM BROMIDE (KBR 90, KCL 10); References: 1,27,47,51MID 621 62101 62101 62101 62104 62105 62106;; Material: POTASSIUM BROMIDE (KBR 75, KCL 25); References: 1,27,47,51MID 622 62201 62201 62201 62204 62205 62206;; Material: POTASSIUM BROMIDE (KBR 50, KCL 50); References: 1,27,47,51MID 623 62301 62301 62301 62304 62305 62306;; Material: POTASSIUM CHLORIDE (KCL 75, KBR 25); References: 1,27,47,51MID 624 62401 62401 62401 62404 62405 62406;; Material: POTASSIUM CHLORIDE (KCL 90, KBR 10); References: 1,27,47,51MID 625 62501 62501 62501 62504 62505 62506;; Material: POTASSIUM CHLORIDE (KCL) (PRSD 8 KB); References: 1,27,47,51MID 626 62601 62601 62601 62604 62605 62606;; Material: POTASSIUM CHLORIDE (KCL) (SYLVITE XTAL); References: 1,27,47,51MID 627 62701 62701 62701 62704 62705 62706;; Material: POTASSIUM CHLORIDE (KCL 50, NACL 50); References: 1,27,47,51MID 628 62801 62801 62801 62804 62805 62806;; Material: POTASSIUM FLUORIDE (KF) (PRSD 8 KB); References: 1,27,47MID 629 62901 62901 62901 62904 62905 62906;; Material: POTASSIUM IODIDE (KI) (PRSD 8 KB); References: 1,27,47MID 630 63001 63001 63001 63004 63005 63006;; Material: RUBIDIUM CHLORIDE (RBCL) (PRSD 8 KB); References: 1,27,47MID 631 63101 63101 63101 63104 63105 63106


640

;; Material: RUBIDIUM IODIDE (RBI) (PRSD 8 KB); References: 1,27,47MID 632 63201 63201 63201 63204 63205 63206;; Material: SILVER CHLORIDE (AGCL) (SINGLE CRYSTAL); References: 27,47,51MID 633 63301 63301 63301 63304 63305 63306;; Material: SODIUM BROMIDE (NABR) (PRSD 8 KB); References: 1,27,47MID 634 63401 63401 63401 63404 63405 63406;; Material: SODIUM CHLORIDE (NACL) (CLEAR CRYSTAL); References: 1,27,47,51,52MID 635 63501 63501 63501 63504 63505 63506;; Material: SODIUM CHLORIDE (NACL) (OPAQUE, IMPURE); References: 1,27,47,51,52MID 636 63601 63601 63601 63604 63605 63606;; Material: SODIUM FLUORIDE (NAF) (PRSD 8 KB); References: 1,27,47MID 637 63701 63701 63701 63704 63705 63706;; Material: AMMONIA (NH3) (LIQUID UNDER PRESSURE); References: 1,27,47MID 638 63801 63801 63801 63804 63805 0;; Material: AMMONIA (NH3) (GAS); References: 1,27,47MID 639 63901 63901 63901 63904 63905 63906;; Material: LITHIUM HYDRIDE (LIH) (CAST, VAC VOIDS); References: 2020MID 640 64001 64001 64001 64004 64005 64006;; Material: LITHIUM HYDRIDE (LIH) (CAST, GAS VOIDS); References: 20MID 641 64101 64101 64101 64104 64105 64106;; Material: METHANE (CH4) (GAS); References: 1,27MID 642 64201 64201 64201 64204 64205 64206;; Material: ZIRCONIUM HYDRIDE (ZRH + ZRH2); References: 20MID 643 64301 64301 64301 64304 64305 0;; Material: ANTIMONY TELLURIDE (SB2TE3) (POLYXTAL); References: 20,27MID 644 64401 64401 64401 64404 64405 0;; Material: ANTIMONY TELLURIDE (SB2TE3) (CPR, N DR); References: 20,27MID 645 64501 64501 64501 64504 64505 0;; Material: ARSENIC TELLURIDE (AS2TE3) (V ZONE MLT); References: 20MID 646 64601 64601 64601 64604 64605 0;; Material: BISMUTH TELLURIDE (BI2TE3-P) (PLANE DR); References: 20,47MID 647 64701 64701 64701 64704 64705 0;; Material: BISMUTH TELLURIDE SULFIDE (BI2TE2S); References: 20MID 648 64801 64801 64801 64804 64805 0


;; Material: INDIUM ANTIMONIDE (INSB) (IMP 0.16); References: 20,27MID 649 64901 64901 64901 64904 64905 64906;; Material: INDIUM ANTIMONIDE (INSB) (IMP 0.33-1.2); References: 20,27MID 650 65001 65001 65001 65004 65005 65006;; Material: INDIUM ARSENIDE (INAS) (POLYX, IMP 3.0); References: 20,27MID 651 65101 65101 65101 65104 65105 0;; Material: INDIUM ARSENIDE (INAS) (PURE, S-DOPED); References: 20,27MID 652 65201 65201 65201 65204 65205 0;; Material: INDIUM TELLURIDE (IN2TE3); References: 20,27MID 653 65301 65301 65301 65304 65305 0;; Material: LEAD TELLURIDE (PBTE) (SINGLE CRYSTAL); References: 20,27MID 654 65401 65401 65401 65404 65405 0;; Material: LEAD TELLURIDE (PBTE) (POLYXTAL); References: 20,27MID 655 65501 65501 65501 65504 65505 0;; Material: LITHIUM MANGANESE SELENIDE (97MN.3LI.-); References: 20,27MID 656 65601 65601 65601 65604 65605 0;; Material: MANGANESE TELLURIDE (95MNTE.5MNAS); References: 20MID 657 65701 65701 65701 65704 65705 0;; Material: MANGANESE TELLURIDE (99MNTE.NATE); References: 20MID 658 65801 65801 65801 65804 65805 0;; Material: MOLYBDENUM SELENIDE (MOSE2); References: 20MID 659 65901 65901 65901 65904 65905 0;; Material: MOLYBDENUM TELLURIDE (MOTE2); References: 20MID 660 66001 66001 66001 66004 66005 0;; Material: SILICON TELLURIDE (SITE); References: 20MID 661 66101 66101 66101 66104 66105 0;; Material: TIN TELLURIDE (SNTE 80, AGSBTE2 20); References: 20MID 662 66201 66201 66201 66204 66205 0;; Material: TIN TELLURIDE (SNTE 60, AGSBTE2 40); References: 20MID 663 66301 66301 66301 66304 66305 0;; Material: SILVER ANTIMONY TELLURIDE (SNTE 25 PC); References: 20MID 664 66401 66401 66401 66404 66405 0;; Material: SILVER SELENIDE (AG2SE); References: 20,27,47MID 665 66501 66501 66501 66504 66505 0


642

;; Material: TANTALUM ANTIMONIDE (TASB); References: 20MID 666 66601 66601 66601 66604 66605 0;; Material: TUNGSTEN SELENIDE (WSE2); References: 20,27MID 667 66701 66701 66701 66704 66705 0;; Material: TUNGSTEN TELLURIDE (WTE2); References: 20,27MID 668 66801 66801 66801 66804 66805 0;; Material: ZINC ANTIMONIDE (ZNSB); References: 20,27,47MID 669 66901 66901 66901 66904 66905 0;; Material: BARIUM NITRATE (BA(NO3)2) (PRSD 8 K8); References: 1,27MID 670 67001 67001 67001 67004 67005 67006;; Material: BARIUM SULFATE (BASO4) (CRYSTAL); References: 27,51MID 671 67101 67101 67101 67104 67105 0;; Material: CALCIUM CARBONATE (CACO3) (NATURAL); References: 1,27,51MID 672 67201 67201 67201 67204 67205 67206;; Material: CALCITE (CACO3) (CRYSTAL) (C AXIS); References: 1,27,51MID 673 67301 67301 67301 67304 67305 67306;; Material: CALCITE (CACO3) (CRYSTAL) (A AXIS); References: 1,27,51MID 674 67401 67401 67401 67404 67405 67406;; Material: CALCIUM MAGNESIUM CARBONATE (CAMGC2O6); References: 1,27,51MID 675 67501 67501 67501 67504 67505 0;; Material: CALCIUM SULFATE DIHYDRATE (CASO4.4H2O); References: 1,27,51MID 676 67601 67601 67601 67604 67605 0;; Material: PLASTER, BUILDING (MOLDED, DRY); References: 1,27MID 677 67701 67701 67701 67704 67705 0;; Material: GYPSUM (CASO4.4H2O) (ARTIFICIAL); References: 1,27MID 678 67801 67801 67801 67804 67805 0;; Material: COPPER SULFATE (CUSO4) (CRYSTAL); References: 27MID 679 67901 67901 67901 67904 67905 0;; Material: COPPER SULFATE HYDRATE (CUSO4.5H2O); References: 1,27,51MID 680 68001 68001 68001 68004 68005 0;; Material: LITHIUM TETRABORATE (LI2O.2B2O3) (EPOX); References: 27MID 681 68101 68101 68101 68104 68105 0;; Material: MAGNESIUM SULFATE (MGSO4) (CRYSTAL); References: 1,27MID 682 68201 68201 68201 68204 68205 68206


;; Material: EPSOMITE (MGSO4.7H2O) (CRYSTAL); References: 1,27,51MID 683 68301 68301 68301 68304 68305 0;; Material: ALUM (K2SO4.AL2(SO4)3.24H2O) (CRYSTAL); References: 1,27MID 684 68401 68401 68401 68404 68405 0;; Material: CHROME ALUM (CR2(SO4)3.K2SO4.24H2O); References: 1,27MID 685 68501 68501 68501 68504 68505 0;; Material: POTASSIUM FERROCYANIDE (K4FE(CN)6.3H2O); References: 1,27MID 686 68601 68601 68601 68604 68605 0;; Material: POTASSIUM NITRATE (KNO3) (PR 8000 KB); References: 1,27MID 687 68701 68701 68701 68704 68705 68706;; Material: SODIUM CHLORATE (NACLO3) (CRYSTAL); References: 1,27,51MID 688 68801 68801 68801 68804 68805 0;; Material: STRONTIUM SULFATE (SRSO4) (CRYSTAL); References: 1,27,51MID 689 68901 68901 68901 68904 68905 0;; Material: MICA (SINGLE CRYSTAL) (A OR B AXES); References: 20,51MID 690 69001 69001 69001 69004 69005 0;; Material: MICA (SINGLE CRYSTAL) (C AXIS); References: 20,51MID 691 69101 69101 69101 69104 69105 0;; Material: MICA (SINGLE CRYSTAL) (SYNTHETIC) (98D); References: 20MID 692 69201 69201 69201 69204 69205 0;; Material: MICA BRICK (RED OR WHITE) (AVG PROP); References: 20MID 693 69301 69301 69301 69304 69305 0;; Material: BRICK, VERMICULITE; References: 20MID 694 69401 69401 69401 69404 69405 0;; Material: MICA INSULATING POWDER; References: 20MID 695 69501 69501 69501 69504 69505 0;; Material: VERMICULITE INSULATING POWDER; References: 20MID 696 69601 69601 69601 69604 69605 0;; Material: PYROPHYLLITE (PARALLEL TO BEDDING); References: 27,51MID 697 69701 69701 69701 69704 69705 0;; Material: PYROPHYLLITE (PERPEND. TO BEDDING); References: 27,51MID 698 69801 69801 69801 69804 69805 0;; Material: TALC; References: 20,27,51MID 699 69901 69901 69901 69904 69905 0


644

;; Material: TOURMALINE; References: 27,51MID 700 70001 70001 70001 70004 70005 0;; Material: GLASS (SEE REF 27, PP E5-E8) (AVG PROP); References: 27MID 701 70101 70101 70101 70104 70105 0;; Material: GLASS, BOROSILICATE CROWN; References: 27,51MID 702 70201 70201 70201 70204 70205 0;; Material: GLASS, PYREX; References: 2,20,27,51MID 703 70301 70301 70301 70304 70305 0;; Material: GLASS, CERAMIC, PYROCERAM 9606; References: 20MID 704 70401 70401 70401 70404 70405 0;; Material: GLASS, CERAMIC, PYROCERAM 9608; References: 20MID 705 70501 70501 70501 70504 70505 0;; Material: DIABASIC GLASS (ARTIFICIAL); References: 27,51MID 706 70601 70601 70601 70604 70605 0;; Material: FLINT GLASS; References: 1,27,46MID 707 70701 70701 70701 70704 70705 0;; Material: FOAMED GLASS (D = 0.144); References: 1MID 708 70801 70801 70801 70804 70805 0;; Material: GLASS, LEAD; References: 20MID 709 70901 70901 70901 70904 70905 0;; Material: GLASS, LIME WINDOW; References: 20MID 710 71001 71001 71001 71004 71005 0;; Material: GLASS, OBSIDIAN; References: 27,51MID 711 71101 71101 71101 71104 71105 0;; Material: GLASS, SODA-LIME; References: 20,27MID 712 71201 71201 71201 71204 71205 0;; Material: GLASS, SODA PLATE; References: 20,51MID 713 71301 71301 71301 71304 71305 0;; Material: GLASS, VYCOR; References: 20,27MID 714 71401 71401 71401 71404 71405 0;; Material: ALUMINA BRICK, FUSED (AL2O3 96) (22 P); References: 1,20,47MID 715 71501 71501 71501 71504 71505 71506;; Material: ALUMINA BRICK, HIGH (AL2O3 53) (20 P); References: 47MID 716 71601 71601 71601 71604 71605 71606


;; Material: ALUMINA BRICK, HIGH (AL2O3 83) (28 P); References: 47MID 717 71701 71701 71701 71704 71705 71706;; Material: ALUMINA BRICK, HIGH (AL2O3 87) (22 P); References: 20MID 718 71801 71801 71801 71804 71805 71806;; Material: BRICK, MASONRY, MEDIUM; References: 1,2,27,46MID 719 71901 71901 71901 71904 71905 0;; Material: BRICK, FIRED CARBON; References: 1,20,27,42,47MID 720 72001 72001 72001 72004 72005 0;; Material: BRICK, CHROME (CR2O3 32); References: 1,27,41MID 721 72101 72101 72101 72104 72105 0;; Material: BRICK, CHROME MAGNESITE (SEE REF 47); References: 20,47MID 722 72201 72201 72201 72204 72205 72206;; Material: CONCRETE, CINDER; References: 1,2,20,27,46MID 723 72301 72301 72301 72304 72305 0;; Material: CONCRETE, STONE (1-2-4 MIX); References: 1,2,20,27,46MID 724 72401 72401 72401 72404 72405 0;; Material: CONCRETE, 1-4 DRY; References: 1,2,20,27,46MID 725 72501 72501 72501 72504 72505 0;; Material: CONCRETE, LIGHTWEIGHT; References: 1,2,20,27,46MID 726 72601 72601 72601 72604 72605 0;; Material: BRICK, DIATOMACEOUS EARTH (ACCR STRATA); References: 4MID 727 72701 72701 72701 72704 72705 0;; Material: BRICK, DIATOMACEOUS EARTH (PRLL STRATA); References: 4MID 728 72801 72801 72801 72804 72805 0;; Material: BRICK, DIATOMACEOUS EARTH (MOLDED, FRD); References: 4MID 729 72901 72901 72901 72904 72905 0;; Material: BRICK, DIATOMACEOUS EARTH (HIGH BURN); References: 4MID 730 73001 73001 73001 73004 73005 0;; Material: BRICK, DIATOMACEOUS EARTH (USE TO 850C); References: 4MID 731 73101 73101 73101 73104 73105 0;; Material: BRICK, DIATOMACEOUS EARTH (USE TO 1100); References: 4MID 732 73201 73201 73201 73204 73205 0;; Material: BRICK, STABILIZED DOLOMITE (22 P); References: 1,47MID 733 73301 73301 73301 73304 73305 0


646

;; Material: BRICK, EGYPTIAN FIRE (SIO2 64-71); References: 20MID 734 73401 73401 73401 73404 73405 0;; Material: BRICK, NORMAL FIRECLAY (22 P); References: 47MID 735 73501 73501 73501 73504 73505 0;;; Material: BRICK, MISSOURI FIRECLAY; References: 1,47MID 736 73601 73601 73601 73604 73605 0;; Material: BRICK, SILICEOUS FIRECLAY (23 P); References: 47MID 737 73701 73701 73701 73704 73705 0;; Material: BRICK, FORSTERITE (MGO 58 SIO2 38)(20P); References: 20,47MID 738 73801 73801 73801 73804 73805 73806;; Material: BRICK, KAOLIN INSULATING (D = 0.43); References: 1,20MID 739 73901 73901 73901 73904 73905 0;; Material: BRICK, KAOLIN INSULATING (D = 0.30); References: 1,20MID 740 74001 74001 74001 74004 74005 0;; Material: BRICK, MAGNESITE SPALL RES (MGO 89); References: 1,20,27,47,48MID 741 74101 74101 74101 74104 74105 74106;; Material: BRICK, MAGNESITE (MGO 87); References: 1,20,27,47,48MID 742 74201 74201 74201 74204 74205 74206;; Material: BRICK, MAGNESITE A (MGO 90) (14.5 P); References: 1,20,27,47,48MID 743 74301 74301 74301 74304 74305 74306;; Material: BRICK, MAGNESITE B 93) (22.6 P); References: 1,20,27,47,48MID 744 74401 74401 74401 74404 74405 74406;; Material: BRICK, MAGNESITE C 86) (17.8 P); References: 1,20,27,47,48MID 745 74501 74501 74501 74504 74505 74506;; Material: BERYLLIUM OXIDE PORCELAIN 4811; References: 20MID 746 74601 74601 74601 74604 74605 0;; Material: ALUMINA PORCELAIN, HIGH; References: 20MID 747 74701 74701 74701 74704 74705 0;; Material: PORCELAIN, HIGH ZIRCON; References: 20MID 748 74801 74801 74801 74804 74805 0;; Material: MAGNESIUM TITANATE PORCELAIN; References: 20,48MID 749 74901 74901 74901 74904 74905 0;; Material: PORCELAIN 576; References: 20MID 750 75001 75001 75001 75004 75005 0


;; Material: PORCELAIN, ORDINARY; References: 1,20MID 751 75101 75101 75101 75104 75105 0;; Material: VERMICULITE, EXPANDED (D = 0.19-0.25); References: 20MID 752 75201 75201 75201 75204 75205 0;; Material: VERMICULITE, EXPANDED (D = 0.3); References: 20MID 753 75301 75301 75301 75304 75305 0;; Material: BRICK, HARD FIRED SILICA (SIO2 94-95); References: 20MID 754 75401 75401 75401 75404 75405 75406;; Material: BRICK, SILICEOUS (SIO2 89 AL2O3 9)(25P); References: 47MID 755 75501 75501 75501 75504 75505 75506;; Material: BRICK, SILLIMANITE (22 PC POROSITY); References: 20MID 756 75601 75601 75601 75604 75605 0;; Material: ALUMINUM OXIDE + CR (AL2O3 23, CR 77); References: 20,48MID 757 75701 75701 75701 75704 75705 0;; Material: ALUMINUM OXIDE + CR (AL2O3 70, CR 30); References: 20,48MID 758 75801 75801 75801 75804 75805 0;; Material: BERYLLIUM OXIDE + BE (BEO, BE 3-12); References: 20MID 759 75901 75901 75901 75904 75905 0;; Material: BERYLLIUM OXIDE + BE + MO (BE 7, MO 7); References: 20MID 760 76001 76001 76001 76004 76005 0;; Material: BERYLLIUM OXIDE + BE + SI; References: 20MID 761 76101 76101 76101 76104 76105 0;; Material: BERYLLIUM + BEO (BE, BEO 0.6-1.7); References: 20MID 762 76201 76201 76201 76204 76205 76206;; Material: CHROMIUM CARBIDE + NI (CR(X)C(Y), NI); References: 48MID 763 76301 76301 76301 76304 76305 0;; Material: SILICON CARBIDE + SI (SIC 76, SI 24); References: 20MID 764 76401 76401 76401 76404 76405 0;; Material: STRONTIUM TITANATE + CO (CO 10); References: 20MID 765 76501 76501 76501 76504 76505 0;; Material: STRONTIUM TITANATE + CO (CO 20); References: 20MID 766 76601 76601 76601 76604 76605 0;; Material: STRONTIUM TITANATE + CO (CO 30); References: 20MID 767 76701 76701 76701 76704 76705 0


648

;; Material: STRONTIUM TITANATE + CO (CO 40); References: 20MID 768 76801 76801 76801 76804 76805 0;; Material: TITANIUM CARBIDE + CO (TIC 80, CO 20); References: 20MID 769 76901 76901 76901 76904 76905 0;; Material: TITANIUM CARBIDE + CO (CO18, NBC,TAC15); References: 20MID 770 77001 77001 77001 77004 77005 0;; Material: TITANIUM CARBIDE + NBC + NI; References: 20MID 771 77101 77101 77101 77104 77105 0;; Material: TITANIUM CARBIDE CERMET K162B; References: 49MID 772 77201 77201 77201 77204 77205 0;; Material: TITANIUM CARBIDE CERMET K138A; References: 49MID 773 77301 77301 77301 77304 77305 0;; Material: TITANIUM CARBIDE CERMET K151A; References: 49MID 774 77401 77401 77401 77404 77405 0;; Material: TITANIUM CARBIDE CERMET K163B1; References: 49MID 775 77501 77501 77501 77504 77505 0;; Material: TITANIUM CARBIDE CERMET K164B; References: 49MID 776 77601 77601 77601 77604 77605 0;; Material: TITANIUM CARBIDE CERMET K165; References: 49MID 777 77701 77701 77701 77704 77705 0;; Material: TITANIUM CARBIDE CERMET K161B; References: 20MID 778 77801 77801 77801 77804 77805 0;; Material: TITANIUM CARBIDE + NI OR CO (AVG PROP); References: 48MID 779 77901 77901 77901 77904 77905 0;; Material: STEEL, TOOL, TUNGSTEN CARBIDE CA4; References: 20MID 780 78001 78001 78001 78004 78005 0;; Material: STEEL, TOOL, TUNGSTEN CARBIDE CA2; References: 20MID 781 78101 78101 78101 78104 78105 0;; Material: TUNGSTEN CARBIDE CERMET K6 AND K96; References: 20,49MID 782 78201 78201 78201 78204 78205 0;; Material: TANTALUM CARBIDE + WC CERMET K601; References: 49MID 783 78301 78301 78301 78304 78305 0;; Material: TUNGSTEN CARBIDE CERMET K94 AND K1; References: 49MID 784 78401 78401 78401 78404 78405 0


;; Material: TUNGSTEN CARBIDE CERMET K92; References: 49MID 785 78501 78501 78501 78504 78505 0;; Material: TUNGSTEN CARBIDE CERMET K701; References: 49MID 786 78601 78601 78601 78604 78605 0;; Material: TUNGSTEN CARBIDE CERMET K801 (WC + NI); References: 49MID 787 78701 78701 78701 78704 78705 0;; Material: TUNGSTEN CARBIDE CERMET CARBOLOY 999; References: 50MID 788 78801 78801 78801 78804 78805 0;; Material: TUNGSTEN CARBIDE CERMET CARBOLOY 905; References: 50MID 789 78901 78901 78901 78904 78905 0;; Material: TUNGSTEN CARBIDE CERMET CARBOLOY 883; References: 50MID 790 79001 79001 79001 79004 79005 0;; Material: TUNGSTEN TITANIUM CARBIDE K2S; References: 20,49MID 791 79101 79101 79101 79104 79105 0;; Material: TUNGSTEN TITANIUM CARBIDE K86, K7H, K3H; References: 49MID 792 79201 79201 79201 79204 79205 0;; Material: TUNGSTEN TITANIUM CARBIDE K84; References: 49MID 793 79301 79301 79301 79304 79305 0;; Material: TUNGSTEN TITANIUM CARBIDE K81; References: 49MID 794 79401 79401 79401 79404 79405 0;; Material: TUNGSTEN TITANIUM CARBIDE K5H; References: 49MID 795 79501 79501 79501 79504 79505 0;; Material: TUNGSTEN TITANIUM CARBIDE KM; References: 49MID 796 79601 79601 79601 79604 79605 0;; Material: TUNGSTEN TITANIUM CARBIDE K4H; References: 49MID 797 79701 79701 79701 79704 79705 0;; Material: TUNGSTEN TITANIUM CARBIDE K21; References: 49MID 798 79801 79801 79801 79804 79805 0;; Material: URANIUM OXIDE + CR (UO2 8O VOL) (97 D); References: 20MID 799 79901 79901 79901 79904 79905 0;; Material: URANIUM OXIDE + MO (UO2 8O VOL) (94 D); References: 20MID 800 80001 80001 80001 80004 80005 0;; Material: URANIUM OXIDE + MO (UO2 8O VOL) (91 D); References: 20MID 801 80101 80101 80101 80104 80105 0


650

;; Material: URANIUM OXIDE + MO (UO2 70 VOL) (92 D); References: 20MID 802 80201 80201 80201 80204 80205 0;; Material: URANIUM OXIDE + NB (UO2 80 VOL); References: 20MID 803 80301 80301 80301 80304 80305 0;; Material: URANIUM OXIDE + ST STEEL (UO2 70 VOL); References: 20MID 804 80401 80401 80401 80404 80405 0;; Material: URANIUM OXIDE + ST STEEL (UO2 80 VOL); References: 20MID 805 80501 80501 80501 80504 80505 0;; Material: URANIUM OXIDE + ZR (UO2 43,ZR 57)(59 P); References: 20MID 806 80601 80601 80601 80604 80605 0;; Material: URANIUM OXIDE + ZR (UO2 80,ZR 20); References: 20MID 807 80701 80701 80701 80704 80705 0;; Material: ZIRCONIUM OXIDE + TI CERMET ZT-15-M; References: 20MID 808 80801 80801 80801 80804 80805 0;; Material: ZIRCONIUM OXIDE (Y2O3 12, ZR 8) (97 D); References: 20MID 809 80901 80901 80901 80904 80905 0;; Material: BOROLITE 101 CERMET (ZRB2 93-96, B 4-7); References: 47,48MID 810 81001 81001 81001 81004 81005 0;; Material: BORIDE Z CERMET (ZRB2 81-87, MOSI2 13); References: 47,48MID 811 81101 81101 81101 81104 81105 0;; Material: AIR; References: 1,2,46MID 812 81201 81201 81201 81204 81205 81206;; Material: GRANITE (LOW K); References: 1,2,27,46,51MID 813 81301 81301 81301 81304 81305 0;; Material: GRANITE (HIGH K); References: 1,2,27,46,51MID 814 81401 81401 81401 81404 81405 0;; Material: GRANITE (AV PROP) (SEE REF 51); References: 1,2,27,46,51MID 815 81501 81501 81501 81504 81505 0;; Material: LIMESTONE (DENSE, DRY); References: 1,2,27,46,51MID 816 81601 81601 81601 81604 81605 0;; Material: LIMESTONE (H2O 15.3); References: 1,2,27,46,51MID 817 81701 81701 81701 81704 81705 0;; Material: CHALK (AV PROP); References: 1,46MID 818 81801 81801 81801 81804 81805 0


;; Material: MARBLE DIELECTRIC (XTAL) (CACO3 99.99); References: 1,27,51MID 819 81901 81901 81901 81904 81905 0;; Material: MARBLE (AV PROP) (SEE REF 51); References: 1,27,51MID 820 82001 82001 82001 82004 82005 0;; Material: ROCK OR STONE (AVERAGE PROPERTIES); References: 1,46MID 821 82101 82101 82101 82104 82105 0;; Material: SANDSTONE (HIGH DENSITY); References: 2,27,46,51MID 822 82201 82201 82201 82204 82205 0;; Material: SANDSTONE (LOW DENSITY); References: 2,27,46,51MID 823 82301 82301 82301 82304 82305 0;; Material: SANDSTONE (AV PROP) (SEE REF 51); References: 2,27,46,51MID 824 82401 82401 82401 82404 82405 0;; Material: SHALE (AV PROP) (SEE REF 51); References: 51MID 825 82501 82501 82501 82504 82505 0;; Material: SLATE (AV PROP) (SEE REF 51); References: 51MID 826 82601 82601 82601 82604 82605 0;; Material: QUARTZ FLOUR, FINE (DRY); References: 51MID 827 82701 82701 82701 82704 82705 0;; Material: SOIL, FINE QUARTZ FLOUR (H2O 21 PC); References: 51MID 828 82801 82801 82801 82804 82805 0;; Material: QUARTZ SAND (DRY) (AV PROP) (SEE REF); References: 51MID 829 82901 82901 82901 82904 82905 0;; Material: QUARTZ SAND (WET) (H2O 4-23) (AV PROP); References: 51MID 830 83001 83001 83001 83004 83005 0;; Material: SAND, NORTHWAY (H2O 4-10) (AV PROP); References: 51MID 831 83101 83101 83101 83104 83105 0;; Material: QUARTZ POWDER, COARSE (H2O 24); References: 51MID 832 83201 83201 83201 83204 83205 0;; Material: SOIL, LOAM (DRY) (AV PROP) (SEE REFS); References: 2,51MID 833 83301 83301 83301 83304 83305 0;; Material: SOIL, LOAM (H2O 4-27 PC) (AV, SEE REFS); References: 2,51MID 834 83401 83401 83401 83404 83405 0;; Material: SOIL, CLAY (WET); References: 51MID 835 83501 83501 83501 83504 83505 0


652

;; Material: SOIL (AV PROPS) (SEE REFS); References: 2,46,51MID 836 83601 83601 83601 83604 83605 0;; Material: SOIL, MARS SURFACE (SEE UCRL-50309); References: MID 837 83701 83701 83701 83704 83705 0;; Material: SOIL, SANDY DRY; References: 46MID 838 83801 83801 83801 83804 83805 0;; Material: SOIL, SANDY (H20 8); References: 46MID 839 83901 83901 83901 83904 83905 0;; Material: ABS RESIN (LOW K); References: 6MID 840 84001 84001 84001 84004 84005 0;; Material: ABS RESIN (HIGH K); References: 6MID 841 84101 84101 84101 84104 84105 0;; Material: ACETYL (DELRIN); References: 6,38MID 842 84201 84201 84201 84204 84205 0;; Material: ACRYLIC (LUCITE, PLEXIGLASS); References: 6,20,38MID 843 84301 84301 84301 84304 84305 0;; Material: ACRYLIC (HIGH K); References: 6,38MID 844 84401 84401 84401 84404 84405 0;; Material: ALKYD ISOCYANATE FOAM (DENSITY 0.16); References: 20MID 845 84501 84501 84501 84504 84505 0;; Material: ALLYL, CAST RESINS (HIGH HEAT CAPACITY); References: 6,38MID 846 84601 84601 84601 84604 84605 0;; Material: ALLYL, CAST RESINS (LOW HEAT CAPACITY); References: 6,38MID 847 84701 84701 84701 84704 84705 0;; Material: BUTADIENE-ACRYLONITRILE RUBBER + C; References: 20MID 848 84801 84801 84801 84804 84805 0;; Material: BUTYL RUBBER; References: 6,39MID 849 84901 84901 84901 84904 84905 0;; Material: CELLULOSE ACETATE (LOW K); References: 6,38MID 850 85001 85001 85001 85004 85005 0;; Material: CELLULOSE ACETATE (HIGH K); References: 6,38MID 851 85101 85101 85101 85104 85105 0;; Material: CELLULOSE ACETATE BUTYRATE (LOW K); References: 6,38MID 852 85201 85201 85201 85204 85205 0


;; Material: CELLULOSE ACETATE BUTYRATE (HIGH K); References: 6,38MID 853 85301 85301 85301 85304 85305 0;; Material: CELLULOSE NITRATE (PYROXYLIN); References: 6,38MID 854 85401 85401 85401 85404 85405 0;; Material: CELLULOSE PROPRIONATE (LOW K); References: 6,38MID 855 85501 85501 85501 85504 85505 0;; Material: CELLULOSE PROPRIONATE (HIGH K); References: 6,38MID 856 85601 85601 85601 85604 85605 0;; Material: CELLULOSE TRIACETATE; References: 38MID 857 85701 85701 85701 85704 85705 0;; Material: DIALLYL PHTHALATE (DAPON); References: 35MID 858 85801 85801 85801 85804 85805 0;; Material: EPOXY, DER 332 (C), HYSOL 6000-OP (K); References: 6,20,38MID 859 85901 85901 85901 85904 85905 0;; Material: EPOXY, GLASS FIBER FILLED (MOLDED); References: 20,38MID 860 86001 86001 86001 86004 86005 0;; Material: EPOXY, SILICA FILLED, CAST; References: 38MID 861 86101 86101 86101 86104 86105 0;; Material: EPOXY, UNFILLED, CAST; References: 38MID 862 86201 86201 86201 86204 86205 0;; Material: ETHYL CELLULOSE (WIDE RANGE OF C, K); References: 6,38MID 863 86301 86301 86301 86304 86305 0;; Material: ETHYL VINYL ACETATE; References: 38MID 864 86401 86401 86401 86404 86405 0;; Material: FLUOROCARBONS, CFE AND CTFE; References: 6,38MID 865 86501 86501 86501 86504 86505 0;; Material: FLUOROCARBONS, FEP; References: 6,38MID 866 86601 86601 86601 86604 86605 0;; Material: FLUOROCARBONS, TFE (TEFLON); References: 1,6,20,38MID 867 86701 86701 86701 86704 86705 0;; Material: TEFLON, REINFORCED; References: 20MID 868 86801 86801 86801 86804 86805 0;; Material: MELAMINE (LOW DENS, LOW K); References: 6,38MID 869 86901 86901 86901 86904 86905 0


654

;; Material: MELAMINE (HIGH DENS, HIGH K); References: 6,38MID 870 87001 87001 87001 87004 87005 0;; Material: MELAMINE, ALPHA CELLULOSE FILLED; References: 38MID 871 87101 87101 87101 87104 87105 0;; Material: MELAMINE, ASBESTOS FILLED (MST 95-205); References: 38MID 872 87201 87201 87201 87204 87205 0;; Material: MELAMINE, CELLULOSE FILLED (MST 95-205); References: 38MID 873 87301 87301 87301 87304 87305 0;; Material: MELAMINE, GLASS FIBER FILLED (MST 205); References: 6,38MID 874 87401 87401 87401 87404 87405 0;; Material: MELAMINE, FABRIC OR FLOCK FILLED; References: 6,38MID 875 87501 87501 87501 87504 87505 0;; Material: METHYL METHACRYLATE; References: 1,38MID 876 87601 87601 87601 87604 87605 0;; Material: NEOPRENE RUBBER; References: 6,38,39MID 877 87701 87701 87701 87704 87705 0;; Material: NITRILE RUBBER; References: 6,39MID 878 87801 87801 87801 87804 87805 0;; Material: NYLON 6, 11, 66, 610 (POLYCAPROLACTAM); References: 1,6,38MID 879 87901 87901 87901 87904 87905 0;; Material: NYLON, GLASS FILLED; References: MID 880 88001 88001 88001 88004 88005 0;; Material: PHENOL-FORMALDEHYDE + PHENOL-FURFURAL; References: 20MID 881 88101 88101 88101 88104 88105 0;; Material: PHENOLIC, CAST, NO FILLER; References: 6,38MID 882 88201 88201 88201 88204 88205 0;; Material: PHENOLIC, CAST, ASBESTOS FILLER; References: 6,38MID 883 88301 88301 88301 88304 88305 0;; Material: PHENOLIC, MOLDED (LOW DENSITY, K); References: 6MID 884 88401 88401 88401 88404 88405 0;; Material: PHENOLIC, MOLDED (HIGH DENSITY, K); References: 6MID 885 88501 88501 88501 88504 88505 0;; Material: PHENOLIC RESIN, PRESSED, TYPES 40, 50; References: 20MID 886 88601 88601 88601 88604 88605 0


;; Material: PHENOXY; References: 6,38MID 887 88701 88701 88701 88704 88705 0;; Material: PLASTIC LAMINATE, VARIOUS TYPES; References: 6,20MID 888 88801 88801 88801 88804 88805 0;; Material: POLYALLOMER; References: 6,38MID 889 88901 88901 88901 88904 88905 0;; Material: POLYCARBONATE, VARIOUS FILLERS; References: 6,38MID 890 89001 89001 89001 89004 89005 0;; Material: POLYESTER, GLASS FIBER REINFORCED, TAC; References: 20MID 891 89101 89101 89101 89104 89105 0;; Material: POLYETHYLENE, LOW DENSITY; References: 6,38MID 892 89201 89201 89201 89204 89205 0;; Material: POLYETHYLENE, MEDIUM DENSITY; References: 6,38MID 893 89301 89301 89301 89304 89305 0;; Material: POLYETHYLENE, HIGH DENSITY; References: 6,38MID 894 89401 89401 89401 89404 89405 0;; Material: POLYIMIDE, H-FILM, KAPTON; References: 6,40MID 895 89501 89501 89501 89504 89505 0;; Material: POLYPROPYLENE, MOPLIN; References: 6,38MID 896 89601 89601 89601 89604 89605 0;; Material: POLYPROPYLENE, COPOLYMER; References: 6,38MID 897 89701 89701 89701 89704 89705 0;; Material: POLYPROPYLENE, FILLED; References: 6MID 898 89801 89801 89801 89804 89805 0;; Material: POLYSTYRENE, FOAMED-IN-PLACE, RIGID; References: 6MID 899 89901 89901 89901 89904 89905 0;; Material: POLYSTYRENE, GENERAL PURPOSE; References: 6,20,38MID 900 90001 90001 90001 90004 90005 0;; Material: POLYSTYRENE, MODIFIED; References: 6MID 901 90101 90101 90101 90104 90105 0;; Material: POLYSTYRENE, PREFOAMED, RIGID, DOW Q103; References: 6,20MID 902 90201 90201 90201 90204 90205 0;; Material: POLYSTYRENE FOAM (D = 0.038) (1 ATM); References: 1MID 903 90301 90301 90301 90304 90305 0


656

;; Material: POLYSTYRENE FOAM (D = 0.046) (1 ATM); References: 1MID 904 90401 90401 90401 90404 90405 0;; Material: POLYSTYRENE FOAM (D = 0.046) (VACUUM); References: 1MID 905 90501 90501 90501 90504 90505 0;; Material: POLYSULFONE; References: 5,6,38MID 906 90601 90601 90601 90604 90605 0;; Material: POLYURETHANE FOAM, FLEXIBLE; References: 6,20,38MID 907 90701 90701 90701 90704 90705 0;; Material: POLYURETHANE FOAMED-IN-PLACE, RIGID; References: 6,20MID 908 90801 90801 90801 90804 90805 0;; Material: POLYURETHANE RUBBER L-100; References: 6,38MID 909 90901 90901 90901 90904 90905 0;; Material: POLYVINYL ALCOHOL; References: 6MID 910 91001 91001 91001 91004 91005 0;; Material: POLYVINYL BUTYRAL; References: 6,38MID 911 91101 91101 91101 91104 91105 0;; Material: POLYVINYL CARBAZOLE; References: 20MID 912 91201 91201 91201 91204 91205 0;; Material: POLYVINYL CHLORIDE, FLEXIBLE; References: 6,38,20MID 913 91301 91301 91301 91304 91305 0;; Material: POLYVINYL CHLORIDE, RIGID; References: 6,38,20MID 914 91401 91401 91401 91404 91405 0;; Material: POLYVINYL CHLORIDE ACYTATE, FLEXIBLE; References: 38MID 915 91501 91501 91501 91504 91505 0;; Material: POLYVINYL CHLORIDE ACYTATE, RIGID; References: 38MID 916 91601 91601 91601 91604 91605 0;; Material: POLYVINYLIDENE CHLORIDE FILM; References: 6,38MID 917 91701 91701 91701 91704 91705 0;; Material: POLYVINYLIDENE CHLORIDE; References: 6,38MID 918 91801 91801 91801 91804 91805 0;; Material: POLYVINYLIDENE FLUORIDE (KYNAR); References: 5,38MID 919 91901 91901 91901 91904 91905 0;; Material: POLYVINYL TPX-R; References: 5,38MID 920 92001 92001 92001 92004 92005 0


;; Material: RUBBER, NATURAL; References: 6MID 921 92101 92101 92101 92104 92105 0;; Material: RUBBER, DIELECTRIC MIX; References: 6,20MID 922 92201 92201 92201 92204 92205 0;; Material: RUBBER, HIGH K; References: 6,20MID 923 92301 92301 92301 92304 92305 0;; Material: RUBBER, NATURAL, FOAM; References: 6,20MID 924 92401 92401 92401 92404 92405 0;; Material: SILICONE FOAM, FLEXIBLE (LRL); References: 6,20MID 925 92501 92501 92501 92504 92505 0;; Material: SILICONE FOAM, RIGID, VARIOUS; References: 6,20MID 926 92601 92601 92601 92604 92605 0;; Material: SILICONE, MOLDED, VARIOUS FILLERS; References: 6,20,38MID 927 92701 92701 92701 92704 92705 0;; Material: SILICONE RUBBER, LOW K (SEE REF 5); References: 5,6,41,44MID 928 92801 92801 92801 92804 92805 0;; Material: SILICONE RUBBER, MEDIUM K (SEE REF 5); References: 5,6,41,44MID 929 92901 92901 92901 92904 92905 0;; Material: SILICONE RUBBER, HIGH K (SEE REF 5); References: 5,6,41,44MID 930 93001 93001 93001 93004 93005 0;; Material: SILICONE RUBBER, RTV 521 AND 093-009; References: 5,6,41,44MID 931 93101 93101 93101 93104 93105 0;; Material: RUBBER, BUNA, WITH CARBON BLACK; References: 6,20,39MID 932 93201 93201 93201 93204 93205 0;; Material: UREA-FORMALDEHYDE, MOLDED; References: 38MID 933 93301 93301 93301 93304 93305 0;; Material: UREA-FORMALDEHYDE, ALPHA CELLULOSE FLLR; References: 38MID 934 93401 93401 93401 93404 93405 0;; Material: BARATOL H.E. (TNT 26, BA NITRATE 76); References: 8MID 935 93501 93501 93501 93504 93505 0;; Material: COMPOSITION B-3 H.E. (RDX 60, TNT 40); References: 8MID 936 93601 93601 93601 93604 93605 0;; Material: COMPOSITION C-4 H.E. (RDX 90, BINDERS); References: 8MID 937 93701 93701 93701 93704 93705 0


658

;; Material: DATB H.E. (DIAMINO TRINITROBENZENE); References: 8MID 938 93801 93801 93801 93804 93805 0;; Material: LX-O4-1 H.E. (HMX 85, VITON A 15); References: 8MID 939 93901 93901 93901 93904 93905 0;; Material: MOCK H.E. RM-04-BG (LX-04-1 MECH MOCK); References: 8MID 940 94001 94001 94001 94004 94005 0;; Material: MOCK H.E. 90010 (PBX-9404 MECH MOCK); References: 8MID 941 94101 94101 94101 94104 94105 0;; Material: NITROCELLULOSE H.E. (12.7 N); References: 8MID 942 94201 94201 94201 94204 94205 0;; Material: PBX-9011 H.E. (HMX 90, ESTANE 10); References: 8MID 943 94301 94301 94301 94304 94305 0;; Material: PBX-9404-03 H.E. (HMX 94, NC 3, BIND 3); References: 8,44MID 944 94401 94401 94401 94404 94405 0;; Material: PETN H.E.; References: 8MID 945 94501 94501 94501 94504 94505 0;; Material: TETRYL H.E.; References: 8MID 946 94601 94601 94601 94604 94605 0;; Material: TNT H.E. (2,4,6-TRINITROTOLUENE) (CAST); References: 8MID 947 94701 94701 94701 94704 94705 0;; Material: MOCK H.E. LM-04-0 H4-048-A294-3; References: 5,8MID 948 94801 94801 94801 94804 94805 0;; Material: MOCK H.E. LM-04-0 H7-048-A522.1; References: 5,8MID 949 94901 94901 94901 94904 94905 0;; Material: FIBERFAX PAPER (CARBORUNDUM CO.); References: 44MID 950 95001 95001 95001 95004 95005 0;; Material: RATTAN; References: 44MID 951 95101 95101 95101 95104 95105 0;; Material: SNOW, FRESH; References: 2,27MID 952 95201 95201 95201 95204 95205 95206;; Material: SNOW, PACKED; References: 27,46MID 953 95301 95301 95301 95304 95305 95306;; Material: WOOD, SPRUCE (WITH GRAIN); References: 46MID 954 95401 95401 95401 95404 95405 0


;; Material: WOOD, SPRUCE (ACROSS GRAIN); References: 46MID 955 95501 95501 95501 95504 95505 0;; Material: CORK, GROUND; References: 2,46MID 956 95601 95601 95601 95604 95605 0;; Material: CORK, GROUND, REGRANULATED; References: 2,46MID 957 95701 95701 95701 95704 95705 0;; Material: WOOD, BALSA (ACROSS GRAIN); References: 1,2,27MID 958 95801 95801 95801 95804 95805 0;; Material: WOOD, BALSA (ACROSS GRAIN); References: 1,2,27MID 959 95901 95901 95901 95904 95905 0;; Material: WOOD, CYPRESS (ACROSS GRAIN); References: 1,27MID 960 96001 96001 96001 96004 96005 0;; Material: WOOD, MAHOGANY (ACROSS GRAIN); References: 1,27MID 961 96101 96101 96101 96104 96105 0;; Material: WOOD, MAPLE (ACROSS GRAIN); References: 1,2,27MID 962 96201 96201 96201 96204 96205 0;; Material: WOOD, OAK, WHITE, LIVE (ACROSS GRAIN); References: 1,2,27MID 963 96301 96301 96301 96304 96305 0;; Material: WOOD, OAK, RED, BLACK (ACROSS GRAIN); References: 1,2,27MID 964 96401 96401 96401 96404 96405 0;; Material: WOOD, NORWAY PINE (ACROSS GRAIN); References: 1,2,27MID 965 96501 96501 96501 96504 96505 0;; Material: WOOD, OREGON PINE (ACROSS GRAIN); References: 1,2,27MID 966 96601 96601 96601 96604 96605 0;; Material: WOOD, VIRGINIA PINE (ACROSS GRAIN); References: 1,2,27MID 967 96701 96701 96701 96704 96705 0;; Material: WOOD, NORWAY PINE (ACROSS GRAIN); References: 1,2,27MID 968 96801 96801 96801 96804 96805 0;; Material: WOOD, TEAK (ACROSS GRAIN); References: 1,2MID 969 96901 96901 96901 96904 96905 0;; Material: WOOD, WHITE FIR (ACROSS GRAIN); References: 1,2MID 970 97001 97001 97001 97004 97005 0;; Material: WOOD, WHITE PINE (ACROSS GRAIN); References: 1,2,27MID 971 97101 97101 97101 97104 97105 0


660

;

Appendix C: PATQ Preference ProgramPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

C PATQ Preference Program

Overview 662

Template File (TEMPLATEDAT) 685

PATQ Limitations 707

Patran Thermal Execution 708

Translation of Patran Thermal Input to SINDA 720

Using TRASYS Translator 754

Using NEVADA Translator 760


662

OverviewPATQ is an interface program that provides communication links between Patran, QTRAN, VIEW FACTOR, SINDA, TRASYS and NEVADA. In a nutshell, this is all that PATQ does. However, some of these communication links are fairly sophisticated.

Typical communications tasks include the following:

• Manipulating material property database files.• Conversion of a Patran neutral file to QTRAN and VIEW FACTOR input data files.• Generation of a QTRAN main program from QTRAN input data files.• Conversion of a QTRAN text output file to Patran Plus neutral file format or nodal results file

format.• Conversion of a QTRAN text output file or nodal results file sequence to X-Y plot file format for

P/PLOT.• Conversion of QTRAN binary input files to text files.• Generate thermal load conditions for a stress code from QTRAN nodal results files.• Direct conversion of QTRAN nodal results files to Patran neutral file format. This is useful for

applying thermal loads directly to an identical structural model.• A SINDA input file can be generated from the QTRAN input files that have been generated by

PATQ.• A TRASYS input file can be generated with QTRAN vfindat and templatedat files. The

TRASYS output can be translated back to QTRAN or SINDA input for further thermal analysis.• A NEVADA input file can be generated with QTRAN vfindat and templatedat files. The

NEVADA output can be translated back to QTRAN or SINDA input for further thermal analysis.

PATQ Main Menu PicksThis section explains the various PATQ menu picks that can be selected. When PATQ is executed, the following menu will appear.

Table C-1 Main Menu

663Appendix C: PATQ Preference ProgramOverview

PATQ Main Menu Picks

QuitThis option simply exits the PATQ program.

Neutral File TranslationThis is normally the first PATQ menu pick that is made to set up and run a Patran Thermal analysis. Use this menu pick to translate a Patran neutral file into QTRAN and VIEW FACTOR input data file segments. This menu pick will also cause PATQ to read in the default TEMPLATEBIN file in the Patran Thermal root directory, as well as any local TEMPLATEDAT file that exists in your current directory. A flow chart of this operation is shown in Figure C-1.

Note: If only boundary conditions have changed form a previously run model (i.e., all the necessary files exist in the current directory) use PATQ utility pick 14 to redefine only files associated with boundary conditions.


664

Figure C-1 Patran Thermal Process Flow Diagram


(continued)

With menu pick 2, PATQ uses the following 3 input data files:

1. Patran neutral file with the thermal model in it, 2. TEMPLATEDAT file (a template file in the local directory), and/or3. TEMPLATEBIN file that is in the Patran Thermal root directory (THERMAL$DIR:[LIBRARY]

on VAX systems).


666

The Patran neutral file must contain all of the Phase 2 data associated with the model (nodes, elements, element properties and boundary conditions).

The TEMPLATEDAT file (see the TEMPLATEFILE subsection for more information) contains auxiliary data that aids PATQ in the translation of the neutral file.

The TEMPLATEBIN file located in the Patran Thermal root directory (THERMAL$DIR:[LIBRARY] on VAX VMS systems) contains MID templates for all materials included in MSc.Software Corporation thermal material property database files (MPIDMKS, MPIDIPS, MPIDFPH, and MPIDCGS also located in the Patran Thermal root directory). If PATQ encounters an MID number in the Patran neutral file and cannot find a corresponding MID template in your local TEMPLATEDAT file, PATQ will attempt to find the missing MID template in the TEMPLATEBIN file. If the MID template is not found, PATQ will abort the translation process. If PATQ does find a matching MID template in TEMPLATEBIN, PATQ will append the MID template to the local TEMPLATEDAT file and also write out a message to the screen.

PATQ menu pick 2 will generate 19 Patran Thermal data files and (optionally) 1 VIEW FACTOR data file. The Patran Thermal data files are as follows:


PATQ will delete any data files that are empty at the end of the translation process initiated by menu pick 2.

The result of a successful translation process as outlined above is a collection of input data files for QTRAN and VIEW FACTOR.

1.2.3.4.5.6.7.8.9.10.11.12.1.

TITLEDAT

NOEDAT

NODXYZDAT

CONDUCDAT

CONVECDAT

RESDAT

CAPDAT

QMACRODAT

TMACRODAT

TFIXDAT

TEMPDAT

QBASEDAT

Neutral File Title Data

Node Number Declarations

Node Locations

Binary Conductive Resistor Data

Convective Resistor Data

Advective Resistor Data, also Reserved For Miscellaneous Resistor Data

Binary Capacitor Data

QMACRO Function Data

TMACRO Function Data

Fixed Node Declaration Data

Initial Node Temperature Data

Constant Heat Source Data

13.

140

15

16

1718

19

20

MMACRODAT

MDBASEDAT

PMACRODAT

PRESSDAT

PFIXDAT

PNODEDAT

FRESDAT

VFINDAT

MMACRO Function Data

Constant Mass Flow Data

PMACRO Function Data

Initial Nodal Pressure Data

Fixed Pressure Node Data

Flow Network Node Data

Flow Network Resistor and Associated Information

View factor Input


668

After PATQ menu pick 2 is selected, PATQ will display a series of submenus. These submenus include declaring the dimensionality of the problem as shown below.

Model Dimensionality

Table C-2 Dimensionality Options

If -2 is selected as the pick (2-D axisymmetric R-Z), PATQ will also prompt which Patran axis to use for the R and Z. This is necessary because Patran models only exist in 3-D Cartesian X-Y-Z space. Normally, one would use the X-axis for R and the Y-axis for Z, since these are the two Patran axes that lie in the plane of the graphics screen by default. However, when performing analyses on rotating machinery, such as turbines, the Patran X-axis may be selected for the Z-axis and the Patran Y-axis may be selected for the R-axis. This is perfectly allowable. Similarly, it may be necessary to choose some other combination in order to maintain compatibility with some other analysis code that uses a fixed convention for R and Z-axis. For example, some structural codes require the use of the X-axis for R and the Z-axis for Z.

The Patran Thermal convention regarding 2-D elements is that all 2-D Cartesian elements are of unit thickness, (i.e., they have a depth of 1 unit parallel to the Z-axis). All 2-D axisymmetric elements are rotated through a complete 360° rotation (i.e., the elements are toroidal or ring elements).

Units ConversionPATQ will also ask if a units conversion on nodal coordinates needs to be performed. This allows a Patran model that was built in one system of units (e.g., inches) to be transformed to another system of units that may be more compatible with the data available for the thermal model (e.g., meters). This conversion operation effects all element surface areas, cross-sectional areas, and thicknesses. It specifically does NOT operate on anything else. For example, this conversion process will affect the units that element surface areas are given in, but will not affect the units that heat fluxes are given in (e.g., Watts/m2 vs. Btu/in2). If converting a Patran model from inches to meters, make sure that the heat fluxes are given in units of power/m2 in the Loads/BCs menu. Note that 2-D triangular and quad elements are always assumed to be of unit depth, even after the coordinate transformation.

Spawn VIEW FACTOR ExectionAfter the Patran neutral file has been translated, option 3 provides the ability to spawn a batch job which will perform the necessary view factor calculations and generate the required radiosity nodes and radiation resistors. After entering this option, PATQ will query the user and determine if a VFCTL needs to be brought in a file from the Patran Thermal root directory. This file is necessary in order to run the VIEW FACTOR code and seldom changes from the default supplied. PATQ will also query whether to retrieve a QINDAT file from the root directory. This file is necessary to create the main program during menu pick 4, but more care needs to be exercised as to whether the root file is satisfactory or if it must


be edited first. The default QINDAT file is set up for a steady-state run with the standard execution option as the defaults. If none of the options are going to be exercised which will change array sizes such as print or maximum time step staging times, and the standard solution module will be executed, then it is probably safe to use the default directory to create the main module even though the start, stop times, and print interval will have to be changed with the editor before the job is executed. The preferred way is to have the QINDAT file edited prior to executing the PATQ module.

QTRANFOR GenerationThe purpose of PATQ menu pick 4 is to generate a new QTRAN main program source file, QTRANFOR. This menu pick is performed after the following steps:

1. Having successfully translated a Patran neutral file with menu pick 2;2. Optionally having successfully executed the VIEW FACTOR program to generate radiosity

network data for the VFRESDAT file. See Introduction (Ch. 1) in the Patran Viewfactor Analysis;3. Having generated any material property data that is not contained in the MSc.Software

Corporation thermal material property database with the system editor in the MATDAT file;4. Having generated any necessary QTRAN MICROfunction data in the MICRODAT file (see

Thermal/Hydraulic Input Deck (Ch. 8)); and5. Having copied and modified (as necessary) a QINDAT QTRAN input data file.

After successfully generating a new QTRANFOR main program source file (Menu Pick 4), select menu pick 5 to compile the QTRANFOR file into a QTRANOBJ object file, link with the QTRAN library files QTRANOLB and ULIBOLB generating the QTRAN executable QTRANEXE, and submitting QTRANEXE for batch execution. This is shown schematically in Figure C-1.

Material File DefinitionsAs PATQ is generating the QTRANFOR file from QINDAT and the $INSERT files, it may come across a reference to an MPID number that is not included in the MATDAT file (lets assume that a material property data set was not built). PATQ will inquire as to what to do if it came across an MPID that was referenced but never defined (i.e., was not in the MATDAT file)). The prompt is as follows:

Table C-3 Material Property File Selections Available

These four BIN files contain identical information, but in different units systems. These binary files are direct access format. It is possible to, delete, copy, or modify these files at will by editing the text files in MATDAT format and converting them with PATQ utility menu pick 2.


670

The binary MID template file TEMPLATEBIN contains the MID templates for these files (all of these files use the same MPID numbers for the same material properties, so they all require identical MID templates). A text version of TEMPLATEBIN is provided as TEMPLATETXT and is also located in Mid Templates Supplied in Templatebin and Templatetxt (App. B). If the MPID files are modified also modify the TEMPLATETXT file accordingly. Using PATQ utilities menu pick 2, generate an updated TEMPLATEBIN file that will reflect the changes to the MPID files.

If PATQ encounters an MPID number that has not been defined in the local MATDAT file, and it is decided not to search the MPIDxxxBIN files, PATQ then aborts the QTRANFOR generation process. Likewise, if PATQ cannot find a referenced MPID number in either the local MATDAT file or in the MPIDxxxBIN file that is specified, PATQ will abort the process.

When PATQ searches through one of the MPIDxxxBIN files (as directed by the user) and finds a match for the specified MPID number, PATQ will then copy the MPID data set from the MPIDxxx file and append it to the local MATDAT file.

There is currently no practical way to scan through the material property files looking for a particular material or data set. The most straightforward way is to find the material of interest in Appendix C or in the TEMPLATETXT file by using the system editor (this file is considerably shorter than any of the MPIDxxx files). Once the material is located use the system editor to search through the appropriate MPIDxxx file to examine the MPID data sets for that material.

Spawn QTRAN Execution to BatchMain menu pick 5 allows the QTRAN job to be spawned off as a batch job. The batch job will compile the QTRANFOR main program created with menu pick 4. After compilation, the main program will be linked with any user routines that have been compiled into the ULIBOLB library in the execution directory or will link to the appropriate routines in the Patran Thermal root library where QTRANOLB and ULIBOLB reside. Then the job will be executed.

Additional PATQ Utilities OptionsSeveral addition PATQ options for data manipulation are available through the utilities option menu. This menu is defined in the following section.

PATQ Utility Menu PicksWhen menu pick 6 is selected from the main menu, the following menu appears:

Table C-4 Utility Menu


Return to Main MenuFinished with utility operations, return to main menu.

Access the Material Property Database UtilityThere are currently two utilities available under this menu pick, and under normal day-to-day operation you will NOT need to use them. After menu pick two of the utility menu is selected, the following selection options are presented.

Table C-5 Material File Manipulation Options

The first option converts a template file containing only MID templates in text form to a binary file TEMPLATEBIN. The system administrator may replace the TEMPLATEBIN file which MSc.Software


672

Corporation Engineering provides in the Patran Thermal root directory (THERMAL$DIR:[LIBRARY] on VAX VMS systems) with a TEMPLATEBIN file that is generated.

Reasons for performing this task are as follows:

1. To add the templates to the TEMPLATEBIN file from which PATQ routinely loads default MID templates. This is handy for those using the same computer who are routinely using a set of material properties and MID templates specific to the analyses that are not included in the TEMPLATEBIN file provided by MSc.Software Corporation. Besides making these additions to the TEMPLATEBIN file, add the MPID data sets to the various MPID files which are also located in the QTRAN root directory. Since these MPID files are text, these files may be added by simply using the system editor.

2. If the default MID templates in the TEMPLATEBIN file are never used and they have become annoying because of the time it takes PATQ to load all of the default MID templates from this file each time a Patran Neutral File translation is performed. In this case, generate a much smaller TEMPLATEBIN file which contains only those MID templates that are routinely used. Please note that PATQ only requires a matter of a few seconds to load the TEMPLATEBIN files, so this is not generally a great motivation to replace the MSc.Software Corporation supplied TEMPLATEBIN file with a smaller customized TEMPLATEBIN file.

The second option allows the binary direct access materials database to be updated. The MPID files, MPIDMKSBIN, MPIDIPSBIN, and MPIDFPHBIN are located in THERMAL$DIR:[LIBRARY]. These files are binary direct access versions of the old MPID data files. Update or tailor the default material database with material properties that are more suited to the applications. This can be done by updating the MPIDxxx text files and then using PATQ utilities menu pick 2 with the second option to convert an existing MPIDxxx file to an MPIDxxxBIN file which PATQ can use when creating the main program with main menu pick 4.

The BIN files are binary direct access with 80 byte records. The first record consists of two integers (Record_A and Record_B) in text form and I10 format, followed by 60 blanks. The first integer is the file record number where the file index begins. The second integer is file record number where the file index ends. Following this first record, this file will contain MPID data sets in text form beginning with record 2 until the beginning of the file index.

For more information on material property database options, examine the text for main menu pick 4, “QTRAN.FOR GENERATION”.

This menu pick can also be used to semi-automatically retrieve material property data sets from the MPID files located in the Patran Thermal root directory (THERMAL$DIR:[LIBRARY] on VAX systems).

File StructureRecord 1 Record_A Record_BRecord 2 MPID dataRecord Athrough B

Index


QOUTDAT Conversion to NRnnnNRF FilesThis menu pick converts trains output file QOUTDAT into a series of Patran nodal results files NRnnnNRF, where “nnn” is an integer number corresponding to the “nnn'th” QTRAN print dump found in the QOUTDAT file. Patran can then read and display the NRnnnNRF nodal results files. Normally, this command does not need to be used because Patran Thermal now generates nodal results files as a part of its standard output. The hydraulic results files are not created.

Output columns in the nodal results files.

* These values are not put in the nodal results file if it is created from a QOUTDAT file.

QOUTDAT Conversion to NFnnnNEU FilesThis menu pick converts QTRAN’s output file QOUTDAT into a series of Patran neutral files NFnnnNEU, where “nnn” is an integer number corresponding to the “nnn'th” QTRAN print dump found in the QOUTDAT file. Patran can then read the NFnnnNEU files and apply them as thermal load cases for structural analysis codes.

X-Y PLOT File Generation (Result vs. Time)Using PATQ utility menu pick 5, temperature vs. time plot files can be generated for the Patran X-Y plot utility. PATQ will use the time value that QTRAN puts at the beginning of each nodal results file as the X data value.

After selecting utility menu pick 5, PATQ will display the following menu.

Table C-6 X-Y Plot Data Source Options

Column Value 1

2

3

4*

5*

6*

7*

8*

Temperature

Net nodal heat flow rate

Explicit Stable Time Step

QMACRO function input for each node

QBASE input for each node

Total heat source output for each node

Temperature error for the last iteration for each node

Average convection coefficient (h)


674

1. QUITThis option simply quits and returns to the top level PATQ menu.

2. NODAL RESULTSIf menu pick 2 is selected (or simply hit the RETURN key), PATQ will build a temperature vs. time plot file from a series of QTRAN nodal results files named NRnnnNRF in sequence. PATQ will prompt for the name of the temperature vs. time plot file name, as well as for the “nnn” value for the first nodal results file to be included in the X-Y plot file (the default “nnn” value is 0). The X-Y plot file name will be the name of a file suitable for reading into Patran’s X-Y plot module for display. PATQ will also prompt for the node number whose history to plot and the nodal results file column number to use. Column number 1 from the nodal results file is temperature (the default), column number 2 is the net nodal heat flow rate, and column number 3 is the explicit stable time step for the node.

3. QOUTDAT FILEIf menu pick 3 is selected, PATQ will attempt to build the temperature vs. time plot file from a QTRAN output file such as QOUTDAT (PATQ will prompt for the actual QTRAN output file name). PATQ will also prompt for two other file names--a “Plot File” and an “X-Y Plot File”. The Plot File refers to a print-plot file suitable for printing on a line printer, while the X-Y “Plot File” refers to a file suitable for reading into Patran’s X-Y plot utility. This utility will prompt for the minimum and maximum expected temperatures for the node, as well as the node number for which temperature history data is desired. Since this utility operates off of a text QOUTDAT (possibly renamed to something else), it is somewhat slower than the X-Y plot file utility that operates off of the nodal results files. Also, while this utility generates both a print-plot file and an X-Y plot file, it can only work with temperature data from QTRAN. The advantage of this print-plot utility is that it is nice for getting a relatively accurate and quick temperature history data for nodes and a graphics terminal is not needed to interpret the results.

Binary File Conversions to Text FilesUsing PATQ utility menu pick 6, the QTRAN binary input files CONDUCDAT, VFRESDAT, CAPDAT, or QPLOTDAT can be converted into text files CONDUCTXT, VFRESTXT, CAPTXT, or QPLOTTXT. This can be useful for debugging.

It is worth noting here that there is relatively little useful information in the CONDUCDAT file (i.e., node numbers and thermal conductivity MPID numbers are typically the only useful data there). This is because the conductive resistors are generated via pates finite element translation utility which constructs finite difference “resistors” mathematically from the finite element data. These resistors have very “unusual” area/length ratios (including many that are negative). These area/length ratios have no obvious geometric interpretations, and so it is very difficult to look at the area/length ratios and then determine if


they are correct. Furthermore, PATQ actually “merges” parallel and nonlinearly similar resistors prior to placing the resistors in the CONDUCDAT file. This further dims the ability to interpret the accuracy of these resistors.

The binary capacitor data in CAPDAT is also generated from the Finite Element translation process; but, because it is generated using the lumped capacitance matrix approach to Finite Elements, the capacitance data has somewhat more of a parallel to the physical geometry of the elements. However, PATQ also merges parallel and nonlinearly similar capacitors (capacitors which have the same material properties) in the same manner as the conductive resistors. As with the conductive resistors, node numbers and MPID numbers make sense, but interpreting the capacitance volumes is not straightforward.

The QPLOTDAT is a compact binary file that contains three header records, a time information record, and a node temperature record. To examine this file or take it to a different system to do postprocessing, it would be necessary to create an ASCII file with FORTRAN control characters. The format of the output file, QPLOTTXT, would include the three 80-character header records. These contain the version of the code used for the analysis, the date and time that the analysis was executed and a title identifying the run. A time stamp record then precedes each group of temperatures output. This record contains the time at which the temperatures apply, the number of temperatures output, and a statement indicating if the solution was the result of a transient or steady-state calculation. The node number and corresponding temperature in the ICCALC units follow.

Interpolation of Temperatures to a Dissimilar Structural MeshThis menu pick takes a Patran thermal neutral file and accompanying QTRAN nodal results files and maps temperatures onto the nodes of a Patran structural neutral file, generating a Patran neutral file containing packet 10 data (packet 10 data is temperature data) or a new nodal results file. This menu pick is used when the thermal mesh and structural mesh are different. If the two meshes are identical, use menu pick 8 instead because it is significantly faster.

After selecting this menu pick, PATQ gives a brief explanation of what is about to happen (see Figure C-1). The user will be asked if they desire to create a new nodal results files in addition to the neutral files. By far the most work is done selecting the interpolation factors that are to be used between the different neutral files. If they are available from a previous operation, they can be specified as the parameters that should be used form this operation by giving the name of the file containing the information created with an earlier operation. PATQ then prompts for the FROM neutral file. The FROM neutral file refers to the name of the neutral file containing the thermal model (i.e., the file FROM which the temperatures are mapped). The default file name is THERMALOUT.


676

Figure C-2 PATQ Utility Menu Pick 7 Process Flow Diagram

PATQ’s next prompt is for the TO neutral file. The TO neutral file refers to the name of the neutral file containing the structural (although it can in fact be thermal or any other Patran neutral file) model that the temperatures are mapped TO. The default file name is PATRANOUT.

The next prompt is for the MAPPED neutral file name, with the default being PATRANMAP. The MAPPED neutral file is where all of the temperature LBC (packet 10) data goes that is generated by the interpolation process. It is this MAPPED neutral file that is normally read in by Patran to apply the interpolated temperatures as thermal load conditions to a structural model. For example, suppose that a structural model Patran database is named STRUCTDAT. Execute Patran using the STRUCTDAT file as the “old” Patran database and then read in the MAPPED neutral file (e.g., PATRANMAP) thermal load cases for the structural model.

The next prompt from PATQ is for the tolerance value, with a default of 0.01. This tolerance value is used to determine how far away a node should be from a thermal element before it automatically becomes ineligible to be paired with that thermal element. The 0.01 default value is obviously totally arbitrary, since a “good” tolerance value is extremely problem and units dependent. From a user’s standpoint, a small tolerance value has two effects. First, it speeds things up because it eliminates many pairing possibilities via very quick “box” tests. That was the good news. The bad news is that near curved boundaries may disallow some pairings that should occur (see Figure C-2).


The program will calculate a minimum tolerance based on the spread of the node locations and the number of elements and nodes. If this value is smaller than that specified by the user it will be used as the initial guess in determining which nodes should be associated with which element. A recursive procedure is used in the selection process. If nodes are not within the tolerance a larger tolerance is used to evaluate all the nodes that didn’t fall within last tolerance used. The user can input a single tolerance or a maximum and minimum value with the number of cycle to be used to move between the minimum and maximum values. If the code had computed a tolerance smaller than specified by the user an additional cycle is added to the recursive process. A logarithmic interpolation between the minimum and maximum values is used to determine the intermediate tolerance values.

Figure C-3 demonstrates how structural nodes with a dissimilar mesh can lie outside of thermal elements near curved boundaries, even though both meshes model the same solid. As can be seen below, this occurs when curved boundaries are represented by chords generated from the sides of an element that is not of sufficient order to exactly model the curvature of the solid. Here, we have linear elements approximating a distinctly nonlinear curved boundary. The result is that there are gaps between the element sides and the curved boundary of the solid. The structural nodes should be within a user-specified distance (tolerance) of the thermal elements if interpolation is to take place.

Figure C-3 Structural Nodes with a Dissimilar Mesh

The interpolation process consists of two major steps. The first step is to determine the thermal element that each structural node should be associated with. The second step is the actual interpolation process.

Step one involves determining how far away each structural node is from each thermal element. If the distance is within tolerance, the thermal element with the shortest distance becomes the owner of the


678

structural node. If no thermal element is within tolerance, then no temperature data is generated for the structural node and the structural node is declared to be out of tolerance. As long as the structural node is inside of some thermal element, life is very easy. Since temperatures are continuous from element to element (i.e., the elements guarantee C0 continuity), ambiguities which arise due to a structural node being on the boundary of one or more thermal elements does not even present any problems. Simply pick an arbitrary thermal element from any of the boundary elements and the C0 continuity guarantees that the same answer is obtained no matter which of the boundary elements are picked. If the structural node is actually in the interior of some thermal element, that element by definition owns that structural node.

To actually perform the interpolation, the parametric coordinates must be computed (here referred to as R, S, and T coordinates) for the structural node relative to the thermal element that owns it. See Figure C-4 and Figure C-5. This is done with a simple Newton-Raphson routine. Once the R, S, and T coordinates have been computed, interpolation can be performed by simple substitution into the element’s basis functions and using the appropriate nodal results files.

First a “real space” element is mapped into parametric space as in Figure C-4.

After passing a rudimentary “box test” to verify that the structural nodes are within a rectangular tolerance envelope of the thermal elements, the structural nodes not eliminated by the box test are also mapped into parametric space. See Figure C-5. If their parametric coordinates are within +1 to -1, they are definitely inside the thermal element and temperature interpolation. If they are not in this range, the parametric coordinates are “clipped” to +1 or -1 and the real space coordinates of the clipped point are then computed.

Figure C-4 Mapping a Thermal Element from Real Space to Parametric Space


Figure C-5 Box Test Quickly Excludes Nodes which are Clearly Outside of the User Assigned Tolerance Bounds. Next, Parametric (R<S) Coordinates are Calculated for Nodes Which Pass the Box Test. The (R,S) Coordinates are Clipped (Limited) to ± 1

As mentioned earlier, this is all very straightforward as long as the structural node actually lies within or on the boundary of some thermal element. Unfortunately, we do not always have this luxury. Sometimes the structural nodes actually lie very close, but outside of the nearest thermal element. This typically happens in models with a curvature. What PATQ does in this case is to compute the R, S, and T parametric coordinates for the structural node, but it limits R, S, and T to the interval +1 to -1 (that is, it “clips” the parametric coordinates see Figure C-6). The +1 to -1 interval limits the computed parametric coordinates to lying on the boundary of the thermal element. The real space (X-Y-Z) distance from the clipped position to the structural node’s actual position is then compared to the tolerance value. If it is within tolerance, this element can then be considered as an owner of the structural node. If it does become the owner, the clipped R, S, and T coordinates are used in the element interpolation functions. This prevents extrapolation beyond the element boundaries (which is what would result if R, S, and T were not clipped), and this is very desirable since the interpolation functions are in general very poorly behaved outside of the elements.

Figure C-4 and Figure C-6 show the results of “clipping” the structural node’s R and S parametric coordinates so that they lie in the interval +1 to -1. The real space coordinates of the clipped point lies on the edge of the element. The distance between this clipped point and the structural node’s true position are compared to the user supplied tolerance value. If the distance is greater than the tolerance value, the structural node is disallowed from being associated with this thermal element. If any other thermal element pairing with the structural node results in a smaller tolerance, the other thermal element becomes the owner of the structural node.


680

Figure C-6 Clipped Node Location of a Structural Node Which Lies Outside of a Thermal Element

PATQ generates a diagnostics file TOLERANCEDAT as a result of the structural node to thermal element pairing operations. It lists the tolerance value (distance from the element edge to the structural node), as well as the “clipped” parametric coordinates of each structural node. It also contains a brief summary of all out-of-tolerance structural nodes.

The user will be asked if he desires to save the interpolation information between the given neutral files for later operations.

After prompting for the tolerance value, PATQ next prompts for the starting Patran SID (set ID, or load case ID) to use. This SID will be output with the neutral file packet 10s generated from interpolating the first nodal results file. Every subsequent nodal results file used in the interpolation process will use an incremented value of this SID.

After prompting for the starting SID, PATQ then reads in the FROM and TO neutral files. PATQ will routinely indicate its progress in reading these files. If no errors are encountered in this process, PATQ then proceeds with the structural node and thermal element pairing operations. If no problems are still detected, PATQ indicates any out-of-tolerance nodes found and writes out the data to the TOLERANCEDAT file.

PATQ then issues the following prompt:

Which column number from the nodal results files do you wish to map values from (for QTRAN, column 1 is the column for temperatures)? (default = 1, type STOP to stop)

Although any column may be selected from a nodal results file, column 1 is the only one that really makes sense for QTRAN nodal results files.


PATQ will continue to indicate its status during the course of the actual interpolation process. It is worth noting that the interpolation process takes very little time relative to the structural node / thermal element pairing operations.

After performing the interpolation process with the designated nodal results file, PATQ will then prompt you with the following.

Do you wish to process another Nodal Results File?(Y or N, default = Y)

If you answer Y, PATQ will then prompt you for the appropriate nodal results file and perform another interpolation (PATQ does not have to go through the pairing operations again).

Convert THERMAL Nodal Results Files to Neutral FilesPATQ utility menu pick 8 generates Patran neutral files containing temperature data (packet 10 information) directly from QTRAN nodal results files. These neutral file packets can then be read by Patran and applied to a structural model as thermal load conditions. A restriction of this menu pick is that the thermal and structural meshes be identical.

If the two meshes are identical, this option is much preferred over PATQ utility menu pick 7 because this pick is significantly faster.

Create a Single Bulk Data FilePATQ utility menu pick 9 “lumps” the QINDAT and all referenced $INSERT files together into a single text output file. This is useful if preparing a QTRAN data input set on a workstation and then transferring the input files across a file network to a mainframe host.

Report Times in Nodal Results FilesPATQ utility menu pick 10 examines a sequence of nodal results files and reports on the simulation time that corresponds to each NRnnnNRF file. This menu pick, as well as utility menu pick 5 (X-Y Plot File Generation), takes a range of NRnnnNRF files. This allows nonsequential NRnnnNRF files to be created and still gets a full traversal of the nodal results files.

Create LCI Type Material PropertiesPATQ utility menu pick 11 reads a MATDAT file and the user can select material properties (through the MPID) that are to be converted to linear computed interval, LCI, type property records. This provides you with the ability to convert table, Hermite, or power series type material properties to the linear computed interval type table which is the most CPU time efficient multi-entry type table. You also have the option to bound the properties to prevent improper extrapolation if the independent variable exceeds

Important:The CONDUCDAT, VFRESDAT, and CAPDAT files are normally output in binary form for a reason (i.e., they can be very LARGE when in text form). This menu pick translates these binary files to text form files. Keep an eye on the available disk space. Also note that the conversion from binary to formatted text form can take a nontrivial amount of CPU time.


682

the table limits. This is done by duplicating the beginning and ending table values. Other table types can be bounded also. However, if a Hermite type table is being bounded, three table entries must be repeated to limit the quadratic extrapolation. PATQ is also going to prompt for the desired starting, ending, and increment desired for the converted property. Know these bounds before entering PATQ.

Specify Direct Solver Memory SizePATQ utility menu pick 12 reads a record that will be used to allocate the quantity of memory that is to be reserved for use by the direct solver. If more memory is required, the problem is segmented into enough partitions so that each partition does not exceed the reserved memory. The default value is 2,000,000 double precision words.

Convert Binary Nodal Results Files to ASCII Nodal Results FilesPATQ utility menu pick 13 will read a specified group of binary nodal results files between specified beginning and ending files and convert them from the standard Patran binary format to the standard ASCII format.

Redfine Boundary ConditionsPATQ utility menu pick 14 will create the boundary condition network without retranslating the node and element definitions. Any model in which the node numbers, location and associativity with the elements is unchanged, but it is desirable to define new boundary conditions can be done with this menu pick. There is no selective options on which boundary conditions are redefined. All boundary conditions will be redefined. One, note of caution: If a boundary condition type has been deleted, it is the responsibility of the user to delete any old file which referenced this boundary condition. For example, if convection had been specified, a CONVECDAT file would have been created. If the convective boundary condition is deleted in the new boundary condition specification, a new convection file would not be generated; however, the old file would still be present and would be used when QTRAN is executed, unless the user deletes it beforehand.

Create SINDA Input File From QTRAN InputPATQ utility menu pick 15 will read the files created by PATQ for input to QTRAN and View factor and creates an input deck that can be executed by SINDA. Two SINDA formats are supported. One is an input deck defined in a format suitable for input to Network Analysis’ SINDA and the other is for input to SINDA85. All options are not available for translation to SINDA and when these conditions arise, appropriate error messages are written to the message file. The message file should be examined for error messages. There is no support in SINDA to properly model variable emissivity of spectral radiation, so these conditions would flag a translation error. For further information, see Translation of Patran Thermal Input to SINDA, 720.

Create TRASYS Input from vfin.dat FilePATQ utility menu pick 16 will read the vfin.dat file created with PATQ man menu pick 2 and use the VTRA directives from the template.dat file to create the geometry input for TRASYS. Triangular or quadratic type surfaces are supported. Only one enclosure can be defined for TRASYS evaluation.


Unlike the SINDA input which can generate a run ready deck, the geometry file must be included in an edited version of the TRASYS run control deck. For further information, see Translating Patran Thermal Model to TRASYS Input, 754.

Create P/Thermal Input from TRASYS outputPATQ utility menu pick 17 will read the TRASYS “punched card” file and create radiation resistors between the surface nodes for radiation interchange and define macro and micro functions necessary to define the average or periodic heating loads resulting from solar heating during orbital flight. The default file names are referenced in the qin.dat so QTRAN will execute when the appropriate files are included in the execution directory. Care should be taken so that heating loads or multiple radiation is not defined. For example, do not include both periodic and average heating files with the default names at the same time, or both heating rates will be applied. For further information, see TRASYS Output to Patran Thermal Input, 756.

Create NEVADA Input from vfin.dat FilePATQ utility menu pick 18 will read the vfin.dat file created with PATQ man menu pick 2 and use the VNEV directives from the template.dat file to create the geometry input for NEVADA. Triangular or quadratic type surfaces are supported. Only one enclosure can be defined for NEVADA evaluation. Like TRASYS, the geometry input file must be edited in the appropriate run control deck. NEVADA fixes the free space temperature to 9999; thus, it is suggested that this ID be used to define the free space ambient node when creating your model and applying the boundary conditions. For further information, see Translating Patran Thermal Model to NEVADA Input, 761.

Create P/Thermal Input from NEVADA outputPATQ utility menu pick 18 will read the NEVADA linage file and create radiation resistors between the surface nodes for radiation interchange and define macro and micro functions necessary to define the average or periodic heating loads resulting from solar heating during orbital flight. The default file names are referenced in the qin.dat so QTRAN will execute when the appropriate files are included in the execution directory. Care should be taken so that heating loads or multiple radiation is not defined. For example, do not include both periodic and average heating files with the default names at the same time or both heating rates will be applied. Also, if the radiation interchange is defined by NEVADA, the P/THERMAL View Factor code should not be run to determine the radiation interchange for this enclosure. For further information, see NEVADA Output to Patran Thermal Input, 763

Convert ASCII Data Files to BinaryPATQ utility menu pick 20 will read the CONDUCDAT, VFRESDAT< CAPDAT, or QPLOTDAT ASCII files and convert them to binary files. This is to allow generic storage of input files for archival purposes or for transferring run decks between different platforms. The ASCII files could have been generated with PATQ utility option 9.


684

Convert ASCII Nodal Results Files to BinaryPATQ utility menu pick 21 will read a Nodal Results ASCII data file and convert it to binary file. This is to allow generic storage of input files for archival purposes or for transferring run decks between different platforms. The ASCII files could have been generated with PATQ utility option 13 or the result of a temperature mapping operation - utility option 7.

685Appendix C: PATQ Preference ProgramTemplate File (TEMPLATEDAT)

Template File (TEMPLATEDAT)The TEMPLATE file is probably the most difficult concept in the entire Patran Thermal system to learn. It is, however, an extremely powerful technique for linking the large quantities of data required for a sophisticated nonlinear analysis to the relatively simple data supplied the Patran. The ability to treat the TEMPLATE file as a library of data is also extremely useful and greatly reduces the man-hours involved in setting up similar analyses.

The concept of the TEMPLATE file is as follows. In the Patran model, supply very short and simple data such as integer numbers (template IDs) to identify materials or to specify boundary conditions. These template ID's (TIDs) are used by PATQ as pointers. Each TID refers to a particular template in the TEMPLATE file. PATQ will use the data in the template identified with the TID number to get additional necessary data for a material or boundary condition.

There are currently seven different types of templates in the TEMPLATE file. These five types are as follows.

Each of these template types is explained in the following subsections. Note that while unique TID numbers for each template type must be used, the same TID numbers for different template types can also be used. For example, there may be only one MID template with a TID of 1. However, there can be an MID template with a TID of 1 and a MACRO template with a TID of 1.

Templates do not have to be sequentially ordered, nor do the template types have to be in any particular order.

A sample TEMPLATE file is provided with the Patran Thermal software and may be accessed with the “GET_QTRAN STARTUP” command at the system level.

Comments can be entered into the TEMPLATE file by beginning any line with an asterisk (*) or semicolon (;). The remainder of any such line will be ignored.

The TEMPLATE file accepts free format input. Free format may be used to input data to the TEMPLATE file.

MID Templates

MACRO Templates

CONV Templates

VFAC Templates

VTRA Templates

VNEV Templates

FLUID Templates

(Material Identification)

(Heat, Temperature, Pressure, Mass Flow Rate Variations)

(Convective Boundary Conditions)

(Radiative Boundary Conditions, P/THERMAL)

(Radiative Boundary Conditions, TRASYS)

(Radiative Boundary Conditions, NEVADA)

(Hydraulic Element Definitions)

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisTemplate File (TEMPLATEDAT)

686

MID TemplatesMID templates supply an intermediate “missing link” between Patran MID (material ID) numbers and QTRAN MPID (material property ID) numbers. Since Patran is based upon material numbers and QTRAN is based upon property numbers, and since it takes up to (6) property numbers to define a material for the solid part of the model (thermal conductivity in the local X', Y', and Z' directions, density, specific heat, and phase change data set), a way is needed to bridge this gap. The solution was to use an MID template. Build one MID template for each material in the model. The MID template consists of the characters “MID” and the template TID number followed by (6) MPID numbers. The MID number that is assigned on the Element Properties form refers to an MID template with the same TID number.

The linkage system between Patran MID numbers and QTRAN material property data is as follows:

1. Assign MID numbers to the model with the Patran Element Properties form.2. Build an MID template for each MID assigned to the model with Patran.3. PATQ uses the MID templates to get the MPID numbers for the conductive resistors and

capacitors that PATQ will generate for QTRAN. This is done when the Patran Neutral File is translated into VIEW FACTOR and QTRAN data files.

4. Build material property definitions. Each material property definition contains an MPID number as part of the definition.

5. When QTRAN is executed, QTRAN will read in the material property definitions.6. QTRAN will then match the material property definitions with the MPID numbers in the

conductive resistor and capacitor data files.

When PATQ is executed to translate the neutral file for the model, PATQ will read in the MID templates and use the MPID numbers for the QTRAN data whenever it encounters an MID number in the neutral file.

When QTRAN is executed and encounters the MPID numbers (and PHID numbers) in the resistor and capacitor data, it matches these MPID numbers (and PHID numbers) with material property definitions that have been supplied in a QTRAN input data file. These definitions are typically constants or data tables of property vs. temperature, but the specifications may be any QTRAN material property evaluation option. See Material Properties, 263.

For example, suppose 101 was entered in the material name data box on the Element Properties form. A MID template 101 must be built prior to translating the model’s neutral file. Suppose that material 101 uses mopeds 1, 2, 3, 4, and 5 for thermal conductivity in the local X', Y', Z' directions, density, and specific heat, respectively, and that it also will use phase change data set 121. The following MID template could be used for this material.

The lines beginning with a semicolon are comments and may be omitted.


Prior to executing QTRAN and running an analysis, material properties 1, 2, 3, 4, 5 and 121 must be defined. This is typically done in the $INSERT file MATDAT. $INSERT files are referenced by QTRAN input file(s) at execution time. See the introduction in Thermal/Hydraulic Input Deck (Ch. 8) for more information about the $INSERT command. This chapter also contains additional data about material property definitions.

If no phase changes are to be considered for a material, the PHID number for that material’s MID template should be given as a zero. If the material is isotropic (Kx = Ky = Kz), the same MPID number should be repeated three times for Kx, Ky, and Kz. For example, the following template specifies an isotropic material with no phase changes allowed.

MACRO TemplatesMACRO templates are used in conjunction with the Patran loads and boundary data to specify variable heat source, temperature, pressure or mass flow rate boundary conditions. To explain what a MACRO template is, it is required that you first understand the manner in which variable heat, temperature, mass flow or pressure boundary conditions are applied with QTRAN. See Boundary Conditions, 322 for more information.

Consider the following problem. You have a very complex time-dependent tabular heat source that you wish to apply to a number of nodes. But each node is to get this time-dependent heat source scaled by an equally complex temperature-dependent function, and further be scaled by the surface area associated with each node. One way not to approach this problem is to build separate data table functions for each node, especially if there are many nodes. Instead, it is more efficient to build the time-dependent data table once and the temperature-dependent function once and assign function IDs to the time-dependent and temperature-dependent functions. Let us call these little functions “microfunctions” since they will be the little building block functions that we will use to build a complete heat source (or temperature source). We will call the complete heat (or temperature) source a macrofunction (since it is made up of one or more microfunctions).


688

You could then assign a unique heat source to each node merely by referencing the microfunctions by their ID numbers (MFIDs) and using a scale factor to account for the surface area associated with each node. The scale factor could also account for any other constant scaling that must be performed (for example, units conversions).

MACRO templates are used to define QTRAN macrofunctions. Macrofunctions are used by QTRAN to specify heat source or temperature boundary conditions. See Heat Source/Sink Macrofunction Definition, 325 and Temperature Control Macrofunctions, 327 for more information about macrofunctions. The macrofunction templates consist of the following data:

1. MACRO keyword.2. Template ID number (TID).3. The number of microfunctions that will be used to build the macrofunction.4. Node numbers NODE1 and NODE2. NODE1 and NODE2 will be used as arguments for any

temperature dependent microfunctions.5. A scale factor for the macrofunction.6. A list of the ID numbers of the microfunctions that will be used to build the macrofunction

(MFIDs).

The scale factor that you use in the macrofunction template does NOT need to account for length, surface area, or volume scaling. Patran and PATQ automatically account for this part of the macrofunction scale factor. Instead the MACRO template scale factor is used as an additional constant scale factor to compute the final macrofunction scale factor.

For example, suppose that a node has a surface area of 1.12 associated with it and that a heat source macrofunction is being applied on a surface area basis. PATQ will take the surface area of 1.12 and multiply it by the MACRO template’s scale factor. This product will be used in the macrofunction that is assigned to this node by PATQ. Normally the MACRO scale factor is simply 1.0, but it may be any value that you choose.

The NODE1 and NODE2 node numbers (see Boundary Conditions, 322) may be 0 or any valid node number defined for your model. If either NODE1 or NODE2, or both NODE1 and NODE2, are entered as zero, PATQ will supply the node number that the function is being assigned to in place of the zeros.

An example MACRO template is as follows.


The lines beginning with semicolons are comments and are optional. This MACRO template has a TID of 7, the number of microfunctions used to define the macrofunctions will be 3 (MFIDs 1, 2024, and 18), NODE1 and NODE2 are given as 0 and 4157 (0 will be replaced by the node number to which the macrofunction(s) is assigned), and a template scale factor of 1.0 (which will be used in addition to any length-area-volume scale factors). The product of the macrofunction will be the output of microfunctions 1, 2024, and 18 and the resultant scale factor multiplied together.

Example

Suppose you wish to assign a distributed heat source boundary condition on a surface area basis to all elements along edge 1 of patch 4. You would click on Loads/BCs on the main menu bar and select Action: Create, Object: Heat Flux (pthermal), Type: Element Uniform or Element Variable. Select target element type as 2D, then click on the Input Data and enter 23.7 for heat flux, 7 for template ID. Then select edge 1 of patch 4 as application region and then click the apply button.

This command states MACRO template 7 will be used to build heat source macrofunctions on edge 1 of patch 4. It will use the product of the scale factor in MACRO template 7 multiplied by the surface area associated with each element and also multiplied by 23.7. This command is entered while still in Patran. After the model is completed and a Patran Neutral File has been completed, add a MACRO template with a TID of 7 to the TEMPLATE file. Let us assume the previous example template is used, but in a slightly more compact form without the optional comments. The template would look like this:

MACRO 73041571.012024 18

The next thing necessary to do is to define what microfunctions 1, 2024, and 18 are (see Microfunction Data, 322 and Microfunction Library, 440 for information about how to define microfunctions). After this step, the distributed heat source boundary conditions that were assigned in Patran Loads/BCs form have been completely defined. This is not particularly simple, but it is extremely versatile.

There are more examples of assigning MACRO boundary conditions in the Patran Thermal Tutorial, complete with Patran commands, session files, TEMPLATE data files, and MICROFUNCTION data files.

Variable temperature sources that are assigned use the same procedure, as do variable nodal heat sources.


690

CONV TemplatesConvective templates are used to specify variable convective boundary conditions. Remembering that all you specify with Patran is a TID number and possibly some constant (or spatially varying) data, a nonlinear convective analysis is obviously going to require more information such as material ID numbers (MPIDs) and geometric properties (GPs). The template corresponding to the TID number entered in Patran provides this information.

An example of a convective template is given below.

This convection template will be used by any Loads & Boundary Condition referencing TID number 1. It states that the convective boundary condition uses QTRAN configuration 13 convective resistors (natural convection from flat plates; see Reading Results (Ch. 6) which are for isothermal plates with natural convection. Configuration 13 resistors require a total of 5 GP values, and you will notice that only 2 are given in this template. This is because the Patran always supplies GP #1 (surface area) and will optionally supply GP #2 and GP #3 from the convection coefficient field of the convection loads and boundary conditions (both GP #2 and GP #3 receive the same Cdata value). This template therefore assumes GP #2 and GP #3 with the Cdata field will be provided, and the template then provides GP #4 and GP #5. For convective configuration 13 (natural convection from flat plates), the GP values are defined by QTRAN to be:

• GP #1 - The surface area associated with the node is always provided by Patran and PATQ.• GP #2 - A characteristic length of the plate (see Microfunction Library (Ch. 10)) (taken from the

convection coefficient value used in Patran convection loads and boundary conditions referencing this template).


• GP #3 - A second characteristic length (see Microfunction Library (Ch. 10)). This GP value is taken from the convection coefficient field used in the Patran convection loads and boundary conditions referencing this template. The GP #3 value provided by Patran and PATQ via the Cdata field of the Patran convection loads and boundary conditions will always be the same as the GP #2 value.

• GP #4 - Plate inclination angle in degrees. This value is given as 10.0 in the above template.• GP #5 - Local gravitational constant, given as 9.8 from the above template.

This CONV template also states that MPIDs 1041, 1042, 1043, 1000, and 1110 will be used for the convective resistors. Configuration 13 resistors require MPIDs for density, viscosity, coefficient of thermal expansion, specific heat, and thermal conductivity. As an example of convection loads and boundary conditions, enter 298.7 for convection coefficient, a convection template ID of 1 and fluid node ID of 1000 on the convection Loads/BCs form in Patran. Then select edge 2 of patch 1 as application region.

This command will assign convective resistors to edge 2 of patch1. GP #2 and GP #3 will be given values of 298.7, CONV template number 1 will be used, and the resistors will be connected between the surface nodes of edge 2 of patch 1 and bulk fluid node number 1000.

If no convection coefficient value had been given in Patran convection Loads/BCs form, the template would have had to provide GP #2 and GP #3 as well. The template would then have looked as follows:

Convection loads and boundary conditions data using this second template would be 1 for convection templateID, 1000 for fluid node ID and the convection coefficient data box left blank.


692

The first Loads & Boundary Condition and the first CONV template have exactly the same effect as the second Loads & Boundary Condition and the second CONV template. They are simply different ways of doing the same thing.

In many configurations, GP #2 and GP #3 refer to the shortest and longest distances to the leading edge of the convective boundary layer. This is obviously something that varies from element to element, and may be entered as a Patran data line or data patch. To provide the same data supplying GP #2 and GP #3 in the template, it would require one template per element. This is somewhat less than ideal. We have therefore provided the ability to assign spatially varying data for GP #2 and GP #3 from a Patran data entity such as a data line or data patch. This is available but not necessary. For many analyses, simply assume constant values of GP #2 and GP #3 and supply them from the template. There are also certain configurations that do not require spatially varying information and it is very convenient to simply include their GP #’s 2 & 3 directly in the template.

VFAC TemplatesRadiative templates are used to specify all radiation boundary conditions. In addition to the data supplied in the Patran View Factor Loads/BCs form (TID, MEDNOD, AMBNOD, CNVSID, NDB_Flags, and ENCL_ID), additional data is necessary for radiation analysis. Specifically, either constant or variable material property data is necessary for the emissivities and transmissivities (for either gray or wavelength-dependent models) as well as the manner in which the transmissivities (if any) are to be calculated. In addition, whether or not the model is gray or wavelength-dependent needs to be specified, and also, what are the wave band boundaries. This additional information is supplied using the VFAC templates.

The format for VFAC templates is given as follows. The square bracket nesting [ ] indicates successive levels of optional parameters.

The parameters for the VFAC template are listed below.


An example of an VFAC template is as follows:

TID REQUIRED: VFAC template ID number.Nbands OPTIONAL--DEFAULT = 0: number of wavelength bands associated with the

Radiative boundary condition. If Nbands = 0, the boundary condition is assumed to be gray. If Nbands is greater than 0, it will be assumed that there will be Nband sets of Ec/Tc/Empid/Lambda_1/Lambda_2/Kflag data lines following.

Eic REQUIRED: Constant emissivity value used for the (1-e)/(e*A) surface resistance Radiative resistors if Empid was entered as 0. If Empid is entered as 0 and Emissivity is given as 1.0, no (1-e)/(e*A) surface resistors are generated (the surface is assumed to be black).

Tc OPTIONAL--DEFAULT = 1.0: constant transmissivity value used for the 1/(F*A*tau) and 1/(F*A*(1-tau)) view factor resistors.

Empid OPTIONAL--DEFAULT = 0: emissivity MPID number (see Section 5.3 for MPID numbers). If Empid = 0, the emissivity will be taken from the constant value entered for Emissivity in the template.

Tmpid OPTIONAL--DEFAULT = 0: transmissivity MPID number (see Section 5.3 for MPID numbers). If Tmpid = 0, the transmissivity data will be taken from the constant value entered for Transmissivity in the template.

Lambda-1 OPTIONAL--DEFAULT = 0.0: shortest wavelength associated with the current wave band being described, if and only if Nbands > 0.

Lambda-2 OPTIONAL--DEFAULT = 0.0: longest wavelength associated with the current wave band being described, if and only if Nbands > 0.

Kflag OPTIONAL -- DEFAULT = 0, where:

0 -->The transmissivity for the view factor resistors will be calculated directly from the material property referenced by the number or from the constant transmissivity value (given in the below template as 0.915) if the number is 0.

1 -->The transmissivity for the view factor resistors will be calculated using either the material property referenced by the number or the constant transmissivity value as an extinction coefficient coupled with the view factor distance.

Collapse OPTIONAL--DEFAULT = 0, where:

0 -->Do not collapse radiosity nodes associated with a given surface node.

>0 -->Collapse radiosity nodes with the same collapse field value. This is a feature to reduce the size of the radiation network.


694

This template will be used by Patran View Factor Loads/BCs form referencing VFAC template number 1. It declares that the radiative boundary condition is gray (Nbands = 0), that the transmissivity of the view factor resistors will be calculated from an extinction coefficient (Kflag = 1) and that the extinction coefficient is a constant of 0.915, and that the emissivity of the surface resistors will be taken from material property MPID 9275609. The collapse value of 5 will be used as an ID to flag radiosity nodes which can be collapsed to a single radiosity node associated with a surface node.

VFAC template 2 above defines a gray surface (Nbands = 0) using variable material properties for emissivity (MPID 7) and transmissivity (MPID 23). The transmissivity will be calculated using MPID 23 as an extinction coefficient (Kflag = 1) along with the view factor distance.


VFAC template 3 above assigns a gray radiative boundary condition with a constant emissivity of 0.95 and a constant transmissivity of 1.00. No 1/(F*A*(1- τ)) resistors will be generated from this template.

Radiative template 4 above assigns a black radiation boundary condition with a constant transmissivity value of 1.0. No 1/(F*A*(1-τ)) resistors will be generated by this template.


696

VFAC template 5 above defines 3 wave bands: 0.0-1.7, 1.7-5.2, and 9.9-1.0E+10 microns. Wave band #1 uses MPID 7 as the emissivity material property, and MPID 9 as the extinction coefficient. Wave band #2 uses 1.0 as the emissivity (black surface, no (1-e)/(e*A) resistors generated for this wave band) and 0.915 as a constant extinction coefficient. Wave band #3 uses MPID 19 for emissivity and a constant 1.0 for the transmissivity (no 1/(F*A*(1-τ)) resistors generated for this wave band). Note that this template does not define any wave bands between 5.2 and 9.9 microns. Presumably, this surface either does not radiate in this wave band, or else the surface will have a view factor boundary condition, using at least one other template to define the radiative boundary conditions within the 5.2-9.9 micron band. Normally, an analysis will require one template for the entire spectrum, but cases do arise (e.g., greenhouse effects) where the problem may need to be defined a little more creatively. Patran Thermal gives you great flexibility.

VTRA TemplatesThis template defines the surface properties required by TRASYS. The radiation boundary condition is specified the same as boundary conditions are defined for P/THERMAL and P/VIEWFACTOR. The


surface properties are treated as constant in two different wavelength bands. One, the solar region which is from 0 to a cutoff wavelength define in the TRASYS input and the IR region which is everything from the cutoff wavelength to infinity.

The format for VTRA templates is given as follows. The square bracket nesting [] indicates successive levels of optional parameters.

The parameters for the VTRA template are listed below.

An example of a VTRA template is as follows:

This template defines 0.2 as the surface absorptivity for diffuse surfaces with incident solar radiation and 70 percent of the solar energy will be transmitted through the material. If a specular analysis is performed, the surface reflectivity will be 0.1. Corresponding values for the IR waveband are a surface emissivity of

TID REQUIRED: VTRA template ID number.

Alpha Solar Absorptivity of surface

Emiss IR Emissivity of surface

Trans Solar Transmissivity of surface material

Trani IR Transmissivity of surface material

sprs Solar Specular reflectivity of surface

spri IR Specular reflectivity of surface


698

0.8, and opaque surface (transmissivity = 0.0) and if a specular surface is define the reflectivity will be 0.2. In this case, the reflectivity would be the same for both a diffuse or specular surface.

VNEV TemplatesThis template defines the surface properties required by NEVADA. The radiation boundary condition is specified the same as boundary conditions are defined for P/THERMAL and P/VIEWFACTOR. The surface properties are treated as constant in two different wavelength bands. One, the solar region which is from 0 to a cutoff wavelength define in the NEVADA input and the IR region which is everything from the cutoff wavelength to infinity.

The format for VNEV templates is given as follows. The square bracket nesting [] indicates successive levels of optional parameters.

The parameters for the VNEV template are listed below.


An example of a VNEV template is as follows:

As with the TRASYS input, this template defines 0.2 as the surface absorptivity for diffuse surfaces with incident solar radiation and 70 percent of the solar energy will be transmitted through the material. If a specular analysis is performed, the surface reflectivity will be 0.1. Corresponding values for the IR waveband are a surface emissivity of 0.8, and opaque surface ( transmissivity = 0.0 ) and if a specular surface is define the reflectivity will be 0.2. In this case, the reflectivity would be the same for both a diffuse or specular surface. NEVADA actually calculates the absorptivity and emissivity from the transmissivity and reflectivity data if they are variable. The reflectivity can be calculated from the specified index of refraction. Currently, if variable reflectivity is to be specified ( a function of incident angle ), the user will have to edit the NEVADA input file. Variable fields are not defined and translated.

TID REQUIRED: VNEV template ID number.

Alpha Solar Absorptivity of surface

Emiss IR Emissivity of surface

Trans Solar Transmissivity of surface material

Trani IR Transmissivity of surface material

sprs Solar Specular reflectivity of surface

spri IR Specular reflectivity of surface

iors Solar index of refraction of surface

iori IR index of refraction of surface


700

FLUID TemplatesFluid templates are used to specify all geometric and material property data necessary to evaluate the variable hydraulic elements. Different fluid element options have different template formats and those fluid options that have all constant properties do not require a fluid template.

The general format of the Fluid template is the FLUID keyword, the template ID, TID number of material properties specified, and the option flag followed by the number of records necessary to indicate all of the material properties desired. The template requirements are defined in Getting Started (Ch. 2).

Below are some examples which show the input for various fluid templates.


702


Example Template FileThe following file is an example of what a complete TEMPLATE file might look like.


704


706

707Appendix C: PATQ Preference ProgramPATQ Limitations

PATQ LimitationsThis subsection contains a brief description of certain limitations that exist in the PATQ program (e.g., maximum number of MID templates, etc.). Although it has been the author's philosophy to avoid coding in such limitations (especially in QTRAN, where there are virtually NO coded limitations visible to the user), expediency has caused a few such limitations to find their way into PATQ for the time being.

These limitations are as follows. First, MID templates may not have a TID number greater than 1000000 (remember also that all TID numbers must be greater than 0). MACRO templates TID number may not be greater than 1000000. The total number of Microfunctions referenced by the MACRO templates must not exceed 1000000. The maximum CONV template TID number may not exceed 1000000. The maximum count of CONV template MPID values and GP values may not exceed 1000000. These limitations are presented in a brief form below..

In general, the maximum values are high enough that they are unlikely to cause anyone serious problems, but keep these limits in mind when building the thermal model.

Maximum MID Template TID Number 1,000,000 Maximum MACRO Template TID Number 1,000,000Maximum number of Microfunctions 1,000,000Maximum CONV Template TID Number 1,000,000Maximum number of MPID + GP Values 1,000,000

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisPatran Thermal Execution

708

Patran Thermal ExecutionThis section outlines the steps necessary to execute the Patran Thermal analysis code package. Briefly, the steps necessary are as follows:

1. Build the model using Patran, if operating QTRAN in Finite Element mode. Build the model and apply boundary conditions from Patran.

2. Build or modify a TEMPLATEDAT file suitable for the problem. This file contains templates for the Material ID numbers (MIDs) assigned in Patran Plus as well as templates for the Template ID (TID) boundary condition codes assigned in Patran. The TEMPLATEDAT file can be thought of as a pointered list architecture. Since Patran Thermal requires a great deal of data for boundary conditions (which is typical of nonlinear codes), it is convenient to build a library of these boundary condition data sets and store them in the TEMPLATEDAT file. These boundary condition data sets are then referenced by a TID from Patran. For example, a time and temperature-dependent heat source may be applied to a portion of your mesh from Patran Plus merely by assigning a heat source TID to that part of the mesh. This TID points to a MACROfunction TID data set in the TEMPLATEDAT file. More than one mesh portion may use the same TEMPLATEDAT TID data set if needed. TID data sets supported by the TEMPLATEDAT file include Material ID sets (MID), MACROfunction sets (MACRO), convective data sets (CONV) hydraulic network data sets (FLUID), and radiation data sets (VFAC). The TEMPLATEDAT file for the problem MUST exist prior to executing the PATQ translator program.

3. Execute the PATQ program to translate the Patran Plus neutral file data and the TEMPLATEDAT file data into QTRAN input data file segments and into an input file for the radiation view factor code (VIEW FACTOR) if required. During this translation phase, PATQ takes the Patran Plus finite element data and boundary condition data and translates it into a mathematically exact resistor/capacitor network model.

4. If the problem involves the calculation of thermal radiation view factors, execute VIEW FACTOR now. It will read the VFINDAT file generated by PATQ and will generate a QTRAN input data file segment named VFRESDAT for radiative resistors.

5. Create (or edit an existing) QINDAT file. QINDAT is the QTRAN input data file. QINDAT contains a number of run control parameters and other data necessary for QTRAN to execute. It will normally contain a number of “$INSERT” filename commands. The $INSERT commands cause the referenced file name to be inserted by QTRAN into the input data stream as QTRAN executes. This keeps the QINDAT file rather small and reference the larger PATQ output files with $INSERT commands. In addition to the PATQ output files, maintain the additional

Note: The conductive resistors coming from PATQ are mathematical in nature and have no physical basis (e.g., negative A/L ratios are not uncommon). Do not be alarmed. They are necessary for the mathematical exactness of the translation.

709Appendix C: PATQ Preference ProgramPatran Thermal Execution

$INSERT files (e.g., a MATDAT file for material property data and a MICRODAT file for QTRAN microfunction data). It should be noted that QTRAN will honor ANY file name included as a $INSERT file. There is nothing special to QTRAN about the PATQ output files. This allows customized data files to be built for the particular applications.

6. Now the QINDAT file has been constructed or modified for the problem. This includes the $INSERT commands necessary for any PATQ output files being used by the model as well as any other data such as material properties, microfunction data, and the VIEW FACTOR VFRESDAT file. Execute PATQ again. This time, select the menu option that will build a new QTRAN main module. What PATQ does is read the QINDAT file that will be run through QTRAN and counts up how large the array dimensions for QTRAN need to be. When the counting process is finished, PATQ then writes out about 300 lines of Fortran into a file called QTRANFOR. QTRANFOR is the QTRAN main module and consists of very little other than dimension statements and a call to subroutine CRUNCH.

7. Now that QTRANFOR exists, compile it and link it to the QTRAN library. The results are in an executable image of QTRAN that is optimally dimensioned for the problem. If using any user-supplied subroutines, these subroutines must be included in the linking process. The exact procedure will be installation-dependent. The user has the ability to execute a predimensioned, predefined QTRAN executable which is in the thermal library with the name qtran_lib.exe. Even if you are executing the predefined executable the step that create the QTRANFOR file should still be performed as this step also loads any undefined material properties from the library.

8. Execute QTRAN. QTRAN will read in the QINDAT file and will generate the output files STATBIN and QOUTDAT, as well as one or more Patran nodal results files named NRnnnNRF (where nnn is an integer number corresponding to each QTRAN print dump). STATBIN is a status file to which QTRAN continuously writes. QOUTDAT is the results output file for the QTRAN run. QINDAT and QOUTDAT are text files. STATBIN is a binary direct access file that can be queried by using the QSTAT utility provided with Patran Thermal. NRnnnNRF files are standard Patran nodal results files containing temperature data as well as the net nodal heat flow rate and the explicit stable time step for each node. The NRnnnNRF files can be read directly by Patran, and they can also be used as restart files for QTRAN. PATQ can also convert the NRnnnNRF files to a Patran neutral file format for use as thermal load conditions for structural codes.Steps 3 through 8 can be performed in Patran under the Analysis menu.The qtran_lib.exe file in the p3thermal_files/lib directory can be replace with one tailored to one’s specific needs. If the problem being executed terminates with errors associated with the problem dimensions simply follow the normal run procedures in which the qtran.f file is compiled, linked and run. The qtran.f file can be altered to better suit a users normal run environment or can be linked with a users specific user library to a special executable. To have this new executable be the standard executed when the direct execution option is flagged, simply replace the qtran_lib.exe with the new qtran.exe created changing its name to qtran_lib.exe.Execute Patran, and read the NRnnnNRF files and display the results of the analysis.


710

PATQ FilesThe files used by PATQ are as follows.

PATQ Input FilesA Patran Plus neutral file is read by PATQ and translated into QTRAN and VIEW FACTOR input data file segments. The TEMPLATEDAT file must exist prior to the translation process.


QINDAT This file is read by both PATQ and QTRAN. PATQ takes the QINDAT file and generates a new QTRAN main program module named QTRANFOR.

QOUTDAT This file is generated by QTRAN and is read by PATQ. PATQ takes the QOUTDAT file and (a) generates Patran nodal results files, (b) generates Patran neutral file segments, or (c) generates time-temperature print-plots.

QPLOTDAT This file is generated by QTRAN and may be read by PATQ. PATQ takes the QPLOTDAT file and converts it from binary to an ASCII file.

NRnnnNRF These files are standard Patran nodal results files generated by QTRAN. One NRnnnNRF file is generated for each QTRAN print dump. PATQ can process these files and convert them to NFnnnDAT files (standard Patran neutral files) which can be used to apply thermal load conditions to structural models. PATQ can also read a sequence of NRnnnNRF files and generate Patran X-Y plot files, thereby allowing you to use Patran’s X-Y plot utility to display temperature histories. Finally, PATQ also reads one or more NRnnnNRF files when it is performing a temperature interpolation from a thermal mesh to a dissimilar structural mesh.


* These values are not put in the nodal results file if it is created from a QOUTDAT file.

TEMPLATEDAT

This file is read by PATQ and contains material property ID numbers along with boundary condition template data.

Column Value1

2

3

4*

5*

6*

7*

8*

Temperature









712

THERMAL$DIR:[LIBRARY]TEMPLATEBINThis file is read by PATQ and contains the default MID templates for the material property database.

THERMAL$DIR:[LIBRARY]TEMPLATETXTThis file can be read by PATQ and converted to TEMPLATEBIN. The TEMPLATETXT file is text and can by modified by your system manager using a text editor.

THERMAL$DIR:[LIBRARY]MPIDMKS,

THERMAL$DIR:[LIBRARY]MPIDIPS,

THERMAL$DIR:[LIBRARY]MPIDFPH, and

THERMAL$DIR:[LIBRARY]MPIDCGSThese files are material property database files which can be read by PATQ when generating a new QTRANFOR file. These text files can be modified with your system editor. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively. These files are material property database files which can be read by PATQ when generating a new QTRANFOR file. These text files can be modified with your system editor. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.

THERMAL$DIR:[LIBRARY]MPIDMKSBIN,

THERMAL$DIR:[LIBRARY]MPIDIPSBIN,

THERMAL$DIR:[LIBRARY]MPIDFPHBIN, and

THERMAL$DIR:[LIBRARY]MPIDCGSBINThese files are material property database binary files which can be read by PATQ when generating a new QTRANFOR files. These files can be created by executing PATQ utility menu pick 2. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.

OLDMATDAT This file is read by PATQ and contains material property data to be translated to LCI type material property tables.

PATQINP This file is an input file that contains all the responses to the PATQ menu request. This file is required when batch submittals are executed with the PATQB or OTRANB commands.


PATQ Output Files

PATQMSG This file is a message file that contains all output written to the screen and the users response. This is a standard ASCII text file that is a record of a PATQ session.

PATQSES This file is a standard ASCII text file that contains the responses of all user request mode by PATQ. This file can be renamed to PATQINP and used for input to future PATQ batch executions. The responses, if different from those used during the creation, would be edited to reflect new desired responses.

QTRANFOR This file is generated by PATQ from a complete QINDAT file. QTRANFOR is the main program module for QTRAN. QTRANFOR must be compiled and linked with the QTRAN library to generate a new executable QTRAN for each problem.

THERMAL$DIR:[LIBRARY]MPIDMKSBIN,

THERMAL$DIR:[LIBRARY]MPIDIPSBIN,

THERMAL$DIR:[LIBRARY]MPIDFPHBIN, and

THERMAL$DIR:[LIBRARY]MPIDCGSBINThese files are material property database binary files which can be generated by PATQ utility menu pick 2. They contain the Patran Thermal material property definitions in units of meters-kilograms-seconds, inch-lbms-seconds, foot-lbms-hours, and centimeters-grams-seconds, respectively.

QPLOTTXT This file is generated by PATQ from the QPLOTDAT file created by QTRAN and converts it from binary to an ASCII file.


714

NRnnnNRF These files can be generated by PATQ from a QTRAN QOUTDAT output file. One NRnnnNRF file is generated for each print dump. Normally, this does not have to be done because QTRAN generates these files automatically.


* These columns are not generated from QOUTDAT files using PATQ menu pick 5.

NFnnnNEU These files are the Patran neutral files generated by PATQ from a QTRAN QOUTDAT output file, from QTRAN NRnnnNRF nodal results files, or from a temperature interpolation operation.

TITLEDAT This file provide information about when and what versions of code were used to generate the input file being executed. In addition it contains a user defined description of the job.

PNODEDAT This file is generated when a neutral file is translated. It is an ASCII file and contains flow network node definition data (DEFPND cards).

NODEDAT This file is generated when a neutral file is translated. It is an ASCII file and contains the node definition data (DEFNOD cards).

NODXYZDAT This file is generated when a neutral file is translated. It is an ASCII file and contains the node location data cards in cartesian coordinates.

MATDAT PATQ will generate material properties if the material property selected does not exist in the mat.dat file and is in the supplied P/THERMAL database. This file can also be created by direct translation if material properties are specified by the fields function in the Patran model. A mat.dat.apnd file in the model directory will be appended to the mat.dat file in all subdirectories which are spawned from Patran.

Column Value1

2

3

4*

5*

6*

7*

8*

Temperature









CONDUCDAT This file is generated when a neutral file is translated. It contains the conductive resistor data. This is a binary file. When used with the $INSERT command, the file name should be followed with a “,C” to tell QTRAN that this is a binary conductive resistor data file. For example:

“$INSERT CONDUCDAT,C”FRESDAT This file is generated when neutral file is translated. It is an ASCII file and contains

the flow network resistor data.CONVECDAT This file is generated when a neutral file is translated. It is an ASCII file and

contains the convective resistor data.TRARSTDAT An ASCII radiation interchange file created by the reverse translation of a

TRASYS analysis.NEVRST.DAT An ASCII radiation interchange file created by the reverse translation of a

NEVADA analysis.RESDAT This file is generated when a neutral file is translated. It is an ASCII file and

contains miscellaneous resistor data, including advective resistor data.CAPDAT This file is generated when a neutral file is translated. It contains the capacitor data.

This is a binary file. When used with the $INSERT command, the file name should be followed with a “,CAP” to tell QTRAN that this is a binary capacitor data file. For example:

“$INSERT CAP.DAT,CAP”TRAMICDAT Micro function tables to define the periodic heating on surfaces exposed to solar

radiation. This is created by the reverse translation of a TRASYS orbital analysis.NEVMICDAT Micro function tables to define the periodic heating on surfaces exposed to solar

radiation. This is created by the reverse translation of a NEVADA orbital analysis.QMCROD AT This file is generated when a neutral file is translated. It is an ASCII file and

contains the QMACRO function heat source data.TRAQMADAT This is an ASCII file created by the reverse translation of a TRASYS analysis and

relates the micro function data to the QMACRO function heating definition for each surface that receives solar radiation during an orbital flight.

NEVQMADAT This is an ASCII file created by the reverse translation of a TRASYS analysis and relates the micro function data to the QMACRO function heating definition for each surface that receives solar radiation during an orbital flight.

TMACROD AT This file is generated when a neutral file is translated. It is an ASCII file and contains the TMACRO function temperature boundary condition data.

MMACRODAT

This file is generated when a neutral file is translated. It is an ASCII file and contains MMACRO function mass flow rate boundary condition data.

PMACRODAT This file is generated when a neutral file is translated. It is an ASCII file and contains PMACRO function pressure boundary condition data.


716

TFIXDAT This file is generated when a neutral file is translated. It is an ASCII file and contains the node numbers of the fixed nodes.

PFIXDAT This file is generated when a neutral file is translated. It is an ASCII file and contains the nodes numbers for which pressure is fixed.

TEMPDAT This file is generated when a neutral file is translated. It is an ASCII file and contains the initial temperatures of nodes whose temperatures were assigned with Patran Loads & Boundary Conditions.

PRESSDAT This file is generated when a neutral file is translated. It is an ASCII file and contains initial pressures of nodes whose pressures were assigned with Patran Loads & Boundary Conditions.

QBASEDAT This file is generated when a neutral file is translated. It is an ASCII file and contains the constant heat source data for nodes assigned constant heat sources with the Patran Loads & Boundary conditions.

TRQBASDAT Average heat sources over an orbit defined from the reverse translation of a TRASYS analysis. This file should not be included if the periodic heating is defined.

NEVBASDAT Average heat sources over an orbit defined from the reverse translation of a NEVADA analysis. This file should not be included if the periodic heating is defined.

MDBASEDAT This file is generated when a neutral file is translated. It is an ASCII file and contains the constant mass flow rate data for nodes assigned a constant mass flow rate with Patran Loads & Boundary Conditions.

NEWMATDAT This file is created by PATQ with utility menu pick 11 and contains material property data that has been translated to LCI type material property tables.

TEMPLATEDAT

The template.dat file will be created if materials are defined which are in the P/THERMAL material database but were not defined in the template.dat file. If direct translation is specified and a template.dat.apnd file is supplied in the model create directory, it will be added to the template.dat file when the job is executed.


Files Written by Direct Translation

Files Created by the Userr

TCOUPLDAT This file is generated by direct translation in Patran when temperature coupling boundary conditions have been specified. It contains a node ID and the companion node which is to be used as internal calculation node IDs.

MATDAT This file is generated by direct translation in Patran when P/THERMAL material properties have been specified in the general fields. A mat.dat.apnd file in the model creation directory will be appended to any material properties specified in the model.

TEMPLATEDAT This file is generated by direct translation in Patran when P/THERMAL material translation has been selected. A template.dat.apnd file in the model creation directory will be appended to any material definitions specified in the model.

MICRODAT This file is generated by direct translation in Patran when P/THERMAL microfunctions have been specified in the general fields. A micro.dat.apnd file in the model creation directory will be appended to any micro functions specified in the model.

GAP_CONVECDAT This file is generated by direct translation in Patran when gap convection or convection between regions is the requested option for the convective boundary condition.

GAP_RADDAT This file is generated by direct translation in Patran when gap radiation or radiation between regions is the requested option for the radiation boundary condition.

../CONVECDATAPND This file is created by the user and can be used to define any type of conductor that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be pulled into any QTRAN execution that is in a subdirectory associated with the model.

../CAPDATAPND This file is created by the user and can be used to define capacitors that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be pulled into any QTRAN execution that is in a subdirectory associated with the model.

../MATDATAPND This file is created by the user and can be used to define material properties that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any mat.dat file that is created while the job is being spawn for execution.


718

VIEW FACTOR Files

QTRAN Files

../TEMPLATEDATAPND This file is created by the user and can be used to define materials and their associated material properties that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any template.dat file that is created while the job is being spawn for execution.

../MICRODATAPND This file is created by the user and can be used to define micro functions that the user wants added to any jobs submitted from the Patran model. This file is placed in the directory in which the model is created and will be appended to any micro.dat file that is created while the job is being spawn for execution.

VFINDAT This file is the main input data file for VIEW FACTOR. It is generated by PATQ from a Patran neutral file. It is a text file.

VFNODEDAT

This file is a VIEW FACTOR output file that contains radiosity nodes generated by VIEW FACTOR. It is a text file.

VFRESDAT This file is the main VIEW FACTOR output file and contains all of the radiative resistor data generated by VIEW FACTOR for QTRAN. VIEW FACTOR allows this file to be named anything but for now we shall call it VFRESDAT. This file is binary, but may be converted to text by PATQ if desired. The “,RAD” tells QTRAN that this is a binary file and must be used with the $INSERT command. For example:

“$INSERT VFRESDAT,RAD”

QINDAT This file is the input data file for QTRAN. QTRAN will honor the command “$INSERT filename” whenever it is encountered in the QINDAT file. QTRAN will also honor a “$RESTART filename next_nnn_value” command, where filename refers to a QTRAN nodal results file (i.e., one of the NRnnnNRF files). This is a text file.

QOUTDAT This file is the output data file generated by QTRAN. This is a text file. For further information see System Energy Balance, 221.

QPLOTDAT This file is the output data file generated by QTRAN. This is a binary file which contains specified node temperatures at each converged iteration.

STATBIN This file is the status file generated by QTRAN. STATBIN is continually updated by QTRAN during execution. This is a binary direct access file that may be accessed with the QSTAT utility.


NRnnnNRF These files are the Patran nodal results files that QTRAN generates. One NRnnnNRF file is generated for each QTRAN print dump, beginning with NR0DAT and incrementing the “nnn” with each successive print dump. These files may also be used as restart files for QTRAN. These are binary files in standard Patran nodal results file format.

NRnnnASC These files are the Patran nodal results files that QTRAN generates if the ASCII flag is selected. One NRnnnASC file is generated for each QTRAN print dump, beginning with NR0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.

NPnnnNRF These files are the Patran pressure nodal results files that QTRAN generates for the hydraulic nodes. Two values can be put in this file - pressure and net mass flow rate. One NPnnnNRF file is generated for each QTRAN print dump, beginning with NP0NRF and incrementing the “nnn” with each successive print dump. These are binary files in standard Patran nodal results file format.

NPnnnASC These files are the Patran pressure nodal results files that QTRAN generates for the hydraulic nodes. Two values can be put in this file - pressure and net mass flow rate. One NPnnnASC file is generated for each QTRAN print dump, beginning with NP0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.

NHnnnNRF These files are the Patran hydraulic element files that QTRAN generates for the hydraulic network. Four values can be put in this file which represent elemental quantities - mass flow rate, differential head, fluid velocity, and volumetric flow rate. In addition to the selected values, the entrance and exit node number of the element is specified. One NHnnnNRF file is generated for each QTRAN print dump, beginning with NH0NRF and incrementing the “nnn” with each successive print dump. These are binary files in standard Patran nodal results file format.

NHnnnASC These files are the Patran hydraulic element nodal results files that QTRAN generates for the hydraulic nodes. Four values can be put in this file which represent elemental quantities - mass flow rate, differential head, fluid velocity, and volumetric flow rate. In addition to the selected values, the entrance and exit node number of the element is specified. One NHnnnASC file is generated for each QTRAN print dump, beginning with NH0ASC and incrementing the “nnn” with each successive print dump. These are text files in standard Patran nodal results file format and can be examined with the editor.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisTranslation of Patran Thermal Input to SINDA

720

Translation of Patran Thermal Input to SINDA

Introduction to the SINDA Utility from Patran ThermalWhen all of the Patran Thermal files (TEMPLATEDAT, MATDAT, CONDUCDAT, CONVECDAT, etc.) have been created, there are two possibilities for performing the analysis. The first option is to submit the job to Patran Thermal’s solver QTRAN. This solver has many advanced features such as adaptive time stepping with a continually updated weighting factor to vary the implicitness or explicitness of the transient analysis. The second option is to create a run-ready SINDA input file and submit the job for SINDA analysis. (The SINDA solver is not supplied by MSc.Software Corporation).

SINDA has been an industry standard for thermal analysis since the 1960s (as CINDA) and is still widely used.

The SINDA utility is designed to create input files for either a SINDA 85 code (which contains blocks of the format “HEADER NODE DATA”) or Network Analysis SINDA (also called SINDA/G with blocks of the format BCD 3NODE “DATA”). There are a wide variety of “BCD” versions of SINDA, such as CINDA, which have only minor input differences.

Some of the unique benefits of the SINDA input file created by Patran Thermal are as follows:

1. Radiation view factors are calculated as an integral part of the Patran Thermal program and are directly accessed by the SINDA utility. Typically, a conduction/convection model for SINDA is created and a separate radiation model is built for an external code (such as TRASYS, or NEVADA) which is run to calculate the radiation view factors. The results of this radiation analysis are cut and pasted into the conduction/convection SINDA input file and is often lengthy and cumbersome. This process is significantly streamlined by having all boundary conditions (including radiation) in one Patran model.

2. The SINDA input file is a mathematically exact representation of the finite element model and is converted into a “Resistor-Capacitor” network. Accuracy is significantly increased in the portion of a model where elements are not orthogonal (even slightly skewed elements).

3. Any of the 971 materials defined in the Patran Thermal material library (each contains thermal conductivity, specific heat, and density) can be automatically input into the SINDA file. All temperature dependent material properties are mapped directly into ARRAY DATA.

4. A subroutine is automatically included at the bottom of each newly created SINDA input file which allows SINDA to directly write Patran nodal results files for postprocessing. This eliminates the need for a reverse translator from SINDA to Patran.

5. All of the conductors for conduction, convection, advection (mass flow), and radiation are grouped separately for easy modification of their values with a “FAC” card.

Creating the SINDA Input FileAt this point, the Patran model is completed and a neutral file exists. To create the SINDA input file, enter Patran Thermal by executing PATQ (or PTHERMAL). The PATQ menu picks, shown below, have been

721Appendix C: PATQ Preference ProgramTranslation of Patran Thermal Input to SINDA

described earlier in Chapter 3. The following describes how these picks relate to SINDA input file creation. Upon entering PATQ, the following menu will appear.

Table C-7 PATQ Menu

Table C-8 PATQ Utilities Menu

Select 2) and Patran Thermal reads the default TEMPLATE.BIN file in Patran Thermals root directory, as well as a local TEMPLATE.DAT file which may exist in the current directory. All the Patran Thermal files (TEMPDAT, CONDUCDAT, etc.) will be created in the local directory.

Select 3) only if VFAC boundary conditions were created for radiation in Patran. This will execute VIEW FACTOR in batch mode and create a VFRESDAT file that will be read later to create radiation resistors in the SINDA input format.

Select 4) if material properties (k, rho, or Cp) need to be automatically read from the Patran Thermal material library and inserted into the local MATDAT file. Otherwise this selection can be skipped.

Select 6) to access the utility menu which is also described in detail in section 3.2.2. The utility menu is where the actual translation to SINDA input occurs and is displayed on the next page.


722

The first file read is the QINDAT file located in the local directory. The local directory is again searched for a file called APPENDSIN This file contains parameters that affect the way the SINDA input file will be created and also contains logic blocks and a subroutine that allows SINDA to write Patran nodal results files. The Fortran files are appended to the bottom of the SINDA input file which is called MODELSIN. The APPENDSIN file is discussed in detail in The APPENDSIN File, 746. If this file does not exist, then the user is prompted as to which type of SINDA file to create:

Table C-9 SINDA Execution Format Options

After the user selects either “1” or “2”, the default APPENDSIN file will be written to the local directory for future customization of SINDA files.

Select 15) to create the SINDA input deck from existing Patran Thermal files created in the previous steps.

Note: It is recommended that all APPENDSIN files be deleted from the local directory before re-executing the SINDA utility if the run is being changed from steady-state to transient (or vice versa) or if the requested deck is being changed from SINDA85 to Network Analysis SINDA (or vice versa).


The SINDA utility then proceeds to read MSC Patran Thermal files and creates the appropriate SINDA input file. The following table shows a sample execution which indicates the files that are read from the local directory and then displays a summary of the total number of nodes and conductors created.

Table C-10 Sample Run Log of SINDA Translation


724


726

The number of conductors created for the SINDA file might be less than the number of conductors created by Patran Thermal. This is done because Patran Thermal creates conductors between boundary nodes in case the desired classification needs to be changed to a nonboundary node during a transient.

If any errors occurred (such as modeling functionality) that SINDA does not support (such as wavelength-dependent radiation), an error message will be displayed underneath the line that displays which file is currently being read. All these messages are included in the PATQMSG message file.


The MODELSIN FileThe resulting input file created by the SINDA utility is called MODELSIN. A sample of this file is shown below:

Table C-11 Sample SINDA Input File


728


730


732


734


736


738


740


742

To understand how the Patran Thermal parameters are translated to SINDA, Table C-12 describes the supported Patran Thermal to SINDA functionality. This table describes how a particular capability is implemented for a particular function. Much of this information will become clear after translating sample problem 1 for basic functionality and problem 10 which uses some of the more advanced functionality with variable heat loads and convection coefficients.

Table C-12 Supported SINDA Translation

Patran Thermal to SINDA Functionality Functionality Capability ImplementationNode Data Constant rho or Cp MPIDs in MATDAT have IEVAL =

“CONST”.Constant rho, variable Cp

MPIDs in MATDAT have IEVAL = “CT” and “TABLE” or “ITABLE”.

Constant Cp, variable rho

MPIDs in MATDAT have IEVAL = “C” and “TABLE” or “ITABLE”.

Both rho & Cp variable MPIDs in MATDAT have IEVAL “TABLE” or “ITABLE”.

Both rho & Cp are massless Advective, ambient, radiosity nodes, etc.Node has a fixed temp TEMP LBC as fixed.

Conduction Constant Conductivity MPID in MATDAT have IEVAL = “C”.Temperature Variable MPIDs in MATDAT have IEVAL

“TABLE” or “ITABLE”


Time Variable MPIDS in MATDAT have IEVAL = “TABLE” or “IT” and ITSCAL=”T” in MATDAT.

Convection Constant “h” CONV LBC with an “h” valueSpatial Variation Use of a fieldTemp Variation Conv Configuration 29 and ITSCAL=F,

R, C, or K.Time Variation Conv Configuration 29 and ITSCAL=T

or MPID is “-”Radiation Gray with fixed emissivity VFAC has constant emissivity in

TEMPLATE.DAT.Advection Flowrate Cp

constant constant PFEG has fixed Mdot and MPID in MATDAT is constant.

time var constant ITSCAL in MATDAT is “T” for time. temp var constant ITSCAL in MATDAT is F, R, C, or K.constant time var ITSCAL in MATDAT is “T” for time. time var time var ITSCALs are “T” for time for both Mdot

and Cp.temp var time var ITSCAL is “T” for time for Cp.constant temp var ITSCAL in MATDAT is F,R,C, or K.time var temp var ITSCAL in MATDAT is “T” for time for

Mdot.temp var temp var ITSCALs in MATDAT are

F, R, C, or K.Heat Source Constant Q HEAT LBC a fixed value or a function of

Length, Area, or Volume.temp variable QMACRO function (must be with one

micro 8 and with arg=1).time variable QMACRO function (must be with one

micro 8 and with arg.=0).Run Control TMPZRO Calculated from ICCALC from

QINDAT.Steady State or Transient IOPT from QINDAT.NLOOP IMAXSS for steady state, 50 for

transient.TSTART TSTART from QINDAT.


744

TIMEND TSTOP from QINDAT.DRLXCA, ARLXCA EPSISS for Steady State and EPSIT for

Transient.DAMPD,DAMPA RELAXS for steady state RELAXT for

transients.

If IFXRLX is 1, then the smallest of the individual

RLX options will be used as the DAMPX factor.

SIGMA This will be put directly into CONDUCTOR DATA.

If SBC is “0” and ICCALC is C or K, then SBC=5.6698E-8.

If SBC is “0” and ICCALC is F or R, then SBC=0.1712e-8.

Otherwise, SBC is read directly from QINDAT.

OUTPUT TPRINT from QINDAT.Initial Temperatures TINITL is read for initial temps in

QINDAT but is overwritten by TEMP LBCs in Patran.

Materials Constant ITSCAL=”C” in MATDAT. Lumped into capacitors and conductors.

ARRAY DATA ITSCAL=”T” or “IT” in MATDAT (time or temp).

Independent temperature columns are converted if

CCALC is different than ITSCAL in MATDAT.

FACTOR is multiplied by dependent column.


Node Data The nodes are written to the MODELSIN file in the NODE DATA block in the following order: diffusion (stores energy), arithmetic (massless), and boundary (fixed temperature). As shown in Table C-12, a wide variety of options are possible for the NODE DATA block. An arithmetic node can be created with the NODE,#,ADD command in Patran. Nodes can have initial temperatures specified in Patran, otherwise the “TINITL” parameter in the QINDAT file is used to provide the initial temperatures. A node can also have a fixed temperature with the “-1” parameter specified in the TEMP LBC as described in Section 2.2.3.1 of this manual. Temperatures that reference macro and micro functions are not supported for this release. This functionality would be created by including the appropriate logic in the SINDA VARIABLES block. Currently, 62,400 is the maximum number of nodes per translation.

Conduction If the MATDAT file specifies the thermal conductivity to be “Constant”, then a constant conductor will be created in the SINDA deck. Time and temperature varying conductors will be created if the material property is input into the MATDAT file in a “TABLE” (or “ITABLE”). If ITSCAL is “T” for time, then a time varying conductor (SIT for Network Analysis' SINDA) will be created. See MPID Number, Function Type, Temperature Scale, Factor and Label (p. 263) in the Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis under Material Properties (Ch. 8) for a description of ITSCAL and IEVAL. There is no limit to the maximum number of conductors per translation.

Convection Convection with a constant heat transfer coefficient is specified as described in Chapter 2 and also in sample problems 1 and 10. Problem 10 also demonstrates how convection can be specified as a function of temperature. This is done by creating a “CONV” template in the TEMPLATEDAT file which references configuration 29. This configuration points to a table of temperature versus heat transfer coefficient in the MATDAT file. Time varying convection is done in a similar way except ITSCAL for the convection MPID in the MATDAT file is “T” for time. Convection can also be created by referencing a spatial varying convection field or data entity (data line, data patch, or data hyperpatch). Other convection configurations are not supported by the SINDA utility.

Radiation Gray body radiation with fixed emissivity is supported as in Section 2.2.3.5 with the VFAC LBC and in the users manual. These radiation resistors are used in problem 10 and in all 3 example View Factor problems. Variable emissivity and spectral radiation are not supported for the SINDA utility.

Advection Variable and/or constant mass flow rate and specific heat are supported for advection. The hydraulic network functionality of Patran Thermal which calculates pressure drops and flow rates is not supported for the SINDA utility.


746

The APPENDSIN FileThe APPENDSIN file contains six parameters at the top of the file and the rest of the file contains the logic blocks which are appended to the bottom of the newly created SINDA data blocks (NODE, CONDUCTOR, etc.). These parameters can be modified to a user-specified format so that every subsequent SINDA file created will be customized.

Table C-13 Sample APPENDSIN File

Heat Source Heat sources are applied by using the HEAT LBC for heat flux or nodal heat source respectively. Constant or variable heat values are supported. Variable heat sources are allowed by using a table of independent variable (time or temperature) versus heat with a MACRO function with microfunction 8. This is the only microfunction supported. For temperature varying sources, “ARG” is equal to “1” and for time varying sources, “ARG” is equal to “0” as specified in MFID, Independent Variable, and Function Type (p. 323) in the Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis under Microfunction Data (Ch. 8).

Run Control The run control parameters are taken from the QINDAT file in the local directory. It is important to note that the SINDA utility will NOT look for any nodes or resistors inserted directly into the QINDAT file. It will only read these nodes and resistors from the appropriate files (nodedat, resdat, etc.) Table C-12 shows which run control parameters are read. All other parameters in the QINDAT file are ignored.

Materials If the IEVAL parameter of the material property (MPID) in the MATDAT file is T (or “IT”) for table, then the table will be put into ARRAY DATA. If the value of ITSCAL (also in the MATDAT file) is different than the value of ICCALC in the QINDAT file, then a conversion of the temperatures in the MATDAT file will take place to match the temperature units specified by ICCALC (the calculation units). A message in the array will note that this has taken place. Any of the thermal conductivities and specific heats in the Patran Thermal material library that are tables can be brought into ARRAY DATA. The phase change properties in the MATDAT file will be ignored by the SINDA utility.


748


750


The APPENDSIN file is created for the user by the SINDA utility if a APPENDSIN file does not already exist in the local directory. If the file does exist in the local directory, then the parameters will be read by the utility and the logic blocks will be appended to the bottom of the SINDA input deck.

The six parameters are described below


752

:

The remainder of the APPENDSIN file contains logic blocks for modification before being appended to

SINDA Format The choices are “BCD” or “HEADER”. This signifies that this file is created for Network Analysis’ “BCD” format SINDA or SINDA ‘85 with “HEADER” format. It is recommended that all APPENDSIN files be deleted from the local directory before re-executing the SINDA utility if the run is being changed from SINDA '85 to Network Analysis’ SINDA (or vice versa). The SINDA utility will prompt the user as to which type of SINDA file should be created next time since an APPENDSIN file no longer exists in the local directory.

Since the default versions of SINDA do not support a negative shape factor (area/length) in SIV statements, a temporary value of 1.0 is assigned in the CONDUCTOR block for the negative cross-derivative terms which are recalculated in VARIABLES 1. If the SIV has been modified to accept a negative shape factor (without taking the absolute value) then the term FIXBCD or “FIXHEADER” can be used which will direct the utility to allow SIV statements with a negative shape factor. These cross-derivative conductors are the key to the inherent accuracy of Patran Thermal’s conductor network.

Submodel Name This is the SINDA ‘85 submodel name and is only relevant for SINDA 85. This line must exist in the APPENDSIN for both types of SINDA but is ignored for Network Analysis’ SINDA.

Conductors & capacitors in arithmetic format (YES, NO)

If YES (default) is entered, then all of the information in NODE DATA and CONDUCTOR DATA blocks will be entered with arithmetic operators (typically with the multiplier symbol "*"). If NO is entered, then all values for a node or conductor entry will be entered as a single value.

Node increment This value is the increment for each node in the Patran model. Node 1 in the Patran model will become node 2001 if the increment is set to 2000. This might be used if multiple Patran models need to be combined into one SINDA deck. This option should be used with caution since the Patran nodes must correspond to the SINDA nodes for postprocessing in Patran.

Conductor increment This value is the increment for conductors in the SINDA input file. If the increment is set to 1000, then the first conductor in the SINDA input file will be 1001. This might be used if multiple Patran models need to be combined into one SINDA deck.

System energy balance criteria (BALENG or EBALSA)

This is the system energy balance criteria. For Network Analysis SINDA, this is the BALENG value. For SINDA 85, this is the EBALSA value. The default value is 0.01.


the bottom of the SINDA input file. Included in these logic blocks is a SUBROUTINE block. This block contains a subroutine called “RESPAT” that allows SINDA to create a file or files with nodal results in a format that Patran can read directly. These nodal results files are of the form “NR#SIN” where # denotes the output number. The “RESPAT” routine can be called directly from SINDA much like a “TPRINT” routine is typically called for printing temperatures to the SINDA output file. By default, this subroutine call is put in EXECUTION (OPERATIONS DATA for SINDA ‘85) for steady- state runs and in OUTPUT CALLS for transient runs.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisUsing TRASYS Translator

754

Using TRASYS Translator

Translation of Patran Thermal View Factors to TRASYSPatran Thermal problems that define view factor calculations can be translated for input to and from the TRASYS code. The correspondence between the Viewfactor code subelemental areas and the TRASYS surface is shown in Figure C-8. A restricted subset of both Patran Thermal and TRASYS capabilities are supported at the moment. The linkages between the codes are not automatic and require intervention by the users in executing the calculations in either direction. The translation requires the vfin.dat file created during Patran Thermal submit. The basic procedure is outlined in the following sections.

Figure C-7 Mapping between the Viewfactor code subelemental areas and the TRASYS Surface Nodes

Translating Patran Thermal Model to TRASYS InputSome of the steps below assume that Patran version 1.4-2 or later is available. For example if the template.dat.apnd file is defined before the job is spawned from Patran the template file will be pulled into the directory where the job is expected to execute. There is more than one way that a user can go about building the TRASYS results and the following just outlines one method.

First the template file has a new entry that defines the TRASYS surface properties. This entry is defined below:

755Appendix C: PATQ Preference ProgramUsing TRASYS Translator

In the above example the different item in the VFAC template which is used by Patran Thermal are:

The VTRA defines the surface properties required by TRASYS. The input definitions are:

VFAC Key word denoting P/Viewfactor informationuid User defined template IDnbands Number of band for wavelength dependent radiationEc Constant Surface EmissivityTc Constant Transmissivity of participating mediaEmpid Material property ID of variable Surface EmissivityTmpid Material property ID of variable participating media TransmissivityL1 Lower wavelength of multiple band radiation.L2 Upper wavelength of multiple band radiationKflag Extension Coefficient flagCollapse Collapse flag


756

The forward translation is done by executing PATQ. It assumes that you have already translated the neutral file to generate the required QTRAN input files in a previous step - menu pick 2. This is followed by a menu pick 6 which brings up the additional utilities menu and select menu pick 16 which will read the vfin.dat file and reformat the radiating surfaces into polygons in the TRASYS format. The output file for input to TRASYS is given the name trasys.inp. Each enclosure is defined as a BCS group with a 6 character name reflecting the enclosure number. Each radiating surface is given a TRASYS node ID which is 10 times the Patran THERMAL surface ID. The parent Patran element ID and node ID’s are identified in comment portions of the TRASYS surface declarations.

Some restrictions on how the TRASYS run should be made are: One, the units for TRASYS are BTU, feet and hours. The thermal model, when it is generated in Patran, should be in these units. If the model has different geometric units, the conversion should be exercised at the initial translation so that all conduction, convection and radiation boundary conditions are in a consistent set of units. Two, since the radiation resistor/conductors defined for Patran Thermal do not include the Stefan Boltzmann constant, SIGMA should be set to 1.0 for the TRASYS run. If it is desired to make a run with SINDA, then the SIGMA can be defined in the SINDA input. The desired output for the resistor network should be directed to tape and punched output should be requested for the desired solar heat fluxes.

TRASYS Output to Patran Thermal InputAfter a successful TRASYS run has been made, a bcd file should be present. This file contains the requested output quantities the end of which is denoted by the character string c$end. If the radiation interchange has not been output to the bcd file, the user needs to add a c$end record at the beginning of the file. The reverse translator is initiated by going into the utilities menu and executing option 17. Normal Patran execution with generate a qin.dat file which has a number of insert file references that are specific to performing thermal analysis using data created from the reverse translation of the TRASYS data. The added file references are summarized on the following page. They are proceeded by a comment type keyword - **TRASYS_XX where the XX refers to one of three types of analysis that can be performed. DY is dynamic analysis with articulating bodies which create time dependent viewfactors, TR is transient analysis without dynamic viewfactors and SS indicates a steady state run based on average properties. When doing the reverse translation the user has a number of options first of which is to create run type qin.dat files. This will uncomment the appropriate files creating specific qin.dat files with suffixes corresponding to the type of analysis desired. To utilize this feature the user should define all input on the analysis form as if a transient run is to be performed. Also, the files are set up assuming a steady state run will be performed providing initial conditions for the transient analysis.

Alpha Solar AbsorptivityEmiss IR EmissivityTrans Solar TransmissivityTrani IR TransmissivitySprs Solar Specular ReflectivitySpri IR Specular Reflectivity


The user will continue to be queried for different options related to the type to reverse translation data is desired and conversion units relative to the TRASYS analysis. TRASYS analysis determine heating loads and viewfactors based on element entities. Since MSC THERMAL performs its analysis based on the finite element approach and uses the nodal subareas, the heat fluxes and viewfactors from TRASYS are distributed to each node of a given element based on the finite element shape functions associated with the element in question. After all the fluxes and viewfactors have been distributed to each node they are combined. As a result even though a finer distribution has been used to define the conditions at each node, the heating and resistor network associated with the finite element network is of the same order one would get from an elemental analysis. All the files created for input to MSC THERMAL at the user’s option can be translated to SINDA format as well.

The user can define the output names. The default names are consistent with those included in the qin.dat file and the information contained in each file is:

Currently all these files are ascii.

The Patran THERMAL TRASYS reverse translator treats the TRASYS ambient (space) node radk's differently than other surface to surface radk's. In the forward translation to TRASYS from Patran THERMAL, each element surface from P3THERMAL is multiplied by 10 as it is written to the TRASYS input deck. If the enclosure references an ambient node then that node ID is added in a comment card at the end of the TRASYS input deck. When creating the operations block in TRASYS, there are three options with regard to numbering the SPACE node.

The preferred option is to use "0" as the default SPACE node number. This will force TRASYS to use 32767 as the space node number. On reverse translation from TRASYS to Patran THERMAL, there is logic in the translator to detect incoming 32767 references and to convert those references to the original

trdkmat.dat Time dependent material properties which are used by the dynamic radiation resistors to define periodic varying viewfactors.

trdynrdk.dat Dynamic resistor definitions which will use the trdkmat.dat material properties to specify variable radiation viewfactors.

trcdrc.dat These are constant radiation resistor to be used in conjunction with the time dependent viewfactors when performing a dynamic analysis. Even though the entire enclosure may indicate articulating surfaces, some changes may not vary enough to warrant the added calculation associated with variable geometry.

travrc.dat Steady state or transient analysis which don’t have variable geometry do not need the variable radiation resistors. I those cases the RADKs are based on average values which are defined in this file.

tramic.dat The microfunction file which has the equivalent TRASYS periodic heat flux array data. Used for both dynamic and transient analysis.

traqma.dat Qmacro function file which relates the microfunction data in the tramic.dat file to each Patran/THERMAL nodal subarea.

trqbas.dat The average heating from TRASYS surface that is distributed to each Patran/THERMAL nodal subarea. Only used for steady state analysis.


758

Patran THERMAL ambient node number which was included in the comment card. The second option is to hard code "32767" as the TRASYS SPACE node number. The result is the same as option 1. The third option for numbering the SPACE node is to number it the same as the ambient node ID in Patran THERMAL multiplied by 10. This will circumvent the 32767 logic and allow the reverse translator to strip the trailing "0" without changing the original Patran THERMAL space node number.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisUsing NEVADA Translator

760

Using NEVADA Translator

Translation of Patran Thermal View Factors to NEVADAPatran Thermal problems that define view factor calculations can be translated for input to and from the NEVADA code. The correspondence between the Viewfactor code subelemental areas and the NEVADA surface is shown in Figure C-9. A restricted subset of both Patran Thermal and NEVADA capabilities are supported at the moment. The linkages between the codes are not automatic and require intervention by the users in executing the calculations in either direction. Patran Thermal 1.4-2 or later is required to do the translation. The translation requires the vfin.dat file created during the Patran Thermal submit. The basic procedure is outlined in the following sections.

Figure C-8 Mapping between the Viewfactor code subelemental areas and the NEVADA Surface Nodes.

761Appendix C: PATQ Preference ProgramUsing NEVADA Translator

Translating Patran Thermal Model to NEVADA InputSome of the steps below assume that Patran version 1.4-2 or later is available. For example, if the template.dat.apnd file is defined before the job is spawned from Patran, the template file will be pulled into the directory where the job is expected to execute. There is more than one way that a user can build the NEVADA results; the following outlines one method.

First the template file has a new entry that defines the NEVADA surface properties. This entry is defined below:

In the above example the different item in the VFAC template which is used by Patran Thermal are:


762

The VNEV defines the surface properties required by NEVADA. The input definitions are:

The forward translation is done by executing PATQ. It assumes that you have already translated the neutral file to generate the required QTRAN input files in a previous step - menu pick 2. This is followed by a menu pick 6 which brings up the additional utilities menu and select menu pick 18 which will read the vfin.dat file and reformat the radiating surfaces into polygons in the NEVADA format. The output file for input to NEVADA is given the name nevada.inp. NEVADA only recognizes one enclosure thus it is import to only include one enclosure in the model being translated. Each radiating surface is given a NEVADA node ID which is 10 times the Patran Thermal surface ID. The parent Patran element ID and node ID’s are identified in comment portions of the NEVADA surface declarations.

Some restrictions on how the NEVADA run should be made are: One, the units for NEVADA are BTU, feet and hours. The thermal model when it is generated in Patran should be in these units. If the model has different geometric units, the conversion should be exercised at the initial translation so that all conduction, convection and radiation boundary conditions are in a consistent set of units. Two, since the radiation resistor/conductors defined for Patran Thermal do not include the Stefan Boltzmann constant, SIGMA should be set to 1.0 for the NEVADA run. If it is desired to make a run with SINDA, then the

VFAC Key word denoting P/Viewfactor informationuid User defined template IDnbands Number of band for wavelength dependent radiationEc Constant Surface EmissivityTc Constant Transmissivity of participating mediaEmpid Material property ID of variable Surface EmissivityTmpid Material property ID of variable participating media TransmissivityL1 Lower wavelength of multiple band radiation.L2 Upper wavelength of multiple band radiationKflag Extension Coefficient flagCollapse Collapse flag

Alpha Solar AbsorptivityEmiss IR EmissivityTrans Solar TransmissivityTrani IR TransmissivitySprs Solar Specular ReflectivitySpri IR Specular ReflectivityIors Solar Index of RefractionIori IR Index of Refraction

763Appendix C: PATQ Preference ProgramUsing NEVADA Translator

SIGMA can be defined in the SINDA input. The desired output for the resistor network should be directed to tape and punched output should be requested for the desired solar heat fluxes.

The Patran THERMAL NEVADA reverse translator treats the NEVADA ambient (space) node radk's differently than other surface to surface radk's. In the forward translation to NEVADA from Patran THERMAL, each element surface from Patran THERMAL is multiplied by 10 as it is written to the NEVADA input deck. If the enclosure references an ambient node, then that node ID is added in a comment card at the end of the NEVADA input deck. When creating a space node in Patran for NEVADA translation, a space node ID of 9999 must be used.

NEVADA Output to Patran Thermal InputAfter a successful NEVADA run has been made, fixed format ASCII files - one for the heating rates and another for the radiation network - should be present. By examining the data in specific fields, it is possible to determine if heating rates, periodic loading or average orbital heating loads are defined. The reverse translator is initiated by going into the utilities menu and executing option 19. At that point the user will be queried if the nodal quantities are to be formatted for SINDA as well as P/THERMAL. You can select output for each of the three types of output available - average heat flux, periodic heat flux, or radiation resistors. For each selection, you are again queried for input and output file names, plus various index offsets and units conversion factors. For the resistors, an intermediate file - tratpt.dat is created which has all the resistor distributed to a given node before they have been combined.

After the reverse translation has been completed, you will have four files, if all options have been exercised. The Patran Thermal qin.dat file has the default names included as insert records in the proper places. The default file names are:

Currently, all these files are ascii. Either have the desired input files available or comment out the undesired insert directives, so that only the desired options are loaded in the QTRAN run. For example, both the average heating and periodic heating should not be defined for the same run. Examples of where the new insert directives are located is shown below.

radrst.dat The equivalent NEVADA radiation resistor network.

Note: You can either use the RADRs from NEVADA or the radiation couplings created by the view factor code or both.

nevmic.dat The micro function file which has the equivalent NEVADA periodic array datanevqma.dat The qmacro function file which defines the NEVADA periodic heating to each

surface that is distributed to each Patran Thermal node.nevbas.dat The average heating from NEVADA surface that is distributed to each Patran

Thermal node.


764

Appendix D: Example ProblemsPatran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

D Example Problems

Overview 766

Example Problem Number 1--Steady State Conduction Problem 767

Example Problem Number 2--Transient Conduction Problem 768

Example Problem Number 3--3-D Iron Cube Problem 770

Example Problem Number 4--Nonlinear Convection Problem 771

Example Problem Number 5--Nonlinear Temperature and Heat Source Boundary Conditions 773

Example Problem Number 6--Steady State Radiation 774

Example Problem Number 7--Sample of Advection/Convection Coupling 776

Example Problem Number 8--Sample of User Routines 778

Example Problem Number 9--Solution of a “Stiff” THERMAL Problem with the Direct Solver 780

Example Problem Number 10--Translate MSC.Patran Thermal Input to SINDA Input 781

Problem Number 11--Solution of a Hydraulic Problem 783


766

OverviewThe example problems described in this section are delivered with the software. To run one of these examples, type the following in a working directory:

1. % get_qtranThis brings up the selection of available examples.

2. Enter the problem directory desired after the prompt.3. Type "*" to copy all the files for the example.4. Execute Patran "patran".5. Under the File menu, select Play Session File and choose the <problem_name>. ses file.6. This will build the model and spawn the Patran Thermal job. Review the modeling forms to see

how the model was built.

767Appendix D: Example ProblemsExample Problem Number 1--Steady State Conduction Problem

Example Problem Number 1--Steady State Conduction Problem

IntroductionExample problem 1 is a constant thermal boundary condition problem designed to help in understanding the steps required for a complete Patran Thermal analysis and to develop intuitive visualization skills in predicting expected results.

Figure D-1 Example Problem 1 - 1M x 1M Square Aluminum Plate

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 2--Transient Conduction Problem

768

Example Problem Number 2--Transient Conduction Problem

IntroductionExample problem 2 is designed to expose the user to Patran Thermal's material property evaluation options and the required syntax for their use. The features, capabilities, and control parameters of the translator will be demonstrated. This translator is a crucial element of the Patran Thermal system and facilitates the creation and translation of input and output files. Finally, the user will be familiarized with Patran Thermal's run control parameters. Remember, run control parameters provide the versatility needed to control analysis results. It is the specification of these parameters that drives the analysis. The example problem directs you to assign thermodynamic material properties to four different materials. This is accomplished through a combination of accessing material templates supplied by MSc.Software Corporation or defined by the user. You may define your own materials by directly entering data (via your system editor) to your material data file; MATDAT. We will define one of our own materials, “artificial unobtainium” by editing its properties into the MATDAT file in this example problem.

769Appendix D: Example ProblemsExample Problem Number 2--Transient Conduction Problem

Figure D-2 Example Problem 2 - 1M x 1M Square

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 3--3-D Iron Cube Problem

770

Example Problem Number 3--3-D Iron Cube Problem

IntroductionExample problem 3 is designed to expose you to the considerations involved in performing 3-dimensional geometry modeling and subsequent thermal analyses. Towards this end, we will examine the problem of a 3-dimensional iron cube with liquid mercury flowing in a channel along one side. This problem will require the use of advection for the transfer of thermal energy with the flow of the liquid mercury. The assumption of convective resistance being negligible due to its high thermal conductivity is acceptable since the advective fluid is liquid metal. The finite element mesh required needs to be fine enough to handle the large temperature difference between the advective fluid and the iron cube.

Figure D-3 Example Problem 3 - 1M x 1M x 1M Iron Cube

771Appendix D: Example ProblemsExample Problem Number 4--Nonlinear Convection Problem

Example Problem Number 4--Nonlinear Convection Problem

IntroductionExample problem 4 is designed to build upon the model and concepts of example problem 3 within a nonlinear convection environment. Convection heat transfer is a function of the media, its flow characteristics, and the geometric relationship of the object to the media. These functions are referred to as configurations. Each configuration is defined to be within a given class of convection correlations. There are presently 31 specific configurations and 6 generic configurations available in Patran Thermal. These configurations are listed in the Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis. There are two classes of properties used as input for the convective resistors. These are: geometric properties (GP) and material properties (MPID). We will use both forced and natural convection over flat plates for this problem.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 4--Nonlinear Convection Problem

772

Figure D-4 Example Problem 4 - Nonlinear Convection

773Appendix D: Example ProblemsExample Problem Number 5--Nonlinear Temperature and Heat Source Boundary Conditions

Example Problem Number 5--Nonlinear Temperature and Heat Source Boundary Conditions

IntroductionExample problem 5 has been designed to expose you to nonlinear temperature and heat source boundary conditions. Environmental temperature and heat conditions in thermal analyses are rarely constant. These nonlinear conditions are defined in Patran Thermal through the use of macrofunctions and microfunctions. Although the model geometry is no more complex than in the previous example problems, the boundary conditions are more complex. These boundary conditions may consist of time dependent and/or temperature dependent conditions.

Figure D-5 Example Problem 5 - Nonlinear Temperature and Heat Source Boundary Conditions

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 6--Steady State Radiation

774

Example Problem Number 6--Steady State Radiation

IntroductionExample problem 6 will guide you through the construction of two separate radiation enclosures, one for gray body radiation and another for wavelength dependent radiation. The radiation resistors are developed using the VIEWFACTOR program.

Key ConceptConvection or conduction requires that a material is present for the transfer of heat energy to occur. A material, however, is not needed for a surface to transmit heat to another surface by radiation. Two types of radiation supported by Patran Thermal are gray body and wavelength dependent. A gray body surface must have the absorptivity equal to the emissivity and that emissivity is constant over the entire temperature range. Wavelength dependent radiation is a significant extension of the gray body theory such that the normal radiosity is divided into discrete frequency bands with the emissivity and transmissivity assumed to be gray within these frequencies. The VIEWFACTOR program then develops the radiation view factors, from which radiation resistors are developed which Patran Thermal can incorporate into the solution.

775Appendix D: Example ProblemsExample Problem Number 6--Steady State Radiation

Figure D-6 Example Problem 6 - Radiative Boundary Conditions 2500 oC (Fixed)

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 7--Sample of Advection/Convection Coupling

776

Example Problem Number 7--Sample of Advection/Convection Coupling

IntroductionExample problem 7 will demonstrate a sample of advection/convection coupling in the context of a 3D steady state analysis.

GoalThis exercise will familiarize the new user with the steps required to define the appropriate boundary conditions for a P3THERMAL analysis involving advective/convective coupling.

GivenA stainless steel block with a hole in it is exposed on one side to an air mass flowing over it. The entire block is initially at a temperature of 25 degrees C. The exterior air mass is large enough that it experiences no temperature drop during the entire traversal of the block. The boundary layer growth begins at the beginning of the block and flat plate heat transfer correlations are assumed to apply along this surface. The interior of the block is cooled by an air mass flowing through a hole in the center of the block, only in this case the mass of air flow is not great enough to prevent the air from being heated. Heat transfer correlations which define the heat exchange for flow inside a tube are valid for this case. The air originates in a plenum in front of the steel block, so the boundary layer for internal cooling begins at the front of the block. Because of symmetry, it is only necessary to model half of the block.

The heating air on the exterior is 100 degrees C and is flowing with a velocity of 10 meters/second. The interior fluid is also flowing at the rate of 10 meters/second with a mass flow rate of 5E-5 kg/second.

FindDetermine the steady state temperature distribution of the block.

777Appendix D: Example ProblemsExample Problem Number 7--Sample of Advection/Convection Coupling

Figure D-7 Example Problem 7 - Advection/Convection Coupling

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 8--Sample of User Routines

778

Example Problem Number 8--Sample of User Routines

IntroductionExample problem 8 will demonstrate a sample of a Patran Thermal analysis utilizing user supplied subroutines in the context of a 2-D transient analysis.

GoalThis exercise will familiarize the new user with the steps required to define the appropriate files and boundary conditions for a Patran Thermal analysis involving user supplied subroutines.

GivenA section of square tubing is cast in a moist sand mold. A quarter symmetry model is developed. The casting is poured in a room which is maintained at 25 degrees C. Ignore all risers and end effects and use a 2-D model to represent the thermal problem. Assume perfect contact between the casting material (material number 351) and the molding sand (material number 831). The casting material has an initial temperature of 1600 degrees C. Heat is lost to the ambient environment at a constant heat transfer coefficient of 500 W/m2-°C on all horizontal surfaces and 1000 W/m2-°C on all vertical surfaces.

The molding sand has an initial moisture content of 40 kg/m3 which can be vaporized. As it is vaporized, it is assumed to be lost out the casting. For this exercise, only capture the energy absorbed in the fluid as it is heated up and vaporized. Do not model any effects of the vapor flowing through the mold and treat those areas that are above the vaporization temperature initially, the same as if it were going through a heat up cycle. Continue to absorb energy until all the moisture has been driven from the sand.

Perform a transient analysis for at least 500 seconds.

Note: You will need to compile the fortran subroutines, umicro.f and uloop7.f located in the subdirectory prob8a. This is done with the command:% ulib uloop7.f% ulib umicro.f

779Appendix D: Example ProblemsExample Problem Number 8--Sample of User Routines

Figure D-8 Example Problem 8 - Sample of a QTRAN Analysis

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 9--Solution of a “Stiff” THERMAL Problem with the Direct Solver

780

Example Problem Number 9--Solution of a “Stiff” THERMAL Problem with the Direct Solver

IntroductionExample problem 9 has been designed to illustrate the thermally “stiff” problem. Patran Thermal has Iterative (SOL=0) and Direct (SOL=2) solution options. For “stiff” THERMAL problems iterative solvers tend to converge very slowly while direct solvers work very efficiently. The problem is solved using both iterative and direct solvers and the run times are compared.

Figure D-9 Example Problem 9 - “Still” Thermal Problem with the Direct Solver

781Appendix D: Example ProblemsExample Problem Number 10--Translate MSC.Patran Thermal Input to SINDA Input

Example Problem Number 10--Translate MSC.Patran Thermal Input to SINDA Input

IntroductionExample problem 10 has been designed to illustrate the translation of input prepared for a Patran Thermal analysis to a format for input to SINDA. The necessary input files can be retrieved with the GET_QTRAN command. The problem is a simple electronic chip made up of multiple materials with convection, radiation and temperature boundary conditions. Both nodal and surface flux heat source are applied to the chip. All of this problem translates to a SINDA input file even though not all functionality of Patran Thermal cannot be translated to SINDA. For example, even though the entire radiosity network is carried into the SINDA input definition, if variable emissivities are modeled, SINDA does not properly calculate the radiation. The supporting routines necessary to handle this case have not been developed at this time. If variable emissivities are modeled, an error message is generated and the remaining portion of the problem is translated to SINDA input. The Patran Thermal convection library is another feature that has not been developed for execution with SINDA.

Key ConceptThe SINDA translation option takes the input files as generated by Patran Thermal and creates the input in a format ready to be executed by SINDA codes whose input formats are compatible with Network Analysis' version or the SINDA85 code. Create the inputs for this demonstration problem and execute Patran Thermal with the iterative solver, the direct solver and the SINDA code. Because the inputs are the same does not mean that all solutions will yield the same results. Methods of solution also contribute to variations in results.

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisExample Problem Number 10--Translate MSC.Patran Thermal Input to SINDA Input

782

Figure D-10 Example Problem 10 - MSC Pastran Thermal Input to SINDA Input

783Appendix D: Example ProblemsProblem Number 11--Solution of a Hydraulic Problem

Problem Number 11--Solution of a Hydraulic Problem

IntroductionExample problem 11 has been designed to illustrate the usage of the hydraulic network option. This example couples the hydraulic solution to a transient thermal solution. The necessary input files can be retrieved with the GET_QTRAN command. The problem is simply a fluid flowing in a copper pipe that has a linear variation in heating rate applied along its length. The fluid extracts the heat from the pipe by a convective boundary condition that has a constant heat transfer coefficient. In this case the oil viscosity has been altered to more dramatically illustrate the coupling of the hydraulic and thermal solutions.

Figure D-11 Example Problem 11 - Solution of a Hydraulic Problem

Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic AnalysisProblem Number 11--Solution of a Hydraulic Problem

784

MSC.Fatigue Quick Start Guide

I n d e xMSC Patran Thermal User’s Guide Volume 1: Thermal/Hydraulic Analysis

INDEX

Index

Symbols$ECHO_OFF, 228$ECHO_ON, 228$INSERT files, 228, 687$RESTART Command, 227$STATUS, 228

Numerics3-D Cartesian Dimensionality Selection w/

PATQ, 6673-D iron cube problem, 770

Aadaptive explicit/implicit weighting, 217advection/convection coupling, 776advective heat transfer, 210Ames, 600anisotropic materials, 223annular space between concentric spheres,

natural convection, 386AREA, 276, 288, 296, 303ARGUMENT, 441arrays, 545automatic mesh generation, 300, 303

BBinary Input File to Text File Conversions, 675Bird & Lightfoot, 600bisection method, phase changes, 208blackbody radiation potential fraction,

microfunction, 454Building Macrofunction from Microfunctions,

325, 327, 331

CCAP.DAT, 715Capacitor Data, 320Cdata, with CONV template, 691

CFIG, 281, 347, 419circular tube in cross flow, forced convection,

356Collapse, 692, 693combined natural and forced convection, inside

horizontal tube, 395, 421COMMONBLK definitions, 468composites, 223condensation (filmwise), 398, 402CONDUC.DAT, 715conductive resistor data, 276constant, microfunction, 442contact coefficients, 102contact resistance, 102Contact resistance with an interstitial fluid, 423contact resistances, 102Control Parameters, Section 5.2.6, 335CONV template, 685, 690CONVEC.DAT, 715convection gap, 107, 108, 111, 717convection, CFIG 1, 347, 419convection, pool boiling, 405convective resistor configuration specification,

281convective resistor geometric properties, 281convective resistor header data, 281convective resistor MPID values, 282convective resistor node numbers, 281convective resistor type specification, 281convective resistors, 2-noded, 209convergence acceleration schemes, 218convergence criteria, 220Conversion of NRnnn.NRF Files to

NFnnn.NEU Files, 681Convert Binary Nodal Results Files to ASCII

Nodal Results Files, 682corrector equation, 216CP_MPID, 301Create LCI type Material Properties, 682Create SINDA Input File from QTRAN Input,


2

683

Ddead band microfunction, 456DEFPND, 254Dissimilar Mesh Temperature Interpolation, 675distance, gray radiative resistor, 288DTMAX(keyword) DTMAXDTMAXH, 253DTMAXA, 253

EEmissivity, 693Empid, 693enclosed spaces between flat plates, natural

convection, 382error estimation, 220Example HYDRAULIC Resistor Definitions, 319Example Template File, 703example, convective resistor, 282example, DFEG HEAT with MACRO template,

689example, MACRO template, 688example, microfunction, 443, 444, 445, 446,

447, 448, 449, 450, 451, 452, 453, 454, 455, 458, 459, 460, 462, 463

examples, gray radiative resistors, 288examples, wavelength dependent resistors, 297exponential function, microfunction, 447extinction coefficient, 286, 295

Ffiles, QTRAN, 718filmwise condensation on a horizontal tube, 402Finite Element to Resistor/Capacitor

Translation, 223fixed order format, 227fixed pressure nodes, 333fixed temperature nodes, 333flat plates, forced convection, 353flip/flop microfunction, 455, 462flow around a sphere, forced convection, 367,

368Flow Chart, P/THERMAL Data Flow, 663FLUID template, 685, 700forced convection, 350

forced convection, circular tube in cross flow, 356

forced convection, flat plates, 353forced convection, flow around a sphere, 367,

368forced convection, generic, 413forced convection, hexagonal tube in cross flow,

361, 363forced convection, inside horizontal tube, 395,

421forced convection, local flat plates, 435forced convection, packed beds, 407, 422forced convection, smooth constant heat flux

tubes, 420forced convection, smooth isothermal tubes,

347, 419forced convection, square tube in cross flow,

358, 360forced convection, staggered tube banks, 370forced convection, vertical plate in horizontal

flow, 365Forsythe & Wasow, 600Fourier Modulus, 217free format input, 227function type specification, material property,

263

GGebhart, 600generic forced convection, 413generic natural convection, 409, 411global temperatures, 335GP values, 281, 308gray radiation networks, 210, 283, 288

HHageman, 600heat source boundary conditions, 773heat source/sink macrofunction data, 325heat sources, global initialization, 335heat transfer texts, 600heat transfer, advective, 210Hermite Polynomial interpolation, 222, 449, 459hexagonal tube in cross flow, forced convection,

361, 363

3INDEX

History Plots, 674horizontal cylinders, natural convection, 378horizontal tube (inside), combined natural and

forced convection, 395, 421horizontal tube, filmwise condensation, 402Hughes, 600hydraulic resistor header data, 307Hydraulic Resistors, 307, 308, 309

IICCALC, 230IDMNRF, 249IECHO, 229IEVAL, 263individual assignments of initial presssures, 337initial global heat sources, 335initial global pressures, 333, 335initial global temperatures, 335Initially Fixed Nodes, 333, 334initially fixed temperature nodes, 333input data echo option, 229input data, PATQ, 710Input to SINDA input, 781Interpolation of Temperatures for Structural

Meshes, 675interpolation, Hermite Polynomials, 222interpolation, linear, 221IPLTBK, 261ISCALE, 230iterative methods, 600ITSCAL, 263

JJames, Smith, & Wolford, 600

KK_MPID, 301Karlekar & Desmond, 600keywords, QIN.DAT, 227Kflag, 693

LLABEL, 263LAMBDA, 296, 693

LENGTH, 276, 303, 667library, microfunction, 440Limitation, 707linear data table, microfunction, 448, 458linear interpolation, 221local flat plates, forced convection, 435

MMACRO templates, 685, 687macrofunction construction from

microfunctions, 327macrofunctions, 213, 688Main Menu Picks, 662Mass flow rate Control Macrofunction Data, 330material properties, 263material property data, 268Material Property Data Base Files (MPID.xxx),

669material property data base utilities, 671material property, function type, 263material property, identification number, 263material property, label, 263material property, scale factor, 263material property, temperature scale, 263Maximum CONV Template TID Number, 707maximum time step, 253maximum time step adjustment, 253MDATA, 268mesh generation, 1-D, 300mesh spacing, recommended, 207MFID, 323, 327, 331, 441Microfunction, 325, 329MID number, template data, 685, 686MPID, 263, 283, 292

Nnatural convection, annular space between

concentric spheres, 386natural convection, enclosed spaces between

flat plates, 382natural convection, generic, 409, 411natural convection, horizontal cylinders, 378natural convection, inside horizontal tube, 395,

421natural convection, rectangular blocks, 375


4

natural convection, sphere, 380natural convection, vertical or inclined surface,

uniform heat flux, 389, 392natural log, microfunction, 452Nbands, 693network construction, 276Neutral File, 663, 674, 710Neutral File Generation From QOUT.DAT, 674Neutral File Translation, 663Neutral File Translation Flow Chart, 663NITBUP parameter, 232Nodal Classification Changes, 334Nodal Results File Generation, 673Nodal Results File Print Options, 249Nodal Results File Times, 682NODE, 326, 328, 330, 337node location, initial, 258node number declarations, 254NODE.DAT, 276, 281, 283, 292, 301, 714NODXYZ(keyword) NODEIDNODEXNODEY

NODEZ, 258nonlinear convection problem, 771nonlinear temperature, 773number of iterations between updates, 232

Ooptimal relaxation parameter, 218output files, 713over relaxation, 218

PP/THERMAL execution, 708P1, 303packed beds, forced convection, 407, 422PATQ, 223, 710PATRAN Neutral File, 710PBLOCK, 260PFIX, 334phase change algorithm, theory, 222phase changes, 208PHID, 301PHID number, template data, 686pool boiling, 405power series, microfunction, 442predictor equation, 216

predictor-corrector algorithm, 216PRESS, 337Pressure Control Macrofunctions, 331pressure nodes, fixed, 333print control, 259print interval adjustments, 259print interval, initial, 259PRINTA, 259

QQBASE.DAT, 716QIN.DAT, 227, 711, 718QINDAT File Listing, 569QMACRO.DAT, 715QOUT.DAT, 711, 718QPLOT.DAT, 711, 718QTRAN arrays, 545QTRAN files, 718QTRAN macrofunctions, 213QTRAN run control parameters, 229QTRAN title data, 229QTRAN.FOR, 669, 713

Rradiation gap, 107, 109, 111, 211, 717radiation networks, gray, 210, 283radiative resistors, wavelength dependent, 291ramp function, microfunction, 446recommended mesh spacing formula, 207rectangular blocks, natural convection, 375relaxation parameter, optimal, 218repeating wave form (linear), microfunction, 460repeating wave form, Hermite microfunction,

451RES.DAT, 715RESTART Command, 227rotating disk, 416run control parameters, 229run option selection, 232

Sscale factor, material properties, 263Siegel & Howell, 600SINDA, 720sine wave, microfunction, 443

5INDEX

Single Bulk Data File, 681skewed meshes, 223smooth constant heat flux tubes, 350SNPSOR, 208SOL parameter, 232solution option, 232Spawn Execution, 668, 670Specify Direct Solver Memory Size, 682sphere, natural convection, 380square tube in cross flow, forced convection,

358, 360square wave, microfunction, 444staggered tube banks, forced convection, 370STAT.BIN, 718steady state Cartesian conduction, 205steady state conduction problem, 767step function, microfunction, 445straight line, microfunction, 457Structural Mesh Temperature Interpolation, 675subroutines, user supplied, 466System energy balance, 221

TTEMP, 337TEMP.DAT, 716Temperature Control Macrofunctions, 327Temperature History Plots, 674Temperature Interpolations, 675temperature nodes, fixed, 333temperature scale definition, 230temperature scale, material properties, 263Temperature vs. Time History Plots, 674temperature, coupled, 257temperatures, global initialization, 335temperatures, initial assignment of individual

nodes, 337temperatures, pressure initialization, 335TEMPLATE file, 685template, CONV, 685template, FLUID, 685template, MACRO, 685template, MID, 685template, VFAC, 685TEMPLATE.BIN, 670TEMPLATE.DAT, 703, 711

TFIX, 334TFIX.DAT, 716theory, phase change algorithm, 222Thermal Load Interpolations For Structural

Meshes, 675Thermal Network, 204thermal radiation, 600thermal resistor assignments, 276TID, 693Time History Plots, 674time step, adjustment of maximum, 253time step, maximum, 253time units definition, 230Times of Nodal Results Files, 682title data, 229TLABEL, 230TMACRO.DAT, 715Tolerance Value (Temperature Interpolations),

676TPRINT(keyword) TPRINT, 259transient conduction, 206transient conduction problem, 768Translation, FEM to RC, 223transmissivity, 693transport phenomena, 600TSCALE, 337

UUHVAL, 437ULIBFOR contents, 484ULOOP7.FOR file listing, 536under relaxation, 218Units (Length) Conversion, 668UPROP, 267upwind differencing, 210user routines, 778user supplied convection subroutines, 437User supplied routines examples, 267, 281,

463, 466, 536Utility Menu, 671

Vvertical enclosed space with uniform heat flux,

natural convection, 392vertical or inclined surface, uniform heat flux,


6

natural convection, 389vertical plate in horizontal flow, forced

convection, 365VFAC template, 685, 692VFDIST, 288, 292VFIN.DAT, 718VFNODE.DAT, 718VFRES.DAT, 718view factors, gray radiative resistors, 288VIEW-FACTOR, 288, 296VNEV templates, 698VTRA templates, 696

Wwavelength dependent radiative resistors, 291wavelength dependent resistors, examples, 297white, 600

XX/Y Plots of Temperature vs. Time, 674

Patran 2008 r1 Thermal User's Guide Volume 1: Thermal/Hydraulic Analysis

Documents

Transcript of Patran 2008 r1 Thermal User's Guide Volume 1: Thermal/Hydraulic Analysis