Patran 2010 - Classes

Patran 2010 

Interface To PATRAN 2 Neutral File 

Preference Guide

Corporate Europe Asia Pacific 

MSC.Software Corporation 

2 MacArthur Place 

Santa Ana, CA 92707 USA 

Telephone: (800) 345-2078 

Fax: (714) 784-4056 

MSC.Software GmbH 

Am Moosfeld 13 

81829 Munich, Germany 

Telephone: (49) (89) 43 19 87 0 

Fax: (49) (89) 43 61 71 6 

MSC.Software Japan Ltd. 

Shinjuku First West 8F 

23-7 Nishi Shinjuku 

1-Chome, Shinjuku-Ku 

Tokyo 160-0023, JAPAN 

Telephone: (81) (3)-6911-1200 

Fax: (81) (3)-6911-1201 

Worldwide Web 

www.mscsoftware.com 

Disclaimer 

This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with 

the terms of such license. 

MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document 

without prior notice. 

The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not 

intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no 

liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information 

contained herein. 

User Documentation: Copyright 2010 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:V2010:Z:NEU:Z: DC-USR-PDF

Contents 

PATRAN 2 Neutral File Preference Guide 

1 Overview 

Purpose 2 

What is Included with this Product? 3 

PATRAN 2 Neutral File Preference Integration with 

Patran 4 

2 Building A Model 

Introduction to Building a Model 6 

Coordinate Frames 8 

Finite Elements 9 

Nodes 9 

Elements 10 

Multi-Point Constraints 11 

Material Library 25 

Materials Form 26 

Element Properties 46 

Element Properties Form 47 

Loads and Boundary Conditions 53 

Structural Displacement 54 

Structural Force 57 

Structural Pressure 60 

Structural and Thermal Temperature 64 

Thermal Convection 71 

Thermal Heat Flux 75 

Thermal Heat Source 81 

Thermal View Factor 85 

Load Cases 89

ii 


3 Running an Analysis 

Review of the Analysis Form 92 

Analysis Form 93 

4 Results Templates 

Introduction 96 

Generic Nodal Results File 97 

Generic Element Results File 99 

5 Files 

Files 102 

6 Unsupported Neutral File Packets 

Unsupported Neutral File Packets 104

Chapter 1: Overview 


1 Overview 

 

Purpose 2 

 

What is Included with this Product? 3 

 

PATRAN 2 Neutral File Preference Integration with Patran 4

2 


Purpose 

Purpose 

Patran is an analysis software system developed and maintained by MSC.Software Corporation. The core 

of the system is Patran, a finite element analysis pre- and postprocessor. A key feature of Patran’s 

predecessor, PATRAN 2, was the ability to interface third party software through the Neutral System. 

The PATRAN 2 Neutral File Preference provides a ready-to-use interface allowing third party codes that 

support the PATRAN 2.5 Neutral File to have immediate access to Patran as a pre- and post-processor. 

As much of the PATRAN 2 neutral file is supported as is possible. For more information, see Neutral File 

Format (p. 725) in the Patran Reference Manual. 

This Preference is fully integrated into Patran. The user can either create a new finite element model (e.g., 

import CAD geometry, define a mesh, assign element properties, materials and loads/boundary 

conditions) or import an existing Neutral File. All of Patran’s model editing capabilities are available. 

Results postprocessing is available. The results files should be stored in PATRAN 2 results file formats 

(e.g., .dis, .els formats). Two generic template files are provided for importing nodal and element results. 

For more information on results template files, see File Types and Formats (p. 46) in the Patran 

Reference Manual.

Chapter 1: Overview 

What is Included with this Product? 

3 

What is Included with this Product? 

The PATRAN 2 Neutral File Preference includes all of the following items: 

• A PCL function contained in patran2nf.plb which will add the PATRAN 2 Neutral File 

Preference specific definitions to any Patran database (not already containing such definitions) at 

any time. 

• This user manual is included as part of the product. An on-line version is also provided to allow 

the direct access to this information from within Patran.

4 


PATRAN 2 Neutral File Preference Integration with Patran 

PATRAN 2 Neutral File Preference Integration with 

Patran 

Creation of a PATRAN 2 Neutral File Preference Template Database 

Two versions of the Patran database are delivered with Patran. Both occur in the 

directory and they are named base.db and template.db. The base.db database is a Patran 

database into which no analysis code specific definitions, such as element types and material models, 

have been stored. The template.db database is a version of the Patran database which contains every 

analysis code specific definition needed by all of the MSC supplied interfaces. In order to create a 

template database which contains only PATRAN 2 Neutral File Preference specific definitions, the user 

should follow these steps: 

1. Within Patran open a new database using base.db as the template. 

2. Enter load_patran2nf() into the command line. 

3. Save this database under a name such as patran2nf.db to be your new “PATRAN 2 Neutral 

File Preference only” template database. 

4. From then on, when opening a new database, refer to patran2nf.db as your template 

database. 

PATRAN 2 Neutral File Preference specific definitions can be added to any database by simply typing 

load_patran2nf() into the Patran command line while the target database is the currently opened 

by Patran. Due to the savings in size and for the sake of simplicity it is highly recommended 

template.db not be used as a template database and that the user create his own unique template 

database which contains only the analysis code specific definitions pertaining to the analysis codes of 

immediate interest. For more details about adding analysis code specific definitions to a database and/or 

creating unique template databases, refer to Modifying the Database Using PCL (Ch. 7) in the PCL and 

Customization or to the Patran Installation and Operations Guide.

Chapter 2: Building A Model 


2 Building A Model 

 

Introduction to Building a Model 6 

 

Coordinate Frames 8 

 

Finite Elements 9 

 

Material Library 25 

 

Element Properties 46 

 

Patran 

 

Load Cases 89

6 


Introduction to Building a Model 


There 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 Preferences.



7 

To use the PATRAN 2 Neutral File Preference, set the analysis code selection to the appropriate selection. 

The analysis type may be set to either Structural or Thermal. Corresponding materials and LBCs will be 

presented for finite element modeling.

8 


Coordinate Frames 

Coordinate Frames 

Coordinate frame information is stored in Neutral File Packet 05 (see Packet Type 05: Coordinate 

Frames (p. 732) in the Patran Reference Manual). The coordinate frame ID is stored on the Header Card 

