Professional Documents
Culture Documents
Preference Guide
Volume 1: Structural Analysis
Corporate Europe Asia Pacific
MSC.Software Corporation MSC.Software GmbH MSC.Software Japan Ltd.
2 MacArthur Place Am Moosfeld 13 Shinjuku First West 8F
Santa Ana, CA 92707 USA 81829 Munich, Germany 23-7 Nishi Shinjuku
Telephone: (800) 345-2078 Telephone: (49) (89) 43 19 87 0 1-Chome, Shinjuku-Ku
Fax: (714) 784-4056 Fax: (49) (89) 43 61 71 6 Tokyo 160-0023, JAPAN
Telephone: (81) (3)-6911-1200
Fax: (81) (3)-6911-1201
Worldwide Web
www.mscsoftware.com
Disclaimer
This documentation, as well as the software described in it, is furnished under license and may be used only in accordance with
the terms of such license.
MSC.Software Corporation reserves the right to make changes in specifications and other information contained in this document
without prior notice.
The concepts, methods, and examples presented in this text are for illustrative and educational purposes only, and are not
intended to be exhaustive or to apply to any particular engineering problem or design. MSC.Software Corporation assumes no
liability or responsibility to any person or company for direct or indirect damages resulting from the use of any information
contained herein.
User Documentation: Copyright 2009 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*2008R2*Z*INT-NA*Z* DC-USR
Contents
Patran Interface to MD Nastran Preference Guide
Patran Interface
MD Nastran Pre
ence Guide,
1 Overview
Purpose 2
Using Patran with SOL 700 2
2 Building A Model
Introduction to Building a Model 6
Coordinate Frames 22
Finite Elements 23
Nodes 23
Elements 24
Multi-point Constraints 27
MPC Types 28
Degrees of Freedom 31
Superelements 56
ii Patran Interface to MD Nastran Preference Guide
Material Library 59
Materials Application Form 59
Material Input Properties Form 61
Material Constitutive Models 62
Linear Elastic 73
Nonlinear Elastic 74
Hyperelastic 75
Elastoplastic 78
Failure 81
Failure 1, Failure 2, Failure 3 82
Creep 84
Viscoelastic 85
Composite 85
Element Properties 87
Element Properties Form 87
Coupled Point Mass (CONM1) 91
Grounded Scalar Mass (CMASS1) 93
Lumped Point Mass (CONM2) 94
Grounded Scalar Spring (CELAS1/CELAS1D) 96
Grounded Scalar Damper (CDAMP1/CDAMP1D) 98
Bush 99
General Section Beam (CBAR) 102
P-Formulation General Beam (CBEAM) 107
Curved General Section Beam (CBEND) 110
Curved Pipe Section Beam (CBEND) 113
Lumped Area Beam (CBEAM/PBCOMP) 115
Tapered Beam (CBEAM) 119
General Section Beam (CBEAM) 124
General Section Rod (CROD) 131
General Section Rod (CONROD) 134
Pipe Section Rod (CTUBE) 136
Scalar Spring (CELAS1/CELAS1D) 137
Scalar Damper (CDAMP1/CDAMP1D) 139
Viscous Damper (CVISC) 141
Gap (CGAP) 142
Scalar Mass (CMASS1) 144
PLOTEL 146
(Scalar) Bush 146
Spot Weld Connector (CWELD) 150
Fastener Connector (CFAST) 152
Standard Homogeneous Plate (CQUAD4) 155
Revised Homogeneous Plate (CQUADR) 158
CONTENTS iii
3 Running an Analysis
Review of the Analysis Form 260
Analysis Form 261
Overview of Analysis Job Definition and Submittal 263
Subcases 354
Deleting Subcases 355
Editing Subcases 356
Optimize 463
Optimization Parameters 467
Subcases 471
Subcase Parameters 474
Subcase Select Optimize 475
Customized Solutions (Topology Optimization) 476
Design Domain 479
Objectives & Constraints 479
Optimization Control 479
Postprocessing 479
Scenario 1 480
Scenario 2 480
The Process 481
Miscellaneous 481
Analysis Form 482
Select Modal Results .DBALL 484
Loading Form 484
Create a Field Form 488
Output Selection Form 489
Define Frequencies Form 490
4 Read Results
Accessing Results 492
Results File Formats 493
Output2 Formats 493
XDB Formats 493
MASTER Formats 494
T16/T19 Formats 495
3dplot Formats 495
Translation Parameters 496
OUTPUT2 496
Defining Translation Parameters for DDAM (SOL 187) 497
XDB 498
MASTER 499
T16/T19 501
6 Delete
Review of Delete Form 568
7 Files
Files 572
CONTENTS ix
8 Errors/Warnings
Errors/Warnings 576
Index 583
x Patran Interface to MD Nastran Preference Guide
Chapter 1: Overview
Patran Interface to MD Nastran Preference Guide
Overview
1
Purpose 2
MD Nastran Product Information 3
2 Patran Interface to MD Nastran Preference Guide
Purpose
1.1 Purpose
Patran is an analysis software system developed and maintained by MSC.Software Corporation. The core
of the system is a finite element analysis pre and postprocessor. Several optional products are available
including; advanced postprocessing programs, tightly coupled solvers, and interfaces to third party
solvers. This document describes one of these interfaces.
The Patran MD Nastran interface provides a communication link between Patran and MD Nastran. It also
provides for the customization of certain features in Patran. The interface is a fully integrated part of the
Patran system.
Selecting MD Nastran as the analysis code preference in Patran, activates the customization process.
These customizations ensure that sufficient and appropriate data is generated for the Patran MD Nastran
interface. Specifically, the Patran forms in these main areas are modified:
• Materials
• Element Properties
• Finite Elements/MPCs and Meshing
• Loads and Boundary Conditions
• Analysis Forms
More information on these topics is contained in Preference Configuration and Implementation (App. A).
The analysis preference also specifies that the model information be output in the MD Nastran Input
File format.
Chapter 1: Overview 3
MD Nastran Product Information
Building A Model
2
Introduction to Building a Model 6
Currently Supported MD Nastran Input Options 8
Adaptive (p-Element) Analysis with the Patran MD Nastran Preference 18
Coordinate Frames 22
Finite Elements 23
Material Library 59
Element Properties 87
Beam Modeling 217
Loads and Boundary Conditions 224
Load Cases 246
Defining Contact Regions 247
Rotor Dynamics 250
6 Patran Interface to MD Nastran Preference Guide
Introduction to Building a Model
The analysis code may be changed at any time during model creation.This is especially useful if the
model is to be used for different analyses in different analysis codes. As much data as possible will be
converted if the analysis code is changed after the modeling process has begun. The analysis option
defines what will be presented to the user in several areas during the subsequent modeling steps.
These areas include the material and element libraries, including multi-point constraints, the applicable
loads and boundary conditions, and the analysis forms. The selected Analysis Type may also affect the
Chapter 2: Building A Model 7
Introduction to Building a Model
allowable selections in these same areas. For more details, see The Analysis Form (Ch. 2) in the
MSC.Patran Reference Manual.
Command Pages
ADAPT 16, 170, 225, 233
BEGIN AFPM 147
BEGIN SUPER 219
BCONP 212
BFRIC 212
BFRIC 212
CACINF3 160
CACINF4 160
CBARAO 86
CBAR 86
CBEAM 97, 100
CBEND 93, 95
CDAMP1 82
CDAMP2 219, 438
CELAS1 81
CELAS2 219, 438
CGAP 116
CHEXA 168
CMASS1 119
CMASS2 219, 438
CONM1 76
CONM2 79
CONROD 111
CPENTA 168
CQUAD4 124, 140, 148, 156, 162
CQUAD8 124, 140, 148, 156, 162
CQUADR 131, 142, 150, 157, 163
Command Pages
CROD 110
CSHEAR 166
CTETRA 168
CTRIAX6 153
Chapter 2: Building A Model 11
Currently Supported MD Nastran Input Options
CTUBE 112
CVISC 115
DCONST 416
DOPTPRM 411, 416
DPHASE 188, 190
DRESP1/2 416
DTI, SETREE 309
DYNRED 240
EIGB 243, 238
EIGC 248
EIGR 238
EIGRL 238
EXTSEOUT 222
FEFACE 15
FEEDGE 15
FORCE 190
FREQ1 250
GMBC 188
GRAV 196
MOMENT 190
MAT1 424
MAT2 424
MAT3 424
MAT8 424
MAT9 424
MPC 28
NLPARM 315
OUTPUT 17, 369
PACINF 160
PARAM, 230, 233, 235, 241, 245, 250,
AUTOSPC 253, 256
PARAM, 230
INREL
PARAM, 230
ALTRED
12 Patran Interface to MD Nastran Preference Guide
Currently Supported MD Nastran Input Options
Pages
PROD 110
PSHEAR 166
PSHELL 124, 131, 140, 142, 148, 150,
156, 157, 162, 163
PSHELL1
PSHELLD
PSOLID 168
PSPRMA
PTUBE 112
PBEAM 100
PVAL 15, 170
PVISC 115
RBAR 29
RBE1 31
RBE2 32
RBE3 33
RFORCE 196
RROD 34
RSPLINE 35
RTRPLT 36
SESET 42, 219
SETREE 309
SPC1 188
SPCD 188
TEMP 193
TEMPF 146
TEMPRB 193
TEMPP1 193
TIC 197, 198
TSTEP 253
TSTEPNL 256, 318
14 Patran Interface to MD Nastran Preference Guide
Currently Supported MD Nastran Input Options
Initial Conditions
Materials
Note:
Note: Element Properties
NTHICK Defines nodal thickness values for beams, plates, and/or shells.
Materials
MATD001 Isotropic Elastic material for beam, shell and solid.
MATD003 Isotropic and kinematic hardening plasticity.
MATD005 Isotropic materials to model soil and foam.
MATD006 Isotropic viscoelastic material.
MATD007 Isotropic material to model nearly incompressible continuum rubber.
MATD012 Isotropic plasticity for 3D solids.
MATD014 Isotropic materials to model soil and foam with failure.
MATD015 Isotropic Johnson/Cook strain and temperature sensitive plasticity.
MATD019 Isotropic strain rate dependent material.
MATD020 Isotropic rigid material.
MATD022 Orthotropic material with optional brittle failure for composites.
MATD024 Isotropic elasto-plastic material with stress x strain curve and strain rate
dependency.
MATD026 Anisotropic honeycomb and foam material.
MATD027 Isotropic material to model rubber using two variables.
MATD028 Isotropic elasto-plastic material for beam and shell.
16 Patran Interface to MD Nastran Preference Guide
Currently Supported MD Nastran Input Options
MATDS06 *MAT_SPRING_GENERAL_NONLINEAR
MATDS07 *MAT_SPRING_MAXWELL
MATDS08 *MAT_SPRING_INELASTIC
MATDS13 *MAT_SPRING_TRILINEAR_DEGRADING
MATDS14 *MAT_SPRING_SQUAT_SHEARWALL
MATDS15 *MAT_SPRING_MUSCLE
Solution Controls
Form Parameters
Execution Control DYSTATIC, DYBLDTIM, DYINISTEP, DYTSTEPERODE,
Parameters DYMINSTEP, DYMAXSTEP, DYSTEPFCTL, DYTERMNENDMAS,
DYTSTEPDT2MS
General Parameters DYLDKND, DYCOWPRD, DYCOWPRP, DYBULKL, DYHRGIHQ,
DYRGQH, DYENERGYHGEN, DYSHELLFORM, DYSHTHICK,
DYSHNIP
Contact Parameters DYCONSLSFAC, DYCONRWPNAL, DYCONPENOPT,
DYCONTHKCHG, DYCONENMASS, DYCONECDT, DYCONIGNORE,
DYCONSKIPTWG
Binary Output DYBEAMIP, DYMAXINT, DYNEIPS, DYNINTSL, DYNEIPH,
Database File DYSTRFLG, DYSIGFLG, DYEPSFLG, DYRLTFLG, DYENGFLG,
Parameters DYCMPFLG, DYIEVERP, DYDCOMP, DYSHGE, DYSTSSZ,
DYN3THDT
Element Creation
MD Nastran supports adaptive, p-element analyses with the 3D-solid CTETRA, CPENTA, and CHEXA
elements; 2D-solid TRIA, and QUAD elements; shells TRIA, and QUAD elements; beams BAR
elements. Patran and MD Nastran allow TET4, TET10, TET16, TET40, WEDGE6, WEDGE15,
WEDGE52, HEX8, HEX20, and HEX64 for p-adaptive analysis for 3D-solids; TRIA3, TRIA6, TRIA7,
TRIA9, TRIA13, QUAD4, QUAD8, QUAD9, QUAD12, and QUAD16 for p-adaptive analysis for 2D-
solids and membranes; TRIA3, TRIA6, TRIA7, TRIA9, TRIA13, QUAD4, QUAD8, QUAD9,
QUAD12, and QUAD16 for p-adaptive analysis for shells; BAR2, BAR3, and BAR4 for p-adaptive
analysis for beams. The preferred approach, when beginning a new model, is to use the higher-order
elements--HEX64, WEDGE52, TET40, and TET16, or TRIA13 and QUAD16, or BAR4. The support
for lower-order elements is provided primarily to support existing models. The higher-order cubic
elements allow more accurate definition of the geometry and more accurate postprocessing of results
from the MD Nastran analysis.The translator generates the appropriate MD Nastran FEEDGE and
POINT entities for all curved edges on the p-elements. Models with HEX64 and WEDGE52 elements
are easily created with the Patran Iso Mesher; models with TET16 elements can be created with the Tet
Mesher. Models with QUAD16 and TRIA13 elements can be created using the Iso Mesher or the Paver.
For p-elements, Patran generates cubic edges to fit the underlying geometry. The cubic edge consists of
two vertex grid points and two points in between. Adjacent cubic edges are not necessarily C1
continuous. If the original geometry is smooth, the cubic edges may introduce kinks which cause false
stress concentrations. Then, the p-element produces unrealistic results especially for thin curved shells.
In Version 7 of Patran, for cubic elements, the two midside nodes on each edge are adjusted so that the
edges of adjacent elements are C1 continuous. The adjustment is done in the Pat3Nas translator. After
the Pat3Nas translator is executed, the location of the two midside nodes in the Patran database has
changed. The user is informed with a warning message. The user can turn the adjustment of midside
nodes ON and OFF with the environment variable PEDGE_MOVE. By default, the midside nodes are
adjusted to make the adjacent elements C1 continuous. For PEDGE_MOVE set to OFF, the points on a
cubic edge are not adjusted.
Patran generates the input for MD Nastran. For cubic edges, FEEDGE Bulk Data entries with POINTs
are written. By default, the location of the two POINTs is moved to 1/3 and 2/3 of the edge in MD
Nastran. The points generated by Patran must not be moved. Therefore, a parameter entry PARAM,
PEDGEP, 1 is written by Patran. PEDGEP=1 indicates that incoming POINTs are not moved in MD
Chapter 2: Building A Model 19
Adaptive (p-Element) Analysis with the Patran MD Nastran Preference
Nastran. The default is PEDGEP= 0, MD Nastran will move the two POINTs to 1/3 and 2/3 of the edge.
The C1 continuous cubic edges improve the accuracy of p-element results.
In the Version 69 Release Guide, a cylinder under internal pressure was tested to determine the quality
of shell p-elements for curved geometry. The accuracy of the results was very good when exact geometry
was used. With C1 continuous edges we recover the same quality of results within single precision
accuracy.
faces of solid elements. If the elements are p-elements, the appropriate FEFACE and GMBC entries are
produced. If applied to non-p-elements, the appropriate SPC1 or SPCD entries are produced.
Several new loads and boundary conditions support the p-shell and p-beam elements. Distributed loads
can be applied to beam elements or to the edge of shell elements. Pressure loads can be applied to the
faces of p-shell elements. Temperature loads can be applied to either the nodes or the elements.
Analysis Definition
Adaptive linear static and normal modes analyses are supported in Version 68 of MSC .Nastran; both
solution types are supported by the Patran MD Nastran Preference. Only a few parameters on the
Analysis forms may need to be changed for p-element analyses. If running a version of MSC . Nastran
prior to Version 68.2 (i.e., Version 68, or 68.1), the OUTPUT2 Request option on the Translation
Parameters form must be set to Alter File in order to process the results in Patran. The Solution
Parameters forms for the linear static and normal modes analyses contain a Max p-Adaptive Cycles
option, which is defaulted to 3. The Subcase Parameters form under Subcase Create has options to limit
the participation of this subcase in the adaptive error analysis. Finally, the Advanced Output Requests
form under Subcase Create has an option to define whether results are to be produced for all adaptive
cycles or only every nth adaptive cycle.
p-elements will be written only for the last cycle. If postprocessing of results from intermediate cycles is
desired, the Adaptive Cycle Output Interval option should be set equal to one.
One of the key uses of output from intermediate adaptive cycles is in examining the convergence of
selected quantities (e.g., stresses). This can be done using the X-Y plotting capability under the Results
application.
Potential Pitfalls
There are several areas where a user can encounter problems producing correct p-element models for MD
Nastran. One is the incorrect usage of the midside nodes in the Patran higher order-elements. These nodes
are used in p-element analysis only for defining the element geometry; analysis degrees of freedom are
not associated with these nodes. Therefore it is illegal, for example, to attach non p-elements to assign
loads or boundary conditions to these nodes. One way this can occur inadvertently is if a nodal force is
applied to the face of a Patran solid. This force is interpreted as a point force at every node (including the
midside nodes) on the face of the solid. For the p-elements, this is not valid. This type of load should
instead be applied as an element uniform or element variable pressure.
Only Coordinate Frames that are referenced by nodes, element properties, or loads and boundary
conditions can be translated. For more information on creating coordinate frames see Creating
Coordinate Frames (p. 393) in the Geometry Modeling - Reference Manual Part 2.
To output all the coordinate frames defined in the model whether referenced or not, set the environment
variable “WRITE_ALL_COORDS” to ON.
Chapter 2: Building A Model 23
Finite Elements
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 unique GRID Bulk Data entries in MD Nastran. Nodes can be created
either directly using the Node object, or indirectly using the Mesh object. Each node has associated
Reference (CP) and Analysis (CD) coordinate frames. The ID is taken directly from the assigned node
24 Patran Interface to MD Nastran Preference Guide
Finite Elements
ID. The X1, X2, and X3 fields are defined in the specified CP coordinate frame. If no reference frame is
assigned, the global system is used. The PS and SEID fields on the GRID entry are left blank.
Elements
The Finite Elements Application in Patran assigns element connectivity, such as Quad4, for standard
finite elements. The type of MD Nastran element to be created is not determined until the element
properties are assigned (for example, shell or 2D solid). See the Element Properties Form, 87 for details
concerning the MD Nastran element types. Elements can be created either directly using the Element
object, or indirectly using the Mesh object
Chapter 2: Building A Model 25
Finite Elements
.
26 Patran Interface to MD Nastran Preference Guide
Finite Elements
This “ghosted” area will become dark when an element property is selected.
Chapter 2: Building A Model 27
Finite Elements
Multi-point Constraints
Multi-point constraints (MPCs) can also be created from the Finite Elements Application. These are
special element types that 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. The full
functionality of the MPC forms are defined in Create Action (FEM Entities).
MPC Types
To create an MPC, first select the type of MPC to be created from the option menu. The MPC types that
appear in the option menu are dependent on the current settings of the Analysis Code and Analysis Type
preferences. The following table describes the MPC types which are supported for MD Nastran.
Degrees of Freedom
Whenever a list of degrees of freedom is 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 MD Nastran MPCs for the various analysis
types:
Note: 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.
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. This form is used to create an MD Nastran MPC Bulk Data entry.
The difference in explicit MPC equations between Patran and MD Nastran will result in the A1 field of
the MD Nastran entry being set to -1.0.
32 Patran Interface to MD Nastran Preference Guide
Finite Elements
Rigid (Fixed)
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and Rigid (Fixed) is the selected type. This form is used to create an MD Nastran RBE2 Bulk Data
entry. The CM field on the RBE2 entry will always be 123456.
RBAR MPCs
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RBAR is the selected type. This form is used to create an MD Nastran RBAR Bulk Data entry
and defines a rigid bar with six degrees of freedom at each end. Both the Dependent Terms and the
Independent Terms lists can have either 1 or 2 node references. The total number of referenced nodes,
Chapter 2: Building A Model 35
Finite Elements
however, must be 2. If either or both of these lists references 2 nodes, then there must be an overlap in
the list of referenced nodes.
Holds the
independent term
information. Either
one or two nodes
may be defined as
having independent
terms.The Nodes
define the GA and
GB fields on the
RBAR entry.The
DOFs define the CNA
and CNB fields.
36 Patran Interface to MD Nastran Preference Guide
Finite Elements
RBE1 MPCs
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RBE1 is the selected type. This form is used to create an MD Nastran RBE1 Bulk Data entry.
Chapter 2: Building A Model 37
Finite Elements
Holds the
independent term
information. Defines
the GNi and CNi
fields on the RBE1
entry. The total
number of Node/DOF
pairs defined must
equal 6, and be
capable of
representing any
general rigid body
motion.
38 Patran Interface to MD Nastran Preference Guide
Finite Elements
RBE2 MPCs
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RBE2 is the selected type. This form is used to create an MD Nastran RBE2 Bulk Data entry.
Chapter 2: Building A Model 39
Finite Elements
RBE3 MPCs
40 Patran Interface to MD Nastran Preference Guide
Finite Elements
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RBE3 is the selected type. This form is used to create a MD Nastran RBE3 Bulk Data entry.
Chapter 2: Building A Model 41
Finite Elements
RROD MPCs
42 Patran Interface to MD Nastran Preference Guide
Finite Elements
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RROD is the selected type. This form is used to create an MD Nastran RROD Bulk Data entry.
Chapter 2: Building A Model 43
Finite Elements
RSPLINE MPCs
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RSPLINE is the selected type. This form is used to create an MD Nastran RSPLINE Bulk Data
entry. The D/L field for this entry is defined on the main MPC form. This MPC type is typically used to
tie together two dissimilar meshes.
Chapter 2: Building A Model 45
Finite Elements
Holds the
dependent term
information.
Determines
what sequence
the independent
and dependent
terms will be
written to the
RSPLINE entry.
RTRPLT MPCs
46 Patran Interface to MD Nastran Preference Guide
Finite Elements
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RTRPLT is the selected type. This form is used to create an MD Nastran RTRPLT Bulk Data
entry.
Chapter 2: Building A Model 47
Finite Elements
The Cyclic Symmetry MPC created by this form will be translated into CYJOIN, CYAX, and CYSYM
entries if cyclic symmetric is the selected type, see Solution Parameters, 277, or into SPC and MPC
entries if the requested type is not explicitly cyclic symmetric.
RBAR1 MPCs
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
50 Patran Interface to MD Nastran Preference Guide
Finite Elements
form and RBAR1 is the selected type. This form is used to create an MD Nastran RBAR1 Bulk Data
entry.
Chapter 2: Building A Model 51
Finite Elements
RTRPLT1 MPCs
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RTRPLT1 is the selected type. This form is used to create an MD Nastran RTRPLT1 Bulk Data
52 Patran Interface to MD Nastran Preference Guide
Finite Elements
entry.
Chapter 2: Building A Model 53
Finite Elements
RJOINT MPCs
This subordinate MPC form appears when the Define Terms button is selected on the Finite Elements
form and RJOINT is the selected type. This form is used to create an MD Nastran RJOINT Bulk Data
54 Patran Interface to MD Nastran Preference Guide
Finite Elements
entry.
Chapter 2: Building A Model 55
Finite Elements
.
56 Patran Interface to MD Nastran Preference Guide
Finite Elements
Superelements
In superelement analysis, the model is partitioned into separate collections of elements. These smaller
pieces of structure, called Superelement, are first solved as separate structures by reducing their stiffness
matrix, mass matrix, damping matrix, loads and constraints to the boundary nodes and then combined to
solve for the whole structure. The first step in creating a superelement is to create a Patran group (using
Group/Create) that contains the elements in the superelement. This group is then selected in the Finite
Elements application on the Create/ Superelement form.
Chapter 2: Building A Model 57
Finite Elements
List of existing
superelements.
3
• Coefficients • Mooney Order:
Rivlin
1
• Ogden
• Foam 2
• Arruda-Boyce
3
• Gent
4
5
• Elastoplastic • Stress/Strain • von Mises • Isotropic
Curve • Tresca • Kinematic
• Mohr- • Combined
Coulomb
• Drucker-
Prager
Chapter 2: Building A Model 63
Material Library
• Drucker-
Prager
• Oak
Ridge
National
Labs
• 2-1/4 Cr-
Mo
ORNL
• Reversed
Plasticit
y ORNL
• Fully
Alpha
Reset
ORNL
• Generalize
d
Plasticit
y
Chapter 2: Building A Model 67
Material Library
Additional materials for Explicit Nonlinear (SOL 700) are listed in the following table.
Linear Elastic
The Input Properties form displays the following for linear elastic properties. The translator produces
MAT1 entries for isotropic materials, MAT8 entries for 2D orthotropic materials, MAT3 entries using
axisymmetric solid elements or MAT9 entries using 3D solid elements (CHEXA, CPENTA, CTETRA)
for 3D orthotropic materials, MAT2 entries for 2D plane stress - 2D anisotropic materials, and MAT9
entries for 3D anisotropic materials. For temperature dependencies, the corresponding MATTi entries are
written referencing TABLEMi entries. Temperature dependency is defined using material fields defined
under the Fields application. SOL 600 jobs using 3D Orthotropic material the MATORT entry is written.
Isotropic Description
Elastic Modulus Elastic modulus, E, (Young’s modulus). Can be temperature
dependent.
Poisson Ratio Poisson’s ratio (NU). Can be temperature dependent. Should be
between -1.0 and 0.5.
Shear Modulus Shear modulus (G). Can be temperature dependent.
Density Density (RHO). Can be temperature dependent.
Thermal Expansion Coefficient Thermal coefficient of expansion (A). Can be temperature
dependent.
Structural Damping Coefficient Structural damping coefficient (GE). Can be temperature
dependent.
Reference Temperature Reference temperature (TREF).
Nonlinear Elastic
The Input Properties form displays the following for nonlinear elastic properties. Use this form to define
the nonlinear elastic stress-strain curve on the MATS1 entry. A stress-strain table defined using the Fields
application can be selected on this form. Based on this information the translator will produce MATS1 of
type NLELAST and TABLES1 entries. This is used primarily for SOL 106 and 129. This option is not
supported by SOL 600. Use an elastoplastic constitutive model instead.
Isotropic Description
Stress/Strain Curve Defines the nonlinear elastic stress-strain curve. You must select
a field from the listbox. It can be strain and/or temperature
dependent. Tabular definition of the stress-strain curve via the
Fields application using a material field of strain should follow
the specifications as outlined by Nastran. The first point of the
material field should be the origin and the second point must be at
the initial yield point. This material curve is elastic, meaning that
in both loading and unloading the material behavior follows the
stress-strain curve as defined. It is not recommended that both
nonlinear elastic and elastoplastic constitutive models be active or
defined for the same material. For work hardening, use the
Elastoplastic constitutive model. See the Nastran Quick
Reference Guide for more details.
Chapter 2: Building A Model 75
Material Library
Hyperelastic
The Input Properties form displays the following for hyperelastic properties. Use this form to define the
data describing hyperelastic behavior of a material. This data is placed on MATHP and TABLES1 entries
or on the MATHE entry for SOL 600.
If you select Test Data as the Data Type, the Input Options form reverts to the form used for non-SOL
600 solutions and data is placed on a MATHP entry (Mooney-Rivlin strain energy model). To use test
data for MATHE/SOL 600 runs, use the Experimental Data Fitting features under the Tools menu to
determine the coefficients and enter them manually.
If Coefficients is selected as the Data Type, use the form to describe the strain energy potential. The
Mooney Rivlin model can be written out as a MATHP or MATHE entry for SOL 600. Make sure you use
the one that is consistent with the solution to be run. Ogden, Foam, Arruda-Boyce, and Gent models are
used for SOL 600 MATHE entries only.
Ogden Description
Bulk Modulus K Defines the Bulk Modulus.
Density RHO Defines the material mass density.
Coefficient of Thermal Defines the instantaneous coefficient of thermal
Expansion expansion. This property is optional. May vary with
temperature via a defined material field
Reference Temperature TREF Defines the reference temperature for the thermal
expansion coefficient.
Modulus k k in the Ogden equation. The number of
moduli required as input is dependent on the Order
of the Polynomial.
Exponent k k in the Ogden equation. The number of
exponents required as input is dependent on the
Order of the Polynomial.
Foam Description
Bulk Modulus K Defines the Bulk Modulus.
Density RHO Defines the material mass density.
Chapter 2: Building A Model 77
Material Library
Foam Description
Thermal Expansion Coefficient Defines the instantaneous coefficient of thermal
expansion. This property is optional. May vary with
temperature via a defined material field
Reference Temperature TREF Defines the reference temperature for the thermal
expansion coefficient.
Modulus n un in the Foam equation. The number of moduli
required as input is dependent on the Order of the
Polynomial.
Deviatoric Exponent n n in the Foam equation. The number of
exponents required as input is dependent on the Order
of the Polynomial.
Volumetric Exponent n n in the Foam equation. The number of
exponents required as input is dependent on the Order
of the Polynomial.
78 Patran Interface to MD Nastran Preference Guide
Material Library
Gent Description
Tensile Modulus Defines standard tension modulus (E). May vary with
temperature via a defined material field.
Elastoplastic
The Input Properties form displays the following for elastoplastic properties. Use this form to define the
data describing plastic behavior of a material. The stress-strain curve data is input via a material property
field of strain and placed on MATS1 and TABLES1 entries. The data input should be the true equivalent
stress vs. equivalent total strain. Other options are placed on the MATEP entry and are valid only for SOL
Chapter 2: Building A Model 79
Material Library
400 & 600. Note that the existence of both an elastoplastic and nonlinear elastic constitutive models in
the same material is not recommended.
Stress at Yield
Beta Parameter beta for parabolic Mohr-Coulomb or
Buyukozturk concrete models. Placed on the
MATEP entry.
10th Cycle Yield Stress Equivalent 10th cycle tensile yield stress for Oak
Ridge National Labs models (ORNL). Placed on the
MATEP entry.
Denominator C Constants for the Cowper-Symonds strain rate
method.
Inverse Exponent P
80 Patran Interface to MD Nastran Preference Guide
Material Library
Melt Temperature
See the Nastran Quick Reference Guide for more information about the necessary data for MATS1 and
MATEP entries.
Failure
The Input Properties form displays the following for failure material models. Note that this failure model
is for non-SOL 400/600/700 solutions. See Failure 1/2/3 for SOL 400/600/700.
• Hashin-Fabric
Property Description
Progressive Failure Options Progressive failure options are None, standard
Progressive Failure, Gradual or Immediate selective
progressive failure for SOL 600. SOL 400 does not
support progressive failure models and will ignore
this setting if set to anything other than None. Only
failure indices are computed when no progressive
failure is specified. Anisotropic materials do not
support progressive failure.
Tension Stress Limit X / Y /Z Tension, compression, and shear stress or strain
Tension Strain Limit X / Y / Z limits used in the Maximum Stress or Strain, Hill,
Hoffman, and Tsai-Wu failure criteria.
Compression Stress Limit X / Y / Z
Compression Strain Limit X / Y / Z
Property Description
Deactivate Tension X / Y/ Z If any value other than blank or 0.0 is entered for
Deactivate Compress X / Y / Z progressive failure options Gradual and Immediate,
Deactivate Shear XY / YZ / ZX failed elements are deactivated (placed ICi fields in
MATF entry). See the Nastran Quick Reference
Deactivate Elements Guide for information.
Creep
The Input Properties form displays the following for creep models.
MATPV Description
Use this form to define either the coefficients and exponents for creep model or provide tabular field
data to define Temperature vs. Creep Strain, Creep Strain Rate vs. Stress, Strain Rate vs. Creep Strain,
or Time vs. Creep Strain in SOL 600 runs. This data is written to the MATVP entry. If tabular data is
provided, this data is written to TABLEM1 entries. It is not recommended to mix the exponents and
coefficients and tabular data. Use one or the other.
Chapter 2: Building A Model 85
Material Library
Viscoelastic
The Input Properties form displays the following for viscoelastic models. This material model is only
used in SOL 600 runs and all data is placed on the MATVE, MATTVE entries. Linear elastic or
hyperelastic constitutive models for isotropic or anisotropic materials must exist in addition to the
viscoelastic model.
Composite
The Composite forms provide alternate ways of defining the linear elastic properties of materials. All the
composite options, except for Laminated Composite, will always result in a homogeneous elastic
material in MD Nastran.
When the Laminated Composite option is used to create a material and this material is then referenced in
a “Revised or Standard Laminate Plate” element property region, a PCOMP entry is created. However,
if this material is referenced by a different type of element property region, for example, “Revised or
Standard Homogeneous Plate,” then the equivalent homogeneous material properties are used instead of
the laminate lay-up data. Only materials created through the Laminated Composite option should be
referenced by a “Revised or Standard Laminate Plate” element property region. Refer to Composite
Materials Construction (p. 116) in the Patran Reference Manual.
Laminated
This subordinate form appears when the Input Properties button is selected on the Materials form,
Composite is the selected Object, and Laminate is the selected Method. Use this form to define the
laminate lay-up data for a composite material. If the resulting material is referenced in a “Revised or
Standard Laminate Plate” element property region, then an MD Nastran PCOMP entry containing the
lay-up data is written. If the resulting material is referenced by any other type of element property region,
the equivalent homogeneous properties of the material are used
86 Patran Interface to MD Nastran Preference Guide
Material Library
.
Chapter 2: Building A Model 87
Element Properties
0D (point elements)
1D (bar elements)
2D (tri and quad elements)
3D (tet, wedge, and hex elements)
The following table outlines the option menus when Analysis Type is set to Structural.
• • Revised
• P-element
• Membrane • Standard
• Revised
•
• P-Formulation
• • Shear Panel
Use this form to create a CONM1 element. This defines a 6 x 6 symmetric mass matrix at a geometric
point of the structural model.
92 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the
orientation of
the 1-2-3 axes
of the mass
matrix. The
value is a
reference to
an existing
coordinate
frame. The 1-
2-3 axes will
be aligned with
the X-Y-Z axes
of the
specified
coordinate
system. If a
non
rectangular
coordinate
system is
specified, the
system will be
evaluated into
a local
rectangular
system, which
is then used to
orient the
mass matrix.
This property
is the CID field
on the CONM1
entry. This
property is
optional.
Defines the values of the mass matrix. These properties are the Mij fields on the CONM1 entry
and can either be real values or references to existing field definitions. Each of these properties
are optional; however, at least one must be defined.
Chapter 2: Building A Model 93
Element Properties
This is a list of Input Properties available for creating a CONM1 element that were not shown on the
previous page. Use the menu scroll bar on the Input Properties form to view these properties.
Use this form to create a CMASS1 element and a PMASS property. This defines a scalar mass element of
the structural model. Only one node is used in this method, and the other node is defined to be grounded.
94 Patran Interface to MD Nastran Preference Guide
Element Properties
Use this form to create a CONM2 element. This defines a concentrated mass at a geometric point of the
structural model.
Chapter 2: Building A Model 95
Element Properties
Defines an offset from the specified node to Defines the translational mass value to be
where the lumped mass actually is to exist in used. This is the M field on the CONM2
the structural mode. This vector is defined in entry. This property can either be a real
the Mass Orientation coordinate system. value or a reference to an existing field
Defines the X1, X2, and X3 fields on the definition. This property is required.
CONM2 entry. This property is optional.
This is a list of Input Properties available for creating a CONM2 element that were not shown on the
previous page. Use the menu scroll bar on the Input Properties form to view these properties.
96 Patran Interface to MD Nastran Preference Guide
Element Properties
Use this form to create a CELAS1 or CELAS1D (for SOL 700) element and a PELAS property. This
defines a scalar spring element of the structural model. Only one node is used in this method. The other
node is defined to be grounded.
Defines the coefficient to be used for this spring. This is the K field on the PELAS entry.
This can either be a real value or a reference to an existing field definition. This property
is required.
Defines which degree of freedom this value is to be attached to. This can be set to UX, UY, UZ,
RX, RY, or RZ. This property defines the setting of the C1 field on the CELAS1 entry. This
property is required.
98 Patran Interface to MD Nastran Preference Guide
Element Properties
Use this form to create a CDAMP1 or CDAMP1D (for SOL 700) element and a PDAMP property. This
defines a scalar damper element of the structural model. Only one node is used in this method. The other
node is defined to be grounded.
Bush
This subordinate form appears when the Input Properties button is selected on the Element
Properties form and the following options are chosen.
This is a list of Input Properties available. Use the menu scroll bar on the Input Properties form to view
these properties.
Use this form to create a CBAR element and a PBAR or PBARL property. A CBARAO entry will be
generated if any Station Distances are specified. This defines a simple beam element in the structural
model.
Note: CBAR entries will include all user input pin flags.
104 Patran Interface to MD Nastran Preference Guide
Element Properties
Section Name Specifies a beam section previously created using the beam library
• Value Type Allows you to define a bar/beam section either by Dimensions
(PBARL/PBEAML) or by Properties (PBAR/PBEAM). If
Dimensions is choosen, the MD Nastran’s built-in section library
(Version 69 and later), PBARL/PBEAML, (for the standard Beam
Library) or PBRSECT/PBMSECT (for an Arbitrary section) will be
used to define the bar/beam. If Properties is chosen, the standard
bar/beam properties, PBAR/PBEAM will be used to define the
beam section. If the Dimensions Option is set to Dimensions, the
Translation Parameters Version must be set to version 69 or later.
Material Name Defines the material to be used. A list of all materials currently in
the database is displayed when data is entered. Either select from the
list using the mouse, or type in the name. This property defines the
value to be used in the MID field on the PBAR entry. This property
is required.
Bar Orientation Defines the local element coordinate system to be used for any
cross-sectional properties. This orientation will define the local XY
plane, where the x-axis is along the beam. This orientation defines
the value for the X1, X2, X3, or G0 fields on the CBAR entry. This
property is required.
• Value Type Specifies how the bar orientation is defined:
When the value type is Vector, it is always input in either the Patran
global or some other Patran user defined coordinate system (i.e. <0
1 0 Coord 5>).
• Reference Coordinates Specifies the MD Nastran coordinate system in which the bar
orientation vector will be written to the CBAR entry:
Note: The reference coordinate system specified does not affect how
the input is interpreted within Patran. Only how it is written to the
CBAR entry.
Chapter 2: Building A Model 105
Element Properties
Offset @ Node 1 Defines the offset from the nodes to the actual centroids of the beam
cross section. These orientations are defined as vectors. These
Offset @ Node 2 properties, after any necessary transformations, become the W1A,
W2A, W3A, W1B, W2B, and W3B fields on the CBAR entry.
Torsional Constant Defines the torsional stiffness of the beam. This is the J field on the
PBAR entry. This value can be either a real value or a reference to
an existing field definition. This property is optional.
Shear Stiff, Y Defines the shear stiffness values. These are the K1 and K2 fields on
the PBAR entry. These values can be either real value or references
Shear Stiff, Z to existing field definitions. This property is optional.
Nonstructural Mass Defines mass not included in the mass derived from the material of
the element. This is defined in terms of mass per unit length of the
beam. This is the NSM field on the PBAR entry. This value can be
either a real value or reference to an existing field definition. This
property is optional.
Y of Point C Indicates the stress recovery. They define the Y and Z coordinates of
the stress recovery points across the section of the beam, as defined
Z of Point C in the local element coordinate system. These are the C1, C2, D1,
Y of Point D D2, E1, E2, F1, and F2 fields on the PBAR entry. These values can
be either real values or references to existing field definitions. These
Z of Point D properties are optional.
Y of Point E
Z of Point E
Y of Point F
Z of Point F
[Contact Beam Radius] This allows the equivalent radius for beam-to-beam contact to be
different for each beam cross section. The MD Nastran entry
BCBMRAD is written to the .bdf file. The BCBMRAD entry format
is different for SOL 400 and SOL 600.
[Station Distances] Defines up to 6 points along each bar element. Values specified are
fractions of the beam length. Therefore, these values are in the range
of 0. to 1. This defines the X1 and X6 fields on the CBARAO entry.
The SCALE field on the CBARAO entry is always set to FR. The
alternate format for the CBARAO entry is not supported. These
values are real values. These properties are optional.
Create Sections, I C L ..., Activates the Beam Library forms. These forms will allow the user
Beam Library to define beam properties by choosing a standard cross section type
and inputing dimensions.
Chapter 2: Building A Model 107
Element Properties
P-Formulation Bar/4
Use this form to create a CBEAM element and a PBEAM or PBEAML property. This form defines a
simple beam element in the structural model for an adaptive, p-element analysis.
Note: Patran will check the element associativity to other elements sharing this
property set and will not export user defined pin flags for nodes which are
shared by two beams sharing the same node.
108 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the local element coordinate system to be used for any cross-sectional properties. This orientation will
define the local XY plane, where the x-axis is along the beam, and this orientation vector, which can be defined as
either a vector or a reference to an existing node, is in the XY plane. This defines the value for the X1, X2, X3, or
G0 fields on the CBAR entry. This property is required.
This is a list of Input Properties available for creating a CBEAM element and a PBEAM or PBEAML
property that were not shown on the previous page. Use the menu scroll bar on the Input Properties form
to view these properties.
Torsional Constant Defines the torsional stiffness of the beam. This is the J field on the
PBEAM entry. This value can be either a real value or a reference to
an existing field definition. This property is optional.
Shear Stiff, Y Defines the shear stiffness values. These are the K1 and K2 fields on
the PBEAM entry. These values can be either real values or references
Shear Stiff, Z to existing field definitions. This property is optional.
Nonstructural Mass Defines mass not included in the mass derived from the material of the
element. This is defined in terms of mass per unit length of the beam.
This is the NSM field on the PBEAM entry. This value can be either a
real value or reference to an existing field definition. This property is
optional.
Y of Point C Indicates the stress recovery. Define the Y and Z coordinates of the
stress recovery points across the section of the beam as defined in the
Z of Point C local element coordinate system. These are the C1, C2, D1, D2, E1, E2,
X of Point D F1, and F2 fields on the PBEAM entry. These values can be either real
values or references to existing field definitions. These properties are
Y of Point D optional.
X of Point E
Y of Point E
X of Point F
Y of Point F
Station Distances Defines up to 6 points along each bar element. Values specified are
fractions of the beam length. Therefore, these values are in the range
of 0. to 1. This defines the X1 and X6 fields on the CBARAO entry. The
SCALE field on the CBARAO entry is always set to FR. The alternate
format for the CBARAO records is not supported. These values are
real values. These properties are optional.
110 Patran Interface to MD Nastran Preference Guide
Element Properties
Use this form to create a CBEND element and a PBEND property. This form defines a curved beam
element of the structural model. The CBEND element has several ways to define the radius of the bend
and the orientation of that curvature.This element in Patran always uses the method of defining the center
of curvature point (GEOM=1). An alternate property of the Curved Pipe element also exists.
Chapter 2: Building A Model 111
Element Properties
This is a list of Input Properties available for creating a CBEND element and a PBEND property that were
not shown on the previous page. Use the menu scroll bar on the Input Properties form to view these
properties.
R of Point E
Z of Point E
R of Point F
Z of Point F
Chapter 2: Building A Model 113
Element Properties
Use this form to create a CBEND element and a PBEND property. This defines a curved pipe
or elbow element of the structural model. The internal pressure is defined as part of the element definition
because, for pipe elbows, the internal pressure affects the element stiffness.
114 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the material to be used. A list of all materials currently in the database is displayed when Defines the
data is entered. Either select from the list using the mouse, or type in the name. Defines the MID center of
field on the PBEND entry. This property is required. curvature of the
pipe bend. This
can be done
either by
specifying a
vector from the
first node of the
element or by
referencing a
node. The
CBEND
element in MD
Nastran has
several ways to
define the
radius of the
pipe bend and
the orientation
of that
curvature.
Defines the
settings of the
X1, X2, X3, and
G0 fields on the
CBEND entry.
This element in
Patran always
uses the
method of
defining the
center of
curvature point
Indicates the
wall thickness
of the pipe.
This is the t
field on the
PBEND entry.
This value
can be either
a real value or
a reference to
an existing
field
definition.
This property
is required.
Defines the offset from the nodes to the actual centroids of the pipe
cross section. These are the RC and ZC fields on the PBEND entry. Indicates the distance from the centroid of
These values can either be real values or references to existing field cross section to mid-wall location. This is t
definitions. These properties are optional. on the PBEND entry. This value can either
value or a reference to an existing field de
This property is required.
Chapter 2: Building A Model 115
Element Properties
This is a list of Input Properties available for creating a CBEND element and a PBEND property that were
not shown on the previous page. Use the menu scroll bar on the Input Properties form to view these
properties.
Use this form to create a CBEAM element and a PBCOMP property. This defines a beam
element of constant cross section, using a lumped area element formulation.The orientation vector can
be defined as either a vector or a reference to an existing node in the XY plane.
116 Patran Interface to MD Nastran Preference Guide
Element Properties
Note: Patran will check the element associativity to other elements sharing this
property set and will not export user defined pin flags for nodes which are shared
by two beams sharing the same node.
Chapter 2: Building A Model 117
Element Properties
Section Name Specifies a beam section previously created using the beam library
• Value Type Allows you to define a bar/beam section either by Dimensions
(PBARL/PBEAML) or by Properties (PBAR/PBEAM). If
Dimensions is choosen, the MD Nastran’s built-in section library
(Version 69 and later), PBARL/PBEAML, will be used to define the
bar/beam. If Properties is chosen, the standard bar/beam properties,
PBAR/PBEAM will be used to define the beam section. If the
Dimensions Option is set to Dimensions, the Translation Parameters
Version must be set to version 69 or later.
Material Name Defines the material to be used. A list of all materials currently in the
database is displayed when data is entered. Either select from the list
using the mouse, or type in the name. This defines the setting of the
MID field on the PBCOMP entry. This property is required.
Bar Orientation Defines the local element coordinate system to be used for any cross-
sectional properties. This orientation will define the local XY plane,
where the x-axis is along the beam. This orientation defines the value
for the X1, X2, X3, or G0 fields on the CBAR entry. This property is
required.
• Value Type The orientation vector can be defined as either a vector or a reference
to an existing node in the XY plane.
• Reference Coordinates Analysis - Analysis Coordinate System.
Pinned DOFs @ Node 1 Indicates whether certain degrees of freedom are to be released. By
default, all degrees of freedom can transfer forces at the ends of beams.
Pinned DOFs @ Node 2 By releasing specified degrees of freedom, pin or sliding type
connections can be created. These degrees-of-freedom are in the
element local coordinate system. The values that can be specified here
are UX, UY, UZ, RX, RY, RZ, or a combination. These properties
define the settings of the PA and PB fields on the CBEAM entry and
are optional.
Warp DOF @ Node 1 Defines a node ID where the warping degree-of-freedom constraints
and results will be placed. These must reference existing nodes within
Warp DOF @ Node 2 the model. They are the SA and SB fields on the CBEAM entry. These
properties are optional.
Area Defines the cross-sectional area of the element. This is the A field on
the PBCOMP entry. This value can be either a real value or a reference
to an existing field definition. This property is optional.
Nonstructural Mass Defines mass not included in the mass derived from the material of the
element. This is defined in terms of mass per unit length of the beam.
This is the NSM field on the PBCOMP record. This value can be either
a real value or a reference to an existing field definition. This property
is optional.
Shear Stiff, Y Defines the shear stiffness values. These are the K1 and K2 fields on
the PBCOMP entry. This value can be either a real value or a reference
Shear Stiff, Z to an existing field definition. This property is optional.
Y of NSM Defines the offset from the centroid of the cross section to the location
of the nonstructural mass. These values are measured in the beam
Z of NSM cross-section coordinate system. These properties are the M1 and M2
fields on the PBCOMP entry. These values can be either real values or
references to existing field definitions. These properties are optional.
Symmetry Option Specifies which type of symmetry is being used to define the lumped
areas of the beam cross section. This is a character string parameter.
The valid settings are No Symmetry, YZ Symmetry, Y Symmetry, Z
Symmetry, or Y=Z Symmetry. This defines the setting of the
SECTION field on the PBCOMP entry. This property is optional.
Chapter 2: Building A Model 119
Element Properties
Ys of Lumped Areas Defines the locations of the various lumped areas. These are defined in
the cross-sectional coordinate system. These properties define the Yi
Zs of Lumped Areas and Zi fields on the PBCOMP entry. These values are lists of real
values. These properties are optional.
Area Factors Defines the Fraction of the total area to be included in this lumped
area. The sum of all area factors for a given section must equal 1.0. If
the data provided does not meet this requirement, the values will all be
scaled to the corrected value. These properties define the values for the
Ci fields on the PBCOMP entry. These values are lists of real values.
These properties are optional.
Use this form to create a CBEAM element and a PBEAM or PBEAML property. This defines a
beam element with varying cross sections.
Chapter 2: Building A Model 121
Element Properties
Note: Patran will check the element associativity to other elements sharing this
property set and will not export user defined pin flags for nodes which are
shared by two beams sharing the same node.
Section Name Specifies a beam section previously created using the beam library
• Value Type Allows you to define a bar/beam section either by Dimensions
(PBARL/PBEAML) or by Properties (PBAR/PBEAM). If Dimensions
is choosen, the MSC.Nastran’s built-in section library (Version 69 and
later), PBARL/PBEAML, will be used to define the bar/beam. If
Properties is chosen, the standard bar/beam properties, PBAR/PBEAM
will be used to define the beam section. If the Dimensions Option is set
to Dimensions, the Translation Parameters Version must be set to
version 69 or later.
Material Name Defines the material to be used. A list of all materials currently in the
database is displayed when data is entered. Either select from the list
using the mouse, or type in the name. This defines the setting of the
MID field on the PBCOMP entry. This property is required.
Bar Orientation Defines the local element coordinate system to be used for any cross-
sectional properties. This orientation will define the local XY plane,
where the x-axis is along the beam. This orientation, after any
necessary transformations, defines the value for the X1, X2, X3, or G0
fields on the CBEAM entry. This property is required.
• Value Type Specifies how the bar orientation is defined:
When the value type is Vector, it is always input in either the Patran
global or some other Patran user defined coordinate system (i.e. <0 1 0
Coord 5>).
122 Patran Interface to MD Nastran Preference Guide
Element Properties
• Reference Coordinates Specifies the MD Nastran coordinate system in which the bar
orientation vector will be written to the CBEAM entry:
Note: The reference coordinate system specified does not affect how
the input is interpreted within Patran. Only how it is written to the
CBEAM entry.
Offset @ Node 1 Defines the offset from the nodes to the shear centers of the beam cross
section. These orientations are defined as vectors. These properties,
Offset @ Node 2 after any necessary transformations, become the W1A, W2A, W3A,
W1B, W2B, and W3B fields on the CBEAM entry.
Pinned DOFs @ Node 1 Indicates whether certain degrees of freedom are to be released. By
default, all degrees of freedom can transfer forces at the ends of beams.
Pinned DOFs @ Node 2 By releasing specified degrees of freedom, pin or sliding type
connections can be created. These degrees-of-freedom are in the
element local coordinate system. The values that can be specified here
are UX, UY, UZ, RX, RY, RZ, or a combination. These properties
define the settings of the PA and PB fields on the CBEAM entry and
are optional.
Warp DOF @ Node 1 Defines a node ID where the warping degree of freedom constraints
and results will be placed. These must reference existing nodes within
Warp DOF @ Node 2 the model. These are the SA and SB fields on the CBEAM entry. These
properties are optional.
Station Distances Defines stations along each beam element where the section properties
will be defined. The values specified here are fractions of the beam
length. These values, therefore, are in the range of 0. to 1. These values
define the settings of the X/XB fields on the PBEAM record. These
values are real values. These properties are optional.
Cross-Sect. Areas Defines the cross-sectional area of the element. This property defines
the settings of the A fields on the PBEAM record. This value can be
either a real value, or reference to an existing field definition. This
property is required.
Inertias 1,1 Defines the various area moments of inertia of the cross section. These
defines the settings of the I1, I2, and I12 fields on the PBEAM entry.
Inertias 2,2 These values are real values. These properties are optional.
Inertias 1,2
Torsional Constants Defines the torsional stiffness parameters. This property defines the J
fields on the PBEAM entry. This is a list of real values, one for each
station location. This property is optional.
Ys of C Points Defines the Y and Z locations in element coordinates, relative to the
shear center for stress data recovery. These define the C1, C2, D1, D2,
Zs of C Points E1, E2, F1, and F2 fields on the PBEAM entry. These are lists of real
Ys of D points values, one for each station location. These properties are optional.
Zs of D Points
Ys of E Points
Zs of E Points
Ys of F Points
Zs of F Points
124 Patran Interface to MD Nastran Preference Guide
Element Properties
Nonstructural Masses Defines the mass not included in the mass derived from the material of
the element. This is defined in terms of mass per unit length of the
beam. This property is the NSM field on the PBEAM entry. This is a list
of real values, one for each station location. This property is optional.
NSM Inertia @ Node 1 Specified the nonstructural mass moments of inertia per unit length
about the nonstructural mass center of gravity at each end of the
NSM Inertia @ Node 2 element. These properties are the NSI(A) and NSI(B) fields on the
PBEAM entry. These values can be either real values or references to
existing field definitions. These properties are optional.
Y of NSM @ Node 1 Defines the offset from the centroid of the cross section to the location
of the nonstructural mass. These values are measured in the beam
Z of NSM @ Node 1 cross-section coordinate system. These are the M1(A), M2(A), M1(B),
Y of NSM @ Node 2 and M2(B) fields on the PBEAM entry. These values can be either real
values or references to existing field definitions. These properties are
Z of NSM @ Node 2 optional.
Shear Stiff, Y Defines the shear stiffness values. These properties are the K1 and K2
fields on the PBEAM entry. These values can be either real values or
Shear Stiff, Z references to existing field definitions. These properties are optional.
Shear Relief Y Defines the shear relief coefficients due to taper. These are the S1 and
S2 fields on the PBEAM entry. These values can either be real values
Shear Relief Z or references to existing field definitions. These properties are
optional.
Warp Coeff. @ Node 1 Specifies the warping coefficient at each end of the element. These
properties are the CW(A) and CW(B) fields on the PBEAM entry. These
Warp Coeff. @ Node 2 values can be either real values or references to existing field
definitions. These properties are optional.
Y of NA @ Node 1 Defines the offset from the centroid of the cross section to the location
of the neutral axis. These values are measured in the beam cross section
Z of NA @ Node 1 coordinate system and are the N1(A), N2(A), N1(B), and N2(B) fields
Y of NA @ Node 2 on the PBEAM entry. These values can be either real values or
references to existing field definitions. These properties are optional.
Z of NA @ Node 2
This set of options provides a method of creating beam models with warping due to torsion. The
capabilities of this beam properties formulation option are similar to those of the “Tapered Section”
formulation, except that warping due to torsion is handled more conveniently.
126 Patran Interface to MD Nastran Preference Guide
Element Properties
Note: Patran will check the element associativity to other elements sharing this property set and will not export user
defined pin flags for nodes which are shared by two beams sharing the same node.
Section Name Specifies a beam section previously created using the beam library
• Value Type Allows you to define a bar/beam section either by Dimensions
(PBARL/PBEAML) or by Properties (PBAR/PBEAM). If Dimensions is
choosen, the MSC.Nastran’s built-in section library (Version 69 and
later), PBARL/PBEAML, will be used to define the bar/beam. If
Properties is chosen, the standard bar/beam properties, PBAR/PBEAM
will be used to define the beam section. If the Dimensions Option is set
to Dimensions, the Translation Parameters Version must be set to version
69 or later.
Material Name Defines the material to be used. A list of all materials currently in the
database is displayed when data is entered. Either select from the list
using the mouse, or type in the name. This defines the setting of the MID
field on the PBCOMP entry. This property is required.
Bar Orientation Defines the local element coordinate system to be used for any cross-
sectional properties. This orientation will define the local XY plane,
where the x-axis is along the beam. This orientation, after any necessary
transformations, defines the value for the X1, X2, X3, or G0 fields on the
CBEAM entry. This property is required.
• Value Type Specifies how the bar orientation is defined:
When the value type is Vector, it is always input in either the Patran
global or some other Patran user defined coordinate system (i.e. <0 1 0
Coord 5>).
Chapter 2: Building A Model 127
Element Properties
• Reference Coordinates Specifies the MD Nastran coordinate system in which the bar orientation
vector will be written to the CBEAM entry:
Note: The reference coordinate system specified does not affect how the
input is interpreted within Patran. Only how it is written to the CBEAM
entry.
Offset @ Node 1 Defines the offset from the nodes to the shear centers of the beam cross
section. These orientations are defined as vectors. These properties, after
Offset @ Node 2 any necessary transformations, become the W1A, W2A, W3A, W1B,
W2B, and W3B fields on the CBEAM entry.
Pinned DOFs @ Node 1 Indicates whether certain degrees of freedom are to be released. By
default, all degrees of freedom can transfer forces at the ends of beams.
Pinned DOFs @ Node 2 Pin or sliding type connections can be created by releasing specified
degrees of freedom. These degrees of freedom are in the element local
coordinate system. The values specified here are UX, UY, UZ, RX, RY,
RZ, or a combination. These properties define the settings of the PA and
PB fields on the CBEAM entry. These properties are optional.
Warping Option This specifies how contraints should be applied to the warping SPOINTs
of unmatched ends within the application region (see continuity rules
above). The choices available include “A free B free”,
“A fixed B fixed”, “A free B fixed”, “A fixed B free”, or “None”. The
choice of “None” is used to disable warping altogether for the current
element property set, in which case no SPOINTs will be generated or
constrained. Only unmatched ends within the application region will be
eligible for constraining, and whether or not a constraint is applied will
depend on the option selected, and whether the unmatched end is
“End A” or “End B” of its beam element. If no selection is made for this
element property, “A free B free” is selected by default.
Warp Coeff. @ Node 1 Specifies the warping coefficient at each end of the element. These
Warp Coeff. @ Node 2 properties are the CW(A) and CW(B) fields on the PBEAM entry. These
values can be either real values or references to existing field definitions.
These properties are optional.
Station Distances Defines stations along each beam element where the section properties
will be defined. The values specified here are fractions of the beam
length. These values, therefore, are in the range of 0. to 1. These values
define the settings of the X/XB fields on the PBEAM record. This field
consists of a set of real values separated by legal delimiters, such as white
space and/or commas. If this list is entered, then the properties that
follow may also be in the form of lists consisting of the same number of
values. If they are in the form of a single real value, then that value will
apply to all stations of the beam element. This property is optional. If it
is not provided, then all other specified section properties apply to the
entire beam, and lists of values will not be accepted.
Cross-Sect. Areas Defines the cross sectional area of the element. This property defines the
settings of the A fields on the PBEAM record. This value can be either a
real value, a list (if a list of stations has been provided), or a reference to
an existing field definition, in which case a single real value will be
evaluated for each element of the application region. This property is
required.
Chapter 2: Building A Model 129
Element Properties
Inertias 1,1 Defines the various area moments of inertia of the cross section. These
Inertias 2,2 values define the settings of the I1, I2, and I12 fields on the PBEAM
Inertias 1,2 entry. These values are single real values that apply to the entire beam,
or a list of real values if a list of stations has been provided. These
properties are optional. If they are not provided, values of 0 will be
assumed.
Torsional Constants Defines the torsional stiffness parameters. This property defines the J
fields on the PBEAM entry. This value is a single real value that applies
to the entire beam, or a list of real values if a list of stations has been
provided. This property is optional. If it is not provided, a value of 0 will
be assumed.
Ys of C Points Defines the Y and Z locations in element coordinates, relative to the
Zs of C Points shear center, for stress data recovery. These define the C1, C2, D1, D2,
Ys of D Points E1, E2, F1, and F2 fields on the PBEAM entry. These values are single
Zs of D Points
Ys of E Points real values that apply to the entire beam, or lists of real values if a list of
Zs of E Points stations has been provided. These properties are optional. If they are not
Ys of F Points provided, values of 0 will be assumed.
Zs of F Points
Nonstructural Masses Defines the mass not included in the mass derived from the material of
the element. This is defined in terms of mass per unit length of the beam.
This property is the NSM field on the PBEAM entry. This value is a
single real value that applies to the entire beam, or a list of real values if
a list of stations has been provided. This property is optional. If it is not
provided, a value of 0 will be assumed.
NSM Inertia @ Node 1 Specifies the nonstructural mass moments of inertia per unit length about
NSM Inertia @ Node 2 the nonstructural mass center of gravity at each end of the element.
These properties are the NSI(A) and NSI(B) fields on the PBEAM entry.
These values can be either real values or references to existing field
definitions. These properties are optional.
Y of NSM @ Node 1 Defines the offset from the shear center of the cross section to the
Z of NSM @ Node 1 location of the nonstructural mass. These values are measured in the
Y of NSM @ Node 2 beam cross-section coordinate system. These are the M1(A), M2(A),
Z of NSM @ Node 2
M1(B), and M2(B) fields on the PBEAM entry. These values can be
either real values or references to existing field definitions. These
properties are optional.
Shear Stiff, Y Defines the shear stiffness values. These properties are the K1 and K2
Shear Stiff, Z fields on the PBEAM entry. These values can be either real values or
references to existing field definitions. These properties are optional.
130 Patran Interface to MD Nastran Preference Guide
Element Properties
Shear Relief Y Defines the shear relief coefficients due to taper. These are the S1 and
Shear Relief Z S2 fields on the PBEAM entry. These values can either be real values or
references to existing field definitions. These properties are optional.
Y of NA @ Node 1 Defines the offset from the shear center of the cross section to the
Z of NA @ Node 1 location of the neutral axis. These values are measured in the beam
Y of NA @ Node 2 cross-section coordinate system. These are the N1(A), N2(A), N1(B), and
Z of NA @ Node 2
N2(B) fields on the PBEAM entry. These values can be either real values
or references to existing field definitions. These properties are optional.
Warping due to torsion is enabled by generating MD Nastran SPOINTs to contain the warping degrees
of freedom. These SPOINTs are not actually present in the Patran database, and there is no way to
recover any results for these SPOINTs. They are created during analysis deck translation, and provide
the means to communicate to MD Nastran the continuity and constraint properties of the warping degrees
of freedom in the model. These attributes of continuity and constraint are implied in the Patran database
through the composition of the element properties application region and the set of options selected.
These continuity and constraint attributes apply to both warping SPOINTs and end release flags. This
connection of these attributes to the composition of the application region is new in Patran 2001r3, and
represents a change in behavior from previous versions of Patran. The general rules of implied continuity
are as follows.
1. Within the application region, two beam elements are taken to be continuous if a GRID ID at an
end of one of the beam elements matches a GRID ID at one of the ends of the other beam element.
If a third beam element in the same application region also contains the same GRID ID, it is
assumed that none of the beam elements is continuous at this location. This condition is known
as a “multiple junction”. Similarly, if none of the other beam elements in the application region
contain a matching GRID ID, the corresponding end of the beam element is taken to be not
continuous. This condition is known as an “unmatched end”.
2. If warping is enabled, then all instances of beam element continuity must have the matching
GRID ID located at “End A” of one of the beam elements and at “End B” of the other. “End A”
and “End B” positions are determined by the order of GRID IDs specified in the element
connectivity array, and the positive direction of the x-axis of the element coordinate system points
from “End A” to “End B”. If warping is not enabled, this restiction does not apply. If warping is
enabled, any violation of this requirement will result in a failure to complete the translation of the
finite element model. In this event, the user will have to reverse the direction of the improperly
oriented beam elements and initiate the translation again.
3. When warping is enabled, all positions of beam element continuity within an application region
will be represented by a single SPOINT at each of these positions, which will be generated at the
time of analysis deck translation and will appear on the CBEAM entries for the appropriate end
of both of the beam elements that are continuous at each location. If any end release codes have
been prescribed for the application region, they will not be applied at locations of beam element
continuity. This is new for Patran 2001r3. For earlier versions of Patran, end release codes would
be applied to all elements of the application region, regardless of continuity.
Chapter 2: Building A Model 131
Element Properties
4. When warping is enabled, individual SPOINTs are generated for all beam ends that are not
continuous. This applies to both “multiple junctions” and “unmatched ends”.
5. The specified end release codes are applied to all discontinuous beam element ends in the
application region, whether “multiple junction” or “unmatched end”, with the applied end release
codes dependent on what has been prescribed for “End A” and “End B” for the application region.
If no end release codes have been prescribed for the application region, none are generated.
6. When warping is enabled, and for unmatched ends only (not multiple junctions), constraints
applied to the SPOINTs are specified by the “warping option” specified in the element properties
form. For example, if “A free B fixed” has been selected and the unmatched end is “End A” of
its beam element, it will not be constrained. If it is “End B” of its element, it will be constrained.
The warping SPOINT for a beam element end involved in a multiple junction will not be
constrained under any circumstances. If the user wishes to constrain warping for a beam element
involved in a multiple junction, he will have to do so by splitting the application region in such a
way that the beam element end becomes an “unmatched end” within its new application region.
7. Warping is considered to be enabled when a value has been specified for the warping coefficient
at either end of the beam element. When the user selects the “Beam Library” option, values for
the warping coefficient get computed autamatically, and thus warping is implicitly enabled. If the
user wishes to disable warping while using the Beam Library option, he must choose “None” as
his “Warping Option” on the “Input Properties ...” form.
Standard
Use this form to create a CROD element and a PROD property. This defines a tension-
compression-torsion element of the structural model.
132 Patran Interface to MD Nastran Preference Guide
Element Properties
Chapter 2: Building A Model 133
Element Properties
Defines the cross-sectional area of the Defines the material to be used. A list of all
element. This is the A field on the materials currently in the database is displayed
PROD entry. This value can be either a when data is entered. Either select from the list
real value or a reference to an existing using the mouse or type in the name. This defines
field definition. This property is the setting of the MID field on the PROD entry.
required. This property is required.
CONROD
Defines the material to be used. A list of all materials currently in the database is displayed when
data is entered. Either select from the list using the mouse, or type in the name. This defines the
setting of the MID field on the CONROD entry. This property is required.
Use this form to create a CTUBE element and a PTUBE property. This defines a tension-
compression-torsion element with a thin-walled tube cross section.
Chapter 2: Building A Model 137
Element Properties
Defines the tube outer diameters at each end of the element. These are the OD and OD2
fields on the PTUBE entry. These values can either be real values or references to existing
field definitions. The outer diameter at Node 1 property is required. The outer diameter at
Node 2 Property is optional.
Defines the
material to be
used. A list of all
materials currently
in the database is
displayed when
data is entered.
This property
defines the setting
of the MID field on
the PTUBE entry.
Either select from
the list using the
mouse, or type in
the name. This
property is
required.
Defines mass not
included in the
mass derived
from the material
of the element.
This property is
defined in terms
of mass per unit
length of the
beam and is the
NSM field on the
PRTUBE entry.
This value can be
either a real value
or reference to an
existing field
definition. This
property is
optional.
Specifies the wall thickness of the pipe. This is the T field on the PTUBE
entry. This value can either be a real value or a reference to an existing
field definition. This property is required.
Use this form to create a CELAS1 or CELAS1D (for SOL 700) element and a PELAS property.
This defines a scalar spring of the structural model.
Chapter 2: Building A Model 139
Element Properties
Defines the coefficient to be used for this Defines what damping is to be included.
spring. This property is the K field on the This property is the GE field on the PELAS
PELAS entry and can be either a real value entry and can be either a real value or a
or a reference to an existing field definition. reference to an existing field definition. This
This property is required. property is optional.
Defines which
degree of
freedom this
value is to be
attached to at
each node. The
degree of
freedom can be
set to UX, UY,
UZ, RX, RY, or
RZ. These
properties
define the
settings of the
C1 and C2 fields
on the CELAS1
entry. These
properties are
required.
Defines the relationship between the spring Number of a User Defined Coordinate
deflection and the stresses within the spring. system, used only for Explicit Nonlinear
This property is the S field on the PELAS (SOL 700). This property is optional.
entry and can be either a real value or a
reference to an existing field definition. This
property is optional.
Use this form to create a CDAMP1 or CDAMP1D (for SOL 700) element and a PDAMP property. This
defines a scalar damper element of the structural model.
Chapter 2: Building A Model 141
Element Properties
Use this form to create a CVISC element and a PVISC property. This defines a viscous damper element
of the structural model.
This is the C1 field on the PVISC entry. This This is the C2 field on the PVISC entry. This
property can either be a real value or a property can either be a real value or a
reference to an existing field definition. This reference to an existing field definition. This
property is optional. property is optional.
Gap (CGAP)
This subordinate form appears when the Input Properties button is selected on the Element Properties
form and the following options are chosen.
Nonadaptive
Use this form to create a CGAP element and a PGAP property. This defines a gap or frictional
element of the structural model for non-linear analysis.
Chapter 2: Building A Model 143
Element Properties
Defines the artificial stiffness of the gap when the gap is open or closed.
The closed stiffness should be chosen to closely match the stiffness of the
surrounding elements. The open stiffness should be approximately 10
orders of magnitude less. These properties are the Ka and Kb fields on the
PGAP entry and can either be real value or references to existing field
definitions. The closed stiffness property is required. The opened stiffness
property is optional.
Defines an initial preload across an initially closed gap. For example, this can be used for
initial thread loading. If the gap is initially open, setting this value to the initial opening
stiffness will improve the solution convergence. This is the F0 field on the PGAP entry and
can either be a real value or a reference to an existing field definition. This property is
optional.
This is a list of Input Properties available for creating a CGAP element and a PGAP property that were
not shown on the previous page. Use the menu scroll bar on the Input Properties form to view these
144 Patran Interface to MD Nastran Preference Guide
Element Properties
properties.
Use this form to create a CMASS1 element and a PMASS property. This defines a scalar mass element of
the structural model.
Defines the translation mass or rotational Defines which degree of freedom this value
inertia value to be applied. This property is the will be attached to at each node. These can be
M field on the PMASS entry and can either be set to UX, UY, UZ, RX, RY, or RZ and defines
a real value or a reference to an existing field the settings of the C1 and C2 field on the
definition. This property is required. CMASS1 entry. These properties are required.
146 Patran Interface to MD Nastran Preference Guide
Element Properties
PLOTEL
This subordinate form appears when the Input Properties button is selected on the Element Properties
form and the following options are chosen.
(Scalar) Bush
This subordinate form appears when the Input Properties button is selected on the Element
Properties form and the following options are chosen.
This is a list of Input Properties available. Use the menu scroll bar on the Input Properties form to view
these properties.
Note that SPOTWELD properties are created automatically (or pre-existing properties selected) when
creating Spotwelds through the Finite Elements application. Therefore no application region is required
(or presented) in the element properties application when defining or modifying spotweld properties
because the existence of the spotweld itself is the application region for the property set.
152 Patran Interface to MD Nastran Preference Guide
Element Properties
Note that FASTENER properties are created automatically (or pre-existing properties selected) when
creating Fasteners through the Finite Elements application. Therefore no application region is required
(or presented) in the element properties application when defining or modifying fastener properties
because the existence of the fastener itself is the application region for the property set.
154 Patran Interface to MD Nastran Preference Guide
Element Properties
1
E f --- Ãd 2
4 f
k = --------------------
l
The stiffness is inserted into the KT1 parameter of the PFAST entry. The length of the fastener will be
determined by summation of the thickness of the two connected shell elements.
The Douglas formula is*:
1
k = ---
c
5 1 1
c = ---------- + 0.8 ---------- + ----------
df Ef t E t 2 E 2
1 1
k = 1
---
c
a
t 1 + t 2 1 1 1 1
- ----------
c = b -------------- + ---------- + ------------- + -------------
2d t E t 2 E 2 2E f t 1 2E f t 2
f 1 1
a b
Hi-Lok in CFRP 0.6667 4.2
Chapter 2: Building A Model 155
Element Properties
a b
Hi-Lok in metal 0.6667 3.0
Solid Rivet 0.4 2.2
In the case of composites, the Douglas and Huth formulas have to be used twice. First, the overall
(engineering) Young’s modulus has to be calculated for both directions (E11 and E22), which then has to
be applied to the formulas. In this case, the shear stillness of the fastener is direction dependent. For
composites or anisotrophic material, the material tensors of the two connected shell elements have to be
transformed into the coordinate system of the CFAST element before the Douglas or Huth formula is
applied. The resulting stiffness is applied to the KT2 and KT3 parameters on the PFAST entry.
* The following symbols are used in the formulas:
Symbol Meaning
Ef Young’s modulus of fastener
df Diameter of fastener
l Length of fastener, evaluated from the FE model
E1 Young’s modulus of first property connected to the fastener
t1 Thickness of first property connected to the fastener
E2 Young’s modulus of second property connected to the fastener
t2 Thickness of second property connected to the fastener
Use this form to create a CQUAD4, CTRIA3, CQUAD8, or CTRIA6 element and a PSHELL
property. The appropriate fields on the PSHELL entry are filled in or left blank to achieve the requested
behavior.
156 Patran Interface to MD Nastran Preference Guide
Element Properties
Chapter 2: Building A Model 157
Element Properties
Defines the
material to be
used. A list of all
materials currently
in the database is
displayed when
data is entered.
Either select one
from the list using
the mouse or type
in the name. This
defines the
settings of the
MID1, MID2,
MID3, and MID4
fields on the
PSHELL entry.
This property is
required.
Defines the
thickness, which
will be uniform
over each
element. This
value can either
be a real value or
a reference to an
existing field
definition. This
property defines
the T1, T2, T3,
and T4 fields on
the CQUAD4/8
and CTRIA3/6
entries and/or the
T field on the
PSHELL entry.
This property is
Defines the basic orientation for any non-isotropic material within the required.
element. There are three ways to assign this definition: (1) reference a
coordinate system, which is then projected onto the element, (2) define a
vector that will be projected onto the element, or (3) define a constant
angle offset from the default element coordinate system. This defines the
setting of the THETA or MCID field on the CQUADi or CTRIAi entry. This
scalar value can either be a constant value in degrees, a vector, or a
reference to an existing coordinate system. This property is optional.
Defines the mass not derived from the material of the element. This is
defined in terms of mass per unit area of the element. This is the NSM field
on the PSHELL entry. This value can be either a real value or a reference to
an existing field definition. This property is optional.
158 Patran Interface to MD Nastran Preference Guide
Element Properties
This is a list of Input Properties, available for creating a CQUADi and a CTRIAi element and a PSHELL
property, that were not shown on the previous page. Use the menu scroll bar on the Input Properties form
to view these properties.
Revised Formulation
Use this form to create a CTRIAR or CQUADR element and a PSHELL property. The
appropriate fields on the PSHELL entry are filled in or left blank to achieve the requested behavior.
Chapter 2: Building A Model 159
Element Properties
160 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the mass not included in the mass derived from the
material of the element. This property is defined in terms of
mass per unit area of the element. and this is the NSM field
on the PSHELL entry. This value can be either a real value or
a reference to an existing field definition. This property is
optional.
Chapter 2: Building A Model 161
Element Properties
Use this form to create a CQUAD4 or CTRIA3 element and a PSHELL property. The
appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the requested
behavior.The p-formulation shell element is supported in MSC . Nastran Version 69 or later. Therefore,
the MD Nastran Version in the Translation Parameter form must be set to 69.
162 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the
material to be
used. A list of all
materials
currently in the
database is
displayed when
data is entered.
Either select from
the list using the
mouse or type in
the name. This
property defines
the settings of the
MID1, MID2,
MID3, and MID4
fields on the
PSHELL entry.
This property is
required.
Defines the basic orientation for any non-isotropic material within the element. There are two ways to
assign this definition: (1) reference a coordinate system, then the projected x-axis of the coordinate
system is the material x-axis (2) define a constant angle offset from the projected x-axis of the basic
system.This defines the setting of the THETA or MCID field on the CQUAD4 or CTRIA3 entry. This
property is optional.
This is a list of Input Properties, available for creating a CQUAD4 and a CTRIA3 element, that were not
shown on the previous page. Use the menu scroll bar on the Input Properties form to view these
Chapter 2: Building A Model 163
Element Properties
properties.
Use this form to create a CTRIA3, CTRIA6, CQUAD4, or CQUAD8 element and a PCOMP
property.
Chapter 2: Building A Model 165
Element Properties
Defines the
material to
be used. A
list of all
materials
currently in
the
database is
displayed
when data is
entered.
Either select
from the list
using the
mouse or
type the
name in.
The
specified
material
must be a
laminate
material in
Patran. The
data in this
material
definition
defines the
settings of
the MIDi, Ti,
and THETAi
fields on the
PCOMP
entry. This
property is
required.
Defines the basic orientation for any non-isotropic Defines mass not included in the mass
material within the element. There are three ways to derived from the material of the
assign this definition: (1) reference a coordinate element. This is the NSM field on the
system, which is then projected onto the element, (2) PCOMP entry. This property is defined
define a vector that will be projected onto the element, in terms of mass per unit area of the
or (3) define a constant angle offset from the default element and can be either a real value
element coordinate system. This property defines the or a reference to an existing field
setting of the THETA or MCID field on the CTRIA3, definition. This property is optional.
CTRIA6 CQUAD4, or CQUAD8 entry. This scalar
value can either be a constant value or a reference to
an existing coordinate system. This property is Defines the offset of the element‘s
optional. reference plane from the plane defined
by the nodal locations. This is the ZOFFS
field on the CTRIA3, CTRIA6, CQUAD4,
or CQUAD8 entry. This value can be
either a real value or a reference to an
existing field definition. This property is
optional.
166 Patran Interface to MD Nastran Preference Guide
Element Properties
Revised Formulation
Chapter 2: Building A Model 167
Element Properties
Use this form to create a CQUADR or CTRIAR element and a PCOMP property.
Defines the basic orientation for any non-isotropic material within the element. There are three
ways to assign this definition: (1) reference a coordinate system, which is then projected onto the
element, (2) define a vector that will be projected onto the element, or (3) define a constant angle
offset from the default element coordinate system. This defines the setting of the THETA or
MCID field on the CTRIAR or CQUADR entry. This scalar value can either be a constant value or
a reference to an existing coordinate system. This property is optional.
See Standard Laminate Plate (CQUAD4/PCOMP), 163 for a description of the SOL 400 Laminate
and Nonlinear Formulation options.
168 Patran Interface to MD Nastran Preference Guide
Element Properties
Use this form to create a CTRIA3, CTRIA6, CQUAD4, or CQUAD8 element and a PSHELL
property. The appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the
requested behavior.
Chapter 2: Building A Model 169
Element Properties
Defines the materials to be used to describe the membrane, bending, shear, and coupling behavior
of the element. A list of all materials currently in the database is displayed when data is entered.
These properties define the settings of the MID1, MID2, MID3, and MID4 fields on the PSHELL
entry. Either select from the list using the mouse or type in the name. These properties are optional.
This is a list of Input Properties available for creating a CTRIA3, CTRIA6, CQUAD4, or CQUAD8
170 Patran Interface to MD Nastran Preference Guide
Element Properties
element and a PSHELL property that were not shown on the previous page. Use the menu scroll bar on
the Input Properties form to view these properties.
Revised Formulation
Use this form to create a CTRIAR or CQUADR element and a PSHELL property. The
appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the requested
behavior.
172 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the materials to be used to describe the membrane, bending, shear, and coupling
behavior of the element. A list of all materials currently in the database is displayed when data is
entered. These properties define the settings of the MID1, MID2, MID3, and MID4 fields, on the
PSHELL entry. Either select from the list using the mouse or type in the name. These properties
are optional.
Defines the uniform thickness, which will be Defines the basic orientation for any non-
used for each element. This property isotropic material within the element. There
defines the setting of the Ti, T2, T3, and T4 are three ways to assign this definition: (1)
fields on the CTRIAR or CQUADR entry reference a coordinate system which is then
and/or the T field on the PSHELL entry. projected onto the element, (2) define a
This value can be either a real value or a vector that will be projected onto the
references to an existing field definition. element, or (3) define a constant angle offset
This property is required. from the default element coordinate system.
This property defines the setting of the
THETA field on the CQUADR or CTRIAR
entry. This scalar value can either be a
constant value or a reference to an existing
coordinate system. This property is optional.
Chapter 2: Building A Model 173
Element Properties
This is a list of Input Properties available for creating a CTRIAR or CQUADR element and a PSHELL
property that were not shown on the previous page. Use the menu scroll bar on the Input Properties form
to view these properties.
Use this form to create a CQUAD4, or CTRIA3 element and a PSHELL property. The
appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the requested
behavior. The p-formulation shell element is supported in MSC . Nastran Version 69 or later. Therefore,
the MSC .Nastran Version in the Translation Parameter form must be set to 69.
Chapter 2: Building A Model 175
Element Properties
Defines the materials to be used to describe the membrane, bending, shear, and coupling
behavior of the element. A list of all materials currently in the database is displayed when data is
entered. These properties define the settings of the MID1, MID2, MID3, and MID4 fields, on the
PSHELL entry. Either select from the list using the mouse or type in the name. These properties
are optional.
This is a list of Input Properties, available for creating a CQUAD4 and a CTRIA3 element that were not
shown on the previous page. Use the menu scroll bar on the Input Properties form to view these
176 Patran Interface to MD Nastran Preference Guide
Element Properties
properties.
Use this form to create a CTRIA3, CQUAD4 elements for creating acoustic field point
mesh for an exterior acoustics analysis. No property cards are created. The material referenced
should be the same as that defined for the 3D solid elements and exterior acoustic infinite elements used
to define the surrounding fluid environment of the structure, although no actual materials is written. In
order to recover results on these meshes, you must set the output request ACFPFRESULT.
178 Patran Interface to MD Nastran Preference Guide
Element Properties
Each acoustic field point mesh defined is written to a seperate section of the bulk data using the BEGIN
AFPM=id.
Input Properties
Chapter 2: Building A Model 179
Element Properties
Tri/6, Quad/8
Use this form to create a CTRIA3, CTRIA6, CQUAD4, or CQUAD8 element and a PSHELL
property. The appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the
requested behavior.
180 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the material to be used. A list of all materials currently in the database is displayed
when data is entered. Either select from the list using the mouse or type in the name. This
property defines the settings of the MID1, MID2, MID3, and MID4 fields on the PSHELL
entry. This property is required.
This is a list of Input Properties available for creating a CTRIA3, CTRIA6, CQUAD4 or CQUAD8
element and a PSHELL property that were not shown on the previous page. Use the menu scroll bar on
the Input Properties form to view these properties.
Use this form to create a CTRIAR or CQUADR element and a PSHELL property. The
appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the requested
behavior.
182 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the material to be used. A list of all materials currently in the database
is displayed when data is entered. Either select from the list using the mouse or
type in the name. This property defines the settings of the MID1, MID2, MID3,
and MID4 fields on the PSHELL entry. This property is required.
Use this form to create a CTRIA3, or CQUAD4 element and a PSHELL property. The
appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the requested
behavior. The p-formulation shell element is supported in MSC .Nastran Version 69 or later. Therefore,
the MSC. Nastran Version in the Translation Parameters form must be set to 69.
184 Patran Interface to MD Nastran Preference Guide
Element Properties
This is a list of Input Properties available for creating a CTRIA3 or CQUAD4 element and a PSHELL
property that were not shown on the previous page. Use the menu scroll bar on the Input Properties form
Chapter 2: Building A Model 185
Element Properties
Use this form to create a CTRIAX6 axisymmetric solid element. This defines an isoparametric and
axisymmetric triangular cross section ring element with midside nodes.
Chapter 2: Building A Model 187
Element Properties
Defines the basic orientation for any non-isotropic material within the element. There
are three ways to assign this definition: (1) reference a coordinate system, which is
then projected onto the element, (2) define a vector that will be projected onto the
element, or (3) define a constant angle offset from the default element coordinate
system. This defines the setting of the TH field on the CTRIAX6 entry. This scalar
value can be either a constant value or a reference to an existing coordinate system.
This property is optional.
Use this form to create axisymmetric solid elements. This defines an isoparametric and axisymmetric
cross section ring element with or without midside nodes.
188 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the material to be used. A list Defines the basic orientation for any non-isotropic material
of all materials currently in the within the element. There are three ways to assign this
database is displayed when data is definition: (1) reference a coordinate system, which is then
entered. Either select from the list projected onto the element, (2) define a vector that will be
using the mouse or type in the name. projected onto the element, or (3) define a constant angle
This property defines the PLCOMP offset from the default element coordinate system. This scalar
entry to be used. This property is value can either be a constant value or a reference to an
required. existing coordinate system. This property is optional.
Note: Only method 3 is supported in this release.
Use this form to create a CTRIA3, CTRIA6, CQUAD4, or CQUAD8 element and a PSHELL property.
The appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the requested
behavior.
Chapter 2: Building A Model 191
Element Properties
Defines the material to be used. A list of all materials currently in the database is
displayed when data is entered. Either select from the list using the mouse or type in the
name. This property defines the setting of the MID1 field on the PSHELL entry. The MID2
field on the PSHELL entry will be set to -1 to define plane strain behavior. This property is
required.
Revised Formulation
Use this form to create a CTRIAR or CQUADR element and a PSHELL property. The appropriate fields
on the PSHELL entry are filled in or left blank in order to achieve the requested behavior.
192 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the material to be used. A list of all materials currently in the database is displayed when
data is entered. Either select from the list using the mouse or type in the name. This property
defines the setting of the MID1 field on the PSHELL entry. The MID2 field on the PSHELL entry will
be set to -1 to define plane strain behavior. This property is required.
Chapter 2: Building A Model 193
Element Properties
Use this form to create a CQUAD4 or CTRIA3 element and a PSHELL property. The appropriate fields
on the PSHELL entry are filled in or left blank in order to achieve the requested behavior. The p-
formulation shell element is supported in MSC. Nastran Version 69 or later. Therefore, the MSC .Nastran
Version in the Translation Parameters form must be set to 69.
194 Patran Interface to MD Nastran Preference Guide
Element Properties
Defines the material to be used. A list of all materials currently in the database is displayed when
data is entered. Either select from the list using the mouse, or type in the name. This property
defines the setting of the MID1 field on the PSHELL entry. This property is required. The MID2
field on the PSHELL entry will be set to -1 to define plane strain behavior.
Additional properties on the form which do not appear on the previous page are:
Use this form to create a CACINF3, CACINF4 elements and a PACINF property. The appropriate fields
on the PACINF entry are filled in or left blank in order to achieve the requested behavior.
196 Patran Interface to MD Nastran Preference Guide
Element Properties
Use this form to create a CTRIA3, CTRIA6, CQUAD4, or CQUAD8 element and a PSHELL property.
The appropriate fields on the PSHELL entry are filled in or left blank in order to achieve the requested
behavior.
Chapter 2: Building A Model 199
Element Properties
Defines the material to be used. A list of all materials currently in the database is displayed
when data is entered. Either select from the list using the mouse or type in the name. This
property defines the settings of the MID1 field on the PSHELL entry. This property is required.
Defines the mass not derived from the Defines the uniform thickness that will
material of the element. This property be used for each element. This value
is defined in mass per unit area of the can either be a real value or reference
element and is the NSM field on the an existing field definition. This property
PSHELL entry. This value can be either defines the T1, T2, T3, and T4 fields on
a real value or a reference to an the CTRIA3, CTRIA6, CQUAD4, or
existing field definition. This property is CQUAD8 entry and/or the T field on the
optional. PSHELL entry. This property is
required.
Defines the basic orientation for any non-isotropic material within the element. There
are three ways to assign this definition: (1)reference a coordinate system, which is then
projected onto the element. (2) define a vector that will be projected onto the element,
or (3) define a constant angle offset from the default element coordinate system. This
property defines the setting of the THETA or MCID field on the CTRIA3, CTRIA6,
CQUAD4, or CQUAD8 entry. This scalar value can either be a constant value or a
reference to an existing coordinate system. This property is optional.
Use this form to create a CTRIAR or CQUADR element and a PSHELL property. The appropriate fields
on the PSHELL entry are filled in or left blank in order to achieve the requested behavior.
Chapter 2: Building A Model 201
Element Properties
Defines the basic orientation for any non-isotropic material within the element. There are
three ways to assign this definition: (1) reference a coordinate system, which is then
projected onto the element, (2) define a vector that will be projected onto the element, or (3)
define a constant angle offset from the default element coordinate system. This defines the
setting of the THETA or MCID field on the CTRIAR or CQUADR entry. This scalar value can
either be a constant value or a reference to an existing coordinate system. This property is
optional.
form and the following options are chosen. Information on this form is used to create input for an
adaptive, p-element analysis.
Use this form to create a CQUAD4 or CTRIA3 element and a PSHELL property. The appropriate fields
on the PSHELL entry are filled in or left blank in order to achieve the requested behavior. The p-
formulation shell element is supported in MSC .Nastran Version 69 or later. Therefore, the MSC. Nastran
Version in the Translation Parameters form must be set to 69.
Chapter 2: Building A Model 203
Element Properties
Defines the material to be used. A list of all materials currently in the database is displayed
when data is entered. Either select from the list using the mouse or type in the name. This
property defines the setting of the MID1 field on the PSHELL entry. This property is required.
Defines the basic orientation for any Polynomial orders for displacement
non-isotropic material within the representation within elements. Each
element. There are two ways to assign contains a list of three integers referring to
this definition: (1) reference a the directions defined by the P-order
coordinate system, then the projected Coordinate System (default elemental).
x-axis of the coordinate system is the Starting P-orders apply to the first adaptive
material x-axis or (2) define a constant cycle. The adaptive analysis process will
angle offset from the projected x-axis of limit the polynomial orders to the values
basic system. This property defines the specified in Maximum P-orders. These are
setting of the THETA or MCID field on the Polyi fields on the PVAL entry.
the CQUAD4 or CTRIA3 entry. This
property is optional.
204 Patran Interface to MD Nastran Preference Guide
Element Properties
Additional properties on the form which do not appear on the previous page are:
Use this form to create a CSHEAR element and a PSHEAR property. This defines a shear panel element
of the structural model.
Chapter 2: Building A Model 205
Element Properties
Additional properties on the form which do not appear on the previous page are:
Nonlinear Formulation This optional property word can take on any of the three values
Automatic, Large Strain, or Small Strain and is only recognized for
implicit nonlinear (SOL 400) analyses. Automatic is the default if not
specified and determines if large or small strain is appropriate based
on the existence of an elastoplastic material constitutive model and/or
if the elements are contained in a contact body. If appropriate, the
PSHEARN entry is written for this property set. Large Strain forces
the PSHEARN entry to be written, regardless; and Small Strain forces
it not to be written, regardless. In addition, if large strain is forced or
detected, the usage of NLMOPTS, LRGSTRN,0 or 1 is written based
on the setting on the Load Increment Parameters form when defining
a Subcase. See Static Subcase Parameters for Implicit Nonlinear
Solution Type, 376.
Solid (CHEXA)
This subordinate form appears when the Input Properties button is selected on the Element Properties
form and the following options are chosen.
Use this form to create a CHEXA, CTETRA, or CPENTA element and a PSOLID property or a CHEXA
and a PCOMP property.
Chapter 2: Building A Model 207
Element Properties
208 Patran Interface to MD Nastran Preference Guide
Element Properties
Additional properties on the form which do not appear on the previous page are:
Nonlinear Formulation This optional property word can take on any of the three values
Automatic, Large Strain, or Small Strain and is only recognized for
implicit nonlinear (SOL 400) analyses. Automatic is the default if not
specified and determines if large or small strain is appropriate based on
the existence of an elastoplastic material constitutive model and/or if the
elements are contained in a contact body. If appropriate, the PSLDN1
entry is written for this property set. Large Strain forces the PSLDN1
entry to be written, regardless; and Small Strain forces it not to be
written, regardless. In addition, if large strain is forced or detected, the
usage of NLMOPTS, LRGSTRN,0 or 1 is written based on the setting on
the Load Increment Parameters form when defining a Subcase. See
Static Subcase Parameters for Implicit Nonlinear Solution Type, 376.
Hex/8, Tet/10
Use this form to create a CHEXA, CTETRA, or CPENTA element and a PSOLID property.
210 Patran Interface to MD Nastran Preference Guide
Element Properties
Additional properties on the form which do not appear on the previous page are:
Use this form to create a CQUAD, CQUAD4, CQUAD8, CTRIA3, or CTRIA6 element and a PLPLANE
property.
Hyperelastic CTRIAX
Formulation
Chapter 2: Building A Model 213
Element Properties
Use this form to create a CQUADX or CTRIAX element and a PLPLANE property.
Use this form to create a CHEXA, CTETRA, or CPENTA element and a PLSOLID property.
Additional properties on the form which do not appear on the form above:
Nonlinear Formulation This optional property word can take on any of the three values
Automatic, Large Strain, or Small Strain and is only recognized for
implicit nonlinear (SOL 400) analyses. Automatic is the default if not
specified and determines if large or small strain is appropriate based on
the existence of an elastoplastic material constitutive model and/or if the
elements are contained in a contact body. If appropriate, the PSLDN1
entry is written for this property set. Large Strain forces the PSLDN1
entry to be written, regardless; and Small Strain forces it not to be
written, regardless. In addition, if large strain is forced or detected, the
usage of NLMOPTS, LRGSTRN,0 or 1 is written based on the setting
on the Load Increment Parameters form when defining a Subcase. See
Static Subcase Parameters for Implicit Nonlinear Solution Type, 376.
Use this form to create CHEXA elements and a PCOMP (SOL 600) or PCOMPLS (SOL400) property.
216 Patran Interface to MD Nastran Preference Guide
Element Properties
Create Action
The first step in using the beam library is to select the section icon for the particular cross section desired
(e.g. I-section).Then the dimensions for each of the components of the beam section must be entered.
218 Patran Interface to MD Nastran Preference Guide
Beam Modeling
Current
beam
section as
selected
from the
section
library icon
palette. The
required
dimensions
are shown.
Enter the
dimensions
of the beam
section
here,
referring to
the beam
section
icon.
List of existing beam sections. This list can be filtered to contain only the section names
of interest using the filter mechanism.
Chapter 2: Building A Model 219
Beam Modeling
Finally, a section name must be entered and the Apply button pushed. The other options available with
the beam library are documented in the Patran Reference Manual, see Beam Library (p. 475) in the Patran
Reference Manual. Once one or more beam sections have been defined, these can be selected in the
section data box on the element properties form.
Supplied Functions
I-Beam - Six dimensions -- lower flange thickness (t1), upper flange thickness
(t2),lower flange width (w1), upper flange width (w2), overall height (H), and web
thickness (t)-- allows for symmetric or unsymmetrical I-beam definition.
Angle - Open section, four dimensions -- overall height (H), overall width (W),
horizontal flange thickness (t1), vertical flange thickness (t2).
Tee - Four dimensions -- overall height (H), overall width (W), horizontal flange
thickness (t1), vertical flange thickness (t2).
Box-Symmetric - Closed section, four dimensions -- overall height (H), overall width
(W), top and bottom flange thicknesses (t1), side flange thicknesses (t2).
Tube - Closed section, two dimensions -- outer radius (R1), inner radius (R2).
Channel - Open section, four dimensions -- overall height (H), overall width (W), top
and bottom flange thicknesses (t1), shear web thickness (t).
220 Patran Interface to MD Nastran Preference Guide
Beam Modeling
Bar - Solid section, two dimensions -- height (H) and width (W).
Hat - Four dimensions -- overall height (H), top of hat flange width (W), bottom of hat
flange width for one side (W1), thickness (t).
H-Beam - Four dimensions -- overall height (H), width between inner edges of vertical
flanges (W), horizontal shear web thickness (t), and thickness of one vertical flange
(W1/2).
Cross - Four dimensions -- overall height (H), vertical flange thickness (t), horizontal
flange thickness (t2), length of free horizontal flange for one side (W/2).
Z-Beam - Four dimensions -- overall height (H2), height of vertical flange between as
measured between horizontal flanges, length of free horizontal flange for one side (W),
thickness (t1).
Hexagonal - Solid section, three dimensions -- overall height (H), overall width (W),
horizontal distance from side vertex to top or bottom surface vertex along the common
edge (i.e., diagonal edge hypotenuse times the cosine of the exterior diagonal angle).
When the Value Type is Vector and the Bar Orientation data box is selected the following select box
appears on the screen.
These select tools provide different options for defining vectors. They are discussed in
more detail in the Select Menu (p. 35) in the Patran Reference Manual.
These tools
provide different
ways to define
vectors. In
addition, the user
These three tools define the orientation vector is requested to
as the 1 (x), 2(y), or 3(z) axis of a selected select a coordinate
coordinate system. This is a convenient way system in which
to specify the orientation when it is aligned this vector is
with one of the three axes of a rectangular defined.
coordinate system. When the system is not The simplest list
rectangular (e.g. cylindrical) these tools may processor syntax
not provide the desired definition because the that appears in the
defined vector does not change direction at databox for a
different points in space--these tools just vector in an
provide an alternate way to define a global alternate
vector. coordinate system
is <x_component,
y_component,
z_component>
coord cord_id (e.g.
<1, 0, 0> coord 3).
In many cases it is
easy to simply type
a definition in this
form into the Bar
This tool may be used to define a general vector Orientation
with respect to an alternate coordinate system. databox.
When this icon is picked, the select menu changes
to the one on the right.
After the orientation has been defined, there are two ways to verify its correctness in Patran. The first
option is in the Element Properties application. By selecting the Show Action, the Definition of X Y
Plane property, and Display Method Vector Plot, the vectors defining the orientation will be shown on
the model. A second option can be used when the Beam Library has been used to define the beam cross
section. There is an option on the Display form Display>LBC/Element Property Attributes (p. 385) in the
Patran Reference Manual called Beam Display. The menu allows different display options for displaying
an outline of the defined cross section on the model in the correct location and orientation.
Users should be aware of one difference between the Patran and MD Nastran definitions for cross section
orientation. In Patran the orientation is completely independent of the analysis coordinate system at the
beam nodes. In MD Nastran, the orientation vector is assumed to be defined in the same system as the
analysis system at the first node of the beam. In Patran it is perfectly permissible to define the orientation
in a different coordinate system from that analysis system. When the NASTRAN input file is generated,
the necessary transformation of this vector to the analysis system at node 1 will be performed.
222 Patran Interface to MD Nastran Preference Guide
Beam Modeling
typed into the Offset @ Node 1 and Offset @ Node 2 data boxes define the end offsets to be radially
inward.
R
Z1
X
Z
Defines the general load type to be applied. Object choices are Displacement, Force,
Pressure, Temperature, Inertial Load, Initial Displacement, Initial Velocity, Velocity,
Acceleration, Distributed Load, CID Distributed Load, Total Load, Contact, Initial
Temperature, Planar Rigid Wall and Init.Rotation Field.
The following table outlines the options when Create is the selected Action.
Object Type
• Displacement • Nodal
• Element Uniform
• Element Variable
• Force • Nodal
• Pressure • Element Uniform
• Element Variable
• Temperature • Nodal
• Element Uniform
• Element Variable
• Inertial Load • Element Uniform
• Initial Displacement • Nodal
• Initial Velocity • Nodal
• Velocity • Nodal
• Acceleration • Nodal
• Distributed Load • Element Uniform
• Element Variable
• CID Distributed Load • Element Uniform
• Element Variable
• Total Load • Element Uniform
• Contact • Element Uniform
• Initial Plastic Strain • Element Uniform
• Initial Stress • Element Uniform
• Initial Temperature • Nodal
• Planar Rigid Wall * • Nodal
• Init. Rotation Field * • Nodal
Static
This subordinate form appears when the Input Data button is selected on the Loads and Boundary
Conditions form and the Current Load Case Type is Static. The Current Load Case Type is set on the Load
Case form. For more information see Loads & Boundary Conditions Form, 224. The information on the
Chapter 2: Building A Model 227
Loads and Boundary Conditions
Input Data form will vary depending on the selected Object. Defined below is the standard information
found on this form.
228 Patran Interface to MD Nastran Preference Guide
Loads and Boundary Conditions
Time Dependent
This subordinate form appears when the Input Data button is selected on the Loads and Boundary
Condition form and the Current Load Case Type is Time Dependent. The Current Load Case Type is set
on the Load Case form. For more information see Loads & Boundary Conditions Form, 224 and Load
Cases, 246. The information on the Input Data form will vary, depending on the selected Object. Defined
below is the standard information found on this form.
230 Patran Interface to MD Nastran Preference Guide
Loads and Boundary Conditions
When specifying real values in the Input Data entries, spatial fields can be referenced. All
defined spatial fields currently in the database are listed. If the input focus is placed in the Input
Data entry and a spatial field is selected by clicking in this list, a reference to that field will be
entered in the Input Data entry.
Chapter 2: Building A Model 231
Loads and Boundary Conditions
Object Tables
These are areas on the static and transient input data forms where the load data values are defined. The
data fields that appear depend on the selected load Object and Type. In some cases, the data fields also
depend on the selected Target Element Type. The following Object Tables outline and define the various
input data that pertains to a specific selected object:
Creates MD Nastran SPC1 and SPCD Bulk Data for Displacement entries. All non blank entries will
cause an SPC1 entry to be created. If the specified value is not 0.0, an SCPD entry will also be created
to define the non zero enforced displacement or rotation. Phase angle specifications will create DPHASE
entries for all corresponding non blank translational or rotational data in frequency response analysis.
Displacement, Velocity and Acceleration LBCs used in frequency response / dynamic analysis also
define the RLOAD1 entries with DISP, VELOC, and ACCEL keywords, respectively. For frequency
response analysis, the LBCs must reference a frequency range of interest defined as a non-spatial
frequency field such that a TABLEDi entry is created. The load case needs to be defined as
Time/Frequency dependent to do this. Values given via this option are total enforced values. For relative
enforced values used in SOL 400, see the description for the Relative Displacement option below.
Element Variable
Applies a zero or nonzero total displacement boundary condition to the face of solid elements. The
primary use of this boundary condition is to apply constraints to p-elements; but it may also be used for
standard solid elements. If applied to a p-element solid, the appropriate FEFACE and GMBC entries are
created. If applied to a standard solid element, the appropriate SPC1 and SPCD entries are created. In
232 Patran Interface to MD Nastran Preference Guide
Loads and Boundary Conditions
frequency response analysis, the phase angles are written as DPHASE entries. See comments above for
nodal displacements.
Applies a zero or nonzero relative displacement boundary condition as opposed to a total magnitude. This
is used in SOL 400 only with multiple steps and not applicable to other solution sequences. This LBC
will be ignored if present in a referenced load case for solution sequences other than SOL 400. The
appropriate SPC1 and SPCR entries are created. For example, if a DOF is specified on a SPCR with 0.0
for step 2, the relative displacement of this DOF for step 2 with respective to step 1 is 0.0. The total
displacement of step 2 is 0.2 if the solution of step 1 for this DOF is 0.2.
Force
Object Type Analysis Type
Force Nodal Structural
Creates MD Nastran FORCE and MOMENT Bulk Data entries. Creates the DPHASE entries in
frequency response analysis when specifying phase angles for out-of-phase loading. RLOAD1 entries are
created for dynamic analysis and reference the appropriate FORCE entries. For frequency response
analysis, the force LBCs must reference a frequency range of interest defined as a non-spatial frequency
field such that a TABLEDi entry is created. The load case needs to be defined as Time/Frequency
dependent to do this.
Chapter 2: Building A Model 233
Loads and Boundary Conditions
Pressure
Object Type Analysis Type Dimension
Pressure Element Uniform Structural 2D
Temperature
Object Type Analysis Type
Temperature Nodal Structural
This option applies only to the P-formulation elements. A TEMPF and DEQATN entry are created for
the constant temperature case. A TEMPF and TABLE3D entry are created for the case when a spatial
field is referenced.
Inertial Load
Object Type Analysis Type
Inertial Load Element Uniform Structural
The acceleration and velocity vectors are defined with respect to the input analysis coordinate frame. The
origin of the rotational vectors is the origin of the analysis coordinate frame. Note that rotational velocity
and rotational acceleration cannot be defined together in the same set.In generating the GRAV and
RFORCE entries, the interface produces one GRAV and/or RFORCE entry image for each Patran
load set.
Initial Displacement
Object Type Analysis Type
Initial Displacement Nodal Structural
Initial Velocity
Object Type Analysis Type
Initial Velocity Nodal Structural
Distributed Load
Object Type Analysis Type Dimension
Distributed Load Element Uniform Structural 1D
Element Variable
Defines distributed force or moment loading along beam elements using MD Nastran PLOAD1 entries.
The coordinate system in which the load is applied is defined by the beam axis and the Bar Orientation
element property. The Bar Orientation must be defined before this Distributed Load can be created. If the
Bar Orientation is subsequently changed, the Distributed Load must be updated manually if necessary.
For the element variable type, a field reference is evaluated at each end of the beam to define a linear load
variation.
Defines a distributed force or moment load along the edges of 2D elements. The coordinate system for
the load is defined by the surface or element edge and normal. The x direction is along the edge. Positive
x is determined by the element corner node connectivity. See Patran Element Library (p. 341) in the
Reference Manual - Part III. For example, if the element is a CQUAD4, with node connectivity of 1, 2,
3, 4. The positive x directions for each edge would be from nodes 1 to 2, 2 to 3, 3 to 4, and 4 to 1. The z
direction is normal to the surface or element. Positive z is in the direction of the element normal. The y
direction is normal to x and z. Positive y is determined by the cross product of the z and x axes and always
points into the element. The MD Nastran entries generated, depend on the element type.
For the element variable type, a field reference is evaluated at all element nodes lying on the edge.
Chapter 2: Building A Model 239
Loads and Boundary Conditions
Contact
Object Type Analysis Type
Contact Element Uniform Structural
This form is used to define certain data for the MD Nastran Input entries. Other data entries are defined
under the Analysis Application when setting up a job for nonlinear static or nonlinear transient dynamic
analysis. A contact table is also supported; by default, all contact bodies initially have the potential to
interact with all other contact bodies and themselves. This default behavior can be modified under the
Contact Table form, located on the Solution Parameters subform in the Analysis Application when
creating a Load Step.
Description
Friction Coefficient of static friction for this contact body. For contact between two
Coefficient (MU) bodies with different friction coefficients, the average value is used.
Define (type of contact) Select 1) Analytic Contact, 2) Contact Area, 3) Exclusion Region, or 4) Glue
Deactivation. The Contact Area and Exclusion Region are defined using MD
Nastran entry BCHANGE in the .bdf file, with NODE for Contact Area, and
EXCLUDE for Exclusion Region. The Glue Deactivation is defined using
MD Nastran entry UNGLUE.
Boundary Type Select either 1) Analytic, or 2) Discrete. By default, a deformable contact
body boundary is defined by the free faces of its elements; this is used by the
Discrete option. However, instead of using the free faces of the elements
(Discrete), it is possible to use spline surfaces (2D) to represent the outer
faces (element faces) of the contact bodies; this is used by the Analytic
option. The Analytic option can improve the accuracy of deformable-
deformable contact analysis.
C0 Continuity Using this, enforces C0-continuity at edges where the normal vector to the
outer contour of the structure indicates a discontinuity. This is enabled for 3D
analysis only.
Auto Detect Select this to cause the automatic detection of any discontinuity.
Discontinuities
Feature Angle If the angle between the normals of two touching (adjacent) segments of
contact bodies is greater than the Feature Angle, there is a discontinuity there,
and the discontinuity (at edge) is preserved.
MFD Increment The MFD file contains the spline surfaces that were created to represent some
or all of the outer faces of the contact model. Using this causes the spline
surfaces to be written to an MFD file every nth increment. This file is an
Patran database, and can be opened with Patran, and the spline surfaces can
be compared with the contact model.
Select See Select Deactivation Region, 242
Discontinuities...
Edge Contact... See Edge Contact Subform, 242
Select Contact Area... See Select Contact Area, 242
Select Exclusion See Select Exclusion Region, 242
Region...
Select Deactivation See Select Deactivation Region, 242
Region...
Description
Select (entity type) Choose to either select Geometry or FEM to define any discontinuities.
Detect Discontinuities Click on this button to determine if there are any discontinuities for the
entities that define the Application Region.
Define Discontinuities Select entities to define the discontinuities.
Description
Include Outside (Solid When detecting contact of solid elements (for example, CHEXA elements)
Element) use this to include contact of the outside of the elements. For details refer to
the BCBODY entry (defines a flexible or rigid contact body in 2D or 3D)
of the MD Nastran QRG. The entry that is used for the BCBODY entry is
COPTB (flag that indicates how body surfaces may contact).
Check Layers (Shell For contact bodies composed of shell elements, this option menu chooses
Element) the layers to be checked. Available options are: Top and Bottom, Top Only,
Bottom Only. Check Layers and Ignore Thickness combination enters the
appropriate flag in the 10th field of the 2nd data block.
Ignore Thickness Turn this button ON to ignore shell thickness. Check Layers and Ignore
Thickness combination enters the appropriate flag in the 10th field of the
2nd data block.
Include Edges (Edges) Use this to specify how body surfaces may contact. There are three options,
Beam/Bar, Free and Hard Shell, or Both. For details refer to the BCBODY
entry (defines a flexible or rigid contact body in 2D or 3D) of the MD
Nastran QRG. The entry that is used for the BCBODY entry is COPTB (flag
that indicates how body surfaces may contact).
Description
Select (entity type) Choose to either select Geometry or FEM to define the contact area.
Define Contact Area Select entities to define the contact area.
Description
Select (entity type) Choose to either select Geometry or FEM to define the exclusion region.
Define Exclusion Select entities to define the exclusion region.
Region
Description
Select (entity type) Choose to either select Geometry or FEM to define the glue deactivation
region.
Define Deactivated Select entities to define the entities that are to be un-glued.
Entities
Input Description
Flip Contact Side Upon defining each rigid body, MSC.Patran displays normal vectors or tic
marks. These should point inward to the rigid body. In other words, the side
opposite the side with the vectors is the side of contact. Generally, the vector
points away from the body in which it wants to contact. If it does not point
inward, then use the modify option to turn this toggle ON. The direction of the
inward normal will be reversed.
Symmetry Plane This specifies that the surface or body is a symmetry plane. It is OFF by
default.
Null Initial Motion This toggle is enabled only for Velocity and Position type of Motion Control.
If it is ON, the initial velocity, position, and angular velocity/rotation are set to
zero in the CONTACT option regardless of their settings here (for increment
zero).
Motion Motion of rigid bodies can be controlled in a number of different ways:
Control velocity, position (displacement), or forces/moments.
Velocity For velocity controlled rigid bodies, define the X and Y velocity components
(vector) for 2D problems or X, Y, and Z for 3D problems.
Angular For velocity controlled rigid bodies, if the rigid body rotates, give its angular
Velocity (rad/time) velocity in radians per time (seconds usually) about the center of rotation
(global Z axis for 2D problems) or axis of rotation (for 3D problems).
Friction Coefficient of static friction for this contact body. For contact between two
Coefficient (MU) bodies with different friction coefficients the average value is used.
Rotation This is a point or node that defines the center of rotation of the rigid body. If
Reference Point left blank the rotation reference point will default to the origin.
Axis of For 2D rigid surfaces in a 3D problem, aside from the rotation reference point,
Rotation if you wish to define rotation you must also specify the axis in the form of a
vector.
First Control Node This is for Force or SPCD controlled rigid motion. It is the node to which the
force or SPCD is applied. A separate LBC must be defined for the force, but
the application node must also be specified here. If both force and moment are
specified, they must use different control nodes even if they are coincident. If
only 1 control node is specified the rigid body will not be allowed to rotate.
Second Control This is for Moment controlled rigid motion. It is the node to which the moment
Node is applied. A separate LBC must be defined for the moment, but the application
node must also be specified here. It also acts as the rotation reference point. If
both force and moment are specified, they must use different control nodes
even if they are coincident.
Defines a velocity field of grid points consisting of a rotation and a traslation specification.
Creates a TIC3 Bulk Data entry.
Application Region
One or more curves, surface edges, or solid
Geometry Filter edges are defined for the Master and Slave
application regions. The application region
u Geometry can only contain geometric entities. To
model contact between FEM entities without
associated geometry, curves must first be
created from the nodes using the tools
available in the Geometry application.
Master Surface: Slide Line
Select Curves
Select the curve or edge.
Add Remove
Adds the entities in the Select
Master Region Curves databox to either the Master
Region or Slave Region depending
on the setting of the Active Region
option menu.
Slave Region
OK Clear
Chapter 2: Building A Model 249
Defining Contact Regions
Contact
The second step is to define a set of properties of these contacting surfaces. This is done by pushing the
Input Data button on the main Application form to bring up the following subordinate form.
If the Penetration Type is
One Sided, nodes in the
Input Data Slave Region are not
allowed to penetrate the
Penetration Type: One Sided segments of the Master
Region. If Two Sided, in
addition, nodes in the
Friction Coefficient (MU1) Master Region are not
allowed to penetrate
segments of the Slave
Region. This is the PTYPE
field on the BCONP entry.
Stiffness in Stick (FSTIF)
Coefficient of static friction
between the two surfaces.
This is the MU1 field on
Penalty Stiffness Scaling Factor (SFAC) the BFRIC entry.
FSTIF on the BFRIC entry
1.0 and SFAC on the BCONP
entry are penalty
parameters in the contact
Slideline Width (W1) formulation. The default
values are usually
adequate.
Create
Modify
Delete
Show
Steady State
Transient
Rotor
Unbalance (Transient only)
Unbalance Form
The Rotor Dynamics Unbalance form is used to create, modify, delete, or show Unbalances, which define
unbalance loads for transient analyses in terms of cylindrical system with the rotor axis as the Z axis.
254 Patran Interface to MD Nastran Preference Guide
Rotor Dynamics
Create
Modify
Delete
Show
Running an Analysis
3
Review of the Analysis Form 260
Translation Parameters 265
Solution Types 271
Direct Text Input 276
Solution Parameters 277
Select Superelements 352
Subcases 354
Subcase Parameters 357
Output Requests 415
Select Superelements 352
Select Explicit MPCs... 443
Non-Structural Mass Properties 444
Select NSM Properties... 449
Subcase Select 451
Restart Parameters 454
Optimize 460
Toptomize 462
Interactive Analysis 470
260 Patran Interface to MD Nastran Preference Guide
Review of the Analysis Form
Analysis Form
This form appears when the Analysis toggle is chosen on the main menu. When preparing for an analysis
run, select Analyze as the Action.
Name of job. This name will be used as the base file name
for all resulting MD Nastran files and message files.
Opens the Direct Text Input form which allows you to directly
enter data for the BULK DATA, Case Control, Executive
Control and File Management sections of the NASTRAN
input file.
Opens the Select Superelements form which allows you to
select the superelements active for the specified job.
The following table outlines the selections for the Analyze action.
Object Method
Entire Model Full Run
Check Run
Analysis Deck
Model Only
Load SimXpert
Selected Group Full Run
Check Run
Analysis Deck
Model Only
Load SimXpert
Existing Deck Full Run
Load SimXpert
Restart Full Run
Check Run
Analysis Deck
Interactive Full Run
The Object indicates which part of the model is to be analyzed. There are four choices: Entire Model,
Current Group, Existing Deck, and Restart.
• Entire Model is the selected Object if the whole model is to be analyzed.
• Selected Group is for specifying the group that contains the model that is to be analyzed. Select
the button Select Group..., under Existing Groups select the desired group, then select Cancel.
The name of the selected group will appear in the Analysis form under Group: . For more
information see The Group Menu (p. 262) in the Patran Reference Manual.
• Existing Deck is selected if you wish to simply submit an existing input file to MD Nastran.
The jobname appearing in the Job Name listbox is appended with the suffix “.bdf” to form the
input filename. This file must reside in the current directory.
You may also use Existing Deck to directly edit the MD Nastran Bulk Data file.
Chapter 3: Running an Analysis 263
Review of the Analysis Form
• Restart is selected if you wish to restart an analysis. Currently, restarts are only supported for
the Linear Static (101), Nonlinear Static (106), and Normal Modes (103) solution types. The
Restart Parameters, 454 form allows you to specify where to resume the analysis.
• Interactive analysis utilizes the Patran Preference for MD Nastran capability for performing
visual interactive modal frequency response analysis. The process begins by creating a modal
analysis solution using MD Nastran. The interactive modal frequency response analysis is then
performed using Patran Analysis: Analyze / Interactive / Full Run. The chain that is followed is
1) using Select Nastran .MASTER... select a .DBALL file, 2) using Create Loading... specify the
loading (for example, Acoustic, Force), 3) using Output Requests... specify the desired output,
and 4) using View Results... view the results.
The Method indicates how far the translation is to be taken.The methods are listed below:
• Full Run is the selected type if an Analysis Deck translation is done, and the resulting input file
is submitted to MD Nastran for complete analysis.
• Check Run is the selected type if an Analysis Deck translation is done, and the resulting input
file is submitted to MD Nastran for a check run only.
• Analysis Deck is the selected type if the Model Deck translation is done, plus all load case,
analysis type and analysis parameter data are translated. A complete input file, ready for MD
Nastran should be generated.
• Model Only is the selected type if a Bulk Data file is created that contains only the model data
including node, element, coordinate frame, element property, material property, and loads and
boundary condition data. The translation stops at that point.
• Load SimXpert will lauch SimXpert and automatically transfer the finite element model. The
environment variable MSC_SX_HOME must be set to a valid local installation directory of
SimXpert for this capability to be available.
In the Patran MD Nastran Interface, a subcase can be thought of as a Patran load case with some
additional parameters (e.g., Output Requests) associated with it. This association is further strengthened
since the default subcases are created for each load case and have the same name as their associated load
case. In the rest of this document, the terms load case and subcase will generally be used interchangeably.
When a specific form is referenced, Load case and Subcase will be capitalized.
Chapter 3: Running an Analysis 265
Translation Parameters
Write PARTSuperelement This is ON by default and if ON and superelements are selected (see Select
Superelements, 352 then BEGIN BULK SUPER = id sections are written in to
the input file for each selected superelement. If OFF and superelements are
selected, then SESET entries are written instead to define the superelements.
Geometry Check Checks the element shapes to make sure they are valid. You can set different
warning levels from None to Fatal depending on how crucial the element
shapes are to your model.
Use Iterative Solver Activates the iterative solver for analysis. The analysis manger does not
support this option and must be disabled when using this option.
Ext. Superelement Spec... Subform used for defining superelement specifications.
Numbering Options... Subform used to indicate offsets for all IDS to be automatically assigned
during translation.
Bulk Data Include File... Prompts you for the filename of the include file.
268 Patran Interface to MD Nastran Preference Guide
Translation Parameters
Numbering Options
This form is activated by the Numbering Options button on the Translation Parameters form. It allows
the user to indicate offsets for all IDS to be automatically assigned during translation. For example, if the
Chapter 3: Running an Analysis 269
Translation Parameters
user types 100 into the Element Properties Offset box, the numbering of element properties in the
resulting NASTRAN input file will begin at 101.
Note that both the Patran Neutral file reader and the Patran MD Nastran input file reader preserve the IDs
of named entities with a “.” syntax, so that a NASTRAN PSHELL record of ID 12 will be assigned the
name “PSHELL.12.” This last option allows great continuity between input model data and output model
data. This option is ON by default and the default Syntax Marker is “.”.
270 Patran Interface to MD Nastran Preference Guide
Translation Parameters
Select File
Chapter 3: Running an Analysis 271
Solution Types
On the Analysis Application form, click Solution Type... and select the Solution Type from the list of
available Solution Types.
For Analysis Type Explicit Nonlinear:
Select ASET/QSET...
Solution
Database Cyclic Parameter
Solution Type Run Symmetry Formulation MD Nastran Version Settings
Linear Static Off Off -- -- 1
Off On -- -- 47
On Off -- -- 101
On On -- -- 114
Chapter 3: Running an Analysis 275
Solution Types
Solution
Database Cyclic Parameter
Solution Type Run Symmetry Formulation MD Nastran Version Settings
Nonlinear Static -- -- -- 66 or Below 66
-- -- -- 67 or Above 106
Normal Modes Off Off -- -- 3
Off On -- -- 48
On Off -- -- 103
On On -- -- 115
Buckling Off Off -- -- 5
On On -- -- 77
On Off -- -- 105
Complex Off -- Direct -- 28
Eigenvalue
Off -- Modal -- 29
On -- Direct -- 107
On -- Modal -- 110
Frequency Off -- Direct -- 26
Response
Off -- Modal -- 30
On Off Direct -- 108
On -- Modal -- 111
On On Direct -- 118
Transient Off -- Direct -- 27
Response
Off -- Modal -- 31
On -- Direct -- 109
On -- Modal -- 112
Nonlinear -- -- -- 66 or Below 99
Transient
-- -- -- 67 or Above 129
Implicit 400
Nonlinear
600
DDAM 2004 187
Solution
Explicit 2005 700
Nonlinear
276 Patran Interface to MD Nastran Preference Guide
Direct Text Input
Saves the current Resets the form back Resets all four
setting and data for the Clears the current to the data values it forms back to its
four sections and form. had at the last OK. previous value and
closes the form. closes the form.
Chapter 3: Running an Analysis 277
Solution Parameters
Linear Static
This subordinate form appears when the Solution Parameters button is selected on the Solution Type
form when Linear Static is selected. Depending on the setting of the Database Run and Cyclic Symmetry
parameters, this Solution Type will generate a SOL 101, 114, 1, or 47 input file.
278 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Database Run Indicates whether a Structured Solution Sequence (SOL 101 or 114) is to be used or
a Rigid Format (SOL 1 or 47). If selected, a Structured Solution Sequence is selected.
Cyclic Symmetry Indicates that this model is a sector of a cyclically repeating part (SOL 114 or 47).
Automatic Constraints Indicates that an AUTOSPC entry is requested, so that MD Nastran will constrain
model singularities.
Inertia Relief Indicates that the inertia relief flags are to be set by including the PARAM, INREL,-
1 command. This flag can only be chosen if Database Run is selected and Cyclic
Symmetry is disabled. If inertia relief is selected, a node-ID for weight generation
must be selected. A PARAM, GRDPNT and a SUPORT command will be written to
the input file using the same node-ID selected for weight generation. The SUPORT
entry will specify all 6 degrees of freedom.
Alternate Reduction Indicates that an alternate method of performing the static condensation is desired.
The PARAM, ALTRED,YES command is included if selected and if Database Run is
also selected
SOL 600 Run Indicates a SOL 600 run.
Contact Parameters Same as the contact parameters available for the Implicit Nonlinear solution type.
Only used with linear contact capability.
Shell Normal Indicates that MD Nastran will define grid point normals for a Faceted Shell Surface
based on the Tolerance Angle. This data appears on a PARAM, SNORM entry.
Tolerance Angle
Mass Calculation Defines how the mass matrix is to be treated within MD Nastran. This controls the
setting of the COUPMASS parameter. This parameter can be set to either Coupled or
Lumped. If set to Coupled, COUPMASS will be set to +1, otherwise, it will be set to
-1.
Data Deck Echo Indicates how the data file entry images are to be printed in the MD Nastran print file.
This controls the setting used for the ECHO Case Control command. This parameter
can have one of three settings: Sorted, Unsorted, or None.
Plate Rz Stiffness Factor Defines the in plane stiffness factor to be applied to shell elements. This defines the
K6ROT parameter. This is an alternate method to suppress the grid point singularities
and is intended primarily for geometric nonlinear analysis.
Maximum Printed Lines Limits the size of the MD Nastran print file that will be generated. This defines the
setting of the MAXLINES Case Control command.
Maximum Run Time Limits the amount of CPU time expressed in CPU minutes that can be used by this
run. This is used to prevent runaway jobs. This defines the setting of the TIME
Executive Control statement.
Wt-Mass Conversion Defines the conversion factor between weight and mass measures. This defines the
setting of the WTMASS parameter.
Node ID for Wt. Gener. Indicates the node ID that is to be used for the Grid Point Weight Generator. This is
the GRDPNT parameter.
Chapter 3: Running an Analysis 279
Solution Parameters
Default Initial Defines the Default Initial Temperature: TEMPD value for subcase entry
Temperature TEMP(INITIAL)
Default Load Temperature Defines the Default Load Temperature: Sets the TEMPD value for the subcase entry
TEMP(LOAD) subcase entry.
Rigid Element Type: The Rigid element type optionmenu presents three different types of rigid elements,
corresponding to the three possible values for the Nastran RIGID= case control. They
are:
• LINEAR: Selects linear rigid elements, which are the rigid elements that
have been available in MD Nastran since its inception.
• LAGR: Selects the new Lagrange rigid elements with the Lagrange multplier
method.
• LGELIM: Selects the new Lagrange rigid elements with the Lagrange
elimination method.
See the Nastran quick reference quide for more details.
Results Output Format On the Results Output Format form you choose which output formats you want to use
with your solution type. For more details, please see Results Output Format, 348.
The table outlines the Database Run and Cyclic Symmetry selections, and the SOL types that will be
used.
On Off 101
On On 114
Off Off 1
Off On 47
Nonlinear Static
This subordinate form appears when the Solution Parameters button is selected on the Solution Type
form, when Nonlinear Static is selected. If the MD Nastran version specified is Version 66 or lower, then
Solution Sequence (SOL) 66 will be employed. However, if the MD Nastran version specified is version
67 or higher, then Solution Sequence 106 will be employed except as described below. For more
280 Patran Interface to MD Nastran Preference Guide
Solution Parameters
information about specification of the MD Nastran version number, see the Translation Parameters, 265
form.
The following table outlines the selections for Large Displacements and Follower Forces, and the altered
LGDISP parameter setting for each.
This is a list of the data input, available for defining the Nonlinear Static Solution Parameters, that were
not shown on the previous page.
Normal Modes
This subordinate form appears when Solution Parameters is selected on the Solution Type form when
Normal Modes is selected. Use this form to generate a SOL 103, 115, 3, or 48 input file, depending on
the Database Run and Cyclic Symmetry parameters below.
The following table outlines the selections for Database Run and Cyclic Symmetry, and the altered SOL
type for each. Indicates whether a Structured Solution Sequence (SOLs 103 or 115) is to be used, or a
Rigid Format (SOL 3 or 48). If Database Run is selected, a Structured Solution Sequence will be selected.
This is a list of data input, available for defining the Normal Modes Solution Parameters, that were not
shown on the previous page.
Defines the method to use to extract the real eigenvalues. This parameter can be set to any
one of the following: Lanczos, Automatic Givens, Automatic Householder, Modified Givens,
Modified Householder, Givens, Householder, Enhanced Inverse Power, or Inverse Power. If
this selection is set to Lanczos, an EIGRL Bulk Data entry should be created. Otherwise,
this defines the setting of the METHOD field on the EIGR Bulk Data entry.
This is a list of data input available for defining the Real Eigenvalue Extraction that was not shown on
the previous page.
Indicates the number of scalar points that must be retained in this dynamic reduction. This
parameter can only be selected if Perform Dynamic Reduction is set to ON and Method of
Coordinate Selection is set to Manual. The Application Preference will automatically create
this many SPOINTs, and place them in the a-set and the q-set.
Defines the number of generalized coordinates to be included in the dynamic reduction.
This parameter can only be selected if Perform Dynamic Reduction is set to ON, and
Method of Coordinate Selection is set to Manual. This is the NQDES field.
Chapter 3: Running an Analysis 287
Solution Parameters
Buckling
This subordinate form appears when Solution Parameters is selected on the Solution Type form when
Buckling is selected. Use this form to generate a SOL 105, 77, or 5 input file, depending on the setting
of the Database Run and Cyclic Symmetry parameters.
The following table outlines the selections for Database Run and Cyclic Symmetry, and the altered SOL
type for each.
This is a list of data input available for defining the Buckling Solution Parameters that were not shown
on the previous page.
Defines the method to use to extract the buckling eigenvalues. This parameter can be set to any one of the
following: Lanczos, Enhanced Inverse Power, or Inverse Power. If Lanczos is selected, an EIGRL entry will be
created. If Inverse Power or Enhanced Inverse Power are selected, and EIGB entry will be created with the
METHOD field set to either INV or SINV specified, respectively.
This is a list of data input, available for defining the Buckling Eigenvalue Extraction, that was not shown
on the previous page.
Complex Eigenvalue
This subordinate form appears when Solution Parameters is selected on the Solution Type form when
Complex Eigenvalue is selected. When you specify the Database Run and Formulation parameters (from
the Solution Type form), Patran generates a SOL 107, 110, 28, or 29 input file.
The following table outlines the selections for Database Run and Formulation, and the altered SOL type
for each. If you select Database Run, a Structured Solution Sequence (SOLs 107 or 110) will be selected.
If you deselect Database Run a Rigid Format Solution Sequence (SOLs 28 or 29) will be selected.
This is a list of data input available for defining the Complex Eigenvalue Solution Parameters that was
not shown on the previous page.
Defines the imaginary component of the beginning of lines in the complex plane. These values cannot be
selected if Extraction Method is set to Upper Hessenberg. This is a list of real values. They are the
OMEGAAJ fields.
Chapter 3: Running an Analysis 295
Solution Parameters
This is a list of data input available for defining the Complex Eigenvalue Extraction that was not shown
on the previous page.
Frequency Response
This subordinate form appears when Solution Parameters is selected on the Solution Type form when
Frequency Response is selected. Patran generates a SOL 108, 111, 118, 26, or 30 input file when you
specify the Database Run, Cyclic Symmetry, and Formulation parameters (from the Solution Type form).
The following table outlines the selections for Database Run, Formulation, and Cyclic Symmetry
parameters, and the altered SOL type for each. If Database Run is selected, a Structured Solution Sequence
(SOLs 108, 111, 118) will be selected. If Database Run is deselected, a Rigid Format (SOLs 26 or 30) will be
selected.
Chapter 3: Running an Analysis 297
Solution Parameters
This is a list of data input, available for defining the Frequency Response Solution Parameters that were
not shown on the previous page.
Transient Response
This subordinate form appears when Solution Parameters is selected on the Solution Type form when
Transient Response is selected. Patran generates a SOL 109, 112, 27, or 31 input file, when you specify
Database Run and Formulation parameters (from the Solution Type form).
The following table outlines the selections for Database Run and Formulation, and the altered SOL type
for each. If Database Run is selected, a Structured Solution Sequence (SOLs 109, 112) will be selected.
If Database Run is deselected, a Rigid Format (SOLs 27 or 31) will be selected.
This is a list of data input available for defining the Transient Solution Parameters that was not shown
on the previous page.
Nonlinear Transient
This subordinate form appears when Solution Parameters is selected on the Solution Type form when
Nonlinear Transient is selected. Use this form to generate either a SOL 99 or a SOL 129 input file,
depending on the version of MD Nastran indicated on the translation parameter form except as indicated
below. Version 66 and below yields SOL 99 and Version 67 and above yields SOL 129.
Indicates that an AUTOSPC entry is requested, so that MD Nastran will
constrain model singularities.
This is a list of data input available for defining the Nonlinear Transient Solution Parameters that was
not shown on the previous page.
Implicit Nonlinear
This subordinate form appears when the Solution Parameters button is selected on the Solution Type
form when Implicit Nonlinear is selected. Use this form to generate a SOL 400 or 600 input file.
Inconsistent MPCs There are three choices for dealing with problem MPCs, 1) Reorder
(reorder the DOFs that are used to define the problem MPCs), 2) Continue
(continue the analysis with no changes to the MPCs DOFs), or 3) Stop (stop
the analysis).
Solver Type Chooses Direct Profile, Iterative Sparse, Direct Sparse , Hardware Sparse,
Multifrontal Sparse (default), or External Sparse as the solver.
Non-Symmetric Specifies non-symmetric for Solver Type of Direct Profile or Multifrontal
Sparse.
Non-Positive Definite Specifies non-positive definite option valid for all solver types, use ON. On
by default in SOL 600, use Nastran Default. Can un select this option by
using OFF.
Memory Defines the amount of work space in words. This can be left blank and the
translator will automatically determine this based on model size.
Multifrontal Sparse Parameters
Chapter 3: Running an Analysis 307
Solution Parameters
• Out-of-Core Threshold For Hardware and Multifrontal Sparse solvers only. Default is 100.
Represents the number of real*4 words in millions of words. Only for SGI
computers running the IRIX operating system.
Bandwidth Optimization Turns on the optimize option for the Direct Profile or Multifrontal Sparse
solvers and uses the Sloan algorithm. Other solvers have their own
optimizer and use it by default.
Deformable-Deformable In Double-Sided method, for each contact body pair, nodes of both bodies
Method will be checked for contact. In Single-Sided method, for each contact body
pair, only nodes of the lower-numbered body will be checked for contact.
Results are dependent upon the order in which contact bodies are defined.
Optimize Constraint Equations Use this to decrease the bandwidth of the model.
Contact Detection... See Contact Detection Subform, 309.
Separation... See Separation Subform, 311.
Friction Parameters... See Friction Parameters Subform, 312.
Enable Initial Contact Click on checkbox to activate the capability for control of initial contact.
The initial contact is for creating an MD Nastran entry BCTABLE with ID
= 0 to be used for increment 0. For SOL 600, this causes rigid contact
bodies to be moved so they just touch adjacent flexible contact bodies. For
SOL 101 and 400, a BCTABLE is used with ID = 0, which causes rigid
contact bodies to be moved, as for SOL 600, and/or adjusting the
coordinates of all active nodes on the surface of all deformable BCBODYs
to remove any prestressed condition.
Initial Contact... See Initial Contact Subform, 314.
Penetration Check This controls contact penetration checking, sometimes referred to as the
increment splitting option. Available options are: At End of Increment, Per
Iteration (default), Suppressed (Fixed), Suppressed (Adaptive). At End of
Increment means penetration is checked at the end of a load increment. Per
Iteration means that penetration is checked at the end of every iteration
within an increment. If penetration is detected, increments are split.
Suppress is to suppress this feature for Fixed and Adaptive load stepping
types.
Reduce Printout of This controls reduction of printout of surface definition.
Surface Definition
Chapter 3: Running an Analysis 309
Solution Parameters
Distance Tolerance Distance below which a node is considered touching a body (error). Leave the
box blank to have MSC.Marc calculate the tolerance as the smaller of 1/20
element edge length or 1/4 shell thickness.
Bias on Distance Tolerance Contact tolerance BIAS factor. The value should be within the range of zero to
one. Models with shell elements seem to be sensitive to this parameter. You may
need to experiment with this value if you have shell element models that will
not converge. The SOL 600 default is 0.9.
Suppress Bounding Box Check Turn ON this button if you want to suppress bounding box checking. This might
eliminate penetration, but slows down the solution.
Include Outside (Solid Element) When detecting contact of elements (beam/bar, shell, solid elements) use this to
include contact of the outside of the elements. For details refer to the BCPARA
entry (contact parameters) of the MD Nastran QRG. The entries that are used for
the BCPARA entry are ITOPBM (beam/bar), ITOPSH (plate/shell), and
ITOPSD (solid).
Include Outside (Rigid Surface) When detecting contact of rigid surfaces use this to include contact of the edges
of the surfaces. For details refer to the BCPARA entry (contact parameters) of
the MD Nastran QRG. The entries that are used for the BCPARA entry are
ITOPBM (beam/bar), ITOPSH (plate/shell), and ITOPSD (solid).
Check Layers For contact bodies composed of shell elements, this option menu chooses the
layers to be checked. Available options are: Top and Bottom, Top Only, Bottom
Only. Check Layers and Ignore Thickness combination enters the appropriate
flag in the 10th field of the 2nd data block.
Ignore Thickness Turn this button ON to ignore shell thickness. Check Layers and Ignore
Thickness combination enters the appropriate flag in the 10th field of the 2nd
data block.
Include Edges Use this to detect contact of edges. There are three options, Beam/Bar, Free and
Hard Shell, or Both. For details refer to the BCPARA entry (contact parameters)
of the MD Nastran QRG. The entries that are used for the BCPARA entry are
ITOPBM (beam/bar), ITOPSH (plate/shell), and ITOPSD (solid).
Activate Quadratic Contact Use this to detect the contact of the edges of quadratic elements (midside
nodes).
Activate 3D Beam-Beam Turn this button ON to activate 3D beam-beam contact. Activate 3D Beam-
Contact Beam Contact enters a one(1) in the 13th field of the 2nd data block. This creates
the MD Nastran Bulk Data entry BCPARA, and uses the entry BEAMP.
Chapter 3: Running an Analysis 311
Solution Parameters
Separation Subform
On the Contact Control Parameters subform, select Separation... This form controls general contact
parameters for contact separation.
Separation Criterion Specifies in which increment (current or next) the separation is allowed to occur.
Separation Criterion enters a one(1) in the 12th field of the 2nd data block if
separation is based on stresses.
Force Value Force/Stress Value is placed in the 5th field of the 3rd data block.
Stress Value
Friction Type Available options for friction Type are: None (default), Shear (for metal forming),
Coulomb (for normal contact), Shear for Rolling, Coulomb for Rolling, Stick-
Slip, Bilinear Shear, and Bilinear Coulomb. The MD Nastran entry BCPARA is
written to the .bdf file, with FTYPE used. Type and Method: places 0, 1, 2, 3, 4,
or 5 in the 4th field of the 2nd data block depending on fiction type, and places a
0 or 1 in the 5th field of the 2rd data block for friction based on nodal forces or
nodal stresses, respectively for Coulomb fiction. Stick-Slip is a Coulomb type
friction.
Method For Coulomb type of friction models (options 2, 4, and 5 above), there are 2
methods for computing friction: Nodal Stress, Nodal Force (default). Type and
Method: places 0, 1, 2, 3, 4, or 5 in the 4th field of the 2nd data block depending
on fiction type, and places a 0 or 1 in the 5th field of the 2rd data block for friction
based on nodal forces or nodal stresses, respectively for Coulomb fiction.
Relative Sliding Velocity Critical value for sliding velocity below which surfaces will be simulated as
sticking. Relative Sliding Velocity is placed in the 1st field of the 3rd data block
for all friction models except Stick-Slip.
Transition Region Slip-to-Stick transition region. Transition Region is placed in the 1st field of the
3rd data block for Stick-Slip model.
Multiplier to Friction Friction coefficient multiplier. Multiplier to Friction Coefficient and Friction
Coefficient Force Tolerance are placed in the 7th and 8th field of the 3rd data block
respectively for the Stick-Slip friction model.
Friction Force Tolerance Friction Force Tolerance. Multiplier to Friction Coefficient and Friction Force
Tolerance are placed in the 7th and 8th field of the 3rd data block respectively for
the Stick-Slip friction model.
Heat Generation Conversion A factor related to how much heat is generated by the friction process.
Factor
314 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Restart Type You can Write restart data, Read restart data and Read and Write restart data. The
default is None for no restart data.
Create Continuous Results If when restarting a job, you wish the results form the previous run to be copied
File into the new POST file, then turn this ON. This will place the RESTART or
RESTART LAST options before the POST option in the input file. Otherwise
they are placed after the POST option which flags MSC.Marc not to copy the
results to the new POST file. If you turn this ON, you must have a
restarname.t16 and/or restartname.t19 file in your local directory or
the MSC.Marc analysis will fail.
Last Converged Increment Writes a RESTART LAST instead of a RESTART option. ON by default.
Reauto OFF by default. This places a REAUTO option in the input file. Any additional
data needed for the REAUTO option are extracted from the first Load Step
information for the restart job. Only if the Restart Type is set to Read or Read and
Write is the REAUTO written or the toggle visible to the user.
316 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Restart from Increment Defines the increment to be read from the file specified in the Select Restart File
form. This is entered in the 3rd data field on the 2nd card of the RESTART
option. It is only requested when Restart Type is set to Read or Read and Write.
The last increment on the restart file is used for the RESTART LAST option
when Last Converged Increment is ON.
Increments Between Writing Defines the number of increments between writing data to the restart file. This is
entered in the 2nd data field on the 2nd card of the RESTART option. It is only
requested when Restart Type is set to Write or Read and Write. When Last
Converted Increment is ON, this is the 4th field of the 2nd data block of the
RESTART LAST option.
Select Restart File... This brings up a file browser to select the restart file when the Restart Type is set
to Read or Read and Write. This file is specified on the command line for
invoking the MSC.Marc solver using the -r option.
Chapter 3: Running an Analysis 317
Solution Parameters
Domain Decomposition
Domain Decomposition is used to partition the model into seperate parts (domains) for parallel
processing. The Method used to do this is named Domain Decomposition Method (DDM). This form
designates that domain decomposition be done manually, semi-automatically, or automatically, for either
SOL 400 or SOL 600 jobs.
Chapter 3: Running an Analysis 319
Solution Parameters
320 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Decomposition Method Set this to Automatic if you wish MD Nastran to automatically create the
domains during analysis run time. Set to Semi-Automatic if you wish to
have MSC.Patran automatically break the model into domains which can be
visualized before submittal. Set to Manual to have full control over the
domains. This requires the creation of the groups before they can be
selected here in this form and associated to a domain.
Number of Domains This determines how many domains are to be created. When you change
this number and press the Enter or Return key, the spread sheet updates with
this number of rows. The default is 1. This corresponds to the number of
CPUs desired to run the job. For the Automatic method, this is the only
input that is required and the spreadsheet is not visible.
Model or Current Group This is for choosing a part of the model to decompose for parallel
processing: Model -- decompose all of the model, Current Group --
decompose just the current group. This choice must be consistent with what
part of the model is specified for analysis (Analysis: Analyze / Entire Model
or Selected Group). This is only active if Decomposition Method is set to
Automatic or Semi-Automatic.
Metis Method There are three Methods that can be used to partition the Model or Current
Group into Domains. They are, 1) Nodal Position, 2) Element Topology, or
3) Best (a procedure that accounts for the best of the nodal, element, or
vector type algorithms). This method can only be used if Decomposition
Method is set to Automatic.
Domain Island Removal Using this option causes some parts of disjoint domains (domain islands) to
be combined with adjacent domains. This can only be used if
Decomposition Method is set to Automatic.
Coarse Graph Using this option sometimes produces domain islands (disjoint domains).
This option (the default) is recommended to reduce the time to decompose
the initial global domain. Use this only if there is a definite need for a better
decomposition. This can only be used if Decomposition Method is set to
Automatic.
Single POST File If more than one CPU processor is used to solve the problem, the
seperate/multiple results files can be compiled into a single file for
postprocessing using Single POST File.
Create Click Create to create Domain Information spreadsheet rows. After doing
this the number of rows will equal the value of Number of Domains in the
form. If Decomposition Method is set to Manual, the previously created
group names will be selectable in Select a Group window at the bottom.
Visualize This is used to display groups. Select a group name for the heading Domain
Information under Group. Click Visualize to display just that group. This
can be done for some or all of the groups.
Chapter 3: Running an Analysis 321
Solution Parameters
DDAM
DDAM is an acronym for Dynamic Design Analysis Method, or DDAM is a methodology for analyzing
ship-mounted equipment that the US Navy uses in the event of a near-miss underwater. Most FEA
products follow the DDAM methodology, as does any hand calculation. MSC has made several
improvements to its products that make DDAM easier to use.
To accommodate the special spectrum and summing conventions MSC made several modifications to
MD Nastran. A DMAP alter in MD Nastran puts out data important for a DDAM analysis. A stand-alone
Fortran program reads the MD Nastran data, calculates the spectral data, formats DDAM run
information, and sends data back to MD Nastran for further postprocessing.
MSC’s DDAM has the following capabilities.
• Calculates all three shock directions simultaneously.
• Automatically calculates the appropriate spectra from input of the coefficients.
• Performs the NRL sum.
• Contains modal selection following 3010 Rev 1 convention.
• Provides manual mode selection if needed.
• Provides mode-by-mode output if desired.
• Uses all available MD Nastran elements.
• Provides NRL summed output in MD Nastran OP2 format for use with most postprocessors.
• Offers an alternate coefficient input method is available that avoids using the Fortran program,
but the classified coefficients must be entered directly in the data file.
• Has unlimited model size.
• Uses MSC’s Lanczos Eigenvalue solver for fast solutions.
DDAM in Patran
DDAM in MD Nastran is a process that involves three main parts, and a number of smaller parts. The
entire procedure is accessed from a simple interface in Patran that integrates the process.
• Part 1, Modal Analysis - A modal analysis is run in MD Nastran. This supplies the frequencies,
mode shapes and modal participation for the model.
• Part 2, Spectrum Generation – Using the output from Part 1, you can use a Fortran program to
calculate the shock spectrum. This is based on the DDS-072 or NRL 1396 documents, or you can
manually enter your own spectrum.
• Part 3, Spectrum Application and Data Recovery – The calculated spectrum from Part 2 is
applied to the mode shapes calculated in Part 1, and the results are calculated on a mode-by-
mode basis. The results from this are then summed using an NRL sum to produce results, one set
for each shock direction.
The Patran interface presents you with a selection of options to calculate the spectrum and sum the
results. The options are stored, and when the MD Nastran modal analysis completes, the Fortran program
automatically starts, using the stored options to drive it. MD Nastran automatically resumes after the
completion of the Fortran program and finishes the analysis.
During is process, a number of files will be created that are inputs and outputs from this process, all
named jobname.xxx using the jobname chosen in Patran. The most important files are:
jobname.ddd – the DDAM potions file that drives the Fortran program
jobname.f11 – the modal information needed to calculate the spectrum
jobname.f13 – the calculated spectra information for input back into MD Nastran
jobname.ver – modal verification file
jobname.opw – Nastran OP2 file with the mode shapes
jobname.opx – Nastran op2 file with the NRL summed results for x-shock
jobname.opy – Nastran op2 file with the NRL summed results for y-shock
jobname.opz – Nastran op2 file with the NRL summed results for z-shock
Once the run is complete, you can look over both the results and the modal verification file. If the results
are not as expected or desired, there are a number of more advanced capabilities of this DDAM procedure
for more control over the process. These include some that are on the Patran forms (changes in 80%
Chapter 3: Running an Analysis 323
Solution Parameters
criterion, minimum G value) and ones that can be accessed using the Patran Direct Text capability (mode-
by-mode output, specific mode selection).
Automatic Constraints Indicates that an AUTOSPC entry is requested. MD Nastran will automatically
constrain model singularities.
Shell Normal Tol. Angle Indicates that MD Nastran will define grid point normals for a Faceted Shell Surface
based on the Tolerance Angle. This data appears on a PARAM, SNORM entry.
Mass Calculation
Chapter 3: Running an Analysis 325
Solution Parameters
• Lumped Defines how the mass matrix is to be treated within MD Nastran. This controls the
• Coupled setting of the COUPMASS parameter. This parameter can be set to either Coupled
or Lumped. If set to Coupled, COUPMASS will be set to +1, otherwise, it will be
set to -1.
Data Deck Echo
• None Indicates how the data file entry images are to be printed in the MD Nastran print
• Sorted file. This controls the setting used for the ECHO Case Control command. This
parameter can have one of three settings: Sorted, Unsorted, or None.
• Unsorted
Plate Rz Stiffness factor Defines the in plane stiffness factor to be applied to shell elements. This defines the
K6ROT parameter. This is an alternate method to suppress the grid point
singularities and is intended primarily for geometric nonlinear analysis.
Maximum Printed Lines Limits the size of the MD Nastran print file that will be generated. This defines the
setting of the MAXLINES Case Control command.
Maximum Run Time Limits the amount of CPU time expressed in CPU minutes that can be used by this
run. This is used to prevent runaway jobs. This defines the setting of the TIME
Executive Control statement.
Wt-Mass Conversion Defines the conversion factor between weight and mass measures. This defines the
setting of the WTMASS parameter.
Node id for Wt. Gener Indicates the node ID that is to be used for the Grid Point Weight Generator. This is
the GRDPNT parameter.
Default Initial Temperature Defines the Default Initial Temperature: TEMPD value for subcase entry
TEMP(INITIAL)
Default Load Temperature Defines the Default Load Temperature: Sets the TEMPD value for the subcase entry
TEMP(LOAD) subcase entry.
SUPPORT Node Selects the point you have chosen for your base input. Note that this is a required
choice with no default, and that you can only pick one node. If multiple nodes are
entered in the data box, only the first one is used.
Results Output Format On the Results Output Format form you choose which output formats you want to
use with your solution type. For more details, please see Results Output Format,
348.
326 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Explicit Nonlinear
This subordinate form appears when the Solution Parameters button is selected on the Solution Type
form when Explicit Nonlinear is selected under Preferences: Analysis... . Use this form to generate a SOL
700 input file.
Form Parameters
Execution Control DYSTATIC, DYBLDTIM, DYINISTEP, DYTSTEPERODE, DYMINSTEP,
Parameters... DYMAXSTEP, DYSTEPFCTL, DYTERMNENDMAS, DYTSTEPDT2MS
Dynamic This is for specifying the entries for the DAMPGBL Bulk Data entry. This is
Relaxation... for defining parameter values for static analysis using dynamic relaxation for
SOL 700 only.
Chapter 3: Running an Analysis 329
Solution Parameters
Form Parameters
General DYLDKND, DYCOWPRD, DYCOWPRP, DYBULKL, DYHRGIHQ,
Parameters... DYRGQH, DYENERGYHGEN, DYSHELLFORM, DYSHTHICK,
DYSHNIP
Contact DYCONSLSFAC, DYCONRWPNAL, DYCONPENOPT,
Parameters... DYCONTHKCHG, DYCONENMASS, DYCONECDT, DYCONIGNORE,
DYCONSKIPTWG
Binary Output DYBEAMIP, DYMAXINT, DYNEIPS, DYNINTSL, DYNEIPH,
Database File DYSTRFLG, DYSIGFLG, DYEPSFLG, DYRLTFLG, DYENGFLG,
Parameters... DYCMPFLG, DYIEVERP, DYDCOMP, DYSHGE, DYSTSSZ,
DYN3THDT
Time History Output This is for specifying the type of output file (Binary, ASCII, Both), and the
Request... Output Time Interval.
Hourglass Setting... See Hourglass Setting Subform, 329
Merge Rigid Mat... See Merge Rigid Material Subform, 331
Dynamic Relaxation See Dynamic Relaxation for Restart Subform, 333
for Restart...
Damping Per See Damping Per Property Subform, 335
Property...
Rigid Body Switch See Rigid Body Switch and Merge Subform, 337
and Merge...
Eulerian See Eulerian Parameters Subform, 343
Parameters...
SPH Control See SPH Control Parameters Subform, 346
Parameters...
.
Chapter 3: Running an Analysis 331
Solution Parameters
Form Parameters
Existing Hourglass List of previously created hourglass settings.
Setting
Hourglass Name Specify the name.
Property Type Specify either a Shell (2D) or Solid (3D) element type.
Control Type Choose one of several types of controlling the hourglass effects. The choices
are: 1) Standard LSDyna Viscous (Property Type = Shell or Solid), 2)
Flanagan-Belytschko Viscous (Property Type = Shell or Solid), 3) Flan-Bely.
Visc. + Vol. Integ. (exact volume integration for solid elements) (Property Type
= Solid), 4) Flanagan-Belytschko Stiffness (Property Type = Shell or Solid), 5)
Flan-Bely. Stiff. + Vol. Integ. (exact volume integration for solid elements)
(Property Type = Solid), 6) Flanagan-Bindeman Stiffness (Property Type =
Solid), 7) Fully Integrated Shell (Property Type = Shell). These entries are
defined on the HGSUPPR Bulk Data entry in the MD Nastran Quick Reference
Guide.
Hourglass This entry is defined on the HGSUPPR Bulk Data entry in the MD Nastran
Coefficient Quick Reference Guide.
Warping Hourglass This entry is defined on the HGSUPPR Bulk Data entry in the MD Nastran
Coeff. Quick Reference Guide.
Bending Hourglass This entry is defined on the HGSUPPR Bulk Data entry in the MD Nastran
Coeff. Quick Reference Guide.
Linear Bulk Visc. This entry is defined on the HGSUPPR Bulk Data entry in the MD Nastran
Coeff. Quick Reference Guide.
Quadr. Bulk Visc. This entry is defined on the HGSUPPR Bulk Data entry in the MD Nastran
Coeff. Quick Reference Guide.
Select Property Set Select a previously created element property. For example, Properties > Create
> 2D > Shell > Options: Explicit PSHELL1 > Input Properties... > Shell
Formulations > HUGHES.
Add Click Add after input all necessary data into the Hourglass Setting form to
create an Existing Hourglass Setting.
Modify Click Modify after input all changed data into the Hourglass Setting form to
update an Existing Hourglass Setting. You must first select the particular
Existing Hourglass Setting.
Form Parameters
Existing Merged List of previously merged MATRIG materials. MATRIG is an MD Nastran
Materials Bulk Data entry for defining rigid body properties.
Merged Material Specify the name of merged material to be created.
Name
Select Material to be Specify the name of an MATRIG material to merge other MATRIG materials
Merged into into.
Select Materials to Specify the names of MATRIG materials that are to be merged into the merged
be Merged material whos name is specified under Merged Material Name.
Add Click Add after input all necessary data into the Rigid Materials form to create
an Existing Merged Materials.
Modify Click Modify after input all changed data into the Rigid Materials form to
update an Existing Merged Materials. You must first select the particular
Existing Merged Materials.
Form Parameters
Relaxation Use this to not use (None Active) or use (Activated Relaxation) relaxation in
performing the simulation.
[Termination Time] The time to stop the simulation. This is optional ([ ]).
Convergence Specify convergence tolerance.
Tolerance
Number of Specify the maximum number of iterations.
Iterations
Papadrakakis Auto Click the checkbox to specify that convergence control is to be automatic
Control using the Papadrakakis method.
Chapter 3: Running an Analysis 335
Solution Parameters
Form Parameters
Papadrakakis To use this it is necessary to not select Papadrakakis Auto Control.
Convergence
Tolerance
Relaxation Factor Specify the value of the Relaxation Factor.
Time step scale Specify the value of the Time step scale Factor.
Factor
Form Parameters
Damping Type Select either Property (use property) or Stiffness (use Rayleigh damping).
System Damping Select a time dependent field under Time Dependent Field. This field will be
Constant Table multiplied by the Scalar Factor for Load Curve entry. The (X,Y,Z) Trans.
Damping Forces and (X,Y,Z) Rot. Damping Moments entries (all of these form
a 6 component load vector) are multiplied by the scaled time dependent field.
Chapter 3: Running an Analysis 337
Solution Parameters
Form Parameters
Time Dependent Select a Field, with it being entered into the System Damping Constant Table
Field list box. For example, select the field named damping_vs_time under Time
Dependent Field. For System Damping Constant Table f:damping_vs_time
appears.
Scale Factor for Specify the scale factor that will multiply the Time Dependent Field specified
Load Curve under System Damping Constant Table.
X Trans. Damping Scale factor for X translation damping forces, in the global coordinate system
Forces directions.
Y Trans. Damping Scale factor for Y translation damping forces, in the global coordinate system
Forces directions.
Z Trans. Damping Scale factor for Z translation damping forces, in the global coordinate system
Forces directions.
X Rot. Damping Scale factor for X rotation damping moments, in the global coordinate system
Moments directions.
Y Rot. Damping Scale factor for Y rotation damping moments, in the global coordinate system
Moments directions.
Z Rot. Damping Scale factor for Z rotation damping moments, in the global coordinate system
Moments directions.
Rayleigh Damping Specify the scalar coefficient () that the global stiffness matrix is multiplied
Coeff. by to obtain the Rayleigh damping matrix.
Form Parameters
Option Only option is At Start (D2R0000).
Existing Merged List of deformable body and rigid body properties that have already been merged.
Properties
Merged Body Name Specify the name of the Existing Merged Properties entry to be created.
Deformable Select an entry under Deformable Property
Property
Chapter 3: Running an Analysis 339
Solution Parameters
Form Parameters
Master Rigid Select an entry under Master Rigid Property
Property
Add Click Add to create an entry under Existing Merged Properties.
Modify Click Modify to save the changed selections under Deformable Property and Master
Rigid Property to update an Existing Merged Properties. You must first select the
particular Existing Merged Properties.
Define Set of Parts to See Define Set of Parts to be Switched Subform, 340
be Switched
Define Inertial See Define Inertial Properties of Rigid Body Subform, 342
Properties of Rigid
Body
340 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Form Parameters
Option Only option is At Stage (D2RAUTO).
Existing Merged List of deformable body and rigid body properties that have already been merged.
Properties
Merged Body Name Specify the name of the Existing Merged Properties entry to be created.
Deformable Select an entry under Deformable Property.
Property
Master Rigid Select an entry under Master Rigid Property. For example, a 2D Shell Element Property
Property created using an Isotropic (SOL 700) Rigid MATRIG material.
Add Click Add to create an entry under Existing Merged Properties.
Modify Click Modify to save the changed selections under Deformable Property and Master Rigid
Property to update an Existing Merged Properties. You must first select the particular
Existing Merged Properties.
Starting Switch Time Specify the time to switch the deformable and rigid properties.
Ending Switch Time Specify the time to terminate the switching of the deformable and rigid properties.
Delay Period Specify the time delay ( for switching.
Rigid Wall/Contact Specify the surface numbers for rigid walls/surfaces that are to contact.
Surf Number
Related Switch Set
Max. Permited Time Specify the maximum time step.
Step Size
Number of Specify the number of deformable parts that will be switched to rigid parts.
Deformable Parts to
Rigid
Number of Rigid Specify the number of rigid parts that will be switched to deformable parts.
Parts to Deformable
Activation Code Select one of the five flags, 1) EQ.0, 2) EQ.1, 3) EQ.2, 4) EQ.3, or 5) EQ.4.
Switch
Pair of Related Select one of the three flags, 1) EQ.0, 2) EQ.1, 3) EQ.-1.
Switches
Nodal Rigid Body Select one of the three flags, 1) EQ.0, 2) EQ.1, 3) EQ.2.
Activation Flag
Nodal Constraint Select one of the three flags, 1) EQ.0, 2) EQ.1, 3) EQ.2.
Activation Flag
Rigid Wall Select one of the three flags, 1) EQ.0, 2) EQ.1, 3) EQ.2.
Activation Flag
342 Patran Interface to MD Nastran Preference Guide
Solution Parameters
.
Chapter 3: Running an Analysis 343
Solution Parameters
Form Parameters
Option Only option is New Rigid Props. (D2RINNER).
Master Rigid Select a Master Rigid Property. For example, a 2D Shell Element Property
Property created using an Isotropic (SOL 700) Rigid MATRIG material.
X Coord of Center of X coordinate of center of mass.
Mass
Y Coord of Center of Y coordinate of center of mass.
Mass
Z Coord of Center of Z coordinate of center of mass.
Mass
Translational Mass Scalar mass value for translation, not rotation.
XX Comp. of Inertia XX (1,1) component of inertia tensor matrix.
Tensor (IXX)
XY Comp. of Inertia XY (1,2) component of inertia tensor matrix.
Tensor (IXY)
XZComp. of Inertia XZ (1,3) component of inertia tensor matrix.
Tensor (IXZ)
YY Comp. of Inertia YY (2,2) component of inertia tensor matrix.
Tensor (IYY)
YZ Comp. of Inertia YZ (2,3) component of inertia tensor matrix.
Tensor (IYZ)
ZZ Comp. of Inertia ZZ (3,3) component of inertia tensor matrix.
Tensor (IZZ)
Form Parameters
Euler Boundary There are three choices, 1) Default, 2) Extrapolate (extrapolate structural mesh pressure to
Treatment Euler elements at solid/fluid boundary), or 3) Element (solid/fluid boundary Euler element
pressure equals the structural element pressure at the solid/fluid boundary).
Multi-Mat. Trans. There are three choices, 1) Default (Impulse), 2) Average (face (surface) velocity is
Scheme averaged simply), or 3) Impulse (face (surface) velocity is impulse weighted).
Material Failure There are three choices, 1) Default (No Fail), 2) Fail (activates transport of fail fraction and
Option thereby keeps track of material that has failed), or 3) No Fail (failed Euler material can
support shear stress again as soon as new material enters the Euler element).
Chapter 3: Running an Analysis 345
Solution Parameters
Form Parameters
Multi-Material The multi-material Eulerian elements use an overflow array to store their material data. This
Array Size array can hold “Multi-Material Array Size” times the number of Eulerian elements. If more
the 10% of the Eulerian elements have more than one material, the value of “Multi-Material
Array Size” must be increased.
Initial Condition A parameter value used to specify the accuracy of the initial conditions in Eulerian elements,
Accuracy when using the geometric shape definition. The parameter value is specified in the input file
using PARAM, MICRO, value.
Mimimum Velocity A parameter value used to specify the minimum velocity. If a calculated velocity is less than
this, it is set to zero (0). It is mainly used to eliminate harmless small values. The parameter
value is specified in the input file using PARAM, VELCUT, value.
Maximum Velocity Specify the maximum velocity for Eulerian and Lagrangian meshes. Although it is not
usually necessary to limit the velocity in Eulerian meshes, there are occasions in regions of
near-vacuous flow where using this can be an advantage. The same thing applies to
Lagrangian meshes, where there is contact. The parameter value is specified in the input file
using PARAM, VELMAX, value, YES/NO. Default is 1.0e10, YES. See the next row for
information on what YES/NO means.
Small Mass Removal Because very high velocities occur mostly in Eulerian elements with very small mass, the
mass in these elements may need to be removed for the analysis to be stable. The above
parameter (PARAM, VELMAX) is used to specify whether or not to eliminate small
masses. YES = eliminate the mass for Eulerian elements for which the velocity is > the value
of VELMAX. NO = do not eliminate the mass for Eulerian elements for which the velocity
is > the value of VELMAX. Default = YES.
Universal Gas Specify the value of the universal gas constant. The parameter value is specified in the input
Constant file using PARAM, UGASC, value.
Single Material Specify the minimum density of single material Eulerian elements. For arbitrary Lagrange-
Elements Euler (ALE) coupling, Eulerian single material elements with strength cannot be used.
Single Mats. with Specify the minimum density of single material Eulerian elements with strength. For
Strength arbitrary Lagrange-Euler (ALE) coupling, Eulerian single material elements with strength
cannot be used.
Multi-Material Specify the minimum density of multi-material Eulerian elements.
Elements
Roe Solver Scheme Specify whether or not to use the Roe solver. The Roe solver accounts for momentum
exchange between Lagrange (structure) and Eulerian material.
Spatial Accuracy There are two schemes that can be used. They are, 1) 1st Order (left and right state variables
are taken as the values the state variables have at the left- and the right-element center), or
2) 2nd Order (left- and right-state variable values at a face by including the left-left and the
right-right element).
Time Integration There are two schemes that can be used. They are, 1) 1st Order, or 2) 2nd Order (three-stage
Scheme time integration scheme).
346 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Form Parameters
Number of Cycles Specify the number of cycles between particle sorting.
Death Time Specify the time when SPH calculations are to be stopped.
Initial Number of Specify the initial number of neighbors per particle. This parameter is for specifying how
Neighbors much memory is to be allocated for arrays during initialization. If the value is positive, the
memory will be dynamically allocated. If the value is negative, the memory allocation will
be static (constant). During the calculation only the closest SPH elements will be considered
as neighbors. Using this option can avoid memory allocation problems.
Particle Approx. There are six theories to choose from, 1) Renormalization (approximation), 2) Symmetric
Theory (formulation), 3) Sym. Renormalization (symmetric renormalization approximation), 4)
Tensor (tensor formulation), 5) Fluid Particle (fluid particle approximation), 6) Fluid
Particle Renorm (fluid particle with renormalization approximation).
Start Time Specify the time to begin particle approximation.
Maximum Velocity Maximum velocity for the SPH particles. Particles whos velocity > this value are
deactivated.
Computation of Select one of the following for two different SPH parts, 1) Particle Approximation
Approx. (approximation is calculated), or 2) No Particle Approximation (approximation is not
calculated; two different SPH materials cannot interact with each other, and penetration is
allowed).
Intergration Type Select 1) 0 ( d h t = 1--- h t div v ), or 2) 1
dt d
smoothing length.
Smoothing Length Select 1) Bucket (sort based on algorithm; very fast), or 2) Global (computation for all the
Comput. model particles ). This is done during initialization.
Box Type Select either 1) Fixed (the box remains fixed in space), or 2) Moving (the user specifies two
corners of the box and a the time dependent Field to describe the motion of the two corners).
As long as a given SPH particle is in a box, the SPH calculation for the particle is performed
for the box. If the particle leaves the box it was inside, it is deactivated.
Select Box Select the name of a box under Select Box. A box must have been previously created under
Loads/BCs: Create / Box Definition / Nodal.
Tail Vector Specify a vector, <X1 Y1 Z1>, that defines the minimum coordinates of the box
(coordinates of the corner of the box at the minimum location).
348 Patran Interface to MD Nastran Preference Guide
Solution Parameters
Form Parameters
Head Vector Specify a vector, <X2 Y2 Z2>, that defines the maximum coordinates of the box
(coordinates of the corner of the box at the maximum location).
Motion Vs Time Specify the time dependent Field that defines the motion of the two corners of the box.
Data
Vel./Disp. Flag Specify whether the time dependent Field is a Velocity or Displacement field.
Coord. System Specify the coordinate system that the Tail and Head Vectors are defined in.
A new variable has been added to the settings.pcl file for results output format defaults per SOL
sequence:
NASTRAN_nnn_DATA_OUTPUT OP2+PUNCH
Where nnn is the solution sequence 101, 400 etc... and OP2+XDB+PRINT+PUNCH+MASTER
+DBALL are the options. This variable is only read from the settings.pcl file when opening a new
database, creating a new job or changing the solution sequence of an existing job. Otherwise the results
output settings are retrieved from the database for an existing job. Note that these variables must be added
to the settings.pcl file by the user and if they do not exist, a standard default is used. Also note that OP2
and XDB are mutually exclusive and both cannot be specified at the same time. The same is true for
MASTER Only and MASTER/DBALL. The settings.pcl file may have one of these variables for each
SOL sequence defined in Patran (>100).
350 Patran Interface to MD Nastran Preference Guide
Solution Parameters
ADAMS Preparation
This form is used when you want to prepare a database for an Adams job.
Chapter 3: Running an Analysis 351
Solution Parameters
SE5 SE6
SE4
In this example, SE1, SE2, & SE3 are upstream of the residual.
SE0 This is not necessary to define in the SE tree. However SE4 is
upstream of SE3 and SE5 & SE6 are upstream of SE4. These
should be defined in the tree.
354 Patran Interface to MD Nastran Preference Guide
Subcases
3.7 Subcases
This form appears when the Subcases... button is selected on the Analysis form. The subcase is the MD
Nastran mechanism for associating loads and boundary conditions, output requests, and various other
parameters to be used during part of a complete run.
The Patran MD Nastran interface automatically associates default parameters and output requests with
each Patran load case to create a subcase with the same name as the load case. You can access the Subcase
Parameters... and Output Requests... forms to view or modify these defaults.
Deleting Subcases
To delete subcases, select Subcases from the Analysis form, and set the Action to Delete.
Editing Subcases
To edit global data for subcases, select Subcases from the Analysis form, and set the Action to Global
Data. The following form appears.
Defines the number of increments to be used to apply the full load. This is the NINC field.
Activates a normal mode analysis of the prestressed system at the end of the subcase.
360 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
This is a list of data input available for defining the Static Nonlinear Iterations that was not shown on the
previous page.
Maximum number of controlled increment steps allowed within the subcase. This is the
MXINC field.
362 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
This is a list of data input available for defining the Transient Nonlinear Iterations that was not shown
on the previous page.
Defines the method to use to extract the real eigenvalues. This parameter can be set to any one of the
following: Lanczos, Automatic Givens, Automatic Householder, Modified Givens, Modified Householder,
Givens, Householder, Enhanced Inverse Power, or Inverse Power. If this is set to Lanczos, this indicates that
an EIGRL Bulk Data entry should be created. Otherwise, this defines the setting of the METHOD field on the
EIGR Bulk Data entry.
This is a list of data input available for defining the Real Eigenvalue Extraction that was not shown on
the previous page.
Synchronous (default) or
Asynchronous
Defines the SYNCFLG field of the MD Nastran
RGYRO Bulk Data entry.
No. of Time Steps and Delta-T determine the solution points in time. The skip factor defines which of the
solution points you wish to perform results processing on. A skip factor of 1 indicates every time step, 2
indicates every other solution step, etc. Total solution time accumulates in order of entry.
For the example shown, MD Nastran will calculate output at 100 time steps ranging between 1. and 100.
Define Damping
Use this form to define Damping in a linear table. Values of frequency must be positive. Discontinuities
(same value of frequency, different value of damping) are allowed at all locations except the first and last
entries in the table. See MD Nastran Quick Reference Guide TABDMP1 for more information.
Modal Damping does not allow a discontinuity to exist as either the first or last entries in the modal
damping data. This will cause an error in MD Nastran. It is strongly recommended that you do not create
such scenario.
If the first and second frequencies (two lowest frequencies) are the same value, a warning will be issued,
even if the damping value for those frequencies are the same. If the last and second to last frequencies
Chapter 3: Running an Analysis 369
Subcase Parameters
(two highest frequencies) are the same value, a warning will be issued, even if the damping value for
those frequencies are the same.
Frequency Solution
This is the Frequency Subcase Parameter Form.
"Add Row" adds a row after the selected row. To insert a row at the beginning of the table,
click on the row label and select "Add Row".
Direct Frequency
When the
Increment type is... Patran...
Discrete Creates a FREQ entry where Start Freq is the frequency value. Multiple Discrete rows
will be written to the same FREQ entry. End Freq. and No. Incr. columns are not used.
Linear Creates a FREQ1 entry. The Start Freq. will be the first frequency and the End Freq.
and No. Increments will have a linear progression in between.
Logarithmic Creates a FREQ2. Same as Linear, except it will have a logarithmic progression.
Modal Frequency
When the
Increment Type is... Patran...
Discrete Creates a FREQ entry where Start Freq is the frequency value. Multiple Discrete rows
will be written to the same FREQ entry. End Freq, No. Incr. and Cluster/Spread
columns are not used.
372 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
Linear Creates a FREQ1 entry. The Start Freq. will be the first frequency and the End Freq.
and No. Increments will have a linear progression in between. The Cluster/Spread
column is not used.
Logarithmic Creates a FREQ2. Same as Linear, except it will have a logarithmic progression.
Lin. Cluster Creates a FREQ3 with type set to LINEAR. This results in a linear distribution of
solution frequencies between each successive pair of natural modes in the specified
frequency interval. The Cluster value, which has a default of 1.0 is used to bias the
linear distribution of solution frequencies. A smaller cluster value has a closer spacing
towards the center, CLUSTER greater than 1.0 has a closer spacing at the ends of the
frequency range.
Log. Cluster Same as Lin. Cluster except that a logarithmic interpolation is used between the start
and end frequencies.
Lin. Spread Creates a FREQ4 entry. The default value of spread is 0.1. The spread is a fractional
amount specified for each mode. With a spread of 0.3 and No. Incr. of 21, there will be
21 evenly spaced frequencies between 0.7*FN and 1.3*FN, where FN a natural
frequency, for all natural frequencies between the specified “Start Freq” and “End
Freq” values.
Fractional Spread Creates a FREQ5 entry. Enter the Start Frequency and End Frequency. These are the
lower and upper bound for the excitation (solution) frequency domain, respectively. It
is desired to obtain a set of excitation frequencies around and at each natural frequency,
obtained previously from the corresponding modal analysis for this simulation. This is
done by providing a list of fractions; for example {fr_1, fr_2, ..., fr_n}. The list is
“multiplied” by each natural frequency to provide a list of excitation frequencies for
each natural frequency; for example fn_j * {fr_1, fr_2, ..., fr_n}, where fn_j is the jth
natural frequency. The fractions cannot be inserted on a single row of the Define
Frequencies form, but multiple rows must be created, with just one fraction per row.
Define Damping
Use this form to define the damping in a linear table. Values of frequency must be positive.
Discontinuities (same value of frequency, different value of damping) are allowed at all locations except
the first and last entries in the table. See MD Nastran Quick Reference Guide TABDMP1 for more
information.
Modal Damping does not allow a discontinuity to exist as either the first or last entry in the modal
damping data. This will cause an error in MD Nastran. It is strongly recommended that you do not create
such scenario.
If the first and second frequencies (two lowest frequencies) are the same value, a warning will be issued,
even if the damping values for those frequencies are the same. If the last and second to last frequencies
Chapter 3: Running an Analysis 373
Subcase Parameters
(two highest frequencies) are the same value, a warning will be issued, even if the damping values for
those frequencies are the same.
Synchronous (default) or
Asynchronous
Defines the SYNCFLG field of the MD Nastran
RGYRO Bulk Data entry.
Load Increment Parameters Defines whether the load increments will be fixed or adapted in each
iteration and the method by which adaptive load increments will be
determined.
Iteration Parameters Sets forth the iterative procedures that are employed to solve the
equilibrium problem at each load increment.
Contact Table Activates, deactivates, and controls the behavior of contact bodies in
the analysis.
Active/Deactive Elements Defines groups of elements to be active or deactive for the subcase.
Break Squeal Parameters For defining parameter values for modeling break squeal for the
subcase. (SOL 400 only).
Load Increment Parameters Defines whether the load increments will be fixed or adapted in each
iteration and the method by which adaptive load increments will be
determined.
Iteration Parameters Sets forth the iterative procedures that are employed to solve the
equilibrium problem at each load increment.
Contact Table Activates, deactivates, and controls the behavior of contact bodies in
the analysis.
Active/Deactive Elements Defines groups of elements to be active or deactive for the subcase
(SOL 600 only).
380 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
• Adaptive Increment Parameters... For adaptive methods, sets boundaries for incrementation.
Load Increment Parameters Defines whether the load increments will be fixed or adapted in each
iteration and the method by which adaptive load increments will be
determined.
Iteration Parameters Sets forth the iterative procedures that are employed to solve the
equilibrium problem at each load increment.
Contact Table Activates, deactivates, and controls the behavior of contact bodies in the
analysis.
Active/Deactive Elements Defines groups of elements to be active or deactive for the subcase (SOL
600 only).
Break Squeal Parameters
The Load Increment Parameters form differs depending on your designation of a Fixed or Adaptive
Increment Type and whether an arclength method is to be used if you select an Adaptive Incrementation
scheme.
384 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
Total Time This is the total time of the analysis for a particular step. It defaults to one (1) if left
blank for static load cases. For time dependent load cases, the total time is the length
of time between distinct time points if left blank. Otherwise the actual value is used
(not recommended because it can’t be variable).
# of Steps of Output Indicates that this many increments evenly spaced in time will be place in the output
file. Default is 0 if left blank. Which means all converged increments will be output
(SOL 600 only).
Quasi-static Inertial ON by default.
Damping
Criteria Multiple adaptive load stepping criteria is available. By default, none of this is
necessary. These criteria are described below in Adaptive Load Incrementation
Criteria, 387.
Time Integration Scheme For Transient Dynamics, indicates the time integration scheme to use in dynamic
analysis.
Minimum Iteration per Enter these values for a SOL 400 run. For SOL 600 these values are defined on the
Increment Iteration Parameters, 391 form.
Maximum Iteration per Enter these values for a SOL 400 run. For SOL 600 these values are defined on the
Increment Iteration Parameters, 391 form.
Matrix Update Method This is the method for controlling stiffness updates. This is the KMETHOD field on
the NLPARM entry for SOL 400 runs.
Load Increment Parameters for SOL 600 and SOL 400, Creep analysis. The MD Nastran entries used for
this are NLADAPT, NLPARM, and TSTEPNL.
386 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
Creep
Increment Type There are three choices, 1) Fixed, 2) Adaptive, and 3) Adaptive Creep.
Suggested Time Increment The approximate time step.
Total Time The total time for the creep analysis.
Max # of Increment Allowed This is for NSMAX.
Creep Tests This is for RAC.
Relative Strain Tolerance This is for TCSTRN.
Relative Stress Tolerance This is for TCSTRS.
Low Stress Cut-off Tolerance This is for TCOFF.
Chapter 3: Running an Analysis 387
Subcase Parameters
This for the MD Nastran NLAUTO entry, Parameters for Automatic Load/Time Stepping. (SOL 600
only).
Loading Table Instances Determines how loading tables (Use Tables must be ON in the Job Parameters
form) are treated. By default loads are increased or decreased such that they always
Reach Peaks-Valleys Only. If you wish you can Reach All Points in Tables or
Ignore all Points in Tables.
Write Instances to Post File Writes Loading Table Instances to the Post file if toggle is ON. Note that if toggle
is ON, then only those instances are written to the POST file and not all the
increments of the analysis. This is for IDMPFLG.
Nodal Temp. Check There are three choices, 1) Omit Check, 2) Below Finish Temperature (to complete
time period when all node temperatures are < FTEMP), and 3) Above Finish
Temperature (to complete time period when all node temperatures are > FTEMP).
This is for IFINISH.
Finish Temperature The terminal temperature. This is for FTEMP.
Use Criterion For a criteria to be used, this toggle must be turned ON.
“Criterion” Range The first and last fields are zero and 1e20 respectively and cannot change. The
second and third must be the same as well as the 4th/5th and 6th/7th which define
the ranges. The “Criterion” title changes according to the Increment Criterion
chosen.
“Criterion” Increment The “Criterion” title changes according to the Increment Criteria chosen.
Allowed
Select a Group (Optional) You can optionally select a group of elements to which this criterion is to be
applied. No group is selected by default.
Chapter 3: Running an Analysis 389
Subcase Parameters
Static
Fixed Increment
Parameter Description
Automatic Cutback Applies to Nonlinear Statics only. It is ON by default. If an increment does
not converge, it allows for a restart from the last increment cuts the
increment size in half.
Number of Cutbacks This is associated with Automatic Cutback. This parameter determines how
many times a cutback is allowed.
Number of Increments For Statics and Creep this is the number of increments specified in the
or NLAUTO option. Or for Transient Dynamics defines the number of steps to
Number of Steps use throughout the analysis for Fixed time step type. Default is 10.
Total Time For Statics, this enters the NLAUTO option which is the total time as
defined in this widget. For Transient Dynamics this is the total time.
For Creep, the total time is either placed in the 2nd data block of a CREEP
INCREMENT option or the total time is divided by the Number of
Increments, if this value is present, and the incremental time is written to the
2nd data block of the CREEP option.
Gamma / Beta For Transient Dynamics only. Default is 0.5.
Time Integration Scheme For Transient Dynamics, the Houbolt and Central Difference cannot be
selected. Indicates the time integration scheme to use in dynamic
analysis.Single Step Houbolt is the default.
Minimum Iteration per Increment Enter these values for a SOL 400 run. For SOL 600 these values are defined
on the Iteration Parameters, 391 form.
Maximum Iteration per Increment Enter these values for a SOL 400 run. For SOL 600 these values are defined
on the Iteration Parameters, 391 form.
Matrix Update Method This is the method for controlling stiffness updates. This is the KMETHOD
field on the NLPARM entry for SOL 400 runs.
Iteration Parameters
This subordinate form appears when the Subcase Parameters... / Iteration Parameters... button is selected
for Analysis Type: Static, Transient Dynamics, Creep, ... Subcases form. Unless otherwise specified all
392 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
parameter references apply to the NLSTRAT (SOL600) entry for the form on the left, and NLPARM
(SOL 400) entry for the form on the right .
Relative Energy
Relative Residual Moment
Relative Rotation
Minimum Reaction Force The value of these widgets (default is blank) is written to the appropriate
Minimum Displacement MAXxx or MINxx param.
Minimum Reaction Moment
Minimum Rotation
Maximum Residual Force
Maximum Displacement
Maximum Residual Moment
Maximum Rotation
Maximum # of Bisections
Contact Table
A contact table is used to control the behavior of and to activate or deactivate, or in some cases, remove
contact bodies from the analysis. This is used for both linear and nonlinear contact.
Chapter 3: Running an Analysis 397
Subcase Parameters
Input Description
Global Contact Detection • Changing this setting should be done with caution as it will over-write any contact
detection changes made to individual contact pairs in the cells. This option sets the
contact detection method in all cells in the contact table.
• Default (by body #) -This is the default where contact is checked in the order the
bodies are written to the input file which is the order in which they are created. In
this scenario, the most finely meshed bodies should be listed first. There will be
contact checks first for nodes of the first body with respect to the second body and
then for nodes of the second body with respect to the first body. If Single Sided
contact is activated on the Contact Parameters subform, then only the first check is
done.
• Automatic -Unlike the default, the contact detection is automatically determined
and is not dependent on the order they are listed but determined by the solver
ordering the bodies starting with those having the smallest edge length. Then there
will be only a check on contact for nodes of the first body with respect to the
second body and not the other way around.
• First ->Second - Blanks the lower triangular section of the table matrix such that
no input can be accepted. Only the contact bodies from the upper portion are
written, which forces the contact check of the first body (the one higher in the
contact table) with respect to the second body.
• Second-> First - Blanks the upper triangular section of the table matrix such that
no input can be accepted. Only the contact bodies from the lower portion are
written. Contact detection is done opposite of First->Second.
• Double-Sided -Writes both upper and lower portions of the table matrix. This
overrules the Single Sided contact parameter set on the Contact Parameters
subform.
Touch All Places a T to indicate touching status for all deformable-deformable or rigid-
deformable bodies.
Glue All Places a G to indicate glued status for all deformable-deformable or rigid-deformable
bodies.
Deactivate All Blanks the spreadsheet cells.
Import/Export Import or Export a file with contact matrix definition data. The format must be CSV.
Select Existing Select an existing Contact Table from a set of tables.
Contact Matrix A matrix defining what and how contact bodies contact.
Body Type Lists the body type for each body; either Deformable or Rigid.
Release This cell can be toggled for each body to Y or N (Yes or No). If Y, this indicates that
the particular contact body is to be removed from this Subcase. The forces associated
with this body can be removed immediately in the first increment or gradually over
the time of the entire Subcase with the Force Removal switch described below.
398 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
Input Description
The Contact Matrix entries The rows correspond to Touching Body. The columns correspond to Touched Body.
An entry of the matrix, for example (Row i,Column j), will have the entry of T, G, or
“blank”. T = touching, G = glue, “blank” = no contact. To change a matrix cell entry,
select the cell (click once) to select it, then click on the cell once to change to the next
selection. For example, T -> G.
Touching Body These are informational or convenience list boxes to allow you to see which bodies an
Touched Body active cell references and to see what settings are active for Distance Tolerance and
other related parameters below. You must click on the touched/touching bodies to see
what values, if any, have been set for the pair combination.
Distance Tolerance Set the Distance Tolerance for this pair of contact bodies. You must press the Enter or
Return key to accept the data in this data box. A nonspatial field can be referenced that
will write this data in TABLE format, if this parameter varies with time, temperature,
or some other independent variable. This overrides any other settings for Distance
Tolerance.
Bias Factor Bias the domain defined by the distance tolerance.
Analysis Properties Select Structural.
Separation Threshold Specify a threshold (force or stress) such that if the contact load (force or stress) is <
this threshold value, the contacting body remains in contact with the contacted body.
Separation Force Set the Separation Force for this pair of contact bodies. You must press the Enter or
Return key to accept the data in this data box. A nonspatial field can be referenced that
will write this data in TABLE format, if this parameter varies with time, temperature,
or some other independent variable. This overrides any other settings for Separation
Force.
Friction Coefficient Set the Friction Coefficient for this pair of contact bodies. You must press the Enter or
Return key to accept the data in this data box. A nonspatial field can be referenced that
will write this data in TABLE format, if this parameter varies with time, temperature,
or some other independent variable. This overrides any other settings for Friction
Coefficient.
Interference Closure Set the Interference Closure for this pair of contact bodies. You must press the Enter
or Return key to accept the data in this data box. A nonspatial field can be referenced
that will write this data in TABLE format, if this parameter varies with time,
temperature, or some other independent variable. This overrides any other settings for
Interference Closure.
Friction Stress Limit This is a bound on the maximum friction stress. This is the friction stress limit for the
bilinear model, t limit . If the shear stress reaches the limit value, the applied friction
force is reduced so that the maximum shear stress is given by min n limit
t .
Slide Off Distance Specify the distance a node must slide off a surface, at an edge, before the node travels
on the surface, at the edge, that is at an angle to the surface that is being slid off of.
Chapter 3: Running an Analysis 399
Subcase Parameters
Input Description
Heat Transfer Coefficient Set the Heat Transfer Coefficient for this pair of contact bodies. You must press the
Enter or Return key to accept the data in this data box. A nonspatial field can be
referenced that will write this data in TABLE format, if this parameter varies with
time, temperature, or some other independent variable. This overrides any other
settings for Heat Transfer Coefficient. This is only used in Coupled analysis (Heat
transfer and Coupled analysis not supported in MSC.Nastran 2004.
Force Removal Select 1) Immediate, or 2) Gradual. This is activated when a body is is set to Release.
For example, 1-seal can be set to Release by clicking once on the corresponding
Release cell, then clicking once again to change from N to Y. The MD Nastran entry
BCMOVE is written to the .bdf file.
Contact Detection Select 1) Automatic, 2) Double Sided, 3) 1st->2nd, or 4) 2nd->1st.
Retain Gaps/Overlaps This is only applicable for the Glued option. Any initial gap or overlap between the
node and the contacted body will not be removed (otherwise the node is projected onto
the body which is the default). For deformable-deformable contact only.
Stress-free Initial Contact This is only applicable for initial contact in increment zero, where coordinates of
nodes in contact can be adapted such that they cause stress-free initial contact. This is
important if, due to inaccuracies during mesh generation, there is a small gap/overlap
between a node and the contacted element edge/face. For deformable-deformable
contact only.
Delayed Slide Off By default, at sharp corners, a node will slide off a contacted segment as soon as it
passes the corner by a distance greater than the contact error tolerance. This extends
this tangential tolerance. For deformable-deformable contact only.
Allow Separation
Breaking Glue See Breaking Glue Parameters Subform, 400
Parameters...
Edge Contact... See Edge Contact Subform, 401
400 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
This form can only be used when there is glued contact (there is G in the Contact Table matrix cells).
.
Input Description
Max Normal Stress The maximum normal stress that will cause the glued contact to become un-glued.
Max Tangential Stress The maximum tangential stress that will cause the glued contact to become un-glued.
First Exponent The exponent of the tangential stress term (BGM) in the following equation:
Second Exponent The exponent of the normal stress term (BGN) in the following equation:
Input Description
Include Outside (Solid When detecting contact of solid elements (for example, CHEXA elements) use
Element) this to include contact of the outside of the elements.For details refer to the
BCTABLE entry (defines contact table) of the MD Nastran QRG. The entries that
are used for the BCTABLE entry are COPTM and COPTS. These flags indicate
how master and slave surfaces may contact.
Include Outside of Rigid When detecting contact of rigid surfaces use this to include contact of the outside
Surface of the rigid surfaces. For details refer to the BCTABLE entry (defines contact
table) of the MD Nastran QRG. The entries that are used for the BCTABLE entry
are COPTM and COPTS. These flags indicate how master and slave surfaces may
contact.
Check Layers For contact bodies composed of shell elements, this option menu chooses the
layers to be checked. Available options are: Top and Bottom, Top Only, Bottom
Only. Check Layers and Ignore Thickness combination enters the appropriate flag
in the 10th field of the 2nd data block.
402 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
Input Description
Ignore Thickness Turn this button ON to ignore shell thickness. Check Layers and Ignore Thickness
combination enters the appropriate flag in the 10th field of the 2nd data block.
Include Edges Use this to detect contact of edges. There are three options, Beam/Bar, Free and
Hard Shell, or Both. For details refer to the BCTABLE entry (defines contact
table) of the MD Nastran QRG. The entries that are used for the BCTABLE entry
are COPTM and COPTS. These flags indicate how master and slave surfaces may
contact.
Active/Deactive Elements
Defines groups of elements to be active or deactive for the subcase.
Solvers/Options
In general, this form is used to select the Nastran solver and other possible options. An SMETHOD case
control entry is written specifying the solver type to use and possibly an ITER bulk data entry for
additional options. Only certain solutions allow the use of the SMETHOD case control as controlled by
Chapter 3: Running an Analysis 405
Subcase Parameters
the user interface. If a solution does not support a solver option, that option is not presented in the form
or menus.
Spectrum Source Select File for a user-defined spectrum, or Coef for a DDAM style coefficient
equation. If you select File, a button appears to the right to let you select the file
where the spectrum is defined. If you select Coef, two other buttons appear:
Coef Source Select File for a user-written coefficient file, or Default to use the coefficients built
into the Fortran program. Note that the built-in coefficients we deliver in the
program are NOT the DDS-072 coefficients. If you use this option for a real
DDAM analysis, the Fortran file must be edited and recompiled. If you select File,
a button appears to the right to let you choose the file where the coefficient data is
stored.
F(x) Type Choices are NRL 1396 and DDS 072. This option toggles between the old NRL
1396 style equations, and the current DDS-072 style equations used for DDAM.
Coefficient Options
• Ship Type Select Surface or Submerged
• Mount Location Choice of Deck, Hull, or Shell.
• Elastic/Plastic Select Elastic or Plastic. Choosing Plastic uses the Elastic/Plastic coefficients;
Elastic uses the elastic coefficients.
Weight Cutoff Default uses the default value compiled into the PCL code, which is 80%. If you
choose Enter Value the text box becomes available and you can enter a percentage
manually. The number entered is the percentage, not the fraction, so 100% of the
modal mass is entered as 100.
Minimum G Level If you select N/A, no minimum G value is used. If you enter a value, all modal
accelerations below the minimum are set to the minimum.
Fore/Aft Axis It is necessary to have the model oriented orthogonal to a global cartesian axis
system, although not necessarily in one particular orientation. This toggle
identifies which global axis is to be interpreted as Fore/Aft.
Vertical Axis This identifies the axis that is in the vertical direction.
Modal Analysis
• Number of Desired Roots These are the limits that control the eigenvalue analysis and are the values from
• Lower the Nastran EIGRL entry. ND is the number of desired roots, V1 is the lower
frequency limit, V2 is the upper frequency limit. For the effects of using one of
• Upper more of these, see the EIGRL section of the MD Nastran Quick Reference Guide.
Chapter 3: Running an Analysis 409
Subcase Parameters
Defines TSTEPNL.
Similar to SOL 129,
Nonlinear Transient
Defines BCTABLE.
Similar to SOL 600 -
Implicit Nonlinear
Contact Table... Activates, deactivates, and controls the behavior of contact bodies in
the analysis.
410 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
Contact Table
A contact table is used to control the behavior of contact bodies and to activate or deactivate, or in some
cases, remove contact bodies from the analysis. This form defines the BCTABLE entry.
Additional Information
The following is also now supported for SOL 700 jobs:
• Additional Properties
• PBEAM71
• BPEAMD
• PBELTD
• PELAS1
• PLPLANE
• PLSOLID
• PSHELL1
• PSHELLD
• PSPRMA
414 Patran Interface to MD Nastran Preference Guide
Subcase Parameters
Note: Many of the output requests that can be defined on the Output Request forms currently apply
only to the printed values in the MD Nastran output file; these result quantities cannot be
imported and postprocessed in Patran. For guidance on specific quantities, review Supported
OUTPUT2 Result and Model Quantities, 502.
MD Nastran Implicit Nonlinear (SOL 600) produces stress and strain results that differ from those results
available with other solution sequences. A detailed discussion of the stress and strain measures for SOL
600 is given in Stress and Strain Measures for Nonlinear Analysis (Ch. 2) in the MSC.Nastran Implicit
Nonlinear (SOL 600) User’s Guide.
416 Patran Interface to MD Nastran Preference Guide
Output Requests
Note: The OK button accepts the output requests and closes the form. The Defaults button deletes all
output requests and replaces them with defaults. The Cancel button closes the form without saving
the output requests.
Chapter 3: Running an Analysis 417
Output Requests
1At the present time, superelement specifications are allowed only in the structured linear static solution
type (Solution Sequence 101).
418 Patran Interface to MD Nastran Preference Guide
Output Requests
Use this listbox to select the result type to This listbox is used to select the group to which the
be created. output requests relate.
Use this list box to select output requests that These are the options that are
are to be modified or deleted. appropriate to the highlighted result
type. They also indicate the options
that were selected for a highlighted
output request. See Table 3-1.
Chapter 3: Running an Analysis 419
Output Requests
Notes:
• The Edit Output Requests form opens with focus in the first result type of the first subcase.
• The top half of the Edit Output Requests form is similar to the Advanced Output Request form.
• The spreadsheet column labels are the result types for the current solution type.
• Putting focus in a cell causes the top half of the form to reflect the current setting, just like the
current advanced output request form. This means that the databox RESULT TYPE: gets
updated with the result type of the currently selected cell. The OUTPUT REQUESTS: databox is
also updated to show the actual content of the cell.
428 Patran Interface to MD Nastran Preference Guide
Output Requests
• If a cell is initially empty, selecting it will cause the top half of the form to display the
appropriate default setting for the selected result type (i.e., column).
• Selecting a column header will allow you to change all subcase output requests of a particular
type. The top half of the Edit Output Requests form will set to the default request of the
particular result type.
• When you select a set of contiguous column cells, the top half of the form will configure to the
upper most selected cell.
• You cannot select multiple columns.
Description:
This function adds either a specified version or a default version of an Output Request type to the list of
default Output Requests.
Input:
INTEGER or_num The OR number of the output request type to add (See Table 3-3).
STRING or_value The value of the selected output request type. Blank implies the
default value.
mscn_user_del_out_req (or_num)
Description:
This function deletes the specified Output Request type from the list of default Output Requests.
Input:
INTEGER or_num The OR number of the Output Request type to delete (See Table 3-3).
Code Sample
FUNTION user_change_default_out_req(sol_seq)
INTEGER sol_seq
IF (sol_seq == 101 || sol_seq == 106) THEN
Chapter 3: Running an Analysis 429
Output Requests
/* This will add this version of the Output Request type to the list
of default */
/* Output Requests for solution 101 and 106. */
mscn_user_add_out_req (4,”MPCFORCES(SORT2,REAL)=ALL FEM”)
/* This will add the default version of these Output Request types
from the list */
/* of default Output Requests for solution 101 and 106. */
mscn_user_add_out_req (10,“ ”)
mscn_user_add_out_req (6,“ ”)
/* This will delete these Output Request types from the list of
default */
/* Output Requests for solution 101 and 106. */
mscn_user_del_out_req (1)
mscn_user_del_out_req (2)
mscn_user_del_out_req (3)
END IF
END FUNCTION
The following is a table that shows the current predefined default Output Requests (those marked with
an X) and the allowed options (those marked with an O) for the various solution sequences.
Table 3-3 Result ID Number
Result ID OR Number
Number
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
(Solution
Sequence
)
101 x x x o o o o o o o o o o o o x
103 o o x o o o o o o o x
105 x o x o o o o o o o o x
106 x x x o o o o o x
107 o o x o o o x
108 x o x o o o o o o o
109 x o x o o o o o o o o o
110 o o x o o o x
111 x o x o o o o o o o
112 x o x o o o o o o o o o
114 x x x o o o o o o o x o o
115 o o x o o o o o o o
129 x o x o o o o o o o
153 o o o o o o x x o o
159 o o o o o o x x o o o o
400 x x
430 Patran Interface to MD Nastran Preference Guide
Output Requests
OR # Default Value
1 DISPLACEMENT(SORT1,REAL)=All FEM
2 STRESS(SORT1,REAL,VONMISES,BILIN)=All FEM;PARAM,NOCOMPS,-1
3 SPCFORCES(SORT1,REAL)=All FEM
4 MPCFORCES(SORT1,REAL)=All FEM
5 FORCE(SORT1,REAL,BILIN)=All FEM
6 OLOAD(SORT1,REAL)=All FEM
7 NLLOAD=All FEM
8 ESE=All FEM
9 STRAIN(SORT1,REAL,VONMISES,STRCUR,BILIN)=All FEM
10 GPSTRESS=All FEM; VOLUME # SET,PRINCIPAL,SYSTEM Coord 0; SURFACE # SET
#,FIBRE ALL,SYSTEM Coord 0, AXIS X1,NORMAL R, TOPOLOGICAL,BRANCH BREAK
11 VELOCITY(SORT1,REAL)=All FEM
12 ACCELERATION(SORT1,REAL)=All FEM
13 GPFORCE=All FEM
14 GPSDCON=All FEM; VOLUME # SET #,PRINCIPAL,SYSTEM Coord 0; SURFACE # SET
#,FIBRE ALL,SYSTEM Coord 0, AXIS X1,NORMAL R, TOPOLOGICAL 0.,BRANCH BREAK
15 ELSDCON=All FEM; VOLUME # SET #,PRINCIPAL,SYSTEM Coord 0; SURFACE # SET
#,FIBRE ALL,SYSTEM Coord 0, AXIS X1,NORMAL R, TOPOLOGICAL 0.,BRANCH BREAK
16 VECTOR(SORT1,REAL)=All FEM
17 THERMAL=(SORT1,PRINT)=All FEM
18 FLUX(SORT1,PRINT)=All FEM
19 OLOAD(SORT1,PRINT)=All FEM
20 SPCFORCES(SORT1,PRINT)=All FEM
21 ENTHALPY(SORT1,PRINT)=All FEM
22 HDOT(SORT1,PRINT)=All FEM
Chapter 3: Running an Analysis 431
Output Requests
23 NLSTRESS
24 BCCONTACT
Note: In SOL 109, 112 & 159 will have SORT2 as the default in some versions of Patran.
Directly entered entries may potentially conflict with those created by the
interface. Writing these entries to the file can be controlled with this toggle.
Available Result Types Lists all of the available result types for the analysis. The numbers
in parentheses are the MSC.Marc POST code numbers, that will be
specified on the MARCOUT entry
Selected Result Types Shows the set of result types that have been selected to be returned
in the analysis.
434 Patran Interface to MD Nastran Preference Guide
Output Requests
The following table shows the post codes that may be selected for a SOL 600 structural nonlinear
analysis.
Note: The POST CODE (<0) are for user-defined quantities via user subroutine UPSTNO.
Chapter 3: Running an Analysis 435
Output Requests
Available Result Types Lists all of the available result types for the analysis. The numbers
in parentheses are the MSC.Marc POST code numbers.
Selected Result Types Shows the set of result types that have been selected to be returned
in the analysis.
Element X-section Results Defines the number of layer points to use through the cross section
of homogeneous shells, plates and beams. This number must be
odd if not a composite.
Note: If no changes are made to the default output requests, no MARCOUT entry will be written
and MD Nastran will determine the appropriate output.
The following table shows the post codes that may be selected for a SOL 600 structural nonlinear
analysis.
If you need to find the start of the X-shock results, search for X-DIRECTION to find this header and
proceed from there.
It is necessary to specify that Patran calculate the combined stresses on a mode-by-mode basis, and NRL
sum the combined results. See Defining Translation Parameters for DDAM (SOL 187) (Ch. 4).
Since the mode-by-mode velocities and accelerations are calculated by multiplying the displacements by
the frequency (omega and omega2), MD Nastran labels them as Eigenvectors. If you ask for
displacement, velocity, and acceleration for three modes, you will find nine Eigenvectors in the .f06 file
with repeating frequencies – the first three (1-3) are displacements, the next three (4-6) velocities, and
the last three (7-9) the accelerations. The .op2 files are similar, reporting the three as Eigenvectors with
repeating frequencies. The magnitude of the values should be a clue as to what you are looking at for all
but the lowest frequencies. The Fortran Driver File (jobname.ddd)
Some of the options you choose on the Subcase Parameters form are written to an external file that is read
by the Fortran file when it calculates the spectrum. While you do not have the ability to edit this file when
using MSC.FEA, the file is a hardcopy ASCII record of what options were used when running the
DDAM analysis. The file is small and has just a few lines that comprise the answers to questions that the
ddam.exe program asks if it is run interactively. File Format (varies depending on chosen options on the
first record)
Record 1
(user spectrum file) (user coef file) (DDS-072 format)
user spectrum file= T (use a user defined spectrum)
= F (use coefficients)
user coef file = T (use an external coefficient file)
= F (use the coefficients compiled into the Fortran)
DDS-072 format = T (use DDS-072 style equations)
= F (use NRL 1396 style equations)
Record 3
pref
pref = 0.0 (use default cutoff in program)
= nnn.nn
Chapter 3: Running an Analysis 441
Output Requests
Record 4
Ming
Ming = 0.0 (no minimum G)
= n.n (use this minimum G value)
Record 5
(F/A axis) (Vert axis)
F/A axis = X (F/A is along the X axis)
= Y (F/A is along the Y axis)
= Z (F/A is along the Z axis)
Vert axis = X (Vertical is along the X axis)
= Y (Vertical is along the Y axis)
= Z (Vertical is along the Z axis)
Record 6
.f11 filename
.f11 filename = name of the .f11 file
Record 7
.f13 filename
.f13 filename = name of the .f13 file
Record 8
.ver filename
.ver filename = name of the modal verification file
Depending on the chosen options, the file will look like one of the following:
No special user options – coefficients from default source:
F F T
nsurf nstruc nplast
pref
ming
f/a_axis vert_axis
.f11 filename
.f13 filename
.ver filename
442 Patran Interface to MD Nastran Preference Guide
Output Requests
F T T
coef.dat filename
nsurf nstruc nplast
pref
ming
f/a_axis vert_axis
.f11 filename
.f13 filename
.ver filename
T F T
spec.dat filename
pref
ming
f/a_axis vert_axis
.f11 filename
.f13 filename
.ver filename
Note: Note that capitalization is required. The file is read free-format, so spacing is not important.
A sample file for a conventional analysis might look like:
F F T
1 1 1
100.
1.
X Z
d1.f11
d2.f11
d1.ver
Chapter 3: Running an Analysis 443
Select Explicit MPCs...
NSM and NSML forms are available through the Tools menu.
Selecting NSM Properties displays the NSM Properties form. NSM Properties forms are MSC Nastran
preference specific.
NSM mass can be applied as Lumped or Distributed.
Chapter 3: Running an Analysis 445
Non-Structural Mass Properties
A Select form has been added to allow for the selection of NSM properties. Multiple sets of NSMs can
be defined in the model. Only the selected sets will be used in the analysis.
The following examples display results of applying lumped and distributed NSMs.
448 Patran Interface to MD Nastran Preference Guide
Non-Structural Mass Properties
This subform appears when the Select NSM Properties... button is selected from the Subcases form.
Chapter 3: Running an Analysis 451
Subcase Select
For SOL 400 runs the Subcase Select form looks the same, except for the Select Steps for New Subcase
button being un-greyed (it is pickable).
452 Patran Interface to MD Nastran Preference Guide
Subcase Select
When the Select Steps for New Subcase button is used the following form appears.
Chapter 3: Running an Analysis 453
Subcase Select
Notice that the selected steps (lc1, lc2, lc3, lc4, and
lc5) match the selected subcases of the parent form.
This indicates that some or all of these steps can be
used in defining the new subcases. By selecting the
steps lc1 and lc3, under Steps Selected, the names
are entered under New Subcase Starting with Steps.
This indicates that two subcases will be defined,
“subcase_lc1” and “subcase_lc3”.
more information on how to submit restart jobs with Analysis Manager. Restart for SOL 600 jobs are
described on (p. 315) and (p. 458).
Name to use for the restart job. An existing restart job may be
modified and/or resubmitted by making a selection from the
Available Restart Jobs listbox.
456 Patran Interface to MD Nastran Preference Guide
Restart Parameters
Nonlinear Static
This subordinate form appears when the Restart Parameters button is selected on the Analysis form and
the solution type is Nonlinear Static.
SOL 600
This subordinate form appears when the Restart Parameters button is selected on the Solution
Parameters form.
OK Cancel
Parameter Description
Restart Type You can Write restart data, Read restart data and Read and Write restart data. The
default is None for no restart data.
Create Continuous Results File If, when restarting a job, you wish the results form the previous run to be copied into
the new .t16 file, then turn this ON. Otherwise MSC.Marc will not copy the results to
the new .t16 file. If you turn this ON, you must have a restarname.marc .t16
and/or restartname.marc.t19 file in your local directory or the MSC.Marc
analysis will fail.
Last Converged Increment Writes a RESTART LAST instead of a RESTART option. ON by default.
Reauto OFF by default. This places a REAUTO option in the MSC.Marc input file. Any
additional data needed for the REAUTO option are extracted from the first Subcase
information for the restart job. Only if the Restart Type is set to Read or Read and
Write is the REAUTO written or the toggle visible to the user.
Chapter 3: Running an Analysis 459
Restart Parameters
Parameter Description
Restart from Increment Defines the increment to be read from the file specified in the Select Restart File
form. It is only requested when Restart Type is set to Read or Read and Write. The
last increment on the restart file is used for the RESTART LAST option when Last
Converged Increment is ON.
Increments Between Writing Defines the number of increments between writing data to the restart file. It is only
requested when Restart Type is set to Write or Read and Write.
Select Restart File... This brings up a file browser to select the restart file when the Restart Type is set to
Read or Read and Write.
460 Patran Interface to MD Nastran Preference Guide
Optimize
3.15 Optimize
When preparing for an optimization analysis run, select Optimize as the Action on the Analysis
application form. This allows setup and submission of SOL 200 jobs.
The functionality is similar and in many cases identical to running a normal analysis as described in
Review of the Analysis Form, 260 and other sections in this chapter. Each button and its subordinate
form that appears when the Action is set to Optimize is explained briefly below.
Use the Optimize action for sizing optimization and combined sizing and topology optimization. For pure
topology, topography and topometry optimization, use the Toptomize action explained in Toptomize,
462.
Note: Using Contact Bodies in Optmization Jobs: Linear contact is supported in optimization
jobs (SOL 200). If contact bodies are present in the model and included in the load cases
associated to the the subcases created, then the contact bodies will be written to the deck.
The most common scenario is using linear contact in optimization jobs to glue non-
congruent meshes together. When this feature is used, you must “glue” the bodies together,
which requires that you set up the proper contact tables to define body pairs that are
properly glued. Usage of the contact table is described in Contact Table, 396.
462 Patran Interface to MD Nastran Preference Guide
Toptomize
3.16 Toptomize
When preparing for a pure topology, topometry, or topography optimization analysis run, select
Toptomize as the Action on the Analysis application form. This allows setup and submission of SOL 200
jobs.
The functionality is similar and in many cases identical to running a normal analysis as described in
Review of the Analysis Form, 260 and other sections in this chapter. Each button and its subordinate
form that appears when the Action is set to Toptomize is explained briefly below.
Use the Optimize action for sizing optimization and combined sizing and topology optimization as
explained in Optimize, 460.
A DESOBJ case control entry is written to the deck which calls out the
appropriate DRESP1 and/or DRESP2 entries with the COMP, FREQ, or
EIGN options. Multiple DRESP1 entries are written when the Constraint
Target is Mass Fraction with multiple property sets selected and
subsequently referenced or combined using an average function on the
DRESP2 entry.
Note that when multiple static subcases are selected, a DRSPAN entry
is written to each subcase as necessary to ensure the objective function
properly spans all subcases.
464 Patran Interface to MD Nastran Preference Guide
Toptomize
A DESSUB case control is written to the deck which calls out the
appropriate DCONSTR and DRESP1 entries. This constraint because
part of the objective if both Minimize Compliance and Maximize
Frequency objective functions are specified and is incorporated via a
DEQATN entry referenced on a DRESP2 entry called out by a DESOBJ
case control.
Constraint Target Specify the constraint target. For Topology, only Mass Fraction is
allowed. For Topography, only Weigh or Volume is allowed. For
Topometry, either of the three are allowed. You must specify the mass
fraction, weight or volume target. By default, the mass fraction is 0.4
(40% of the original mass). However, volume and weight have no
defaults. If the Objective Function is set to only Maximize Frequency,
then a Constraint Target is not required (can be set to None) for
Topometry and Topography only.
Optimization Control
Use this form to set various controls used during the optimization run. They are briefly described here
but the user is referred to the MSC Nastran Quick Reference Guide for further information. Leaving a
field blank will trigger usage of the default in most cases. Some parameters must be provided or the
analysis cannot proceed. Setting the Maximum Design Cycles is the most common usage of this form to
limit the analysis to something reasonable. Each optimization type has different settings:
Design Domain
The property sets that define the intended design domain are set on this form as well as manufacturing
constraints. The form works by clicking on a valid property set (row) in the top spread sheet. This action
adds the selected row to the bottom spread sheet, which are the active domains during the optimization
run. To remove domains, click on the rows of interest in the bottom spread sheet and press the Remove
Selected Rows button.
Chapter 3: Running an Analysis 467
Toptomize
From this form you can also define manufacturing constraints to impose on the topology optimization.
Each property set is written to a TOPVAR, TOMVAR, or BEADVAR entry in the input file depending on
the optimization Type set in the Objectives & Constraints form. The values of various parameters on
these entries can be different for each property set. It is recommended that you review the settings for
each property set defined in the design domain before submitting the job. When a property set is added
to the selected design domain properties spreadsheet, some of the values are set in the various columns
from the settings on the Optimization Control form. To change these settings for an individual property
set, simply click on the cell to be changed. A widget will appear above the spreadsheet allowing you to
change the value. Use the Enter key to accept the new value into the spreadsheet. The same can be done
when opening the Manufacturing Constraints form. The values set in the Manufacturing Constraint forms
will correspond only to the property sets that are selected from the Design Domain spreadsheet. If you
do not select any rows in the Design Domain spreadsheet, then any change made on the Manufacturing
Constraints form will be applied to all property sets in this spreadsheet. For this reason, care should be
taken to verify all changes are what is intended.
The tables below indicate the parameters that can be set for each property set of the design domain. Any
parameter set on this form overrides any global setting of that parameter that may be defined under the
Objective & Constraints form or the Optimization Control form. For more information on each
parameter, the user is directed to the MSC Nastran Quick Reference Guide.
Ref. Coordinate System Any direction, plane, or axis specified for the constraints will be in
the Reference Coordinate Frame specified.
Minimum Member Size By default all constraints are off. You may turn any on that are
applicable. Some combinations are not possible in Nastran and the
Symmetric Constraints interface should indicate if an incompatible combination is
selected.
Extrusion Constraints
Note that all of these values can differ for each selected design
Casting Constraints domain from the Design Domain form (bottom spreadsheet). By
selecting a row from the spreadsheet, you can see the settings
change on the Manufacturing Constraints form if there are
differences. If multiple rows are selected, only the settings for the
top row are displayed on the Manufacturing Constraints from. If a
change is made to a value with multiple rows selected, the new
value is associated to all the selected property sets. If no property
sets are selected, it is the same as if all are selected. So care
should be taken when changing values on this form to ensure only
the property sets of interest are being affected.
Ref. Coordinate Frame Any vector specified for the draws direction of the beads will be in
the Reference Coordinate Frame specified.
Extrusion Direction By default the Extrusion Direction is Normal to the surface. If Vector
is specified, a user defined vector can be specified in any
Nodes to Exclude/Include acceptable manner with the select mechanism.
Note that all of these values can differ for each selected design
domain from the Design Domain form (bottom spreadsheet). By
selecting a row from the spreadsheet, you can see the settings
change on the Manufacturing Constraints form if there are
differences. If multiple rows are selected, only the settings for the
top row are displayed on the Manufacturing Constraints from. If a
change is made to a value with multiple rows selected, the new
value is associated to all the selected property sets. If no property
sets are selected, it is the same as if all are selected. So care
should be taken when changing values on this form to ensure only
the property sets of interest are being affected.
Postprocessing
Postprocessing topology optimization results requires that you read element density values (the new
mesh from optimization) using the Nastran results .xdb file (e.g. jobname.xdb) or .des file (e.g.
jobname.des) through the Tools | Design Study | Postprocessing menu and use that application to
view the results rather than through the Patran Results application. See Tools>Design Studies>Post-
Process (p. 546) in the Patran Reference Manual.
470 Patran Interface to MD Nastran Preference Guide
Interactive Analysis
Assumptions
Interactive modal frequency response requires that a normal modes analysis of the structure has been
completed using Nastran, and that a .DBALL/MASTER database exists containing the model data and
the normal modes solution. Currently, the interactive paradigm presumes the Nastran executable, the
modal database, and the Patran executable are all located in the same directory. To maintain optimal
performance, licensing and security should be local also. Given these initial conditions, the following
scenarios exist for performing interactive frequency response.
Scenario 1
If the initial normal modes analysis was modeled in Patran, then that Patran database should be selected
under File/Open when starting Patran. This provides the user with the model from which to exercise the
interactive frequency response wizard, provided the correct flag was set to precondition the Nastran
normal modes database for this purpose. This is done in Patran by going to Analysis/Solution
Type/Interactive Modal Analysis, and activating the check box.
Scenario 2
The normal modes model may have been built and run without using Patran. If the user intends to use the
MSC integrated product to proceed with interactive frequency response, then special care must be taken
when preparing the NASTRAN input file for the normal modes analysis. Specifically, the Nastran normal
modes input file must contain the following statement just before the CEND delimiter:
include `SSSALTERDIR:run0.V2001`
Note that both “ticks” are right handed and that SSSALTERDIR must be capitalized. Nastran then creates
an environment variable called SSSALTERDIR which points to where the sssalters are located when
performing a standard installation.
Chapter 3: Running an Analysis 471
Interactive Analysis
If the user does not have a standard Nastran installation, then he will be required to specify the full
directory path. For example, if the file run0.V2001 is located in the directory /scr2/mike/tmp, then he
must include the following statement just prior to the CEND delimiter:
include `/scr2/mike/tmp/run0.V2001`
This include statement provides the DMAP alter required to precondition the large modal database. This
conditioning enables efficient data manipulation during the interactive frequency response solution
phase.
Under this scenario, the model data will need to be imported by starting Patran and requesting “Read
Input File” from the Analysis Menu. This procedure is described in greater detail in Chapter 5 of this
user’s guide, and constitutes reading a NASTRAN Input File for the model data. Once the model data is
placed in the Patran database, interactive frequency response can proceed.
The Process
Scenario 1 or 2 above can be followed to provide a Patran database with a data model suitable for
performing interactive frequency response. The Analysis menu shown below controls the interactive
analysis process. Submenus for Select NASTRAN .DBALL, Create Loading, Output Requests, Create a
Field, and Define Frequencies are discussed.
Solution Type--Is currently fixed to Frequency Response (Modal Frequency Response) as the only
solution available in interactive analysis format. Subsequent versions of Nastran and Patran may expand
this capability to other solution types.
Loading Menu--The loading menu provides a spreadsheet to guide the user through load and boundary
condition application.
Miscellaneous
The Interactive Modal Frequency response solution process is staged, in the sense that a normal mode
solution is performed first to create what we refer to as the large database (so named for obvious reasons),
and then a fast restart procedure is used to develop the frequency response. The normal modes solution
is where the user specifies any weight to mass conversion quantities (see PARAM, WTMASS) as well
as a specification of the mass matrix formulation desired (see PARAM, COUPMASS). The mass units
and desired mass matrix formulation then, are automatically accounted for in the subsequent
determination of the frequency response quantities calculated.
472 Patran Interface to MD Nastran Preference Guide
Interactive Analysis
Analysis Form
Loading Form
This form allows you to create loading sets. The following is the default form.
The following shows the Loading Form filled out with a few different load conditions.
If Load Type = Acoustic, Load Entity can only reference elements and the default direction for the load
application is relative to the element normal regardless of the Coord Frame selection. The Basic
coordinate system is the default reference (COORD 0), unless, the element was defined in a local
coordinate system, in which case that Coord ID will appear in the Coord Frame column. If the user
changes the Direction from NORMAL to a specific direction vector, then the applied pressure direction
is relative to the Coord Frame referenced.
If Load Type = Force, Load Entity can only reference nodes (grid points), and a direction vector is input
to define application direction relative to the coordinate frame reference. If no coordinate reference frame
is specified, the default becomes the Basic Coordinate system (Coord 0).
If Load Type = Displacement, Velocity, or Acceleration, Load Entity can only be selected from nodes
that will appear in the Load Entities list box. These nodes represent the set of all possible nodes to which
enforced motion can be applied, and is limited to nodes that were constrained during the normal modes
analysis. The Basic coordinate system is the default reference (COORD 0), unless, the node was defined
in a local coordinate frame, in which case that Coord ID will appear in the Coord Frame column.
When Load Type = Displacement, Velocity, or Acceleration, and a specific node has been selected in
Load Entities, the Direction specification will indicate which directions are available X, Y, and / or Z in
Chapter 3: Running an Analysis 475
Interactive Analysis
the reference coordinate frame. When an enforced motion is defined for a selected degree of freedom, it
is eliminated from the available enforced motion set. Only one enforced motion boundary condition per
degree of freedom can be applied to a given node. (Enforced motion cannot be applied to rotational
degrees of freedom for interactive analysis).
476 Patran Interface to MD Nastran Preference Guide
Interactive Analysis
Read Results
4
Accessing Results 492
Supported OUTPUT2 Result and Model Quantities 502
Supported T16/T19 Results Quantities 511
Supported MSC.Access Result Quantities 516
Supported 3dplot Results Quantities 543
492 Patran Interface to MD Nastran Preference Guide
Accessing Results
XDB Formats
The same basic issues exist for MSC.Access databases as for OUTPUT2 files. For example, the
MSC.Access database (xdb file) may be exchanged between computer Systems that have binary
compatibility. That is, an XDB file generated on a SUN Machine may be used on an IBM/AIX, HPUX
or SGI computers.
However, in order to exchange the XDB file on binary incompatible machines, one needs to use the
TRANS and RECEIVE utilities delivered with every installation of MD Nastran.
TRANS converts an XDB file generated by MD Nastran to an “equivalent” character, i.e. ASCII, file
which can be transported to another computer across the network via ftp or rcp. RECEIVE converts the
character file back into the XDB format for postprocessing.
For more information on TRANS and RECEIVE utilities, please consult the “Configuration and
Operations Guide” for V70 of MSC.Nastran.
A MSC.Access XDB database is created by MD Nastran by placing a PARAM,POST,0 in the bulk data
portion of the input file. See Translation Parameters, 265.
In this release of the product, it is assumed that the Geometry, loads and results output all reside in the
same physical XDB file. That is, "split" XDB databases are not supported.
494 Patran Interface to MD Nastran Preference Guide
Accessing Results
MASTER Formats
Using the MASTER format, you can attach to the MD Nastran database directly saving the extra step of
creating alternate form of MD Nastran model and results data, i.e. OP2 and/or XDB. Because the model
and results data in the MD Nastran database tends be sequential in nature, an index provides fast “direct”
access to the data. The indexing is accomplished by two indexing modules in MD Nastran named: ifpindx
and ofpindx.
The DRA/DBALL capability uses the MD Nastran toolkit, i.e. MNT, capability. The MNT interfaces
with the MD Nastran executable in a client-server. This means that in order to use the DRA/DBALL
feature one needs to have access to MD Nastran installation. If you do not have access to a MD Nastran
installation you will need to use the MD Nastran mini server that is delivered with Patran to import
DRA/DBALL files.
To point to a MD Nastran installation, the location of the MD Nastran executable is set in the following
files: p3_trans.ini(NT), .site_setup(UNIX,LINUX). On Windows NT, the “ACommand20xx” must be
set to the MD Nastran executable. On UNIX, on the other hand, “MSP_NASTRAN_CMD20xx” needs
to be set to the MD Nastran executable.
To point to a MD Nastran mini server, the location of the MD Nastran mini server executable must be
set on Windows with the “AcommandNasServer” environment variable. On UNIX, you must set the
environment variable “MSCP_NASTRAN_SERVER” . By default the MD Nastran mini server is located
in $P3_Home/mscnastran_files/servermode/nastran.exe.
Note that you are required to point to a V2004 or later version of MD Nastran. If you specify an
MSC.Nastran executable earlier than V2004 you will be presented with a modal form preventing you
from using this capability. However, you may bypass this restriction by setting the
“DRA_NAST_NOVEDRCHK” environment variable.
The DRA/MASTER functionality only supports static analysis (SOL101). This includes the support of
Superelements, grid point forces and other result types available in the OP2 or XDB translators.
This capability supports importing the model data into Patran database. Moreover, since this capability
reuses the import/bdf functionality all of the model information available in the database shall be
imported including Nodes, Elements, Coordinate systems, material properties, physical properties, loads
and boundary conditions, load cases, parameters and etc...
The “indexing” modules are tied to a system cell. That is, an MD Nastran database is indexed and saved
by MD Nastran by setting system cell “316” to a value “7”. This system cell tells MD Nastran executable
to create index files for IFP and OFP datablocks and move the indexed datablocks to the “MASTER”
file. This means that one can even delete the “DBALL” file after the MD Nastran run completes. For
example, if you would like to get an Indexed MASTER data file for the job some_job.bdf, the following
must be executed:
< ...>/nastran some_job.bdf sys316=7 scr=no sdir=/tmp
This example generates a “some_job.MASTER and some_job.DBALL database files. You can delete the
*.DBALL file because it does not contain any results or model data of importance. However, if you
would like to perform a restart from the run then the DBALL file must be kept for future use but the
“Master” file may be moved to other directories at will.
Chapter 4: Read Results 495
Accessing Results
The MD Nastran toolkit environment is derived from the MD Nastran installation via the use of the “rc”
files which is documented in the MSC.Nastran (p. 1) in the MSC.Nastran 2004 Installation and
Operations Guide. For example, you can set the amount of memory used by the MD Nastran to 20 mega-
words by setting the “memory=20MW” in one of the “rc” files, i.e. nastran.rcf file in the current working
directory on the NT platform. This setting can be double checked using the MD Nastran “whence”
command as follows:
< ...>/nastran some_job.bdf whence=mem
The same basic issues exist for attaching to an Indexed MD Nastran database as attaching an XDB
database. That is, the MD Nastran database (MASTER file) may be exchanged among computer
Systems that have binary compatibility. That is, a MASTER file generated on a SUN Machine can not
be used on an IBM/AIX, HPUX or SGI computers.
However, at this time it is not possible to exchange the MASTER file on binary incompatible machines.
T16/T19 Formats
The T16 file is the MSC.Marc binary results file and the T19 file is the MSC.Marc ASCII results (POST)
file that are created by a SOL 600 analysis, the contents of which can be imported or attached for
postprocessing. When domain decomposition is used, multiple files are produced where # is the domain
number. This file format is recommended for post-processing SOL 600 runs since it has more
information, such as contact info and additional nonlinear analysis information, then the xdbor OP2
formats.
These results file types are used for accessing SOL 600 results.
3dplot Formats
The 3dplot ptf file is the LS-Dyna binary results file that are created by a SOL 700 analysis, the contents
of which can be attached for postprocessing.
This option is available only for Explicit Nonlinear.
496 Patran Interface to MD Nastran Preference Guide
Accessing Results
Translation Parameters
OUTPUT2
This subordinate form appears when the Translation Parameters button is selected and Read Output2 is the
selected Object. When reading results there are three Method options that may be selected: Result
Entities, Model Data or Both. This form affects import of all these objects as noted below
Tolerances
• Division Defines the tolerances used during translation. The division tolerance is
• Numerical used to prevent division by zero errors. The numerical tolerance is used
when comparing real values for equality. When the Object is set to Model
Data, only these tolerances are available.
Chapter 4: Read Results 497
Accessing Results
MSC.Nastran Version Specifies the version of MSC .Nastran that created the OUTPUT2 file to be
read. Solid Element orientation differs between versions less than 67 and
version 67 and above. Elementally oriented Solid element results may be
translated incorrectly if the wrong version is specified.
Additional Results to be Imported
• Rotational Nodal Results Indicates which results categories are to be filtered out during translation.
• Stress/Strain Invariants Rotational Nodal Results, Stress and Strain Invariants, and Stress and Strain
Principal Direction Results can be skipped during translation. Items
• Principal Directions selected will be translated. Items not selected will be skipped. By default,
Rotational Nodal Results, Stress and Strain Invariants, and Stress and Strain
Tensor Principal Directions are ignored during translation.
• P-element P-order Field Creates a field that describes the polynomial orders in all p-elements in the
model at the end of an adaptive cycle.
Element Results Positions If an element has results at both the centroid and at the nodes, this filter will
indicate which results are to be included in the translation.
XDB
This subordinate form appears when the Translation Parameters button is selected and Result Entities is
the selected Object.
Tolerances
• Division Defines the tolerances used during translation. The division tolerance is used
• Numerical to prevent division by zero errors. The numerical tolerance is used when
comparing real values for equality. When the Object is set to Model Data,
only these tolerances are available.
MSC.Nastran Version Specifies the version of MSC .Nastran that created the OUTPUT2 file to be
read. Solid Element orientation differs between versions less than 67 and
version 67 and above. Elementally oriented Solid element results may be
translated incorrectly if the wrong version is specified.
Chapter 4: Read Results 499
Accessing Results
MASTER
This subordinate form appears when the Translation Parameters... button is selected and MASTER is the
selected Object.
500 Patran Interface to MD Nastran Preference Guide
Accessing Results
Tolerances
• Division Defines the tolerances used during translation. The division tolerance
• Numerical is used to prevent division by zero errors. The numerical tolerance is
used when comparing real values for equality. When the Object is set
to Model Data, only these tolerances are available.
MSC.Nastran Version Specifies the version of MSC .Nastran that created the OUTPUT2 file
to be read. Solid Element orientation differs between versions less
than 67 and version 67 and above. Elementally oriented Solid element
results may be translated incorrectly if the wrong version is specified.
Additional Results to be Imported
• Rotational Nodal Results Indicates which results categories are to be filtered out during
• Stress/Strain Invariants translation. Rotational Nodal Results, Stress and Strain Invariants,
and Stress and Strain Principal Direction Results can be skipped
• Principal Directions during translation. Items selected will be translated. Items not
selected will be skipped. By default, Rotational Nodal Results, Stress
and Strain Invariants, and Stress and Strain Tensor Principal
Directions are ignored during translation.
• P-element P-order Field Creates a field that describes the polynomial orders in all p-elements
in the model at the end of an adaptive cycle.
Element Results Positions If an element has results at both the centroid and at the nodes, this
filter will indicate which results are to be included in the translation.
Chapter 4: Read Results 501
Accessing Results
T16/T19
This subordinate form appears when the Translation Parameters... button is selected and T16/T19 is the
selected Object.
Results
Global Variables
In addition to standard results quantities, a number of Global Variables can be created. This table outlines
Global Variables that may be created. Global Variables are results quantities where one value is
representative of the entire model.
Coordinate Systems
In some cases, the elemental stresses and strains are transformed from one coordinate frame to another
when imported into the Patran database. The following describes the coordinate systems for these
element results after they are imported into the Patran database. The coordinate system names referred
to are described in the Patran or the MD Nastran documentation.
CTRIA3 Table 4-1 Results are in the MD Nastran system which coincides with the Patran IJK
system. At the user’s request during postprocessing, these results can be transformed by
Patran to alternate coordinate systems. If the user selects a component of a stress or strain
tensor to be displayed, by default, the Results application transforms the tensor to a
projected global system (Projected Global System).
CQUAD4 Table 4-2 Results are in the MD Nastran “bisector” coordinate system but may be
transformed by Patran to alternate coordinate systems (e.g., global) during postprocessing.
If the user selects a component of a stress or strain tensor to be displayed, by default, the
Results application transforms the tensor to a projected global system (Projected Global
System). Import of results when this element is used in a hyperelastic analysis is not
currently supported.
CHEXA, Table 4-3 The user can request that MD Nastran compute element results in either a local
CPENTA, element or alternate coordinate system via the PSOLID entry. If the element results are in
CTETRA the local element system, these are converted to the Patran IJK system on import. If the
results are in a system other than local element, they are imported in this system. These
results may be transformed to alternate systems during postprocessing.
CQUAD8, Table 4-4 The elemental coordinate system, used by MD Nastran for results, is described
CTRI6 in the MD Nastran documentation. These results are imported into the Patran database “as-
is”. These results can be postprocessed in Patran using the “As Is” options, but they cannot
be transformed to alternate coordinate systems.
XY Plots
For results from MD Nastran design optimization solution 200 runs, three XY Plots are generated, but
not posted, when the Read OUTPUT2 option is selected:
1. Objective Function vs. Design Cycle.
1. Maximum Constraint Value vs. Design Cycle.
1. Design Variable vs. Design Cycle.
510 Patran Interface to MD Nastran Preference Guide
Supported OUTPUT2 Result and Model Quantities
These plots can be viewed under the XY Plot option in (p. 1) in the MSC.Patran User’s Guide. When they
are initially posted, you will have to expand their windows to view them properly.
Model Data
The following table outlines all the data that will be created in the Patran database when reading model
data from an MD Nastran OUTPUT2 file and the location in the OUTPUT2 file from where it is derived.
This is the only data extracted from the OUTPUT2 file. This data should be sufficient for evaluating
results values.
Nodal Coordinates
Transformation Matrix
Origin
Nodal Connectivity
Chapter 4: Read Results 511
Supported T16/T19 Results Quantities
In addition to these standard results quantities, several Global Variable results can be created. Global
Variables are results quantities where one value is representative of the entire model. The following table
defines the Global Variables which may be created.
Nodal Results
Elemental Results
Primary Label Secondary Label Type Objects
Bar Forces Translational VECTOR FBEMR
Rotational VECTOR FBEMR
Warping Torque SCALAR FBEMR
Translational VECTOR FBEMRI
Rotational VECTOR FBEMRI
Warping Torque SCALAR FBEMRI
Translational VECTOR FBEMMP
Rotational VECTOR FBEMMP
Warping Torque SCALAR FBEMMP
Translational VECTOR FTUBR
Rotational VECTOR FTUBR
Translational VECTOR FTUBRI
Rotational VECTOR FTUBRI
Translational VECTOR FTUBMP
Rotational VECTOR FTUBMP
Translational VECTOR FCONR
Rotational VECTOR FCONR
Translational VECTOR FCONRI
Rotational VECTOR FCONRI
Translational VECTOR FCONMP
Rotational VECTOR FCONMP
Translational VECTORs FELSR
FELSRI
FELSMP
FDMPR
FDMPRI
FDMPMP
Rotational VECTOR FBARR
Translational VECTOR FBARR
Rotational VECTOR FBARRI
Translational VECTOR FBARRI
524 Patran Interface to MD Nastran Preference Guide
Supported MSC.Access Result Quantities
ENG_TENSOR ERODRI
ENG_TENSOR ERODMP
ENG_TENSOR EBEMR
ENG_TENSOR EBEMRI
ENG_TENSOR EBEMMP
NONE ENG_TENSOR ETUBR
ENG_TENSOR ETUBRI
ENG_TENSOR ETUBMP
NONE ENG_TENSOR ECONR
ENG_TENSOR ECONRI
ENG_TENSOR ECONMP
NONE ENG_TENSOR EELSR
ENG_TENSOR EELSRI
ENG_TENSOR EELSMP
NONE ENG_TENSOR EQD4R
ENG_TENSOR EQD4RI
ENG_TENSOR EQD4MP
NONE ENG_TENSOR EBARRI
ENG_TENSOR EBARR
ENG_TENSOR EBARMP
NONE ENG_TENSOR ETETR
ENG_TENSOR ETETRI
ENG_TENSOR ETETMP
NONE ENG_TENSOR EQD8R
ENG_TENSOR EQD8RI
ENG_TENSOR EQD8MP
530 Patran Interface to MD Nastran Preference Guide
Supported MSC.Access Result Quantities
ENG_TENSOR EQDRRI
ENG_TENSOR EQDRMP
NONE ENG_TENSOR GQD4R
NONE ENG_TENSOR GQD8R
NONE ENG_TENSOR GTR3R
NONE ENG_TENSOR GTR6R
NONE ENG_TENSOR EBRXR
NONE ENG_TENSOR EQD4XR
ENG_TENSOR EQD4XRI
ENG_TENSOR EQD4XMP
NONE ENG_TENSOR EBRXR
Shear Panel Stresses Maximum Shear SCALAR SSHRR
Average Shear SCALAR SSHRR
Maximum Shear SCALAR SSHRRI
Average Shear SCALAR SSHRRI
Maximum Shear SCALAR SSHRMP
Average Shear SCALAR SSHRMP
Maximum Shear SCALAR SSHRR
Average Shear SCALAR SSHRR
Maximum Shear SCALAR SSHRRI
Average Shear SCALAR SSHRRI
Maximum Shear SCALAR SSHRMP
Average Shear SCALAR SSHRMP
Shear Panel Strains Maximum Shear SCALAR ESHRR
Average Shear SCALAR ESHRR
Maximum Shear SCALAR ESHRRI
Average Shear SCALAR ESHRRI
Maximum Shear SCALAR ESHRMP
Average Shear SCALAR ESHRMP
Chapter 4: Read Results 531
Supported MSC.Access Result Quantities
HPENR,
HQD4R,
HQDXR.
HQUDR,
HTETR,
HTR3R,
HTR6R,
HTRXR
Logarithmic Strains TENSOR HHEXR,
HPENR,
HQD4R,
HQDXR.
HQUDR,
HTETR,
HTR3R,
HTR6R,
HTRXR
542 Patran Interface to MD Nastran Preference Guide
Supported MSC.Access Result Quantities
HPENR,
HQD4R,
HQDXR.
HQUDR,
HTETR,
HTR3R,
HTR6R,
HTRXR
Volumetric Strains TENSOR HHEXR,
HPENR,
HQD4R,
HQDXR.
HQUDR,
HTETR,
HTR3R,
HTR6R,
HTRXR
Topology Optimization Element Density SCALAR DVHIST
Chapter 4: Read Results 543
Supported 3dplot Results Quantities
Read Input File as the selected Action on the Analysis form allows much of the model data from a MD
Nastran input file to be translated into the Patran database. A subordinate File Selection form allows the
user to specify the MD Nastran input file to translate. This form is described on the following pages.
Chapter 5: Read Input File 547
Review of Read Input File Form
The following table shows the relation between the entity types listed above and the actual MD Nastran
entry types effected. If an entity type is filtered out, it is treated as if those entries did not exist in the
original input file.
It should be noted that since the GRID entry is controlled with the Nodes filter, the grid.ps load set with
the permanent single point constraint data will also be controlled by the Nodes filter.
550 Patran Interface to MD Nastran Preference Guide
Review of Read Input File Form
ID offset value to
be used during
import. The new ID
value will be the ID
found in the
NASTRAN input
file plus this offset
value.
All references made in the input file will also be offset. If a node references a particular CID as its
analysis frame, then the reference will be offset as well. If the coordinate frame is defined in the same
input file, the proper references should be maintained. The preference will be properly maintained. If the
coordinate frame existed in the file prior to the import, then it needs to be the offset CID. If a coordinate
frame with that CID is not found in the database, an error message will be issued.
Chapter 5: Read Input File 551
Review of Read Input File Form
To determine which offset effects a particular MD Nastran entry type, refer to the table in the previous
section.
For Patran entities identified by integer IDs (nodes, elements, coordinate frames, and MPCs), the offset
value is simply added to the MD Nastran ID to generate the Patran ID.
For Patran entities identified by text names (materials, element properties, load sets, and load cases), the
offset value is first added to the MSC Nastran ID. The new integer value is then used to generate the
Patran name per the naming conventions described in later sections.
When the OK button is selected, the newly imported data will be committed to the Patran database, and
can not be undone. If there is any question as to whether or not this import was desired, review the
graphics data prior to selecting OK on this form. If the import was not correct, select the undo button on
the main menu bar before selecting OK on this form.
Reject Cards...
OK
Chapter 5: Read Input File 553
Review of Read Input File Form
OK
Only entry types not supported by Patran are sent to the reject entry blocks. (This includes comments.)
Cards which are otherwise recognized, but can not be imported due to syntax or invalid data errors are
not sent to the reject blocks. The rejected entries will have no characters in front of the command name.
Commands preceded by the character $> are used by the MSC/AMS product to allow processing of
comment lines.
Note: As long as you don not delete the reject casrd file, Patran will re-insert the rejected entries
back into the input file if you use the same jobname.
554 Patran Interface to MD Nastran Preference Guide
Data Translated from the NASTRAN Input File
Partial Decks
This Patran function can read incomplete MD Nastran files (except where explicitly noted). However, if
the BEGIN BULK command is missing, the program can get confused when trying to determine if a
particular entry belongs to the case control or bulk data. If you experience any difficulties importing a
file that does not have a BEGIN BULK command, add one to the top of the file. This should avoid any
such confusion.
Coordinate Systems
The following coordinate system definitions can be read into Patran.
Command Comments
CORD1C References to the GRIDs on these entries are lost. The locations of the referenced
GRIDs are extracted, and those locations are used to create the Patran definition.
CORD1R
CORD1S
CORD2C References to RIDs are lost. The specified locations are converted to global
cartesian for use in the Patran definitions.
CORD2R
The original B and C points are not retained. Their values are recomputed when a
CORD2S
new NASTRAN input file is created. The definition will be equivalent, but not
identical.
Referential Integrity
Coordinate systems and GRIDs which are referenced as part of a CORD definition must be in the same
input file. If these are not found in the input file, the definition will be rejected.
Chapter 5: Read Input File 555
Data Translated from the NASTRAN Input File
References to coordinate frames other than for new coordinate frame definitions can be resolved with
coordinate frames previously found in the Patran database.
Chaining
Due to limitations in the Patran definitions of coordinate systems, chained definitions (definitions based
on other coordinate systems or grids) are modified during import. The resulting definitions are equivalent
in global space, but are based on global cartesian coordinates rather than GRID references or coordinate
locations in other systems. This change is carried through when a new NASTRAN input file is created.
All coordinate systems will be created using CORD2 type definitions, and they will all reference global
cartesian coordinates. These definitions will be different from, but equivalent to, the original definitions.
SPOINTs
SPOINTs are treated as GRIDs at the global origin. They are assumed to have their GRID CD and CP
fields set to the basic system, and their PS field is set to permanently constrain degrees-of-freedom 2
through 6.
Referential Integrity
Coordinate frames referenced in the CP field must exist in the same input file. Coordinate frames
referenced on the CD field can exist in either the same input file, or the Patran database prior to the
import.
PBARL pbarl.<pid>
556 Patran Interface to MD Nastran Preference Guide
Data Translated from the NASTRAN Input File
CONM1 conm1
CONM2 conm2
CONROD conrod
CPENTA PSOLID psolid.<pid>
CQUAD4 PSHELL pshell.<pid> (See PSHELL comments below.)
PCOMP pcomp.<pid> A new material named pcomp.<pid> will be created and
referenced.
Higher order elements (CQUAD8, CTRIA6, CTRIAX6, CHEXA, CPENTA, CTETRA) will generate
linear elements in Patran if none of the mid-edge nodes are specified.
Chapter 5: Read Input File 559
Data Translated from the NASTRAN Input File
PSHELL Properties
PSHELL properties can be imported as any one of five Patran property types. The MID1, MID2, MID3,
12I/T3, and TS/T property fields are used to determine which one to choose. If MID2 is -1 and MID3 is
0, then a Plane Strain property set is used. If MID2 and MID3 are both 0, then a Membrane property set
is chosen. If MID1 and MID3 are 0, then a Bending property set is used. If MID1, MID2, and MID3 are
all the same, and the MD Nastran defaults are used for 12I/T3 and TS/T, then a Homogeneous property
set is used. If all else fails, then an Equivalent Section property set is chosen.
Fields
If a field is required to store varying data, the field will have the same name as the property set, with the
name of the specific property word appended to it. For example, if property set “pshell.101” has a varying
thickness, the field will be named “pshell.101.Thickness”.
Referential Integrity
Nodes and coordinate frames referenced on elements or element properties must exist, but they do not
need to be in the input file. They could also have been defined in the Patran database prior to the import.
If a material is referenced, but can not be found, a new material with no properties will be created. A
message will be issued indicating the creation of this material.
If an element property set is referenced, but can not be found, a new property set with no properties will
be created. A message will be issued indicating the creation of this property set.
PB .pb<PB>
560 Patran Interface to MD Nastran Preference Guide
Data Translated from the NASTRAN Input File
SB .sb<SB>
PA .pa<PA>
PB .pb<PB>
CDAMP1, CDAMP2, C1 .ca<C1>
CQUADR, CTRIA3,
CTRIA6, CTRIAR
Materials
The following MD Nastran material definitions can be read into Patran.
MPCs
The following MD Nastran MPC and rigid element definitions can be read into Patran.
Since Patran uses a slightly different basis MPC equation, the equation
coefficients (Ai) will probably be scaled by a constant multiplier during
import. The resulting equation will be equivalent, but not necessarily
identical to the original definition in the NASTRAN input file.
RBAR RBAR
RBE1 RBE1
RBE2 RBE2
Fixed
RBE3 RBE3
RROD RROD
RSPLINE RSPLINE
RSSCON RSSCON
RTRPLT RTRPLT
MPCs in Patran are treated as elements and are not associated to load cases. As a result, all SUBCASE
related data is lost. The MPCs are simply imported into the model and are no longer associated to a
specific load case.
MPCs can reference SPOINTs instead of GRIDs. If this is detected, the corresponding component field
will be set to 1 (UX) to be consistent with the import of SPOINTs.
The MPCADD command is not read since the MPCs are simply imported and no associated to a load
case. The SID references on the MPC entry are also lost for the same reason. New MPC IDs are assigned
to these elements during import.
562 Patran Interface to MD Nastran Preference Guide
Data Translated from the NASTRAN Input File
Load Sets
The following MD Nastran Loads and Boundary Condition definitions can be read into Patran.
Fields
If a field is required to store varying data, the field will have the same name as the load set, with the name
of the specific data word appended to it. For example, if load set “force.101” has a varying force
magnitude, the field will be named “force.101.Force”.
Load cases are created in Patran from the SUBCASE definitions in the NASTRAN input file. Load sets
not referenced by a SUBCASE definition are created as load sets in Patran, but are not associated to a
load case. Load sets defined above the first SUBCASE command, plus any permanent single point
constraint sets from the GRID entries, are associated to all load cases created during this import. If there
is no case control data, then load sets will be created, but they will not be assigned to any load cases.
The SPCADD and LOAD entries are used in creating load cases in Patran, but the SID of these entries
is lost. The SIDs on the individual SPCx, FORCE, MOMENT, GRAV, PLOADx, RFORCE, and TEMPx
entries are used in creating the names of the load sets.
The name for the created load cases is derived from the subtitle of the SUBCASE. This is done for
consistency with the forward PAT3NAS translation.
A job is created during the import. The name of the created job is the basename of the file being read.
MD Nastran allows load sets to be referenced in multiple places with different scale factors. This is not
possible in Patran. Therefore, in some cases, multiple copies of the same load set need to be created with
the only difference being the scale factor. The name of these load sets are modified to include the subcase
ID to create unique names.
564 Patran Interface to MD Nastran Preference Guide
Data Translated from the NASTRAN Input File
TABLES
The following table types are supported during import of a NASTRAN input file. Note that some forms
of the table commands are converted to an equivalent version supported by Patran.
Delete
6
Review of Delete Form 568
Deleting an MD Nastran Job 569
568 Patran Interface to MD Nastran Preference Guide
Review of Delete Form
The Delete option under Action allows the user to delete jobs that have been created for the MD Nastran
preference.
Chapter 6: Delete 569
Deleting an MD Nastran Job
Files
7
Files 572
572 Patran Interface to MD Nastran Preference Guide
Files
7.1 Files
The Patran MD Nastran interface uses or creates several files.The following table outlines each file and
its uses. In the file name definition, jobname will be replaced with the jobname assigned by the user.
*.db This is the Patran database. During an analyze pass, model data is read from this database
and, during a Read Results pass, model and/or results data is written into it. This file
typically resides in the current directory.
jobname.jbr These are small files used to pass certain information between Patran and the independent
translation programs during translation. There should never be a need to directly alter these
files. These files typically reside in the current directory.
jobname.bdf This is the NASTRAN input file created by the interface. This file typically resides in the
current directory.
msc_v#_sol#.alt These are a series of MD Nastran alters that are read during forward translation. These alters
instruct MD Nastran to write information to the OUTPUT2 file that the results translation
will be looking for. The forward translator searches the Patran file path for these files, but
they typically reside in the <installation_directory>/alters directory. If these files do not
meet specific needs, edit them accordingly. However, the naming conversion of msc_v#
<version #>_sol#<solution #>.alt must be preserved. Either place the edited file back into
the <installation_directory>/alters directory or in any directory on the Patran file path, which
takes precedence over the <installation_directory>/alters directory. If these files are not
used, remove them from the Patran file path, rename them, or delete them altogether.
jobname.op2 This is the MD Nastran OUTPUT2 file, which is read by the Read Results pass. This file
typically resides in the current directory and contains both model and results data. It is
created by placing a PARAM,POST,-1 in the input file.
jobname.xdb This is the MD Nastran XDB file or MSC.Access database, which is attached by the Read
Results pass. This file typically resides in the current directory and contains results data. It
is created by placing a PARAM, POST,0 in the input file.
jobname.marc.t16 SOL 600 file recommended for use in postprocessing SOL 600 analyses.
jobname.flat This file may be generated during a Read Results pass. If the results translation cannot write
data directly into the specified Patran database it will create this jobname flat file. This file
typically resides in the current directory.
jobname.marc.xxx File generated by a SOL 600 analysis. See the “MD Nastran Implicit Nonlinear (SOL 600)
User’s Guide” for a complete list.
Chapter 7: Files 573
Files
Errors/Warnings
8
Errors/Warnings 576
576 Patran Interface to MD Nastran Preference Guide
Errors/Warnings
8.1 Errors/Warnings
There are many error or warning messages that may be generated by the Patran MD.Nastran Interface.
The following table outlines some of these.
Message Description
Unable to open a new message file " ". Translation If the translation tries to open a message file and cannot, it
messages will be written to standard output. will write messages to Standard Output. On most systems,
the translator automatically writes messages to standard
output and never tries to create a separate message file.
Unable to open the specified OUTPUT2 file " ". The OUTPUT2 file was not found. Check the OUTPUT2
file specification in the translation control file.
The specified OUTPUT2 file " " is not in standard The OUTPUT2 file is not in standard binary format. Check
binary format and cannot be translated. the OUTPUT2 file specification in the translation control
file.
Group " " does not exist in the database. Model data The name of a nonexistent group was specified in the
will not be translated. translator control file. No model data will be translated from
the OUTPUT2 file.
Needed file specification missing! The full name of The translation control file must be specified as the first on-
the job file must be specified as the first command- line argument to the translator.
line argument to this program.
Unable to open the specified database " ". Writing If the translator cannot communicate directly to the
the OUTPUT2 information to the PCL command file specified database. It will write the results and/or model data
" ". to a PCL session file.
Unable to open either the specified database " ", or a The naspat3 translator is unable to open any output file.
PCL command file, " ". Check file specification and directory protection.
Unable to open the NASTRAN input file " ". The translator was unable to open a file to where the input
file information will be written.
Unable to open the specified database, " ". The forward Patran MD.Nastran translator was unable to
open the specified Patran database.
Alter file of the name " " could not be found. No The OUTPUT2 DMAP alter file, for this type of analysis,
OUPUT2 alter will be written to the NASTRAN input could not be found. Correct the search path to include the
file. necessary directory if you want the alter files to be written to
the input file.
No property regions are defined in the database. No Elements referenced by an element property region in the
elements or element properties can be translated. Patran database will not get translated by the forward Patran
MD.Nastran translator. If no element regions are defined, no
elements will be translated.
Chapter A: Preference Configuration and Implementation
Patran Interface to MD Nastran Preference Guide
Patran p3patran.plb
Analysis
mscnastran.plb Analyze
MscNastranExecute
Patran
Database
Alter Library
jobname.bdf MD Nastran
Figure A-2 shows the process of reading information from an MD Nastran OUTPUT2 file. When the
Apply button is selected on the Read Output2 form, a <jobname>.jbr file is created and the results
translation is started. The results interface process reads the data from the MD Nastran OUTPUT2 file
580 Patran Interface to MD Nastran Preference Guide
Patran MD Nastran Preference Components
and stores the results in the Patran database. Status messages from the interface are recorded in the
Patran session file.
p3patran.plb
Patran
Analysis mscnastran.plb
Read
Output2
jobname.jbr
Patran
database
MD Nastran jobname.OP2
Figure A-3 shows the process of translating information from a NASTRAN input file into a Patran
database. The behavior of the main Analysis/Read Input File form and the subordinate file select form is
Chapter A: Preference Configuration and Implementation 581
Patran MD Nastran Preference Components
dictated by the mscnastran.plb PCL library. The Apply button on the main form activates the input
file reader program, which reads the specified NASTRAN input file.
Patran
p3patran.plb
Analysis
Read
Input File mscnastran.plb
NASTRAN
Input File
input_file_name.error.*
Index
Patran Interface to MD Nastran Preference Guide
T
t16 file, 511, 543
588 Patran Interface to MD Nastran Preference Guide
V
VECTOR, 419
VU mesh, 20
W
warnings, 576
WTMASS, 283