2006 MD Nastran Release Guide
2006 MD Nastran Release Guide
2006 MD Nastran Release Guide
Release Guide
Corporate
MSC.Software Corporation
2 MacArthur Place
Santa Ana, CA 92707 USA
Telephone: (800) 345-2078
Fax: (714) 784-4056
Europe
MSC.Software GmbH
Am Moosfeld 13
81829 Munich, Germany
Telephone: (49) (89) 43 19 87 0
Fax: (49) (89) 43 61 71 6
Asia Pacific
MSC.Software Japan Ltd.
Shinjuku First West 8F
23-7 Nishi Shinjuku
1-Chome, Shinjyku-Ku
Tokyo 160-0023, JAPAN
Telephone: (03)-6911-1200
Fax: (03)-6911-1201
Worldwide Web
www.mscsoftware.com
Disclaimer
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 2006 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.
This software may contain certain third-party software that is protected by copyright and licensed from MSC.Software suppliers.
MSC, MSC., MD, MSC.Dytran, MSC.Marc, MSC.Nastran, MD Nastran, MSC.Patran, the MSC.Software corporate logo, and
Simulating Reality are trademarks or registered trademarks of the MSC.Software Corporation in the United States and/or other
countries.
NASTRAN is a registered trademark of NASA. PAMCRASH 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. ABAQUS is a
registered trademark of ABAQUS Inc. All other brand names, product names or trademarks belong to their respective owners.
MDNA:V2006:Z:Z:Z:DC-REL-PDF
Contents
MD Nastran 2006 Release Guide
MD Nastran 2006
Release Guide
List of Nastran Books xii Table of Contents
2 Nonlinear Analysis
Nonlinear Transient Analysis in SOL 400 10
Introduction 10
Benefits 10
Limitations for the Current Release 11
A New Numerical Integration Method – HHT 11
Nonlinear Iteration Algorithms 12
Case Control Structure – SUBCASE, STEP, ANALYSIS, and NLIC 14
Vector Operations and Convergence Criteria 16
Nonlinear Iteration Summary Table for Nonlinear Transient Analysis in SOL 400
17
Output Data Grouping: NLPACK 18
Restarts 19
Initial Conditions 21
Transient Temperature Loads 23
Boundary Condition (SPC and MPC) Changes 24
Direct Matrix Input Changes 24
Outputs 25
iv MD Nastran 2006 Release Guide
Error Handling 25
User Interfaces 26
Examples 27
3 Numerical Enhancements
New Iterative Solver Option 74
Introduction 74
Benefits 74
Method and Theory 74
Inputs 75
Outputs 75
Guidelines and Limitations 76
Demonstration Example 76
Example Input Data 76
Example Output 81
MDACMS Enhancements 83
Background 83
Summary 83
New FMS Command: MEMLIST 83
New Module: RESMOD 84
Option P1 = ‘ATBC’ 86
Option P1 = ‘MPART’ 86
Option P1 = ‘LININD’ 87
Option P1 = ‘LDSWEEP’ 88
Option P1 = ‘USWEEP’ 89
4 Elements
Three-Node Beam Element 96
Introduction 96
Benefits 96
Input 96
Guidelines and Limitations 97
Formulation 99
Output 101
Example 103
6 Aeroelasticity
Monitor Points 188
Introduction 188
Benefits 189
Input 189
Output 190
Examples 193
Guidelines and Limitations 193
Spline6/7 195
Introduction 195
Benefits 196
Input 196
7 Optimization
Topology Optimization with Manufacturability Constraints 204
viii MD Nastran 2006 Release Guide
Introduction 204
Benefits 204
Input 205
Guidelines and Limitations 207
Supporting Trust Region in SOL 200 for Adaptive Move Limits 223
Introduction 223
Benefits 223
Theory 223
Input 225
Outputs 226
Guidelines and Limitations 227
Examples 227
8 Miscellaneous Enhancements
Export of Static Loads 234
Introduction 234
Benefits 234
Input 234
Output 235
Examples (TPL: exptld/imptld, sysmod/fbody, sfsw/ffsw) 235
Guidelines and Limitations 236
Preface
Reference Books
❏ Quick Reference Guide
❏ DMAP Programmer’s Guide
❏ Reference Manual
User’s Guides
❏ Getting Started
❏ Linear Static Analysis
❏ Basic Dynamic Analysis
❏ Advanced Dynamic Analysis
❏ Design Sensitivity and Optimization
❏ Thermal Analysis
❏ Numerical Methods
❏ Aeroelastic Analysis
❏ Superelement
❏ User Modifiable
❏ Toolkit
❏ Implicit Nonlinear (SOL 600)
❏ Explicit Nonlinear (SOL 700)
Preface xiii
Technical Support
For help with installing or using an MSC.Software product, contact your local
technical support services. Our technical support provides the following
services:
• Resolution of installation problems
• Advice on specific analysis capabilities
• Advice on modeling techniques
• Resolution of specific analysis problems (e.g., fatal messages)
• Verification of code error.
If you have concerns about an analysis, we suggest that you contact us at an
early stage.
You can reach technical support services on the web, by telephone, or e-mail:
Web Go to the MSC.Software website at www.mscsoftware.com, and click on
Support. Here, you can find a wide variety of support resources including
application examples, technical application notes, available training courses,
and documentation updates at the MSC.Software Training, Technical Support,
and Documentation web page.
xiv MD Nastran 2006 Release Guide
Email Send a detailed description of the problem to the email address below that
corresponds to the product you are using. You should receive an
acknowledgement that your message was received, followed by an email from
one of our Technical Support Engineers.
Training
The MSC Institute of Technology is the world's largest global supplier of
CAD/CAM/CAE/PDM training products and services for the product
design, analysis and manufacturing market. We offer over 100 courses
through a global network of education centers. The Institute is uniquely
positioned to optimize your investment in design and simulation software
tools.
Our industry experienced expert staff is available to customize our course
offerings to meet your unique training requirements. For the most effective
training, The Institute also offers many of our courses at our customer's
facilities.
The MSC Institute of Technology is located at:
2 MacArthur Place
Santa Ana, CA 92707
Phone: (800) 732-7211
Fax: (714) 784-4028
The Institute maintains state-of-the-art classroom facilities and individual
computer graphics laboratories at training centers throughout the world. All
of our courses emphasize hands-on computer laboratory work to facility skills
development.
We specialize in customized training based on our evaluation of your design
and simulation processes, which yields courses that are geared to your
business.
In addition to traditional instructor-led classes, we also offer video and DVD
courses, interactive multimedia training, web-based training, and a specialized
instructor's program.
Internet Resources
MSC.Software (www.mscsoftware.com)
MSC.Software corporate site with information on the latest events, products
and services for the CAD/CAE/CAM marketplace.
Engineering-e.com (www.engineering-e.com)
Engineering-e.com is the first virtual marketplace where clients can find
engineering expertise, and engineers can find the goods and services they need
to do their job
CATIASOURCE (plm.mscsoftware.com)
Your SOURCE for Total Product Lifecycle Management Solutions.
MD Nastran Release Guide
Ch. 1: Overview of MD Nastran 2006 Ch. 1: Overview of MD Nastran 2006Key Highlights for MD
J
Overview
Nastran 2006
2 MD Nastran 2006 Release Guide
Overview
The MD Nastran 2006 release brings major new features for enterprise computing in the areas of high
performance computing, nonlinear analysis, assembly modeling, optimization, rotor dynamics and
aeroelasticity.
Nonlinear Analysis
• Nonlinear Transient Analysis in SOL 400 - Nonlinear transient (SOL 400) extends the nonlinear
analysis capabilities of SOL 129. It features a new transient analysis solution (HHT method),
adaptive time step control, SPC and MPC changes between Subcase/Step, improved nonlinear
iteration performance, the new nonlinear squeeze film damper element for rotor dynamics, and
expanded nonlinear iteration controls.
• MD Nastran Implicit Nonlinear - SOL 600 – The performance and capabilities of MD Nastran’s
implicit nonlinear solution have been greatly improved over MSC.Nastran. These include more
robust data exchange, faster contact (three to six-fold CPU time improvements), auto SPC and
MSET, inertia relief, an improved out-of-core solver, expanded results support, automated brake
squeal computations, improved fixed time stepping, and improved user subroutine support.
• MD Nastran Explicit Nonlinear - SOL 700 – With this new release capability you can perform
crash and drop test analysis using existing Nastran models.
Numerical Enhancements
• Iterative Solvers – There is now a new iterative solution for static analysis. Also, significant
performance improvements along with reduction in I/O requirements have been achieved in the
ACMS solution.
Elements
• Arbitrary Beam Cross-Section – The interface for describing arbitrary cross-section shapes for
bar and beam elements has been enhanced to include a cross-section outline display, stress data
recovery and design optimization. The profiles can now be optimized using SOL 200. Stress
recovery includes both torsion and shear terms.
• Line Interface Element – You can now connect dissimilar meshes along edges. A set of MPC
(multipoint constraint) equations are internally generated to enforce the compatibility of
displacements and rotations across the interface. This feature is particularly useful for global-
local modeling, where a local fine mesh is required in a particular region due to high stress
gradients.
• CWSEAM Connector Elements
CWSEAM Element - A seam element to connect surface patches is now available. This element
extends the existing CWELD and CFAST connector elements. The seam weld is defined by
selecting two surface patches by their property IDs and specifying the width and the thickness of
CHAPTER 1 3
Overview of MD Nastran 2006
the seam. Extensive error checking and user diagnostics include detection of missing
connections for CWSEAMs, defined across corners and cutouts.
RBE2GS Element – This element generates internal RBE2 element connecting a grid point pair
closest to a user-defined search grid point. You can exclude optional grids within search radius.
• Three-Node Beam Element – A general spatial three-node beam element has been developed for
linear static, modal, dynamic, and buckling analyses. The element is implemented as a curved
one-dimensional Timoshenko beam element with initial curvatures and pre-twist. The cross-
sectional warping effect is also included.
Aeroelasticity
• Monitor Points - We have added support for monitor points, including a MONPNT2 that selects
a specific element response for output, a MONPNT3 that outputs an integrated load on a
structural subcomponent, and a MONDSP1 that provides averaged displacement components.
All of these are available in SOLs 101 and 144, while SOL 146 supports MONPNT1 and
MONDSP1.
• Export and Import of Loads -Two methods have been provided to extract loads from an analysis
for import into another analysis. The EXPORTLD Case Control command supports the creation
of a datablock that contains the external load of a user specified set of grids. Alternatively, one
can export a “free-body” load based on the grid point forces of a user specified subcomponent.
Both of these loads can be imported into a subsequent analysis via dblocate commands, and
included in the external load specification.
4 MD Nastran 2006 Release Guide
Optimization
• Topology Optimization with Manufacturability Constraints – This release supports
manufacturing constraints including casting (draw direction), extruding, and symmetry to ensure
that the optimal size and shape determined for the given set of loads and boundary conditions
conforms to manufacturing.
Input Changes
Section New Modified
nastran NASTRAN
Statement
Executive MODEL_CHECK SOL 600,ID
Control SOL 700,ID
CHAPTER 1 5
Overview of MD Nastran 2006
Input Changes
Section New Modified
Case AERCONFIG PFGRID ADAMSMNF
Control EXPORTLD PFMODE BCONTACT
FBODYLD PFPANEL EXTSEOUT
MONITOR SETP DRSPAN
BCONTACT
DEFAULT *
ENDTIME *
Bulk Data ACC EOSPOL * AEFORCE
ACCMETR FBODYLD AELINK
BCBODY FBODYSBE BCPROP#*
BCBOX GBAG BCTABLE#*
BCGRID * MATD001 * BNDFIX
BCMATL MATD2AN * BNDFIX1
BCPARA MATD2OR * BNDFREE
BCPROP MATD003 * BNDFREE1
BCSEG * MATD005 BSET
BCTABLE MATD006 * BSET1
BJOIN MATD007 * BSURF#*
BRKSQL# MATD009 CELAS2D
BSURF MATD010 * DESVAR
CBEAM3 MATD012 * DRESP1
CBELT * MATD013 * IPSTRAIN#
CBUTT * MATD014 * ISTRESS#
CCRSFIL * MATD015 * ITER
CDAMP1D * MATD018 * MATD126
CDAMP2D * MATD019 * MATHED#
CELAS1D * MATD020 * MATORT#
CELAS2D * MATD20M * MBOLTUS#
CFILLET * MATD022 * NLSTRAT#
CINTC MATD024 * PBARL
COMBWLD * MATD026 * PCONV
CORD1RX MATD027 * RESTART#*
CORD2RX MATD028 * TSTEPNL
CORD3RX MATD030 *
CORD3R * MATD031 *
CSPOT * MATD032 *
CSPR MATD054 *
CWSEAM MATD057 *
D2R0000* MATD058 *
D2RAUTO* MATD059 *
D2RINER* MATD062 *
DAMPGBL * MATD063 *
DYCHANG* MATD064 *
DYDELEM* MATD066 *
DYPARAM * MATD067 *
DYRELAX* MATD068 *
DYRIGSW * MATD069 *
DYTERMT* MATD070 *
DYTIMHS * MATD071 *
ENDDYNA* MATD073 *
6 MD Nastran 2006 Release Guide
Input Changes
Section New Modified
Bulk Data MATD074 * PLOADB3
MATD076 * PSHELL1 *
MATD077 * PSHELLD
MATD080 * PSOLIDD *
MATD081 * PSPRMAT
MATD083 * PWSEAM
MATD087 * RBE2A
MATD093 * RBE2D
MATD094 * RBE2F *
MATD095 * RBE3D *
MATD097 * RBJOINT *
MATD100 * RCONN *
MATD119 * RESTART
MATD121 * SBPRET *
MATD126 * SBRETR *
MATD127 * SBSENSR *
MATD181 * SBSLPR *
MATDB01 * SPCD2 *
MATDS01 SPLINE6
MATDS02 SPLINE7
MATDS03 * SUPORT6#
MATDS04 * SWLDPRM
MATDS05 * TABLEDR *
MATDS06 * TEMPB3
MATDS07 * TICD *
MATDS08 * TIC3 *
MATDS13 * TMPSET
MATDS14 * TODYNA*
MATDS15 * TTEMP
MATF USRSUB6#
MATRIG WALL *
MONDSP1 WALLGEO
MONPNT1
MONPNT2
MONPNT3
PBEAM3
PBEAM71 * +
PBEAMD
PBELTD *
PCOMPA *
PELAS1*
CHAPTER 1 7
Overview of MD Nastran 2006
Input Changes
Section New Modified
Parameters CWLDIGNR* MARCCBAR#* MARCAUTO# MARCSOLV#
DYDTOUT,DT* MARCRCID# MARCOTIM# MARCUSUB#
DYDYLOAD* MARGPFOR# MARCPINN# MRESTALL#
DYELAS1C,* MEXTRNOD# MARCPOST# MRMAXMEM#
DYELAS1F,* MLSTRAIN# MARCRBE3# MRSPAWN2#
DYELAS1R,* MRBEPARM,# MARCSAME# MRSPEEDSE#
DYELPLET,* MRCOMPOS# MARCSLHT# MRTABLS2#
DYELPLFL,* MRCONVER# MRTABLS1#
DYELPLSY,* MRPSHELL#
DYSTEPFCT,,# MSPEEDOU#
HEATCMD# SCALEMAS,*
MARCBATCH# STEPFCT*
MARCBUSH#
MARCITER#
Items with a pound sign (#) next to them are only available for MD Nastran Implicit Nonlinear (SOL 600). Items
with an asterisk (*) sign next to them are only available for MD Nastran Explicit Nonlinear (SOL 700). See the
individual parameter for further details. + PBEAM71 has three alternates, please see the MD Nastran Quick
Reference Guide for more information.
2 Nonlinear Analysis
J
Nonlinear Transient Analysis in SOL 400, 10
J MD Nastran Implicit Nonlinear - SOL 600, 44
J
MD Nastran Explicit Nonlinear - SOL 700, 60
10 MD Nastran 2006 Release Guide
Introduction
Nonlinear transient analysis in SOL 400 improves the general nonlinear solution procedure in MD
Nastran. It allows most linear files to be run in a nonlinear analysis environment, and includes the
nonlinear solution types:
• SOL 106, nonlinear static analysis (Prerelease)
• SOL 129, nonlinear transient analysis
• Rotor Dynamics
Different types of nonlinear analysis can now talk to each other in a meaningful physical sequence.
For the MD Nastran 2006 release, nonlinear transient analysis is now considered a product release for
SOL 400. However, the nonlinear static analysis still remains a pre-release.
In this release guide, all items pertaining to the nonlinear transient analysis are discussed. For nonlinear
static analysis, only items pertaining to the transient analysis are discussed. These include the SUBCASE
and STEP Case Control command and the static pre-loads.
Benefits
The benefits of the nonlinear transient analysis in SOL 400 are discussed in this section. Some of the
benefits may be subject to the limitation discussed in next section. The benefits are:
• A new transient solution integration method, the HHT (Hilbert-Hughes-Taylor) method, to give
stable transient solution.
• Improved nonlinear iteration algorithms to make the solution easier and faster to converge.
These includes ADAPT, AUTO, ITER, and SEMI methods.
• A new SUBCASE and STEP case control structure allows flexible loading and solution
sequences. Different nonlinear analysis types can now communicate with each other in a
meaningful physical sequence in a SUBCASE.
• A new comprehensive nonlinear summary table for the transient analysis.
• Support of the initial conditions (IC).
• A new control command NLIC allows any previous converged nonlinear static solution as the
preload for the first nonlinear transient step.
CHAPTER 2 11
Nonlinear Analysis
• The boundary conditions SPC and MPC can change between load steps.
• Direct matrix input, such as K2PP, M2PP, B2PP, and TFL, can change between load steps.
• Support for “grid based reordering” for a faster version of decomposition for time step size
change and stiffness update in the nonlinear iterations.
• Support the nonlinear thermal loads in the transient analysis. Two new Bulk Data entries,
TTEMP and TMPSET, have been added for this new feature in the nonlinear transient analysis.
• Support for rotor dynamics in the nonlinear transient analysis.
• A user-friendly restart procedure introduced earlier is available to nonlinear transient analysis.
• A more flexible output method for the nonlinear transient analysis. You can use a new
parameter NLPACK to control the output and restart time steps.
• Solution output at requested time points. Also, allows the simulation of the same output logic
and format of SOL 129 by specifying a negative NO on the TSTEPNL Bulk Data entry.
• Supports linear superelements.
• Supports the XDB database for communicating with a post processor, such as MSC.Patran.
• The OTIME output request is supported (except NLSTRESS).
For numerical integration, the second order HHT (Hilbert-Hughes-Taylor) method is used in nonlinear
transient analysis in SOL 400. It provides a user-definable parameter α, which defines a numerical
damping associated with higher frequency modes, but also maintains the accuracy in the essential lower
frequency modes. Since it is a key feature of the HHT method, it is sometimes called the HHT-α method.
When α < 0 , numerical damping is introduced into the system. This leads to an unconditionally stable
integration time scheme when it is in the following range
1
– --- ≤ α ≤ 0
3
When comparing with other numerical damping methods even at α = – 1 ⁄ 3 (the maximum numerical
damping value), the HHT method still introduces less damping. Therefore, the solution is more accurate
theoretically. Note that when α = 0 , this method is equivalent to the central finite difference method.
The numerical damping, α , can be specified using parameter NDAMP (default is -0.05 in SOL 400).
Another difference is that the time step adjustment is performed at the beginning of a SUBCASE or at a
converged time step. Bisection is performed during a time step when the program determines that the
solution is diverging.
When the program determines that the large nonlinearity is gone and the solution is stabilized toward
convergence, reversal of the bisection is performed in order to maintain the time step size required by
the time step adjustment method given above.
The METHOD field on the TSTEPNL Bulk Data entry selects the nonlinear iteration method. There are
four options available.
• ADAPT – The convergence of a time step is obtained chiefly by the time step adjustment and
the load iteration. No stiffness update is performed during the normal iteration. Stiffness updates
are performed only for divergent processing and at solution convergence of a time step with
number of iterations greater than 3*MAXITR. MAXITR is the maximum number of iterations
given on the TSTEPNL Bulk Data entry. Even for divergence processing, the main method to
correct the divergence is bisection.
• AUTO – The convergence of a time step is achieved by automatically selecting the load
iterations and the stiffness updates, in combination with the ADAPT method. The ADAPT
method can be deselected by setting ADJUST=0 on the TSTEPNL Bulk Data entry. This is the
default method. For divergence processing, the divergence is corrected by a combination of
stiffness updates and bisections. The AUTO method always tries to maintain the time step size
required by the time step adjustment method.
• ITER – The convergence of a time step is achieved by performing a stiffness update at every
KSTEP load iterations, in combination with the ADAPT method. Again, the ADAPT method
can be deselected by setting ADJUST=0. When KSTEP=1, this is the full Newton method. The
divergence processing is the same as that of the AUTO method.
• SEMI – Same as the AUTO method, except that a stiffness update is performed at first iteration
of a new time step.
A stiffness update is always performed at convergence of a STEP, irrespective of the option selected.
AUTO and ADAPT are two major methods in SOL 400. The AUTO method tries to maintain the time
step size required by the time adjustment method or the user time step. The ADAPT method usually
converges with a time step size smaller than the time step required by the time step adjustment method
or the user time step. For most problems, AUTO method gives better solutions; therefore, it is selected
as the default method. However, if the time step estimated by the time step adjustment method or the user
time step is too large, the ADAPT method gives a better solution. A better solution here means that the
solution converges faster or does not diverge.
The DT and NO fields on the TSTEPNL Bulk Data entry need more explanation here. The DT field
defines the user time step size. NO, which may be positive or negative, defines that, at every |NO| time
steps, the results are saved for output. Since both time step size adjustment and bisection may modify the
time step size, options are given to select whether to output at user time step size DT or at internally
computed time step size, as shown in the following:
14 MD Nastran 2006 Release Guide
If NO > 0, the output will be at the user time step size or multiples of the user time step size.
Also, the time step size computed by the time step adjustment will never be greater than the user
time step size DT. For default, NO = 1.
If NO < 0, the output will be at the internally computed time step size, which may or may not be
at the user time point determined by DT. Also, the time step size computed by the time step
adjustment can be either greater or less than the use time step size DT.
• Multiple SUBCASEs may be executed in one job where the types of analysis, loads and
boundary conditions can be changed. All SUBCASEs are independent of each other, i.e., no load
history information is transmitted from one SUBCASE to the next. At the start of each
SUBCASE, the deflections, stresses and strains throughout the model are zero. For example:
SUBCASE 1
ANALYSIS = NLSTAT $ This line can be omitted
NLPARM = 100
STEP 110
LOAD = 110
STEP 120
LOAD = 120
CHAPTER 2 15
Nonlinear Analysis
SUBCASE 2
ANALYSIS = NLTRAN
TSTEPNL = 200
STEP 210
DLOAD = 210
STEP 220
DLOAD = 220
• In the above example, the solutions of SUBCASE 1 and SUBCASE 2 are independent of each
other. If solution divergence is detected in a step, MD Nastran will terminate the solution of the
current subcase and jump to the next subcase if it exits.
• A case control command placed below the step level allows that command to vary from one step
to another. If it is placed above the step level, the command remains constant for all steps in the
subcase. Most of the case control commands, which can be placed below the subcase level, can
also placed below the step level. For example, all steps in above examples use the same Case
Control command NLPARM = 100 in SUBCASE 1 and TSTEPNL = 200 in SUBCASE 2.
• The SOL 400 uses an enhanced dynamic solution algorithm that makes the linear static solution
and the nonlinear static solution special cases of the general nonlinear solution procedure. For
example:
SUBCASE 10
STEP 1
ANALYSIS = LNSTATIC
LOAD = 10
STEP 2
ANALYSIS = NLSTATIC
LOAD = 20
NLPARM = 20
In above example, SUBCASE 10 has two steps. The first step requests a linear static analysis
and the second step requests a nonlinear static analysis.
• In the MD Nastran release, NLSTATIC and NLTRAN analyses can be mixed in a single
SUBCASE. For example:
SUBCASE 10
STEP 1
ANALYSIS = NLSTAT
LOAD = 10
NLAPRM = 110
STEP 2
ANALYSIS = NLSTAT
LOAD = 20
NLPARM = 120
STEP 3
ANALYSIS = NLTRAN
DLOAD = 30
TSTEPNL = 130
16 MD Nastran 2006 Release Guide
In the above example, SUBCASE 10 has three steps. The first two request a nonlinear static
analysis and the third requests a nonlinear transient analysis. Since there is no NLIC request in
the third step, the final result of the second step automatically becomes the initial condition of
the third step. Note that in one SUBCASE, all steps of NLSTAT must come before the STEPs of
NLTRAN.
• The meaning of multiple SUBCASEs without STEP is dependent on the system cell NASTRAN
SYSTEM (366), as follows:
• 0 - The solutions of all SUBCASE are independent of each other. This is consistent with the
new SOL 400 procedure. MD Nastran will keep all SUBCASE commands in the Case Control
file and insert internally a “STEP 1” for each SUBCASE.
• 1 - The solution of each SUBCASE is a continuation of the previous SUBCASE. This is
similar to the solution sequence SOL 129 procedure. MD Nastran will convert internally all
the SUBCASE identification number to STEP identification number and insert a “SUBCASE
1” before the first STEP.
The default is 0.
Both SUBCASE and STEP are used in Examples 1, 2, 3, 4, 5, 7, and 8. SUBCASE only is used in
Example 9. No SUBCASE and no STEP are used in Example 6.
0 N O N - L I N E A R I T E R A T I O N M O D U L E O U T P U T
- TIME STEP - - - ERROR FACTORS - - CONV ITR MAT AVG TOTL - - - - - DISP - - - - - - NO. TOT TOT
TIME NO. BIS ADJUST ITR DISP LOAD WORK RATE DIV DIV R_FORCE WORK AVG MAX AT GRID C QNV KUD ITR
1.10800E-02 1108 0 1.0000 2 8.58E-07 3.52E-03 2.40E-08 0.01 0 1 6.6E+01 3.451E+00 1.61E-03 -8.120E-03 103 3 7 0 2202
1.10900E-02 1109 0 1.0000 2 8.81E-07 3.65E-03 2.25E-08 0.01 0 1 6.8E+01 3.462E+00 1.61E-03 -8.134E-03 103 3 7 0 2204
1.11000E-02 1110 0 1.0000 2 9.02E-07 3.77E-03 2.07E-08 0.01 0 1 7.0E+01 3.473E+00 1.61E-03 -8.147E-03 103 3 7 0 2206
1.11100E-02 1111 0 1.0000 2 9.21E-07 3.89E-03 1.88E-08 0.01 0 1 7.2E+01 3.484E+00 1.61E-03 -8.160E-03 103 3 7 0 2208
1.11200E-02 1112 0 1.0000 2 9.40E-07 4.01E-03 1.66E-08 0.01 0 1 7.4E+01 3.495E+00 1.62E-03 -8.173E-03 103 3 7 0 2210
For a large problem, TIME STEP NO,l TOT KUD, and TOT ITR in this table may be too large to be
printed in the allocated fields, resulting in print overflow. If any of these values overflows, an additional
line is printed to show the offsets of these values. In the table below, TOT ITR of the first line is 111764.
The offset of TOT ITR is shown as TOT ITR= 110000+XXX, where XXX is the number shown under
the TOT ITR column.
0 N O N - L I N E A R I T E R A T I O N M O D U L E O U T P U T
- TIME STEP - - - ERROR FACTORS - - CONV ITR MAT AVG TOTL - - - - - DISP - - - - - - NO. TOT TOT
TIME NO. BIS ADJUST ITR DISP LOAD WORK RATE DIV DIV R_FORCE WORK AVG MAX AT GRID C QNV KUD ITR
2.99820E-01 9982 0 1.0000 4 3.99E-08 5.61E-04 2.24E-09 0.03 0 1 6.0E2.386E 7.32E-02 -1.860E-01 101 3 10 0 1764
2.99830E-01 9983 0 1.0000 4 4.04E-08 5.77E-04 2.25E-09 0.03 0 1 6.1E2.386E 7.32E-02 -1.861E-01 101 3 10 0 1768
2.99840E-01 9984 0 1.0000 4 4.10E-08 5.93E-04 2.26E-09 0.03 0 1 6.3E2.385E 7.32E-02 -1.862E-01 101 3 10 0 1772
2.99850E-01 9985 0 1.0000 4 4.15E-08 6.09E-04 2.27E-09 0.03 0 1 6.4E2.385E 7.32E-02 -1.863E-01 101 3 10 0 1776
2.99860E-01 9986 0 1.0000 4 4.20E-08 6.26E-04 2.27E-09 0.03 0 1 6.6E2.385E 7.32E-02 -1.865E-01 101 3 10 0 1780
• Restart data – these are used to described the material and geometric state of the structure model.
We use them to reconstruct the stiffness, the mass, the damping matrices and other tables
required in later usage. Restart data are usually much larger than the output data if the structural
model is large. This type of data can be saved selectively without degrading the effectiveness of
the transient analysis.
For this purpose, in the current release, a user modifiable parameter: ‘PARAM, NLPACK,N’ is
available. N means that SOL 400 will pack output data for N output time steps and restart data for the
last time step as a single data package. For example, if N = 100 (the default), then one data package has
output data for 100 output time steps and restart data for the last time step. Later usage, such as restart
or initial condition for later step, can be performed only at NLPACK data group boundaries.
Some N’s have special meaning
• N = -1, all output data for a STEP and restart data for the end of the STEP are grouped into a
single package. This is the SOL 129 grouping method. In this case, the restart can be performed
only at STEP boundaries.
• N = 0, this is illegal.
• N = 1, each package of data on the database includes the output data for one output time step and
restart data. This is the NLSTATIC grouping method. Therefore, for the nonlinear static
analysis, the restart can be performed at each user output load increment, which is controlled by
INTOUT on the NLPARM Bulk Data entry.
NLPACK is used in Example 1.
Restarts
A nonlinear restart allows you to use the material or the geometrical properties of a previously converged
solution as a new starting point to continue the analysis. This is useful when you want to change your
loading sequence, the solution criteria, or to extend the analysis.
For SOL 400, a user-friendly restart procedure for the nonlinear static pre-release is available. For
nonlinear transient analysis, the following principles are noted.
• The restart must be continued at a previous converged solution point in a nonlinear transient
analysis or a static analysis by specifying a SUBCASE, STEP, and/or TIME (LOADFAC). This
is accomplished by using the Case Control command NLRESTART. Refer to the Case Control
Command Descriptions (p. 196) in the MD Nastran Quick Reference Guide.
• When the cold start is ANALYSIS=NLSTAT, it can be restarted at any user-specified output
load increment (controlled by NOUT in NLPARM Bulk Data entry).
• When the cold start is ANALYSIS=NLTRAN, it must be restarted from a saved or check-
pointed time step. The checkpoint times are dependent on DT and NO values on the TESTEPNL
Bulk Data entry, and PARAM, NLPACK of the cold start run. The checkpoint times are integer
multiples of (DT x NO) x NLPACK. For example, if DT=0.001 second, NO=10, and
NLPACK=100, the possible times that can be used for restart are at 1.0, 2.0, etc... If a requested
restart time does not match a checkpoint time, the closest checkpoint time will be used
20 MD Nastran 2006 Release Guide
• The geometry and the initial material properties of the structural model cannot be modified. This
is obvious because any modification to the geometry or the initial material properties would
invalidate the previous analysis and require the nonlinear solution to start from the very
beginning. In such cases, it is simpler to initiate another cold start.
Performing a restart is described in the following sub-sections.
Depending on the option selected with the NLRESTART command, the nonlinear restart may be
logically divided into three types: a case restart, a step restart, or a time restart:
The case restart begins the execution with a SUBCASE. All five types of modification described above
are legal for a case restart.
The step restart begins the execution with a STEP, which may be a new step or a previously executed
step. Although boundary condition and analysis type modifications are allowed, you have the
responsibility to determine whether they are meaningful. Special attention should be given to the analysis
type modification; it may not be meaningful in many situations and could lead to erroneous results.
The time restart begins execution with a user-specified TIME. For a time restart, you should not modify
the analysis type, boundary conditions, or load requests. You need to exercise discretion when
attempting other types of modification at this level. Also, in order to perform this type of restart, the
specified TIME must be at the NLPACK data group boundary. If it is not, SOL 400 will search for the
nearest data boundary and use this boundary as the restart point.
Examples for cold start and restart are given in Example 4 and Example 5.
Initial Conditions
In SOL 400, the traditional way of requesting initial conditions by using the Case Control command, IC,
and its associated Bulk Data entry, TIC, to assign initial displacements and velocities is supported.
In the current release, a user-friendly interface to define initial condition is implemented. This is the new
Case Control command NLIC. It allows users to assign the result of any previous STEP of NLSTAT
analysis as the initial condition for the first STEP of NLTRAN analysis in a SUBCASE. The following
is an example:
SUBCASE 10
STEP 1
ANALYSIS = NLSTAT
LOAD = 10
NLAPRM = 110
22 MD Nastran 2006 Release Guide
STEP 2
ANALYSIS = NLSTAT
LOAD = 20
NLPARM = 120
STEP 3
ANALYSIS = NLTRAN
NLIC STEP 1 LOADFAC 0.5
DLOAD = 30
TSTEPNL = 130
Now, the 3rd STEP will use the result of the 1st STEP at 50% load increment as the initial condition.
Please note that the NLIC can only be defined at a load increment whose output flag is on - an available
restart point in static analysis. Otherwise, a fatal error message will be issued and job will be terminated.
Here, SOL 400 will not search for the nearest available restart point, because we want you to know the
precise restart point.
In above example, if ‘LOADFAC 0.5’ is left out, then STEP 3 will take last state of STEP 1 as its initial
condition. In this case, the job will always run because the last state of a step is always a restart point.
For NLIC, there are some rules and limitations:
• SOL 400 requires that all STEPs’ of NLSTAT must be located before all STEPs’ of NLTRAN.
In other words, analysis change can only occur once between NLSTAT and NLTRAN in one
SUBCASE.
• In one SUBCASE, the beginning time of a transient STEP will be reset to 0.0 when the analysis
type is changed from a static STEP to transient STEP (or NLIC Case Control command is
detected).
• If you do not specify a NLIC entry when the analysis type changes from NLSTAT to NLTRAN,
the final result of the last STEP of NLSTAT will be picked up as the initial condition.
• The NLIC (or IC) can only appear in the first transient analysis STEP (ANALYSIS=NLTRAN)
in a SUBCASE. Otherwise, it will be ignored.
• The new Case Control command NLIC can only specify restart-able NLSTAT location as the
initial condition. (Please read the Restart section for the definition of “Restart-able”.)
• It is not allowed to use NLIC to select the initial condition from any previous STEP of
NLTRAN, SOL 400 will issue a fatal error message and you should run a restart job instead.
• In the same STEP, the NLIC cannot appear together with an IC. A fatal error message will be
issue when NLIC and IC appear in the same STEP.
• The NLIC can only be used in SOL 400 (NONLIN).
Parameter ICOPT is used with the NLIC and IC Case Control commands. At the beginning of a
NLTRAN step, the user input loads may or may not be in equilibrium with the results of the previous
preload step. When ICOPT = 0, SOL 400 will compute the initial acceleration based on your’s inputs.
Otherwise, it will be assumed that the initial acceleration is null. In other words, when ICOPT = 1 (the
default), it is assumed that the whole structure is in equilibrium automatically. Theoretically, ICOPT =
0 gives better performance in the iteration algorithm since it guarantees the equilibrium in the beginning
to avoid a suddenly jump of loads or displacements. The drawback of ICOPT = 0 comes from the
CHAPTER 2 23
Nonlinear Analysis
characteristics of the mass matrix itself, whose inverse matrix is required when computing the initial
acceleration. The mass matrix is usually highly singular for a ‘lumped’ mass matrix or for a model with
only solid 3D elements, a large amount of CPU times may be required and the accuracy of the result may
be in doubt.
An alternative way to resolve the problem of ICOPT = 1 with a suddenly large jump of loads or
displacements is to insert a NLTRAN step in between the analysis step and its previous preload step. This
step will have very short time duration in comparison with the analysis step and will provide a transition
between the preload step and the analysis step.
NLIC is used in Example 4 and Example 5. ICOPT is also used in these two examples.
ε T ( t ) = α ( T ( t ) ) ⋅ ( T ( t ) – T re f ) – α ( T 0 ) ⋅ ( T 0 – T re f ) (2-1)
where
For all nonlinear elements, the temperature effect, in both static and transient, is directly handled as
thermal strain in SOL 400 when computing the element forces.
To support the thermal effect in nonlinear transient analysis, two new bulk data entries have been created
in the MD Nastran release. They are TTEMP and TMPSET. Basically, TTEMP is to define a time-
dependent dynamic thermal field, T ( t ) , which includes a spatial temperature distribution (TMPSET)
and a time function (TABLEDi), in the same form as TLOAD1. TMPSET defines the spatial distribution
by referencing a set of grid points. The temperatures ( Tp ) of these grid points are defined by TEMPD,
TEMP, TEMPP1, or TEMPRB in the normal way. Please see the Bulk Data Entry Descriptions (Ch. 8)
in the MD Nastran Quick Reference Guide, for the details of these two new bulk data entries. By using
TTEMP and TMPSET, the whole model can be separated into finite sub-regions and each sub-region can
have its own temperature distribution pattern. If it is necessary, you can also make every grid point as
an independent sub-region or make the whole model as a single sub-region.
24 MD Nastran 2006 Release Guide
As in nonlinear static analysis, TEMP(INIT) and TEMP(LOAD) commands are used in the Case Control
file to define the temperature input in nonlinear transient analysis. The SID of TEMP(LOAD) can refer
to TTEMP to define the transient temperature load for a STEP. The spatial temperature distribution
defined by TEMP, TEMPD, etc., must have the same SID as that of the associated TTEMP. If
TEMP(INIT) refers to TTEMP entry, only the spatial temperature distribution of the entry is used and
the time function is ignored.
The Case Control command TEMP(LOAD) can also refers to a spatial distribution (TEMP, etc.) directly
without TTEMP. In this case, the temperature time functions are linearly interpolated for the current step
by using the last values of the previous step and the values of the spatial distribution referenced by the
TEMP(LOAD) command. For the first step of a subcase, the interpolation is performed between the
TEMP(INIT) temperature and the current temperature.
The thermal effects computed by the above method depend on the current material state and geometric
shape of the structural model. Therefore, they are called the ‘nonlinear’ transient temperature loads.
For all upper stream superelements and all linear elements in the residual, the thermal effects are
computed using the conventional method – you can use the DLOAD Bulk Data entry to combine multiple
TLOAD1 and TLAOD2’s, whose EXCITE_ID reference thermal loads. The DLOAD Bulk Data entry
must be referenced by a DLOAD Case Control command to be selected for analysis. The transient
temperature loads computed by this method depend on the initial stiffness matrix only and are called the
‘linear’ transient temperature load. The TEMP(LOAD) and all its corresponding temperature related
bulk data entries introduced above can only describe the thermal effect for the nonlinear elements in the
residual. If there is no DLAOD Case Control command to select the temperature load for the linear
temperature load, the temperature effect for the linear part of the structure will be lost.
An example for the temperature load is given in Example 3.
Outputs
The outputs are requested by using the Case Control commands. All existing output Case Control
commands such DISPLACEMENT, VELOCITY, ACCELERATION, STRESS, NLSTRESS, OLOAD,
SPCFORCE, etc., are also allowed in the nonlinear transient analysis in SOL 400.
Two special outputs, “Nonlinear Iteration Summary Table” and “PARAM, PH2OUT”, are available for
nonlinear transient analysis in SOL 400. In addition, a new output control, “PARAM, NLPACK”, is
added for the current release for nonlinear transient analysis only.
This new parameter, NLPACK (=100 is the default), is used to control the packed output in SOL 400.
The value of NLPACK represents the total number of output time steps in one output package. SOL 400
will process the output procedure only after collecting all "NLPACK" output time steps or at the end of
each STEP. For details, please see Output Data Grouping: NLPACK, 18.
Because the matrix and table trailers output volume may be extremely high, the diagnostic output
requests of DIAG 8 and DIAG 15 have been turned off automatically when preparing the output data in
the solver of SOL 400 if NLPACK ≠ 1. This action can reduce the .F04 file output size tremendously,
especially, when there is a large output time steps requested. You can force them on by setting DIAG
56 but it is not recommended.
Error Handling
In SOL 400, there are three types of fatal errors:
• User or system fatal errors.
• Fatal errors due to solution divergence
• Fatal errors due to lack of CPU time.
For user or system fatal errors, if error occurs before the solution iteration phase, the run will terminate
immediately without output the stored data. If the error occurs during the solution iteration phase, SOL
will try to output all stored data for the current subcase and terminate the run. The solution will not
continue into next subcase if there are multiple subcases.
For fatal error due to solution divergence, SOL 400 will try to output all stored data for the current
subcase and terminate the subcase. The solution sequence will jump to perform the next subcase if there
are multiple subcases.
For fatal error due to not enough CPU time, SOL 400 will try to output all stored data and terminate the
run.
26 MD Nastran 2006 Release Guide
User Interfaces
The user interfaces, which are important or new to the nonlinear transient analyses in SOL 400, are
summarized in this section. For detail, please refer to the MD Nastran Quick Reference Guide.
Parameters
• PARAM, LGDISP – Requests a geometric nonlinear analysis. The default is 0, no geometric
nonlinear effect.
• PARAM, FOLLOWK – Requests whether the follower force stiffness will be used in a
geometric nonlinear analysis. The default is YES.
• PARMA, FKSYMFAC – Controls whether the symmetrical follower force stiffness will be used
in a geometric nonlinear analysis. Default = 0.24.
• PARAM, MAXLP – Specifies maximum number of iterations for element relaxation and
material point sub-increment process. Default = 10.
• PARAM, NLAYERS – Specifies the number of layer for through thickness integration in the
material nonlinear analysis. Default = 5.
• PARAM, NLTOL – Selects defaults for CONV, EPSU, EPSP, and EPSW for the Bulk Data
entries NLPARM and TSTEPNL. Default = 2.
• PARAM, PH2OUT – Requests phase II outputs for a nonlinear analysis. Default = 0, phase III
output only.
• PARAM, NLPACK – Control the total output time step in one output package; see section
Output Data Grouping above. Default = 100.
CHAPTER 2 27
Nonlinear Analysis
• PARAM, NDAMP – Specifies the α values when the HHT-α method using in SOL 400, see
section A New Numerical Integration Method above. Default = -0.05.
• PARAM, ICOPT – Select how to handle the equilibrium when dealing with the initial condition,
see section Initial Conditions above.
Examples
The following nine examples show the inputs and capabilities of the nonlinear transient analysis. The
intention of these examples is to show the input structure for SOL 400. The model itself and the detailed
entries in the Bulk Data file are not important.
Example 1
Example one, EX01, is a simplified version of the standard QA file, NLTSUB02. This model only has
QUAD4 elements. It has both material nonlinearity (MATS1) and geometrical nonlinearity (PARAM,
LGDISP, 1). The 1st STEP will process the output data at every 5 output time steps and the 2nd STEP
do it only once because of the settings of the parameter NLPACK. All bold-font statements are entries
pertaining to the nonlinear analysis.
ID MSC, EX01 $
TIME 150 $
SOL 400 $
CEND
TITLE=ISOTROPIC MATERIAL & MATS1, ELLIPTIC CYLINDER UNDER EX01
SUBTITLE =SPC CHANGE IN EACH STEP, NLPACK’s
SET 10 = 10000,11200
28 MD Nastran 2006 Release Guide
SET 20 = 101
SEALL = ALL
DISPL = ALL
STRESS = 20
$
SUBCASE 100
ANALYSIS=NLTRAN
STEP 10
PARAM,NLPACK,5
DLOAD = 100
SPC = 200
TSTEPNL = 310
STEP 20
PARAM,NLPACK,-1
DLOAD = 100
SPC = 400
TSTEPNL = 320
$
BEGIN BULK
PARAM NDMAP -0.05
PARAM LGDISP 1
TSTEPNL 310 100 0.01 10 AUTO
TSTEPNL 320 100 0.01 10 AUTO
$
PLOAD4 510 101 5. THRU 112
$
TLOAD1 100 510 0 0 120
TABLED1 120 +TBD1
+TBD1 0. 0. 5. 1. 16. 1. ENDT
MAT1 100 3.+7 0.3 .283-2
MAT1 101 3.+7 0.3 .283-2
MATS1 100 PLASTIC 3.+5 500000.
$
GRID 10000 100. 0.0 10. 345
GRID 10001 100. 0.0 0.0 345
GRID 10100 99.3625 3.30491 10. 345
GRID 10101 99.3625 3.30491 0.0 345
GRID 10200 96.8149 6.51543 10. 345
GRID 10201 96.8149 6.51543 0.0 345
GRID 10300 92.5105 9.59323 10. 345
GRID 10301 92.5105 9.59323 0.0 345
GRID 10400 86.6025 12.5 10. 345
GRID 10401 86.6025 12.5 0.0 345
GRID 10500 79.2443 15.1974 10. 345
GRID 10501 79.2443 15.1974 0.0 345
GRID 10600 70.5889 17.6472 10. 345
GRID 10601 70.5889 17.6472 0.0 345
GRID 10700 60.7898 19.8111 10. 345
GRID 10701 60.7898 19.8111 0.0 345
GRID 10800 50. 21.6506 10. 345
GRID 10801 50. 21.6506 0.0 345
GRID 10900 38.3729 23.1276 10. 345
GRID 10901 38.3729 23.1276 0.0 345
GRID 11000 26.0617 24.2037 10. 345
GRID 11001 26.0617 24.2037 0.0 345
GRID 11100 13.2197 24.8406 10. 345
GRID 11101 13.2197 24.8406 0.0 345
GRID 11200 0.0 25. 10. 345
GRID 11201 0.0 25. 0.0 345
$
CHAPTER 2 29
Nonlinear Analysis
Example 2
Example two, EX02, is modified version of the standard QA file, NLTSUB02. It shows two different
types of analyses in the same job. This model is similar to the Example one except for adding some static
loads and the required NLPARM’s. All bold-font statements are entries that show the difference in the
two different analysis types.
ID MSC, EX02 $
TIME 150 $
SOL 400 $
CEND
TITLE=TEST MIXED ANALYSES - NLSTAT AND NLTRAN EX02
SUBTITLE =SPC CHANGE IN THE STEPS IN EACH SUBCASE
SET 10 = 10000,11200
SET 20 = 101
SEALL = ALL
DISPL = ALL
STRESS = 20
$
SUBCASE 100
ANALYSIS=NLSTAT
STEP 10
LOAD = 800
SPC = 200
NLPARM = 110
STEP 20
LOAD = 900
SPC = 400
NLPARM = 120
$
SUBCASE 200
ANALYSIS=NLTRAN
STEP 10
30 MD Nastran 2006 Release Guide
DLOAD = 100
SPC = 200
TSTEPNL = 310
STEP 20
DLOAD = 100
SPC = 400
TSTEPNL = 320
$
BEGIN BULK
NLPARM 110 10 AUTO YES
NLPARM 120 10 AUTO YES
$
LOAD 800 0.01 1.0 510
LOAD 900 0.05 1.0 510
(.. The rest is the same as what is in the Bulk Data file in the first
example....)
ENDDATA
Example 3
Example three, EX03, is modified form of the standard QA file, NLTTL002. This model only has 1
QUAD4 element and 2 TRAI3 elements. Its major purpose is to show the various combinations of
TTEMP and TMPSET inputs in nonlinear transient analysis for the thermal effect. All the bold-font
statements are entries related to the temperature related inputs.
ID MSC, EX03 $
SOL 400
DIAG 8,15
TIME 60
CEND
SEALL = ALL
SUPER = ALL
TITLE = THERMAL LOAD TEST FOR NONLINEAR TRANSIENT ANALYSIS EX03
SUBTITLE = Q4/T3 MODEL, TTEMP AND TMPSET
$ECHO = NONE
MAXLINES = 999999999
$
TEMPERATURE(INITIAL) = 1
SUBCASE 1
analysis=NLTRAN
step 1
TSTEPNL= 1
SPC = 2
TEMPERATURE(LOAD) = 3
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
step 2
TSTEPNL= 1
SPC = 2
TEMPERATURE(LOAD) = 4
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
SUBCASE 2
analysis=NLTRAN
step 3
TSTEPNL= 1
SPC = 2
CHAPTER 2 31
Nonlinear Analysis
TEMPERATURE(LOAD) = 5
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
step 4
TSTEPNL= 1
SPC = 2
TEMPERATURE(LOAD) = 6
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
SUBCASE 3
analysis=NLTRAN
step 5
TSTEPNL= 1
SPC = 2
TEMPERATURE(LOAD) = 7
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
step 6
TSTEPNL= 1
SPC = 2
TEMPERATURE(LOAD) = 8
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
SUBCASE 4
analysis=NLTRAN
step 7
TSTEPNL= 1
SPC = 2
TEMPERATURE(LOAD) = 9
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
step 8
TSTEPNL= 1
SPC = 2
TEMPERATURE(LOAD) = 10
DISPLACEMENT(SORT1,REAL)=ALL
nlstress = all
stress = all
$
BEGIN BULK
PARAM POST -1
PARAM COUPMASS 1
PARAM LGDISP 1
PARAM K6ROT 100.
PARAM,NOCOMPS,-1
PARAM PRTMAXIM YES
PARAM,COMPMATT,YES
PARAM,EPSILONT,INTEGRAL
PARAM NLTOL 0
TSTEPNL,1,4,0.25,1,AUTO
$
PCOMP 1 79. 0.
* 1 .04875 0. YES
$
MAT8 1 7.15+6 2.9+6 .29 1.4+6 1.9-4
32 MD Nastran 2006 Release Guide
SPC1 1 123456 1 2
spc1 1 123456 4
$
TTEMP,3,111,300
TMPSET,111,4,5
TTEMP,3,101,310
TMPSET,101,1,2
$
TTEMP,4,102,400
TMPSET,102,1,2,4,5
$
TTEMP,5,201,500
TMPSET,201,1,2,4,5
$
TTEMP,6,-1,400
$
TTEMP,7,202,700
TMPSET,202,1,2
$
TTEMP,8,204,800
TMPSET,204,1,2
$
TTEMP,9,402,900
TMPSET,402,1,2,4,5
$
TEMP 1 1 79.
TEMP 1 2 79.
TEMP 1 4 79.
TEMP 1 5 79.
$
TEMP 3 1 80.
TEMP 3 2 80.
TEMP 3 4 80.
TEMP 3 5 80.
TABLED1 300
0.0 .9875 1.0 1.0 ENDT
TABLED1 310
0.0 .9875 1.0 1.0 ENDT
$
TEMP 4 1 81.
TEMP 4 2 81.
TEMP 4 4 81.
TEMP 4 5 81.
TABLED1 400
1.0 .9876542 2.0 1.0 ENDT
$
TEMP 5 1 80.
TEMP 5 2 80.
TEMP 5 4 80.
TEMP 5 5 80.
TABLED1 500
0.0 .9875 1.0 1.0 ENDT
$
TEMP 6 1 81.
TEMP 6 2 81.
TEMP 6 4 81.
TEMP 6 5 81.
$
$
TEMP 7 1 80.
34 MD Nastran 2006 Release Guide
TEMP 7 2 80.
TEMP 7 4 80.
TEMP 7 5 80.
TABLED1 700
0.0 .9875 1.0 1.0 ENDT
$
TEMP 8 1 81.
TEMP 8 2 81.
TEMP 8 4 81.
TEMP 8 5 81.
TABLED1 800
1.0 .9876542 2.0 1.0 ENDT
$
TEMP 9 1 80.
TEMP 9 2 80.
TEMP 9 4 80.
TEMP 9 5 80.
TABLED1 900
0.0 .9875 1.0 1.0 ENDT
$
TEMP 10 1 81.
TEMP 10 2 81.
TEMP 10 4 81.
TEMP 10 5 81.
ENDDATA
Example 4
Example four, EX04, is modified from the standard QA file, NLTIC19. This model only has 1 HEXA
element. Its purpose is to shows two different types of analyses in the same SUBCASE, the model itself
is not important. All the bold-font statements are entries that show the difference between those analyses
and how to set the initial condition for the nonlinear transient analysis after static analysis. Note that the
nonlinear transient analysis does not use the final results of the closest static analysis as the initial
condition; instead, it asks the results of the 50% load increment in the 1st STEP to be the initial condition.
Also, parameter ICPOT=0 is selected, which will compute the initial acceleration at the beginning (t=0.0)
of the transient analysis when it is not in balance.
ID MSC, EX04 $
DIAG 8,15
TIME 60
SOL 400 $
CEND
TITLE= ELASTIC-PLASTIC STATIC & TRANSIENT RESPONSE, EX04
SUBTI= INITIAL ACCELERATION COMPUTED - PARAM,ICOPT,0
SET 1 = 1111
SET 2 = 100
DISP = 1
VELO = 1
ACCE = 1
OLOAD = 1
$ STRESS(PLOT) = 2
SUBCASE 1130
step 1
LABEL=UNIAXIAL TENSION (LOADING)
ANALYSIS=NLSTAT
SPC=100
LOAD=1130
CHAPTER 2 35
Nonlinear Analysis
NLPARM = 1
step 2
LABEL=UNIAXIAL TENSION (UNLOADING)
ANALYSIS=NLSTAT
SPC=100
NLPARM = 1
step 10
LABEL=I.C. FROM THE FIRST NLSTAT STEP(50%) - UNBALANCED CASE (NLIC)
ANALYSIS=NLTRAN
NLIC STEP 1 LOADFAC 0.5
SPC=100
DLOAD=2130
TSTEPNL=10
param,icopt,0
BEGIN BULK
PARAM,LANGLE,3
PARAm,LGDISP,1
PARAM,W4,1.0
$
NLPARM 1 4 AUTO ALL
1.-6
TSTEPNL 10 2000 0.001 AUTO
$
MAT1 1 30.0+6 11.5+6 0.3 7.332-2 0.01
PSOLID 1 1
$
SPC1 100 123456 1000
SPC1 100 1 1010
SPC1 100 2 1001
SPC1 100 3 1100
GRDSET 456
$
TLOAD1 2130 2130 0 500
TABLED1 500 +TAB1
+TAB1 0. 0. 1. -1. 1.2 0. 10. 0. +TAB2
+TAB2 ENDT
$
LOAD 1130 -1.6 2. 121
LOAD 2130 -1.6 1. 121
$
GRID 1000 0. 0. 0.
GRID 1100 1. 0. 0.
GRID 1110 1. 1. 0.
GRID 1010 0. 1. 0.
GRID 1001 0. 0. 1.
GRID 1101 1. 0. 1.
GRID 1111 1. 1. 1.
GRID 1011 0. 1. 1.
$
CHEXA 100 1 1000 1100 1110 1010 1001 1101 +HX100
+HX100 1111 1011
$
PLOAD4 121 100 36.+3 1100 1111
PLOAD4 121 100 36.+3 1000 1011
ENDDATA
36 MD Nastran 2006 Release Guide
Example 5
Example five, EX05, is a modified version of the standard QA file, NLTIC19R. This model is a restart
run of the Example four, EX04. Since there is no structure change in the SUBCASE 1130 and there is
no parameter in NLRESTART command, this restart job will start from the 2nd SUBCASE. Its purpose
is to shows how the Case Control commands NLRESTART and NLIC can work together. All bold-font
statements are entries that show the key Case Control commands in this example. Note that the nonlinear
transient analysis in the 2nd SUBCASE asks the final results in the 1st STEP of the 1st SUBCASE to be
the initial condition. Also, parameter ICPOT=1 (the default) is selected, which will NOT compute the
initial acceleration but loads in the beginning (t=0.0) of the transient analysis, that assumes the whole
model is in equilibrium automatically when initial conditions are applied.
ASSIGN RSFILE=’DBSDIR:ex04.MASTER’ $
RESTART LOGICAL=RSFILE $
$
ID MSC, EX05 $
DIAG 8,15
TIME 60
SOL 400 $
CEND
TITLE= ELASTIC-PLASTIC STATIC & TRANSIENT RESPONSE, EX05
SUBTI= NO INITIAL ACCELERATION COMPUTED - PARAM,ICOPT1
SET 1 = 1111
SET 2 = 100
DISP = 1
VELO = 1
ACCE = 1
OLOAD = 1
$ STRESS = 2
NLRESTART
SUBCASE 1130
step 1
LABEL=UNIAXIAL TENSION (LOADING)
ANALYSIS=NLSTAT
SPC=100
LOAD=1130
NLPARM = 1
step 2
LABEL=UNIAXIAL TENSION (UNLOADING)
ANALYSIS=NLSTAT
SPC=100
NLPARM = 1
step 10
LABEL=I.C. FROM THE FIRST NLSTAT STEP - UNBALANCED CASE (NLIC)
ANALYSIS=NLTRAN
NLIC STEP 1 LOADFAC 0.5
SPC=100
DLOAD=2130
TSTEPNL=10
param,icopt,0
SUBCASE 1131
LABEL=I.C. FROM THE 1st NLSTAT STEP OF PREVIOUS SUBCASE (NLIC)
ANALYSIS=NLTRAN
NLIC SUBCASE 1130 STEP 1
SPC=100
DLOAD=2130
TSTEPNL=10
CHAPTER 2 37
Nonlinear Analysis
param,icopt,1
BEGIN BULK
ENDDATA
Example 6
Example six, EX06, is modified from the standard QA file, NLTROT01. This model simply shows how
to run Rotor Dynamics in SOL 400. All bold-font statements are the basic entries that may be required
in rotor dynamic analysis.
ID MSC, EX06 $
SOL 400
DIAG 8, 15
CEND
$
ANALYSIS=NLTRAN
RIGID=LINEAR
$
RGYRO= 100
TSTEP= 100
SET 99= 101
disp= 99
$
BEGIN BULK
$
UNBALNC, 100, 2.0, 101, 0., 1., 0.,
, 1.0, 0.0, 0.0, 0.0, 1000., none
$
TSTEPNL, 100, 5000, 3.0E-4, 10
$
ROTORG 10 101 THRU 103
$
RSPINT 10 101 102 FREQ 100
0.01
TABLED1, 100,
, 0.0, 22.5, 100.0, 22.5, endt
$
$ ROTOR 1
$
GRID, 101, , 0., 0., 0.
GRID, 102, , 1., 0., 0., , 14
GRID, 103, , 2., 0., 0.
GRID, 104, , 0., 0., 0.
GRID, 105, , 2., 0., 0.
$
RBE2, 1001, 102, 123456, 101, 103
RBE2, 1002, 101, 123456, 104
RBE2, 1003, 103, 123456, 105
$
CONM2, 1004, 102, , 50.,
, 5.0, , 15.0, , , 15.0
$
CELAS1, 1005, 1000, 104, 2
CELAS1, 1006, 1000, 104, 3
CELAS1, 1007, 1000, 105, 2
CELAS1, 1008, 1000, 105, 3
PELAS, 1000, 1.0E+5, 0.0
$
param, g, 0.05
38 MD Nastran 2006 Release Guide
Example 7
Example seven, EX07, is modified from the standard QA file, NLTK2PP1. This model shows how to
apply K2PP in SOL 400, such as using different sets of K2PP in different STEP. For example, the 1st
STEP requests the K2MAT matrix as a K2PP input and the 2nd STEP requests the combination of
K2MAT and K3MAT matrices as a K2PP input. All the bold-font statements are the entries that are
required in this kind of analysis.
ID MSC, EX07 $
SOL 400 $
DIAG 8,15
TIME 50
CEND
$
SEALL=ALL
MPC = 20
SPC = 10
analysis=NLTRAN
TITLE = LINEAR TRANSIENT RESP. (DIRECT METHOD) TEST EX07
SUBTITLE = COULOMB FRICTION LESS F3(0),F4(0)
$ ECHO = NONE
SET 10= 1,7
DISP=10
$
SUBCASE 1
STEP 1
DLOAD = 12
K2PP = K2MAT
TSTEPNL = 10
STEP 2
DLOAD = 12
K2PP = K2MAT, K3MAT
TSTEPNL = 10
$
BEGIN BULK
param,ndamp,-0.055
$
CORD2R 1 0 0. 0. 0. 0. 0. 1. +CORD
+CORD 1. 0. 0.
$
GRDSET 1 1 1246
GRID 1 -460. 0. 0.
GRID 3 -460. 0. 100.
GRID 5 -460. 0. 200.
GRID 2 290. 0. 0.
GRID 4 290. 0. 100.
GRID 6 290. 0. 200.
GRID 7 0. 0. 200.
$
CONM2 3 3 1 0.6867
CONM2 4 4 1 1.2735
CONM2 7 7 1 15.445 +CONM
+CONM 3.0E5
$
CHAPTER 2 39
Nonlinear Analysis
CELAS2 1 2200. 1 3 3 3
CDAMP2 1 3.2 1 3 3 3
CELAS2 2 4200. 2 3 4 3
CDAMP2 2 6.2 2 3 4 3
CELAS2 3 550. 3 3 5 3
CDAMP2 3 13.3 3 3 5 3
CELAS2 4 2000. 4 3 6 3
CDAMP2 4 0. 4 3 6 3
$
MPC 10 7 3 750. 5 3 -290. +MPC10
+MPC10 6 3 -460.
MPC 11 7 5 750. 5 3 -1. +MPC11
+MPC11 6 3 1.
MPCADD 20 10 11
$
SPC1 10 5 1 THRU 6
$
TABLED1 12 +TBLD11
+TBLD11 -100. 0. 0. 0. 0.005 3. 100. 3. +TBLD12
+TBLD12 ENDT
$
EPOINT 101
$
DMIG K2MAT 0 1 1 1
DMIG K2MAT 1 3 101 2.
DMIG K2MAT 101 1 3 -2.
$
DMIG K3MAT 0 1 1 1
DMIG K3MAT 1 3 101 3.
DMIG K3MAT 101 1 3 -3.
$
DAREA 12 101 1.
DELAY 12 101 0.
$
EPOINT 202
$
DMIG K2MAT 2 3 202 2.
DMIG K2MAT 202 2 3 -2.
$
DMIG K3MAT 2 3 202 3.
DMIG K3MAT 202 2 3 -3.
$
DAREA 12 202 1.
DELAY 12 202 0.54
$
TLOAD1 12 12 12 12
$
TSTEPNL 10 1000 0.002 1 AUTO 10000
ENDDATA
Example 8
Example eight, EX08, is modified from the standard QA file, NLTSTP06. This model shows the
example of the SPC-Set change between STEP’s. All the bold-font statements are the entries that are
required.
ID MSC, EX08 $
TIME 150 $
SOL 400 $
40 MD Nastran 2006 Release Guide
DIAG 8,15 $
CEND
TITLE=ANISOTROPIC MATERIAL & MATS1, ELLIPTIC CYLINDER UNDER EX08
SUBTITLE = TWO STEP’S TEST, SPC SET CHANGE AND SAME DT
SET 10 = 10000,11200
SET 20 = 101
SEALL = ALL
DISPL = ALL
STRESS = 20
SPCF = ALL
OLOAD = ALL
$
SUBCASE 100
ANALYSIS=NLTRAN
STEP 10
DLOAD = 100
SPC = 200
TSTEPNL = 310
STEP 20
DLOAD = 100
SPC = 400
TSTEPNL = 320
$
BEGIN BULK
PARAM LGDISP 1
TSTEPNL 310 100 0.01 10 AUTO +TS11
TSTEPNL 320 100 0.01 10 AUTO +TS21
$
PLOAD4 510 101 5. THRU 112
$
TLOAD1 100 510 0 0 120
TABLED1 120 +TBD1
+TBD1 0. 0. 5. 1. 16. 1. ENDT
MAT2 100 3.2967+79.8901+60. 3.2967+70. 1.1538+70.283-2
MAT2 101 3.2967+79.8901+60. 3.2967+70. 0.283-2
MATS1 100 PLASTIC 3.+5 500000.
$
GRID 10000 100. 0.0 10. 345
GRID 10001 100. 0.0 0.0 345
GRID 10100 99.3625 3.30491 10. 345
GRID 10101 99.3625 3.30491 0.0 345
GRID 10200 96.8149 6.51543 10. 345
GRID 10201 96.8149 6.51543 0.0 345
GRID 10300 92.5105 9.59323 10. 345
GRID 10301 92.5105 9.59323 0.0 345
GRID 10400 86.6025 12.5 10. 345
GRID 10401 86.6025 12.5 0.0 345
GRID 10500 79.2443 15.1974 10. 345
GRID 10501 79.2443 15.1974 0.0 345
GRID 10600 70.5889 17.6472 10. 345
GRID 10601 70.5889 17.6472 0.0 345
GRID 10700 60.7898 19.8111 10. 345
GRID 10701 60.7898 19.8111 0.0 345
GRID 10800 50. 21.6506 10. 345
GRID 10801 50. 21.6506 0.0 345
GRID 10900 38.3729 23.1276 10. 345
GRID 10901 38.3729 23.1276 0.0 345
GRID 11000 26.0617 24.2037 10. 345
GRID 11001 26.0617 24.2037 0.0 345
GRID 11100 13.2197 24.8406 10. 345
CHAPTER 2 41
Nonlinear Analysis
Example 9
Example nine, EX09, is modified from the standard QA file, NLTSTP07. This model shows that the
upper stream superelement can have output requests that are different from the residual. Also, a case
control command OTIME is used here to select a subset of all output time steps, which is selected by the
TSTEPNL Bulk Data entry. It can reduce the output data dramatically. For example, in the following
file, TSTEPNL asks output at time=0.0, 0.1,…, 1.0 second but OTIME overwrites this request and only
makes output at time=0.5 second. All the bold-font statements are the entries that are required to
complete all above requests in this example.
ID MSC, EX09 $
TIME 150 $
SOL 400 $
DIAG 8,15 $
CEND
TITLE=Test For Upperstream Superelement Output Request EX09
SUBTITLE = OTIME Output Request
SET 1 = 0.5
SET 10 = 11200
SET 20 = 101
LOADSET = 500
DISPL = 10
OTIME = 1
$
SUBCASE 10
42 MD Nastran 2006 Release Guide
SUPER=10
METHOD=10
SET 10001 = 10001
DISP =10001
SUBCASE 100
ANALYSIS=NLTRAN
DLOAD = 100
SPC = 200
TSTEPNL = 310
$
BEGIN BULK
PARAM LGDISP 1
$
SESET,10,10000,thru,10301
SEQSET1 10 0 10500 THRU 11001
EIGRL 10
$
TSTEPNL 310 100 0.01 10 AUTO +TS11
$+TS11 1.E-2
LSEQ 500 110 510
PLOAD4 510 101 5. THRU 112
$
TLOAD1 100 110 0 0 120
TABLED1 120 +TBD1
+TBD1 0. 0. 5. 1. 16. 1. ENDT
$MAT1 100 3.+7 0.3 .283-2
MAT2 100 3.2967+79.8901+60. 3.2967+70. 1.1538+70.283-2
MAT2 101 3.2967+79.8901+60. 3.2967+70. 0.283-2
MATS1 100 PLASTIC 3.+5 500000.
$
GRID 10000 100. 0.0 10. 345
GRID 10001 100. 0.0 0.0 345
GRID 10100 99.3625 3.30491 10. 345
GRID 10101 99.3625 3.30491 0.0 345
GRID 10200 96.8149 6.51543 10. 345
GRID 10201 96.8149 6.51543 0.0 345
GRID 10300 92.5105 9.59323 10. 345
GRID 10301 92.5105 9.59323 0.0 345
GRID 10400 86.6025 12.5 10. 345
GRID 10401 86.6025 12.5 0.0 345
GRID 10500 79.2443 15.1974 10. 345
GRID 10501 79.2443 15.1974 0.0 345
GRID 10600 70.5889 17.6472 10. 345
GRID 10601 70.5889 17.6472 0.0 345
GRID 10700 60.7898 19.8111 10. 345
GRID 10701 60.7898 19.8111 0.0 345
GRID 10800 50. 21.6506 10. 345
GRID 10801 50. 21.6506 0.0 345
GRID 10900 38.3729 23.1276 10. 345
GRID 10901 38.3729 23.1276 0.0 345
GRID 11000 26.0617 24.2037 10. 345
GRID 11001 26.0617 24.2037 0.0 345
GRID 11100 13.2197 24.8406 10. 345
GRID 11101 13.2197 24.8406 0.0 345
GRID 11200 0.0 25. 10. 345
GRID 11201 0.0 25. 0.0 345
$
CQUAD4 101 100 10000 10001 10101 10100
CQUAD4 102 100 10100 10101 10201 10200
CQUAD4 103 100 10200 10201 10301 10300
CHAPTER 2 43
Nonlinear Analysis
• There are two new parameters for allocating the memory use, the first
PARAM,MRALLOCG,value; allocates the initial amount of General memory. The value
specified is in megabytes. In this release General memory is used for material property data,
boundary condition data, overhead, and the assembly of the global stiffness matrix (except CASI
solver). The General memory is also used for Solver 0 and Solver 4 (NLSTRAT,ISOLVER).
The second parameter PARAM,MRALLOCS,value’ allocates the initial memory for the
decomposition of the global stiffness matrix for Solver 8 (multifrontal direct solver). This is
often useful to avoid reallocation of memory which occurs in deformable-deformable contact.
For parallel processing the amount specified is the total for the job. It is divided by the number
of domains used for each domain.
• The CASI iterative solver was added; which can be activated by the NLSTRAT ISOLVER
entry. Currently, two preconditioner are available, a primal and standard preconditioned, types 0
and 1, respectively. The primal preconditioner is the default and is recommended for ill-
conditioned problems. If a non-positive definite matrix is encountered (such as in a buckling
analysis), the solver automatically switches to a direct solver. In this release this solver may not
be used for Herrmann elements, where the Lagrange multiplier is at the corner node, such as the
higher order elements or the triangular and tetrahedral elements. This solver should also not be
used with the gap element.
As an example of the improved performance with this solver an engine block with 2.2 million
degrees of freedom was analyzed with the following normalized results.
Normalized
Solver Type Solution Time
2 0.785
8 1.0
9 0.174
• The computational times associated with running jobs in parallel has been reduced. This
reduction is both in the time associated with creating the domains in during the solution process.
For poorly conditioned models, the improvements have been as large as a factor of two.
• MD Nastran 2006 PC versions are released using the Intel version of MSC.Marc as the default.
The Digital Visual Fortran (DVF) version is available on the MD Nastran CD, but is no longer
fully supported by SOL 600. If you prefer to use the DVF version, the OUTR options (op2,
punch, xdb, f06) are no longer available and if attempted will generate an error.
Memory has been reduced for analyses run in parallel.
• The number of contact bodies has been increased from 99 to 999
• We have made improvements to MD Nastran so more problems with MPC's, RBE2, RBAR, and
RTRPLT will run to completion. For the 2006 release, AUTOMSET (param,automset,yes) has
been added. Most analyses will not require AUTOMSET and since it takes additional
computing time, MPC-CHECK,3 (param,marmpchk,3) should usually be used instead for
models with complex rigid systems.
46 MD Nastran 2006 Release Guide
• MPC's and rigid elements combined with contact and/or the same node in more than one contact
body can sometimes cause the solver portion of SOL 600 to fail. There is a new feature in
MSC.Marc known as optimized contact that can frequently help these types of models to run
correctly. For version MSC.Marc 2005 r3, optimized contact is not the default either in
MSC.Marc (stand-alone) or MD Nastran SOL 600. If MSC.Marc exit 2011 or convergence
problems are encountered with such models, you should try optimized contact. To invoke
optimized contact from MD Nastran, set field 6 of each BCBODY entry with flexible contact to
2. In addition, set field 3 of each "SLAVE" continuation line (the next line after all lines with
SLAVE) to 2. In turn, this sets MSC.Marc's CONTACT entry 4th datablock, 3rd field to 2 and
each CONTACT TABLE 3rd datablock 8th entry to 2 respectively. Detailed discussions and an
example of optimized are provided in Chapter 8 of the MSC.Marc Theory and Information
Manual (Volume A of the MSC.Marc documentation) - see text before and after figure 8-4.
• For most bulk data entries, SOL 600 does not make the distinction between zero and a blank.
Thus, if a zero is entered and the default is some other value, the default will normally be used.
If you wish to use zero, enter a small number such as 1.0E-12 instead.
• Not all MD Nastran Case Control or Bulk Data entries are supported in SOL 600. Please
consult the MD Nastran Version 2006 QRG (SOL 600 Executive Control entry) for a list of
items that are not supported.
• Inertia Relief has been added. The SOL 600 capability exceeds that available in other MD
Nastran solution sequences using new Bulk Data entry, SUPORT6.
• The “support” method may be used to specify which degrees of freedom should be
“supported” for each body. This is an extension of the PARAM,INREL,1 method and may
use fewer computer resources than the eigenvalue method for some models.
Inertia Relief may be employed on a subcase-by-subcase basis and can be removed if all
previously unsupported bodies merge into the main body (which is supported) either all at once
or gradually.
• PSHELL with the same bending-membrane coupling as in other solution sequences has been
added into the 2006 release. This will allow you to analyze composite structures using the
smeared approach (such as done in other MD Nastran solution sequences) or through-the-
thickness integration (which is more accurate and presently the only way to analyze composite
structures) will be offered. If material nonlinearity occurs in the element, then the PSHELL
smeared approach should not be used. The choice is activated by using PARAM,MRPSHELL,1.
• Post-buckling responses using the single-file parallel option sometimes do not agree with the
responses using a single processor for the 2006 version. It is recommended that post-buckling
analyses use a single processor.
• A new option named DMIG-OUT is available in the 2006 release. This capability will allow the
stiffness, differential stiffness and mass matrices (assembled or element-by-element) to be
output for selected output times or at the end of each nonlinear subcase for use in other analyses.
This is a less expensive procedure, than using the Bulk Data entry, MDMIOUT (which creates a
superelement), but results in a much larger matrix.
• We have made the following improvements to the OP2 file produced by SOL 600 for MD
Nastran 2006:
CHAPTER 2 47
Nonlinear Analysis
• Contact forces are now included on the OP2 file in the “slide line” block.
• GPFORCE is available starting with the 2006 release
• MPC forces are now included on the OP2 file.
• In the 2006 release, Case Control MUST be used to create an OP2 file. This is consistent with
other Nastran solution sequences, but is a change in behavior from previous releases.
• For the 2006 release, you must include Case Control requests such as DISP=ALL in order to
obtain output in op2, xdb, punch or f06 files. In addition, OUTR requests on the SOL 600
entry must be made (for example OUTR=OP2,F06). The applicable Case Control requests
for SOL 600 are DISP, STRESS, STRAIN, SPCFORCE, MPCFORCE, GPFORCE and
BOUTPUT. BOUTPUT maps 3D contact to the older 2D Slideline Contact datablock (see
item codes for contact in section 6 of the 2006 Quick Reference Guide). At present,
MSC.Patran cannot process 2D slideline or 3D contact from the op2 or xdb.
• The output interval for the t16 file (and thus the OP2 file) is controlled by either the NLPARAM
bulk data or PARAM,MARCOTIM, which is documented in the MD Nastran 2006 Quick
Reference Guide.
• A preliminary version of Grid Force Balance is available. The output is available in the op2,
xdb, f06 and punch files and is triggered by Case Control GPFORCE( )=ALL as well as
PARAM,MARGPFOR
• A simplified procedure is available for activating large displacement – large strain analysis, by
using the PARAM,MLSTRAIN. This option will automatically select the best formulation
based upon the individual element type and material model. It effectively replaces the use of
PARAM,LGDISP; PARAM, MRUPDATE; PARAM, MRFINITE and PARAM,MARCDILT
for most simulations. Internally the following formulations are used.
• The Gent and Arruda Boyce models may now be used with plane stress, shell and membrane
elements
48 MD Nastran 2006 Release Guide
• The NLELAST option on the MATS1 is now supported in SOL 600 as in the other solution
sequences (106, 129, and 400). It is more general in that it may be used will all structural element
types (except the shear panel).
• A new higher order tetrahedral element is available which has improved behavior in bending. To
activate this element, use the PARAM,MRALIAS,127184 to switch the element formulation
from SOL 600 element type 127 to 184.
• The method for updating the thickness of shells and plane stress elements has changed if the
PARAM,MRFINITE or PARAM,MLSTRAIN. This is activated using: PARAM,MRV09V11,1
• The in-plane shear behavior of the CQUAD 4 element using reduced integration has been
improved. This element technology is invoked by using PARAM,075140. This is activated
using: PARAM,MRV09V11,1
• Dissimilar meshes of shell elements may now be “glued” together using fully moment carrying
capability of the contact glue option. This is activated using the BCTABLE option.
• A new parameter has been added when using SOL 600 analysis. When relevant, this generally
results in improved behavior, but will lead to some differences in results with the previous
release. This is activated using PARAM,MRV09V11,value, where
Note that the above features are only used for certain problems. Even though all are included
with the default option, they have no effect for problems that do not use them. For example,
feature,5801 has no effect on models that do not use SOL 600 element type 140, feature 601 has
no effect on models that do not have contact.
• The speed of the t16op2 results translator has been increased by a factor of 4 or more for large
models. The speed increase is triggered using PARAM,MSPEEDOU,1
• Translation speed has increased for beam and shell type elements (in addition to the previous
speed enhancements for solid elements) by using PARAM,MSPEEDSE,2 (or 3). The speed
increase varies from model to model but can be as great as a factor of 4-10 for some models.
CHAPTER 2 49
Nonlinear Analysis
• A new Bulk Data entry for brake squeal named BRKSQL is available which replaces several
parameters and MARCIN entries previously used. With the entry, new capabilities are also
introduced. It is now possible to determine the unstable brake squeal roots using MD Nastran’s
complex eigenvalue solver and unsymmetric friction stiffness matrices for an undeformed
structure or after a nonlinear subcase. Brake squeal analysis for SOL 600 is accomplished by
starting a primary MD Nastran job (as usual) which spawns SOL 600 to calculate the
unsymmetric friction stiffness matrices either at the beginning or end of a nonlinear subcase,
then spawning a second MD Nastran job to calculate the complex eigenvalues. Unstable roots
indicate potential brake squeal. They are designated by positive real roots and negative damping
in the f06 output file. See the BRQSQL entry from more details and the attached example.
• A new fixed-time stepping approach has been added which avoids some convergence problems
with AUTO LOAD particularly for multiple subcases. AUTO LOAD is still available but the
new approach is recommended particularly for multiple subcases. The available methods are
selected using PARAM,MARCITER,N where N is the number of fixed time steps desired.
• MD Nastran SOL 600 now uses the same compilers on all systems. This allows user
subroutines to be employed on all systems. For Windows and Linux, the Intel compiler is now
used. Previously, the Digital Visual Fortran and PFG Fortran compilers, respectively, were
used. Only the Intel versions are delivered with MD Nastran.
• User subroutine support has been added through Bulk Data entry, USRSUB6
• The SOL 600,ID executive control statement has been revised to add some clarifying remarks
• TEMP(INIT) does not work properly using Updated Lagrange (param,mvarupdat,1). If
TEMP(INIT) is required in the model, please use the Total Lagrange formulation
(param,marupdat,-1). If all initial temperatures are zero, TEMP(INIT) may be omitted and
Updated Lagrange may be used.
• The Case Control BCTABLE text has been clarified
• The NDDL description for some SOL 600 bulk data entries is not up to date. These entries are
intercepted and placed on a special database used by the SOL 600 translators. Another aspect of
the NDDL not being up to date is that the 3D contact Bulk Data entries are only valid for SOL
600. They must be removed from the input deck for other solution sequences for MD Nastran
2006. It is anticipated that this will be corrected in the next MD Nastran release.
• The following new Bulk Data entries have been added for SOL 600 (see next section for a
description of each new entry):
• BRKSQL (Brake Squeal)
• SUPORT6 (Inertia Relief for SOL 600)
• USRSUB6 (User subroutines for SOL 600)
• The following Bulk Data entries have been revised or additional capabilities added:
• RESTART (Shared with SOL 700, items for SOL 700 were added)
• NLSTRAT (CASI solver, rigid rotation control added)
• IPSTRAIN (text clarified)
• IPSTRESS (text clarified)
50 MD Nastran 2006 Release Guide
• MRSPAWN2
• MARCPINN
• MRESTALL
• MARCOPP2
• MSPEEDSE
• MARCSAME
• The following parameter has been removed:
• MARNOT16
• Detailed Descriptions of each new Bulk Data entry:
52 MD Nastran 2006 Release Guide
BRKSQL Specifies data for Brake Squeal Calculations using SOL 600
Format:
1 2 3 4 5 6 7 8 9 10
BRKSQL METH AVSTIF FACT1 GLUE ICORD
R1 R2 R3 X Y Z
NASCMD
RCFILE
Example:
BRKSQL 1 5.34E6 1.0 1.0
0.0 0.0 1.0 2.0 3.0 4.0
tran
nastb
Field Contents
METH Method flag corresponding to the type of brake squeal calculations to be performed.
(Integer, Default = 1)
0 = Perform brake squeal calculations before any nonlinear analysis has taken place.
Field Contents
R1 X direction cosine (basic coord system) of axis of rotation; corresponds to ROTATION
A second datablock. (Real; no Default. Required field)
R2 Y direction cosine (basic coord system) of axis of rotation; corresponds to ROTATION
A second datablock.
R3 Z direction cosine (basic coord system); corresponds to ROTATION A second
datablock. (Real; no Default. Required field)
X X coordinate in basic coord system of a point on the axis of rotation; corresponds to
ROTATION A third datablock. (Real; no Default. Required field)
Y Y coordinate in basic coord system of a point on the axis of rotation; corresponds to
ROTATION A third datablock. (Real; no Default. Required field)
Z Z coordinate in basic coord system of a point on the axis of rotation; corresponds to
ROTATION A third datablock. (Real; no Default. Required field)
NASCMD Name of a command to run MD Nastran (limited to 64 characters) -- used in
conjunction with the CONTINUE options on the SOL 600 entry. The full path of the
command to execute MD Nastran should be entered. The string will be converted to
lower case. See Remark 2. (Character; Default = nastran)
RCFILE Name of an RC file to be used with a secondary MD Nastran job (limited to 8
characters) -- used in conjunction with the CONTINUE options on the SOL 600 entry.
An extension of “.rc” will automatically be added. See Remark 2. (Character; Default
= nastb.rc)
Remarks:
1. This entry is used to calculate complex eigenvalues for brake squeal using unsymmetric stiffness
friction matrice. Options exist to obtain the unsymmetric stiffness matrices using the undeformed
geometry (initial contact) or after all specified nonlinear subcases.
2. SOL 600 performs brake squeal calculations. The main (original) MD Nastran job with input file
jid.dat or jid.bdf spawns the SOL 600 job. MD Nastran SOL 600 calculates unsymmetric friction
stiffness matrices that1 are saved on a file (jid.marc.bde with associated file jid.marc.ccc). The
primary MD Nastran job then creates input data for a second MD Nastran job (jid.nast.dat) to use
the unsymmetric stiffness matrices in an complex eigenvalue extraction. The primary MD
Nastran job spawns a second MD Nastran job to calculate the complex eigenvalues. The complex
eigenvalues and eigenvectors are found in jid.nast.f06, jid.nast.op2, etc.
NASCMD is the name of the command used to execute the secondary MD Nastran job.
NASCMD can be up to 64 characters long and must be left justified in field 2. The sting as entered
will be used as is -- except that it will be converted to lower case regardless of whether it is entered
in upper or lower case.
54 MD Nastran 2006 Release Guide
RCFILE is the name of an RC file to be used for the secondary MD Nastran job. It should be
similar to the RC file used for the primary run except that additional memory will usually be
necessary to calculate the complex eigenvalues and batch=no should also be specified. RCFILE
is limited to 8 characters and an extension of “.rc” will be added automatically. This entry will be
converted to upper case in MD Nastran but will be converted to lower case before spawning the
complex eigenvalue run. This RC file must be located in the same directory as the MD Nastran
input file. This entry is the same as specifying PARAM,MRRCFILE. One or the other should be
used.
3. MPC are produced for contact surfaces with glued contact. DMIGs are produced for contact
surfaces without glued contact. The brakes and drums should not use glued contact; other regions
of the structure can used glued contact.
4. The continuation lines may be omitted if defaults are appropriate.
5. When a BRKSQL entry is used, PARAM,MRMTXNAM and PARAM,MARCFIL1 should not
be entered.
6. When brake squeal matrices are output, unsymmetric friction stiffness matrices are output for
non-glued contact surfaces. For surfaces with glued contact, MPCs are output. The GLUE flag
signals SOL 600 to look for these MPCs and combine them with other MPCs that might be in the
model using MPCADD, or if no MPCs were originally used, to add the MCPs due to glued
contact. Glued contact surfaces may not be used for the disk-rotor interface. If GLUE is zero or
blank, the MPC for glued contact in the brake squeal bde file, if present, will be ignored.
Sometimes MD Nastran puts out MPCs with only one degree-of-freedom defined. Such MPCs
will be ignored; otherwise, MD Nastran will generate a fatal error.
7. If ICORD=1, an MD Nastran t19 file will be automatic.
CHAPTER 2 55
Nonlinear Analysis
SUPORT6 Inertia Relief for SOL 600 - Used in MD Nastran Implicit Nonlinear -
SOL 600 only
Format:
1 2 3 4 5 6 7 8 9 10
SUPORT6 SID METH IREMOV GID CDOF CID IDS1
MODES FMAX FSHIFT
Examples:
SUPORT6 2 1 3000 123456 0
SUPORT6 3 2
6 0.6 -10.0
SUPORT6 0 3 1 101
SUPORT6 4 3 -2
56 MD Nastran 2006 Release Guide
Field Contents
SID Set ID corresponding to a Case Control SUPORT1 command or zero (Integer, Default
= 0)
0 = if this is the only SUPORT6 entry, use this SUPORT6 entry for all subcases. If
there are multiple SUPORT6 entries, use the one with SID=0 for increment zero.
N = Use this SUPORT6 entry for the subcase specified by Case Control SUPORT1=N
Different SUPORT6 entries can be used for each subcase if desired and different
subcases can use different methods.
If there is only one SUPORT6 entry (with SID=0) no Case Control SUPORT1
commands are necessary.
METH Method to use (Integer, Default = 0)
0 = Inertia relief is not active for this subcase
1 = Use the “Kinematic” method – do not enter continuation line. Input will come
from fields 5-7 of this entry
2 = Use the “Eigenvalue” method – Input data from the 2nd line must is used and fields
5-7 of the primary line must be blank (any SUPORT/SUPORT1 Bulk Data entries are
ignored).
3 = Use the “Support Method”, usually specified using param,inrel,-1 for other
solution sequences (see Remark 3). Do not enter the continuation line. Input will
come from all SUPORT entries and those SUPORT1 entries with ID=SID.
IREMOV Method to retain or remove inertia relief from a previous subcase (Integer, Default =
1)
1 = Retain inertia relief conditions from previous subcase
1 = Remove inertia relief loads immediately
2 = Remove inertia relief loads gradually
IREMOV should be blank or 1 unless METH is 0
GID Reference Grid ID for kinematic method (Integer, Default = 0)
=0 Use the origin
=N Use grid ID N
(Used for METH=1 ONLY)
CDOF Degrees of freedom for which inertia relief loads will be applied (Integer, no Default).
Enter a string of values identifying the degrees of freedom for the model. For 3D
models, usually 123456 is entered. For 2D models two or three degrees of freedom
as applicable may be entered. The limit is 6 degrees of freedom for 3D models (see
Remark 2).
(Used for METH=1 ONLY)
CID Coordinate system flag designating how to apply inertia relief loads (Integer, Default
= 0)
0= Basic coordinate system
N=Apply loads in coordinate system designated by field 7 of the GRID entry for grid
id N.
(Used for METH=1 ONLY)
CHAPTER 2 57
Nonlinear Analysis
Field Contents
IDS1 ID of SUPORT1 entries to be used if METH=3 and SID=0 (Integer, no Default)
For METH=3, only SUPORT1 entries with ID=IDS1 will be used in increment zero.
All SUPORT entries will be used
(Used for METH=3 when SID=0 ONLY)
MODES Number of modes to use in the Eigenvalue method (Integer, no Default)
(Used for METH=2 ONLY)
FMAX Rigid body modes frequency cutoff (Hz) (Real, Default =1.0 Hz)
(Used for METH=2 ONLY)
FSHIFT Shift frequency used in Lanczos eigenvalue extraction (Hz) (Real, Default = -1.0 Hz)
(Used for METH=2 ONLY)
Remarks:
1. The continuation entry is required only if the eigenvalue method (METH=2) is used. Fields 5-7
must be blank if the eigenvalue method is to be used. The continuation option must be omitted
if the kinematic method is to be used. The kinematic method is similar to param,inrel,-2 for other
solution sequences except that the inertia relief loads are updated at each iteration.
2. For the kinematic method, a maximum of 6 degrees of freedom are allowed for 3D structures (2
or 3 dof for 2D structures). You are responsible for knowing how many rigid body modes need
to be “constrained” with inertia relief. For multiple contact bodies which are unsupported at the
beginning of an analysis but eventually contact, there are usually 6 dof per flexible body. This
situation requires the use of the eigenvalue method with MODES set to 6 times the number of
unsupported flexible bodies. If some flexible bodies are supported in some directions but not in
others, the number will be less than 6 per body. It is suggested that a preliminary SOL 103
eigenvalue extraction be performed to assess the number of rigid body modes.
3. The parameter INREL is ignored by SOL 600.
58 MD Nastran 2006 Release Guide
USRSUB6 Defines User Subroutines for SOL 600 - Used in MD Nastran Implicit Nonlinear
- SOL 600 only
Format:
1 2 3 4 5 6 7 8 9 10
USRSUB6 U1 U2 U3 U4 U5 U6 U7 U8
U9 U10
Examples:
USRSUB6 UDAMAG UVOID TENSOF
USRSUB6* SEPFORBBC
Field Contents
Ui Name of user subroutine to be included (Character, no Default) See MSC.Marc
Volume D for list of available User subroutines
Remarks:
1. All user subroutines must reside in the directory where the MD Nastran input file resides.
2. All names must be in lower case and have the extension .f
3. SOL 600 combines all user subroutines into one large subroutine named u600.f and u600.f is
passed to the command line when spawned from MD Nastran.\
Non-Supported Items
Of the remaining non-supported items, the most important are listed below. If your model requires the
use of these items, you should use SOL 106 or 129 instead.
• CGAP is only partially supported and its use with SOL 600 is discouraged
• Most MD Nastran superelements types are not available yet except for external
superelements. SOL 600 may be used to create a superelement and write out a DMIG that may
be used in a subsequent MD Nastran analysis.
• Certain Case Control entries such as STATSUB are not available
CHAPTER 2 59
Nonlinear Analysis
• MSC.Marc 2005 r3 is installed with MD Nastran 2006. Appropriate licenses are needed to use
SOL 600. For most computer systems, installation is automatic. However, for some systems,
particularly IBM AIX systems, the MSC.Marc Installation Manual found in the MSC Combined
Documentation CD should be consulted. For certain IBM AIX systems, the include file in the
tools directory must be changed and the ~/marc2005/lib/lib_extra directory might need to be
renamed to ~/marc2005/lib/lib_shared if a compiler is not available. MSC technical support
personnel can assist with these issues.
• For MD Nastran 2006 it is still recommended that postprocessing be accomplished using the t16
file particularly if contact output or multiple type of stress or strain tensor information is desired.
MSC.Patran and certain other programs can postprocess all t16 data.
60 MD Nastran 2006 Release Guide
Introduction
SOL 700 is the first release of powerful Explicit Nonlinear Solution available in MD Nastran 2006 and
offers unprecedented new technology to analyze transient dynamic events of short duration with severe
geometric and material nonlinearities.
MD Nastran SOL 700 allows users to work within one common modeling environment using the same
Bulk Data interface. The NVH, linear and nonlinear models can be used for explicit applications such as
crash, crush, and drop test, blade out and bird strike simulations. This dramatically reduces the time spent
to build different models for implicit and explicit analysis and prevents the users from making mistakes
because of unfamiliarity between different programs.
MD Nastran SOL 700 is being developed in phases. The first phase, available in MD Nastran 2006 r1 is
intended to solve highly nonlinear transient structural applications such as crash simulations, drop test,
crush and impact problems. Although Phase 1 primarily addresses crash and impact loading, usually
described by initial velocity input, other types of dynamic loading are also supported. Special crash
features such as seat belts and occupant dummies are also supported. Future releases of MD Nastran will
also support fluid structure interaction (FSI) capability and allows users to simulate applications such as
airbags, sloshing and blast problems.
SOL 700 is based on the well-known LS-DYNA solver, which is well integrated inside MD Nastran. The
MD Nastran style of input data is processed within the IFP (Input File Processor) for user input errors
and then filtered and mapped directly to the LS-DYNA memory by means of LS-DYNA style structured
file. There are no translations between Nastran “.bdf” input file to LS-DYNA “.key” input file format.
LS-DYNA then continues with computations to produce output results for highly nonlinear problems.
Native LS-DYNA results files such as d3plot and d3thdt are available for post processing. In the MD
Nastran 2006 r1 release, standard Nastran output such as op2, xdb and punch are not available but may
be supported in future releases.
The MD Nastran input can contain as many subcases as desired; however only one may be selected for
use in any particular SOL 700 analysis. This is done using the Case Control commands, SKIP ON or
OFF, to pick the desired subcase.
dynamics or static analysis, the run time sometimes becomes too large for explicit methods and implicit
analyses need to be employed.
New entries have been added to MD Nastran to make it easier to describe crash and impact. Examples
are the new TICD entry that adds a from-thru-by grid ID description so that initial velocity input can be
described by one line rather than a TIC entry for each grid. This allows an existing input file to be edited
and quickly changed to a crash analysis.
For those familiar with the LS-DYNA material descriptions, about 70 of the most commonly used LS-
DYNA material models are supported in SOL 700. Contact is described using the same style as MD
Nastran Implicit Nonlinear Solution (SOL 600); however, a new entry called “WALL” is added to
facilitate the modeling of rigid and flat barriers commonly used during crash and impact simulations.
During explicit simulations, the structure will usually undergo very large deformations. As elements are
distorted severely, the smallest element dimension will control the simulation timestep and therefore the
runtime.
When the time step for explicit analysis decreases to very small values or reaches zero, the job will hung.
To alleviate the small time step problem, an initial and minimum time step using PARAM*,DYINISTEP
and PARAM*DYMINSTEP should be defined. Default values of 1.0E-6 and 1.0E-9 have been defined
respectively if these parameters are not entered. If different values are desired, you can enter them (both)
in the Bulk Data or in an RC file. RC files do not allow wide-field parameters, therefore if they are to be
entered in an RC file, they must be truncated to 8 characters. For example, param,dyinistep,1.0E-4 and
param,dyminstep,1.0E-8 are both valid entries.
The scripts used to execute the explicit solution were improved for parallel runs when different
computers are involved. It is recommended that only the same type of computers running the same O/S
be used with the exception that different O/S’s may be used in certain cases for Linux systems and
different versions of Windows may be used with PC’s. For such systems, a hostlist needs to be setup with
the format:
Hostname1 #cpus1 workdir1 exe1
Hostname2 #cpus2 workdir2 exe2
Hostname3 #cpus3 workdir3 exe3
etc.
• If exe3 is blank, it is assumed that the exe on node 3 is at the same location as node 1
• workdir(i) is not used but is added for compatibility with SOL 600 and other MSC products. A
dummy entry needs to be made if exe(i) is required
• Multiple CPU runs using a machine with several cpu’s in the same box do not require a hostlist
• See the SOL 700,ID (p. 175) in the MD Nastran Quick Reference Guide for more details
• Two ways of specifying dynamic loads are available using PARAM,DYDYLOAD. The first
method is to translate the loads in MD Nastran. The second method is to pass the loads directly
to the explicit solution which has improved capabilities to handle these loads. A description of
this parameter follows:
PARAM,DYDYLOAD,IFLAG (Integer, Default = 1)
CHAPTER 2 63
Nonlinear Analysis
Determines if MD Nastran dynamic loads are passed directly to the explicit solution or translated by the
internal translator in MD Nastran.
1. Dynamic loads are translated by the internal translator in MD Nastran.
2. Dynamic loads are passed directly to the explicit solution. For this option to work properly, if
loads other than what is listed below are used, the job may fail or obtain the wrong results.
Case Control
DLOAD
LOADSET
LOAD (dynamic relaxation only)
Bulk Data
LSEQ
DLOAD
DELAY
LOAD (dynamic relaxation only)
DAREA
TLOAD1
TABLED1, TABLED2, TABLED3
FORCE
FORCE2
MOMENT
MOMENT2
GRAV
PLOAD
PLOAD4
RFORCE (CID, METHOD, RACC, MB fields are not available)
SPCD
Note:
1. This parameter may be placed in rc files.
Error diagnostics have been improved. You should examine files jid.dytr_prep.d3hsp,
jid.dytr_prep.out and jid.dytr.d3hsp for the string “Error” as well as the standard files jid.f06
(search for FATAL and Severe Warning”) and jid.log (look for anything unusual) should a job
not run to completion.
The following new Bulk Data entries have been added:
• ACCMETR – Define seat belt an accelerometer
• BCGRID – Define grid points to be included as slave body contact entity
64 MD Nastran 2006 Release Guide
• BCSEG – Define grid points which are part of an element to be used in contact analyses
• CBELT – Define a Seatbelt Element
• DYDELEM – Delete failed elements and continue analysis
• DYTERMT – Terminate the job depending on user-specified conditions (such as failed
elements)
• DYRELAX – Dynamic relaxation specifications for restart runs
• DYCHANG – Boundary changes for restart runs
• D2R0000 – Switch standard materials to rigid materials
• D2RINER – Define inertial properties for materials switch to rigid materials
• PBELTD - Define section properties for the seat belt elements
• R2RAUTO – Switch parts to rigid materials
• RBE2F – Define nodal constraint sets for translational motion in global coordinates
• RCONN – Defines a rigid connection between the different parts of Lagrangian meshes
• SBPRET – Defines a seat belt pretensioner
• SBRETR – Defines a seat belt retractorBSENSR – Defines a seat belt sensor
• SBSLPR – Define seat belt slip ring
• SPCD2 – Define an imposed nodal motion on a node or a set of nodes.
The following Bulk Data entries have been changed or additions have been made
• CELAS2D
• PBARL (now available for SOL 700)
• RESTART (new options added)
• DYPST1, DYPST2, DYPST3, DYPST4, DYPST5 (Bulk Data entries for d3plot to op2).
• WALLGEO – Defines a geometric rigid wall
The following SOL 700 parameters have been added or revised:
• CWLDIGNR
• SCALEMASS
• STEPFCT
• DYELPLSY
• DYELPLET
• DYELPLFL
• DYELAS1C
• DYELAS1F
• DYELAS1R
• DYDTOUT
CHAPTER 2 65
Nonlinear Analysis
• DYDYLOAD
• DYPARAM,ELDLTH
• DYPARAM,LSDYNA,BINARY
• DYPARAM,LSDYNA,DB-EXTENT
• DYPARAM,LSDYNA,HOURGLASS
• DYPARAM,LSDYNA,OUTPUT
• DYPARAM,LSDYNA,RELAX
Portions the MD Nastran input file named projtl.dat are shown and discussed below:
+ 0
PARAM,DYDTOUT,5
PARAM*,DYCONSLSFAC,1.0
PARAM,OGEOM,NO
PARAM,AUTOSPC,YES
PARAM,GRDPNT,0
param,dyendtim,1
param,dymats1,1
param,dyldknd,0
$
BCTABLE 1 4
SLAVE 3
+
YES
MASTER 4
$
BCBODY 3 3 DEFORM 3 0
BCBODY 4 3 DEFORM 4 0
$
BCPROP 3 2
BCPROP 4 1
$
$
$ ========== PROPERTY SETS ==========
$
$ * projectile *
$
PSOLID 1 1
$
$ * plate *
$
PSOLID 2 2
$
$
$ ========= MATERIAL DEFINITIONS ==========
$
$
$
$ -------- Material MAT_PLASTIC_KINE.2 id =2
MATD024 1 18.62 1.17 .22 0.0179 0.8
$ -------- Material MAT_PLASTIC_KINE.1 id =1
MATD024 2 7.896 2.1 .284 0.01 0.8
$
$
$
$ ======== Load Cases ========================
$
$
$ ------- Initial Velocity BC ini -----
$
TICD 1 1 1 0.1246 2586 1
TICD 1 1 3 -0.03339 2586 1
.
.
.
ENDDATA
All of the previous input data are described in the MD Nastran Quick Reference Guide and summarized
above. Note that it was only necessary to add BCONTACT=1 to the Case Control, a few new Bulk Data
CHAPTER 2 69
Nonlinear Analysis
parameters and a few contact entries to the Bulk Data to an existing file that would be used in MD
Nastran SOL 101, 106, 109 or 129 analyses.
3 Numerical Enhancements
J
New Iterative Solver Option, 74
J MDACMS Enhancements, 83
J
MPYAD Method 1 Enhancement, 90
J Improved Robustness in the Lanczos Method, 91
J
MLDMP in Solution 111 (Pre-Release), 92
74 MD Nastran 2006 Release Guide
Introduction
Static structural analyses of very large solid element models pose difficult computational challenges for
the solvers available in MD Nastran. For most modeling situations, the sparse direct solver is the solver
of choice because it is usually the most efficient. However, as the number of degrees of freedom grows
ever larger, iterative solution methods become more attractive since they tend to produce results faster
than the direct method. For this reason, both solution techniques are available in MD Nastran.
In order to increase performance even more in the iterative method, the solver offered by Computational
Applications and System Integration, Inc. (CASI) is being introduced into MD Nastran.
Benefits
The introduction of the element-based iterative solver option allows users to run larger jobs faster and
with fewer resources (memory and disk) than could be done before. It is anticipated that most jobs will
run at least twice as fast when the element-based solver option is specified compared to jobs run with any
of the existing MD Nastran iterative solver pre-conditioner choices. For very large jobs, the performance
could be up to ten times better.
r
N1 = --------
b
r
N2 = ------
b
T –1 T –1
N3 = r M r ⁄ b M b
T T
N4 = ( ∆x A∆x ) ⁄ ( x Ax )
Inputs
The SMETHOD Case Control command must be used to select the iterative solver. The SMETHOD
command has been enhanced to allow selection of either the existing matrix-based technique or the new
element-based technique directly, accepting all default options. This is accomplished by specifying
SMETHOD=MATRIX to invoke the existing matrix-based iterative solution technique and
SMETHOD=ELEMENT to invoke the new element-based iterative solution technique. The SMETHOD
command also accepts the specification of an integer value representing the ID of an ITER Bulk Data
entry. In this way, default options can be changed. The PRECOND field of the ITER Bulk Data entry
accepts the keyword “CASI” to indicate that the element-based solver is to be used.
Outputs
There is no new MD Nastran output produced by the element-based iterative solver. The intermediate
convergence parameter output produced by the MSGFLG=YES option of the ITER Bulk Data entry
contains the values of the four convergence norms at each iteration. A summary file is produced by the
element-based iterative solver that contains various statistics about the solution process. The file name
uses the Job ID (jid.PCS), where jid is the name of the input data file.
76 MD Nastran 2006 Release Guide
Demonstration Example
A simple example is presented that demonstrates the use of the element-based iterative solver. The ITER
Case Control command is used to specify the element-based iterative solver. The example problem is
used for demonstration purposes only and is not representative of anything in particular. The model data
consists of a simple solid brick structure subject to an end load.
GRID,126,, 3.125,0.50,0.50
GRID,127,, 4.375,0.50,0.00
GRID,128,, 4.375,0.50,0.50
GRID,129,, 5.625,0.50,0.00
GRID,130,, 5.625,0.50,0.50
GRID,131,, 6.875,0.50,0.00
GRID,132,, 6.875,0.50,0.50
GRID,133,, 8.125,0.50,0.00
GRID,134,, 8.125,0.50,0.50
GRID,135,, 9.375,0.50,0.00
GRID,136,, 9.375,0.50,0.50
GRID,137,, 0.000,0.50,0.25
GRID,138,, 1.250,0.50,0.25
GRID,139,, 2.500,0.50,0.25
GRID,140,, 3.750,0.50,0.25
GRID,141,, 5.000,0.50,0.25
GRID,142,, 6.250,0.50,0.25
GRID,143,, 7.500,0.50,0.25
GRID,144,, 8.750,0.50,0.25
GRID,145,,10.000,0.50,0.25
GRID,146,, 0.625,0.50,0.25
GRID,147,, 1.875,0.50,0.25
GRID,148,, 3.125,0.50,0.25
GRID,149,, 4.375,0.50,0.25
GRID,150,, 5.625,0.50,0.25
GRID,151,, 6.875,0.50,0.25
GRID,152,, 8.125,0.50,0.25
GRID,153,, 9.375,0.50,0.25
CTETRA 1 1 1 4 3 7 137 38
55 105 122 75
CTETRA 2 1 1 4 7 5 137 122
105 73 146 57
CTETRA 3 1 4 7 5 8 122 57
146 76 40 138
CTETRA 4 1 1 2 4 5 37 56
137 73 121 146
CTETRA 5 1 2 4 5 8 56 146
121 106 76 138
CTETRA 6 1 2 8 5 6 106 138
121 74 58 39
CTETRA 7 1 5 8 7 11 138 40
57 107 124 79
CTETRA 8 1 5 8 11 9 138 124
107 77 147 59
CTETRA 9 1 8 11 9 12 124 59
147 80 42 139
CTETRA 10 1 5 6 8 9 39 58
138 77 123 147
CTETRA 11 1 6 8 9 12 58 147
123 108 80 139
CTETRA 12 1 6 12 9 10 108 139
123 78 60 41
CTETRA 13 1 9 12 11 15 139 42
59 109 126 83
CTETRA 14 1 9 12 15 13 139 126
109 81 148 61
CTETRA 15 1 12 15 13 16 126 61
148 84 44 140
CTETRA 16 1 9 10 12 13 41 60
139 81 125 148
80 MD Nastran 2006 Release Guide
CTETRA 17 1 10 12 13 16 60 148
125 110 84 140
CTETRA 18 1 10 16 13 14 110 140
125 82 62 43
CTETRA 19 1 13 16 15 19 140 44
61 111 128 87
CTETRA 20 1 13 16 19 17 140 128
111 85 149 63
CTETRA 21 1 16 19 17 20 128 63
149 88 46 141
CTETRA 22 1 13 14 16 17 43 62
140 85 127 149
CTETRA 23 1 14 16 17 20 62 149
127 112 88 141
CTETRA 24 1 14 20 17 18 112 141
127 86 64 45
CTETRA 25 1 17 20 19 23 141 46
63 113 130 91
CTETRA 26 1 17 20 23 21 141 130
113 89 150 65
CTETRA 27 1 20 23 21 24 130 65
150 92 48 142
CTETRA 28 1 17 18 20 21 45 64
141 89 129 150
CTETRA 29 1 18 20 21 24 64 150
129 114 92 142
CTETRA 30 1 18 24 21 22 114 142
129 90 66 47
CTETRA 31 1 21 24 23 27 142 48
65 115 132 95
CTETRA 32 1 21 24 27 25 142 132
115 93 151 67
CTETRA 33 1 24 27 25 28 132 67
151 96 50 143
CTETRA 34 1 21 22 24 25 47 66
142 93 131 151
CTETRA 35 1 22 24 25 28 66 151
131 116 96 143
CTETRA 36 1 22 28 25 26 116 143
131 94 68 49
CTETRA 37 1 25 28 27 31 143 50
67 117 134 99
CTETRA 38 1 25 28 31 29 143 134
117 97 152 69
CTETRA 39 1 28 31 29 32 134 69
152 100 52 144
CTETRA 40 1 25 26 28 29 49 68
143 97 133 152
CTETRA 41 1 26 28 29 32 68 152
133 118 100 144
CTETRA 42 1 26 32 29 30 118 144
133 98 70 51
CTETRA 43 1 29 32 31 35 144 52
69 119 136 103
CTETRA 44 1 29 32 35 33 144 136
119 101 153 71
CTETRA 45 1 32 35 33 36 136 71
153 104 54 145
CTETRA 46 1 29 30 32 33 51 70
144 101 135 153
CHAPTER 3 81
Numerical Enhancements
CTETRA 47 1 30 32 33 36 70 153
135 120 104 145
CTETRA 48 1 30 36 33 34 120 145
135 102 72 53
PSOLID 1 1 0
MAT1,1,1.0
SPC1,1,456,1,THRU,153
SPC 1 1 123 0.
SPC 1 2 123 0.
SPC 1 3 123 0.
SPC 1 4 123 0.
SPC 1 55 123 0.
SPC 1 56 123 0.
SPC 1 37 123 0.
SPC 1 38 123 0.
SPC 1 137 123 0.
PLOAD4* 1 48 1.000000000E+00 1.000000000E+00*
* 1.000000000E+00 1.000000000E+00 33 30*
* 0 1.000000000E+00 0.000000000E+00 0.000000000E+00*
*
PLOAD4* 1 45 1.000000000E+00 1.000000000E+00*
* 1.000000000E+00 1.000000000E+00 33 32*
* 0 1.000000000E+00 0.000000000E+00 0.000000000E+00*
*
ENDDATA
Example Output
The output generated consists of the usual MD Nastran output as well as an output file generated by the
element-based iterative solver. The contents of this file summarize various statistics about the solution
process. Some of the statistics include the number of terms in the various matrices, number of degrees
of freedom, number of iterations taken and convergence parameter values. The file will have a suffix of
.PCS and appear in the same location as other output files produced by the job. The contents of the .PCS
file for the example problem are shown here for reference.
****************************************************************************
**
(C) Copyright 1992-2004
Computational Applications and System Integration Inc.
All rights Reserved.
****************************************************************************
**
****************************************************************************
**
MDACMS Enhancements
Background
Matrix Domain Automated Component Modal Synthesis (MDACMS) is now the default ACMS
method. The older Geometric Domain approach (GDACMS) remains available but is not the
recommended ACMS method. The PARTOPT keyword on the DOMAINSOLVER Executive System
command is used to choose between the Geometric and Matrix (or DOF) domains: PARTOPT=DOF is
now the default for ACMS.
Summary
The primary goal of development of MD Nastran 2006 MDACMS is to improve performance by
reducing disk I/O and Executive System overhead. Generally, this is achieved by allowing Nastran to
utilize memory more effectively than in the past. In addition, several subDMAPs have been consolidated
into a single new DMAP module.
Specific enhancements to the MDACMS capability include the following:
• The ability to specify key scratch datablocks for Scratch Memory (SMEM) residence via a new
FMS command: MEMLIST.
• Introduction of a new module to perform functions in support of residual vector calculations:
the RESMOD module.
• Enhancements to matrix multiply-and-add (MPYAD module) Method 1.
Specify a list of scratch datablocks that may reside in scratch memory (SMEM).
Format:
MEMLIST DATABLK = (DBname1, DBname2, ..., DBnamei)
Describer Meaning
DBnamei Name of a MD Nastran datablock.
Remarks:
1. Only NDDL and local scratch datablocks may be included in MEMLIST specification.
2. Datablocks specified will reside in SMEM on a first come, first served basis.
3. Datablocks not specified by this command will not reside in SMEM.
4. Database directories for the SCRATCH DBset reside in SMEM and are not affected by any
MEMLIST specification.
5. Continuation lines are allowed.
6. Multiple MEMLIST commands are honored.
7. Scratch I/O activity is reported in the F04 file by including DIAG 42 in the Executive Section.
Example:
MEMLIST DATABLK = (KOO, MOO, KQQ, MQQ)
If generated, datablocks KOO, MOO, KQQ, and MQQ will reside in scratch memory. All other
datablocks will be excluded from scratch memory.
Format:
RESMOD I1,I2,I3,I4,I5/O1,O2,O2,O3,O4,O5/P1/P2/P3/P4/P5/P6 $
Ii: Input data blocks. I1 is required. I2 through I5 may not be necessary depending
on the value of P1.
Parameters:
Remark:
Each option corresponds to a different value of the first parameter, P1, as follows.
‘MPART’ Partitions stiffness, mass, and eigenvector matrices based on mass content
‘LININD’ Find linearly independent and dependent vectors of a matrix
‘LDSWEEP’ Sweeps “modal” loads for load vectors
‘USWEEP’ Sweeps a matrix for small vectors
Option P1 = ‘ATBC’
Performs the matrix multiplication [I1]T[I2][I3] if [I3] is present; [I1]T[I2][I1] otherwise.
Format:
RESMOD I1,I2,I3,,/O1,,,,/’ATBC’ $
O1 Matrix product.
Remark:
[I2] is assumed to be symmetric.
Example:
Compute the product [D] = [A] T [B] [C]
RESMOD A,B,C,,/D,,,,/’ATBC’ $
Option P1 = ‘MPART’
Partitions stiffness, mass, and eigenvector matrices based on mass content.
Format:
RESMOD PHI,K,M,,/PHI0,K0,PHI1,M1,K1/’MPART’////ZROSTIFF/ZROMASS $
Parameters:
Remark:
Only real matrices are supported.
Option P1 = ‘LININD’
Partitions a matrix into linearly independent and dependent sets.
Format:
RESMOD U,M,,,/U0,U1,,,/’LININD’////ZROVEC $
Parameters:
Remarks:
1. M may be purged, in which case the identity matrix is assumed.
2. Output matrices [U0] and [U1] should satisfy the following conditions:
T
[ U0 ] [ M ] [ U0 ] = computational zeros
T
[ U1 ] [ M ] [ U0 ] > 0.0
3. Only real matrices are supported.
Option P1 = ‘LDSWEEP’
Sweeps “modal” loads for load vectors.
Format:
RESMOD LD,PHI,MXX,MQQ,/LDIND,,,,/’LDSWEEP’/NORMFLG $
Parameters:
Remarks:
1. The filtered load vectors are:
T T
[ LDIND ] = [ LD ] – [ M ] [ PHI ] ⋅ INV ( [ PHI ] [ M ] [ PHI ] ) ⋅ [ PHI ] [ LD ]
2. Only real matrices are supported.
CHAPTER 3 89
Numerical Enhancements
Option P1 = ‘USWEEP’
Sweeps a matrix for small vectors.
Format:
RESMOD U,PHI,MXX,MQQ,/UIND,,,,/’USWEEP’/NORMFLG $
U A set of vectors.
PHI Modal vectors.
MXX Mass matrix, physical degrees of freedom.
MQQ Mass matrix, modal degrees of freedom.
Parameters:
Remarks:
1. The filtered vectors are:
T
[ UIND ] = [ U ] – INV ( [ PHI ] [ MQQ ] [ PHI ] ) ⋅ [ MXX ] ⋅ [ U ]
2. Only real matrices are supported.
90 MD Nastran 2006 Release Guide
[ D ] = ±[ A ] [ B ] ±[ C ]
This results in a reduction of the number of operations necessary to complete the matrix multiply.
MPYAD Method 1 Storage 3 is frequently invoked during MDACMS reduction operations.
Example
This example demonstrates the potential impact of these enhancements.
Problem Definition:
• Acoustic Analysis (modal frequency response, SOL 111)
• Over 600,000 grid points; 3.5 million degrees of freedom
• Over 4,000 structure modes up to 600 Hertz; 200 fluid modes
• 12 load cases; over 700 forcing frequencies
Machine Resources
• Linux IA64 with 12Gb main memory
• HP DS2100 3-way striped scratch disk
Version Elap (sec) CPU (sec) Total I/O (gb) HiWater Disk (gb)
MSC.Nastran 2005 r2 12472 10734.3 37.303 1501.81
MD Nastran 2006 9369 8239.3 31.873 684.402
Speedup 24.88% 23.24% 14.56% 54.43%
The MSC.Nastran 2005 r2 run was made with one gigabyte of memory (“mem=1gb”). The MD Nastran
2006 run was made using “mem=8gb smem=7gb”. This resulted in the same Open Core size (1gb) but
with 7gb memory devoted to SMEM. The standard MEMLIST specification found in
SSSALTER:memlist.acms was used for MD Nastran 2006. Finally, both runs utilized serial processing.
CHAPTER 3 91
Numerical Enhancements
User Interface
The MLDMP option may be selected by specifying
DOMAINSOLVER MODES (PARTOPT=DOF)
in the Executive Control Section of the input file, and then using the DMP and NCLUST command line
keywords to specify the number of processors and the number of logical clusters, respectively.
Remember that the number of logical clusters is the same as the number of frequency segments. The
value of DMP should be a multiple of NCLUST. The number of matrix domains will be the quotient
DMP/NCLUST, so it is recommended that values of DMP and NCLUST be chosen so that
DMP/NCLUST is a power of 2.
The upper frequency limit must be specified on the EIGRL bulk data entry, and it is recommended that
a lower frequency limit be specified as well.
Case Study
A 1.3 Mdof body-in-white model was run, computing modes up to 300 Hz (1397 eigenvalues), using a
cluster of 8 IBM P655 servers, each with 8 1.5-GHz POWER4+ processors and 16 GB of physical
memory. Each node had two local, 73GB disks for scratch.
The parallel performance scaled well, achieving nearly a 6-fold improvement when using 16 processors.
6
5
4
Speedup 3
2
1
0
2 4 8 16
Number of Processors
CHAPTER 3 93
Numerical Enhancements
The MLDMP option also reduces the per-processor resource requirements in terms of both memory
required and I/O performed:
2000 250
Megawords
1500 200
processor
I/O per
(GB)
1000 150
100
500
50
0 0
1 2 4 8 16 1 2 4 8 16
Number of Processors Number of Processors
94 MD Nastran 2006 Release Guide
MD Nastran 2006 Release Guide
Ch. :
4 Elements
J
Three-Node Beam Element, 96
J CWSEAM Connector Elements, 105
J
Line Interface Element, 117
J Arbitrary Beam Cross-Section, 126
96 MD Nastran 2006 Release Guide
Introduction
A general three-node beam element has been developed for linear static, modal, dynamic and buckling
analyses. The element has been implemented as a curved one-dimensional Timoshenko beam element so
that both the initial curvatures of beam reference axis and the cross-section shears are included in the
formulation of linear strain-displacement relations. The geometry of beam axis is specified by the offset
vectors from the grid points to the shear centers of the beam cross-sections. The quadratic interpolation
is used for both beam axis and the shape functions. When a three-node beam element degenerates to a
two-node straight beam element, the linear interpolation is adopted. Variable cross-sectional properties
are interpolated quadratically for a three-node and linearly for a degenerate two-node beam element.
Unlike MD Nastran two-node straight beam element (CBEAM), the three-node beam element is
developed based on the displacement method, in which the displacements at nodal points are taken as
primary variables and the variational principle is applied to minimize the total element energy in
formulating element stiffness, consistent mass and differential stiffness matrices.
At each beam element nodal point, there are three translative and three rotational degrees of freedom,
respectively. When the beam cross-section torsional warping effect is considered, another degree of
freedom, which represents the warping variable, is added to the six nodal degrees of freedom at each grid
point. The warping degrees of freedom are represented by either scalar or grid points.
Element-related loads, such as distributed forces and moments, as well as thermal loads, can be applied
on this element. The solution output includes element stresses, strains, forces and moments, element
strain energy and grid point forces.
Benefits
Perhaps the most suitable situation of the application of three-node beam elements is that the element is
used in conjunction with higher-order shell elements, such as TRIA6 and QUAD8 that are used to model
stiffeners. It can also be applied as an alternative to the existing straight two-node beam element in
modeling favorably a structural geometry with initial curvatures.
In addition to normal stresses and strains at beam cross-sections, both shear stresses and strains are also
recovered at cross-sectional stress output points. When warping effect is considered, normal stresses
caused by cross-sectional bi-moments are computed and output accordingly.
Input
Several new Bulk Data entries have been created for three-node beam element connection, property,
distributed thermal and mechanical loads. They are CBEAM3, PBEAM3, TEMPB3 and PLOADB3.
For a detailed description of each entry, please refer to MD Nastran Quick Reference Guide included in
this release.
CHAPTER 4 97
Elements
Locus of Shear
Locus of Shear
Center
Center
ZZeelem
l em Y e le m
Yelem C e beb
C
eet
νν wW cc
AA e
en
n
X e l em
X elem
BB
waWa
GC
GC
GA
GA w
Wb
b
GB
GB
The element coordinate system ( X ele m , Yele m , Zele m ) is established by the orientation vector ν in the same
way as what is defined for CBEAM element, as shown in Figure 4-1.
For a spatial curve, such as the beam reference axis, the natural coordinate system is its Frenet-Serret
frame ( e t, e n, e b ) , as shown in Figure 4-1. Here e t , e n and e b are the unit tangential, normal and bi-normal
vectors, respectively. Tangent vector e t points to the direction from A to B along the beam axis. Vector
en is in the plane defined by these three non-collinear shear centers and points inwardly with respect to
the bending of beam axis. Bi-normal vector is perpendicular to both e t and e n by following the right-
98 MD Nastran 2006 Release Guide
hand rule of e b = e t ⋅ e n . When the beam axis is a straight line, i.e., three sectional shear centers are
collinear, the Frenet-Serret frame is undefined. Then it will be replaced by the element coordinate system.
To formulate finite element equations and define the beam element properties, a local convected
coordinate system ( e x, e y, e z ) is created. The x-axis is always along the beam axis and its convected x
coordinate is measured by the arc-length, s. Its base vector, e x , is taken as same as vector e t . The base
vectors of the local coordinate system, e y and e z , are defined in such a way that they rotate an angle φ
(pre-twist angle), from e n and e b , respectively, in the plane of beam cross-section, as shown in
Figure 4-2. The orthogonal curvilinear coordinate system ( e x, e y, e z ) is introduced here as the local
convected coordinate system, instead of the Frenet-Serret frame, to model the pre-twist of the beam
cross-section. When φ = 0 , the Frenet-Serret frame (or the element coordinate system if the beam axis
is straight) becomes the local convected coordinate system. The angle, φ , may vary along the beam axis.
The pre-twist angles at three beam cross-sections are given in Bulk Data entry, CBEAM3.
eb
eb
e z ez
ey
ey
Shear
Sh ear
Center
en en
C enter
The properties of a three-node beam element listed in Bulk Data entry, PBEAM3, are referred to the local
coordinate system. The output of element stresses, strains and forces is also presented in the local
coordinate system.
in defining cross-sectional properties, such as area moments and product of inertia, and locations of
neutral axis and nonstructural mass center of gravity. Four stress output points on a beam cross-section
are also specified in the local coordinate system. Unlike PBEAM, in which you can specify the
properties at as many as nine intermediate stations, PBEAM3 requires their definitions at only three grid
locations. For a degenerate two-node beam element, those fields related to the mid-grid are ignored.
Values of warping function and its gradients at stress output points are required if torsional warping
stresses are to be recovered.
Shear effectiveness factors may not be zero. Since the element is formulated on the Timoshenko beam
theory and quadratic shape functions are used for interpolation, zero shear effectiveness factors will not
automatically lead to a three-node Euler-Bernoulli beam element.
Limitations
There are some limitations in the current implementation with the three-node beam element. First of all,
it is limited to linear analysis solution sequences only. Heat transfer analysis with the three-node beam
element is not supported. Other limitations are identified as follows.
• X-Y PLOT output
• Random analysis
• PBEAML and PBCOMP related features
• CBEAM related features, such as pin-flags and shear relief
Formulation
Strain-Displacement Relations
The formulation of a three-node beam element is based on Timoshenko beam theory. The kinematical
assumption hereafter is that the displacement vector at an arbitrary point of the beam cross-section is
uniquely defined by the displacement vector at the beam reference axis and the rotations of the cross-
section, superposed by a longitudinal warping displacement. For small deformation theory, the rotation
of the cross-section is a vector. The displacement vector at point (s, y, z) of a beam cross-section is
u ( s, y, z ) = U x e x + U y e y + U z e z
where:
100 MD Nastran 2006 Release Guide
U x ( s, y, z ) = u ( s ) + zθ y ( s ) – yθ z ( s ) + ω ( s )ψ ( y, z )
U y ( s, y, z ) = ν ( s ) – zθ x ( s )
U z ( s, y, z ) = w ( s ) + yθ x ( s )
in which u ( s ) , v ( s ) and w ( s ) are three translative displacement components at the beam axis; θ x ( s ) ,
θy ( s ) and θ z ( s ) are three rotational degrees of freedom of the beam cross-section; and ψ ( y, z ) is a given
warping function and ω ( s ) the warping degree of freedom. The assumption of the warping displacement
is based on the Saint-Venant torsion theory of straight bars.
The Green-Lagrangian normal and shear strains, { ε, γ y, γ z } , are
ε = ε 0 + zχ y – yχ z + ψω s
γ y = γ y 0 – zχ x + ψ y ω
γ z = γ z 0 + yχ x + ψ z ω
where:
ε0 = u , s + κy w – κz v
γ y0 = ν , s – θ z + κ z u – κ x w
γ z0 = w , s + θ y – κ y u + κ x ν
χ x = θ x, s – κ z θ y + κ y θ z
χ y = θ y, s + κ z θ x
χ z = θ z, s – κ y θ x
∂ψ
ψ y = ------- + κ z ψ
∂y
∂ψ
ψ z = ------- – κ y ψ
∂z
in which ( ) , s = ∂ ( ) ⁄ ( ∂s ) , the derivative with regard to the arc-length of beam axis.
Constitutive Relation
The general stress-strain relations are given, including thermal loads, at an arbitrary point of a beam
cross-section, as
σ C 11 C 12 C 13 ε α∆T
{ σ } = τy = C 22 C 23 γ y – 0
τz Sym C 33 γ z 0
CHAPTER 4 101
Elements
where C ij are material elastic constants, α the thermal expansion coefficient and ∆T the variation of
temperature.
Nx = ∫ σdA
A
Vy = ∫ τ y dA
A
Vz = ∫ τ z dA
A
Mx = ∫ ( yτ z – zτ y ) dA
A
My = ∫ σz dA
A
Mz = ∫ ( – yσ ) dA
and the bi-shear force and bi-moment, which are associated with the warping degree of freedom and its
derivative, are
Vb = ∫ ( τ y ψ y + τ z ψ z ) dA
A
Mb = ∫ σψ dA
A
Output
Element forces, moments, stresses and strains, are computed at three beam cross-sections, in the local
coordinate system. These three cross-section locations are related to either three grid points or two Gauss
integration points and the parametrized origin. Both normal and shear stresses and strains are output at
four cross-sectional stress recovery points in the local coordinate system.
The output examples of element forces, stresses and strains are shown in Listing 4-1, Listing 4-2, and
Listing 4-3.
102 MD Nastran 2006 Release Guide
F O R C E S I N B E A M 3 E L E M E N T S ( C B E A M 3 )
- FORCES IN LOCAL COORDINATE SYSTEM -
GRID/ - BENDING MOMENTS - - SHEAR FORCES - AXIAL TOTAL BI-SHEAR BI-MOMENT
ELEMENT-ID GAUSS MY MZ QY QZ FORCE TORQUE FORCE
0 2901
2901 0.0 -1.156075E+03 -2.348231E+01 0.0 1.087807E+02 0.0 0.0 0.0
2902 0.0 -1.125649E+02 -1.096482E+02 0.0 1.902465E+01 0.0 0.0 0.0
2903 0.0 -6.343201E+02 -6.656523E+01 0.0 6.390266E+01 0.0 0.0 0.0
0 3901
3901 0.0 -1.048109E+03 -3.558532E+00 0.0 1.042715E+02 0.0 0.0 0.0
3903 0.0 -7.528904E+02 -7.162810E+01 0.0 7.585925E+01 0.0 0.0 0.0
3904 0.0 -9.004999E+02 -3.759332E+01 0.0 9.006535E+01 0.0 0.0 0.0
0 3902
3903 0.0 -7.267761E+02 -7.611831E+01 0.0 7.135274E+01 0.0 0.0 0.0
3902 0.0 -1.843143E+01 -1.042837E+02 0.0 3.180659E+00 0.0 0.0 0.0
3905 0.0 -3.726037E+02 -9.020099E+01 0.0 3.726670E+01 0.0 0.0
S T R E S S E S I N B E A M 3 E L E M E N T S ( C B E A M 3 )
S T R A I N S I N B E A M 3 E L E M E N T S ( C B E A M 3 )
Example
ID MSC, b3arcbck $ ARCH BUCKLING
SOL 105
TIME 10
CEND
$
TITLE = BUCKLING OF AN ARCH WITH CBEAM3 ELEMENTS
SUBTI = HALF CIRCLE, PRESSURE LOAD
SPC = 10
DISP = ALL
FORCE = ALL
SPCFORCE = ALL
$
SUBCASE 1
LABEL= LOAD CASE
LOAD = 10
SUBCASE 2
LABEL= BUCKLING CASE
METHOD = 10
$
BEGIN BULK
$-------2-------3-------4-------5-------6-------7-------8-------9-------0---
----
EIGRL 10 5
$
PLOADB3 10 1 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 2 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 3 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 4 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 5 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 6 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 7 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 8 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 9 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 10 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 11 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
PLOADB3 10 12 LOCAL 0.0 1.0 0.0 FORCE 1.0 +
+ 100. 100. 100.0
$
CBEAM3 1 1 1 2 21 100
CBEAM3 2 1 2 3 22 100
CBEAM3 3 1 3 4 23 100
CBEAM3 4 1 4 5 24 100
CBEAM3 5 1 5 6 25 100
CBEAM3 6 1 6 7 26 100
CBEAM3 7 1 1 8 31 100
CBEAM3 8 1 8 9 32 100
CBEAM3 9 1 9 10 33 100
104 MD Nastran 2006 Release Guide
CBEAM3 10 1 10 11 34 100
CBEAM3 11 1 11 12 35 100
CBEAM3 12 1 12 13 36 100
$
PBEAM3 1 2 .1 .01 .01 0.0 .02 +
+ 0.5 0.0 0.0 0.5 -0.5 0.0 0.0 -0.5
$
MAT1 2 1.0E+7 0.3 .05 .001 0.0 .01 +MAT1-2
+MAT1-2 1000. 2000. 3000.
$
GRID 2 2.58819 9.659258 0.0
GRID 3 5.0 8.660254 0.0
GRID 4 7.07107 7.07107 0.
GRID 5 8.66025 5.0 0.
GRID 6 9.65926 2.58819 0.
GRID 7 10. 0. 0.
$-------2-------3-------4-------5-------6-------7-------8-------9-------0---
----
GRID 8 -2.588199.659258 0.0
GRID 9 -5.0 8.660254 0.0
GRID 10 -7.071077.07107 0.
GRID 11 -8.660255.0 0.
GRID 12 -9.65926 2.58819 0.
GRID 13 -10. 0.0 0.0
$-------2-------3-------4-------5-------6-------7-------8-------9-------0---
----
GRID* 21 1.30526 9.91445 *
* 0.0
GRID* 22 3.82683 9.2388 *
* 0.0
GRID* 23 6.08761 7.93353 *
* 0.0
GRID* 24 7.93353 6.08761 *
* 0.0
GRID* 25 9.2388 3.82683 *
* 0.0
GRID* 26 9.91445 1.30526 *
* 0.0
GRID* 31 -1.30526 9.91445 *
* 0.0
GRID* 32 -3.82683 9.2388 *
* 0.0
GRID* 33 -6.08761 7.93353 *
* 0.0
GRID* 34 -7.93353 6.08761 *
* 0.0
GRID* 35 -9.2388 3.82683 *
* 0.0
GRID* 36 -9.91445 1.30526 *
* 0.0
$GRID 100 0.0 0.0 0.0
$-------2-------3-------4-------5-------6-------7-------8-------9-------0---
----
SPC1 10 12345 7 13
SPC1 10 123456 100
$
ENDDATA
CHAPTER 4 105
Elements
Introduction
The functionality of connector elements is enhanced by supporting a seam element to connect
two surface patches. To define the seam weld, you must select two surface patches by their
property IDs and specify the width and the thickness of the seam. You also have to specify start
point “GS” and end point “GE” of the seam segment. These two points do not have to lie on or
in between the shell planes. The program will project these two points onto the selected surface
patches to find the connecting shell grids.
Inputs
The seam connection is modeled by the new CWSEAM and PWSEAM Bulk Data entries and
the modified SWLDPRM Bulk Data entry.
Format:
1 2 3 4 5 6 7 8 9 10
CWSEAM EID PID “GRIDID” PIDA PIDB
GS GE
Alternate Format:
1 2 3 4 5 6 7 8 9 10
CWSEAM EID PID “XYZ” PIDA PIDB
XS YS ZS XE YE ZE
Example:
CWSEAM 3 17 GRIDID 2305 7116
30024 65467
106 MD Nastran 2006 Release Guide
Field Contents
EID Element identification number. (0 < Integer < 100,000,000)
PID Property identification number of a PWSEAM entry. (Integer > 0)
LTYPE Connectivity search type. (Character)
If LTYPE=”GRIDID”, location is defined by GS and GE.
If LTYPE=”XYZ”, location is defined by two XYZ locations.
PIDA,PIDB Property identification numbers of PSHELL entries defining surface A and B
respectively. (Integer > 0)
GS, GE Grid ID’s of piercing points on patches A and B of the Start and End of the seam.
(Integer > 0)
XS,YS,ZS Location of the start of the seam in basic coordinate system. (Real or blank)
XE,YE,ZE Location of the end of the seam in basic coordinate system. (Real or blank)
Remarks:
1. Element ID numbers must be unique with respect to all other element ID numbers.
2. GS and GE define the start and end points of the seam element. At these points and using the value
W specified on the PWSEAM entry, surface patches A and B are determined. Points projected
onto the surface patches A and B from GS and GE are used to determine the auxiliary points that
form faces of a CHEXA element. These auxiliary points are then connected to the physical grids
of the patches. The total number of unique physical grids ranges from a possibility of 6 to 32 grids.
The auxiliary points must have a projection on patches A and B, but they do not have to lie on
patch A or B.
3. A maximum of three shell elements of patch A and three shell elements of patch B can be
connected with one CWSEAM element, see Figure 4-3.
S
Figure 4-3 Connected Shell Elements for a CWSEAM Element
CHAPTER 4 107
Elements
Format:
1 2 3 4 5 6 7 8 9 10
PWSEAM PID MID W T
Example:
PWSEAM 7 1 16.
Field Contents
PID Property identification number. (Integer > 0)
MID Material identification number. (Integer > 0)
W Width of the seam. See Remark 1. (Real > 0.)
T Thickness of the seam. See Remark 2. (Real > 0. or blank)
Remarks:
1. The length of the seam is the distance between GS and GE. The width of the seam is measured
perpendicular to the length and lies in the plane of the patches A and B (see Figure 4-4). The width
is also used to find the projection of the seam on the two patches A and B.
GE
GS
Format:
1 2 3 4 5 6 7 8 9 10
SWLDPRM PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3 PARAM4 VAL4
Example:
SWLDPRM GSPROJ 15.0 GSMOVE 2 PRTSW 1
Field Contents
PARAMi Name of the spot weld parameter. Allowable names are listed in Table 4-1.
(Character)
VALi Value of the parameter. (Real or Integer; see Table 4-1.)
CHAPTER 4 109
Elements
Remarks:
1. This entry changes the default settings of control variables for the CFAST, CWELD, and
CWSEAM connector elements. None of the parameters of this entry are required. Only one
SWLDPRM entry is allowed in the Bulk Data Section.
2. Connectivity information is generated for the CFAST and CWSEAM elements. For the CWELD,
connectivity information is only generated for the PARTPAT, ELPAT, ELEMID, and GRIDID
options.
Check the Angle and Find Next Candidate Element for CWELD
and PARTPAT Format
If GSPROJ is greater than zero, MD Nastran will check the angle between SHSA and SHSB while
searching for the projected shell elements. If the angle is greater than GSPROJ, the program will loop
back to find next possible projection pair and check the angle between them again, until the angle of the
new pair is less than GSPROJ or all candidate elements have been checked.
S1 ⁄ E1
S2
E4
SHSA M
SHMA
SHEA
S4
S3 E2
E3
This model is acceptable.
112 MD Nastran 2006 Release Guide
S2 E4
M
S1 ⁄ E1
SHSA
SHEA
S3
SHMA E3
S4
E2
This model fails.
• This shared grid is a shell grid of another two different shell elements.
S3 S2
S4 E4
S1 ⁄ E1
E2 E3
4. If SHSA and SHEA do not share any corner grid, MD Nastran will check if there is an element
(SHMA) lying between SHSA and SHEA. SHMA must share two corner grids with SHSA and
another different one corner grid with SHEA, or vice versa. The following five examples
demonstrate the acceptable and failed cases.
• SHMA shares one edge with SHSA and shares one corner grid with SHEA. This case is
acceptable.
S1 S4
S2 E4
S3 E1
E2 E3
• SHMA shares one edge with SHEA and shares one corner grid with SHSA. This case is
acceptable.
CHAPTER 4 113
Elements
E1 E4
S1 E3
S4 E2
S2 S3
• SHMA shares one corner grid with SHSA and shares another corner grid with SHEA. An
error is detected because the seam spans a cutout.
S1 E4
S4 E1
S2 S3 E2 E3
• SHMA shares one edge with SHSA and shares another edge with SHEA. This case is
acceptable.
S1 S4 E1 E4
S2 S3 E2 E3
• There does not exist a single element that shares an edge or corner grid with SHSA or SHEA.
An error is detected because the length of the seam spans more than three elements.
114 MD Nastran 2006 Release Guide
S1 S4 E1 E4
S2 S3 E2 E3
R E A L E I G E N V A L U E S
MODE EXTRACTION EIGENVALUE RADIANS CYCLES GENERALIZED GENERALIZED
NO. ORDER MASS STIFFNESS
1 1 -3.607717E-05 6.006427E-03 9.559526E-04 1.000000E+00 -3.607717E-05
2 2 2.210966E-05 4.702091E-03 7.483609E-04 1.000000E+00 2.210966E-05
3 3 4.523934E-05 6.726020E-03 1.070479E-03 1.000000E+00 4.523934E-05
4 4 4.937511E-05 7.026743E-03 1.118341E-03 1.000000E+00 4.937511E-05
5 5 1.087932E-04 1.043040E-02 1.660049E-03 1.000000E+00 1.087932E-04
6 6 1.537703E-04 1.240041E-02 1.973587E-03 1.000000E+00 1.537703E-04
7 7 1.154947E+07 3.398451E+03 5.408803E+02 1.000000E+00 1.154947E+07
8 8 1.585229E+07 3.981493E+03 6.336742E+02 1.000000E+00 1.585229E+07
9 9 2.653947E+07 5.151647E+03 8.199102E+02 1.000000E+00 2.653947E+0
10 10 2.959784E+07 5.440389E+03 8.658648E+02 1.000000E+00 2.959784E+07
11 11 3.002028E+07 5.479077E+03 8.720222E+02 1.000000E+00 3.002028E+07
12 12 3.041736E+07 5.515193E+03 8.777703E+02 1.000000E+00 3.041736E+07
13 13 3.328896E+07 5.769658E+03 9.182696E+02 1.000000E+00 3.328896E+07
14 14 3.757468E+07 6.129819E+03 9.755909E+02 1.000000E+00 3.757468E+07
15 15 4.259932E+07 6.526814E+03 1.038775E+03 1.000000E+00 4.259932E+07
16 16 4.738684E+07 6.883810E+03 1.095592E+03 1.000000E+00 4.738684E+07
CHAPTER 4 117
Elements
Introduction
Line interface element is used to connect dissimilar meshes along the edges of finite element mesh
subdomains. These subdomains have boundaries usually associated with either two-dimensional shell
elements or one dimensional beam elements. A set of MPC (Multipoint Constraint) equations are
internally generated with the interface boundary grids to enforce the compatibility of displacements and
rotations across the interface.
There are perhaps three situations in which finite element analysts want to use the interface element
technique to connect two or more independently meshed regions. They are:
• Different groups of engineers work almost independently in building finite element models.
• Global-local modeling is used in the analysis, where a fine mesh is required in a particular area
due to high stress gradients while the rest of area only needs a coarse mesh, in consideration of
the balance of computing resources and the solution accuracy.
• Some regions of a structural model need constant changes or modifications, while the rest of
structure needs little or no change.
The purpose of interface element technology is to provide engineers a simple and useful tool in building
a more flexible finite element model. The interface element technology is not intended to raise the overall
solution accuracy with the existing mesh resolutions of individual subdomains. It is rather how to
preserve the solution accuracy in the regions where the finite element results are more interesting to an
analyst than in others. The method that we have developed for the line interface element is to achieve
primarily the continuity of displacements and rotations across the interface in a way that a measure of
their discontinuity is minimized. Since the smoothness (continuity of derivatives) of displacement
components across the interface is not enforced by this method, some fluctuation of stresses in the
vicinity of the interface could be expected. This stress unevenness or interface effect, however,
diminishes quickly in the area away from the interface. This is a phenomenon that can be explained by
Saint-Venant’s Principle.
When applying an interface element, you are asked to specify a boundary on which all the degrees of
freedom at the grids are taken as the independent. The degrees of freedom associated with the grids on
other boundary or boundaries referenced by the interface element are taken as the dependent and put into
the m-set. In the terminology of contact mechanics, the interface boundaries are categorized as the master
and slave ones. The nodal points on the master boundary are the independent grids and the nodes on the
slave boundary are the dependent grids. An interface element is equivalent to a glued or tied contact that
connects the dissimilar meshes.
The conventional way to specify the dependency or master-slave relationship of the interface boundaries
is that the boundary with a fine mesh is tied to the one with a coarse mesh. In other words, the boundary
with a fine mesh is chosen as a dependent or slave boundary and the one with a coarse mesh as an
independent or master boundary. This practice, however, sometimes introduces a seemingly stiff
connection along the interface. In this case, it may yield better solutions by switching the dependency
relation between the interface boundaries.
118 MD Nastran 2006 Release Guide
The line interface element is intended for linear and non-superelement analyses. It should not be used for
heat transfer analyses at this moment.
User Interface
There are two Bulk Data entries used to define a line interface element. CINTC is the element connection
entry which specifies the connectivity of line interface boundaries, represented by Bulk Data entry,
GMBNDC.
Bulk Data Entry: CINTC
Format:
1 2 3 4 5 6 7 8 9 10
CINTC EID TYPE
LIST=(BID1(INTP1), BID2(INTP2),…, BIDn(INTPn) )
Example:
Field Contents
EID Element identification number. (0<Integer<100,000,000)
TYPE Connectivity. (Character; Default = "GRDLIST”)
If TYPE=”GRDLIST” or blank (default), the user will specify the boundaries
via Bulk Data entry GMBNDC. See Remark 2.
BIDi Boundary curve identification number, referenced to Bulk Data entry
GMBNDC. See Remark 2. (Integer 0)
INTPi Interpolation scheme. (Character; Default=”L”)
INTP=”L”: Linear interpolation;
INTP=”Q”: Quadratic interpolation.
Remarks:
1. Line interface element identification numbers must be unique with respect to all other line
interface elements.
CHAPTER 4 119
Elements
2. There must be at least two BIDi specified. If all BIDi are positive, by default, the degrees of
freedom associated with the grids on the boundary represented by the first BID will be taken as
the independent (n-set), and the degrees of freedom with the grids on the rest of boundaries are
taken as the dependent (m-set). If there is a single negative BID, the degrees of freedom
associated with the grids on the boundary represented by this BID will be taken as the
independent (n-set), and the rest of the degrees of freedom with other boundaries are used as the
dependent (m-set). If there are two or more negative BIDs, the degrees of freedom with the first
negative one will be taken as the independent.
3. Forces of multipoint constraints may be recovered with the MPCFORCE Case Control command.
4. The m-set degrees of freedom specified on the boundary grids by this entry may not be specified
by other entries that define mutually exclusive sets.
Bulk Data Entry: GMBNDC
This is an existing Bulk Data entry originally designed for p-element edges along a curve interface. If it
is referenced by Bulk Data entry CINTC, the value of Field ENTITY must be GRID.
with the interface element. It is designed to handle potentially ill-conditioned matrix [ R m g ] by reassigning
dependent set (m-set) from the existing MPC equations, based on its rank deficiency. It needs further
verifications to see how well the interface element works with AUTOMSET.
GRIDI GRIDF
GRIDF
GRIDI GRIDI=GRID
GRIDI=GRID
Open Boundary
Open Boundary ClosedBoundary
Closed Boundary
Both dependent and independent open boundaries may share either initial or final grids or both of them.
By assigning the same end grid to a pair of boundaries, the you have more flexibility in applying the
interface element when one interface element connects or intersects with another interface element. This
rule, however, may not apply to the closed boundaries.
A pair of interface boundaries can either be matching or non-matching, as shown in Figure 4-8. The non-
matching boundaries have at least one dangling end grid. The interface line integration is taken along the
common arc-length shared by both boundaries. Redundant dangling grids, as shown in Figure 4-9, are
excluded from the processing of interface element.
CHAPTER 4 121
Elements
Matching Boundaries
Matching Boundaries
For an interface element with closed boundaries, special caution must be taken when selecting the initial
grids. Since the initial grid can be any one on a closed boundary, it is required that the two initial grids
on the dependent-independent closed boundaries be as closed as possible, as shown in Figure 4-10. In
other words, a selection of an initial grid being a redundant grid in terms of the other initial grid is not
supported. When one of the boundaries is open, this rule does not apply.
122 MD Nastran 2006 Release Guide
GRIDIA GRIDIA
GRIDIB GRIDIB
When the interface consists of curved boundaries, as shown in Figure 4-11, the interface boundary grids
should be aligned along the actual line of structural geometry. In this release we have not implemented
a capability that enables MD Nastran to check the integrity of interface boundary geometries. The
existence of awry grids in the boundary grid list will lead to some interface malfunction without notice.
CHAPTER 4 123
Elements
CINTC 1001
LIST=( 101, 102 )
GMBNDC 101 67 107
GRID 72 77 82 87 92 97 102
GMBNDC 102 6 66
GRID 12 18 24 30 36 42 48
54 60
124 MD Nastran 2006 Release Guide
Introduction
In MD Nastran, enhancements have been made to ABCS in the area of cross-section outline display,
stress data recovery and design optimization. In addition, ABCS algorithm has become the default
formulation for pre-defined shapes of PBARL/PBEAML.
Benefits
Usually, MD Nastran recovers axial stresses at four ‘extreme’ points of the BAR/BEAM element cross-
section. Although this may be acceptable on typical usage scenario for 1D element, the contribution of
torsion and shear forces are simply assumed to be very minor and ignored. In MD Nastran 2006, for the
first time a venue is provided to perform complete stress recovery for the whole cross-section with torsion
and shear effect included. The stresses recovered can be post-processed as familiar GPSTRESS via
SURFACE for each distinct cross-section. In addition, MD Nastran SOL 200 users can also perform
optimization with the ‘screened’ stresses of BAR/BEAM elements.
Furthermore, an alternative formulation using ABCS logic for PBARL/PBEAML is also offered in MD
Nastran 2006. Previously the equations used for PBARL/PBEAML were constructed under the
assumption that the cross-sections are thin-walled. The properties, especially J, K1, K2, Cwa and Cwb,
computed by such equations may have significant error. With the alternative formulation as default for
PBARL/PBEAML, the correct properties are computed regardless if the section is thin-walled or not.
ABCS enhancements includes the following items
1. Output a PostScript, ‘.ps’, file for displaying the outline of cross-section. Also included in the
‘.ps’ file is the markers of center of gravity and shear center and sectional properties.
2. Generation of nodal and connection bulk data entries of FEM discretization for arbitrary beam
cross-section
3. Stress data recovery for whole cross-section with contribution from torsion and shear included.
In addition, ‘screened’ version of full stress recovery is also available which has the
maximum/minimum direct stresses and max von Mises stress.
4. New RTYPE=ABSTRESS for ‘screened’ stresses can be utilized as constraints in optimization.
5. Alternative formulation for PBARL/PBEAML – selectable via SYSTEM(606), or TWBRBML
on MDLPRM
Inputs
Minimal user input is required to control the new features. For each item of the ABCS enhancements,
its input is discussed in following sections.
CHAPTER 4 127
Elements
PARAM,ARBMPS,YES (default)
The default value for parameter ARBMPS is ‘YES’ which flags the generation of PS file. The PS file
has the name of ‘mydeck.ps’ for an input file of ‘mydeck.dat’. The PS file includes following important
information.
• outline of the cross-section
• marker for the location of center of gravity. For ABCS via PBMSECT, marker for the location
of shear center is also shown.
• Properties of the cross-section
PARAM,ARBMFEM,YES (default)
The default value for parameter ARBMFEM is ‘YES’ which flags the generation of file(s) of FEM of
each distinct cross-section. ‘PARAM,ARBMFEM,NO’ switches off the generation of ‘.bdf’ file for
FEM of cross-section.
Stress recovery for whole cross-section The required input for ABCS logic to perform stress recovery
for whole cross-section is the element force. Hence, to activate stress recovery for whole cross-section,
the following input must be present in the input file.
1. ELFORCE (or simply FORCE) output request in the case control and
2. ‘PARAM,ARBMSS,YES’ (Default=NO) as bulk data entry
Due to the potential of a huge amount of output, these stresses are only available in OUTPUT2 format.
In addition, the stresses recovered are prepared in a pattern consistent with GPSTRESS via SURFACE.
The recovered stresses for each grid of FEM of cross-section are σx, τxy, τzx, principal stresses and von
Mises stress. Note that recovered ABCS direct stresses are placed in stress tensor consistent with direct
stress of SURFACE. The following table shows where recovered direct stresses in stress tensor.
σx σx
σy τxy
σz
τxy τzx
128 MD Nastran 2006 Release Guide
τyz
τzx
As a data reduction process, max/min of σ , τ xy , τzx and max von Mises stress of each station of every
selected element are collected from stress recovery for the whole cross-section and is available in print
file (f06). These collected stresses are called ‘screened’ stresses which can be utilized as design response
for SOL 200 job.
New response type RTYPE=ABSTRESS is available on DRESP1 for using ‘screened’ stresses of
BAR/BEAM elements as design response. An example for the new response type is as follows
DRESP1,23,ABSVM,ABSTRESS,PBMSECT, , 9, , 32
where max von Mises stress (item code 9) of all elements refers to PBMSECT,32 is selected as design
response.
Alternative formulation for PBARL/PBEAML The default formulation is now set to use Finite
Element Method to compute sectional properties. The alternate formulation will be active under the
following conditions
1. GROUP field of PBARL/PBEAML must be either left BLANK or has “MSCBML0” as input
2. job run on a short-word (32 bits) machine
To switch back to the beam library equations, use either ‘NASTRAN twbrbml=1’ in executive control
file or ‘mdlprm,twbrbml,1’ in bulk data.
Output
Post-Script file for the outline of ABCS A ‘.ps’ file for all PBRSECT/PBMSECT of a job will be
available at the conclusion of a job. GhostScript/GSview, available for download at
http://www.cs.wisc.edu/~ghost/, can be utilized for viewing of PostScript file.
Generation of FEM for cross-sections The file generated has the following naming convention
AAA_xxyyy_zz.bdf
where AAA – By default, it assume the input file name. To alter AAA to a name other than input file
name, use
ASSIGN opcase=’any character string’ $
CHAPTER 4 129
Elements
1 BEAM LIBRARY TEST CASE BLO MAY 29, 2005 MSC.NASTRAN 5/27/05 PAGE 10
TRANSVERSE TIP LOAD
0 SUBCASE 1
S T R E S S E S I N B E A M E L E M E N T S ( S C R E E N E D )
AXIAL SHEAR-XY SHEAR-XZ VON MISES
ELEMENT-ID STATION MAX MIN MAX MIN MAX MIN MAX
2 0.000 2.206054E+00 -2.254727E+00 2.075935E-01 -2.175731E-02 1.687584E-01 -1.681947E-01 2.258905E+00
2 1.000 6.117611E-17 -6.315223E-17 2.075935E-01 -2.175731E-02 1.687584E-01 -1.681947E-01 3.694130E-01
New response type, ABSTRESS, for optimization An example of output for ABSTRESS sensitivity
is shown as follows
--------------------------------------------------------------------------------------------------------------------------------
DRESP1 ID= 323 RESPONSE TYPE= ABSTRESS ELEM ID= 2 COMP NO= 9 SEID= 0
SUBCASE RESP VALUE DESIGN VARIABLE COEFFICIENT DESIGN VARIABLE COEFFICIENT
--------------------------------------------------------------------------------------------------------------------------------
1 2.2589E+00 31 DBOXGS 0.0000E+00 232 DBOXCP -2.2693E+00
2 2.0246E+00 31 DBOXGS 0.0000E+00 232 DBOXCP -1.7749E+00
Guidelines
1. Finite element formulation for computing cross-sectional properties is considered more accurate,
especially for thin-walled cross-sections, across wider spectrum of beam cross-sections. Hence,
it is the default formulation for PBARL/PBEAML. However, there is a minor performance
penalty that came with the accuracy.
2. Use only matching ‘.bdf’ and ‘.op2’ files from the same job to visualize the stress pattern,
3. For SOL 200 optimization jobs, finite element formulation for PBARL/PBEAML is highly
recommended due to the potential that new design can cross the thin-/thick-walled line.
Limitations
1. Finite element formulation for arbitrary beam cross-section is available only on short-word
machines. Hence, the alternative formulation for PBARL/PBEAML using finite element method
is supported only on short-word machine. Typically, Cray is a long-word machine and finite
element formulation for arbitrary beam cross-section is not supported.
2. Arbitrary beam cross-section supports constant section for beam elements via PBMSECT. Cross-
sectional variation from end A to end B is not supported via PBMSECT. However, tapered cross-
section is supported via PBEAML even if finite element formulation is utilized.
3. Stress recovery for the full cross-section is available only for Static (SOL 101), Modes (SOL 103)
and Optimization (SOL 200).
4. Stress recovery for the full cross-section is available for the first cycle of a SOL 200 job.
5. For SOL 200 jobs, the stresses recovered can be successfully post-processed with the companion
‘.bdf’ file only if the properties have no discrepancy between analysis and design model.
Example
A simple file, zbm5a1, with two PBMSECT entries is utilized here to demonstrate the features
implemented. Double box cross-section is modeled with PBMSECT,31 using FORM=GS and
PBMSECT,32 using FORM=CP. The overall width of PBMSECT,31 and the thickness of outer wall of
PBMSECT,32 are selected as design variables. Some key bulk data entries are shown as follows
CHAPTER 4 131
Elements
$
$ DBOX section using pbmsect with GS option
POINT 111 0.0 0.0
POINT 112 20.0 0.0
POINT 113 20.0 19.4
POINT 114 0.0 19.4
POINT 125 1.0 1.0
POINT 126 10.0 1.0
POINT 127 10.0 18.4
POINT 128 1.0 18.4
POINT 132 11.0 1.0
POINT 133 19.0 1.0
POINT 134 19.0 18.4
POINT 135 11.0 18.4
$
SET1 111 111 THRU 114
SET1 122 128 127 126 125 128
SET1 133 132 133 134 135
$
pbmsect 31 10 GS
OUTP=111,inp=122,inp=133
DESVAR 31 DBOXGS15.00.0160.0
DVPREL1112pbmsect31 W
31 1.0
$
$ DBOX section using pbmsect with CP option
$
DESVAR 232 DBOXCP 1.00 0.01 3.0
DVPREL1 312 pbmsect 32 T
232 1.0
$
POINT 201 0.5 0.5
POINT 202 10.5 0.5
POINT 203 19.5 0.5
POINT 204 19.5 18.9
POINT 205 10.5 18.9
POINT 206 0.5 18.9
POINT 224 10.5 10.0
SET1 201 201 THRU 206
SET1 202 202 224 205
pbmsect 32 10 CP
OUTP=201,T=1.0,BRP=202,
T(11)=[1.2,PT=(202,224)],T(12)=[1.2,PT=(224,205)]
Zbm5a1 uses default value for PARAM,ARBMPS and PARAM,ARBMFEM. Hence, output files are:
1. zbm5a1.ps – the content is shown in Figure 4-15 and Figure 4-16.
2. zbm5a1_bm31_01.bdf - FEM for PBMSECT,31 shown as Table 4-2
3. zbm5a1_bm32_01.bdf – FEM for PBMSECT,32 shown as Table 4-3.
132 MD Nastran 2006 Release Guide
Note: The GRID and CTRIA6 numbering are based on the processing sequence of the arbitrary
beam cross-section. The first GRID (or CTRIA6) of the first cross-section processed will
have ID of 10001. The first GRID of 2nd cross-section processed has ID of 20001.
The output of stress recovery of whole cross-section is available in OUTPUT2 format. For zbm5a1, the
files are
1. zbm5a1_bm31_01.op2 – stress recovery for all elements referencing PBMSECT,31
2. zbm5a1_bm32_01.op2 – stress recovery for all elements referencing PBMSECT,32
Contour plots with data from zbm5a1_bm31_01.op2 are shown in the following figures. Axial stress,
shear stress in xy, shear stress in zx and von Mises stress are shown in Figure 4-17, Figure 4-18,
Figure 4-19 and Figure 4-20, respectively. In these figures, the number after ‘Grid Point Stresses’ has
XXYY format where
136 MD Nastran 2006 Release Guide
1 BEAM LIBRARY TEST CASE BLO JUNE 16, 2005 MSC.NASTRAN 6/15/05 PAGE 17
TRANSVERSE TIP LOAD
0 SUBCASE 1
S T R E S S E S I N B E A M E L E M E N T S ( S C R E E N E D )
AXIAL SHEAR-XY SHEAR-XZ VON MISES
ELEMENT-ID STATION MAX MIN MAX MIN MAX MIN MAX
2 0.000 2.206054E+00 -2.254727E+00 2.075935E-01 -2.175731E-02 1.687584E-01 -1.681947E-01 2.258905E+00
2 1.000 6.117611E-17 -6.315223E-17 2.075935E-01 -2.175731E-02 1.687584E-01 -1.681947E-01 3.694130E-01
1 BEAM LIBRARY TEST CASE BLO JUNE 16, 2005 MSC.NASTRAN 6/15/05 PAGE 18
LATERAL TIP LOAD
0 SUBCASE 2
S T R E S S E S I N B E A M E L E M E N T S ( S C R E E N E D )
AXIAL SHEAR-XY SHEAR-XZ VON MISES
ELEMENT-ID STATION MAX MIN MAX MIN MAX MIN MAX
2 0.000 2.023472E+00 -2.023472E+00 8.784060E-02 -8.598299E-02 1.045674E-01 -8.338179E-03 2.024639E+00
2 1.000 2.304938E-16 -2.304893E-16 8.784060E-02 -8.598299E-02 1.045674E-01 -8.338179E-03 1.998240E-01
MD Nastran 2006 Release Guide
Ch. :
J
Efficiency Enhancements to MTRXIN Module for Handling DMIG Data, 142
J Enhancements to BSETi/BNDFIXi and CSETi/BNDFREEi Bulk Data Entry
Processing, 143
J
Enhancements to MATMOD Module Option 16, 144
J
Enhancements to External Superelement Usage Via EXTSEOUT Case
Control Command, 149
J
Changes to Rotordynamic for MD Nastran 2006, 153
J Exterior Acoustics, 172
142 MD Nastran 2006 Release Guide
Introduction
Option 16 of the MATMOD module was designed to put a matrix into DMIG format in a MATPOOL-
type data block as well as to optionally generate DMIG punched output. This option is very useful,
particularly in analyses involving part and external superelements. However, its implementation suffers
from several deficiencies and inconveniences as explained below.
1. Only G-size matrices are handled. In particular, if the input matrix is square or symmetric, both
the rows and columns must be of G-size. If it is a rectangular matrix, the rows must be of G-size,
while the columns are regarded as just sequential entities.
2. The rows and columns of the input matrix must be in external sort. This is a particularly
inconvenient requirement since it requires re-arrangement of its rows and columns that are
normally in internal sort. This requirement forces the use of Option 9 of the MATGEN module
to generate a transformation matrix to convert from internal sort to external sort and then
employing this transformation matrix to perform the required transformation of the desired matrix
before it can be used as input to the MATMOD module.
3. The name of the matrix in the DMIG output is the same as the name of the data block containing
the input matrix. There is no way to give an arbitrary name to the matrix in the DMIG output.
4. Even if only the DMIG punched output is desired, the MATPOOL-type output data block still has
to be generated even though it may never be used thereafter.
Major enhancements have been made to Option 16 of the MATMOD module in order to overcome the
above deficiencies and inconveniences. These enhancements utilize an additional input data block and
several additional parameters to accomplish their purpose. These enhancements are explained below.
1. The size of the input matrix is no longer restricted to G-size. Instead, any size corresponding to
any valid displacement set of the User Set (USET) table is allowed. Also, for the first time, Option
16 can handle rectangular matrices wherein the columns correspond to a displacement set and are
not necessarily regarded as sequential entities. This allows Option 16 to handle the more general
case of rectangular matrices wherein the rows and columns correspond to different displacement
sets.
2. The rows and columns of the input matrix need not be in external sort. They can be in internal
sort which is their normal arrangement.
3. The name of the matrix in the DMIG output need not be the same as the name of the data block
containing the input matrix. An arbitrary name can be specified for the matrix in the DMIG
output.
4. The MATPOOL-type output data block need not be generated if only the DMIG punched output
is desired.
CHAPTER 5 145
Dynamics and Superelements
Usage
As indicated earlier, the above enhancements are accomplished by using one additional input data block
and several additional parameters. The new usage of Option 16 is as follows:
MATMOD MATRIX,EQEXIN,USET,,,/MATPOOLX,/16/P2/P3/P4////////
P12/P13/P14/P15 $
Input data block USET and the parameters P3, P13, P14 and P15 represent additions as part of the
enhancements. The default values for these additional parameters have been chosen such that legacy
files employing the old usage of Option 16 will continue to give the same results as before. A full
description of the enhanced Option 16 usage is given in the Appendix.
Example
The power of the enhancements is well illustrated by the example given under the description of Option
16 in the Appendix. This example clearly shows that the enhanced features of Option 16 result in much
simpler and more efficient DMAP programs than was the case in earlier versions.
Format:
MATMOD MATIN,EQEXIN,USET,,,/MATPOOLX,/16/PUNCHFLG/
SORTFLG/TYPOUT////////CONTCHR/DMIGNAME/
ROWSETNM/COLSETNM $
MATPOOLX MATPOOL-type table data block containing MATIN in DMIG format. See
Remark 9.
146 MD Nastran 2006 Release Guide
Parameters:
Remarks:
1. The program checks to ensure that the form of MATIN is either 1 (square), 6 (symmetric) or 2
(rectangular). If this is not so, the program issues a warning message and proceeds without
generating any output from this call to the MATMOD module.
2. If the default value of 0 for SORTFLG is used, the rows of MATIN must be of G-size. If MATIN
is square or symmetric, its columns must also be of G-size. Further, the default value of 0 for
SORTFLG also assumes that the rows and columns of MATIN are in external sort. In order to
accomplish this, it is necessary to first generate a transformation matrix via MATGEN module
Option 9 and then employ this matrix to transform the rows and columns of MATIN from internal
sort to external sort. (This is illustrated in the Example shown below.)
CHAPTER 5 147
Dynamics and Superelements
3. If non-blank continuation characters are specified for CONTCHR, then a maximum of 99,999
DMIG entries can be generated for any single matrix. If this maximum number is exceeded, the
program terminates the job with a fatal error.
4. The program checks to ensure that the number of rows and columns of MATIN correspond to the
displacement sets specified (or implied) by ROWSETNM and COLSETNM. If this condition is
not satisfied, the program issues a warning message and proceeds without generating any output
from this call to the MATMOD module.
5. If the form of MATIN is either 1 (square) or 6 (symmetric), then the IFO field on the generated
DMIG entry is set to 1 or 6. If the form is 2 (rectangular), then IFO is set to 2 if a displacement
set is specified (or implied) for COLSETNM. Otherwise, IFO is set to 9. (If the form is 6, only
the terms in one triangle are output. The MTRXIN module, which converts DMIG data in
MATPOOL-type data blocks into matrices, fills in the other triangle for symmetric matrices.)
6. The rows of the DMIG entry are always labeled with the appropriate grid/scalar IDs and
component numbers. If a displacement set is specified (or implied) for COLSETNM, then the
columns of the DMIG entry are also labeled with the appropriate grid/scalar IDs and component
numbers. Otherwise, the columns of the DMIG entry are labeled sequentially, starting with unity.
7. The EQEXIN input data block may not be purged.
8. The USET input data block may be purged if (a) the default value of 0 is used for SORTFLG or
(b) the displacement set specified (or implied) by ROWSETNM is ‘G’ and the displacement set
specified (or implied) by COLSETNM is either ‘G’ or the columns are just sequential entities.
9. The MATPOOLX output data block may be purged if PUNCHFLG is specified as non-zero and
only the DMIG punched output is desired.
Example:
Generate DMIG punched output for the boundary stiffness matrix KAA, the boundary load matrix PA
and the matrix GMN (representing the MPC/rigid element equations) for an external superelement. The
KAA DMIG entry is to be named KAAEXTSE, the PA DMIG entry is to be named PAEXTSE and the
GMN DMIG entry is to be named GMNEXTSE.
The DMAP shown illustrates the usage of Option 16 using input matrices in internal sort (capability
available in MD Nastran 2006) as well as using input matrices in external sort (usage only possible prior
to MD Nastran). It can be seen that the DMAP for the former case is much simpler and more efficient
than for the latter case.
It should be pointed out here that, if the internal and external sorts are different, the DMIG output
resulting from the two scenarios shown below will “appear” to be different. This is because the matrix
elements will be output in different order, but their values will be the same. The DMIG output from the
two scenarios will yield identical matrices if they are used in turn by the MTRXIN module to re-generate
the matrices.
DMAP using input matrices in internal sort (MD Nastran 2006 and subsequent releases)
TYPE PARM,,I,N,PUNCHFLG=1 $ GENERATE DMIG PUNCHED OUTPUT
148 MD Nastran 2006 Release Guide
MATMOD KAA,EQEXIN,USET,,,/,/16/PUNCHFLG/SORTFLG//////////
’KAAEXTSE’/’A’ $
MATMOD PA,EQEXIN,USET,,,/,/16/PUNCHFLG/SORTFLG//////////
’PAEXTSE’/’A’ $
MATMOD GMN,EQEXIN,USET,,,/,/16/PUNCHFLG/SORTFLG//////////
’GMNEXTSE’/’M’/’N’ $
Introduction
The EXTSEOUT Case Control command allows for the creation of an external superelement (SE) for
subsequent use in an assembly process. In response to many user needs and requirements, several
enhancements have been introduced to this feature in MD Nastran 2006. These enhancements are
described below. Complete details are given in the expanded description of the EXTSEOUT command
in the MD Nastran 2006 Quick Reference Guide.
Thus, with the above usage, we have the following possible values for the ASMBULK keyword:
The above usage often causes confusion when the user is dealing with more than one external SE in an
assembly run. In order to provide more flexibility and convenience to the user, a new keyword called
DMIGSFIX (for DMIG suffix) has been added to the EXTSEOUT Case Control command. The format
of this keyword is
DMIGSFIX = cccccc
where “cccccc” is a suffix (up to six characters) that will be appended to the appropriate letters to give
unique names to the DMIG Bulk Data entries of the boundary matrices. Thus, with this usage, the DMIG
Bulk Data entries for the boundary matrices will have the following names:
CHAPTER 5 151
Dynamics and Superelements
If the name specified for DMIGSFIX is EXTID, it is regarded as a special case. In this case, the ID of
the external SE specified via the EXTID keyword is used as part of the DMIG names. Thus, for example,
if the user has specified EXTID = 15 and DMIGSFIX = EXTID, then the DMIG Bulk Data entries for
the boundary matrices will have the following names:
The above design makes it very convenient for the user to associate the names of the boundary DMIG
matrices with specific external SEs.
RSPINR – Specifies the relative spin rates between rotors for complex eigenvalue, frequency response,
and static analyses.
Format:
1 2 3 4 5 6 7 8 9 10
Field Contents
ROTORID Identification number of rotor. (Integer > 0; Required)
GRIDA/GRIDB Positive rotor spin direction is defined from GRIDA to GRIDB (Integer > 0;
Required. See Remark 2.)
SPDUNIT Specifies whether the listing of relative spin rates is given in terms of RPM
(revolutions/minute) or frequency (revolutions (cycles)/unit time). (Character;
’RPM’ or ’FREQ’; Required)
SPTID Relative spin rate. See Remark 3. (Real or Integer; if integer, must be > 0,
Required)
GR Rotor structural damping factor. See Remark 3. (Real, Default = 0.0)
ALPHAR1 Scale factor applied to the rotor mass matrix for Rayleigh damping (Real, Default
= 0.0. See Remark 5.)
ALPHAR2 Scale factor applied to the rotor stiffness matrix for Rayleigh damping (Real;
Default = 0.0. See Remark 5.)
HYBRID Identification number of HYBDMP entry for hybrid damping (Integer > 0; Default
= 0. See Remark 6.)
154 MD Nastran 2006 Release Guide
Remarks:
1. An RSPINR entry must be present for each rotor defined by a ROTORG entry.
2. The rotor spin axis is determined from the ROTORG entries. The positive rotation vector is from
GRIDA to GRIDB. GRIDA and GRIDB must be specified on the ROTORG entry.
3. If the entry is a real number, the value is considered constant. If the entry is an integer number,
the value references a DDVAL entry that specifies the relative rotor spin rates. The number of
spin rates for each rotor must be the same. Relative spin rates are determined by correlation of
table entries. The ith entry for each rotor specifies the relative spin rates between rotors at
RPMi/FREQi. Spin rates for the reference rotor must be in ascending or descending order.
4. Rotor structural damping specified by the GR entry will be added as equivalent viscous damping.
The equivalent damping will be calculated using:
[ B ro t o r ] s t ru ct u ra l = ------------ [ K r o to r ]
GR
WR3
where WR3 is a user parameter
5. Rayleigh damping for the rotor will be calculated as
[ B ro t o r ] R ay l ei g h = α R1 ( M ro t o r ) + α R2 [ K ro t o r ]
6. For hybrid damping of the rotors, only the rotor mass and stiffness will be used for the modes
calculation.
CHAPTER 5 155
Dynamics and Superelements
RSPINT– Specifies rotor spin rates for nonlinear and direct linear transient analysis.
Format:
1 2 3 4 5 6 7 8 9 10
Field Contents
ROTORID Identification number of rotor. (Integer > 0; Required)
GRIDA/GRIDB Positive rotor spin direction is defined from GRIDA to GRIDB.See Remark 2.
(Integer > 0; Required.)
SPDUNIT Specifies whether the spin rates are given in terms of RPM (revolutions/minute) or
frequency (revolutions(cycles)/unit time). (Character; ’RPM’ or ’FREQ’;
Required)
SPTID Rrotor spin rate. See Remark 3. (Real or Integer; if integer, must be > 0, Required)
SPDOUT EPOINT to output the rotor speed vs. time. Output will be in SPDUNITs (Integer
> 0 or blank)
GR Rotor structural damping factor. See Remark 3. (Real, Default = 0.0)
ALPHAR1 Scale factor applied to the rotor mass matrix for Rayleigh damping (Real,
Default = 0.0. See Remark 5.)
ALPHAR2 Scale factor applied to the rotor stiffness matrix for Rayleigh damping. See
Remark 5. (Real; Default = 0.0.)
HYBRI Identification number of HYBDMP entry for hybrid damping. See Remark 6.
(Integer > 0, Default = 0)
Remarks:
1. A RSPINT entry must be present for each rotor defined by a ROTORG entry.
2. The rotor spin axis is determined from the ROTORG entries. The positive rotation vector is from
GRIDA to GRIDB. GRIDA and GRIDB must be specified on the ROTORG entry.
3. If the entry is a real number, the value is considered constant. If the entry is an integer number,
the value references a TABLED1 entry that specifies the rotor spin rate history.
4. Rotor structural damping specified by the GR entry will be added as equivalent viscous damping.
The equivalent damping will be calculated using:
[ B ro t o r ] s t ru ct u ra l = ------------ [ K r o to r ]
GR
WR3
156 MD Nastran 2006 Release Guide
Format:
1 2 3 4 5 6 7 8 9 10
Field Contents
ID Identification number of HYBDMP entry (Integer > 0; Required)
METHOD Identification number of METHOD entry for modes calculation. (Integer > 0,
Required)
SDAMP Identification number of SDAMP entry for modal damping specification. (Integer > 0;
Required)
KDAMP Selects modal “structural” damping (Character: “Yes” or “NO”, see Remark 1; Default
= “NO”)
Remarks:
1. For KDAMP = “YES”, the viscous modal damping is entered into the complex stiffness matrix
as structural damping.
2. Hybrid damping is generated using modal damping specified by the user on TABDMP entries.
T
b ( ω1 ) φ1
b( ω2 ) T
φ2
BH = φ1 φ2 … φn
b ( ωn ) T
φn
T
g ( ω1 ) φ1
g( ω2) T
φ2
KH = φ1 φ2 … φn
g ( ωn ) T
φn
158 MD Nastran 2006 Release Guide
where
Format:
1 2 3 4 5 6 7 8 9 10
OFFSET1 OFFSET2
Field Contents
SID Nonlinear load set identification number. (Integer > 0, Required)
GA Inner (e.g., damper journal) grid for squeeze film damper. (Integer > 0, Required)
GB Outer (e.g., housing) grid for squeeze film damper. (Integer > 0, Required)
PLANE Radial gap orientation plane: XY, XZ, or ZX. See Remark 1. (Character, Default = XY)
BDIA Inner journal diameter. (Real > 0.0, Required)
BLEN Damper length. (Real > 0.0, Required)
BCLR Damper radial clearance. (Real > 0.0, Required)
SOLN Solution option: LONG or SHORT bearing. (Character, Default = LONG)
VISCO Lubricant viscosity. (Real > 0.0, Required)
PVAPCO Lubricant vapor pressure. (Real, Required)
NPORT Number of lubrication ports: 1 or 2 (Integer, no Default)
CHAPTER 5 159
Dynamics and Superelements
Field Contents
PRES1 Boundary pressure for port 1. (Real > 0.0, Required if NPORT = 1 or 2)
THETA1 Angular position for port 1. (0.0 < Real > 360.0, Required if NPORT = 1 or 2). See
Remark 2.
PRES2 Boundary pressure for port 2. (Real > 0.0, Required if NPORT = 2).
THETA2 Angular position for port 2. See Remark 2. (0.0 < Real < 360.0, Required if NPORT =
2)
NPNT Number of finite difference points for damper arc. (Odd integer < 201, Default = 101)
OFFSET1 Offset in the SFD direction 1. (Real, Default = 0.0)
OFFSET2 Offset in the SFD direction 2. (Real, Default = 0.0)
Remarks:
1. The XY, YZ, and ZX planes are relative to the displacement coordinates of GA and GB. The
plane coordinates correspond to the NLRSFD directions 1 and 2. GA and GB should be
coincident grids with parallel displacement coordinate systems. Wrong answers will be produced
if this rule is not followed.
2. The angular measurement is counterclockwise from the displacement x-axis for the XY plane, the
y-axis for the YZ plane, and the z-axis for the ZX plane.
Format:
1 2 3 4 5 6 7 8 9 10
PBUSH2D
Format:
1 2 3 4 5 6 7 8 9 10
Campbell Diagrams
Campbell diagram generation is activated in complex modes analysis (SOLs 107 and 110) by the
CAMPBELL Case Control command. The command will have the following format:
CAMPBELL= n
The CAMPBELL command references the following Bulk Data entry.
Format:
1 2 3 4 5 6 7 8 9 10
CAMPBLL CID VPARM DDVALID TYPE ID NAME/FID
162 MD Nastran 2006 Release Guide
Field Contents
CID Identification number of entry (integer > 0, required).
VPARM Variable parameter, allowable entries are: ‘SPEED’, ‘PROP’, ‘MAT’.
‘SPEED’, reference rotor speed will be varied (rotordynamic option only).
‘PROP’, element property values will be varied (currently not
implemented)
‘MAT’, element material properties will be varied (currently not
implemented).
DDVALID Identification number of DDVAL entry that specifies the values for the
variable parameter (integer > 0, required).
TYPE For VPARM set to ‘SPEED’ allowable entries are: ‘FREQ’ and ‘RPM’.
For VPARM set to ‘PROP’, allowable entries are the names of property
entries, such as ‘PBAR’, ‘PELAS’, etc.
For VPARM set to ‘MAT’, allowable entries are the names of material
entries, such as ‘MAT1’ or ‘MAT2’, etc.
ID Property or material entry identification number (integer > 0, not required
for VPARM set to ‘SPEED’, required for VPARM set to ‘PROP’ or
‘MAT’).
NAME/FID For VPARM set to ‘SPEED’, no entry required.
For VPARM set to ‘PROP’, property name, such as ‘T’, ‘A’, or field
position of the property entry, or word position in the element property
table of the analysis model.
For VPARM set to ‘MAT’, material property name, such as ‘E’ or ‘RHO’,
or field position of the material entry.
1 1
{ φ } f o rw a rd = – i { φ } b ac kw a rd = i (5-1)
0 0
CHAPTER 5 163
Dynamics and Superelements
The forward and backward components are found by minimizing the error between the calculated modes
and the ‘pure’ forward and backward whirl vectors of the reference rotor.
{ err } = { φ } – [ A ] { α } (5-2)
[ A ] = [ [ A ] f o rw a rd [ A ] b ac k wa rd ] (5-3)
{ φ } f o rw a rd 0 0
{ φ } 0
0 f o rw ar d
0 0 .
[ A ] f o r wa rd = (5-4)
. . .
.
. .
. . { φ } f o rwa rd
{ φ } b a ck wa r d 0 0
{ φ } 0
0 ba c kw a rd
0 0 .
[ A ] b ac kw a rd = (5-5)
. . .
.
. .
. . { φ } b a ck wa rd
α f o rw ar d
{α} = (5-6)
α b a ck w ar d
The error is minimized using a least-mean-square procedure. The square of the error is:
2 * T * * * T T
{ err } = { err } { err } = ( { φ } – [ A ] { α } ) ( { φ } – [ A ] { α } )
(5-7)
* T * T * T * T * T * T
= {φ } { φ} – { φ } [ A ]{ α} – { α } [ A ] {φ } + { α } [ A ] [ A ]{ α }
2
∂err * * T * T
-------------- = – { φ } [ A ] + { α } [ A ] [ A ] (5-8)
∂α
Setting the above equation to zero and taking the complex transpose results in
* T * T
– [A ] {φ} + [A ] [A]{α} = {0 } (5-9)
* T –1 * T
{α} = ([A ] [A]) [A ] {φ} (5-10)
Using Eq. (5-1) and Eq. (5-3), the following simplification can be made,
{ α } = --- [ A ] { φ }
1 * T
(5-11)
2
The { α } terms are used to calculate the forward and backward components of the modes,
{ φ r ot o r } f or wa rd = --- [ A ] f o rw a rd ( [ A ] f o rw a rd { φ } )
1 * T
2
(5-12)
{ φ ro t o r } b a ck wa rd = --- [ A ] ba c kw ar d ( [ A ] b a ck wa rd { φ } )
1 * T
2
The proportional rotor kinetic and strain energies are determined using the following procedure:
norm KE ( φ r ot o r )
Proportional Kinetic Energy = ----------------------------------------------- (5-13)
norm KE ( φ )
norm SE ( φ ro t o r )
Proportional Strain Energy = ---------------------------------------------- (5-14)
norm SE ( φ )
where:
KE ( u ) = ( [ M ] { u } ) ⋅ { u } (5-15)
SE ( u ) = ( [ K ] { u } ) ⋅ { u } (5-16)
and the norm of the vector is defined as the sum of the absolute values of all the terms.
Note that scale factors in the above equations have been removed because the proportional calculation
will cancel these terms.
Modes with kinetic or strain energies greater than a user specified value will be considered forward or
backward whirl modes.
CHAPTER 5 165
Dynamics and Superelements
[ err ] = [ X ] [ φ ] i – 1 – [ X ] [ φ ] i [ β ] (5-17)
[ φ ] are the normalized forward and backward whirl modes (rotor dofs only)
{ φ}
{ φ } = -------------------------------------------------
- (5-18)
* T * T
{φ } [ X ] [ X ]{ φ}
Using the same method in the above procedure produces the following results for the scaling matrix
* T * T T * T * T
[ β ] = ( [ φ ] i [ X ] [ X ] [ φ ] i ) ( [ φ ]i [ X ] [ X ] [ φ ] i – 1 ) . (5-19)
The [ β ] matrix is used to whether the modes have shifted position in the LAMA table.
The [ β ] matrix columns are examined for the largest term. This term is set to 1.0 and the other terms
in the column are set to 0.0. The [ β ] matrix can now be used to shuffle the eigenvalues.
The new order is appended to the LAMA matrix for Campbell Diagram plotting.
Comments
For speed-dependent Campbell diagrams, at low speeds, the split into forward and backward modes may
not be very pronounced. It may be best to start at the higher speeds and move down instead of moving
up. Also, do not try to find forward and backward modes at zero RPM.
When forward and backward modes cross, they may be difficult to separate. If this happens, it is
probably best to ‘jump’ (ignore) these modes and continue to the next rotor speed. They should be
picked-up at the next speed step. We will need to ‘fill-in’ later so PATRAN can plot the results.
166 MD Nastran 2006 Release Guide
( B + α1 M + α2K ) + -------
g
- K + -------- K4 s
1
s s s W3 s W4
Mu·· ( t ) + u· ( t )
g
+ ( B + BH + α1 M + α2 K ) + ------------ R
K R + ------------ K4 R + -------------- KH R + ΩB
1 1 G
R R R R R R WR 3 WR4 WRH
Ks + K r
+ g r C K 1 C K 4 1 C K H u ( t ) = F ( t )
+ Ω K C B + K C BH + α1 K C M + α2 K C K + ------------ + ------------ K + -------------- K
R R WR3 K WR4 WRH
(5-22)
-------
g
= support viscous damping equivalent to structural damping
W3- K s
-------
1
= support viscous damping equivalent to material structural damping
W4- K4 s
------------
1
= rotor viscous damping equivalent to material structural damping
WR4 K4 R
-------------
1
= rotor viscous damping equivalent to hybrid structural damping
WRH-
KH R
G
B = gyroscopic force matrix
Ks = support stiffness matrix
KR = rotor stiffness matrix
K4 s = support material damping matrix
K4 R = rotor material damping matrix
CHAPTER 5 167
Dynamics and Superelements
CK 4
KR = “circulation” matrix due to K4 R
CK H
K = “circulation” matrix due to KH R
WR3 , WR4 , and WRH are users parameters
2 G B S + α1M S + α2K S + B R + BH R + α1 R M R + α2 R K R
– Ω ( M – iB ) + iΩ CB CB H CM CK
–i( K + K + α1 R K + α2 R K )
(5-24)
( 1 + ig )K S + iK4 S
+ CK C K4 C KH
u(Ω) = F(Ω)
+ ( 1 + ig R )K R + iK4 R + iKH R + g R K +K +K
Eq. (5-23), asynchronous excitation, and Eq. (5-24), synchronous excitation, are used in frequency
response and complex modes analyses.
To order to support multiple rotors spinning at different rates, Eqs. (5-23) and (5-24) are modified to the
following forms:
Frequency Response
For frequency response with asynchronous excitation, Ω for each rotor is constant and can be
determined from the rotation speed of the reference rotor, Ω ref , and relative rotation rates specified by
the user. The equation of motion to be solved is:
168 MD Nastran 2006 Release Guide
B S + α1M S + α2K S
– ω2 M + i ω n
+ G
∑ Rj
B + BH Rj + α1 M
Rj R j + α2 K
Rj Rj + Ω j ( Ω re f )B j
j=1
(5-25)
( 1 + ig )K S + i K4 S
n ( 1 + ig R j )K Rj + iK 4 Rj + iKH Rj
+ u(ω) = F(ω)
+
∑ CB C BH gR j C K 1 C K 4 1 C K H
+ α1 Rj K j + α2 R j K j + ------- K j + ---- K j
CM CK
j = 1 + Ω j ( Ω ref ) K j + K j ω ω
+ ---- K j
ω
For the option to bypass the frequency-dependent looping, the equation of motion to be solved is:
B S + α1M S + α2K S +
– ω2 M + i ω n gR j
B + BH + α1 M + α2 K + Ω ( Ω )B G + ----------- ------------
1 -------------
1
∑ Rj - K + -
K4 + KH Rj
Rj Rj Rj R j Rj j ref j WR3 Rj WR4 Rj WRH
j = 1
( 1 + ig )K S + i K4 S (5-26)
+
n
+ ∑ K R j + ( Ω j ( Ω ref ) )
j=1
g Rj C K 1 C K 4 1 C K H
K C B + K C BH + α1 K C M + α2 K C K + ------------ K + ------------ K j + -------------- K R j u(ω) = F(ω)
j j Rj Rj j
where the subscript j references the individual rotors.
For frequency response with synchronous excitation, the excitation frequency is equal to the spin rate
of the reference rotor, ω = Ω ref . The spin rates of the additional rotors can be determined from the
relative spin rates specified by the user. The equation of motion to be solved is:
B S + α1M S + α2 K S
– Ω 2 M + iΩ n
ref ref G
+ ∑ B R j + BH Rj + α1 R j M R j + α2 R j K R j + Ω j ( Ω re f )B j
j=1
( 1 + i g )K S + iK 4 S
n
(5-27)
( 1 + i g j )K Rj + iK 4 Rj + iKH Rj
+
+
∑
+ Ω j Ω re f
j=1
CB C BH CM CK g R j C K 1 C K 4 1 C K H
K j + Kj + α1 Rj K j + α2 R j K j + ------------ K j + ---------- K j + ---------- K j u ( Ω ref ) = F ( Ωref )
Ω re f Ω ref Ω ref
For the option to bypass the frequency-dependent lookup of rotor speeds, Ω for each rotor is written as
a linear function dependent on the reference rotor spin rate ( Ω j ( Ω ref ) = α j + βj Ω re f ) . The scaling factors,
α j and β j , are determined from the relative spin rates specified by the user. The Ω ref in the 1 ⁄ Ω re f terms
are replaced by the values of user parameters WR3, WR4, and WRH. The equation of motion to be
solved is:
n
–Ω2 M – i
∑ β j Bj
G
ref
j = 1
n
+ iΩ re f B S + α1M S + α2K S + ∑
j= 1
g Rj K + ------------
1
K4 Rj + -------------- KH R j
G 1
B R j + BH Rj + α1 R j M R j + α2 R j K R j + α j B j + ------------
WR 3 R j WR4 WRH
(5-28)
g R j C K 1 C K 4 1 C K H
– iβ K C B + K C B H + α1 K C M + α2 K C K + ------------ K + ------------ K + -------------- K
j j j Rj j Rj j WR3 j WR 4 j WRH j
( 1 + ig )K S + i K4 S +
+
n
∑ KR j
+ αj
j = 1
g Rj C K 1 C K 4 1 C K H
K C B + K C BH + α1 K C M + α2 K C K + ------------ + ------------ K j + -------------- K j u ( Ω ref ) = F ( Ω ref )
j j Rj j Rj j WR3 K j WR4 WRH
Complex Modes
For complex modes with asynchronous excitation, the spin rate Ω for each rotor is constant and can
be determined from user input and the reference rotor spin rate, Ω ref . The equation of motion to be
solved is:
170 MD Nastran 2006 Release Guide
B S + α1M S + α2K S +
– ω2 M + i ω n
∑
j = 1
g Rj
B + BH + α1 M + α2 K + Ω ( Ω )B G + ------------ K + ------------ K4 + -------------- KH R j
1 1
Rj Rj Rj Rj Rj R j j re f j WR3 R j WR4 R j WRH
(5-29)
1 + ig K S + iK 4 S +
+
n
+ ∑
j=1
g R j C K 1 C K4 1 C K H
K + Ω ( Ω ) K C B + K C B H + α1 K C M + α2 K C K + ----------- u(ω) = 0
WR3- j
K + ------------ K j + -------------- K j
Rj j ref j j Rj Rj WR 4 WRH
n
–Ω 2 M – i
∑ βj Bj
G
ref
j= 1
n
g Rj K + -----------
1
- K4 + -------------- KH R j
G 1
B Rj + BH Rj + α1 Rj M R j + α2 R j K R j + α j B j + ------------
WR 3 R j WR4 R j WRH
(5-30)
g R j C K 1 C K 4 1 C K H
– i β K C B + K C B H + α1 K C M + α2 K C K + -----------
WR3- j
K + ------------ K j + -------------- K j
j j j Rj j Rj j WR4 WRH
( 1 + ig )K S + i K4 S +
+
n
∑ K Rj + α j
j = 1
g R j C K 1 C K 4 1 C K H
K C B + K C B H + α 1 K C M + α2 K C K + ------------
j j Rj j Rj j ------------ K
WR 3 K j + WR4 j + -------------- K j u ( Ω ref ) = 0
WRH
B + B + α 1M + α2K + -------
g 1 - K4
s Rj s s W3- K s + -------
W4 s
Mu·· ( t ) + n u· ( t )
------------ K + ------------ K4 + -------------- KH + Ω ( t )B
g 1 1
∑ Rj
R G
+ B + BH Rj + α1 M
Rj Rj + α2 K
Rj R j + WR3 R WR4 Rj WRH Rj j j
j=1
·
n K + Ω j ( t )K T
Rj j
+ KS + ∑ g r C K 1 C K 4 1 C K H
+ Ω ( t ) K C B + K C BH + α1 K C M + α2 K C K + ------------
j= 1 j j j Rj j R j j WR3 K j + -----------
WR4
- K j + -------------
WRH
- K j
u(t) = F(t)
(5-31)
172 MD Nastran 2006 Release Guide
Exterior Acoustics
Introduction
Nastran has been used to analyse interior acoustic problems for a long time. With interior acoustic
problems, the acoustic domain considered is bounded. A typical example is the determination of the
sound pressure inside a car.
With exterior acoustic problems, the acoustic domain is unbounded. The analysis studies the sound
pressure in the vicinity of the vibrating body or far away from the body. A further important result is the
acoustic power radiated from the vibrating structure. A typical example is the determination of the
radiated acoustic power of an engine.
In MD Nastran 2006 the infinite elements from MSC.Actran have been integrated to allow the analysis
of exterior acoustic problems. The infinite elements are attached to the boundary of the acoustic finite
element mesh to provide the correct non-reflecting boundary condition. This is a prerelease and should
be used for production work with care.
Apart from standard acoustic results within the finite region it is possible to compute acoustic results at
points within the infinite elements. These points, the so-called field points, may be connected by elements
to form a field point mesh. If a field point mesh is defined, also the acoustic power through this field point
mesh is computed.
Benefits
The integration of the proven and tested infinite elements from MSC.Actran into MD Nastran largely
facilitates the analysis of exterior acoustic problems. It is no longer necessary to transfer data between
different programs but the analysis can be done completely within MD Nastran.
Input
New Bulk Data entries, CACINF3 and CACINF4, are used to define the connectivity of the infinite
elements. The properties of the infinite elements are defined on PACINF Bulk Data entries.
Field points and field point meshes are defined in separate sections of the bulk data file. These sections
must follow the main bulk data section.
Output of radiated power from the wetted surface and intensities on the wetted surface is controlled by
Case Control commands ACPOWER and INTENSITY. Output of field point mesh results is controlled
by Case Control command ACFPMRESULT.
geometry of the base is defined by its connectivity and the location of the corner grids. In order to avoid
overlapping of the infinite elements, the surface they are attached to must be convex. However, it is not
necessary that this surface is smooth.
Within an infinite element, the acoustic pressure is expanded into a power series of (1/r) where r is the
distance from the pole.The radial interpolation order is the number of terms kept in this series.
The connectivity of the base is defined on the CACINF3 and CACINF4 Bulk Data entries. The
orientation should be such that the normal vector on the base points into radial direction. However, MD
Nastran will automatically change the orientation if the normal vector does not point away from the pole.
The location of the pole as well as the radial interpolation order are defined on PACINF Bulk Data
entries.
174 MD Nastran 2006 Release Guide
Format:
1 2 3 4 5 6 7 8 9 10
CACINF3 EID PID G1 G2 G3
Field Contents
EID Element Identification Number (Integer > 0)
PID Property Identification Number of a PACINF entry (Integer > 0)
Gi Grid Point Identification Numbers of Element Base Connection Points (Integer > 0)
Format:
1 2 3 4 5 6 7 8 9 10
CACINF4 EID PID G1 G2 G3 G4
Field Contents
EID Element Identification Number (Integer > 0)
PID Property Identification Number of a PACINF entry (Integer > 0)
Gi Grid Point Identification Numbers of Element Base Connection Points (Integer > 0)
Format:
1 2 3 4 5 6 7 8 9 10
PACINF PID MID RIO X1 X2 X3
Field Contents
PID Property Identification Number of PACINF entry (Integer > 0)
MID Material Identification Number of a MAT10 entry (Integer > 0)
XP, YP, ZP Coordinates of the Pole of the Infinite Elements (in the Basic Coordinate System)
Example
BEGIN AFPM=100
$
PARAM, POST, -1
$
$ Isolated Field Points along a Line
$
GRID 1001 2 5. 0. 0.
GRID 1002 2 6. 0. 0.
GRID 1003 2 7. 0. 0.
GRID 1004 2 8. 0. 0.
176 MD Nastran 2006 Release Guide
GRID 1005 2 9. 0. 0.
GRID 1006 2 10. 0. 0.
CORD2R, 2,, 0., 0., 0., -.5, -.5, .707107
, .5, .5, .707107
$
BEGIN AFPM = 200
$
PARAM, POST, -1
$
GRID, 1,, -1., -1., 2.
GRID, 2,, 0., -1., 2.
GRID, 3,, 1., -1., 2.
GRID, 4,, -1., 0., 2.
GRID, 5,, 0., 0., 2.
GRID, 6,, 1., 0., 2.
GRID, 7,, -1., 1., 2.
GRID, 8,, 0., 1., 2.
GRID, 9,, 1., 1., 2.
$
GRID, 11,, -1., -1., 2.
GRID, 12,, 0., -1., 3.
GRID, 13,, 1., -1., 2.
GRID, 14,, -1., 0., 3.
GRID, 16,, 1., 0., 3.
GRID, 17,, -1., 1., 2.
GRID, 18,, 0., 1., 3.
GRID, 19,, 1., 1., 2.
$
CQUAD4, 1, 1, 1, 2, 5, 4
CQUAD4, 2, 1, 2, 3, 6, 5
CQUAD4, 3, 1, 4, 5, 8, 7
CQUAD4, 4, 1, 5, 6, 9, 8
$
CQUAD4, 5, 1, 12, 16, 18, 14
CTRIA3, 6, 1, 11, 12, 14
CTRIA3, 7, 1, 12, 13, 16
CTRIA3, 8, 1, 16, 19, 18
CTRIA3, 9, 1, 14, 18, 17
$
ENDDATA
Format:
ALL
ACPOWER SORT1 , PRINT,PUNCH , [ CSV = unit ] = n
SORT2 PLOT
NONE
Describer Meaning
SORT1 Output will be presented as tabular listing of panels for each excitation frequency
SORT2 Output will be presented as tabular listing of excitation frequencies for each panel
(Default)
PRINT The printer will be the output medium (Default).
PUNCH The punch file will be the output medium.
PLOT Results are generated but not output.
CSV Results will be written to a .csv file.
unit Unit of the .csv file as used on the ASSIGN statement
ALL Radiated power will be processed for the wetted surface and all panels.
n Set identification of a previously defined set of panels. Radiated power will be
processed for the wetted surface and all panels in the referenced set.
NONE Radiated power will not be processed.
Format:
ALL
INTENSITY SORT1 , PRINT,PUNCH = n
SORT2 PLOT
NONE
178 MD Nastran 2006 Release Guide
Describer Meaning
SORT1 Output will be presented as tabular listing of grid points for each excitation
frequency (Default)
SORT2 Output will be presented as tabular listing of excitation frequencies for each grid
point
PRINT The printer will be the output medium (Default).
PUNCH The punch file will be the output medium.
PLOT Results are generated but not output.
ALL Intensities will be computed for all grid points of the wetted surface.
n Set identification of a previously defined set of grid points. Intensities will be
computed for the grid points in this set only.
NONE Acoustic intensities will not be processed.
Format:
ACFPMRESULT SORT1 , PRINT,PUNCH , VELOCITY = YES
SORT2 PLOT NO
ALL
REAL or IMAG , POWER = YES
= n
PHASE NO
NONE
Describer Meaning
SORT1 Output will be presented as tabular listing of grid points for each excitation
frequency (Default)
SORT2 Output will be presented as tabular listing of excitation frequencies for each grid
point
PRINT The printer will be the output medium (Default).
CHAPTER 5 179
Dynamics and Superelements
Describer Meaning
PUNCH The punch file will be the output medium.
PLOT Results are generated but not output.
VELOCITY Requests output of particle velocities (Default: NO)
REAL or IMAG Requests rectangular format (real and imaginary) of complex output. Use of either
REAL of IMAG yields the same output.
PHASE Requests polar format (magnitude and phase) of complex output. Phase output is in
degrees.
POWER Requests output of power through field point mesh (Default: YES)
ALL Results of all field point meshes will be processed
n Set identification of a previously defined set of field point mesh identifiers. Results
will be processed for the field point meshes in this set only.
NONE Field point mesh results will not be processed.
Output
In addition to the standard acoustic results, the following results may be requested:
• Acoustic energy radiated from the wetted surface or from panels
• Normal component of the acoustic intensity at grid points of the wetted surface
• Acoustic pressure and intensity at the field points
• Acoustic velocity at the field points
• Acoustic energy flowing through the field point mesh
Field point mesh results can be written to the .f06 file or the .op2 file. The .xdb file is not yet supported.
Guidelines
1. The surface the infinite elements are attached to must be convex but it need not be smooth.
Infinite elements have to be connected to acoustic grid points. Thus it is necessary to model the
vicinity of the vibrating structure with acoustic finite elements until a convex surface is reached.
2. The radial interpolation order required depends on the directivity of the pressure field. Usually, a
higher order is needed for higher frequencies.
3. It is recommended to study the sensitivity of the results with respect to the radial interpolation
order by repeating the analysis with a different radial interpolation order.
4. Infinite elements are supported in direct and modal frequency response analysis (SOL 108 and
SOL 111). Experience shows that a large number of fluid modes is needed to get converged
results. Thus, modal reduction of the fluid is not recommended. However, modal reduction can
be applied to the structure.
180 MD Nastran 2006 Release Guide
5. Efficiency can be increased if the iterative solver is used. It is recommended to use the Jacobi
preconditionner with an epsilon of 10-4.
Limitations
1. Infinite elements are supported in a frequency response analysis only (SOL 108 and SOL 111).
2. In this prerelease, case control commands ACPOWER and INTENSITY are not yet supported.
Example
In this example, the sound transmission through an elastic plate embedded in an infinite rigid wall is
analysed. Figure 5-2 shows the geometry of the plate and of the fluid region meshed with finite elements.
The finite element mesh of the structure and of one quarter of the fluid can be seen in Figure 5-3.
Infinite Elements are attached to the top and the four lateral faces but not to the bottom. The pole of all
infinite elements is at the center of the plate. The finite element mesh of the structure together with one
quarter of the infinite element mesh is shown in Figure 5-4.
The field point mesh is a cube which completely encloses the fluid mesh. Thus, the power through this
field point mesh equals the total power radiated from the plate. Figure 5-5 shows the fluid mesh and one
quarter of the field point mesh.
CHAPTER 5 181
Dynamics and Superelements
The excitation is a uniform pressure applied to the plate. The acoustic pressure in the finite element mesh
and acoustic results at some discrete field points located along the z-axis and at the field points of the
field point mesh are computed. Acoustic results at the field points include the acoustic pressure and the
acoustic intensities.
Input File
SOL 108
CEND
TITLE = Vibrating Plate Example
SUBTITLE = Direct Frequency Response
$
ECHO = SORT(EXCEPT, GRID, CHEXA, CQUAD4, CACINF4)
$
DLOAD = 10
FREQ = 20
SMETHOD = 30
SPC = 1
$
DISP(PLOT) = ALL
ACFPMRESULT(PHAS) = ALL
$
BEGIN BULK
$
PARAM, POST, -1
$
ACMODL, IDENT
CHAPTER 5 183
Dynamics and Superelements
$
RLOAD1, 10, 200,,, 300
PLOAD2, 200, 1., 1, THRU, 150
TABLED1, 300
, 0., 1., 1000., 1., ENDT
$
FREQ, 20, 10.
$
ITER, 30
PRECOND = J,
ITSEPS = 1.0E-4
$
$ Fluid
$
GRDSET,,,,,, -1
INCLUDE 'fluid1.bdf'
$
$ Structure
$
INCLUDE 'structure.bdf'
$
BEGIN AFPM=100
$
$ Isolated Field Points
GRID, 10001,, 0., 0., 3.5
GRID, 10002,, 0., 0., 5.
GRID, 10003,, 0., 0., 10.
$
BEGIN AFPM=200
$
$ Field Point Mesh
INCLUDE 'fpm.bdf'
$
ENDDATA
Excerpt of fluid1.bdf
$ Exterior Acoustics - Vibrating Plate Example
$ Fluid Model of Domain 1: Finite and Infinite Elements
$
$ ------------------------------------------------------------------
-
$
$ PID MID RIO XP YP ZP
PACINF 10 20 10 0. 0. 0.
PSOLID 2 20 PFLUID
MAT10 20 1.21 340.
$
CHEXA 1001 2 1001 1002 1018 1017 1177 1178
1194 1193
CHEXA 1002 2 1002 1003 1019 1018 1178 1179
1195 1194
184 MD Nastran 2006 Release Guide
…
$ Infinite Elements
$
CACINF4 13901 10 3641 3642 3658 3657
CACINF4 13902 10 3642 3643 3659 3658
CACINF4 13903 10 3643 3644 3660 3659
CACINF4 13904 10 3644 3645 3661 3660
CACINF4 13905 10 3645 3646 3662 3661
CACINF4 13906 10 3646 3647 3663 3662
…
Results
Figure 5-6 shows the acoustic pressure in the Finite Element mesh and Figure 5-7 shows some results
printed to the .f06.
6 Aeroelasticity
J
Monitor Points, 188
J Spline6/7, 195
J
Combination of Controllers/User Input Loads Enhancements, 197
J Separate Rigid and Flexible Aero Meshes, 199
J
Miscellaneous Aeroelastic Enhancements, 201
188 MD Nastran 2006 Release Guide
Monitor Points
Introduction
“Monitor Points” is a term used collectively to refer to four data items that have been implemented in
MD Nastran:
1. MONPNT1 – The MONPNT1 provides integrated loads at a user defined point in a user defined
coordinate system. The user also identifies the nodes (on either the structural or aerodynamic
model) whose loads are to be integrated. MD Nastran 2006 adds the ability to specify an output
coordinate system in addition to the coordinate system used in defining the location of the
integration point. It availability has been extended from SOL 144 to SOL’s 101 and 146.
2. MONPNT2 – The MONPNT2 provides element results (Stress, Strain, Force) in a tabulated
fashion. For the results to be accurate, the term selected must be a linear function of the
displacements.
3. MONPNT3 – The MONPNT3 provides a summation of grid point forces at a user specified
integration points. This can be used to provide the net load acting at a fuselage or wing station by
making a “cut” in the structure and then identifying all the grids and elements on one side of the
cut
4. MONDSP1 – The MONDSP1 allows for the sampling of a displacement vector to create a
blended displacement response at a user specified point and coordinate system. The displacement
monitor point is essentially an RBE3 element (limited to a single dependent point) and the
dependent grid is now an arbitrary point.
While Monitor Points have been developed with primarily aeroelastic considerations in mind, their
applicability in any type of analysis is recognized. The following table shows which solution sequences
currently support monitor point processing.
Solution
Sequence MONPNT1 MONPNT2 MONPNT3 MONDSP1
SOL 101 X x x x
SOL 144 X x x x
SOL 146 X x
monitor point results in a matrix S that can be multiplied by the set of solution vectors U to provide the
monitor point results:
T
MP3 = S U (6-1)
The S matrix (denoted MP3INT in the dmap sequences) is computed as a preprocessing operation. The
monitor point results are then calculated using Equation (6-1) or 2 once the displacements have been
computed.
In this enhanced process, the exclusion flag (XFLAG) has special significance. This flag can be used to
exclude specified force types from the calculation. If the XFLAG field is set by the user to exclude all
of the candidate force types (i.e., XFLAG=SMAD), then the enhanced algorithm can be employed and
a filtering process is applied to see which set of the elements and grids listed in the GRIDSET and
ELEMSET will result in a non-zero resultant force. I.e., if all the elements attached to a particular grid
are included in the ELEMSET, the grid can be filtered out and if all the grids a particular element attaches
to are included in the GRIDSET, then the element can be filtered out. The remaining grids and elements
are then included in the mini-EMA step.
If the XFLAG is blank, then a complementary filtering process occurs. Excluding of grids and elements
occurs as above but now the remaining set of elements is discarded and the mini-EMA includes those
elements that are attached to the retained grids that are NOT included in the ELEMSET.
If some, but not all, of the candidate force type are excluded (e.g., XFLAG=A), then the enhanced
method cannot be applied and the MONPNT3 processing reverts to the original grid point force
methodology.
Benefits
The MONPNT1 was first introduced in MSC.Nastran 2001 and provides the user with a way to extract
the applied loading for a specified set of structural nodes or aerodynamic elements. This enables the
batch calculation of VMT (shear, moment and torque) data as well at aerodynamic coefficient data for
user specified regions and locations.
The MONPNT2 provides a way of pinpointing a particular response for output, as opposed to finding a
particular item in a large OFP listing.
The MONPNT3 provides a summation of the internal loads and therefore useful in calculating resultant
forces at a cut in the structure.
The MONDSP1’s ability to provide an averaged displacement is seen as providing a qualitative
assessment of the elastic deflection of a vehicle. An example is to monitor the nominal pitch and plunge
at a station along the wing.
Input
The MONITOR Case Control command provides control over the print of the monitor points results
Toggles can be used to control the print of the individual monitor types. This command must be placed
190 MD Nastran 2006 Release Guide
above the subcase level or in the first subcase and applies to all subcases. The print associated with SOL
146 results can be particularly voluminous since data can be given for every frequency or time point.
The MONPNT1, MONPNT2, MONPNT3 and MONDSP1 entries are shown in the Quick Reference
Guide. As mentioned, the MONPNT1 has been enhanced to provide an output coordinate system for
displaying the results. Note that the loads can be on the structural or the aerodynamic model as specified
by the COMP field that, in turn, identifies a AECOMP entry that can invoke CAEROi or AELIST entries
for aerodynamic elements or a SET1 entry for structural grids.
The MONPNT2 entry requests that the user identify the element type and NDDL item. The type is
obtained from the table given in Remark 5 of this entry and it is seen that there are separate types for
composite and element corner results.
The MONPNT3 entry identifies a piece of structure by identifying the elements and nodes associated
with it. The grid point force data associated with these entities is then integrated to the location specified
on the entry. The XFLAG can be used to exclude certain grid point force types from consideration.
The MONDSP1 entry is similar to the MONPNT1 entry but now it is displacements that are being
averaged. The AECOMP entry can invoke either structural grids or aerodynamic elements.
Output
A comprehensive depiction of the prints of the monitor points across all the solution sequences would be
too detailed for the purposes of this document. Several key tables are presented here and it is suggested
that the examples of the following subsection be exercised to get an idea of the printout to expect. For
SOL 144, the MONPNT1 and MONDSP1 entries can be on either the aerodynamic or the structural
mesh. An example of MONPNT1 output on both meshes that is extracted from the m31chk example file
is shown here:
CHAPTER 6 191
Aeroelasticity
S T R U C T U R A L M O N I T O R P O I N T I N T E G R A T E D L O A D S
CONFIGURATION = AEROSG2D XY-SYMMETRY = ASYMMETRIC XZ-SYMMETRY = ASYMMETRIC
MACH = 5.000000E-01 Q = 7.000000E+02
CONTROLLER STATE:
ANGLEA = 9.6005E-03 URDD3 = -1.0000E+00 ELEV = 1.7303E-01
AXIS RIGID AIR ELASTIC REST. INERTIAL RIGID APPLIED REST. APPLIED
---- ------------- ------------- ------------- ------------- -------------
CX 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
CY 0.000000E+00 0.000000E+00 5.530298E-14 0.000000E+00 0.000000E+00
CZ 4.735976E+03 4.835128E+03 5.000000E+01 0.000000E+00 0.000000E+00
CMX 7.039471E+03 7.187045E+03 6.000000E+01 0.000000E+00 0.000000E+00
CMY 1.717664E+04 1.727710E+04 0.000000E+00 0.000000E+00 0.000000E+00
CMZ 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
A E R O D Y N A M I C M O N I T O R P O I N T I N T E G R A T E D L O A D S
CONFIGURATION = AEROSG2D XY-SYMMETRY = ASYMMETRIC XZ-SYMMETRY = ASYMMETRIC
MACH = 5.000000E-01 Q = 7.000000E+02
CONTROLLER STATE:
ANGLEA = 9.6005E-03 URDD3 = -1.0000E+00 ELEV = 1.7303E-01
It is seen that the trim state is first printed and this is followed by labeling information and finally the
data. The monitor points extend over the same portion of the vehicle and it is seen that the results
compare well. In this case, there is no externally applied load so that the structural results show zeroes
and there are no applied loads on the aero mesh. If applied structural loads were present, the rigid and
elastic total loads would be printed in the two columns while only the elastic increment would be printed
for the aerodynamic model.
A print of MONDSP1 data extracted from the msimpms example is shown next.
192 MD Nastran 2006 Release Guide
S T R U C T U R A L M O N I T O R P O I N T D I S P L A C E M E N T S
CONFIGURATION = AEROSG2D XY-SYMMETRY = ASYMMETRIC XZ-SYMMETRY = SYMMETRIC
MACH = 4.500000E-01 Q = 2.000000E+00
CONTROLLER STATE:
URDD3 = 1.4909E-04 URDD5 = -2.5493E-05
A E R O D Y N A M I C M O N I T O R P O I N T D I S P L A C E M E N T S
CONFIGURATION = AEROSG2D XY-SYMMETRY = ASYMMETRIC XZ-SYMMETRY = SYMMETRIC
MACH = 4.500000E-01 Q = 2.000000E+00
CONTROLLER STATE:
URDD3 = 1.4909E-04 URDD5 = -2.5493E-05
In this case, different displacement requests have been made so that the structural and the aerodynamic
results do not compare.
The final output shown here is for MONPNT2 and MONPNT3 results from a SOL 101 run made with
example q2010601.
CHAPTER 6 193
Aeroelasticity
S T R U C T U R A L I N T E R N A L M O N I T O R P O I N T L O A D S (MONPNT2)
S T R U C T U R A L F R E E B O D Y M O N I T O R P O I N T I N T E G R A T E D L O A D S
It is seen that each MONPNT2 produces its own line of data for each subcase while the MONPNT3
results contain as many rows as the have been specified in the AXES field on the MONPNT3 entry.
Examples
The monitor point capability extends across solutions sequences and monitor point types. The following
table contains the names of tpl files that demonstrate a particular combination.
The prints in SOL 146 can be voluminous since each component that is printed requires its own table for
the list of frequency or time points.
For the aeroelastic solutions, the MONPNT1 and MONDSP1 data can be calculated based on structural
grids or aerodynamic elements. MONPNT2 and MONPNT3 results are only available on the structural
model.
The MONPNT2 results are computed by multiplying a predefined matrix times the solution vector. This
assumes that the desired quantity is a linear function of the solutions. Clearly, this is not the case for
synthesized responses; e.g. (von Mises stress).
CHAPTER 6 195
Aeroelasticity
Spline6/7
Introduction
Two new spline method are available in MD Nastran 2006: 3D finite surface spline (SPLINE6) and 3D
finite beam spline (SPLINE7). These splines support 6 degrees of freedom for both the aerodynamic and
structural meshes and may be used to couple the aerodynamic and structural models.
Both methods use the same basic approach to solving the interpolation problem: they form a small,
virtual finite element enforced motion statics problem to measure the motion of the dependent dofs. The
computed displacements under unit enforced motion of the independent grids are then the spline
interpolant. In the case of the beam spline (as shown in Figure 6-1 below), the virtual mesh is comprised
of a set of bar elements laid along a user-defined axis. The independent and dependent points are
connected to the virtual beam by RBE3 and RBE2 elements. In the case of the plate spline, the user
defines the mesh and RBE3 elements are used to connect the DOF’s to the virtual surface mesh. The user
can specify the elements that are to be used in the virtual mesh. Typically, the aerodynamic elements are
used as the virtual mesh.
Figure 6-1
196 MD Nastran 2006 Release Guide
Benefits
These new methods work across almost all aero mesh types and are suitable for “external” aero methods
in addition to structure-to-structure splines. These new methods are the only ones that are full 6DOF to
6DOF spline methods; hence, they are the only ones that can be used in structure-to-structure loads
mapping applications. With a little work using standard Nastran or by using the MD Nastran toolkit, these
two new spline methods may be used to perform structure-to-structure splining.
Standard MD Nastran does not support the user interface to drive the methods for structure-to-structure
mapping so it would be necessary to develop custom mapping tools, perhaps using MD Nastran Toolkit
to drive the mapping of loads from the aeroelastic finite element model to the internal loads FE using
these methods.
Input
The SPLINE6 and SPLINE7 entries are described in some detail in the MD Nastran Quick Reference
Guide. These entries do not result in additional output.
CHAPTER 6 197
Aeroelasticity
Introduction
Changes were made in the user interface for aeroelasticity to facilitate synthesizing controllers from
multiple inputs. The first change was a simple change in AELINK Bulk Data entry that is of significant
benefit when many subcases are being run. The AELINK entry now supports the character string
“ALWAYS” or ID=0 in place of the trim set ID specified at the subcase level in case control. The effect
of this is that a single AELINK entry can now apply to all of the subcases in the run.
The AEFORCE Bulk Data entry was enhanced in several ways: the resulting description of AEFORCE
Bulk Data entry in Appendix D shows two additional features, both when MECH=STRUCT is being
used:
1. The PERQ option of field 9 was activated.
2. Field 7 (LSET) can point to any type of loading whereas previously it could only select FORCE
of MOMENT load types.
Two other enhancements applicable to AEDW and AEPRESS entries as well as AEFORCE:
The first is in the nature of the correction in a design flaw. In previous releases of MD Nastran, if a
UXVEC entry only contained Label INTERCPT with a value of 1.0, the forces were added to all v-space
terms that included the intercept. This has been corrected so that the forces are only present for the
INTERCPT state.
The second is if AExxxx (i.e., AEFORCE/AEDW/AEPRESS) entries that point to the same UXVEC are
summed. Previously only a single AExxxx/UXVEC combination was permitted.
Benefits
With these enhancements, the user can now sum forces from a series of AExxxx entries to achieve a
single controller. For example, there may be wind tunnel results on a number of components (e.g.,
missiles and fuselage segments) at a unit angle of attack that are not included in the aerodynamic model.
Multiple AEFORCE entries that point to a single UXVEC vector that has INTERCPT and ANGLEA
terms can now be used to add these effects in the simulation. Note that the LSET call out can also refer
to a LOAD Bulk Data entry so that load superposition can occur and the import load feature of Section
x.1 can be utilized.
The benefit of the ID=”ALWAYS” on the AELINK entry is significant when hundreds of subcases are
run in a single job submittal.
198 MD Nastran 2006 Release Guide
Input/Output
The introduction has already described the changes available on the AELINK, AEDW, AEFORCE and
AEPRESS entries. There is no change in the output due to these enhancements.
Examples (aelinka.dat,
aelinkb.dat,i3fusa.dat,aepload4.dat,fusae.dat)
Aelinka.dat shows how ALWAYS can be used to make the linking condition apply to all subcases while
aelinkb.dat has one controller using the ALWAYS feature while another has subcase dependent linking
so that a scheduled deployment can be simulated.
i3fusa.dat is a variation of tpl file osprey.dat. It removes the engine controllers but adds user input
aerodynamics for the fuselage at the intercept. The following fragment of this file shows how this
concept is implemented:
Introduction
MD Nastran has been enhanced to support the ability to generate the rigid aerodynamic loads on one
mesh while the aeroelastic increments are generated from a second mesh.
Benefits
This enhancement adds to the infrastructure of the static aeroelastic analysis of SOL 144, but is not
accompanied by any immediate useful application. A possible application would be to use CFD
generated or wind tunnel derived aerodynamics to provide the rigid loads while the aeroelastic
increments could be generated using the current aerodynamic methods in MD Nastran. Having the
concept of separate rigid and flexible meshes available does simplify the task of incorporation these
alternative aerodynamics using a customized solution.
Input
The AERCONFIG Case Control command is provided to identify the aerodynamic configuration that
represents the rigid aerodynamics. The use of this command can be demonstrated by making two
separate runs: the first contains the rigid mesh and is run with SCR=NO to save the needed data blocks.
The AECONFIG command is used to identify this mesh. The second run inputs the flexible mesh using
standard bulk data input and the AECONFIG command while the flexible mesh is input using a
combination of DBLOCATE statements and the AERCONFIG command to identify the rigid mesh. See
the example below for the DBLOCATE requests.
Output
The following data related to aeroelastic results are written to the DBC and are therefore available in the
.xdb output:
7 Optimization
J
Topology Optimization with Manufacturability Constraints, 204
J Revised Optimizer Options, 220
J
Supporting Trust Region in SOL 200 for Adaptive Move Limits, 223
J Support of Analysis Model Value Overriding Design Model Value, 230
204 MD Nastran 2006 Release Guide
Introduction
Topology optimization is a powerful tool to generate design concepts in the early design stage. MD
Nastran 2006 contains substantial enhancements to this capability that provides a number of
manufacturability constraints to aid in producing designs that are more practical in terms of actually
manufacturing the proposed design. The constraints include minimum member size, symmetry
constraints, casting constraints (also called draw direction constraints), and extrusion constraints.
Benefits
Minimum Member Size (Constraints)
The minimum member size constraint is mainly used to control the size of members in topology optimal
designs. By avoiding thin members enhances the simplicity of the design and hence its manufacturability.
Minimum member size is more like quality control than quantity control.
Extrusion Constraints
It is often desirable to produce a design with a constant cross-section along a given direction. This
constraint is particularly essential for a design manufactured through an extrusion process. By using the
extrusion manufacturing constraints in topology optimization, constant cross-section designs can be
obtained for solid models regardless of the boundary conditions, loads, and finite element mesh.
Symmetry Constraints
It is often desirable to design a symmetric component or system. However, regular topology optimization
cannot guarantee a perfect symmetric design, even if the design space, boundary conditions, and loads
are symmteric. By using symmetry constraints in topology optimization, a symmtric design can be
obtained regardless of the boundary conditions or loads. These symmetric constraints can also be used
for irregular finite element meshes.
Input
The TOPVAR Bulk Data entry has been enhanced to provide manufacturing constraints. To select a
topologically designable region, the user needs to specify a group of elements by using a Bulk Data entry,
TOPVAR. All elements that reference property ID given on a TOPVAR entry are topologically
designable. Topology design variables are automatically generated with one design variable per
designable element. The manufacturability constraints are then applied on all elements referencing the
given property ID.
The basic format for TOPVAR is:
1 2 3 4 5 6 7 8 9 10
TOPVAR ID LABEL PTYPE XINIT XLB DELXV POWER PID
“SYM” CID MSi MSi MSi
“CAST” CID DDi DIE
“EXT: CID EDi
“TDMIN” TV
Field Contents
ID Unique topology design region identification number. (Integer > 0)
LABEL User-supplied name for printing purpose. (Character)
PTYPE Property entry name. Used with PID to identify the elements to be designed.
(Character: “PBAR”, “PSHELL”, ‘PSOLID”, etc.)
XINIT Initial value. (Real, XLB < XINIT). Typically, XINIT is defined to match the
mass target constraint, so the initial design does not have violated constraints.
For example, if the mass target is 30% on DRESP1=FRMASS, then it is
recommended XINIT=0.3.
XLB Lower bound to prevent the singularity of the stiffness matrix. (Real; Default
= 0.001)
DELXV Fractional change allowed for the design variable during approximate
optimization. (Real > 0.0; Default = 0.2. See Remark 3).
POWER A penalty factor used in the relation between topology design variables and
element Young’s modulus. (Real > 1.0; Default = 3.0). 2.0 < POWER < 5.0 is
recommended.
PID Property entry identifier (Integer > 0)
“SYM” Indicates that this line defines symmetry constraints.
CID Rectangular coordinate system ID used for specifying manufacturing
constraints. See Remark 4 (Blank or Integer > 0; Default = 0 = the basic
coordinate system)
MSi Mirror symmetry plane. See Remark 5 & 7 (Character, ‘XY’, ‘YZ’, or ‘ZX’)
206 MD Nastran 2006 Release Guide
Field Contents
“CAST” Indicates that this line defines casting constraints (i.e., die draw direction
constraints). See Remarks 6 and 7.
DDi Draw Direction. DDi=X, Y, Z or X-, Y-, Z- for a single die option (DIE=1)
where X-, Y-, Z- indicates the opposite direction of X, Y, and Z respectively.
DDi=X, Y, and Z for two die option (DIE =2) (Character)
DIE Die Options. (Blank or integer 1 or 2; Default = 1)
= 1 (or blank). A single die will be used and the die slides in the given draw
direction (i.e., material grows from the bottom in the draw direction)
= 2. Two dies will be used and the dies split apart along the draw direction (i.e.,
material grows from the splitting plane in opposite direction along the axis
specified by the draw direction DDi. The splitting plane is determined by
optimization)
“EXT” Indicates that this line defines extrusion constraints (i.e., enforce constant
cross-section) See Remark 6 and 7.
EDi Extrusion direction. (Character, X, Y, or Z)
“TDMIN” Indicates that this line defines a minimum member size, See Remarks 9 and 10.
TV Minimum member size. See Remark 9. (Real > 0.0)
Remarks:
1. The topologically designable element properties include PROD, PBAR, PBARL, PBEND,
PBEAM, PBEAML, PSHELL, PSHEAR, PSOLID, and PWELD. Multiple TOPVAR’s are
allowed in a single file.
2. All designed element properties must refer to a MAT1 entry; therefore, a PCOMP cannot be used
as designed property in topology optimization. PCOMP’s can be used as non-designed properties
in a topology optimization job.
3. If DELXV is blank, the default is taken from the specification of DELX parameter on the
DOPTPRM entry.
4. Only CORD1R and CORD2R can be used as a referenced coordinate system to specify topology
manufacturing constraints. Only one reference coordinate system CID is allowed for each
TOPVAR entry.
5. One, two or three different mirror symmetry planes can present (such as MS1=XY, MS2=YZ, and
MS3=ZX).
6. Casting (“CAST”) and Extrusion (“EXT”) manufacturability constraints can be applied to
PTYPE=”PSOLID” only. Casting constraints cannot be combined with extrusion constraints for
the same TOPVAR entry.
7. Some symmetry constraint types can be combined with casting or extrusion constraints. The
referenced coordinate system CID must be the same for the combined constraints. Some possible
combinations are:
CHAPTER 7 207
Optimization
For “EXT” constraints, possible combinations are (EDi=X, MSi=XY and/or ZX), (EDi=Y,
MSi=YZ and/or XY), (EDi=Z, MSi=ZX and/or YZ).
For “CAST” constraints, possible combinations are (DDi=X or -X, MSi=XY and/or ZX),
(DDi=Y or -Y, MSi=YZ and/or XY), (DDi=Z or -Z, MSi=ZX and/or YZ).
8. For two dies option (DIE=2), the splitting plane is optimized. For a single die DIE=1, the parting
plane is the bottom surface of the designed part in the draw direction.
9. TDMIN is a dimensional quantity with a guideline that it be set to at least three times a
representative element dimension.
10. Without a TDMIN continuation line, the minimum member size constraint is taken from the
specification of TDMIN parameter on the DOPTPRM entry. This option is applied on 2 and 3 D
elements only. Minimum member size constraints can be used with “SYM”, “CAST”, and “EXT”
constraints.
Input
The input data for this example related to topology optimization model is given in Listing 7-1.
DESOBJ = 1
DESGLB = 1
SUBCASE 1
$ Subcase name : Default
SUBTITLE=Default
SPC = 2
LOAD = 2
ANALYSIS = STATICS
BEGIN BULK
DCONSTR 1 2 .5
TOPVAR, 1 , Tshel, Pshell, .5, , , , 1
DRESP1 1 COMPL COMP
DRESP1 2 FRMASS FRMASS
210 MD Nastran 2006 Release Guide
Output
Figure 7-2 shows the topology optimized result that is smoothed and remeshed by using MSC.Patran
2005 r2. It is noticed that there are some small members.
Input
The input data for this example related to topology optimization with “minimum member size” is given
in Listing 7-2. The minimum member size value is defined by the parameter TDMIN = 0.5 on the
DOPTPRM entry and corresponds to the length of 10 elements.
DESOBJ = 1
DESGLB = 1
SUBCASE 1
$ Subcase name : Default
SUBTITLE=Default
SPC = 2
LOAD = 2
ANALYSIS = STATICS
BEGIN BULK
DOPTPRM, TDMIN, 0.5
DCONSTR 1 2 .5
TOPVAR, 1 , Tshel, Pshell, .5, , , , 1
DRESP1 1 COMPL COMP
DRESP1 2 FRMASS FRMASS
Output
Figure 7-3 shows the topology optimized result with “minimum member size” TDMIN=0.5. Compared
the design shown in Figure 7-2, this design with “minimum member size” is obviously much simpler and
there are no tiny members at all.
Figure 7-3 MBB Beam Topology Design with “Minimum Member Size”
212 MD Nastran 2006 Release Guide
Input
To apply symmetric constraints on designed properties, users need to create a reference coordinate
system using a rectangular coordinate system CORD1R or CORD2R. In this example, grid 10001
(location x=3, y=1, and z=0) is defined as the origin. Grid 10002 (x=3, y=1, and z=1) lies on the z-axis,
and grid 1003 (x=4, y=1, and z=0) lies in the x-z plane. CORD1R CID=1 defines a reference coordinate
system. A continuation line “SYM” enforces the property PSHELL=1 to be symmetric about the planes
YZ and ZX in the reference coordinate system CID=1. In addition, a minimum member size
TDMIN=0.15 is applied. The input data for this example is given in Listing 7-3.
DESOBJ = 1
DESGLB = 1
SUBCASE 1
$ Subcase name : Default
SUBTITLE=Default
SPC = 2
LOAD = 2
ANALYSIS = STATICS
BEGIN BULK
CORD1R 1 10001 10002 10003
GRID 10001 3. 1. 0.0
GRID 10002 3. 1. 1.0
GRID 10003 4. 1. 0.0
TOPVAR, 1 , Tshel, Pshell, , , , , 1
, SYM , 1 , YZ , ZX
, TDMIN, 0.15
DRESP1 1 COMPL COMP
DRESP1 2 FRMASS FRMASS
DCONSTR 1 2 .5
Output
Figure 7-4 shows the topology optimal result with symmetric constraints and minimum member size.
CHAPTER 7 213
Optimization
Figure 7-4 MBB Beam with Symmetric Constraints and Minimum Member Size
214 MD Nastran 2006 Release Guide
Input
The extrusion constraints enforce a constant cross-section design along the given extrusion direction. The
input data related to imposing an extrusion constraint along the z-axis in the basic coordinate system (as
the default option) is given in Listing 7-4.
DESOBJ = 1
DESGLB = 1
SUBCASE 1
$ Subcase name : Default
SUBTITLE=Default
ANALYSIS = STATICS
SPC = 2
LOAD = 2
CHAPTER 7 215
Optimization
Output
Figure 7-6 shows the topology optimized result with extrusion constraints. It is obvious that the design
has a constant cross-section along the z-axis.
Input
The casting constraints with one die option enforce the material can only be added to the region by
“filling up” in the given draw direction from the bottom (or, stated another way, that voids extend from
the top surface and do not reappear in the die direction). To apply casting constraints and symmetric
constraints on designed properties, a reference coordinate system CID=1 is defined by using a
rectangular coordinate system CORD1R. A “CAST” continuation line defines casting constraints in the
Y direction and one die is a default option. Another “SYM” continuation line defines symmetric
constraints about the YZ plane. The input data related to the topology optimization model is given in
Listing 7-5.
DESOBJ = 1
DESGLB = 1
SUBCASE 1
$ Subcase name : Default
SMETHOD=ELEMENT
SUBTITLE=Default
ANALYSIS = STATICS
SPC = 2
LOAD = 2
$ Direct Text Input for this Subcase
BEGIN BULK
DRESP1 2 Frmass FRMASS
DRESP1 1 COMPL COMP
DCONSTR 1 2 .3
CORD1R 1 5 167 7
PSOLID 1 1 0
TOPVAR, 1 , TSOLID, PSOLID, .3, , , , 1
, CAST, 1 , Y
, SYM, 1 , YZ
PSOLID 1 1 0
Output
Figure 7-7 shows the topology optimized result with one die casting constraints. It is observed that the
design material is added by “filling up” in the Y direction from the bottom. In addition, the design is
symmetric about the YZ plane in the reference coordinate system CID=1.
CHAPTER 7 217
Optimization
Figure 7-7 Torsion Beam with One Die Casting Constraints in Y Direction
218 MD Nastran 2006 Release Guide
Input
The input for two die casting constraints is similar to the one die option in Example 5. Here, the difference
is that 2 are selected for the DIE field on the TOPVAR entry. The input data related to imposing two die
casting constraints is given in Listing 7-6.
DESOBJ = 1
DESGLB = 1
SUBCASE 1
$ Subcase name : Default
SUBTITLE=Default
ANALYSIS = STATICS
SPC = 2
LOAD = 2
$ Direct Text Input for this Subcase
BEGIN BULK
DRESP1 2 Frmass FRMASS
DRESP1 1 COMPL COMP
DCONSTR 1 2 .3
CORD1R 1 5 167 7
PSOLID 1 1 0
TOPVAR, 1 , TSOLID, PSOLID, .3 , , , , 1
, CAST, 1 , Y, 2
, SYM , 1 , YZ
PSOLID 1 1 0
Output
Figure 7-8 shows the topology optimized result with two die casting constraints. It is observed that the
design material grows from the splitting plane in opposite directions along the y-axis specified in the
reference coordinate system CID=1. The splitting plane is determined by optimization and in this case
corresponds to the
CHAPTER 7 219
Optimization
Figure 7-8 Torsion Beam with Two Die Casting Constraints in Y-Axis
220 MD Nastran 2006 Release Guide
Introduction
MD Nastran 2006 has made MSCADS the default optimizer for the Design Optimization in Solution 200.
This provides MSC with greater flexibility in maintaining and enhancing the optimization algorithm
relative to the DOT optimizer that is licensed from Vanderplaats Research & Development, Inc. (VR&D)
and has been the mainstay algorithm for many years. DOT is still available as an option that requires
explicit selection by the user. MSCADS is MSC.Software’s version of the ADS (Automated Design
Synthesis) code, a public domain FORTRAN program developed by Dr. G. N. Vanderplaats while he
was on the faculty of the Naval Postgraduate School under a contract from the Navy and NASA/Langley.
Dr. Srinivas Kodiyalam provided MSC.Software with his enhanced version of the ADS source code at
no cost.
The topology optimization of the previous section typically involves thousands of design variables (the
simple MBB beam, for example, has 4800 independently designed elements). The MSCADS and DOT
optimizers are intended for problems with much fewer design variables, with 3-4000 considered a
practical upper limit. For this reason, MSC recommends that serious users of the topology optimization
capability consider acquiring the Topology Optimization option, which contains the BIGDOT optimizer,
also from VR&D. This code has been shown to be capable of handling tens of thousands of design
variables while considering numerous constraints. At the same time, it must be stated that it is not strictly
necessary to acquire the Topology Optimization option in order to apply topology optimization. A
preliminary assessment of this capability on limited sized problems can be made using only the Design
Optimization option. It is necessary in this case to explicitly select the MSCADS or DOT optimizer as
outlined in the Input subsection below, in this case since the default when there are TOPVAR Bulk Data
entries is to use BIGDOT.
Benefits
The MSCADS optimizer provides numerous options for performing design optimization that can be
explored. The BIGDOT optimizer not only enables performing practical topology optimization tasks but
can also be used to perform standard shape and sizing optimization for design tasks with many thousands
of design variables. This latter capability requires that both the Topology Optimization and the Design
Optimization options be available.
Input
There are two ways to select the optimizer code. One way is by modifying an executive system parameter
OPTCOD in the Runtime Configuration (RC) file as shown in Table 7-2.
CHAPTER 7 221
Optimization
1 – DOT Optimizer
2 – BIGDOT Optimizer
The second way is by a new parameter OPTCOD added to the DOPTPRM Bulk Data entry that has
options shown in Table 7-3. The parameter METHOD is used to select optimization methods.
Output
There are no outputs that are affected by optimizer selection with the exception that the optimizer output
produced using the IPRINT parameter on the DOPTPRM entry is dependent on the method selected. In
particular, the banner for the MSCADS code appears as:
M S C . A D S
E N H A N C E D A D S P R O G R A M
F O R
A U T O M A T E D D E S I G N S Y N T H E S I S
Introduction
Formal approximate optimization is used in SOL 200 to find a new design without performing expensive
and exact finite element analyses (Ref. 1, Chapter 2.7). However, move limits must be applied to define
a restricted region on which an adequate approximate model can be created.
Convergence checks are made following each approximate optimization task. Currently, if the
approximate optimization comes up with a design that an exact analysis shows is actually worse, it is
assumed that the region defined by move limits are too generous and they are reduced. Using Trust
Region Concepts, this simple update strategy can be improved in three fundamental ways:
1. A merit function is applied to provide a more quantitative measure of the quality of the
approximation.
2. A provision is made to increase the move limits when the approximate optimization results are
shown to be of high quality.
3. If the new design is judged to actually be worse, it is discarded and the approximate optimization
task is performed again with tighter move limits.
Benefits
Since the move limits can be either reduced or increased in an adaptive fashion, it is expected that the
quality of the approximate model will be enhanced. This should lead to more robust optimization result
and faster convergence. In addition, rejecting a bad design should also smooth the design optimization
process.
Theory
Concept of Trust Region
The main idea behind the Trust Region is to first compute a merit function that is a combination of the
objective function and the maximum violated constraint value and then form a ratio of the exact
reduction in a merit function to the predicted reduction in the merit function. The ratio can be written as
follows, assuming a design task is a constrained minimization optimization task:
MF p – MF c
Ratio = ------------------------------
MF p – MF a
224 MD Nastran 2006 Release Guide
where:
Notice that a merit function is the sum of objective ( Φ ) and the product of penalty weight and the
maximum violated constraint ( g ) . Subscripts c, p and a, indicate that the function is evaluated exactly
at the current design cycle, evaluated exactly at the previous design cycle and evaluated approximately,
respectively. The penalty weight plays an important role in a successful optimization task with Trust
Region Method.
The magnitude of Ratio varies in the real interval of ( – ∞, ∞ ) . The denominator is the predicted
reduction in merit function while the numerator is the exact reduction in merit function. Since we
consider the case of minimizing the objective, the denominator should always produce a positive number
to indicate that the optimizer has done a good job.
Different Ratio values can measure the quality of the approximate model. For example, a negative Ratio
(likely due to negative numerator) indicates that the approximate model is so bad that the exact merit
function is greater than the previous exact. Thus reducing move limits is necessary. On the other hand,
Ratio = 1 indicates the approximate model is very good that the predicted reduction is identical to the
exact reduction and the move limits can be increased. In general, the following strategies are used to
update move limits if:
1. Ratio < η 1 (say 0.01), reject the design, cut the move limits in half and repeat the approximate
optimization task. For a minimization task, the reduction in the merit function must be greater
than zero. A too small or negative Ratio indicates that the new design proposed by the
approximate model either does not reduce the merit function, or the quality of the approximate
model is very poor.
2. η 1 < Ratio < η2 (say 0.25), accept the design, but cut the move limits in half for the next
approximate design task. The ratio in this range indicates that quality of the approximate model
is not good enough, or the current move limit is still too large.
3. η 2 < RATIO < η 3 (say 0.75), accept the design and do not adjust the move limits.
4. Ratio > η 3 , accept the design, but increase the move limits by 50%, up to a pre-specified upper
value. The ratio approaching to 1 indicates that the approximate model I is accurately predicting
the actual behavior. Therefore, the current move limits can be increased. In addition, although
Ratio > 1 indicates that the approximate model is not particularly accurate, but it predicts in the
right direction so that larger move limits can also be used.
optimization problem should also be solved in the same fashion to minimize the merit function that is
formed by the objective and the corresponding 2nd term. A capability to transform an approximate
optimization task to a feasible design was implemented and can be readily used here to satisfy this
consistency requirement. Notice that the algorithm of Ref. 3 computes the penalty weight,
PW = Pena l ⋅ Φ o , where Φ o is the starting objective at the beginning of the approximate optimization job,
while here PW is obtained with a single number (See Penalty Weight Section).
Penalty Weight
Penalty Weight (PW) is used to form the merit function. The penalty weight plays an important role in
a successful optimization task with Trust Region Method. It is problem dependent. The larger it
becomes, the more the maximum violated constraint is penalized. There are two ways to define PW:
automatic and user specified. For the automatic way, PW = 10 * the initial objective from the initial
design cycle. This is the default option. Alternatively, the user can provide his own through a Bulk Data
Parameter, MXLAGM1 (See Input Section). Then, PW = 10.* MXLAGM1.
Rejecting a Design
If Ratio < η 1 , the current design will be rejected. When the flag is set, the subsequent design sensitivity
phase will be skipped and the approximate optimization job will be performed based on the previous
good design with reduced move limits.
Input
New Parameters added to the DOPTPRM entry
Outputs
Special Printout from DOM12
If Trust Region method is invoked, DOM12 prints out additional information message as shown below.
This message is printed out once every design cycle. The left column is design cycle number. It prints
out Objective, Maximum violated constraint and merit function for exact current, exact previous and
approximate. It further prints out Ratio together with numerator, denominator. It also prints out the final
Update factor for move limits plus the rejecting status. Finally, it prints out current move limits for
property and design variable ply penalty weight.
DCYCL OBJECTIVE MAX-CONS MERIT-FUN NUMER DENOM RATIO UPFAC REJ-FLAG TTTT
2 PREV 6.893711E+00 2.133793E+01 1.477869E+03 5.0832E+02 5.0839E+02 9.9987E-01 2.0000E+00 0 TTTT
CURR 9.935308E+00 1.392006E+01 9.695438E+02 TTTT
APPX 9.935904E+00 1.391907E+01 9.694761E+02 TTTT
MOVEP,MOVP-MIN = 5.000000E-01 1.000000E-02 TTTT
MOVEX,MOVX-MIN = 1.000000E+00 5.000000E-02 TTTT
NDOFs(NDV-NACS)= 0 TTTT
PENAL WEIGHT = 0.6894E+02 TTTT
***************************************************************
S U M M A R Y O F D E S I G N C Y C L E H I S T O R Y
***************************************************************
Examples
The example (dtrustr2.dat) is a Stiffened Panel constrained optimization job taken from the testing
problem library (d200x7.dat). It tries to minimize a weight response while satisfies stress and
displacement constraints. The same job was run with and without Trust Region (TR). The Trust Region
is invoked by specifying TREGION=1 on the DOPTPRM entry. In addition, the parameter MXLAGM1
is set to 10.
Figure 7-9 plots the objective history and DELX history with and without TR. The TR job converges at
design cycle 15 (notice that plots count initial design cycle as 1 that is actually zero if counted in the f06)
while the non-TR job converges at design cycle 27. Both has same final objective function with
maximum feasible constraint at the tolerance of GMAX=0.5%. The fast convergence achieved by the
TR job may be explained by the DELX history shown at the bottom of Figure 7-9. The non-trust region
job uses a constant move limit (e.g., DELX=0.5) while the DELX in the trust region job is adaptively
updated: between design cycles 2 and 6, DELX=1.0 and then reduced below 0.5 between design cycles
8 and 14. Finally, Figure 7-10 plots the maximum constraint values with and without TR. Listing 7-7 lists
the summary of the design history.
228 MD Nastran 2006 Release Guide
16.0 6.0
5.5
14.0
5.0
3.5
8.0 3.0
2.5
6.0
2.0
4.0 1.5
1.0
2.0
0.5
0.0 0.0
0 5 10 15 20 25 30
Design Cycle
Figure 7-9 Objective History of Example 2: Trust Region vs. Non-Trust Region
1.4
1.2
Maximum Constraint
1.0
0.8
0.6
0.4
0.2
0.0
0 5 10 15 20 25 30
-0.2
Design Cycle
MaxC-TR MaxC-NTR
Figure 7-10 Max. Constraint History of Example 2: Trust Region vs. Non-Trust Region
CHAPTER 7 229
Optimization
References
1. MSC.Nastran 2004 Design Sensitivity and Optimization User’s Guide, MSC.Software
Corporation, Santa Ana, CA., 2003
2. MSC.Nastran 2005 Release Guide, MSC.Software Corporation, Santa Ana, CA., 2004
3. Prof. L. Lasdon, private communication, Dec. 13, 2004.
230 MD Nastran 2006 Release Guide
Introduction
In SOL 200, when the value of an analysis model property is different from a design model value
obtained by the relation defined on a DVxREL1 entry, the design model value overrides the analysis
model value. The new PVAL option provides an alternate to allow the analysis model value to take the
precedence over the design model value.
Benefits
Provides a flexible way for a sizing optimization job to start with either design model values or analysis
model values.
Input
The PVAL option is applicable to three linear design property entries: DVPREL1, DVCREL1 and
DVMREL1. To activate this option, specify the character input of “PVAL” on the COEF1 field on a
DVPREL1 (DVCREL1, DVMREL1) entry.
Output
None.
Example
The example shows designing a plate thickness. The plate thickness, 2.5, is defined on PSHELL 1 entry.
First, the design entries without the PVAL option are given below. In this case, the design model value,
2.0 (the product of the initial design variable value, 1.0 and the coefficient, 2.0 on the DVPREL1 entry)
will override the analysis model value. The comparison of analysis model value and design model value
printed in the f06 file is shown here:
PSHELL 1 2 2.5
DESVAR 1 THICK 1. 0.1 10.
DVPREL1 1 PSHELL 1 T
1 2.0
CHAPTER 7 231
Optimization
----- COMPARISON BETWEEN INPUT PROPERTY VALUES FROM ANALYSIS AND DESIGN MODELS -----
------------------------------------------------------------------------------------------------------------------------------------------------------------
PROPERTY PROPERTY PROPERTY ANALYSIS DESIGN LOWER UPPER DIFFERENCE SPAWNING
TYPE ID NAME VALUE VALUE BOUND BOUND FLAG FLAG
------------------------------------------------------------------------------------------------------------------------------------------------------------
PSHELL 1 T 2.500000E+00 2.000000E+00 N/A N/A WARNING
Then, the DVPREL1 entry with the PVAL option is shown here with other two entries being kept the
same. In this case, the design model value equals the analysis model property value, 2.5 obtained directly
from the 4th field of PSHELL 1 entry. The similar comparison of analysis model value and design model
value is printed in the f06 file.
DVPREL1 1 PSHELL 1 T
1 PVAL
----- COMPARISON BETWEEN INPUT PROPERTY VALUES FROM ANALYSIS AND DESIGN MODELS -----
------------------------------------------------------------------------------------------------------------------------------------------------------------
PROPERTY PROPERTY PROPERTY ANALYSIS DESIGN LOWER UPPER DIFFERENCE SPAWNING
TYPE ID NAME VALUE VALUE BOUND BOUND FLAG FLAG
------------------------------------------------------------------------------------------------------------------------------------------------------------
PSHELL 1 T 2.500000E+00 2.500000E+00 N/A N/A NONE
8 Miscellaneous Enhancements
J
Export of Static Loads, 234
J Enhanced Participation Factor Results, 237
J
Total Strain Energy Output for Defined SETs, 249
J Model Checkout Procedures - Method to Vary Material Properties, 252
234 MD Nastran 2006 Release Guide
Introduction
Functionality was added to MD Nastran to facilitate load transfer from one run to the next in three
important ways:
1. MD Nastran can use Grid Point Force methodology to extract the load on a user defined free body.
This load is output on a PG-like matrix that has an associated NAME, ID and optional label. A
BGPDT data block is also produced that contains information on the grids associated with the
free-body.
2. MD Nastran can export static loads from a load case defined in the current subcase.
3. MD Nastran can now import a load from a pre-defined database (including, but not limited to,
loads produced using the previous steps) to be used in the formation of the load on a structure.
Benefits
The design of complex structures frequently involves joint development with a system integrator and a
number of subcontractors. The development of design loads is typically the task of the system integrator
based on an analysis of the entire vehicle. It is then necessary to communicate the loads on the pieces of
the structure to various subcontractors. The ability to extract the load on a free body is particularly useful
in aeroelasticity, where the load can be a combination of applied, rigid aerodynamic and inertial loadings.
The ability to export the statically applied load, or some portion of the load, is felt to be of benefit when
it is desired to apply the same loading to different representations of the same structure.
Input
The ability to export a statically applied load is enabled by the new EXPORTLD Case Control command
as described in the MD Nastran 2006 Quick Reference Guide. Typically, this is applied at the subcase
level, but can be applied above the subcase level as well. In any case, the command results in a unique
load vector (qualified by LOADID and LOADNAME) for each subcase. If a subset of grids is provided
by identifying a SET Case Control command as part of the EXPORTLD command, only the loads on the
grids associated with this grid are exported. A BGPDT (Basic Grid Point Data Table) is output with the
load vector to identify the degrees of freedom associated with each of the rows in the vector.
The ability to export a free body load is done through the combination of the new FBODYLD Case
Control command and the FBODYLD and FBODYSB Bulk Data entries. The FBODYLD Case Control
command is used to point to the FBODYLD Bulk Data (via the NAMEi called out on the case control
command) that defines the submodel for which the freebody load will be calculated and stored. The case
control command also provides an optional load ID that can be associated with the load. The FBODYLD
Bulk Data entry, in turn, points to a FBODYSB Bulk Data entry. The FBODYLD entry provides a label
that is intended to identify the loading condition while the FBODYSB entry has a second label that is
intended to identify the component. Both labels are optional. The FBODYSB entry identifies the grids
CHAPTER 8 235
Miscellaneous Enhancements
and elements that make up the free body and provides the ability to exclude certain types of grid point
forces in creating the free body load.
The remarks for the EXPORTLD Case Control command indicate how the loads created with an
EXPORTLD request can be used in a subsequent run using FMS statements such as:
ASSIGN loads1=’run1.MASTER’
DBLOCATE datablk=(EXTLD,EXTBGP) WHERE(LOADNAME=’ALLCASES’),
CONVERT(LOADID=LOADID+1000) LOGICAL=loads1
…
CEND
LOADS=1001 $ Select external load with LOADID=1001, imported
from previous run.
The EXTLD datablock contains the loads whereas the EXTBGP contains the grid point information that
is used to match up the imported loads with the grid points. Clearly, it is necessary that the Grid ID’s
have the same meaning in the two runs.
The import of a load created using the FBODYLD Case Control command is similar except it is now
necessary to rename the datablocks created in the previous run to match those required for the import of
these loads:
ASSIGN loads1=’fbrun1.MASTER’
DBLOCATE datablk=(FBLPG/EXTLD,FBLBGPDT/EXTBGP)
WHERE(LOADNAME=’fblcase’), CONVERT(LOADID=LOADID+1000)
LOGICAL=loads1
…
CEND
LOADS=1001 $ Select external load with LOADID=1001, imported
from previous run.
Output
The new commands produce limited output. The FBODYLD request does produce informational
messages from a DBDICT statement that requests output on the presence of all FBLPG and FBLBGPDT
data blocks along with qualifiers as to loadid, namei (from case control and the FBODYLD Bulk Data
entry), submodel name from the FBODYSB entry and the labels from the two bulk data entries.
which is in equilibrium across the cutout. The fbody.dat file imports this load onto a model that is only
the center section of the original model. It is necessary to constrain a corner of this “free body” to remove
the rigid body motion. An examination of the .f06 results for this run shows that the SPC forces are
negligible while the stresses agree well for the elements that are shared between the two models. The
displacements do not agree, but this is to be expected because they displacements for the small model are
relative to the artificially constrained model.
Sfsw.dat is a SOL 144 run that demonstrates the ability to ask for different free body loads is separate
subcases and has multiple FBODYLD/FBODYSB pairs for different components of the familiar forward
swept wing. The fuselage subsystem is selected for further analysis in the subsequent run and it is seen
the FBODYSB entry with FUSELAGE in the NAMES field has the applied loads excluded using an ‘A’
in the XFLAG field. Ffsw.dat imports this load into a SOL 101 that only has a model of the fuselage and
comparison of the results shows that the stresses in the bars that represent the fuselage agree well between
the two runs.
Introduction
New Case Control commands PFMODE, PFPANEL and PFGRID have been implemented to request
modal, panel and grid participation factors. These commands will replace the existing FLSPOUT and
MCFRACTION Case Control commands.
A new, consistent output format is used for all types of modal and panel participation factors. This format
is similar to the output format obtained with the MCFRACTION command. The output format of grid
participation factors is similar to the output format of displacements.
In addition, the new implementation supports
• panel definition by referencing a set of grids, a set of elements or a set of properties.
• panel and grid participation factors in direct frequency response analysis (SOL 108).
Finally, an adjoint method is used to compute acoustic structural modal participation factors, acoustic
panel participation factors and acoustic grid participation factors, resulting in significant performance
improvements.
Benefits
• The new case control commands and the new output formats provide a consistent user interface
to all kinds of participation factors that is easy to use.
• The following example shows significant reductions of computation times and IO when
computing panel participation factors:
Panel participation factors have been These data refer to the computation of the participation
computed for 2 fluid grid points and 9 factors only.
panels.
238 MD Nastran 2006 Release Guide
Theory
In a linear structural dynamic analysis, the results at a degree of freedom considered are the sum of the
contributions of the different modes, e.g., the accelerations at a degree of freedom considered are the sum
of the accelerations due to the responses of the different structural modes. These contributions are called
structural modal participation factors or modal contribution fractions. The degrees of freedom
considered are called response degrees of freedom. Structural modal participation factors allow to
identify the structural modes that have the largest influence on the response.
Likewise, in an acoustic analysis, the pressure at a grid point considered is the sum of the pressures due
to the responses of the different fluid modes. These contributions are called acoustic fluid modal
participation factors. Acoustic fluid modal participation factors allow to identify the fluid modes that
have the largest influence on the response.
In a coupled analysis, the pressure at a response degree of freedom is the sum of the pressure due to the
acoustic sources in a rigid cavity, and the pressure due to the acceleration of the fluid-structure interface,
the so-called wetted surface. The pressure due to the acoustic sources in a rigid cavity is called the load
participation factor.
The acceleration of the fluid-structure interface is the sum of the accelerations due to the responses of the
different structural modes, obtained from a coupled analysis. These contributions are called acoustic
structural modal participation factors. One acoustic structural modal participation factor equals the
CHAPTER 8 239
Miscellaneous Enhancements
pressure at the response degree of freedom if there are no acoustic sources, and if the acceleration of the
wetted surface consists of the response of one mode only. Thus, the acoustic structural modal
participation factors allow to identify the structural modes that have the largest influence on the pressure
at the grid point considered. In the absence of acoustic sources within the cavity, the acoustic structural
modal participation factors sum up to the total pressure at the response degree of freedom.
Modal participation factors, by their nature, are useful only in the low-frequency range where the
resonance frequencies are well separated, and the response is dominated by a small number of modes.
On the contrary, geometric participation factors are useful also at higher frequencies where the response
has contributions from a large number of modes. There are two types of geometric participation factors,
namely panel participation factors and grid participation factors.
A panel is a set of grid points of the wetted surface. The panel participation factor is that pressure at the
grid point considered that results from the accelerations of the grid points of the panel only, with all other
grid points of the wetted surface kept fixed. Thus, panel participation factors allow to identify the regions
of the wetted surface that have the largest influence on the acoustic pressure at the grid point considered.
Panel participation factors usually do not sum up to the total acoustic pressure. This is only the case if
the panels do not overlap, and if their union equals the complete wetted surface.
The accelerations of the grid points of the panel are the sum of the accelerations due to the different
structural modes. The pressure due to the accelerations at the grid points of the panel that are due to one
mode only is called the acoustic panel modal participation factor. Acoustic panel modal participation
factors sum up to the panel participation factors.
Finally, if the panels consist of one grid point only, acoustic grid participation factors are obtained. For
each structural grid point of the wetted surface, there are six acoustic grid participation factors, i.e. the
pressures at the response degree of freedom due to the accelerations of the six degrees of freedom of this
grid point. The acoustic grid participation factors depend on the mesh size. Thus, their absolute value has
no physical meaning. However, if the mesh of the wetted surface is of comparable size everywhere, the
acoustic grid participation factors allow to quickly identify the regions that make the largest contribution
to the acoustic pressure at the grid point considered, and thus help to define the panels.
Participation factors are complex quantities, summing up to the complex response. Thus, if they are
divided by the response, they sum up to one. The participation factors divided by the response are called
normalized participation factors. Normalized participation factors are complex quantities, too.
The real parts of the normalized participation factors sum up to one whereas the imaginary parts sum up
to zero. Thus, the real part of a normalized participation factor is that part of the participation factor that
is in phase with the total response, divided by the magnitude of the total response. It is called the modal
fraction. The phase of a normalized participation factor is the phase of the participation factor relative to
the total response.
If the modal fraction is multiplied by the magnitude of the total response, the projected participation
factor is obtained. It is that part of the participation factor that is in phase with the total response. The
projected participation factors sum up to the total magnitude.
240 MD Nastran 2006 Release Guide
Input
Computation and output of modal participation factors is controlled by the PFMODE Case Control
command:
PFMODE STRUCTURE , PRINT, PUNCH , REAL or IMAG ,
FLUID PLOT PHASE
ALL
[ SORT = sorttype ], [ KEY = sortitem ], ITEMS = ,
( itemlist )
ALL ALL
FLUIDMP = m f , STRUCTMP = m s ,
NONE NONE
ALL ALL
PANELMP = setp , SOLUTION = setf , [ FILTER = fratio ]
NONE NONE ,
setdof
[ NULL = ipower ] ) =
NONE
Examples
SET 20 = 25/T3, 33/T3
PFMODE(STRUCTURE, STRUCTMP=ALL) = 20
Compute structural modal participation factors for z-translations at grid points 25 and 33
SET 20 = 11217
SET 90 = 25., 30., 35.
PFMODE(FLUID, STRUCTMP=ALL, FLUIDMP=ALL,
SOLUTION = 90) = 20
Compute acoustic structural and fluid modal participation factors for pressure at grid point 11217 at
excitation frequencies 25Hz, 30Hz and 35Hz.
Computation and output of panel participation factors is controlled by the PFPANEL Case Control
command:
CHAPTER 8 241
Miscellaneous Enhancements
ALL
PFPANEL PRINT, PUNCH , REAL or IMAG , PANEL = ----------- ,
PLOT PHASE setp
ALL
[ SORT = sorttype ], [ KEY = sortitem ], ITEMS = ,
( itemlist )
ALL
SOLUTION = setf , [ FILTER = fratio ], [ NULL = ipower ]
NONE
= setdof
NONE
Example
SET 100 = 10., 12.
SET 200 = 1222, 1223
PFPANEL(SOLUTION=100, SORT=ABSD) = 200
Compute acoustic panel participation factors for pressure at grid points 1222 and 1223 at excitation
frequencies 10Hz and 12Hz. Output is sorted according to descending modal fractions.
Computation and output of grid participation factors is controlled by the PFGRID Case Control
command:
ALL
PFGRID PRINT, PUNCH , REAL or IMAG , GRIDS =
PLOT PHASE setg
ALL
setdof
SOLUTION = setf =
NONE
NONE
Example
SET 20 = 11217
SET 90 = 25., 30., 35.
PFGRID(SOLUTION = 90) = 20
Compute acoustic grid participation factors for the pressure at grid point 11217 at excitation frequencies
25Hz, 30Hz and 35Hz.
Detailed descriptions of the PFMODE, PFPANEL and PFGRID Case Control Commands can be found
in the Quick Reference Guide.
242 MD Nastran 2006 Release Guide
Panels are defined in the Bulk Data Section using PANEL Bulk Data entries which reference SET1 or
SET3 Bulk Data entries.
• SET1 Bulk Data entries list the grid points of the panels.
• SET3 Bulk Data entries with option ELEM list the elements of the panels. The panels consist of
all grid points associated to these elements.
• SET3 Bulk Data entries with option PROP list the property identifiers of the elements of the
panels. The panels consist of all grid points associated to the elements with the property
identifiers defined.
Output
Output can be printed to the .f06 file, written to the .pch file or the .op2 file or stored in the database for
later access by SimOffice.
Three different formats are used for printed output to the .f06 files. The format for modal participation
factors is similar to the format obtained with the MCFRACTION command. The header contains the type
of the participation factor, information on the grid point and degree of freedom considered, the total
response, information on excitation frequency, subcase and load and information on the maximum modal
response, the sort method and the filter. In case of acoustic panel modal participation factors, the header
contains the name of the panel considered and the panel response instead of the total response.
The data are presented in ten columns:
The format for acoustic panel participation factors is the same as for modal participation factors, except
that the first two columns contain the panel names.
CHAPTER 8 243
Miscellaneous Enhancements
Load participation factors are included in the acoustic structural modal participation factors and the
acoustic panel participation factors, with a mode number of 0 and a panel name –LOAD-. Acoustic
structural modal participation factors, together with the load participation factor, sum up to the total
response.
Acoustic grid participation factors use the output format of complex displacements. Both real and
imaginary part or magnitude and phase format are available. There is one output per excitation frequency
and fluid grid point.
Example
The numbers printed indicate the normalized acoustic pressure at the selected grid point due to the
accelerations at the corresponding degrees of freedom.
Guidelines
The amount of output produced may be very large. This is especially true for acoustic panel mode
participation factors and for acoustic grid participation factor (e.g., the number of data produced for
acoustic panel modal participation factors equals the number of subcases times the number of excitation
frequencies times the number of response degrees of freedom times the number of panels times the
number of structural modes). Consequently, output should be limited to a small number of excitation
frequencies and to a small number of response degrees of freedom.
244 MD Nastran 2006 Release Guide
Limitations
In the current version, acoustic participation factors are not computed correctly in case of direct enforced
motion.
Example
The example shows the acoustic analysis of a cabin. The cabin is excited by four forces at the corners of
the seat. The result of interest is the pressure at the driver’s ear.
The frequency response of the pressure shows a peak at 37Hz. To investigate this peak, acoustic fluid and
structure modal participation factors and panel participation factors are requested at a frequency of 37Hz.
Panels are defined for the front window, the rear wall, the left and the right side, the top and the bottom.
Input Data
$ Participation Factor Test Problem: Cabin
$
$ Coupled Modal Frequency Response Analysis
$
$ Participation Factor Example - Cabin
CHAPTER 8 245
Miscellaneous Enhancements
$
$ Illustrates use of
$ o Acoustic Fluid Modal Participation Factors
$ o Acoustic Struct. Modal Part. Factors
$ o Acoustic Panel Part. Factors
$ o Acoustic Grid Part. Factors
$
$ =======================================================
$
SOL 111
DIAG 8
CEND
$
ECHO=SORT(EXCEPT,CBEAM,CQUAD4,CHEXA,CPENTA,GRID)
AUTOSPC(NOZERO) = YES
$
METHOD(STRUCTURE)=1
METHOD(FLUID) =2
$
FREQ = 100
DLOAD = 200
$
SET 1 = 11217
SET 20 = 11217
SET 90 = 37.
$
246 MD Nastran 2006 Release Guide
DISP(PHAS) = 1
$
PFMODE(FLUID, STRUCTMP=ALL, FLUIDMP=ALL,
SOLUTION=90, SORT=ABSD) = 20
PFPANEL(SOLUTION=90, SORT=ABSD) = 20
$
OUTPUT(XYPLOT)
XPAPER=29.
YPAPER=21.
XGRID=YES
YGRID=YES
XTITLE = Frequency
YTITLE = Pressure
XYPLOT DISP RESPONSE / 11217(T1)
$
BEGIN BULK
$
$ Request OP2 for PATRAN
PARAM, POST, -1
$
$ Define Structural Damping
PARAM, G, 0.02
$
$ Define Fluid Damping
PARAM, GFL, 0.002
$
$ Define Reference Pressure for dB (in Pa)
PARAM, PREFDB, 2.8284-5
$
PARAM, GRDPNT, 0 $ Request Weight Output
$
$ Structural and Acoustic Modes up to 300Hz
EIGRL, 1,,300.
EIGRL, 2,,300.
$
$ Frequency Range: 25Hz to 100Hz by Steps of 5Hz
FREQ1, 100, 25., 5., 15
$ Additional Frequencies around Resonance Frequencies
FREQ4, 100, 25., 100., 0.01, 5
$
$ Excitation Forces
RLOAD1, 200, 210,,, 220
DAREA, 210, 1, 3, 1., 7, 3, 1.
DAREA, 210, 29, 3, 1., 35, 3, 1.
TABLED1, 220
, 0., 1., 1000., 1., ENDT
$
$ Nonmatching Fluid-Structure Interface
ACMODL, DIFF
$
$ Include Structural and Acoustic Model
INCLUDE 'cabin_structure.bdf'
INCLUDE 'cabin_fluid.bdf'
$
CHAPTER 8 247
Miscellaneous Enhancements
$ Panels
$
SET3, 101, ELEM, 127, THRU, 162, 667, THRU, 738
SET3, 201, ELEM, 37, THRU, 72, 739, THRU, 810
SET3, 301, ELEM, 331, THRU, 384
SET3, 401, ELEM, 25, THRU, 36, 73, THRU, 126
SET3, 501, ELEM, 271, THRU, 294, 601, THRU, 612
SET3, 601, ELEM, 1, THRU, 24, 455, THRU, 478,
, 497, THRU, 562
$
PANEL, LEFT, 101, RIGHT , 201, FRONT, 301, REAR, 401
PANEL, TOP , 501, BOTTOM, 601
$
ENDDATA
Acoustic Structural Mode Participation Factors:
248 MD Nastran 2006 Release Guide
The acoustic structural mode participation factors show that the largest contribution comes from the 7th
structural mode which has a resonance at 37.2Hz. The acoustic panel participation factors show that the
rear wall and the bottom make the largest positive contribution whereas all remaining panels make
negative contributions.
CHAPTER 8 249
Miscellaneous Enhancements
Introduction
Total Strain Energy output can now be requested for user defined element SETs.
Inputs
A new Case Control command, SETP described below is introduced for defining the list of element
SETs, which are referenced by the ESE – Element Strain Energy Output request.
Formats
SETP n = {i1[,i2,i3 THRU i4 EXCEPT i5,i6,i7,i8 THRU i9]}
Examples
SET 77=5
SET 88=5, 6, 7, 8, 9, 10 THRU 55
Describer Meaning
n SETP identification number. Any SETP may be redefined by reassigning its
identification number. SETPs specified under a SUBCASE command are
recognized for that SUBCASE only. (Integer > 0)
SET Identification numbers. If no such identification number exists, the request
is ignored. (Integer > 0)
EXCEPT Set identification numbers following EXCEPT will be deleted from output list as
long as they are in the range of the set defined by the immediately preceding
THRU. An EXCEPT list may not include a THRU list or ALL.
Remarks:
1. A SETP command may be more than one physical command. A comma at the end of a physical
command signifies a continuation command. Commas may not end a set. THRU may not be used
for continuation. Place a number after the THRU.
2. Set identification numbers following EXCEPT within the range of the THRU must be in
ascending order.
250 MD Nastran 2006 Release Guide
In SET 88 above, the numbers 77, 78, etc., are included in the set because they are outside the
prior THRU range.
3. SETP usage is limited to the EDE, EKE, and ESE Case Control Commands.
Example
A small example (see setp01.dat in the examples folder) is shown below to show usage of the SETP
command. Note only essential entries are shown.
id msc, setp $
TIME 6
SOL 101
CEND
SPC=1
setp 100 = 1 thru 43
set 1 = 1
set 2 = 2
set 3 = 3
set 4 = 4
set 5 = 5
set 6 = 6
set 7 = 7
set 8 = 8
set 9 = 9
.
.
SUBCASE 1001
LOAD=101
ese = 100
SUBCASE 1002
LOAD=102
ese = 100
BEGIN BULK
CQUAD4 1 1 1 2 9 8
CQUAD4 2 1 2 3 10 9
CQUAD4 3 1 3 4 11 10
CQUAD4 4 1 4 5 12 11
CQUAD4 5 1 5 6 13 12
CQUAD4 6 1 6 7 14 13
CQUAD4 7 1 8 9 16 15
CQUAD4 8 1 9 10 17 16
CQUAD4 9 1 10 11 18 17
.
.
ENDDATA
CHAPTER 8 251
Miscellaneous Enhancements
Output Example
An excerpt of the element strain energy output for the example is shown below:
0 SUBCASE 1001
E L E M E N T S T R A I N E N E R G I E S
0 SUBCASE 1001
E L E M E N T S T R A I N E N E R G I E S
Introduction
A new feature has been introduced that provides users with a simple means to evaluate the mass and
thermal load characteristics of a structure. The feature is intended primarily for linear static analysis runs
that are being used to validate aspects of the finite element model prior to embarking on more expensive
production static and dynamics analyses. It allows the user to temporarily modify the material density
and thermal expansion coefficient fields of material property bulk data entries. To implement the feature,
the new MODEL_CHECK Executive Control statement and several NASTRAN Statement keywords
have been introduced. Use of the feature causes the affected material property fields to be temporarily
modified during the run. All results will be based on the temporary values of the material properties. The
material property data stored on the Material Property Table data block is not modified and retains the
original values supplied on the bulk data entries.
Benefits
The introduction of this new feature simplifies the procedure typically used to evaluate the mass and
thermal load characteristics of a finite element model. This procedure usually involves preparation,
usage and storage of a duplicate set of bulk data material property entries that have the material density
and thermal expansion coefficient values set to the values desired for model checkout purposes. When
the model is undergoing checkout procedures, the production set of bulk data material property entries is
replaced by the alternate set of bulk data material property entries. Creating and switching between the
two sets of data for production and checkout runs is tedious and prone to errors. The material property
update options of the MODEL_CHECK statement improve user productivity by reducing the need to
create, maintain and substitute different sets of material properties needed for model check purposes.
Inputs
This feature is activated using the new MODEL_CHECK Executive Control statement. The
MODEL_CHECK statement features keywords that allow a value to be temporarily assigned to the
CHAPTER 8 253
Miscellaneous Enhancements
material density and thermal expansion coefficients. The general format of the statement used to change
material properties to a specified value is:
MODEL_CHECK [ MAT_DENSITY=value, ] [ MAT_TECO=value, ] [ MAT_TEIJ=value ]
The complete description of the MODEL_CHECK statement can be found in Executive Control
Statement Descriptions (p. 108) in the MD Nastran Quick Reference Guide.
Outputs
The MODEL_CHECK material property update feature produces no printed output other than an
informational message summarizing the updates that will take place.
Demonstration Example
A simple example is presented that demonstrates the material property update feature. The example
consists of several disjoint models and is not intended to be representative of any production model. The
MODEL_CHECK statement is used to temporarily set all material densities and thermal expansion
coefficients to 0.0. This results in model mass contributions from only the CONM2 element and the non-
structural mass as well as results for the temperature load case (subcase 3) being null.
SUBCASE 3
LABEL = TURN ON TEMP LOADS
TEMP(LOAD) = 2
$
BEGIN BULK
$
$ C O M M O N D A T A T O A L L P R O B L E M S
PARAM, SNORM, 0.
$
CORD2C 1 0 3.0 -1.0 0.0 9.0 -1.0 0.0 +CORD2C
+CORD2C 9.0 0.0 -1.0
$
CORD2R 2 0 0.0 -2.0 0.0 1.011234-2.0 0.0 +CORD2R
+CORD2R 0.0 0.0 0.0
$
CORD2S 3 1 3.0 225.0 0.0 3.0 225.0 1.234567+CORD2S
+CORD2S 3.0 -45.0 3.0
$
GRAV 3 1.0 1.0 1.0 1.0
TEMPD 1 100.0
TEMPD 2 200.0
$
MAT1 1 1. .8 .1 .05 .001 100. .01 +MAT11
+MAT11 2.0 3.0 4.0
MATT1 1 2 +MATT1
+MATT1 4 5 6
$
MAT1 2 1.0E+7 0.3 .05 .001 100.0 .01 +MAT1-2
+MAT1-2 1000. 2000. 3000.
MATT1 2 +MATT1-2
+MATT1-2 2 2
$
MAT2 22 1.0E+7 0.5E+6 0.5E+6 1.0E+7 0.5E+6 1.0E+7 .022 +MAT221
+MAT221 .01 .02 .025 100.0 0.035
MATT2 22 +MATT221
+MATT221
$
MAT3 33 1.0E+7 1.0E+7 1.0E+7 .33 .33 .33 .00259 +MAT331
+MAT331 2.4E+6 .001 .001 .001 100. .025
MATT3 33 +MATT331
+MATT331
$
MAT8 3 1.E+7 1.E+7 .25 4.E+6 4.E+6 4.E+6 1.0 +MAT81
+MAT81 1.-6 2.-6 1.E-4 1.E-3 1.E-4 +MAT82
+MAT82 1.0
$
MAT9 9 1.E+7 1.E+7 +MAT91
+MAT91 1.E+7 +MAT92
+MAT92 5.1+3 5.1+3 5.1+3 .05 .001 +MAT93
+MAT93 .002 .003 .004 .005 .006 100.0 .008
MATT9 9 +MATT91
+MATT91 +MATT92
+MATT92 +MATT93
+MATT93
$
TABLEM1 2 +TABLE-2
+TABLE-2 0.0 1.0 150.0 1.0 150. 0.5 300. 0.5 +TABL-2
+TABL-2 ENDT ENDT
TABLEM2 3 100.0 +TABLE-3
+TABLE-3 0.0 0.1 50.0 0.1 50.0 0.5 150.0 0.5 +TABL-3
256 MD Nastran 2006 Release Guide
$+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++
$
$ DUM1 ELEMENT NO. 53
$
$ADUM1,6,3,0,3,CTRIAX6 $
CTRIAX6 5301 33 5301 5302 5303 5304 5305 5306 +TRIAX61
+TRIAX6130.0
GRID 5301 0 6.0 0.0 0.0 0 2456
GRID 5302 0 6.0 0.0 2.0 0 2456
GRID 5303 0 6.0 0.0 4.0 0 2456
GRID 5304 0 4.238 0.0 3.0 0 2456
GRID 5305 0 2.536 0.0 2.0 0 2456
GRID 5306 0 4.238 0.0 1.0 0 2456
SPC1 1 3 5302
PLOADX 1 .0222139.03332095301 5302 5303
$
$+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
++++
$
$ CONM2 ELEMENT NO. 30
$
CONM2 3001 3001 0 1.0 1.0 1.0 1.0 +CONM21
+CONM21 1.0 1.0 1.0 1.0 1.0 1.0
GRID 3001 0 0.0 0.0 0.0
SPC 1 3001 123456 0.0
$
$========================================================================
$
$ DMIG ELEMENT NO. 100
$ NOTE:P.S. 3 ADDED 14-JAN-82
GRID 10000
GRID 10001 3
DMIG MATK 0 6 2 0
DMIG MATK 10000 3 10000 3 1.D6 +
10001 3 -1.D6
DMIG MATK 10001 3 10001 3 1.D6
DMIG MATLOAD 0 9 1 0
DMIG* MATLOAD 1 +DMIG
*DMIG 10000 3 1.
DMIG* MATLOAD 2 +DMIG2
*DMIG2 10000 3 0.
$
enddata
Example Output
The printed output for the example problem consists of all of the output typically generated by a static
analysis for the requests present in the case control section of the input and is not reproduced here. There
is a small section of additional printed output generated in the Executive Control Echo region when the
MODEL_CHECK material property options are used. The output summarizes the requested material
property updates and is shown on the next several lines.
CHAPTER 8 259
Miscellaneous Enhancements
$
MODEL_CHECK MAT_DENSITY=OFF,
MAT_TECOEFF=OFF,MAT_TEIJ=OFF
*******************************************************************************************************
*******************************************************************************************************
* *
* THE PRESENCE OF THE MODEL_CHECK EXECUTIVE STATEMENT CAUSES THE FOLLOWING MATERIAL *
* PROPERTY VALUES TO BE MODIFIED FOR EVERY MAT1, MAT2, MAT3, MAT8 AND MAT9 MATERIAL *
* PROPERTY ENTRY PRESENT IN THE INPUT BULK DATA SECTION: *
* MATERIAL DENSITY REVISED VALUE = 0.00000E+00 *
* THERMAL EXP. DIRECT COEFF. REVISED VALUE = 0.00000E+00 *
* THERMAL EXP. SHEAR COEFF. REVISED VALUE = 0.00000E+00 *
* *
*******************************************************************************************************
*******************************************************************************************************
There is no other printed output generated that is peculiar to the material property update feature. All
other output is typical printed output that is generated by the case control requests. For this example, the
Grid Point Weight Generator output was requested via param,grdpnt,0 in the bulk data so that the mass
of the structure could be verified as being produced by only the CONM2 element and the element non-
structural mass.
260 MD Nastran 2006 Release Guide