in entry ID. Coordinate frame types are stored on the Header Card in entry IV and are rectangular (IV = 

1), cylindrical (IV = 2) and spherical (IV = 3). Three points (A, B, C), each located by three coordinates 

(1, 2, 3) in the global system, are required to define a coordinate frame. A 3x3 rotation matrix (R) is 

computed and stored in Packet 05. Four data cards, each containing 5 entries, are used to store the 

coordinate points and rotation matrix: Data Card 1 (A1, A2, A3, B1, B2), Data Card 2 (B3, C1, C2, C3, 

R11), Data Card 3 (R21, R31, R12, R22, R32), Data Card 4 (R13, R23, R33). 

For more information on creating coordinate frames see Creating Coordinate Frames (p. 393) in the 

Geometry Modeling - Reference Manual Part 2.


Finite Elements 

9 


Finite elements in Patran allows the definition of basic finite element construction. Created under Finite 

Elements are the nodes, element topology and multi-point constraints. 

For more information on how to create finite element meshes, see Mesh Seed and Mesh Forms (p. 25) 

in the Reference Manual - Part III. 

Nodes 

Nodes in Patran will generate Packet 01 entries in the neutral file (see Packet Type 01: Node Data 

(p. 728) in the Patran Reference Manual). Nodes can be created either directly using the Node object, or 

indirectly using the Mesh object. The Node ID is stored on the Header Card, entry ID. Each node location, 

defined relative to a coordinate frame, is defined by 3 values. These values are stored on Data Card 1, 

entries X, Y and Z. The coordinate frame is stored on Data Card 2, entry CID. If no reference frame is 

assigned, the global system (CID = 0) is used. Nodes that are exported to the neutral file are always 

resolved relative to the global system (CID = 0). The condensation flag, entry ICF on Data Card 2, 

indicates whether nodes are referenced by one or more elements (ICF = 1) or are unreferenced (ICF = 0). 

Data Card 2 contains entries which currently cannot be referenced within Patran and are set to default 

values. These include the Node Type (GTYPE = G), Number of Degrees of Freedom (NDF = 6), Node 

Configuration (CONFIG = 0) and the 6 permanent single point constraint flags (PSPC = 000000).

10 



Elements 

Finite Elements in Patran assigns element connectivity, such as Quad/4, for standard finite elements. The 

type of element to be created is not determined until the element properties are assigned. Elements can 

be created either discretely using the Element object, or indirectly using the Mesh object. Each element 

results in the creation of a Neutral File Packet 02 (see Packet Type 02: Element Data (p. 729) in the 

Patran Reference Manual). The Element ID is stored on the Header Card, entry ID. The shape (bar=2, 

tri = 3, quad = 4, tet = 5, wedge = 7, hex = 8) is stored on the Header Card, entry IV. The element’s nodes 

are listed on Data Card 2, entry LNODES.



11 

Multi-Point Constraints 

Multi-point constraints (MPCs) can be created from the Finite Elements menu. These are special element 

types which define a rigorous behavior between several specified nodes. The forms for creating MPCs 

are found by selecting MPC as the Object on the Finite Elements form. Each defined MPC results in the 

creation of a Neutral File Packet 14 (see Packet Type 14: MPC Data (p. 735) in the Patran Reference 

Manual). The MPC ID is stored on the Header Card, entry MPC ID. The MPC Set ID--Header Card, 

entry MPC SID--always equals 1.

12 


Finite Elements



13 

MPC Types 

To create an MPC, first select the type of MPC to be created from the option menu. The explicit and 

implicit MPC types defined for PATRAN 2.5 are available and described in the following table. 

MPC Type Analysis Type Description 

Explicit Structural Creates an explicit MPC between a dependent degree-of-freedom 

and one or more independent degrees-of-freedom. The dependent 

term consists of a node ID and a degree-of-freedom, while an 

independent term consists of a coefficient, a node ID, and a 

degree-of-freedom. An unlimited number of independent terms 

can be specified, while only one dependent term can be specified. 

An optional constant term can be specified. 

Rigid (Fixed) Structural Creates a rigid MPC between one independent node and one or 

more dependent nodes in which all six structural degrees-offreedom 

are rigidly attached to each other. An unlimited number 

of dependent terms can be specified, while only one independent 

term can be specified. Each term consists of a single node. There 

is no constant term for this MPC type. 

Rigid (Pinned) Structural Creates a rigid MPC between one independent node and one or 

more dependent nodes in which all three translational degrees-offreedom 

are rigidly attached to each other. An unlimited number 

of dependent terms can be specified, while only one independent 

term can be specified. Each term consists of a single node. There 

is no constant term for this MPC type. 

Linear Surface Structural Creates an implicit MPC intended to connect topologically 

to Surface 

incompatible elements to model a continuum. Each dependent 

(LSS) 

term consists of a node while two nodes describe the independent 

term. There is no constant term for this MPC type. 

Linear Surface 

to Volume 

(LSV) 

Linear Volume 

to Volume 

(LVV) 

Structural 

Structural 

Creates an implicit MPC intended to connect a plate model to a 

solid model. The plate node displacements and rotations are 

defined in terms of the displacements of the solid element nodes. 

Each dependent terms contains one node while each independent 

terms consists of two nodes. There is no constant term for this 

MPC type. 

Creates an implicit MPC intended to connect topologically 

incompatible solid elements to model a continuum. Each 

dependent term contains one node while each independent term 

consists of a minimum of three nodes and a maximum of four 

nodes. All three translational structural degrees-of-freedom are 

automatically specified. There is no constant term for this MPC 

type.

14 



MPC Type Analysis Type Description 

Structural 

Quadratic 

Surface to 

Surface (QSS) 

Quadratic 

Surface to 

Volume (QSV) 

Quadratic 

Volume to 

Volume (QVV) 

Structural 

Structural 


incompatible elements to model a continuum. Each dependent 

terms consists of a node and each independent term consists of 

three nodes. There is no constant term for this MPC type. 

Creates an implicit MPC intended to connect a shell model to a 

solid model. The plate node displacements and rotations are 

defined in terms of the displacements of the solid element nodes. 

Each dependent term contains one node and each independent 

term consists of three nodes. There is no constant term for this 

MPC type. 


incompatible solid elements to model a continuum. Each 

dependent term containing one node while each independent term 

consisting of eight nodes. All three translational structural 

degrees-of-freedom are automatically specified. There is no 

constant term for this MPC type. 

Slide Structural Creates an implicit MPC intended to define a vector between two 

nodes along which a dependent node must move. Each dependent 

term consists of a node while each independent term consisting of 

two nodes. There is no constant term for this MPC type.



15 

Degrees-of-Freedom 

Whenever a list of degrees-of-freedom are expected for an MPC term, a listbox containing the valid 

degrees-of-freedom is displayed on the form. The following degrees-of-freedom are supported by the 

PATRAN 2 Neutral File Preference for MPCs: 

UX 

UY 

UZ 

RX 

RY 

RZ 

Degree-of-freedom 

Analysis Type 

Structural 

Structural 

Structural 

Structural 

Structural 

Structural 

Important: 

Care must be taken to make sure that a degree-of-freedom that is selected for an MPC 

actually exists at the nodes. For example, a node that is attached only to solid structural 

elements will not have any rotational degrees-of-freedom. However, Patran will allow 

you to select rotational degrees-of-freedom at this node when defining an MPC.

16 



Explicit MPCs 

This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements 

form, and Explicit is the selected type. The name EXPLICIT will appear in Packet 14, Data Card 1, entry 

TYPE.



17 

Rigid (Fixed, Pinned) 


form, and Rigid (Fixed or Pinned) is the selected type. The name RIGID will appear in Packet 14, Data 

Card 1, entry TYPE.

18 



Linear Surface to Surface (LSS) MPCs 


form, and Linear Surf-Surf is the selected type. The name LSS will appear in Packet 14, Data Card 1, 

entry TYPE.



19 

Linear Surface to Volume (LSV) MPCs 


form, and Linear Surf-Vol is the selected type. The name LSV will appear in Packet 14, Data Card 1, 

entry TYPE.

20 



Linear Volume to Volume (LVV) MPCs 


form, and Linear Vol-Vol is the selected type. The name LVV will appear in Packet 14, Data Card 1, entry 

TYPE.



21 

Quadratic Surface to Surface (QSS) MPCs 


form, and Quadratic Surf-Surf is the selected type. The name QSS will appear in Packet 14, Data Card 

1, entry TYPE.

22 



Quadratic Surface to Volume (QSV) MPCs 


form, and Quadratic Surf-Vol is the selected type. The name QSV will appear in Packet 14, Data Card 1, 

entry TYPE.



23 

Quadratic Volume to Volume (QVV) MPCs 


form, and Quadratic Vol-Vol is the selected type. The name QVV will appear in Packet 14, Data Card 1, 

entry TYPE.

24 



Slide MPCs 


form, and Slider(12) is the selected type. The name SLIDE will appear in Packet 14, Data Card 1, entry 

TYPE.


Material Library 

25 


The Materials form will appear when the Material toggle is chosen. The selections made on the Materials 

menu will determine which material form appears, and ultimately, which material will be created. 

Two analysis types are available for the PATRAN 2 Neutral File Preference: Structural and Thermal. If 

the analysis type is structural, the following material types may be defined: Isotropic (type 1), 2D 

Anisotropic (type 2), 3D Anisotropic (type 6), 2D orthotropic (type 3), 3D Orthotropic (type 3), and 

Composite (types 11 to 13). If the analysis type is thermal, the following material types may be defined: 

Isotropic (type 4) and Anisotropic (type 5). Structural materials include thermal material properties (e.g, 

conductivity and specific heat) while thermal materials only include the thermal material properties. Each 

material definition will be stored in a unique Neutral File Packet 03 (see Packet Type 03: Material 

Properties (p. 730) in the Patran Reference Manual. 

The following pages discuss the Materials forms, and details of all the material property definitions 

supported by the PATRAN 2 Neutral File Preference.

26 



Materials Form 

This form appears when Materials is selected on the main menu when the analysis type is Structural. The 

analysis type may also be Thermal.



27 

Structural Isotropic 

Linear Elastic 

This subordinate form appears when the Input Properties button is selected on the Materials form when 

Structural Isotropic is selected on the Material form, and when Linear Elastic is the selected Constitutive 

Model on the Input Options form. Use this form to define the linear elasticity values and other 

miscellaneous values for an Isotropic material (material type = 1). All entered values appear in Packet 

03, Data Card 2. 

Thermal Properties 


Isotropic is selected on the Material form, and when Thermal Properties is the selected Constitutive 

Model on the Input Options form. Use this form to define the linear thermal values for an Isotropic 

material (material type = 1). All entered values appear in Packet 03, Data Card 2.

28 



2D Orthotropic 


This subordinate form appears when the Input Properties button is selected on the Materials form 

when 2D Orthotropic is the selected Object, and Linear Elastic is the selected Constitutive Model on 

the Input Options form. Use this form to define the elasticity properties, and other miscellaneous data 

for a 2 dimensional Orthotropic material (material type = 3). All entered values appear in Packet 03, 

Data Card 2.



29 

The remaining Linear Elastic properties for 2D Orthotropic materials and their location in the PATRAN 

2 Neutral File are shown.

30 





2D Orthotropic is selected on the Material form, and when Thermal Properties is the selected Constitutive 

Model on the Input Options form. Use this form to define the linear thermal values for an 2D Orthotropic 




31 

3D Orthotropic 



3D Orthotropic is the selected Object, and Linear Elastic is the selected Constitutive Model on the Input 

Options form. Use this form to define the elasticity properties and other miscellaneous data for a 3D 

Orthotropic material. (material type = 3). All entered values appear in Packet 03, Data Card 2.

32 



The remaining Linear Elastic properties for 3D Orthotropic materials and their location in the PATRAN 




33 



3D Orthotropic is selected on the Material form, and when Thermal Properties is the selected Constitutive 

Model on the Input Options form. Use this form to define the linear thermal values for an 3D Orthotropic 


34 



2D Anisotropic 



2D Anisotropic is the selected Object, and Linear Elastic is the selected Constitutive Model on the Input 


Anisotropic material (material type = 2). All entered values appear in Packet 03, Data Card 2.



35 

The remaining Linear Elastic properties for 2D Anisotropic materials and their location in the PATRAN 


36 





2D Anisotropic is selected on the Material form, and when Thermal Properties is the selected 

Constitutive Model on the Input Options form. Use this form to define the linear thermal values for an 

2D Anisotropic material (material type = 2). All entered values appear in Packet 03, Data Card 2.



37 

3D Anisotropic 



3D Anisotropic is the selected Object, and Linear Elastic is the selected Constitutive Model on the Input 


Anisotropic material (material type = 6). All entered values appear in Packet 03, Data Card 2.

38 



More of the Linear Elastic properties for 3D Anisotropic materials and their location in the PATRAN 2 

Neutral File are shown.



39 

The remaining Linear Elastic properties for 3D Anisotropic materials and their location in the PATRAN 


40 





3D Anisotropic is selected on the Material form, and when Thermal Properties is the selected 

Constitutive Model on the Input Options form. Use this form to define the linear thermal values for an 

3D Anisotropic material (material type = 6). All entered values appear in Packet 03, Data Card 2.



41 

Composite 

The Composite forms provide alternate ways of defining the linear elastic properties of materials. All 

composite options, except for Laminated Composite, will always result in a homogeneous elastic 

material. Three composite material types are currently supported in the neutral file: Halpin-Tsai (HAL, 

type = 11), Laminate (LAM, type = 12) and Rule of Mixtures (MIX, type = 13). The HAL and MIX 

options are stored in Neutral File Packet 03 as are the other homogeneous materials. The LAM option is 

also stored in Packet 03; however, an additional data card, Data Card 3, is used to store the associated ply 

data (thicknesses, orientation angles and material IDs). The number of associated ply data values (the 

number of defined plies) is stored on the Header Card, entry N1. 

Patran will compute and store, for a composite material, in Packet 03 the equivalent engineering 

properties (Data Card 2, Material Constants 27 to 35), 21 material stiffness matrix terms (Data Card 2, 

Material Constants 37 to 57), 6 2D membrane stiffness (A) matrix terms (Data Card 2, Material 

Constants 58 to 63), 6 2D bending stiffness (D) matrix terms (Data Card 2, Material Constants 64 to 69) 

and 9 2D membrane/bending (B) coupling terms (Data Card 2, Material Constants 70 to 78). 

Neutral file import of a Halpin-Tsai (HAL) material will be converted to a 3D Orthotropic material in 

Patran. Similarly, import of a neutral file containing a Rule of Mixtures (MIX) material will be converted

42 



to a 3D Anisotropic material in Patran. The reason for the conversion is that, although Patran supports 

creation of these material types, the PATRAN 2 Neutral File does not provide for a complete definition. 

This is also the reason that a neutral file export of these material types results in the creation of a 

homogeneous elastic material. The PATRAN 2 Neutral File only supports full definition of a Laminated 

(LAM) composite material. 

For detailed discussions on how to build composite materials, please refer to Composite Materials 

Construction (p. 112) in the Patran Reference Manual. 

Laminated 


Composite is the selected Object, and Laminate is the selected Method. Use this form to define the 

laminate lay-up data for a composite laminate material (LAM, material type = 12). Each defined 

composite laminate material will be stored in a unique Neutral File Packet 03. The total thickness, 

number of plies and offset are defined on Data Card 2, Material Constants 3, 4 and 5, respectively. The 

total number of associated ply data values is stored on the Header Card, entry N1.



43 

Thermal Isotropic 



Thermal Isotropic (TIS) is selected on the Material form, and when Linear Elastic is the selected 

Constitutive Model on the Input Options form. Use this form to define the linear elastic thermal material 

values for an Thermal Isotropic material (material type = 4). All entered values appear in Packet 03, Data 

Card 2.

44 



Thermal Anisotropic 



Thermal is the analysis type, Anisotropic is the selected Object, and Linear Elastic is the selected 

Constitutive Model on the Input Options form. Use this form to define the elasticity properties Thermal 

Anisotropic (TAN) material (material type = 5). All entered values appear in Packet 03, Data Card 2.



45

46 


Element Properties 


The Element Properties form appears when the Element Properties toggle is chosen.There are several 

option menus available when creating element properties. The selections made on the Element Properties 

menu will determine which element property form appears, and ultimately, which element will be 

created. 

Element properties are simply categorized as Generic 0D, Generic 1D, Generic 2D and Generic 3D. An 

element configuration ID, required for each property set definition, is used to distinguish element types 

(e.g., Generic 3D, Configuration 8 might represent an 8-node hexahedral while Generic 3D, 

Configuration 10 might represent a 10-node tetrahedral). Each category of element dimension has a 

number of pre-defined property definitions. For example, Generic 1D properties include Configuration 

ID, Orientation, Offset at Nodes 1 and 2, and Pinned degrees-of-freedom at nodes 1 and 2. The remaining 

properties are generically defined as Prop 1, Prop 2, etc. Each of the generic properties can contain real 

scalar, string, integer or material property name data. 

Element property data is stored in Neutral File Packet 04 (see Packet Type 04: Element Properties 

(p. 731) in the Patran Reference Manual). Finite element definitions, stored in Packet 02, reference the 

associated Packet 04 element properties by the property ID. 

Two analysis types are available under the PATRAN 2 Neutral File Preference: Structural and Thermal. 

Element property sets can reference materials. For those element property sets created under the 

Structural type, the following materials are available: Isotropic, 2D Orthotropic, 3D orthotropic, 2D 

Anisotropic, 3D Anisotropic and Composite. Element property sets created under the Thermal type can 

only reference Thermal Isotropic (TIS) and Thermal Anisotropic (TAN) materials. For more details about 

these materials, please refer to the Material Librarysection of this document. 

The following pages give an introduction to the Element Properties form, and details of all the element 

property definitions supported by the PATRAN 2 Neutral File Preference.



47 

Element Properties Form 

This form appears when Element Properties is selected on the main menu. There are four option menus 

on this form, each will determine which element type will be created, and which property forms 

will appear.

48 



Generic 0D 

This subordinate form appears when the Input Properties button is selected on the Element Properties 

form. The data entered is stored in Neutral File Packet Types 02 (Element Data) and 04 (Property Data). 

The shape code will be 2 (Packet 02, Header Card, entry IV and Packet 04, Header Card, entry N1). 

In addition to the Configuration Id entry, the remaining entries are generically described as “Prop N” 

where N = 1, 2, ...39. The data entered in these boxes is stored in Packet 04 Data Cards. Each Data Card 

contains five data entries. Thus, Prop 1 through Prop 5 are on the first Data Card, Prop 6 through Prop 

10 on the second Data Card, etc. All of these entries are optional. Only the first data entry up to the largest 

data box number with entered data are stored in Packet 04. The number of data fields stored is indicated 

in Packet 04, Header Card, entry N4.



49 

Generic 1D 



The shape code will be 2 (Packet 02, Header Card, entry IV and Packet 04, Header Card, entry N1). 

The remaining entries are generically described as “Prop N” where N = 1, 2, ...34. The data entered in 

these boxes is stored in Packet 04 Data Cards. Each Data Card contains five data entries. Thus, Prop 1 

through Prop 5 are on the first Data Card, Prop 6 through Prop 10 on the second Data Card, etc. All of 

these entries are optional. Only the first data entry up to the largest data box number with entered data 

are stored in Packet 04. The number of data fields stored is indicated in Packet 04, Header Card, entry N4.

50 



Generic 2D 



The shape code will be 3 or 4 for a triangle or quadrilateral, respectively (Packet 02, Header Card, entry 

IV and Packet 04, Header Card, entry N1). 

In addition to the Configuration Id and Material Orientation entries, the remaining entries are generically 

described as “Prop N” where N = 1, 2, ...38. The data entered in these boxes is stored in Packet 04 data 

cards. Each data card contains 5 data entries. Thus, Prop 1 through Prop 5 are on the first data card, Prop 

6 through Prop 10 on the second data card, etc. All of these entries are optional. Only the first data entry 

up to the largest data box number with entered data are stored in Packet 04. The number of data fields 

stored is indicated in Packet 04, Header Card, entry N4.



51 

Generic 3D 



The shape code will be 5, 7, or 8 for a tetrahedral, wedge or hexahedral, respectively (Packet 02, Header 

Card, entry IV and Packet 04, Header Card, entry N1). 

In addition to the Configuration Id entry, the remaining entries are generically described as “Prop N” 

where N = 1, 2, ...39. The data entered in these boxes is stored in Packet 04 Data Cards. Each Data Card 

contains five data entries. Thus, Prop 1 through Prop 5 are on the first Data Card, Prop 6 through Prop 

10 on the second Data Card, etc. All of these entries are optional. Only the first data entry up to the largest 

data box number with entered data are stored in Packet 04. The number of data fields stored is indicated 

in Packet 04, Header Card, entry N4.

52 


Element Properties


Loads and Boundary Conditions 

53 


The Loads and Boundary Conditions (LBCs) form will appear when the Loads/BCs toggle, located on 

the Patran application selections, is chosen. When creating a loads and boundary condition there are 

several option menus. The selections made on the Loads and Boundary Conditions menu will determine 

which loads and boundary conditions form appears, and ultimately, which loads and boundary conditions 

will be created. 

Each defined LBC will result in the creation of one or more associated neutral file packets. Currently 

available Structural LBCs include Displacement (Packet 08), Force (Packet 07), Pressure (Packets 06 and 

07) and Temperature (Packets 10 and 11). The following Thermal LBCs are available: Heat Flux (Packets 

15 and 16), Heat Source (Packet 16), Convection (Packet 17), Temperature (Packets 10 and 11) and View 

Factor Data (Packet 19). 

The following pages give an introduction to the Loads and Boundary Conditions form, and details of all 

the loads and boundary conditions supported by the PATRAN 2 Neutral File Preference.

54 



Structural Displacement 

This form defines the Displacement LBCs. The associated data will be stored in Neutral File Packet 08. 

The constraint set ID (Packet 08, Header Card, entry IV) is controlled by the associated Load Case (see 

the Load Cases documentation for more details). 

This subordinate form appears when the Input Data button is selected on the LBCs form when the Current 

Load Case Type is Static and the LBC Type is Displacement.



55 

This subordinate form appears when the Select Application Region button is selected on the Loads and 

Boundary Conditions form when the Current Load Case Type is Static and the Loads and Boundary 

Condition Type is Displacement. The nodes can either be explicitly selected (Geometry Filter = FEM) or 

indirectly through their association with one or more geometrical entities (Geometry Filter = Geometry). 

In either case, each selected node will generate a Packet 08. The node ID is stored in the Header Card, 

entry ID.

56 


Loads and Boundary Conditions



57 

Structural Force 

This form defines the Force LBCs. The associated data will be stored in Neutral File Packet 07. The Load 

Set ID (Packet 07, Header Card, entry IV), is controlled by the associated Load Case (see the Load Cases 

documentation for more details). 

This subordinate form appears when the Input Data button is selected on the Loads and Boundary 

Conditions form when the Current Load Case Type is Static and the LBC Type is Force.

58 




Boundary Conditions form when the Current Load Case Type is Static and the LBC Type is Force. The 

nodes can either be explicitly selected (Geometry Filter = FEM) or indirectly through their association 

with one or more geometrical entities (Geometry Filter = Geometry). In either case, each selected node 

will generate a Packet 07. The node ID is stored in the Header Card, entry ID.



59 

s

60 



Structural Pressure 

This form defines the Pressure Loads and Boundary Conditions. The associated data will be stored in 

Neutral File Packet 06. The Load Set ID (Packet 06, Header Card, entry IV), is controlled by the 

associated Load Case (see the Load Cases documentation for more details). 


Conditions form when the Current Load Case Type is Static, the Target Element Type is 3D and the Loads 

and Boundary Condition Type is Pressure. This form is applicable for both element uniform and variable 

pressures. If the load type is Uniform, then only one pressure value is stored; otherwise, three or four 

pressure values, for triangles or quadrilaterals, are stored for Variable load types.



61 


Conditions form when the Current Load Case Type is Static, the Target Element Type is 2D and the Loads 

and Boundary Condition Type is Pressure. This form is applicable for both element uniform and variable 

pressures. If the load type is Uniform, then only one pressure value is stored; otherwise, three or four 

pressure values, for triangles or quadrilaterals, are stored for Variable load types.

62 




Boundary Conditions form when the Current Load Case Type is Static, LBC Type is Pressure and the 

Target Element Type is 3D. This form is applicable for both element uniform and variable load types. 

The elements’ faces can either be explicitly selected (Geometry Filter = FEM) or indirectly through their 

association with one or more geometrical entities (Geometry Filter = Geometry). In either case, each 

selected element will generate a Packet 06. The element ID is stored in the Header Card, entry ID.



63 


Boundary Conditions form when the Current Load Case Type is Static, LBC Type is Pressure and the 

Target Element Type is 2D. This form is applicable for both element uniform and variable load types. 

The elements and element’s edges can either be explicitly selected (Geometry Filter = FEM) or indirectly 

through their association with one or more geometrical entities (Geometry Filter = Geometry). In either 

case, each selected element will generate a Packet 06. The element ID is stored in the Header Card, 

entry ID.

64 



Structural and Thermal Temperature 

This form defines the Structural and Thermal Temperature LBCs. The associated data will be stored in 

Neutral File Packets 10 (nodal) and 11 (element uniform). The Load Set ID (Header Card, entry IV), is 

controlled by the associated Load Case (see the Load Cases documentation for more details). The 

locations of data within either Packet 10 or 11, as input on these forms, are discussed below.



65 


Conditions form when the Current Load Case Type is Static and the Loads and Boundary Condition Type 

is Temperature. This input data form is applicable for nodal, element uniform and variable temperatures 

loads. Nodal temperature data will be stored in Packet 10 and element temperature data in Packet 11.

66 




Boundary Conditions form when the Current Load Case Type is Static, LBC Type is Nodal Temperature. 

The nodes can either be explicitly selected (Geometry Filter = FEM) or indirectly through their 

association with one or more geometrical entities (Geometry Filter = Geometry). In either case, each 

selected node will generate a Packet 10. The node ID is stored in the Header Card, entry ID.



67 

This subordinate form appears when the Select Application Region button is selected on the LBCs form 

when the Current Load Case Type is Static, LBC Type is Temperature and the Target Element Type is 

3D. This form is applicable for both uniform and variable element temperature loads. The elements can 

either be explicitly selected (Geometry Filter = FEM) or indirectly through their association with one or 

more geometrical entities (Geometry Filter = Geometry). Each selected element will generate a Packet 

11 for uniform loads and one or more Packet 10’s, one for each element node, for variable loads. The 

element ID is stored in the Header Card, entry ID.

68 












69 








70 





71 

Thermal Convection 

This form defines the Thermal Convection LBCs. The associated data will be stored in Neutral File 

Packet 17. The Convection Coefficient Set ID (Header Card, entry IV), is controlled by the associated 

Load Case (see the Load Case documentation for more details). 


Load Case Type is Static, the Target Element Type is 3D and the LBC Type is Thermal Convection.This 

form is applicable for both element uniform and variable convection coefficients. If the load type is 

Uniform, then only one convection coefficient is stored; otherwise, from one to four convection 

coefficients are stored for Variable load types. Uniform load types are indicated by setting the node flag

72 



NFLAG = 0 (Data Card 1). Variable load types are indicated by setting the node flag NFLAG = 1 (Data 

Card 1) and identifying the location and number of element nodes with the eight integer node flags 

NODE (Data Card 1); each node flag is 0 if no coefficient is defined and 1 for a defined coefficient. 


Load Case Type is Static, the Target Element Type is 2D and the LBC Type is Thermal Convection. This 

form is applicable for both element uniform and variable pressures. If the load type is Uniform, then only 

one pressure value is stored; otherwise, from one to four heat flux values are stored for Variable load 

types.



73 


when the Current Load Case Type is Static, LBC Type is Pressure and the Target Element Type is 3D. 

This form is applicable for both element uniform and variable load types. The element’s faces can either 

be explicitly selected (Geometry Filter = FEM) or indirectly through their association with one or more 

geometrical entities (Geometry Filter = Geometry). In either case, each selected element will generate a 

Packet 17. The element ID is stored in the Header Card, entry ID.

74 




when the Current Load Case Type is Static, LBC Type is Thermal Convection and the Target Element 

Type is 2D. This form is applicable for both element uniform and variable load types. The elements can 


more geometrical entities (Geometry Filter = Geometry). In either case, each selected element will 

generate a Packet 17. The element ID is stored in the Header Card, entry ID.



75 

Thermal Heat Flux 

This form defines the Thermal Heat Flux LBCs. The associated data will be stored in Neutral File Packet 

16. The Heat Flux Set ID (Header Card, entry IV), is controlled by the associated Load Case (see the 

Load Case documentation for more details). The locations of data within Packet 16, as input on these 

forms, are discussed below.

76 




Load Case Type is Static, the Target Element Type is 3D and the LBC Type is Thermal Heat Flux. This 

form is applicable for both element uniform and variable heat flux. If the load type is Uniform, then only 

one heat flux value is stored; otherwise, from one to four values are stored for Variable load types. 

Uniform load types are indicated by setting the node flag NFLAG = 0 (Data Card 1). Variable load types 

are indicated by setting the node flag NFLAG = 1 (Data Card 1) and identifying the location and number 

of element nodes with the eight integer node flags NODE (Data Card 1); each node flag is 0 if no heat 

flux is defined and 1 for a defined flux. As heat flux is currently only supported as a per unit area value, 

the dimension code N3 = 2 on Packet 16’s Header Card.



77 


Load Case Type is Static, the Target Element Type is 2D and the LBC Type is Thermal Heat Flux.This 

form is applicable for both element uniform and variable pressures. If the load type is Uniform, then only 

one pressure value is stored; otherwise, from one to four heat flux values are stored for Variable load 

types.

78 




when the Current Load Case Type is Static, LBC Type is Thermal Heat Flux and the Target Element Type 

is 3D. This form is applicable for both element uniform and variable load types. The element’s free faces 

can either be explicitly selected (Geometry Filter = FEM) or indirectly through their association with one 

or more geometrical entities (Geometry Filter = Geometry). In either case, each selected element will 

generate a Packet 16. The element ID is stored in the Header Card, entry ID.



79 


when the Current Load Case Type is Static, LBC Type is Thermal Heat Flux and the Target Element Type 

is 2D. This form is applicable for both element uniform and variable load types. The elements and 

element’s edges can either be explicitly selected (Geometry Filter = FEM) or indirectly through their 

association with one or more geometrical entities 

(Geometry Filter = Geometry). In either case, each selected element will generate a Packet 16. The 


80 





81 

Thermal Heat Source 

This form defines the Thermal Heat Source LBCs. The associated data will be stored in Neutral File 

Packet 15 (Nodal) or 16 (Element Uniform). The Heat Source Set ID (Header Card, entry IV), is 

controlled by the associated Load Case (see the Load Case documentation for more details).

82 




Load Case Type is Static and the LBC Type is Thermal Heat Source. This form is applicable for both 

nodal and element uniform heat sources. If the load type is Nodal, then the heat source data is stored in 

Packet 15 with the node stored on the Header Card, entry ID and the heat source value in entry HEAT on 

Data Card 1. Uniform heat source loads are stored in Packet 16 and are indicated by setting the node flag 

NFLAG = 0 (Data Card 1). The Element ID is stored on the Header Card in the entry ID and the heat 

source value on Data Card 2, entry HEAT. If a uniform element heat source is defined, the dimension 

code N3 = 3 on Packet 16’s Header Card, indicating a per unit volume value. 


when the Current Load Case Type is Static and the LBC Type is Thermal Heat Source. The nodes can 


more geometrical entities (Geometry Filter = Geometry). In either case, each selected node will generate 

a Packet 15. The node ID is stored in the Header Card, entry ID.



83 


when the Current Load Case Type is Static, LBC Type is Element Uniform Thermal Heat Source. The 

elements can either be explicitly selected (Geometry Filter = FEM) or indirectly through their association 

with one or more geometrical entities (Geometry Filter = Geometry). In either case, each selected 

element will generate a Packet 16. The element ID is stored in the Header Card, entry ID.

84 





85 

Thermal View Factor 

This form defines the Thermal View Factor Loads and Boundary Conditions. The associated data will be 

stored in Neutral File Packet 19.

86 




Load Case Type is Static and the LBC Type is Thermal View Factor. This form is valid for 1D, 2D and 

3D elements.



87 

The remaining input on the previous form is as follows. 

This subordinate form appears when the Select Application Region button is selected on the LBCs for3m 

when the Current Load Case Type is Static, LBC Type is Thermal View Factor. The elements can either 

be explicitly selected (Geometry Filter = FEM) or indirectly through their association with one or more 

geometrical entities (Geometry Filter = Geometry). In either case, each selected element will generate a 

Packet 19. The element ID is stored in the Header Card, entry ID.

88 




Load Cases 

89 

Load Cases 

Load Cases in Patran are used to group a series of Loads and Boundary Conditions (LBCs) into one load 

environment for the model. 

Load Cases 

Load case names can be used to control the Loads and Boundary Conditions Set IDs in the neutral file. 

If a load case name is of the format “load_case_name.xxx” where xxx is a valid integer, all associated 

LBCs will retain this number as a Set ID upon export to the neutral file. If no Load Case names use the 

valid integer extension, then the non-empty Load Cases (ones with assigned LBCs) will be sequentially 

numbered beginning from 1. If one or more Load Cases exist with a valid integer extension, the largest 

integer extension is used as the base and all subsequent non-empty Load Cases without a valid integer 

extension are numbered as sequential increments off this value. For more detailed discussions of this 

form, refer to Create Load Cases (p. 162) in the Patran Reference Manual.

90 


Load Cases

Chapter 3: Running an Analysis 


3 Running an Analysis 

 

Review of the Analysis Form 92

92 


Review of the Analysis Form 


The Analysis form appears when the Analysis toggle, located on the Patran switch, is chosen. Currently, 

the available options on the Analysis form are to export and import a PATRAN 2 Neutral File. The 

following pages describe these forms.

Chapter 3: Running an Analysis 


93 

Analysis Form 

This form appears when the Analysis toggle is chosen on the main menu. The Apply button simply 

accesses the File Export or Import form under the File option on the Patran control panel.

94 


Review of the Analysis Form

Chapter 4: Results Templates 


4 Results Templates 

 

Introduction 96 

 

Generic Nodal Results File 97 

 

Generic Element Results File 99

96 


Introduction 

Introduction 

The PATRAN 2 Neutral File Preference provides two generic PATRAN 2 type results file templates. 

PATRAN 2 provided for the import of results, defined in a text file and defined by a template file. Patran 

also supports this means of results import. 

Two generic results templates are delivered with this Preference. The intention is to provide a mechanism 

to import both nodal and element based results. These templates can be copied and edited to match 

specific results file formats. For more information on results file templates, please refer to Patran 2.5 

Results Files (p. 46) in the Patran Reference Manual.


Generic Nodal Results File 

97 


The PATRAN 2 Neutral File Preference includes a generic nodal results template, 

p2nf_nod.res_tmpl. Typically, this template is located in the directory 

$P3_home/res_templates. The following documents the results file contents expected by the 

generic nodal results template. 

Record 

Description 

Record 1 

TITLE, NNODES, MAXNOD, VALMAX, NDMAX, NWIDTH 

Record 2 SUBTITLE 1 


Record 4 to NODID, VAL(1), VAL(2), VAL(3), VAL(4), VAL(5), VAL(6) 

NNODES+3 

Record 

Record 1 

TITLE 

(80A1) 

Description (Format) 

Record 2 

NNODES, MAXNOD, VALMAX, NDMAX, NWIDTH 

(2I9, E15.6, 2I9) 


(80A1) 


(80A1) 

Record 5 to 

NNODES+4 

NODID, (VAL(J), J =1 TO NWIDTH) 

(I8, (5E13.7))

98 



where the parameters are: 

Parameter 

TITLE 

SUBTITLE 1 

SUBTITLE 2 

NNODES 

MAXNOD 

VALMAX 

NDMAX 

NWIDTH 

NODID 

VAL(J) 

Description 

Title (up to 80 characters) 

Same format as TITLE. 


Number of nodes (integer) 

Highest node ID number (integer) 

Maximum absolute nodal result value (real) 

Node ID where VALMAX occurs (integer) 

Number of columns of data (integer) 

Node ID (integer) 

Result value #J (J =1 TO 6) for Node # NODID (real)


Generic Element Results File 

99 


The PATRAN 2 Neutral File Preference includes a generic element results template, 

p2nf_els.res_tmpl. This template is modeled after the PATRAN 2 element stress results file 

template. Typically this template is located in the directory $P3_home/res_templates. The 

following documents the results file contents expected by the generic element results template. 

Record 

Description 

Record 1 

TITLE, NWIDTH 



Record 4 to N+3 ID, NSHAPE, (VAL(J), J=1 TO NWIDTH) 

Record N+4 ID = 0 or end-of-file 

Record 

Record 1 

where the parameters are: 

TITLE 

(80A1) 

Record 2 

NWIDTH 

(I5) 


(80A1) 


(80A1) 

Record 5 to 

NNODES+4 

Description (Format) 

ID, SHAPE, (VAL(J), J =1 TO NWIDTH) 

(2I8, /, (6E13.7)) 

Parameter 

TITLE 

SUBTITLE 1 

SUBTITLE 2 

NWIDTH 

ID 

Description 

Title (up to 80 characters) 



Number of columns of data (integer) 

Element ID (integer)

100 



Parameter 

Description 

NSHAPE Essential shape code (BAR = 2, TRI = 3, QUAD = 4, TET = 5, PYR = 6, 

WEDGE = 7, HEX = 8; integer) 

VAL(J) 

Result value(s) (real) 

The generic element results template is defined such that NWIDTH = 20 where the columns 1 - 6 are 

labeled as “Generic Tensor 1,” columns 7 - 12 as “Generic Tensor 2” and columns 13 - 20 as “Scalar 1,” 

“Scalar 2,”...”Scalar 8,” respectively. The intent of providing this format for the generic elements results 

template is not to force a particular results file format but rather provide an illustration as to how an 

element results file template can be defined to describe a results file format containing both tensor and 

scalar results.

Chapter 5: Files 


5 Files 

 

Files 102

102 


Files 

Files 

These files are associated with the PATRAN 2 Neutral File Preference. 

File Name 

*.db 

*.out 

p2nf_nod.res_tmpl 

p2nf_els.res_tmpl 

Description 

This is the Patran database. This file typically resides in the 

current directory. 

This is the PATRAN 2.5 neutral file. These files typically reside in the 

current directory. 

The generic nodal results template. This file typically resides in the 

/res_templates directory. 

The generic element results template. This file typically resides in the 

/res_templates directory.

Chapter 6: Unsupported Neutral File Packets 


6 

Unsupported Neutral File 

Packets 

 

Unsupported Neutral File Packets 104

104 


Unsupported Neutral File Packets 

Unsupported Neutral File Packets 

The intent of the PATRAN 2 Neutral File Preference is to support as much of the PATRAN 2 Neutral File 

contents as possible. However, a few Data Packets remain unsupported. 

Packet 

Packet 09 

Packet 12 

Packet 13 

Packet 36 

Packet 37 

Packet 38 

Packet 40 

Packet 41 

Packet 46 

Packet 47 

Packet 48 

Description 

Bar element initial displacements 

Degree-of-freedom (DOF) lists 

Mechanism Entities 

Data-line data 

Data-patch data 

Data-hyperpatch data 

LIST card 

DATA card 

Primitive data 

Primitive face data 

Field data (PCL format)

MSC.Fatigue Quick Start Guide 

Index 


Index 

Index 

A 

analysis, 92 

Analysis Preferences, 6 

analysis type, 7 

structural, 7, 25 

thermal, 7, 25 

B 

base.db, 4 

C 

composite materials 

Halpin-Tsai, 41 

Rule of Mixtures, 41 

coordinate frame, 8 

E 

element properties, 46 

generic 0D, 46, 48 




F 

finite elements, 9 

H 

Halpin-Tsai, 41 

L 

LBCs, see load and boundary conditions 

load and boundary conditions, 53 

convection, 53, 71 

displacement, 53, 54 

force, 53, 57 

heat flux, 53, 75 

heat source, 53, 81 

pressure, 53, 60 

temperature, 53, 64 

view factor, 53, 85 

load cases, 89 

load_patran2nf(), 4 

M 

materials, 25 

2D anisotropic, 25, 34 

2D orthotropic, 25, 28 

3D anisotropic, 25, 37 

3D orthotropic, 25, 31 

composite, 25, 41 

composite, also see composite materials, 

41 

isotropic, 25 

laminate, 41 

structural isotropic, 27 

thermal anisotropic, 44 

thermal isotropic, 43 

MPCs, see multi-point constraints 

multi-point constraints, 11 

degrees-of-freedom, 15 

explicit, 13, 16 

linear surface to surface (LSS), 13, 18 

linear surface to volume (LSV), 13, 19 

linear volume to volume (LVV), 13, 20 

quadratic surface to surface (QSS), 14, 21 

quadratic surface to volume (QSV), 14, 22 

quadratic volume to volume (QVV), 14, 23 

rigid (fixed), 13, 17 

rigid (pinned), 13, 17 

slide, 14, 24

106 


N 

neutral file 

export, 93 

import, 93 

Packet 01, 9 

Packet 02, 10 

Packet 03, 25 

Packet 04, 46 

Packet 05, 8 

Packet 06, 60 

Packet 07, 57 

Packet 08, 54 

Packet 09, 104 

Packet 10, 64 

Packet 11, 64 



Packet 14, 11 

Packet 15, 81 

Packet 16, 75, 81 

Packet 17, 71 

Packet 19, 85 









unsupported packets, 104 

nodes, 9 

T 

template.db, 4 

thermal, 7 

U 

unsupported neutral file packets, 104 

P 

patran2nf.plb, 3 

R 

results file templates, 96 

Rule of Mixtures, 41 

S 

structural, 7

Patran 2010 - Classes

Create successful ePaper yourself

Delete template?

Save as template?