Professional Documents
Culture Documents
Release Guide
Main Index
Corporate Europe Asia Pacific
MSC.Software Corporation MSC.Software GmbH MSC.Software Japan Ltd.
2 MacArthur Place Am Moosfeld 13 Shinjuku First West 8F
Santa Ana, CA 92707 81829 Munich 23-7 Nishi Shinjuku
Telephone: (800) 345-2078 GERMANY 1-Chome, Shinjuku-Ku
FAX: (714) 784-4056 Telephone: (49) (89) 43 19 87 0 Tokyo 160-0023, JAPAN
Fax: (49) (89) 43 61 71 6 Telephone: 0120-924-832 (toll free,
Japan only)
Mobile phone: 03-6911-1222
Fax: (81) (3)-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 2010 MSC.Software Corporation. Printed in U.S.A. All Rights Reserved.
This notice shall be marked on any reproduction of this documentation, in whole or in part. Any reproduction or
distribution of this document, in whole or in part, without the prior written consent of MSC.Software Corporation is
prohibited.
This software may contain certain third-party software that is protected by copyright and licensed from
MSC.Software suppliers. PCGLSS 6.0, Copyright © 1992-2005, Computational Applications and System
Integration Inc. All rights reserved. PCGLSS 6.0 is licensed from Computational Applications and System
Integration Inc. METIS is copyrighted by the regents of the University of Minnesota. A copy of the METIS product
documentation is included with this installation. Please see "A Fast and High Quality Multilevel Scheme for
Partitioning Irregular Graphs". George Karypis and Vipin Kumar. SIAM Journal on Scientific Computing, Vol. 20,
No. 1, pp. 359-392, 1999.
MSC, MD, Dytran, Marc, MSC Nastran, MD Nastran, Patran, MD Patran, the MSC.Software corporate logo,
OpenFSI 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.
Revision 0. October 5, 2010
NA:V2010:Z:Z:Z:DC-REL-PDF
Main Index
Contents
MSC Nastran 2010 Release Guide
MSC Nastran 2010
Release Guide
Table of Contents
Preface to the MSC Nastran 2010 Release Guide viii
List of Books ix
Technical Support x
Internet Resources xi
5 Optimization
Part Superelement Optimization Enhancements 44
Main Index
iv MSC Nastran 2010 Release Guide
Parallel Sensitivities 64
6 Aeroelasticity
Input of Pressures on an Aerodynamic Mesh 96
7 Elements
Enhancements to Connector Elements 114
8 Miscellaneous
Enhanced MONSUM 134
Main Index
Contents v
A Connectors
Connectors Output 146
Main Index
vi MSC Nastran 2010 Release Guide
Main Index
MSC Nastran Release Guide Preface
Preface
Preface to the MSC Nastran 2010 Release Guide
List of Books
Technical Support
Internet Resources
Main Index
viii MSC Nastran 2010 Release Guide
Preface to the MSC Nastran 2010 Release Guide
Main Index
Preface ix
List of Books
Listed below are some of the Nastran documents. You may find any of these documents from
MSC.Software at www.simcompanion.mscsoftware.com.
Reference Books
• Quick Reference Guide
• DMAP Programmer’s Guide
• Reference Manual
User’s Guides
• Getting Started
• Linear Static Analysis
• Dynamic Analysis
• MD Demonstration Problems
• Thermal Analysis
• Superelements
• Design Sensitivity and Optimization
• Implicit Nonlinear (SOL 600)
• Explicit Nonlinear (SOL 700)
• Aeroelastic Analysis
• User Defined Services
• EFEA User’s Guide
• EFEA Tutorial
• EBEA User’s Guide
Both MD Nastran and MSC Nastran books are listed for your convenience.
Main Index
x MSC Nastran 2010 Release Guide
Technical Support
Technical Support
For technical support phone numbers and contact information, please visit:
http://www.mscsoftware.com/Contents/Services/Technical-Support/Contact-Technical-Support.aspx
Support Center (http://simcompanion.mscsoftware.com)
Support Online. The Support Center provides technical articles, frequently asked questions and
documentation from a single location.
Main Index
Preface xi
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.
Main Index
xii MSC Nastran 2010 Release Guide
Internet Resources
Main Index
Chapter 1: Overview of MSC Nastran 2010 MSC Nastran Release Guide
Overview
Main Index
2 MSC Nastran 2010 Release Guide
Overview
Overview
MSC.Software is pleased to introduce you to the exciting new technologies in MSC Nastran 2010, the
premier and trusted CAE solution for aerospace, automotive, defense, and manufacturing industries
worldwide. This release includes a wide range of new features and enhancements to our nonlinear
implicit (SOL 600) solution and our linear solutions in the areas of durability and NVH, Optimization,
and Aeroelasticity.
More information on Implicit Nonlinear (SOL 600) can be found in Implicit Nonlinear (SOL 600) (Ch. 2).
More information can be found in Numerical Methods and High Performance Computing (Ch. 3).
More information can be found in Dynamics (Noise and Vibration) (Ch. 4).
Optimization
• PART Superelement Optimization
• Integer Input for DTABLE
• Optimization - Invariant DRESP3 Gradients
Main Index
CHAPTER 1 3
Overview of MSC Nastran 2010
More information on these optimization enhancements can be found in Optimization (Ch. 5).
Aeroelastic Enhancements
• Aeroelasticity - Output of Trimmed Loads
• CSV Output of Trim Results
Elements
• Connector for Durability
• Offsets Support for Buckling
Main Index
4 MSC Nastran 2010 Release Guide
Overview
Main Index
Chapter 2: Implicit Nonlinear (SOL 600) MSC Nastran 2010 Release Guide
SOL 600 Enhancements
Main Index
6 MSC Nastran 2010 Release Guide
SOL 600 Enhancements
Introduction
MSC Nastran SOL 600 is a Solution Sequence that allows MSC.Nastran users to use the familiar MSC
Nastran input file format to execute complex nonlinear problems via a translation to MSC.Marc. Based
upon customer input since the MSC Nastran 2008 release, a series of enhancements have been made to
increase the functionality of the product.
Benefits
This allows a broader set of Nonlinear Problems to be solved within the Nastran framework. These
enhancements are outlined below:
• Added plane stress to add Marc’s capabilities – use the MRALIAS PARAM or the ALIASM
Bulk Data option
• Implemented PARAM,TSTATIC for dynamic analyses
• Added friction vs other variable described by tables capability – see BCBODY and /or
BCTABLE
• Better control of 2-D Rigid bodies Rx, Ry to for 2D rigid contact orientation
• Provide support for contact user subroutines ufric, ufricbbc, uhtcon, digeom, sepstr, spfor – see
BCBODY and BCONUDS
• Added rigid contact rigid surface temperature and sink temperature for heat transfer simulations
– see BCBODY and BCTABLE.
• Added new options for BCBOX, such that the user can specify if the complete element needs to
be in the box to be put in body, or only a single node.
• Allow contact variables such as velocity to be defined using tables.
• Added conversion of CHEXA and CPENTA to solid shell (customer request)
• Add delamination capabilities – see MDELAM Bulk Data entry
• Improved VCCT crack propagation so the path along the crack tip in 3-d can be easier to
describe - see VCCT Bulk Data Option – Not supported by GUI
• Add material mixtures capability – see MIXTURE Bulk Data entry
• SOL 600 now supports RSSCON
• SOL 600 now supports RSPLINE
• Added new type of RBE3 to uniformly distribute applied loads – see the RBE3U Bulk Data
entry. Note that this does not distribute stiffness.
• Added generalized alpha method for dynamics, this includes support for the Hilbert-Hughes-
Taylor (HHT) procedure. Use the HMOUBOLT Param and set dynamic operator to 7.
Main Index
CHAPTER 2 7
Implicit Nonlinear (SOL 600)
Table 2-1 New Parameters and Bulk Data Entries for SOL 600
New for MSC Nastran 2010 (SOL 600)
Description
Parameters
MARAUTO Determines whether NLAUTO entries for SOL 600,129 will override the
default or not
MARCTOTD Determines whether for SOL 600 dynamic analyses will use full table
association.
MARCTOTL Determines whether total or incremental loads are used in a SOL 600 static
nonlinear analysis.
MARCTOTT Determines whether total loads, including pressures, gravity, spcd, etc., with
associated tables are used in a SOL 600 static or dynamic analysis.
Main Index
8 MSC Nastran 2010 Release Guide
SOL 600 Enhancements
Table 2-1 New Parameters and Bulk Data Entries for SOL 600
New for MSC Nastran 2010 (SOL 600)
Description
MARCL001 Determines whether Marc’s POINT LOAD (without tables) 2nd datablock, 3rd
field will be honored or not. If this value is set to 1 multiple loads at the same
dof in the same subcase will usually be summed.
MARFATAL Determines whether non-existent grid id’s for BCBODY entries will cause fatal
errors or not.
MARTET10 Controls how to treat badly shaped 10-node tetra elements in SOL 600 if
renumbering the element does not correct problems.
MARTETIN Controls whether additional information messages are output to the .f06 file or
not when param,martet10 is set to a positive value.
MCORDUPD Determines the coordinates will be updated if one of the CONTINUE options is
specified on the SOL 600 Executive Control statement.
MINSOUTT Determines elements that deform so much that they go inside-out in an analysis
will be deactivated.
MMBOLTUS Controls how the top and bottom nodes are placed in the Marc “tying 69” input
when MBOLTUS is used in a SOL 600 model.
MQUATERN Controls whether quaternions will be used for SOL 600 models with large
rotation.
MREVPLST Determines whether 2D plain stress triangular element node numbers will be
reversed or not.
MRDYNOLD Determines whether dynamic loads created by SOL 600 are the same as in MSC
Nastran 2008 and prior releases or uses a new calculation method.
MRCONTAB Determines whether CONTACT and CONTACT TABLE for SOL 600 use
table-driven form or not.
MRPLOD4R Determines how PLOAD4 pressures are treated in Marc when
PARAM,MRPLOAD4,2 is set.
MRPOISCK Controls whether to check if a “bad” Poisson ratio has been entered in SOL 600
for MAT1 entries.
MRSPRVER Controls how CELAS and all other items map to the Marc input data.
MNASTLDS Option to determine complex force and/or moments using OLOAD’s as
calculated from SOL 101.
MSPLINC0 This parameter controls whether to enforce C0 continuity for all spline options
if any are requested by setting IDSPL=1 on any BCBODY entry.
MSTTDYNE Controls whether SOL 600 may have static and dynamic load cases in the same
analysis.
MTABIGNR Determines whether tables for VCCT analyses will be ignored or used.
Main Index
CHAPTER 2 9
Implicit Nonlinear (SOL 600)
Table 2-1 New Parameters and Bulk Data Entries for SOL 600
New for MSC Nastran 2010 (SOL 600)
Description
MTEMPCHK Controls how temperature-dependent properties are checked in the Marc
portion of SOL 600.
MTEMPDWN Option to automatically choose the FeFp multiplicative decomposition
plasticity model (PARAM,MARCPLAS,5) for plasticity problems with thermal
loading when the temperature decreases (see PARAM,MARCPLAS).
MTET4HYP Controls settings for TET4 elements with hyperelasticity.
MUALLUDS Controls how material, contact and element-related user subroutines are
specified in SOL 600.
MVERMOON Controls whether 5-term Mooney series or 5-constant Mooney will be used in
the Marc portion of SOL 600.
Bulk Data Entries
CSSHLH Defines conversion of CHEXA elements to Solid Shell elements in SOL 600
only.
CSSHLM Defines conversion of CHEXA or CPENTA elements described by material ID
to Solid Shell elements in SOL 600 only.
CSSHLP Defines conversion of CPENTA elements to Solid Shell elements in SOL 600
only.
DMIGROT Defines large rotation and other characteristics of a matrix entered using DMIG
in SOL 600.
ISTRESS Defines initial stress values. This is the MSC Marc’s initial stress option used in
SOL 600 only.
MATNLE The MATNLEx entries specify advanced forms of nonlinear elastic materials.
MATTUSR Specifies table variation of user defined generic materials in SOL 600 and
MD Nastran SOL 400 only.
MATUDS Allows the user to provide material routines for use with enhanced material
models in SOL 600.
MATUSR Specifies user-defined, generic material properties for hypoelastic material
models in SOL 600 and user defined material models in MSC Nastran SOL 400
only.
MAUXCMD Defines auxiliary command to spawn on Nastran process from another Nastran
process in SOL 600.
MDELAM Defines materials for which delamination may occur in SOL 600 only.
MDMIAUX Specifies the DOMAINSOLVER command to be used in conjunction with
secondary spawned jobs when MDMIOUT is used. SOL 600 only.
Main Index
10 MSC Nastran 2010 Release Guide
SOL 600 Enhancements
Table 2-1 New Parameters and Bulk Data Entries for SOL 600
New for MSC Nastran 2010 (SOL 600)
Description
MISLAND Defines an island of connected elements that will be completely removed if the
number of elements within the island becomes smaller than a specified value in
SOL 600 only.
MIXTURE Defines constituents of “composite” material on original and potentiality
damaged state.
PBMARB6 Defines arbitrary beam/bar cross section for use in SOL 600.
PBMNUM6 Defines four specific numerically integrated BEAM/BAR cross section for use
in SOL 600.
RBE3U Defines Method to Distribute Applied Loads to a Surface in SOL 600
TABD1MD Defines how TABLED1 entries are internally modified in SOL 600.
Additional Documentation
In addition to the MD Nastran Quick Reference Guide the user should refer to Marc Volume A for a
theoretical discussion of material models, fracture mechanics and dynamics. For additional information
on the nonlinear solid section beams one should refer to Marc Volume B.
Main Index
Chapter 3: Numerical Methods and High Performance Computing MSC Nastran 2010 Release
Guide
MPI Selection
New Solver Available for Complex Eigenvalue Analysis
Main Index
12 MSC Nastran 2010 Release Guide
MPI Selection
MPI Selection
A single analysis executable is now provided for serial execution as well as DMP execution with all
supported MPI implementations.
In previous versions:
• A separate analysis executable was delivered for DMP execution.
• If more than one MPI (Message Passing Interface) implementation was supported on a given
platform, a separate analysis executable had to be delivered for each supported MPI
implementation.
• An unsupported MPI implementation could not be used without creating a new, separate analysis
executable
Starting with MSC Nastran 2010, a single analysis executable will be delivered which can be used for
both DMP and serial jobs, and which can be used with any supported MPI implementation on a given
platform. Moreover, it is possible to use an unsupported MPI implementation with the same executable.
Main Index
CHAPTER 3 13
Numerical Methods and High Performance Computing
Introduction
The UMFPACK linear equation solver was first incorporated into Nastran in 2004. It was embedded in
the Auto-Mset capability, as well as integrated into the frequency response module (FRRD1) where it is
available for complex unsymmetric solutions. In MSC Nastran 2010, UMFPACK is available in the
complex Lanczos eigenvalue extraction method of the CEAD module.
More information about UMFPACK is available at the following URL:
http://www.cise.ufl.edu/research/sparse/umfpack/.
Benefits
The UMFPACK linear equation solver is more efficient than the default Nastran sparse unsymmetric
solver. This is accomplished by employing contemporary matrix reordering techniques and
computational kernels.
Inputs
To invoke the UMFPACK solver for complex eigenvalue analysis, the UMFLU keyword must be
specified as the factorization method, which must be present on the SPARSESOLVER Executive
Command:
SPARSESOLVER CEAD (FACTMETH=UMFLU)
Outputs
Use of UMPACK will cause User Information Message 4216 is appear in the F04 file:
11:04:19 0:25 5969.0 948.0 15.6 1.2 UMFD BGN
*** USER INFORMATION MESSAGE 4216 (FACDRVI)
PARAMETERS FOR IN-CORE SPARSE UNSYM. DECOMP ( MATRIX TYPE=RDP) FOLLOW
MATRIX SIZE =185931 ROWS NUMBER OF NONZEROES =12587614 T
NUMBER OF ZERO COLUMNS =0 NUMBER OF ZERO DIAGONAL TERMS =0
MEMORY REQUIREMENT = 147711 K WORDS MEMORY AVAILABLE = 496541 KWO
MAX FRONT SIZE = 2964 NONZERO TERMS = 67880689
11:04:44 0:50 7013.0 1044.0 40.7 25.2 UMFD END
Main Index
14 MSC Nastran 2010 Release Guide
New Solver Available for Complex Eigenvalue Analysis
Demonstration Example
An example models is shown here.
Main Index
CHAPTER 3 15
Numerical Methods and High Performance Computing
Example
Main Index
16 MSC Nastran 2010 Release Guide
New Solver Available for Complex Eigenvalue Analysis
Main Index
Chapter 4: Dynamics (Noise and Vibration)
MSC Nastran 2010 Release Guide
Equivalent Radiated Power (ERP)
Frequency Dependent Rigid Absorber Properties
Dynamics - Monitor Points in Dynamic Solution Sequences
Main Index
18 MSC Nastran 2010 Release Guide
Equivalent Radiated Power (ERP)
Introduction
In automotive applications, the noise inside the passenger compartment can be caused by many sources
including vehicle drive train and vibrating body panels. The Equivalent Radiated Power (ERP)
calculation focuses on the vibration of body panels, which radiate acoustic power to the passenger cabin.
Understanding which panels are responsible for the radiated power is important in understanding the
structural behavior and acoustic consequences. The radiated power is a function of skin normal velocity,
fluid density and speed of sound through the fluid.
Benefit
The ERP calculation can be used to compare laser measurements to calculated values in a quantitative
way to validate calculations. ERP can also be used during the design phase to understand the effect of
individual panels on the overall acoustic response. Previously the calculation was performed by in-house
tools. In MSC Nastran 2010 the ERP calculation is made directly by the solver and provides convenient
output in the form of a CSV file.
Theory
In a mathematical sense, ERP squares the normal velocity and multiplies it with the element area. The
sum over this product, multiplied with a constant yields the ERP over a panel. ERP values can be
calculated for both structure and structure-fluid models.
panel
2
ERP = C V n S
surf
RHOCP
ERPdB = 10LOG --------------------------------- ERP v a lu e
ERPREFDB
Main Index
CHAPTER 4 19
Dynamics (Noise and Vibration)
Input
The ERP calculation is typically requested for a group of elements defined on a SET3 Bulk Data entry.
The parameters ERPRHO, ERPC, ERPRLF, ERPREFDB, and RHOCP can be defined on either the ERP
Case Control command, or as PARAM entries in the Bulk Data Section. The RHOCP parameter can only
be specified on the ERP Case Control command. The ERP Case Control also references an ERPPNL
Bulk Data entry.
The new Bulk Data entry for ERPPNL is:
Format:
1 2 3 4 5 6 7 8 9 10
ERPPNL NAME1 SETID1 NAME2 SETID2 NAME3 SETID3 NAME4 SETID4
NAME5 SETID5
Example:
Field Contents
NAMEi Panel label. (CHAR)
SETIDi Identification number of a SET3 Bulk Data entry that lists the panel property entries
or the panel elements. (Integer > 0)
Remarks:
1. The SET3 entries can only refer to CQUAD4, CQUADR, CTRIA3, or CTRIAR structural
elements or PSHELL or PCOMP property entries. CQUAD8 and CTRIA6 entries are ignored.
2. NAMEi are used in a Case Control SET definition defining setp to select the panels in the Case
Control command ERP.
Main Index
20 MSC Nastran 2010 Release Guide
Equivalent Radiated Power (ERP)
Requests the form and type of ERP panel participation factor output.
Format:
frequency 0.01
KEY = FILTER = ,
fraction real _value
1.0 1.0
ERPRHO = ERPC =
real _value real _value
1.0 1.0
RHOCP = ERPRLF =
real _value real _value
ALL
1.0
ERPREFDB = CSV = unit = setp
real _value
NONE
Examples:
SET 17 = 10.,20.,30.,40.,80.,100. $ A list of frequencies
SET 25 = ROOF, DOORLF $ A list of ERP Panel names
$ from a ERPPNL Bulk Entry
ERP ( PRINT,PUNCH,SOLUTION=17,KEY=frac ) = 25
Describer Meaning
SORT1 Output is presented as a tabular listing of ERP panels for each frequency.
SORT2 Output is presented as a tabular listing of frequency for each ERP panel.
PRINT Output is written to the .f06 file
PUNCH Output is written to the .pch file
PLOT Results are computed and placed on the ERP table but not output.
SOLUTION Keyword to select frequencies
setf Identifier of Case Control SET command defining frequencies.
Main Index
CHAPTER 4 21
Dynamics (Noise and Vibration)
Describer Meaning
ALL If associated with SOLUTION, all frequencies are selected. If associated with setp, all
ERPPNL entries are selected.
KEY Keyword selecting the output item used to sort the printed output. The default produces
output sorted on either frequency (SORT2) or ERP panel name (SORT1).
KEY=fraction produces output sorted in descending order of the fractional ERP value
of total ERP.
FILTER Keyword specifying the value of a filter to b e applied to the printed output only. ERP
values are printed only if the fractional ERP value of total ERP exceeds the filter value.
ERPRHO Fluid density for Equivalent Radiated Power (ERP) analysis. This item is actually an
MSC Nastran parameter.
ERPC Phase speed of the fluid for Equivalent Radiated Power (ERP) analysis. This item is
actually an Nastran parameter.
ERPRLF Radiation loss factor. In frequency the scale factor C = ERPRLF * (½ERPRHO *
ERPC). In transient the scale factor C = ERPRLF * (ERPRHO * ERPC).
RHOCP Scale factor used in dB computation. This item is actually an MSC Nastran parameter.
ERPREFDB Scale factor used in dB computation. This item is actually an MSC Nastran parameter.
ERP
The dB calculation is ERPdB = 10 log RHOCP -----------------------------
- .
ERPREFDB
Remarks:
1. ERP is required to produce any ERP output.
2. Output is generated in SORT2 by default. Unlike other Case Control requesting SORT2 format,
the ERP command does not force all other output into SORT2 format.
3. FILTER has no effect on PUNCHed, CSV or OP2 output.
4. In addition to individual panel output a summary named ALLPANEL is produced. If there are
multiple subcases, the panel name is formed from the serial subcase number (1-nsubc) and the
characters ‘ALLP’ as in ALLP0002 unless the ERP command request output for ALL panels
across the Subcases. In this case, the summary panel name ALLPANEL is retained.
5. Selectable frequencies are dependent on the presence of an OFREQ Case Control command.
6. ERPRHO, ERPC, ERPRLF, RHOCP, and ERPREFDB are actually PARAM,name,value entries.
Main Index
22 MSC Nastran 2010 Release Guide
Equivalent Radiated Power (ERP)
7. The filter process avoids printing ERP for cases where ERP/ERPMAX is less than the FILTER
value. ERPMAX is the maximum ERP value across all frequencies for a panel.
8. If output to a .csv file is requested, the file must be assigned with logical key USERFILE and
FORM=FORMATTED, e.g.,
ASSIGN USERFILE = myfile.csv UNIT=50 FORM=FORMATTED STATUS=NEW
The SET3 Bulk Data entry is also necessary to define.
Set 3 Examples:
• Set3,id,prop,pshellid1,pshellid2,etc.
• Set3,id,elem,elemid1,elemid2,etc.
• Set3 prop, can be exchanged between acoustic and ERP panels
See Bulk Data entry SET3 (p. 3119) in the MD/MSC Nastran Quick Reference Guide. Also see the Bulk
Data entry ERPPNL (p. 1816) in the MD/MSC Nastran Quick Reference Guide.
Example Input
The following input is typical for ERP calculation including CSV output.
File Management
ASSIGN USERFILE=’myerp.csv’ UNIT=30 FORMATTED NEW DELETE
Case Control
ERP(PUNCH,Filter=0.0,rhocp=2.0E9,ERPRHO=1.189E-12,ERPC=3.43E5,CSV=30)=ALL
Output
The results are available in the OP2, MASTER, Print, Punch, and CSV formats. The output includes ERP,
Fraction, and ERP(dB). Note that the fraction is not based on the entire ERP of the model, just the ERP
that is calculated and there is no check for overlapping or missing elements. There is also a summation
of total ERP. Both SORT1 and SORT2 options are available.
Main Index
CHAPTER 4 23
Dynamics (Noise and Vibration)
Test Cases
The following test cases are available in the TPL in directory /tpl/erp_mdr4:
erp_1000.dat, erp_base1_frac.dat, erp_base2_frac.dat, erp_c_param.dat, erp_erpx3.dat, erp_fs.dat,
erp_rhocp.dat, erp_soln.dat, erp_base1.dat, erp_base2.dat, erp_c.dat, erp_def.dat, erp_frac_c.dat,
erp_ofreq.dat, erp_rho.dat
Main Index
24 MSC Nastran 2010 Release Guide
Equivalent Radiated Power (ERP)
The input for erp_base1.dat is a standard modal frequency response with a pressure loading and including
fluid-structure interaction. The case control and bulk data entries required for ERP calculation are as
follows:
Case Control
ERP(PRINT,PUNCH,FILTER=0.0)=ALL
FREQUENCY = 8.000000E+00
E Q U I V A L E N T R A D I A T E D P O W E R
Main Index
CHAPTER 4 25
Dynamics (Noise and Vibration)
To obtain CSV output, an ASSIGN statement is added and the ERP case control is modified as follows:
ASSIGN USERFILE='MYERP.CSV' UNIT=30 FORMATTED NEW DELETE
ERP(PRINT,PUNCH,SORT1,FILTER=0.0,CSV=30) = ALL
The resulting CSV file is easily manipulated into a graph using Microsoft Excel, or other programs that
understand CSV format. Note that the graph shown in Figure 4-3 is based on a modified erp_base1.dat
file that has a FREQ1 entry with more output frequencies. Note that the panels that contribute to the
overall ERP switch at the frequencies of 31 and 33Hz.
Listing 4-3 TPL example erp_base1.dat Output in CSV format (partial listing)
Subcase, 1000
" EQUIVALENT RADIATED POWER IN PANELS OF QUAD4S
"
" ALL IN 1 SUBCASE
"
" FIRST SUBCASE (1000) SUBCASE 1000 "
Equivalent Radiated Power
, ERP , ERP , Fraction , Fraction , ERP(dB) , ERP(dB)
Area , 1.00000E+01, 1.90000E+01, 1.00000E+01, 1.90000E+01, 1.00000E+01, 1.90000E+01
Frequency , ERPX0 , ALLPANEL , ERPX0 , ALLPANEL , ERPX0 , ALLPANEL
2.00000E+00, 3.60158E-03, 7.82186E-03, 1.00530E-04, 1.55386E-04,-2.44351E+01,-2.10669E+01
4.00000E+00, 3.66840E-04, 1.86478E-03, 1.02395E-05, 3.70450E-05,-3.43552E+01,-2.72937E+01
6.00000E+00, 9.09168E-02, 2.00855E-01, 2.53775E-03, 3.99009E-03,-1.04136E+01,-6.97118E+00
8.00000E+00, 2.70249E-02, 3.18962E-02, 7.54341E-04, 6.33637E-04,-1.56824E+01,-1.49626E+01
1.00000E+01, 5.50420E+00, 7.52376E+00, 1.53638E-01, 1.49464E-01, 7.40694E+00, 8.76435E+00
1.20000E+01, 2.83194E-01, 4.29973E-01, 7.90474E-03, 8.54165E-03,-5.47917E+00,-3.66559E+00
1.40000E+01, 3.58258E+01, 5.03383E+01, 1.00000E+00, 1.00000E+00, 1.55420E+01, 1.70190E+01
1.60000E+01, 2.49801E-02, 5.04161E-02, 6.97266E-04, 1.00154E-03,-1.60241E+01,-1.29743E+01
Main Index
26 MSC Nastran 2010 Release Guide
Equivalent Radiated Power (ERP)
Main Index
CHAPTER 4 27
Dynamics (Noise and Vibration)
GUI Support
Neither SimXpert nor Patran currently support pre or post processing of ERP. However, the CSV output
provides a convenient interface for users who want to generate plots using Microsoft Excel.
Main Index
28 MSC Nastran 2010 Release Guide
Frequency Dependent Rigid Absorber Properties
Introduction
The capability to model basic rigid skeleton porous absorber properties in acoustic response analysis was
introduced in MSC Nastran 2007. It allows modeling some types of absorbent material such as vehicle
seat structures or lining materials with stiff carcasses.
The absorber material is described taking into account an equivalent fluid analogy and is modeled as
standard fluid elements using:
The limitation for MSC Nastran 2007 implementation is that the normalized admittance coefficient
cannot be defined as frequency dependent.
In MSC Nastran 2010 the frequency dependency for this coefficient has been implemented. The new
option FFLUID has been added for field 8 of PSOLID entry. Furthermore the user must take care to
define the normalized admittance coefficient in the MAT10 entry properly calculated at = 1.0 .
Benefits
The new capability introduced in MSC Nastran 2010 allows defining an automatic calculation of a
different value for the normalized admittance depending on the value of the excitation frequency.
The major benefit for the user is the possibility to describe in a very simple way the right absorbing
behaviors of the rigid porous material at the different excitation frequencies.
Note the user interface chosen to define the frequency dependency of the porous absorber allows:
• Maintaining the backward compatibility (Frequency independent porous absorbers can still be
modeled)
• Defining one set of fluid elements to have frequency dependent normalized admittance
coefficient and another set to be frequency independent
Theory
The porous absorber properties are described by complex parameters (density and bulk modulus). The
general implementation allows introducing complex material properties for elements in the fluid which
Main Index
CHAPTER 4 29
Dynamics (Noise and Vibration)
represent region where sound energy is absorbed. It implies that if the complex density and bulk modulus
are constant:
Mass density
2 2
r + i
= r + i i e = ------------------
-
r
Bulk Modulus B
2 2
Br + Bi
B = B r + iB i B e = -------------------
-
Br
Damping coefficient GE
GE = -----i
r
Bi Bi
= ----- = 2f -----
Br Br
INPUT
As already mentioned, the equivalent fluid analogy allows using the same entries used to describe a
standard fluid region. PSOLID and MAT10 entries are affected by this implementation.
PSOLID Entry
A new option for field 8 (FCTN) of the PSOLID entry has been introduced
1 2 3 4 5 6 7 8 9 10
PSOLID PID MID CORDM IN STRESS ISOP FCTN COROT
FAC
FCTN Fluid element flag. (Character: “FFLUID” indicates a fluid element with frequency
dependent rigid absorber properties, “PFLUID” indicates a fluid element, “SMECH”
indicates a structural element; Default = “SMECH.”)
Main Index
30 MSC Nastran 2010 Release Guide
Frequency Dependent Rigid Absorber Properties
All the elements which refer to a PSOLID entry where the option FFLUID has been selected will be
considered as rigid porous absorber with frequency dependent normalized admittance coefficient.
MAT10 Entry
No modification has been done in the format of this entry and no new options have been added. The only
remark that has to be done is relative to the meaning of field 7 in case of frequency dependent rigid porous
absorber.
1 2 3 4 5 6 7 8 9 10
MAT10 MID BULK RHO C GE ALPHA
In fact:
• If the MAT10 entry is referenced in a PSOLID entry where FFLUID option is selected, the value
in the 7th field (ALPHA) is considered as the normalized admittance coefficient calculated at
unit circular excitation frequency = 1.0 ;
• If the MAT10 entry is referenced in a PSOLID entry where PFLUID option is selected, the value
defined in field 7 (ALPHA) has no special meaning but it is only the normalized admittance
coefficient calculated at the most appropriate excitation frequency (defined in order to have good
results in the range of interest.
The use of a nonzero value in field 7 of the MAT10 entry causes the generation of a damping matrix,
because the normalized admittance coefficient is multiplied by the imaginary operator i. Consequently,
the use of modal methods on the fluid are not appropriate and frequency response analysis must be carried
out using the direct method, at least for the fluid.
OUTPUT
There is no additional output are generated for the elements used to describe the frequency dependent
rigid absorber region.
Test Cases
There are many test cases available in the TPL in subdirectory /tpl/fdr_absorb
Main Index
CHAPTER 4 31
Dynamics (Noise and Vibration)
Consider the following unbounded fluid (air) and porous absorber medium domains as in Figure 4-5. An
acoustic source is placed at the location indicated and the acoustic response (pressure) at the center of
the fluid is monitored.
Figure 4-5
The equations illustrated above have been used to calculate the equivalent properties to be used in the
MAT10 entries. Two different calculations have been executed to check the effect of the new frequency
dependent porous absorber properties implementation.
1. Frequency independent materials have been considered and frequency of 250 Hz was selected to
calculate the values of alpha for air and the porous absorber.
Air Material
Main Index
32 MSC Nastran 2010 Release Guide
Frequency Dependent Rigid Absorber Properties
Main Index
CHAPTER 4 33
Dynamics (Noise and Vibration)
The results using frequency dependent rigid absorber properties fit completely with those from Actran.
In fact the increasing differences obtained using the original implementation for porous material
properties departing from the reference excitation frequency (250 Hz in the example) disappear.
GUI Support
Currently neither Patran or SimXpert support the preprocessing definition of the FFLUID option in field
8 of the PSOLID entry.
The post-processing capability of Patran and SimXpert is not affected by this implementation.
Main Index
34 MSC Nastran 2010 Release Guide
Frequency Dependent Rigid Absorber Properties
Main Index
CHAPTER 4 35
Dynamics (Noise and Vibration)
Introduction
Monitor points is a generic name for four types of user requests. The MSC Nastran R1 Release Guide
provided the most comprehensive discussion of these inputs. Briefly,
1. MONPNT1 – The MONPNT1 provides integrated loads at a user defined point in a user defined
coordinate system.
2. MONPNT2 – The MONPNT2 provides element results (e.g., Stress, Strain, Force)
3. MONPNT3 – The MONPNT3 provides a summation of grid point forces at a user specified
integration points.
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.
Prior to MSC Nastran 2010, monitor points were only available in SOLs 101, 103, 144 and 146. Design
of Monitor Points, 57 discusses the MSC Nastran 2010 implementation in SOL 200. These sections
discusses their application in the linear dynamic response solution sequences; i.e., SOLs 108, 109, 111
and 112.
Benefits
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 for static or dynamic
aeroelasticity). This enables the batch calculation of VMT (shear, moment and torque) data for user
specified regions and locations.
MONPNT2 provides a way of pinpointing a particular response for output, as opposed to finding it in a
large OFP listing.
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.
Input
There is no change to the input required to define the monitor points, only the solution sequences which
are supported. The MSC Nastran Quick Reference Guide provides guidance on specifying the
MONPNT1, MONPNT2, MONPNT3 and MONDSP1 Bulk Data entries. The MONITOR Case Control
command must be used to obtain output results in the dynamic solution sequences. The command
provides options for frequency response results in terms of either the Real/Imag or MAG/Phase form.
Main Index
36 MSC Nastran 2010 Release Guide
Dynamics - Monitor Points in Dynamic Solution Sequences
Output
Test Cases
The following test cases are available in the TPL in directory /tpl/ue6_09a. There are four TPL files with
the name sXXXm13d and four with sXXXm2 where the XXX is one of 108,109,111 or 112. The m13d
files contain MONPT1, MONPNT3 and MONDSP1 entries while m2 files contain MONPNT2 entries.
A set of MONDSP1s are generated to define virtual point displacement results using an RBE3 derived
from the GRIDs defined on the SET1 lists referenced on the AECOMP entry:
MONDSP1 DISP2 THIS IS A DISPLACEMENT MONITOR POINT
123456 PLATE3 52 1. 2. 3.
AECOMP PLATE3 SET1 3 4
Main Index
CHAPTER 4 37
Dynamics (Noise and Vibration)
A set of MONPNT1s are generated to define integration load monitor points; the integration occurs over
the GRIDs associated with the SET1 entries defined on the AECOMP entry:
MONPNT1 MPT11 THIS IS THE FIRST MONPNT1
123456 PLATE1 52 1. 2. 3.0
AECOMP PLATE1 SET1 1 2
SET1 1 110000 110010 111010 111000
SET1 2 110505
Finally, a set of MONPNT3s are generated to sum Grid Point Forces defined on the GRIDSET and
ELEMSET.
MONPNT3 MPT31 THIS IS THE FIRST MONPT3
123456 5 6 1. 2. 3.
SET1 5 110901 119992 110903 110904 110905
SET1 6 1100081 9999980
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
(REAL/IMAGINARY)
FREQUENCY T1 T2 T3 R1 R2 R3
------------ ------------ ------------ ------------ ------------ ------------ ------------
1.000000E+02 9.331630E-06 7.714264E-06 1.142239E-06 3.345541E-07 -4.731310E-07 4.621815E-07
-5.560066E-08 -4.663981E-08 -6.488654E-09 -1.900483E-09 2.687689E-09 -3.033787E-09
2.000000E+02 9.721770E-06 8.044613E-06 1.186316E-06 3.474638E-07 -4.913880E-07 4.847471E-07
-1.203002E-07 -1.010250E-07 -1.398631E-08 -4.096495E-09 5.793319E-09 -6.610803E-09
3.000000E+02 1.044643E-05 8.658742E-06 1.267942E-06 3.713716E-07 -5.251988E-07 5.268791E-07
-2.072620E-07 -1.743763E-07 -2.394549E-08 -7.013472E-09 9.918547E-09 -1.152342E-08
4.000000E+02 1.165478E-05 9.684080E-06 1.403449E-06 4.110607E-07 -5.813276E-07 5.976722E-07
-3.416177E-07 -2.881529E-07 -3.912291E-08 -1.145883E-08 1.620524E-08 -1.929935E-08
Main Index
38 MSC Nastran 2010 Release Guide
Dynamics - Monitor Points in Dynamic Solution Sequences
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 (MONPNT1)
(REAL/IMAGINARY)
FREQUENCY RESULTANT
------------ ------------
1.000000E+02 -3.689061E-01
-3.930317E-05
2.000000E+02 -3.910366E-01
4.639984E-04
3.000000E+02 -4.319148E-01
2.253416E-03
4.000000E+02 -4.992898E-01
6.649540E-03
GUI Support
Patran
Patran supports Monitor Point creation via the Flight Loads application. To access Flight Loads, it needs
to be installed during the Patran installation and the current analysis type must be Aeroelasticity. The
figures in this section provide a general description of how to create the various Monitor Points described
in this chapter. After the Monitor Points are created, the user can export them to a bdf file for subsequent
inclusion in a non-aeroelasticity solution. Finally, the user will have to change the Analysis Type back to
Structures. Currently Patran does not support the post-processing of Monitor Point results.
Main Index
CHAPTER 4 39
Dynamics (Noise and Vibration)
Figure 4-7 Setting Analysis Type to Aeroelasticity for Monitor Point Access via Flight Loads
Figure 4-8 Flight Loads icon enables the flight loads menus
Main Index
40 MSC Nastran 2010 Release Guide
Dynamics - Monitor Points in Dynamic Solution Sequences
Main Index
CHAPTER 4 41
Dynamics (Noise and Vibration)
Main Index
42 MSC Nastran 2010 Release Guide
Dynamics - Monitor Points in Dynamic Solution Sequences
SimXpert
SimXpert does not currently support Monitor Point Creation.
Main Index
Chapter 5: Optimization MSC Nastran 2010 Release Guide
5 Optimization
Part Superelement Optimization Enhancements
Optimization - Invariant DRESP3 Gradients
Design of Monitor Points
Parallel Sensitivities
DTABLE Enhancement for Dynamic Analysis
Constants with DTABLE2
New Optimizer - IPOPT
Topology and Topometry Enhancements
Build External Servers Using the SCons Tool
Deactivation of Original Design Sensitivity (DSA)
Main Index
44 MSC Nastran 2010 Release Guide
Part Superelement Optimization Enhancements
Introduction
Part Superelements are a method for defining superelements by having a completely independent bulk
data for each Superelement. One advantage of Part Superelements is that bulk data for various
components or subassemblies can be easily assembled without the need to renumber GRIDs, properties,
etc. Another advantage is that parameters are independent for each superelement. The method for
defining Part Superelements in MSC Nastran is by the delimiter BEGIN SUPER=seid, where seid is the
user-defined Superelement Identification number. Note that the residual structure is defined in the main
Bulk Data Section (BEGIN BULK, or BEGIN SUPER=0). The residual structure is also designated as a
Part Superelement with seid=0. The residual structure includes the effects of all the upstream Part
Superelements and is used to calculate the solution vector. For more information on Superelements and
Part Superelements, refer to the MSC Nastran 2001 Superelement User’s Guide.
Part Superelement Optimization was introduced in MSC Nastran 2008 with the limitation that the design
variables, responses, and constraints for SOL 200 optimization were required to be defined in the main
Bulk Data Section. With the MSC Nastran 2010 release, Part Superelement Optimization extends the
design model in SOL 200 to allow design of upstream Part Superelements in addition to the residual
structure.
Benefits
Part Superelement technology is widely used in the Aerospace and Automotive industry to assemble bulk
data models from various sources. Some advantages of Part Superelement technology include automatic
connections based on geometry searches and the ability to have completely independent bulk data.
Extending the design model to Part Superelements will allow users great flexibility in assembling models
and performing design optimization using Part Superelement technology. Design variable, response, and
constraint definition for Part Superelement Optimization can include the residual structure and all Part
Superelement(s). Design variables can be linked across Part Superelements. In addition synthetic
responses can include responses from different Part Superelements are supported with new Bulk Data
entries, namely SEDLINK, SEDRSP2, and SEDRSP3.
Input
Each Partitioned Superelement may contain traditional Solution 200 bdf entries such as DESVAR,
DVPREL1, DRESP1, etc. The new bulk data entries are introduced to support cross boundary Part
Superelement design variable linking and synthetic responses. These new bulk data entries are for Part
Superelement only and must involve quantities from more than one Part Superelement. See additional
comments and remarks for Bulk Data entries SEDLINK, SEDRSP2, and SEDRSP3 (p. 3096) in the
MD/MSC Nastran Quick Reference Guide. These bulk data entries must be specified in the residual Bulk
Data Section.
Main Index
CHAPTER 5 45
Optimization
1 2 3 4 5 6 7 8 9 10
SEDLINK ID DSEID DDVID C0 CMULT ISEID1 IDV1 C1
ISEID2 IDV2 C2 ISEID3 IDV3 C3
ISEID4 IDV4 C4 -etc.-
1 2 3 4 5 6 7 8 9 10
SEDRSP2 ID LABEL EQID or REGION METHOD C1 C2 C3
FUNC
“DESVAR” DVSEID1 DVID1 DVSEID2 DVID2 DVSEID3 DVID3
1 2 3 4 5 6 7 8 9 10
SEDRSP3 ID LABEL GROUP TYPE REGION
“DESVAR” DVSEID1 DVID1 DVSEID2 DVID2 DVSEID3 DVID3
Main Index
46 MSC Nastran 2010 Release Guide
Part Superelement Optimization Enhancements
-etc.-
For user convenience, specifying PARAM,PSENPCH,YES will write the updated bulk data entries into
separate ‘.pch’ files for each Part Superelement, and each design cycle. Note that the number of design
cycles that are output is dependant on the value of PARAM,DESPCH. The advantage of specifying
PARAM,PSENPCH,YES is that each of the ‘.pch’ files with the updated design bulk data can be used to
replace the original model with an ‘INCLUDE’ entry after the appropriate ‘BEGIN SUPER=seid’. If
PARAM,SPENPCH,YES is not specified, the updated bulk data entries for all Part Superelements are
written to a single ‘.pch’ file which will require the user to manually extract each Part Superelement
model from the .pch file and place it in the appropriate ‘BEGIN SUPER=seid’ section of the Bulk Data
Section.
Output
For SOL 200 with design models in each Part Superelement, the .f06 output is similar to non Part
Superelement optimization jobs. There are some minor differences that are specific to Part
Superelements only.
Main Index
CHAPTER 5 47
Optimization
Comparison Between Input Property Values from Analysis and Design Models
This section of the .f06 will repeat for the design model of each Part Superelement. A sample for a Part
Superelement is shown as follows:
1 DOUBLE FLYSWATTER MODEL $ ANALYSIS USING PART SUPERELEMENTS JANUARY 13, 2009 MSC Nastran 1/12/09 PAGE 39
S.E. STATICS - MULTIPLE LOADS SUPERELEMENT 4
0
----- 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 4 T 5.000000E-02 5.000000E-02 5.000000E-03 1.000000E+20 NONE
1. THE DIFFERENCE FLAG IS USED TO CHARACTERIZE DIfFERENCES BETWEEN ANALYSIS AND DESIGN MODEL PROPERTIES:
IF THE FLAG IS NONE, THEN THERE IS NO SIGNIFICANT DIFFERENCE BETWEEN THE TWO VALUES.
IF THE FLAG IS WARNING, THEN THE USER IS ADVISED THAT DIFFERENCES EXIST AND THE DESIGN MODEL
IS BEING USED TO OVERRIDE THE ANALYSIS MODEL.
IF THE FLAG IS FATAL, THEN THE DIFFERENCES ARE GREATER THAN 1.00000E+35 AND THE RUN WILL BE TERMINATED.
2. THE SPAWNING FLAG (*) INDICATES THAT THE SPAWNED PROPERTY IS DERIVED EITHER FROM THE BEAM CROSS SECTION
LIBRARY OR FROM A PBEAM ENTRY. THE PROPERTY ID FOR THE SPAWNED PROPERTY IS IDENTICAL TO ITS PARENT.
Please note that the Part Superelement ID shows up in the title line of a page. In addition, residual Part
Superelement will get two versions of above output, first and last. If there are differences between design
and analysis model for residual Part Superelement, the differences will show up in the first version.
Main Index
48 MSC Nastran 2010 Release Guide
Part Superelement Optimization Enhancements
$ ******************************
$ * *
$ * PART SE 2 *
$ * *
$ ******************************
$
$ *************************************************************
$ * *
$ * CONTINUOUS DESIGN CYCLE NUMBER = 5 *
$ * *
$ *************************************************************
$
$ ******************************
$ * *
$ * PART SE 2 *
$ * *
$ ******************************
$
$ UPDATED DESIGN MODEL DATA ENTRIES
$
DESVAR * 102T2 1.00000001E-01 1.00000001E-01+D 1V
*D 1V 1.00000000E+01
$ ******************************
$ * *
$ * PART SE 2 *
$ * *
$ ******************************
$
$ UPDATED ANALYSIS MODEL DATA ENTRIES
$
PSHELL* 2 2 5.00000035E-03 2*
* 1.00000000E+00 2 8.33333313E-01 0.00000000E+00*
* 0 *
*
Main Index
CHAPTER 5 49
Optimization
6. Design Responses for Image Part Superelements (copies, mirrors, etc. via SEBULK Bulk Data
entry) are supported in the design model.
Test Cases
The following test cases are available in TPL library tpl\pse_200:
d200pse1, d200pse2, d200pse3, p200pse6, d200pse7, d200pse8, d200psea and d200pseb
Main Index
50 MSC Nastran 2010 Release Guide
Part Superelement Optimization Enhancements
The case control is similar to case control and design model definition is similar to non Part Superelement
optimization files. Note that the DESSUB in the case control points to the DCONSTR in each Part
Superelement.
BEGIN SUPER=1
$ design model for SE 1
DCONSTR 100 101 -7.00 7.00
DCONSTR 100 102 -7.00 7.00
DESVAR 101 T1 1.0 .1 10.0
DESVAR 1001 GE_1 1. 0.1 10.
DRESP1 101 S1G57Z DISP 3 57
DRESP1 102 S1G93Z DISP 3 93
DVMREL1 1001 MAT1 1 GE .005
++0000031001 .05
DVPREL1 1 PSHELL 1 T .005
++000001101 .05
$ each BEGIN SUPER has additions to the design model
Main Index
CHAPTER 5 51
Optimization
The output is similar to output from non Part Superelement Optimization runs, as an example, the Design
Variable History for d200pse1.dat is:
Main Index
52 MSC Nastran 2010 Release Guide
Part Superelement Optimization Enhancements
There is no direct Patran support for the SEDLINK, SEDRSP2, and SEDRSP3 entries, nor
PARAM,PSENPCH. These entries could be added via Direct Text Input, or the bdf can be modified
before job submission.
SimXpert does not currently support SOL 200 Design Optimization.
Post Processing
With PARAM,POST,-1 the objective, maximum constraint, and design variable history data will be
written to the OP2 and available for post-processing by Patran as normal.
SimXpert does not currently support Optimization.
Main Index
CHAPTER 5 53
Optimization
Introduction
One component of the design model in gradient based design optimization is the design response
definition. A design response can be used as an objective or a constraint can be placed on the response
to bound the optimization space. A simple example of an objective is to minimize the weight. Constraint
can be as simple as “von Mises stress must be less than 20,000 psi,” or as complex as a subroutine that
calculates multiple margins of safety based on stress, stability, empirical, and manufacturing
considerations. In MSC Nastran, there are three types of responses:
1. Direct responses are output quantities generated by a typical MSC Nastran analysis. Examples
are Weight, Frequency, Stress, Displacement, etc. Direct responses are specified for the design
model by specifying DRESP1Bulk Data entries.
2. Equation based responses can be defined by the user based on current design model values and
constants. The equation based responses can be quite extensive and allow the user great flexibility
in defining a synthesized response. The DRESP2 is used to define equation based results.
3. External responses are available by calling a user supplied subroutine. This type of response gives
the user ultimate flexibility by allowing the designer to write his own subroutines that can include
empirical based tables, conditional clauses, loops, etc. in defining the response. The DRESP3is
used to define the inputs and external response server used to calculate the responses.
Sensitivity analysis is performed to calculate the gradient of each response with respect to each design
variable. Additional information on design optimization in MSC Nastran can be found in the MD
Nastran Design Sensitivity and Optimization User’s Guide.
The MSC Nastran 2008 release enhanced DRESP3 by returning multiple responses, providing for
analytic gradients, and using a more efficient algorithm when there are many more DRESP1’s in the
DRESP3 than there are design variables. The MSC Nastran 2010 release has added a feature that allows
the user to specify that gradients of the DRESP3 with respect to the design are to be considered invariant
during the approximate optimization task.
Benefits
In the approximate optimization task, DRESP3 gradients have been calculated using central differencing
techniques. For a DRESP3 with 100 arguments, this entails 200 calls to the server for a single gradient
calculation. This can be a performance burden if the server call is non-trivial. For this reason, it was
decided to implement invariant gradient approach which assumes the gradient is not a strong function of
the individual arguments. The approximate optimizer does not have to make any calls to the server.
Input
The format of the DRESP3 Bulk Data entry is unchanged. The user is required to modify the R3SGRT
server subroutine that supplies MSC Nastran with the information on the number of responses and the
Main Index
54 MSC Nastran 2010 Release Guide
Optimization - Invariant DRESP3 Gradients
type of gradient evaluation desired. Prior to MSC Nastran 2008, the only gradient option that was
supported was finite difference so there was no need for the user to specify the method to be used. MSC
Nastran 2008 provided two options for the gradient type and this was specified in the R3SGRT subroutine
by specifying a GRDTYP for each response. With MSC Nastran 2010, the number of options is four:
• GRDTYP = 1 specifies that analytic gradients will be provided by the user and they will be
computed explicitly during the approximate optimization task
• GRDTYP = 2 specifies that analytic gradients will be provided by the user and they will be
considered invariant during the optimization task.
• GRDTYP = 3 specifies that finite difference techniques will be required to compute gradient
information and they will be computed explicitly during the approximate optimization task.
• GRDTYP = 4 specifies that finite difference techniques will be required to compute gradient
information and they will be considered invariant during the approximate optimization task.
The user provided R3SVALD subroutine that evaluates the DRESP3 response does not need to be
modified as a result of this enhancement.
Output
There is no change to the existing output formats.
Examples
There are two tests cases in the TPL subdirectory /tpl/edresp3_08 that demonstrate the invariant dresp3
capability:
dresp3fi.dat – This file calculates all the gradients using finite difference methods and considers the
gradients to be invariant during the approximate optimization task (i.e., GRDTYP = 4).
dresp3fo.dat – This file calculates all the gradients using all four methods. The R3SGRT subroutine in
this case has the following specification:
ERROR = 0
nresp = 1
DO 100 ITYPE = 1, NTYPES
IF (TYPNAM .EQ. R3TYPE(1)) THEN
grdtyp(1) = 3
go to 200
else IF (TYPNAM .EQ. R3TYPE(2)) THEN
grdtyp(1) = 1
go to 200
else IF (TYPNAM .EQ. R3TYPE(3)) THEN
Main Index
CHAPTER 5 55
Optimization
grdtyp(1) = 2
go to 200
else IF (TYPNAM .EQ. R3TYPE(4)) THEN
grdtyp(1) = 3
go to 200
else IF (TYPNAM .EQ. R3TYPE(5)) THEN
grdtyp(1) = 4
go to 200
else
ERROR = BADTYP
END IF
100 CONTINUE
It is seen that the user is able to specify the gradient type as a function of the response name.
Other Guidelines
In R3SGRT, GRDTYP needs to be defined for all NRESP responses and the values must be either 1, 2,
3 or 4. It is an error if any other value is used.
MSC currently does not have test cases that allow an evaluation of the relative performance of the
various gradient options. However, one can make the following recommendations:
1. If the DRESP3 evaluations are cheap and simple, GRDTYP = 1 (analytic, variant) is
recommended.
2. If the DRESP3 evaluations are simple, but expensive, GRPTYP = 2 (analytic, invariant) is
recommended. It would seem that this option would be rarely needed.
3. If the DRESP3 evaluations are not simple, but still cheap, GRDTYP = 3 (finite difference,
variant) is recommended.
4. If the DRESP3 evaluation are complex and expensive, GRDTYP = 4 (finite difference, invariant)
is recommended.
Main Index
56 MSC Nastran 2010 Release Guide
Optimization - Invariant DRESP3 Gradients
The invariant gradients will not provide as accurate a calculation as the variable ones so it becomes a
trade-off between the time spent performing the optimization and possible more design iterations to reach
the final design. It is expected that this new capability will be used sparingly, but will provide a dramatic
improvement in CPU time in special circumstances.
The current limitation that all GRDTYP’s for a particular TYPE be the same is retained for this project.
The GRDTYP’s do not need to all be the same for all the DRESP3’s in an input file. That is, one can
specify analytic variant gradients (GRDTYP = 1) for one TYPE and finite difference, invariant gradients
(GRDTYP = 4) for another type.
Additional Information
Building and Using DR3SERV (p. 253) in the MD Nastran 2010 Installation and Operations Guide has
information on installing and running the DR3SERV, the server associated with the DRESP3.
Post Processing
There are no additional post-processing requirements associated for Invariant DRESP3 Gradients.
Main Index
CHAPTER 5 57
Optimization
Introduction
Monitor points is a generic name for four types of output requests. The MSC Nastran R1 Release Guide
provided the most comprehensive discussion of these inputs. Briefly,
1. MONPNT1– The MONPNT1 provides integrated loads at a user defined point in a user defined
coordinate system.
2. MONPNT2– The MONPNT2 provides element results (e.g., Stress, Strain, Force)
3. MONPNT3– The MONPNT3 provides a summation of grid point forces at a user specified monito
points.
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.
With the release of MSC Nastran 2010, each of the MONPNT1, MONPNT3 and MONDSP1 quantities
can now be specified as design response quantities on the DRESP1entry. The MONPNT2 capability for
element results effectively duplicates existing DRESP1 response quantities, so MONPNT2 is not
supported.
Benefits
The user of this capability is likely to be an investigator who wants to control a load path in an aeroelastic
analysis. This is a sophisticated application that is related to aeroelastic tailoring, implying that it will be
done in conjunction with composites. It’s likely that our users will find other applications that are
currently undefined.
Input
The existing DRESP1 entry now has 5 additional options. The following is extracted from the
description of the entry DRESP1 (p. 1644) in the MD/MSC Nastran Quick Reference Guide:
Main Index
58 MSC Nastran 2010 Release Guide
Design of Monitor Points
36. For monitor point responses (RTYPE = STMONP1, STMOND1, MONPNT3 AEMONP1 or
AEMOND1) the ATTA field specifies the components to be extracted. These can be any subset
of the integers 1 through 6 that appear on the monitor quantity with the NAME provided in the
PTYPE field. All of these responses can be invoked in a static aeroelastic (ANALYSIS=SAERO)
subcase. STMONP1, STMOND1 and MONPNT3 can be invoked from a static
(ANALYSIS=STAT) subcase. The responses are not available in a dynamic response or normal
modes subcase. The response types have the following meaning:
a. STMONP1 – A structural MONPNT1
b. STMOND1 – A structural MONDSP1
c. MONPNT3 – A MONPNT3
d. AEMONP1 – An aerodynamic MONPNT1
e. AEMOND1 – An aerodynamic MONDSP1
For all but the STMONP1, the response is the elastic monitor point value. For the STMONP1, it is the
elastic “minus” inertial “plus” elastic applied load value.
Output
The various response outputs have been modified to clearly identify Monitor Points.
Main Index
CHAPTER 5 59
Optimization
---------------------------------------------------------------------------------------------------------
INTERNAL EXTERNAL INTERNAL
INTERNAL DCONSTR RESPONSE DRESPx RESPONSE L/U REGION SUBCASE
ID ID ID ID TYPE FLAG ID ID VALUE
---------------------------------------------------------------------------------------------------------
1 100 10 3456 STMOND1 UPPER 0 10 2.3412E-01
2 100 11 4567 MONPNT3 LOWER 0 10 -2.7536E-01
3 100 8 5678 GPFORCE LOWER 5678 10 -2.7536E-01
4 100 8 5678 GPFORCE UPPER 5678 10 2.6273E-01**
5 100 9 5679 GPFORCE LOWER 5679 10 5.7648E-02
6 100 9 5679 GPFORCE UPPER 5679 10 -6.6978E-02
7 100 1 6543 EQUA UPPER 6543 10 6.6703E-02
----------------------------------------------------------------------
| R E S P O N S E S IN D E S I G N M O D E L |
----------------------------------------------------------------------
------------------------------------------------------------------------------------------------------------
INTERNAL DRESP1 RESPONSE NAME COMPONENT LOWER UPPER
ID ID LABEL NO. BOUND VALUE BOUND
------------------------------------------------------------------------------------------------------------
10 3456 STIP SWTIP 3 N/A 3.0853E+00 2.5000E+00
11 4567 SMP3 SPOINT 3 1.0000E+00 1.2754E+00 N/A
****************************************************************************
* *
* D E S I G N S E N S I T I V I T Y M A T R I X O U T P U T *
* *
* *
* R E S P O N S E S E N S I T I V I T Y C O E F F I C I E N T S *
* *
****************************************************************************
----------------------------------------------------------------------------------------------------------------
DRESP1 ID= 3456 RESPONSE TYPE= STMOND1 NAME = SWTIP COMP NO= 3 SEID= 0
SUBCASE RESP VALUE DESIGN VARIABLE COEFFICIENT DESIGN VARIABLE COEFFICIENT
----------------------------------------------------------------------------------------------------------------
10 3.0853E+00 1 INBD -8.0550E-01 2 SNDD -6.8049E-01
----------------------------------------------------------------------------------------------------------------
DRESP1 ID= 4567 RESPONSE TYPE= MONPNT3 NAME = SPOINT COMP NO= 3 SEID= 0
SUBCASE RESP VALUE DESIGN VARIABLE COEFFICIENT DESIGN VARIABLE COEFFICIENT
----------------------------------------------------------------------------------------------------------------
10 1.2754E+00 1 INBD 3.6495E+00 2 SNDD -3.9502E+00
Main Index
60 MSC Nastran 2010 Release Guide
Design of Monitor Points
Test Cases
Three test cases are provided in the tpl subdirectory /tpl/ue_mdr4 that demonstrate this new capability:
The subcase invokes constraints on each type of monitor responses with constraints contrived to force
their retention. This test case is used to test the quality of the sensitivities. A part of the bulk data file
which contains the monitor points, the design response and their constraints is shown here:
Main Index
CHAPTER 5 61
Optimization
Main Index
62 MSC Nastran 2010 Release Guide
Design of Monitor Points
Reference Documents
The MSC Nastran Quick Reference Guide provides a description of the input required for these new
responses while the Design Sensitivity and Optimization User’s Guide is a good resource for learning
about design optimization in MSC Nastran.
Main Index
CHAPTER 5 63
Optimization
Main Index
64 MSC Nastran 2010 Release Guide
Parallel Sensitivities
Parallel Sensitivities
Introduction
Design sensitivity and optimization in MSC Nastran requires sensitivity calculation of the design
responses w.r.t. each design variable. Design sensitivity calculations can be a very costly portion of a
SOL 200 run for models with large numbers of design variables and large numbers of design responses.
The Design Sensitivity and Optimization User’s Guide provides great detail about design sensitivity
calculations in MSC Nastran.
In MSC Nastran 2010, design sensitivity calculations have been enhanced to be performed in a
distributed parallel (dmp) environment in SOL 200 of MSC Nastran. The parallel implementation divides
the sensitivity task across a number of processors so that each processes a subset of the total number of
design variables. Following the sensitivity analysis and before optimization, the separate sensitivity data
are appended into a global sensitivity set.
Benefits
Parallel Sensitivity Analysis is aimed at users who have design optimization tasks that spend significant
time in the sensitivity calculation phase. This typically occurs for models with large dof, or there are
many (perhaps thousands) of design variables and the adjoint method of sensitivity analysis is either
unavailable or still time consuming.
Inputs
1. Specify the DOMAINSOLVERExecutive Control statement with the new DSA keyword. For
example:
DOMAINSOLVER DSA
Other DOMAINSOLVER options like ACMS, FREQ, and MODES may also be specified or
modified along with DSA. For example,
DOMAINSOLVER DSA ACMS
Note: DOMAINSOLVER options MODES and FREQ are defaults on with dmp keyword on the
Nastran submittal command, but the DSA option must be explicitly specified.
2. Specify the dmp=n keyword on the Nastran submittal command; where n is the number of
available processors.
Outputs
There are no new outputs. It should be noted that with dmp=n, by default, only the master processor’s
output (f04 and f06) is saved. “slaveout=yes” may be specified on the Nastran submittal command to
request the slaves’ output.
Main Index
CHAPTER 5 65
Optimization
Test Cases
TPL problem /ugdesopt/dsoug7.dat involves a frequency response sizing optimization problem. As an
example, the Executive Control Section is modified as follows:
domainsolver acms dsa
SOL 200
cend
and the job is submitted with:
nastran dsoug7 dmp=2
The job converges after five design cycles and compares exactly with the serial results demonstrating
that the parallel sensitivity calculations provide the same answers.
Testing on larger models has demonstrated that the implementation of parallel sensitivity scales well for
statics. Similar performance is expected for other analysis disciplines and on all platforms that support
dmp.
Figure 5-3 Example problem dspdsa1 run with MEM=2Gb on IBM Power5
Main Index
66 MSC Nastran 2010 Release Guide
Parallel Sensitivities
Post Processing
There are no additional post-processing requirements associated for the parallel sensitivity enhancement.
Main Index
CHAPTER 5 67
Optimization
Introduction
As discussed in Optimization - Invariant DRESP3 Gradients, 53, one component of the design model in
gradient based design optimization is the design response definition. The advanced response definitions
are available via the equation based response DRESP2, or the external program response DRESP3. In
addition to using design variables and direct responses, the user may want to define constants to use in
the advanced response equations. These constants can be defined with a DTABLEentry for subsequent
use by the DRESP2 or DRESP3. Additional information on design optimization in MSC Nastran can be
found in the MD Nastran Design Sensitivity and Optimization User’s Guide.
The DTABLE enhancement for MSC Nastran 2010 allows the DTABLE entry to reference a TABLEDi
entry. In MSC Nastran 2010, when the DTABLE encounters an Integer input for VALUi, it will use the
Real values found on TABLEDi. When the corresponding LABLi is used in a synthesized response
DRESP2, the data defined on the TABLEDi entries will be used.
Benefits
The DTABLE enhancement benefits dynamic optimization problems that use the MATCH function by
greatly simplifying the input. The integer input for DTABLE in MSC Nastran 2010 reduces the input to
1 TABLEDi, 1 DRESP1 with ATTB field left blank and a DRESP2 with a single LABLi under DTABLE
and a single NRid under DRESP1.
Prior to this enhancement, the user would need to define
1. DTABLE with LABLi for each forcing frequency
2. DRESP1 for each forcing frequency
3. A DRESP2 with MATCH function with DTABLE calls out each LABLi and DRESP1 ID
involved
For a frequency response SOL 200 job with, say, 50 forcing frequencies, one will need DATBLE with
50 (LABLi,VALUi) pairs, 50 DRESP1 each with a single frequency specified and a DRESP2 which has
50 LABLi under DTABLE flag and 50 NRid under DRESP1 flag. The old-style vs. new-style simplified
input will be demonstrated in the sample section.
Input
The DTABLEBulk Data entry now accepts integer input for a VALUi. The integer value invokes a
TABLEDi which carries (freq,value) or (time,value) pairs for a number of frequencies or times,
respectively. The TABLEDi will be interpolated for frequency or time values that are not explicitly
defined in the table.
Main Index
68 MSC Nastran 2010 Release Guide
DTABLE Enhancement for Dynamic Analysis
1 2 3 4 5 6 7 8 9 10
DTABLE LABL1 VALU1 LABL2 VALU2 LABL3 VALU3 LABL4 VALU4
LABL5 VALU5 LABL6 VALU6 LABL7 VALU7 LABL8 VALU8
-etc.-
Output
No new output.
Test Cases
There are two tests cases in the TPL subdirectory /tpl/dtabl200 that demonstrate the DTABLE
enhancement
Main Index
CHAPTER 5 69
Optimization
$
dresp1,130,f130,frvelo,,,1,30.,701001
dresp1,131,f131,frvelo,,,1,31.,701001
dresp1,132,f132,frvelo,,,1,32.,701001
.
. (55 DRESP1 removed)
.
dresp1,188,f188,frvelo,,,1,88.,701001
dresp1,189,f189,frvelo,,,1,89.,701001
dresp1,190,f190,frvelo,,,1,90.,701001
$
dresp2,330,f330,MATCH
+,dtable,c30,c31,c32,c33,c34,c35,c36,
+, ,c37,c38,c39,c40,c41,c42,c43,
+, ,c44,c45,c46,c47,c48,c49,c50,
+, ,c51,c52,c53,c54,c55,c56,c57,
+, ,c58,c59,c60,c61,c62,c63,c64,
+, ,c65,c66,c67,c68,c69,c70,c71,
+, ,c72,c73,c74,c75,c76,c77,c78,
+, ,c79,c80,c81,c82,c83,c84,c85,
+, ,c86,c87,c88,c89,c90
+,dresp1,130,131,132,133,134,135,136,
+, ,137,138,139,140,141,142,143,
+, ,144,145,146,147,148,149,150,
+, ,151,152,153,154,155,156,157,
+, ,158,159,160,161,162,163,164,
+, ,165,166,167,168,169,170,171,
+, ,172,173,174,175,176,177,178,
+, ,179,180,181,182,183,184,185,
+, ,186,187,188,189,190
With the DTABLE enhancement, the input for MSC Nastran 2010 is shown as follows
Listing 5-12 MSC Nastran 2010 DTABLE enhanced input for MATCH function
tabled1 530
20. 1.e+10 2000. 1.e+10 endt
DTABLE const 1.e+10 const2 530
$
dresp1,130,f130,frvelo,,,1, ,701001
$
dresp2,330,f330,MATCH
+,dtable,const2
+,dresp1,130
Note that this example happens to have a constant matching function. Usually, the matching function in
dynamic analysis is not constant and TABLED1 entry may have many more physical lines to define the
response curve.
Post Processing
There are no additional post-processing requirements associated with the DTABLE Enhancement.
Main Index
70 MSC Nastran 2010 Release Guide
Constants with DTABLE2
Introduction
As discussed in Optimization - Invariant DRESP3 Gradients, 53, one component of the design model in
gradient based design optimization is the design response definition. The advanced response definitions
are available via the equation based response DRESP2, or the external program response DRESP3. In
addition to using design variables and direct responses, the user may want to define constants to use in
the advanced response equations. These constants can be defined with a DTABLE entry for subsequent
use by the DRESP2 or DRESP3. Additional information on design optimization in MSC Nastran can be
found in the MD Nastran Design Sensitivity and Optimization User’s Guide.
Historically, the DTABLE entry was used to associate a real constant to a label for subsequent use in
design property relations (DVCREL2, DVMREL2, DVPREL2) or advanced design responses (DRESP2,
DRESP3). The DTABLE has a simple input that is a paired label / constant (LABLi/VALUi).
The DTABLE2 Bulk Data entry extends this capability to “lookup” constant values defined on property,
connectivity, and material entries.
Benefits
DTABLE2 provides a direct access to fields with real value on property, connection and material entries.
This allows the user to change the input file properties without having to redefine all of the values
associated to the properties that are defined on a DTABLE entry. The LABLi on DTABLE2 entries can
be used interchangeably with LABLi on DTABLE for level 2 property relations: DVCREL2, DVMREL2,
and DVPREL2as well as advanced responses: DRESP2and DRESP3.
Input
The new Bulk Data entry for DTABLE2 is:
Format:
1 2 3 4 5 6 7 8 9 10
DTABLE2 LABL1 PNAME1 PID1 FNAME1 LABL2 PNAME2 PID2 FNAME2
LABL3 PNAME3 PID3 FNAME3
Example:
DTABLE2 PTHK10 PSHELL 10 T MAT1E MAT1 38 E
CBARX1 CBAR 3888 X1
Main Index
CHAPTER 5 71
Optimization
Field Contents
LABLi Label for the constant. (Character)
PNAMEi Property, material or connection bulk data entry name. (Character)
PIDi ID of PNAMEi entry. (Integer > 0)
FNAMEi Field name of PNAMEi. (Character)
Output
No new output for DTABLE2.
Test Cases
TPL Problem d200tb2b.dat
TPL problem tpl/dtabl200/d200tb2b.dat is modified to use DTABLE2 for the DRESP2 reference. The
label DVP11 is associated to PBAR with ID 11, “A” for area. The PNAME “A” is taken directly from
the Bulk Data entry PBAR:
1 2 3 4 5 6 7 8 9 10
PBAR PID MID A I1 I2 J NSM
C1 C2 D1 D2 E1 E2 F1 F2
K1 K2 I12
Field Contents
PID Property identification number. (Integer > 0)
MID Material identification number. (Integer > 0)
A Area of bar cross section. (Real; Default = 0.0)
Main Index
72 MSC Nastran 2010 Release Guide
Constants with DTABLE2
Field Contents
I1, I2, I12 Area moments of inertia. (Real; I1 > 0.0, I2 > 0.0, I1*I2 > I12 2 ; Default = 0.0)
J Torsional constant. (Real; Default = 1--- I 1 + I 2 for SOL 600 and 0.0 for all other
2
solution sequences)
NSM Nonstructural mass per unit length. (Real)
Ci, Di, Ei, Fi Stress recovery coefficients. (Real; Default = 0.0)
K1, K2 Area factor for shear.(Real or blank)
Main Index
CHAPTER 5 73
Optimization
dvcrel1 10 11
dvmrel1 13
dvprel2 3
dvcrel2 12
dvmrel2 14
dresp2 999
Post Processing
There are no additional post-processing requirements associated with DTABLE2.
Main Index
74 MSC Nastran 2010 Release Guide
New Optimizer - IPOPT
Introduction
MSC Software conducts surveys of optimizer technologies from industry and academia. This has lead to
the integration of optimizer IPOPT. IPOPT implements an interior point line search filter method that
aims to find a local optimal solution for large scale nonlinear optimization. It was originally developed
by Carnegie Mellon University in 2002 and now is supported by IBM.
Interior point method as one of barrier methods was first proposed in the sixties. Barriers methods are
used to transform a “difficult” constrained problem into a sequence of “easy” unconstrained problems.
MSCADS SUMT method is one of this classical barrier method and BIGDOT is also based on this
approach. Barrier methods were popular during the sixties. However, this classical barrier method has its
shortcomings, practitioners of nonlinear programming lost interest and switched to newly emerging,
apparently more efficient MMFD and SQP-like methods (MSCADS and DOT) in the mid-seventies and
eighties.
In the mid-eighties, a modern interior-point revolution started with the well-known Karmarkar linear
programming algorithm which can be interpreted as a barrier method. Since then, interior point
algorithms have emerged as one of most important and useful algorithms for mathematical programming.
In particular, these interior point methods provide an attractive alternative to active constraint set
methods in handling problems with large numbers of design variables and inequality constraints.
IPOPT is a software package for large scale nonlinear optimization. This code has been shown to be
capable of handling tens of thousands of design variables. It can be used to solve SOL 200 sizing, shape,
topology, topometry, and topography problems. Currently, SOL 200 has two license options, Design
Optimization and Topology Optimization (IPOPT requires the Topology Optimization license feature).
In MSC Nastran 2010, IPOPT has been made the default optimizer for topology, topometry, and
topography design optimization problems. This is done because testing indicates that IPOPT provides a
more robust solution than the MSCAD SUMT method. The choice of optimizers can be made with the
OPTCOD feature on the DOPTPRMBulk Data entry, or with MSC Nastran System Cell OPTCOD (413)).
See also notes in the .Licensing, 77.
Benefits
In theory, the interior point method is a very robust algorithm that provides an alternative to SOL 200
existing optimizers, in particular, MSCADS SUMT method. The IPOPT optimizer not only enables
performing practical topology, topometry, and topography optimization tasks but can also be used to
perform standard shape and sizing optimization for design tasks.
Theory
In this section, a very brief discussion about the interior point method implemented in IPOPT is
presented. More detail can be read on paper “On the implementation of a primal-dual interior point filter
Main Index
CHAPTER 5 75
Optimization
line search algorithm for large-scale nonlinear programming”, Mathematical Programming, 106(1):25–
57, 2006 by A. Wachter and L. T. Biegler.
To simplify the description of the interior point method, we consider a problem with equality constraints
as
minimize fx
subject to Cj X = 0 j = 1 2 m (5-1)
Xi 0 i = 1 2 n
where X L and X U are the lower and upper bounds on the design variables X . n is the number of design
variables, and m is the number of equality constraints. The objective function f X and the inequality
constraints C j X are assumed to be twice continuously differentiable. Inequality constraints can be
transformed to equality constraints by introducing slack variables.
In general, gradient-based optimization algorithms have a common strategy as below:
A general optimization algorithm loop
• Start k = 0 , X = X 0
• Evaluate f X and C j X
Two critical parts of the optimization task consists of determining a search direction and finding a best
one-dimensional search step. The determining a search direction is the most time consuming part and
one of major difference between the interior method and SOL 200 other optimization methods.
Main Index
76 MSC Nastran 2010 Release Guide
New Optimizer - IPOPT
As a barrier method, the interior point algorithm computes (approximates) solutions for a sequence of
barrier problems
n
i
minimize:
x = f x – ln x
i =1
(5-2)
for a decreasing sequence of barrier parameters µ converging to zero. Equivalently, this can be
interpreted as applying a homotopy method to the primal-dual equations,
f x + c x – z = 0
cx = 0 (5-3)
XZe – e = 0
with the homotopy parameter which is driven to zero. Here, R m and zR n correspond to the
Lagrangian multipliers for the equality constraints and the bound constraints, respectively. Note, that
Eq. (5-3) for = 0 together with “x; z 0 are the Karush-Kuhn-Tucker (KKT) conditions for the
original problem Eq. (5-2). Those are the first order optimality conditions for Eq. (5-1) if constraint
qualifications are satisfied Eq. (5-3).
In order to solve the barrier problem Eq. (5-2) for a given fixed value j of the barrier parameter, a
damped Newton's method is applied to the primal-dual Eq. (5-3). Here, a search direction is obtained
from solving a symmetric linear system
Wk + k + w I Ak x x k + A k k
dk
= j (5-4)
T
Ak –c I dk c xk
where Jacobian A k = c x k and W k denotes the Hessian 2xx L x k k z k of the Lagrangian function
T
L x z = f x + c x – z
The overall efficiency of the interior point method is dependent on solving a n + m n + m sparse
linear system Eq. (5-4).
Main Index
CHAPTER 5 77
Optimization
Input
There are two ways to select the optimizer IPOPT code. One way is by modifying the Nastran system
cell OPTCOD (413))as shown in Table 5-1.
The second way is by a parameter OPTCOD on a DOPTPRM Bulk Data entry that has options shown in
Table 5-2.
.Licensing
MSC provides two optimization license options:
1. Optimization (license file FEATURE line MD_Optimization)
2. Topology Optimization (license file FEATURE line MD_Topology_Optimization).
The default behavior is as follows:
• If both MD_Optimization and MD_Topology_Optimization licenses are found:
The default behavior is that the optimizer and METHOD will be automatically selected for a
better performance based on number of design variables, number of constraints, number of
active/violated constraints and computer memory.
Main Index
78 MSC Nastran 2010 Release Guide
New Optimizer - IPOPT
Output
If default OPTCOD and/or METHOD is used, the program prints injobname.f06 what optimizer and
method is used. For example,
***SYSTEM INFORMATIN MESSAGE 6649 (ADS9D)
MSCADS METHOD = 1 (MMFD) HAS BEEN SELECTED FOR DESIGN CYCLE= 1.
Examples
There are several example files in the TPL that can be used to demonstrate the new IPOPT performance.
Main Index
CHAPTER 5 79
Optimization
This composite structure is modeled with 62 CQUAD4 elements, 55 CSHEAR elements, 39 CROD
elements, and 39 CONM2 elements. Two static load cases are imposed along with an eigenvalue load
case. The objective was to minimization. There are 153 sizing design variables and 414 stress and failure
index constraint and a lower and upper bounds on the first fundamental frequency. To use IPOPT, a
parameter OPTCOD=IPOPT is added on Bulk Data entry DOPTPRM such as
Table 5-3 shows the IPOPT results for this example and all results are comparable.
Main Index
80 MSC Nastran 2010 Release Guide
New Optimizer - IPOPT
.
Figure 5-5 TPL file /topography/ip3dbeam.dat Beam Finite Element Model
The input data for this example related to topology optimization model is given in Listing 5-5. A Bulk
Data entry TOPVAR =1 is used to define a topological design region. Type one design responses
DRESP1 = 2 and 10 identify compliance and fractional mass respectively. OPTCOD=IPOPT on the Bulk
Data entry DOPTPRM selects the new optimizer IPOPT for solving this optimization problem.
SMETHOD= ELEMENT is used to select CASI iterative solver that can provide a major speedup in the
solution of large static analyses for solid element models.
Main Index
CHAPTER 5 81
Optimization
SUBCASE 1
$ SUBCASE NAME : RUN1_LOAD_CASE
SUBTITLE=RUN1_LOAD_CASE
SPC = 2
LOAD = 3
BEGIN BULK
DCONSTR 1 2 .2
DOPTPRM, OPTCOD, IPOPT
TOPVAR 1 PSOLID PSOLID .2 1
DRESP1 2 FRM FRMASS
DRESP1 10 COMP COMP
Figure 5-6 shows the topology optimized result that is smoothed and smoothed by using Patran. This
optimal design is very clear without any checkerboard effect.
Main Index
82 MSC Nastran 2010 Release Guide
Topology and Topometry Enhancements
Introduction
Topometry optimization is a special form of sizing optimization most commonly used for shell elements
whereby each shell element in a property region is allowed to change thickness independently of its
neighboring element. This provides the user an insight to the optimum material distribution to achieve
the objective while satisfying constraints. Additional element types commonly supported by topometry
optimization are non-volume elements such as CWELD, CBUSH, and CFAST.
Topology optimization adjusts each elements’ “effectivity” by adjusting the modulus of Elasticity and
density to determine a optimum material distribution. Topology optimization can be applied to solid,
shell, and beam elements.
The two methods are describe in further detail in the MD Nastran Design Sensitivity and Optimization
User’s Guide.
MSC Nastran 2010 contains a few enhancements for SOL 200 topometry and topology optimization
capabilities. The enhancements include
1. density constraint method for topology minimum member size control
2. composite (PCOMP) topometry optimization
3. discrete topometry optimization.
4. enhanced TOPVAR entry and casting constraints
Benefits
Topology Optimization Density Constraint Method
A density constraint method is implemented for topology minimum member size control. This approach
is more efficient than the filtering method for topology problems with a very fine mesh and a relatively
large predefined minimum member size.
Main Index
CHAPTER 5 83
Optimization
1 2 3 4 5 6 7 8 9 10
TOMVAR ID TYPE PID PNAME/ XINIT XLB XUB DELXV
FID
“DLINK” TID C0 C1
“DDVAL” DSVID
Field Contents
TYPE Property entry type. Used with PID to identify the elements to be designed.
(Character: “PBAR”, “PSHELL”, “PSOLID”, and “PCOMP”, etc.)
“DDVAL” Indicates that this line defines discrete TOMVAR variables
DSVID DDVAL entry identifier (Integer > 0)
“DLINK” Indicates that this line relates a ply thickness to another ply thickness
TID TOMVAR entry identifier (Integer > 0).
C0 Constant term (Real; Default = 0.0)
C1 Coefficient term (Real; no Default)
Main Index
84 MSC Nastran 2010 Release Guide
Topology and Topometry Enhancements
Format:
1 2 3 4 5 6 7 8 9 10
TOPVAR ID LABEL PTYPE XINIT XLB DELXV POWER PID
“SYM” CID MSi MSi MSi CS NCS
“CAST” CID DDi DIE ALIGN
“EXT” CID EDi ALIGN
“TDMIN” TV
Field Contents
XINIT Initial value. (Blank or Real, XLB < XINIT < 1.0 Default=blank). Typically,
XINIT is defined to match the mass constraint on DRESP1=FRMASS, so the
initial design does not have violated constraints. In this case, the default is set
to the constraint value. If the mass (DRESP1=FRMASS or WEIGHT) is the
objective, the default is 0.9. The default of XINIT is 0.6 for the other cases.
ALIGN Indicates whether the designed property finite element mesh is precisely
aligned with the draw direction or extrusion direction. (Character: “YES” or
“NO” or Blank; Default = blank = “NO”)
Output
The only change in output for these features is for the Composite Topometry optimization. In this case,
a element result file jobname.plyxxx (where xxx is a PCOMP ply identifier) contains the optimal design
values for each composite ply. The element result file can be imported into Patran or third party post-
processor to display composite topometry optimization results.
Main Index
CHAPTER 5 85
Optimization
Examples
TPL Problem /topography/tomex5.dat
TPL problem /topography/tomex5.dat is a 2D Composite Plate example intended to demonstrate a ply-
by-ply thickness optimization using the TOMVAR entry. This composite plate has 640 CQUAD4
element as shown in Figure 5-7. The ply layup is symmetric: 0°, 90°, 45°, -45°,-45°,45°,90°,0°. The
objective is to minimize structural compliance and lower/upper bounds are applied on each ply thickness.
since the composite is modeled with the “SYM” option, there are 4 independent design variables. The
problem is treated as a planar problem an dofs 3456 are permanently constrained on a GRDSET entry.
The input data for this example pertinent to the composite lay up and topometry optimization model is
given in Listing 5-16. The TOMVAR Bulk Data entries 1-4 define the ply-by-ply thickness optimization.
It is noticed that all four ply thickness per element are independent variables. Thus, there are 640x4
independent design variables.
Main Index
86 MSC Nastran 2010 Release Guide
Topology and Topometry Enhancements
ANALYSIS = STATICS
$ DIRECT TEXT INPUT FOR GLOBAL CASE CONTROL DATA
SUBCASE 1
$ SUBCASE NAME : RUN1_LOAD_CASE
SUBTITLE=RUN1_LOAD_CASE
SPC = 2
LOAD = 3
BEGIN BULK
PCOMP 1 -.0105 0.0 0.65E6 TSAI SYM
70 1.000 0.0 YES 70 1.000 90. YES
70 1.000 45. YES 70 1.000 -45. YES
DOPTPRM, OPTCOD, IPOPT
DRESP1 10 COMP COMP
$...DESIGN TOPOMETRY DESIGN DEFINITION
TOMVAR, 1 , PCOMP, 1, T1 , .5, 1.25-3, 1.0
TOMVAR, 2 , PCOMP, 1, T2 , .5, 1.25-3, 1.0
TOMVAR, 3 , PCOMP, 1, T3 , .5, 1.25-3, 1.0
TOMVAR, 4 , PCOMP, 1, T4 , .5, 1.25-3, 1.0
In addition to the standard .f04, .f06 and .pch output files, the final ply thickness distributions are
contained in files tomex5.ply0001, tomex5.ply0002, tomex5.ply0003, tomex5.ply0004. To post process
these in Patran, they must be read from the tools menu, and then the results can be displayed using
standard Patran fringe plots.
Main Index
CHAPTER 5 87
Optimization
Figure 5-9 through Figure 5-12 show the optimized ply thickness distribution for all elements.
Main Index
88 MSC Nastran 2010 Release Guide
Topology and Topometry Enhancements
The DLINK feature can be used to relate one ply thickness to another ply thickness in order to support
composite element-by-element thickness optimization. The input data for this example is given in
Listing 5-17. The DLINK line is used to explicitly link the thickness of plies 2, 3, and 4 to ply 1. Thus,
each composite element has only one independent design variables.
Main Index
CHAPTER 5 89
Optimization
Figure 5-13 shows the optimized element-by-element thickness distribution. Note that only 1 ply output
file is generated: tomex6.ply0001.
Main Index
90 MSC Nastran 2010 Release Guide
Topology and Topometry Enhancements
Post Processing
Patran supports post processing of PCOMP Topometry enhancements as described previously in Output,
84.
Main Index
CHAPTER 5 91
Optimization
Introduction
MSC Nastran provides the external server capability (beam library, DRESP3 and Spline servers) to allow
the client to create their custom applications without modifying the Nastran program. Prior to MSC
Nastran 20101, the binary server executables are built using make utilities. Starting this release, they will
be built using the SCons tool.
Overview
SCons is a Software Construction tool. Its major benefits are given below. It is expected that SCons tool
provide same or better experience to build an external server.
1. Automatically to resolve source code dependencies;
2. Fairly easy to build binary programs on various platforms with different operating systems. It is
particular true for building external server programs on Windows;
3. Easy to develop applications that use combined Python scripts and other source codes written in
C or Fortran because SCons configuration files are written in Python scripts;
4. Easy to extend the server template codes by simply adding your source codes to the target
directory without the need to modify SConscript.
Although DRESP3 server is used to describe the procedures to build an external server, they can be
applied directly to beam library and spline servers.
Main Index
92 MSC Nastran 2010 Release Guide
Build External Servers Using the SCons Tool
The SCons tool requires a subdirectory be created for each server program. For example, directory
dr3serv is created for server dr3serv that contains a SConscript file and Fortran files r3sgrt, r3svald,
r3svals. It is convenient to use the program name as the directory name but is not required.
Main Index
CHAPTER 5 93
Optimization
that is architecture dependent. For example, arch=LX8664 indicates Linux 64 bit machine or
arch=WIN8664 a Window 64 bit machine.
If you do not have the write privilege to the install_dir, you have two options:
1. Define APPS_LOCAL and SCA_OBJECT construction variables to redirect the output to
another writable location. To learn more about the SCons build environment, please consult
Subsection of 'Build External Servers using SCons tools' Under the External Response Section in
the DS&O's User Guide.
2. Copy the entire dr3 directory to another location that you have the write access to. This option is
particularly useful when you want to create your server program in a new subdirectory.
Main Index
94 MSC Nastran 2010 Release Guide
Deactivation of Original Design Sensitivity (DSA)
Main Index
Chapter 6: Aeroelasticity MSC Nastran 2010 Release Guide
6 Aeroelasticity
Input of Pressures on an Aerodynamic Mesh
Aeroelasticity - Output of Trimmed Loads
CSV Output of Trim Results
SUBCOM/SUBSEQ with Static Aeroelasticity
Upper Hessenberg Complex Eigenanalysis No Longer Supported for
Flutter Analysis
Main Index
96 MSC Nastran 2010 Release Guide
Aeroelasticity
Introduction
In MSC Nastran 2010 the user can apply pressures at aerodynamic grid (AEGRID) points. Previously,
this was not possible.
Benefits
It is now possible to input pressures that come from an external source, such as CFD analyses or wind
tunnel tests, onto an aerodynamic mesh and Nastran will transform these pressures to forces that can be
included in a static aeroelastic analysis.
Feature Description
A new Nastran module has been provided that combines information input on the AEPRESS/DMIJ
entries with geometry provided on AEGRID/AEQUAD4/AETRIA3 entries and coordinate systems data
to produce forces at the aerodynamic mesh points. Spline input can then be used to transfer these forces
to structural grid points so that they can be included in a standard SOL 144 static aeroelastic analysis. No
new input commands or entries are required to invoke this capability.
Main Index
CHAPTER 6 97
Aeroelasticity
6. It is not possible to combine aerodynamic mesh input with Doublet Lattice like aerodynamics in
a single run. However, it is possible to have separate meshes using the “RIGID/Flexible Mesh”
concepts introduced in MSC Nastran 2005 R3. This entails making an initial run with only the
rigid aerodynamic mesh and then, in a subsequent run, attaching the database from this run and
using the AERCONFIG case control command to identify the rigid mesh results in a static
aeroelastic analysis that would obtain its flexible increments from a doublet lattice based analysis.
7. Currently, this technology is only available in static aeroelasticity (SOL 144 or the
ANALYSIS=SAERO option in SOL 200). Support for SOL 146 (dynamic response) is not
provided at this time.
Test Cases
The following test cases are available on the TPL in subdirectory /tpl/aero_asm: cyl144b.dat
where is the rotation speed in radians/sec. r is the radius of the cylinder and V is the freestream
velocity. The pressure acts radially while Nastran requires input in rectangular coordinates at the grid
points. With a coordinate system that has positive x in the direction of the flow and the z axis normal to
the flow, the radial pressure at each point has components in the x and z directions. For irrotational flow,
the net force in the streamwise direction is zero so that it is only necessary to input the z component of
the pressure. Note that 3D effects of the flow are neglected so there is no spanwise component.
Main Index
98 MSC Nastran 2010 Release Guide
Aeroelasticity
Figure 6-1 The Aerodynamic and Structural Model for the Flow Around a Spinning
Cylinder.
A section of the pressure input is given shown in Figure 6-2. The AEPRESS entry identifies a UXVEC
entry that indicates the state of the pressure input. In this case, the state includes the intercept and a CIRC
value of 0.1, where CIRC is the r V parameter. The AEPRESS data at the UXVEC condition is input
as a vector using the DMIJ format that lists the grid and component for each real number that provides
the pressure at the mesh point. Since the three dimensional aspects of the flow are ignored in this analysis,
the same pressure distribution in input at the 5 spanwise cuts.
Main Index
CHAPTER 6 99
Aeroelasticity
Figure 6-2 A Portion of the Input Bulk Data that Provides Pressure Data on the
Aerodynamic Mesh
Figure 6-3 provides an additional snippet with splining and boundary condition information. The
SPLINE7 is a 6 DOF spline that uses a finite beam technique to connect all the aerodynamic mesh points
to the structural grids that are defined along the axis of the tube. The GRDSET entry constrains the
motion in the 1256 directions at all the structural grid points while the SPC condition invokes symmetry
about the x-axis and the SUPORT entry allows the tube to move in the 3 direction.
$ $
$ * 6DOF FINITE BEAM SPLINE * $
$ $
$ EID CAERO BOX1 BOX2 SETG DZ
aelist 101 1 thru 16 101 thru 116 401
201 thru 216 301 thru 316 402 403
404 thru 416
set1 101 1001 thru 1011
SPLINE7 100 1 101 101 1.0
both
spc 1 1006 4
suport 1006 3
grdset 1256
Figure 6-3 Spline and Boundary Condition Input for the Spinning Cylinder
The goal of the analysis is to determine the rate of rotation necessary to create a lift force that is equal to
the weight (URDD3 = 1.0) of the aluminum tube when immersed in an airstream moving at M = .45
(Velocity = 6031.8 inches/sec) at sea level. The .f06 file indicates that the value of the CIRC parameter
at “trim” is 1.214E-3. The rotational rate is then 1.214E-3 6031.8 2 = 1.16 cycles/second.
References
1. Kuethe, A.M and Schetzer, J.D., Foundations of Aerodynamics, John Wiley & Sons, New York,
Second Edition, 1959.
Main Index
100 MSC Nastran 2010 Release Guide
Aeroelasticity
GUI Support
Patran Flight Loads -
SimXpert does not currently support aeroelastic analysis.
Main Index
CHAPTER 6 101
Aeroelasticity
Introduction
MSC Nastran now supports the creation of bulk data force/moment entries for trim loads.
Benefits
A primary reason for performing a static aeroelastic analysis is to determine the aeroelastic loads acting
on the free-flying vehicle. With this new capability it is now possible to output the loads from the trim
solution in the familiar FORCE/MOMENT Bulk Data entry format so that these loads could be passed
to the group performing detailed stress analysis. In another application, these loads could be viewed in a
graphical fashion using, for example, MD Patran.
Input
The TRIMF Case Control command is used to invoke this new capability. The user can provide an
ASSIGN statement to direct the results to a special purpose file, or they will go to the .pch file by default.
The TRIMF command is quite flexible in that it can output load components or total loads. It is also
possible to limit the output to a set of user defined grid points.
TRIMF Format:
Example:
TRIMF(LOADSET=10001,LARGE)=ALL
TRIMF(UNIT=59,INERTIA,NOSUM)=1
Describer Meaning
UNIT Fortran unit to which data are written. (Optional; Default = 7) (punch file).
LOADSET Load set id for output bulk data entries. If the TRIMF specification results in
multiple load sets, then the defined ID will be used for the first and each subsequent
load set has an ID incremented by 1. (Optional; Default = 1)
LARGE Write the output data in large field format (16 characters per field). The default is 8
characters per field.
INERTIA Write out inertial loads as a separate load set. By default, the separate load set will
not be written.
Main Index
102 MSC Nastran 2010 Release Guide
Aeroelasticity
Describer Meaning
APPLIED Write out applied loads as a separate load set. By default, the separate load set will
not be written.
AIR Write out aerodynamic loads as a separate load set. By default, the separate load set
will not be written.
NOSUM By default, the sum of the inertial, applied, and aerodynamic loads will be written
as a separate load set. This option suppresses the writing of that set of loads.
RIGID Write out rigid instances of the selected loads (Inertial, Applied, Air and/or Sum) as
separate load sets. By default, the separate load set will not be written.
NOELASTIC By default, the sum of the rigid and elastic increment loads will be written as a
separate load set. This option suppresses the writing of that set of loads.
QNORM Normalize the load by the dynamic pressure used in the trim analysis. By default,
the loads are not normalized.
ALL Loads for all points will be output
n Set identification of a previously appearing SET command. Only loads on points
with identification numbers that appear on this SET command will be output
(Integer > 0)
Remark:
1. By default, the loads are written to the punch file (Fortran unit 7). If the user specifies an alternate
Fortran unit number on the TRIMF entry, by default the loads will be written to a file name that
is machine specific (i.e. ‘fort.53’ on many UNIX platforms). The user may connect the Fortran
unit to a user-defined file name by using an ASSIGN entry in the FMS Section of the input file.
For example:
ASSIGN USERFILE='load13.inc',STATUS=UNKNOWN,FORMATTED,UNIT=53
2. Up to eight loads sets are available: Rigid Inertial, Rigid Applied, Rigid Air, Rigid Sum and four
more with the sum of the rigid and elastic increment.
3. Care must be taken if LOADSET is specified in a run with multiple subcases. There are no checks
that the load set IDs which are generated by one subcase are not also used for another subcase.
For example, consider the following Case Control commands:
SUBCASE 1
TRIM = 1
TRIMF(RIGID) = ALL $
SUBCASE 2
TRIM = 2
TRIMF(LOADSET=2) = ALL
Subcase 1 will generate two load sets with set IDs 1 and 2. Subcase 2 will also output a load set
ID 2.
4. The LOADSET option should not be specified in a TRIMF entry that is located above the subcase
level. For example, consider the following:
Main Index
CHAPTER 6 103
Aeroelasticity
TRIMF(LOADSET=101) = ALL
SUBCASE 1
TRIM = 1
SUBCASE 2
TRIM = 2
Here, both subcases will output trim loads with load set ID = 101.
Output
The output of TRIMF are FORCE and MOMENT bulk data entries. The output is to either the punch file
or user defined file. See test case below for sample output.
Test Cases
The following test cases are available in the TPL in directory /tpl/ue6_09a: trimf.dat
TPL file trimf.dat is a variation of the ha144e.dat test file documented in the MSC Nastran Aeroelastic
User’s Guide. The variation is to add the following trimf commands in two of the five subcases:
assign userfile='abrupt.inc', status=unknown,formatted,unit=53
...
...
SUBCASE 1
TRIM = 1 $ HIGH SPEED LEVEL FLIGHT
SUBCASE 2
TRIM = 2 $ HIGH SPEED ROLLING PULLOUT
SUBCASE 3
trimf(unit=53,loadset=1,rigid)=all
TRIM = 3 $ HIGH SPEED PULLOUT WITH ABRUPT ROLL
SUBCASE 4
trimf(loadset=10,inertia,air,rigid) = 100
TRIM = 4 $ HIGH SPEED SNAP-ROLL ENTRY
SUBCASE 5
TRIM = 5 $ HIGH SPEED CLIMBING TURN
The test case in contrived to test a number of the features of the new capability. For example, the assign
statement is used to capture the output from the third subcase while the data from the fourth subcase goes
to the .pch file. It is seen that the output only goes to a set of grids in the fourth subcase. This feature
could be used, for example, if only the loads on the wing are of interest.
Main Index
104 MSC Nastran 2010 Release Guide
Aeroelasticity
Main Index
CHAPTER 6 105
Aeroelasticity
$...............................................................................
$
$ TRIM CASE: 4
$ RIGID AERODYNAMIC LOADS
$
FORCE 12 100 0 1.0 0.0 416.853-16643.4
FORCE 12 111 0 1.0 0.0 0.0 9339.64
FORCE 12 112 0 1.0 0.0 0.0 -16832.9
FORCE 12 121 0 1.0 0.0 0.0 18282.9
FORCE 12 122 0 1.0 0.0 0.0 -4692.2
$...............................................................................
$
$ TRIM CASE: 4
$ ELASTIC AERODYNAMIC LOADS
$
FORCE 13 100 0 1.0 0.0 166.317-15698.5
FORCE 13 111 0 1.0 0.0 0.0 24597.3
FORCE 13 112 0 1.0 0.0 0.0 -19263.1
FORCE 13 121 0 1.0 0.0 0.0 33389.
FORCE 13 122 0 1.0 0.0 0.0 -5317.57
$...............................................................................
$
$ TRIM CASE: 4
$ RIGID (AERODYNAMIC + APPLIED - INERTIAL) LOADS
$
FORCE 14 100 0 1.0 -1.65-12-32730.5-16664.5
FORCE 14 111 0 1.0 1584.39-4922.53 9041.61
FORCE 14 112 0 1.0 1056.26-4337.95-15877.9
FORCE 14 121 0 1.0 4753.18-3093.03 19127.7
FORCE 14 122 0 1.0 3168.79-3118.28-2975.3
$...............................................................................
$
$ TRIM CASE: 4
$ ELASTIC (AERODYNAMIC + APPLIED - INERTIAL) LOADS
$
FORCE 15 100 0 1.0 -1.65-12-32781.3-15653.6
FORCE 15 111 0 1.0 1584.39-4922.53 24228.1
FORCE 15 112 0 1.0 1056.26-4337.95-17402.1
FORCE 15 121 0 1.0 4753.18-3093.03 34050.1
FORCE 15 122 0 1.0 3168.79-3118.28-3485.
GUI Support
Patran currently does not support the TRIMF case control
SimXpert does not have an aeroelastic workspace.
Main Index
106 MSC Nastran 2010 Release Guide
Aeroelasticity
Introduction
MSC Nastran 2010 contains a new feature that allows the user to create a summary of the trim results in
a CSV (Comma Separated Values) file suitable for viewing and manipulating in a spreadsheet
application.
Benefits
The CSV file provides a convenient summary of the trim results that would otherwise have to be gleaned
from disparate parts of the .f06 file. This is particularly valuable when hundreds of subcases are being
analyzed in a single run.
Input
The CSV feature in activated by PARAM LDSUM (Ch. 5) in the MD/MSC Nastran Quick Reference
Guide. The unit the CSV file is written to is specified by PARAM XYUNIT. An assign statement such as:
assign userfile='aecsv1.csv' status=unknown form=formatted unit=52
defines the file where the results are stored. The unit 52 corresponds to PARAM XYUNIT 52.
PARAM LDSUM
Default = 0
Dictates what information is to be stored on a CSV (comma separated values) file in a SOL 144 (static
aeroelasticity) task. The unit the CSV file is stored to is specified by param XYUNIT. LDSUM has the
following options:
• = 0 (Default) – Do not create a CSV file for static aeroelasticity
• =1 Create a CSV file that contains for each static aeroelastic subcase:
a. Subcase ID
b. Mach number
c. Dynamic Pressure
d. Trim Values
e. Mass and CG information (mass, xcg,ycg,zcg, IXX,IYY,IZZ,IXY,IXZ and IYZ)
• =2 Same as 1 plus net structural monitor point (MONPNT1, MONDPS1, MONPNT2,
MONPNT3) results
• = 3 Same as 2 plus the output of RIGID AIR, ELASTIC RESTRAINED, and INERTIAL,
RIGID APPLIED and ELASTIC APPLIED components for the structural MONPNT1 results
Main Index
CHAPTER 6 107
Aeroelasticity
Output
The output is a csv file as shown in the test case below.
Test Cases
The following test cases are available in the TPL in directory /tpl/ue_csv09: aecsv1.dat, aecsv4.dat
Main Index
108 MSC Nastran 2010 Release Guide
Aeroelasticity
BEGIN BULK
PARAMAESMETHRITZ
GUI Support
Patran currently does not support PARAM,LDSUM
SimXpert does not have an aeroelastic workspace.
Main Index
CHAPTER 6 109
Aeroelasticity
Introduction
The SUBCOM/SUBSEQ commands that were previously limited to statics problems have been
extended to static aeroelasticity problems (both in SOL 144 and in SOL 200 with ANALYSIS=SAERO).
Benefits
The motivation for this task is to allow a scaling of the results (displacements and element responses)
from a static aeroelastic trim analysis as a postprocessing operation. This is particularly of benefit in an
optimization task where one desires to explore applying different limit factors to the results in a design
task.
User Inputs
The existing SUBCOM/SUBSEQ case control commands have been activated for a static aeroelastic
analysis. Typically, a single SUBSEQ coefficient is used to scale the results of the previous subcase,
although multiple coefficients are supported. In a SOL 200 job, the SUBCOM subcase needs to be
accompanied by an ANALYSIS=SAERO command to designate that this subcase is to be grouped with
the static aeroelastic subcases.
Outputs
Data recovery occurs for the SUBCOM subcases in the same way as any other subcase. The SUBCOM
ID appears on the right hand side of the page to indicate that the results are associated with the SUBCOM
Example
A variation of the familiar HA144A test case for the forward swept wing is used to demonstrate the new
SUBCOM capability in a SOL 144 test case. The test case is available in the TPL in directory
/tpl/ue_csv09: subcoma.dat. The case control is shown below and it is seen that there is a SUBCOM 4
that requests output that is 50% greater than that of subcase 3.
TITLE = EXAMPLE HA144A: 30 DEG FWD SWEPT WING WITH CANARD HA14 HA144A
SUBTI = SYMMETRIC FLIGHT CONDITIONS, DOUBLET-LATTICE AERO
LABEL = HALF-SPAN MODEL, STATIC SYMMETRIC LOADING
Main Index
110 MSC Nastran 2010 Release Guide
Aeroelasticity
ECHO = BOTH
SPC = 1 $ SYMMETRIC CONSTRAINTS
DISP = ALL $ PRINT ALL DISPLACEMENTS
STRESS = ALL $ PRINT ALL STRESSES
FORCE = ALL $ PRINT ALL FORCES
AEROF = ALL $ PRINT ALL AERODYNAMIC FORCES
APRES = ALL $ PRINT ALL AERODYNAMIC PRESSURES
SUBCASE 1
TRIM = 1 $ 1 G LEVEL FLIGHT (LOW SPEED)
SUBCASE 2
TRIM = 2 $ 1 G LEVEL FLIGHT (HIGH SUBSONIC SPEED)
SUBCASE 3
TRIM = 3 $ 1 G LEVEL FLIGHT (LOW SUPERSONIC SPEED)
subcom 4
subseq(1.5)
BEGIN BULK
A snippet of the output from this job is shown below. It is seen that the displacements of SUBCOM 4
are 50% greater than those of SUBCASE 3.
1 EXAMPLE HA144A: 30 DEG FWD SWEPT WING WITH CANARD HA14 HA144A OCTOBER 21, 2009 MSC Nastran 10/20/09 PAGE 62
SYMMETRIC FLIGHT CONDITIONS, DOUBLET-LATTICE AERO
0 HALF-SPAN MODEL, STATIC SYMMETRIC LOADING SUBCASE 3
D I S P L A C E M E N T V E C T O R
D I S P L A C E M E N T V E C T O R
Main Index
CHAPTER 6 111
Aeroelasticity
Main Index
112 MSC Nastran 2010 Release Guide
Aeroelasticity
Main Index
Chapter 7: Elements
MSC Nastran Release Guide
7 Elements
Enhancements to Connector Elements
Offsets for Beams and Shells
Main Index
114 MSC Nastran 2010 Release Guide
Enhancements to Connector Elements
Introduction
A finite element modeler has many ways of modeling structural connections and fasteners. Spot welds,
seam welds, bolts, screws, and so on can be represented, depending on the modeling goals, either with
flexible springs or bars (CBUSH, CBAR), rigid elements (RBAR, RBE2, RBE3), or multipoint
constraints (MPC). Though generally, these elements are sometimes difficult to use; singularities may be
introduced particularly in the out-of-plane rotational direction for shells, rigid body invariance may not
be assured, and data preparation and input can be a formidable task in real-world applications. Increasing
mesh refinement can also introduce further stiffness errors; point-to-point connections in which effective
cross-sectional areas are larger than 20% of the characteristic element lengths can often lead to significant
underestimation of connector stiffness.
Connector elements are a special class of elements that were introduced to MSC Nastran in V2001. The
first implementation was for elements that represent spot welds. These elements are convenient to define
by the user because all that is necessary to define the elements a geometric location in space. Subsequent
versions of MSC Nastran have provided many enhancements and now include elements that can model
bolts and seam welds.
In MSC Nastran 2010, there have been further enhancements to the existing elements to allow data
recovery in dynamic solution sequences, calculate displacements and stresses for seam weld elements
and support user defined coordinate systems for spot weld elements the way that user defined coordinate
systems are used for bolt elements.
Benefits
The following features are included in MSC Nastran 2010.
1. Support auxiliary displacement output for frequency response and transient analysis for CWELD,
CFAST and CSEAM elements.
2. Generate eight auxiliary grids internally and compute their associated displacements for CSEAM
elements.
3. Provide stress and strain output for CSEAM elements.
4. Support user defined element coordinate system for CWELD elements.
Theory
Mathematical Model to Construct the CSEAM Auxiliary Points
The four auxiliary vertex points of the cross section at start point GS are constructed by the following
s s
equations (see Figure 7-1), where t 1 and t 2 are tangent vectors of the element coordinate system at start
Main Index
CHAPTER 7 115
Elements
s
point GS, W is the width of the seam, and T is the thickness of the seam. For a continuous seam, t 1 and
s
t 2 vectors are adjusted to a common face for the two consecutive seam elements. Therefore, the four
auxiliary grids at the start point S of the ith seam should be coincident with the four auxiliary grids at the
end point E of the (i-1)th seam, if both elements have same width and thickness.
W s T s
x S A1 = x s – ----- t 1 – --- t 2
2 2
W s T s
x S A2 = x s – ----- t 1 – --- t 2
2 2
W s T s
x S B1 = x s – ----- t 1 – --- t 2
2 2
W s T s
x S B2 = x s – ----- t 1 – --- t 2
2 2
s
t2
GSB1 GSB2
T/2
GS s
T/2 t1
GSA1 GSA2
W/2 W/2
Figure 7-1 Seam Weld Cross Section at Start Point S
The four auxiliary vertex points of the cross section at end point GE are calculated in the same way as
that for the start point GS. These eight auxiliary points form an auxiliary HEXA element with the
following vertex points.
1 2 3 4 5 6 7 8
GSA1 GSA2 GSB2 GSB1 GEA1 GEA2 GEB2 GEB1
Main Index
116 MSC Nastran 2010 Release Guide
Enhancements to Connector Elements
Input
The only new input is related to the element coordinate system on the CWELD entry. The relevant
changes are shown in the following CWELD entry (other items that did not change are not shown).
The other enhancements are to extend the solution sequences and provide additional output for the
CSEAM.
Main Index
CHAPTER 7 117
Elements
Defines a weld or fastener connecting two surface patches or points. Large displacement and large
rotational effects are supported when using SOL 600 and MSC Nastran SOL 400 only.
Format:
1 2 3 4 5 6 7 8 9 10
CWELD EWID PWID GS “PARTPAT” GA GB MCID
PIDA PIDB
XS YS ZS
Example:
Format ELPAT:
Example:
CWELD 103 5 403 ELPAT
309 511
Format ELEMID:
CWELD EWID PWID GS “ELEMID” GA GB MCID
SHIDA SHIDB
Example:
CWELD 103 5 403 ELEMID
309 511
Format GRIDID:
CWELD EWID PWID GS “GRIDID” GA GB SPTYP MCID
Main Index
118 MSC Nastran 2010 Release Guide
Enhancements to Connector Elements
Example:
CWELD 7 29 233 GRIDID QT
15 28 31 35 46 51 55 60
3 5 8
Format ALIGN:
CWELD EWID PWID “ALIGN” GA GB MCID
Example:
CWELD 7 29 ALIGN 103 259
Remarks:
15. MCID = -1 or blank (Default), then the coordinate system is as defined in Remark 12.
If MCID > 0, then a “beam” like coordinate system is defined. The x ele m axis direction of the
connector defined as
xB – xA
1 = ---------------------
xB – xA
Output
The results of CWELD and CFAST elements are stored in standard beam and standard bush formats
respectively; while the results of CSEAM elements are displayed in hexa format with the eight auxiliary
grids as vertex points. For frequency response, the output data may be in rectangular or polar format. The
examples below will give a description of the output.
Test Cases
The following test cases are available in the TPL in directory /tpl/rg4_conn: r4_conn_exa.dat,
r4_conn_exb.dat
Main Index
CHAPTER 7 119
Elements
SOL 108
END
DISPL= ALL
FORCE=1
STRESS=1
SUBCASE 1
SUBTITLE= shear the weld
dload=1
method= 400
freq=11
BEGIN BULK
$ Spot weld
cweld, 30, 30, 300, elpat, , , , 755, +CW1
+CW1, 11, 10
pweld, 30, 10, 0.1
$
cord2r, 755, , 0., 0., 0., 0., 0., -1.,
, 0., 1., 0.
Main Index
120 MSC Nastran 2010 Release Guide
Enhancements to Connector Elements
The displacement, element force and stress results are shown as follows.
0 SUBCASE 1
FREQUENCY = 1.000000E+01
C O M P L E X D I S P L A C E M E N T V E C T O R
(REAL/IMAGINARY)
0 SUBCASE 1
Main Index
CHAPTER 7 121
Elements
0 SUBCASE 1
FREQUENCY = 1.000000E+01
C O M P L E X F O R C E S I N W E L D E L E M E N T S ( C W E L D P )
(REAL/IMAGINARY)
0 SUBCASE 1
FREQUENCY = 1.000000E+01
C O M P L E X S T R E S S E S I N W E L D E L E M E N T S ( C W E L D P )
(REAL/IMAGINARY)
ELEMENT AXIAL MAX STRESS MIN STRESS MAX STRESS MIN STRESS MAXIMUM BEARING
ID STRESS END-A END-A END-B END-B SHEAR STRESS STRESS
30 1.147757E+00 1.278480E+03 -1.276184E+03 6.728133E+01 -6.498582E+01 1.297688E+02 3.134292E+01
-1.376786E-01 1.531557E+02 -1.534311E+02 7.810646E+00 -8.086003E+00 1.557555E+01 3.761164E+00
...
swldprm prtsw 1
$
cseam100011000se0elem113214
1000110002
cseam100021000se010elem330440
1000310004
cseam100031000se1010elem5030060400
1000510006
Main Index
122 MSC Nastran 2010 Release Guide
Enhancements to Connector Elements
cseam100041000sl1030pshell70200
1000710008
cseam100051000sl1030 pshell70200
1000910010
$
$23456
pseam 1000 200.2
$
D I S P L A C E M E N T V E C T O R
S T R E S S E S I N S E A M E L E M E N T S ( C S E A M )
0 CORNER ------CENTER AND CORNER POINT STRESSES--------- DIR. COSINES MEAN
ELEMENT-ID GRID-ID NORMAL SHEAR PRINCIPAL -A- -B- -C- PRESSURE VON MISES
0 10001 0GRID CS 8 GP
0 CENTER X 7.490945E+02 XY 3.996807E-02 A 7.490945E+02 LX 1.00 0.0 0.0 -2.497961E+02 7.489476E+02
Y 2.938447E-01 YZ -7.958079E-13 B 1.469501E-01 LY 0.00 0.0 0.0
Z 0.0 ZX 9.094947E-12 C 1.469501E-01 LZ 0.00 0.0 0.0
0 101000001 X 1.635867E+03 XY 7.365383E-02 A 1.635867E+03 LX 1.00 0.00 0.00 -6.910887E+02 1.425098E+03
Y 1.320214E+02 YZ -2.318950E-02 B 1.320214E+02 LY 0.00 1.00 0.00
Z 3.053776E+02 ZX -3.091930E-04 C 3.053776E+02 LZ 0.00 0.00-1.00
0 101000002 X 1.635903E+03 XY 7.365383E-02 A 1.635903E+03 LX 1.00 0.00 0.00 -6.911407E+02 1.425078E+03
Y 1.320599E+02 YZ 2.318950E-02 B 1.320599E+02 LY 0.00 1.00 0.00
Z 3.054590E+02 ZX -3.091930E-04 C 3.054590E+02 LZ 0.00 0.00-1.00
0 101000003 X -1.369259E+02 XY 6.282309E-03 A -1.311691E+02 LX 0.00 0.00-1.00 1.911511E+02 1.713834E+02
Y -1.311691E+02 YZ 2.318950E-02 B -3.053584E+02 LY 1.00 0.00 0.00
Z -3.053584E+02 ZX -3.091930E-04 C -1.369259E+02 LZ 0.00 1.00 0.00
0 101000004 X -1.370004E+02 XY 6.282309E-03 A -1.312972E+02 LX 0.00 0.00-1.00 1.912586E+02 1.714006E+02
Y -1.312972E+02 YZ -2.318950E-02 B -3.054782E+02 LY 1.00 0.00 0.00
Z -3.054782E+02 ZX -3.091930E-04 C -1.370004E+02 LZ 0.00 1.00 0.00
0 101000005 X 1.636985E+03 XY 7.365383E-02 A 1.636985E+03 LX 1.00 0.00 0.00 -6.919526E+02 1.425502E+03
Y 1.326195E+02 YZ -2.318950E-02 B 1.326195E+02 LY 0.00 1.00 0.00
Z 3.062530E+02 ZX 3.091930E-04 C 3.062530E+02 LZ 0.00 0.00-1.00
0 101000006 X 1.636935E+03 XY 7.365383E-02 A 1.636935E+03 LX 1.00 0.00 0.00 -6.918799E+02 1.425529E+03
Y 1.325717E+02 YZ 2.318950E-02 B 1.325717E+02 LY 0.00 1.00 0.00
Z 3.061331E+02 ZX 3.091930E-04 C 3.061331E+02 LZ 0.00 0.00-1.00
0 101000007 X -1.395096E+02 XY 6.282309E-03 A -1.322068E+02 LX 0.00 0.00-1.00 1.926500E+02 1.704930E+02
Y -1.322068E+02 YZ 2.318950E-02 B -3.062338E+02 LY 1.00 0.00 0.00
Z -3.062338E+02 ZX 3.091930E-04 C -1.395096E+02 LZ 0.00 1.00 0.00
0 101000008 X -1.394977E+02 XY 6.282309E-03 A -1.322486E+02 LX 0.00 0.00-1.00 1.926329E+02 1.703949E+02
Y -1.322487E+02 YZ -2.318950E-02 B -3.061523E+02 LY 1.00 0.00 0.00
Z -3.061523E+02 ZX 3.091930E-04 C -1.394977E+02 LZ 0.00 1.00 0.00
Main Index
CHAPTER 7 123
Elements
Introduction
The original design of the BAR, BEAM and shells included an offset feature. This feature allows you to
specify a BAR/BEAM axis of shear centers offset from connected grid points; and, a shell element
reference plane offset from the connected grids for triangular and quadrilateral shell elements.
The axis of the elastic BAR/BEAM was assumed to extend from the two endpoints offset from the
connected grid points; and, the reference surface of the shell element connected points offset from the
connected grids. The elastic stiffness was then calculated in the offset element coordinate system and
transformed to the connected grid points using the rigid body transformation equations.
Prior to the offset project in MSC Nastran 2010, element offsets had the following limitations:
• The differential stiffness is not supported. Therefore, they are not applicable in solution
sequence where differential stiffness is required, such as linear buckling analysis (SOL 105).
• The effect of offsets is not included the mass matrix, thus in dynamic analysis, the mass matrix
is only an approximation for offsets.
Main Index
124 MSC Nastran 2010 Release Guide
Offsets for Beams and Shells
• The effect of offset is not included in computation of thermal loads, pressure loads, or gravity
loads.
• For curved shell problems, the offset is defined in the z direction of the element and not the shell
normal direction, this results in gaps between elements when offset geometry is applied.
• The transformation is linear; therefore, it cannot be used nonlinear analysis.
This enhancement extends the use the offsets to nonlinear solutions, linear differential stiffness, load and
mass generation and maintenance of geometric continuity for adjacent curved shells along the common
shell normal.
Note: The element offset project was completed for both MD Nastran and MSC Nastran. This
section includes the complete capability description for both MD Nastran and MSC
Nastran as documented in the MD Nastran 2010 Release Guide. For MSC Nastran, the new
offset methods are available in all the linear solution sequences that calculate differential
stiffness, but the new offset capability is not available in the MSC Nastran nonlinear
solutions (SOL 106 and SOL 129).
Benefit
The enhanced offset method has the following benefits:
• DIFFERENTIAL STIFFNESS - The differential stiffness is computed for the offset so that it is
applicable to solution sequences that required differential stiffness. These include, for example,
SOL 103, SOL 105, and SOL 400.
• MASS - The effect of offset is included in the mass matrix generation.
• LOADS - The effect of offset is included in the load generation.
• GEOMETRY COMPATIBILITY - For QUAD4, TRIA3, QUADR, TRIAR, QUAD8 and
TRIA6 elements the shell normal is used as the offset direction. Thus, the new offset will
enhance solution of a model in two aspects: there is no gap in the offset geometry, and the mass
and stiffness matrices are computed based on the offset geometry. Figures New Offset Behavior
when Angle between adjacent elements is less than SNORM and New Offset Behavior when
Angle between adjacent elements is greater than SNORM demonstrate how the new offsets are
considered in conjunction with SNORM.
• NONLINEAR EFFECTS - The transformations are nonlinear so that it can be used in
nonlinear analysis such as SOL 400.
Feature Description
Differential Stiffness
The original offset method does not compute the differential stiffness for offset. Therefore, it is not
applicable to solution sequences where differential stiffness is needed such as SOL 103 or SOL 105. The
Main Index
CHAPTER 7 125
Elements
enhanced offset computes the differential stiffness for offset, using the same formulation as that of the
Lagrange RBAR element. The Lagrange multipliers are eliminated internally. For the new offset method,
the differential stiffness is computed for offsets for solution sequences that require it. These include SOL
105, SOL 400 and any linear solution that supports differential stiffness effects via the case control entry
STATSUB.
Mass Matrix
For an element, the mass matrix is computed at the offset locations of the element. The mass matrix needs
to be transformed from the offset locations to the external grid points. In performing this transformation,
mass moments of inertial are created. Without this transformation, the mass matrix for model with offsets
is only an approximation. With this transformation, the mass matrix for SOL 103, and other dynamic
solution sequences are correctly computed. The additional terms in the mass matrix may adversely affect
the solution time for dynamic solutions; therefore, a provision to disable the mass offset calculation
while retaining other offset effects is available.
Load Effects
For element loads, such as thermal, pressure, and gravity load, the loads are computed at the offset
locations of the element. These loads are transformed from the offset locations to the external grid points.
For thermal load, there are two types of effect due to offset:
• The location of thermal load is changed due to offset, i.e. the thermal load is first computed at
the element offset locations and then transformed to the external grid points. This effect is
computed for both linear solution sequences and nonlinear solution sequence SOL 400.
• The temperature load will change the length of the offset. This effect is computed for the
nonlinear solution sequence SOL 400 only.
If you don’t want these effects to be calculated, a provision to disable the offset load effects is available.
Offset Direction
For beam elements, the direction of offset is given by the WiA and WiB on the connection Bulk Data
entries.
For shell elements, the old offset direction is in z-direction of the element coordinate system. For curved
shell model, such as cylindrical shell, this approach has two deficiencies:
• The offset geometry has gap or overlap in the structure model.
• The computations of stiffness matrix, mass matrix, and element load are based on the original
geometry, which is not the same as the offset geometry.
In order to remedy these deficiencies, the new offset method for QUAD4, TRIA3, QUADR, TRIAR,
QUAD8, and TRIA6 use the shell normal as the offset direction for default.
Main Index
126 MSC Nastran 2010 Release Guide
Offsets for Beams and Shells
If you don’t want the geometric advantages of the new offset method, a provision to revert to the previous
offset behavior for shell elements is available.
Figure 7-6 Unique Grid Point Normal for Adjacent Shell Elements
Figure 7-7 New Offset Behavior when Angle between adjacent elements is less than
SNORM
Figure 7-8 New Offset Behavior when Angle between adjacent elements is greater than
SNORM
Main Index
CHAPTER 7 127
Elements
Nonlinear Analysis
For nonlinear analysis, the following are implemented for the new offset method:
• The offsets are formulated in large rotation theory.
• The differential stiffness for offsets is computed.
• For thermal loads, the length of the offsets may change due to thermal loads. This effect has
been implemented.
Input
The new offset formulation must be invoked by specifying MDLPRM,OFFDEF,option in the Bulk Data
Section. The format of the MDLPRM entry and options associated with OFFDEF are shown.
MDLPRM Format:
1 2 3 4 5 6 7 8 9 10
MDLPRM PARAM1 VAL1 PARAM2 VAL2 PARAM3 VAL3 -etc.-
Example:
MDLPRM QR6ROT 2 QRSHEAR 1 OFFDEFF LROFF
Main Index
128 MSC Nastran 2010 Release Guide
Offsets for Beams and Shells
Note that there is no Case Control modification or other modifications to the input file required. By
default, the old offset definition is used (MDLPRM,OFFDEF,ELMOFF)
Output
There is no new output associated with the new offset methodology.
Main Index
CHAPTER 7 129
Elements
Test Problems
The following test cases are available in the TPL in directory /tpl/offsetmeth:
Main Index
130 MSC Nastran 2010 Release Guide
Offsets for Beams and Shells
Main Index
CHAPTER 7 131
Elements
GUI Support
Patran
Currently Patran does not support the definition of MDLPRM,OFFDEF,offdef. However, it is expected
that this will be supported in Patran 2008r3.
SimXpert
SimXpert supports the definition of MDLPRM,OFFDEF,option. Figure 7-12 shows the GUI interface.
Main Index
132 MSC Nastran 2010 Release Guide
Offsets for Beams and Shells
Main Index
Chapter 8: MiscellaneousMSC Nastran 2010 Release Guide
8 Miscellaneous
Enhanced MONSUM
PARAM,NONCUP Usage Extended to SOL 111
Application Regions
New Input File Reader - IFPSTAR
Brake Squeal Analysis
Results and Output Changes
MSC Nastran Error List
Main Index
134 MSC Nastran 2010 Release Guide
Enhanced MONSUM
Enhanced MONSUM
Introduction
The MONSUM Bulk Data entry was introduced in MSC Nastran 2007 to enable the linear combination
of monitor results or the updating in place of a monitor result. The MSC Nastran 2007 implementation
imposed the restriction that the results to be summed must be of the same type. This restriction has been
relieved in the current delivery.
Benefits
The MONSUM feature of MSC Nastran 2007 allowed to user to perform such tasks as units conversion
on a monitor result or to combine similar types on monitor results. Users also felt a need to combine
different types of monitor points to create a special purpose response that is meaningful in the analysis
task at hand. This extension of the MONSUM provides this added capability.
Feature Description
The enhanced MONSUM, 2527 Bulk Data entry is described in the MD Nastran Quick Reference Guide.
“Legacy” input files are supported in that the alternate format shown in the guide is identical to the
standard format of earlier releases. A remark in the MONSUM description indicates that the summed
quantities must be of a similar type, specifically:
Force and moment summation monitor points: AMONPNT1, SMONPNT1, MONPNT3
Displacement monitor points: AMONDSP1 and SMONDSP1
Example
Two examples are provided in the TPL:
Monsum2.dat – This is a SOL 144 file that has five MONSUM entries. Three of these demonstrate the
legacy feature while one combines an aerodynamic monpnt1 and a monpnt3 and another combines a
structural monpnt1 with an aerodynamic monpnt1.
Monsum4.dat – This is another SOL 144 file that has a single MONSUM entry that combines a structural
mondsp1 with an aerodynamic mondsp1.
Main Index
CHAPTER 8 135
Miscellaneous
The summed results are printed as one of the monitor types with the following order of precedence:
smonpnt1, smondsp1, monpnt3, amonpnt1, amondsp1. E.g., an amonpnt1 and a monpnt3 appearing on
the same entry will result in a monpnt3 regardless of which appears first.
If different monitor results are being summed, the NAME appearing on the MONSUM should be unique
with respect to other names. For the update in place, the name can be the same.
Main Index
136 MSC Nastran 2010 Release Guide
PARAM,NONCUP Usage Extended to SOL 111
NONCUP = -1 Use uncoupled solution if there are no off-diagonal terms in any of the
modal matrices (MHH, BHH, and KHH); otherwise use coupled solution.
NONCUP > -1 Use coupled solution regardless of the existence of off-diagonal terms in
the modal matrices.
NONCUP = -2 Use uncoupled solution regardless of the existence of off-diagonal terms in
the modal matrices.
Main Index
CHAPTER 8 137
Miscellaneous
Application Regions
Introduction
A new set concept called SET3 has been added which allows one to group together a list of nodes,
elements, properties or a list of points and associate them with a unique id.
Benefits
Application region can be used for group the elements or nodes. It is necessary for total heat load, contact
loads, super element radiation load, and primitive radiation load. It is more convenient for the translator
to process the groups of FEM data.
Input
SET3 entry is used to define the application regions.
Main Index
138 MSC Nastran 2010 Release Guide
New Input File Reader - IFPSTAR
Benefits
The benefits of the IFPStar component include:
• Faster input processing (up to 40% faster for typical large models)
• SORT is not required before interpretation
• Significantly lower memory requirements
• Clearer error messaging
• Rule based definition identifies exact entry and field of illegal data
• Identification of which INCLUDE file / line number of an illegal entry
• Uses Quick Reference Guide rule base
• Provides consistent and rigorous rule checking
• Template definition of fields provides easier implementation of new features, thus reducing
development time.
• Higher precision of input tables – 64bit maintained
• The higher precision may cause slightly different answers compared to previous versions or
models run with the old Input File Processor (IFP)
• Replaces IFP, RMDUPBK, and XSORT modules with a single more efficient module
• Extensible and Pluggable to in-house or external applications (future)
• Simplifies the process of adding new entries
IFPStar significantly improves developers’ ability to add or modify Nastran bulk data entries in a very
short amount of time (less than 3 hours for a very complex entry, comparing to days using legacy IFP
module). Rather than ad-hoc parsing rules buried in multiple layers of code, within the application,
IFPStar utilizes template-based definitions for entries, which simplifies the process of adding new fields,
putting proper checks in place on the fields within an entry, adding boundary conditions, etc …
Another advantage of IFStar component is that it leverages the “component” capability of the SCA
framework, which means the component can be used in any SCA enabled application (in house or
external), and can easily be updated in the field, without the need for updating the entire installation.
Main Index
CHAPTER 8 139
Miscellaneous
SPC1 IO 12 1 3
Both IFPStar component and legacy IFP module catch the user’s error, and below is how each one issues
the error messages:
IFPStar Component:
*** USER FATAL MESSAGE 9994 (BULKPM)
Term Violation for Entity: SPC1 near line 27
SID:IO is an illegal integer value.
Main Index
140 MSC Nastran 2010 Release Guide
New Input File Reader - IFPSTAR
In RESTART runs, the “/” bulk data has been enhanced to have more user friendly commands.
Previously, the only options on the “/” bulk data entry were to remove specific sorted bulk data line
numbers, but with IFPStar the delete directives are more user friendly. Please refer to the Quick
Reference Guide for more details.
The sorted bulk data (print/punch) will have a slightly different look.
In future versions of MSC Nastran and MSC Nastran new bulk data entries will only be supported by the
IFPStar component.
Known Issues
In addition to the entries listed above, there are a few items that will not work with the IFPStar
component. MSGMESH is no longer supported. Basic replication entries are supported, but some
advanced replication applications may not work. In this case, it is recommended to use the old IFP
processor with the case control command ECHO=PUNCH to generate a bulk data input without
replications.
Since this is a brand new component, and Nastran has 30+ years of legacy, while all attempts have been
made to support the legacy, it is possible that some client models may not work with-in the bounds of
IFPStar component rules and definitions.
When this rare situation occurs with your existing models, you can get around this problem by using the
old IFP by adding the following system cell nastran system(444)=0 to the top of your input file (see next
paragraph for more details).
Main Index
CHAPTER 8 141
Miscellaneous
Main Index
142 MSC Nastran 2010 Release Guide
Results and Output Changes
Main Index
CHAPTER 8 143
Miscellaneous
Details will be clear from the descriptions of these parameters in the ENFMETH and ENFMOTN (p. 724)
in the MD/MSC Nastran Quick Reference Guide.
NEW OPTMIZER
Optimization tasks that previously used the BIGDOT optimization algorithm now employ the IPOPT
optimization algorithm (See The IPOPT Algorithm (App. C) in the Design Sensitivity and Optimization
User’s Guide). These are typically topology optimization tasks or tasks with many design variables. If
the user explicitly selects the BIGDOT algorithm using OPTCOD=BIGDOT on the DOPTPRM bulk
data entry, the IPOTPT algorithm will be used in its place and a User Information Message will be printed
that indicates this. It is expected that the results from the two algorithms will be similar, but not exactly
the same.
Main Index
144 MSC Nastran 2010 Release Guide
MSC Nastran Error List
Main Index
Ap. A: Connectors
MSC Nastran 2010 Release Guide
A Connectors
Connectors Output
Main Index
146 MSC Nastran 2010 Release Guide
Connectors Output
Connectors Output
0 SUBCASE 1
FREQUENCY = 1.000000E+01
C O M P L E X F O R C E S I N W E L D E L E M E N T S ( C W E L D P )
(REAL/IMAGINARY)
ELEMENT AXIAL MAX STRESS MIN STRESS MAX STRESS MIN STRESS MAXIMUM BEARING
ID STRESS END-A END-A END-B END-B SHEAR STRESS STRESS
30 3.525211E+00 2.045557E+03 -2.038507E+03 6.397730E+01 -5.692688E+01 2.092356E+02 4.010323E+01
-4.228557E-01 2.446496E+02 -2.454954E+02 6.845903E+00 -7.691615E+00 2.511545E+01 4.812626E+00
0 SUBCASE 1
FREQUENCY = 2.000000E+01
C O M P L E X S T R E S S E S I N W E L D E L E M E N T S ( C W E L D P )
(REAL/IMAGINARY)
ELEMENT AXIAL MAX STRESS MIN STRESS MAX STRESS MIN STRESS MAXIMUM BEARING
ID STRESS END-A END-A END-B END-B SHEAR STRESS STRESS
30 3.521090E+00 2.046250E+03 -2.039208E+03 6.432576E+01 -5.728358E+01 2.094103E+02 4.010902E+01
-4.218517E-01 2.448205E+02 -2.456642E+02 6.932804E+00 -7.776507E+00 2.515803E+
Main Index
Appendix A 147
Connectors
S T R E S S E S I N S E A M E L E M E N T S ( C S E A M )
0 CORNER ------CENTER AND CORNER POINT STRESSES--------- DIR. COSINES MEAN
ELEMENT-ID GRID-ID NORMAL SHEAR PRINCIPAL -A- -B- -C- PRESSURE VON MISES
10001 0GRID CS 8 GP
CENTER X 7.747896E+05 XY -3.827610E+03 A 7.748116E+05 LX 1.00 0.00-0.01 -2.940678E+05 7.270885E+05
Y 1.074136E+05 YZ 1.673470E-10 B 2.502929E-09 LY-0.01 0.00-1.00
Z 2.328306E-09 ZX 1.746230E-09 C 1.073916E+05 LZ 0.00 1.00 0.00
90001 X 1.711155E+06 XY -7.739222E+03 A 1.711200E+06 LX 1.00 0.00-0.01 -8.162711E+05 1.342475E+06
Y 3.764584E+05 YZ -3.868169E+03 B 3.602726E+05 LY-0.01 0.23-0.97
Z 3.611997E+05 ZX -5.157554E+01 C 3.773406E+05 LZ 0.00 0.97 0.23
90002 X 1.707039E+06 XY -7.739222E+03 A 1.707084E+06 LX 1.00 0.00-0.01 -8.103257E+05 1.345162E+06
Y 3.646422E+05 YZ 3.868169E+03 B 3.572576E+05 LY-0.01-0.47-0.88
Z 3.592958E+05 ZX -5.157554E+01 C 3.666358E+05 LZ 0.00 0.88-0.47
90003 X -1.638654E+05 XY 8.400235E+01 A -1.563204E+05 LX 0.01 0.00-1.00 2.261826E+05 1.983753E+05
Y -1.563954E+05 YZ 3.868169E+03 B -3.583610E+05 LY 1.00-0.02 0.01
Z -3.582869E+05 ZX -5.157554E+01 C -1.638663E+05 LZ 0.02 1.00 0.00
90004 X -1.655750E+05 XY 8.400235E+01 A -1.580980E+05 LX 0.01 0.00-1.00 2.286519E+05 2.005495E+05
Y -1.581723E+05 YZ -3.868169E+03 B -3.622819E+05 LY 1.00 0.02 0.01
Z -3.622085E+05 ZX -5.157554E+01 C -1.655759E+05 LZ-0.02 1.00 0.00
90005 X 1.727548E+06 XY -7.739222E+03 A 1.727593E+06 LX 1.00 0.00-0.01 -8.258101E+05 1.352764E+06
Y 3.830623E+05 YZ -3.868169E+03 B 3.659432E+05 LY-0.01 0.22-0.98
Z 3.668194E+05 ZX 5.157554E+01 C 3.838939E+05 LZ 0.00 0.98 0.22
90006 X 1.722568E+06 XY -7.739222E+03 A 1.722612E+06 LX 1.00 0.00-0.01 -8.186157E+05 1.356026E+06
Y 3.703815E+05 YZ 3.868169E+03 B 3.612509E+05 LY-0.01-0.39-0.92
Z 3.628978E+05 ZX 5.157554E+01 C 3.719841E+05 LZ 0.00 0.92-0.39
90007 X -1.698541E+05 XY 8.400235E+01 A -1.598039E+05 LX 0.01 0.00-1.00 2.312129E+05 1.993407E+05
Y -1.598779E+05 YZ 3.868169E+03 B -3.639800E+05 LY 1.00-0.02 0.01
Z -3.639066E+05 ZX 5.157554E+01 C -1.698548E+05 LZ 0.02 1.00 0.00
90008 X -1.706989E+05 XY 8.400235E+01 A -1.607165E+05 LX 0.01 0.00-1.00 2.324332E+05 2.003621E+05
Y -1.607901E+05 YZ -3.868169E+03 B -3.658836E+05 LY 1.00 0.02 0.01
Z -3.658106E+05 ZX 5.157554E+01 C -1.706996E+05 LZ-0.02 1.00 0.00
10002 0GRID CS 8 GP
CENTER X 7.406084E+05 XY 9.462977E+02 A 7.406120E+05 LX 1.00 0.00 0.00 -2.397683E+05 7.514921E+05
Y -2.130364E+04 YZ 4.292815E-10 B -2.130482E+04 LY 0.00 1.00 0.00
Z -1.583248E-08 ZX 1.333328E+03 C -2.400266E+00 LZ 0.00 0.00-1.00
90009 X 1.623490E+06 XY 1.970375E+03 A 1.623494E+06 LX 1.00 0.00 0.00 -6.671043E+05 1.446252E+06
Y 8.306726E+04 YZ 9.464031E+02 B 8.306052E+04 LY 0.00 1.00 0.00
Z 2.947562E+05 ZX 1.612613E+03 C 2.947584E+05 LZ 0.00 0.00-1.00
90010 X 1.623357E+06 XY 1.970375E+03 A 1.623361E+06 LX 1.00 0.00 0.00 -6.669126E+05 1.446268E+06
Y 8.317433E+04 YZ -9.464031E+02 B 8.316755E+04 LY 0.00 1.00 0.00
Z 2.942068E+05 ZX 1.612613E+03 C 2.942091E+05 LZ 0.00 0.00-1.00
90011 X -1.337316E+05 XY -7.777978E+01 A -1.233649E+05 LX-0.01-0.01-1.00 1.839953E+05 1.666055E+05
Y -1.233709E+05 YZ -9.464031E+02 B -2.949047E+05 LY 1.00 0.01-0.01
Z -2.948834E+05 ZX 1.612613E+03 C -1.337162E+05 LZ-0.01 1.00-0.01
Main Index
148 MSC Nastran 2010 Release Guide
Connectors Output
S T R E S S E S I N S E A M E L E M E N T S ( C S E A M )
0 CORNER ------CENTER AND CORNER POINT STRESSES--------- DIR. COSINES MEAN
ELEMENT-ID GRID-ID NORMAL SHEAR PRINCIPAL -A- -B- -C- PRESSURE VON MISES
90012 X -1.333445E+05 XY -7.777978E+01 A -1.228786E+05 LX-0.01-0.01-1.00 1.834361E+05 1.662438E+05
Y -1.228843E+05 YZ 9.464031E+02 B -2.941010E+05 LY 1.00-0.01-0.01
Z -2.940796E+05 ZX 1.612613E+03 C -1.333288E+05 LZ 0.01 1.00-0.01
90013 X 1.608190E+06 XY 1.970375E+03 A 1.608193E+06 LX 1.00 0.00 0.00 -6.591450E+05 1.435601E+06
Y 7.755697E+04 YZ 9.464031E+02 B 7.755026E+04 LY 0.00 1.00 0.00
Z 2.916883E+05 ZX 1.054044E+03 C 2.916916E+05 LZ 0.00 0.00-1.00
90014 X 1.608294E+06 XY 1.970375E+03 A 1.608298E+06 LX 1.00 0.00 0.00 -6.592958E+05 1.435494E+06
Y 7.790112E+04 YZ -9.464031E+02 B 7.789438E+04 LY 0.00 1.00 0.00
Z 2.916921E+05 ZX 1.054044E+03 C 2.916954E+05 LZ 0.00 0.00-1.00
90015 X -1.357683E+05 XY -7.777978E+01 A -1.230557E+05 LX-0.01-0.01-1.00 1.835484E+05 1.627915E+05
Y -1.230615E+05 YZ -9.464031E+02 B -2.918279E+05 LY 1.00 0.01-0.01
Z -2.918155E+05 ZX 1.054044E+03 C -1.357617E+05 LZ-0.01 1.00-0.01
90016 X -1.356183E+05 XY -7.777978E+01 A -1.228063E+05 LX-0.01-0.01-1.00 1.833317E+05 1.627466E+05
Y -1.228120E+05 YZ 9.464031E+02 B -2.915773E+05 LY 1.00-0.01-0.01
Z -2.915649E+05 ZX 1.054044E+03 C -1.356115E+05 LZ 0.01 1.00-0.01
10003 0GRID CS 8 GP
CENTER X 1.284104E+03 XY -4.129671E+01 A 1.285049E+03 LX 1.00 0.02 0.00 -2.544763E+02 1.610510E+03
Y -5.206752E+02 YZ 6.457412E-10 B -5.216197E+02 LY-0.02 1.00 0.00
Z -2.142042E-08 ZX 8.847564E-08 C -2.142039E-08 LZ 0.00 0.00-1.00
90017 X 2.416318E+03 XY -5.225373E+01 A 2.417096E+03 LX 1.00 0.01 0.00 -4.974160E+02 3.080820E+03
Y -1.092519E+03 YZ -4.401031E+01 B -1.094830E+03 LY-0.01 1.00 0.03
Z 1.684483E+02 ZX -5.868064E-01 C 1.699818E+02 LZ 0.00 0.03-1.00
90018 X 2.495232E+03 XY -5.225373E+01 A 2.496019E+03 LX 1.00 0.02 0.00 -6.114019E+02 3.040780E+03
Y -9.753662E+02 YZ 4.401031E+01 B -9.776510E+02 LY-0.02 1.00-0.03
Z 3.143401E+02 ZX -5.868064E-01 C 3.158376E+02 LZ 0.00-0.03-1.00
90019 X -8.759534E+01 XY -3.033968E+01 A -2.349008E+01 LX-0.42-0.08-0.91 1.068964E+02 1.504556E+02
Y -5.015059E+01 YZ 4.401031E+01 B -1.968506E+02 LY 0.88-0.30-0.38
Z -1.829433E+02 ZX -5.868064E-01 C -1.003486E+02 LZ 0.24 0.95-0.19
90020 X -1.375186E+02 XY -3.033968E+01 A -7.612272E+01 LX-0.44 0.04-0.90 1.790078E+02 2.061600E+02
Y -9.965966E+01 YZ -4.401031E+01 B -3.093700E+02 LY 0.88 0.21-0.42
Z -2.998451E+02 ZX -5.868064E-01 C -1.515307E+02 LZ-0.17 0.98 0.13
90021 X 2.982642E+03 XY -5.225373E+01 A 2.983355E+03 LX 1.00 0.01 0.00 -8.526937E+02 3.380599E+03
Y -8.465572E+02 YZ -4.401031E+01 B -8.487935E+02 LY-0.01 1.00 0.03
Z 4.219966E+02 ZX 5.868065E-01 C 4.235193E+02 LZ 0.00 0.03-1.00
90022 X 2.948929E+03 XY -5.225373E+01 A 2.949649E+03 LX 1.00 0.01 0.00 -8.039978E+02 3.369357E+03
Y -8.420306E+02 YZ 4.401031E+01 B -8.444359E+02 LY-0.01 1.00-0.04
Z 3.050948E+02 ZX 5.868065E-01 C 3.067800E+02 LZ 0.00-0.04-1.00
90023 X -2.039378E+02 XY -3.033968E+01 A -1.402171E+02 LX-0.43-0.02-0.90 2.671824E+02 2.728479E+02
Y -1.611178E+02 YZ 4.401031E+01 B -4.434710E+02 LY 0.90-0.16-0.42
Z -4.364915E+02 ZX 5.868065E-01 C -2.178590E+02 LZ 0.13 0.99-0.09
90024 X -1.412352E+02 XY -3.033968E+01 A -7.500764E+01 LX-0.41 0.04-0.91 1.766120E+02 1.980148E+02
Y -9.800105E+01 YZ -4.401031E+01 B -3.004030E+02 LY 0.89 0.22-0.39
Z -2.905998E+02 ZX 5.868065E-01 C -1.544254E+02 LZ-0.18 0.98 0.12
S T R E S S E S I N S E A M E L E M E N T S ( C S E A M )
0 CORNER ------CENTER AND CORNER POINT STRESSES--------- DIR. COSINES MEAN
ELEMENT-ID GRID-ID NORMAL SHEAR PRINCIPAL -A- -B- -C- PRESSURE VON MISES
10004 0GRID CS 8 GP
CENTER X 2.857427E+00 XY -5.724032E-02 A 7.595094E+00 LX-0.01 0.00-1.00 -3.483943E+00 6.644488E+00
Y 7.594403E+00 YZ -5.420588E-10 B 1.257286E-08 LY 1.00 0.00-0.01
Z 1.257285E-08 ZX -6.053597E-09 C 2.856735E+00 LZ 0.00 1.00 0.00
90025 X 1.577084E+00 XY 5.002377E+00 A 6.410882E+00 LX 0.72-0.69 0.05 -2.286139E+00 9.076537E+00
Y 1.218060E+00 YZ 1.910919E-01 B -3.610427E+00 LY 0.69 0.72 0.03
Z 4.063272E+00 ZX 2.547832E-03 C 4.057961E+00 LZ 0.06-0.02-1.00
90026 X -5.694098E+00 XY 5.002377E+00 A -8.618130E-01 LX 0.72-0.04 0.69 8.216681E+00 1.117548E+01
Y -6.043215E+00 YZ -1.910919E-01 B -1.292361E+01 LY 0.69 0.06-0.72
Z -1.291273E+01 ZX 2.547832E-03 C -1.086462E+01 LZ-0.01 1.00 0.07
90027 X 3.802032E+00 XY -5.116858E+00 A 1.589757E+01 LX-0.39 0.01-0.92 -4.467181E+00 1.785942E+01
Y 1.373110E+01 YZ -1.910919E-01 B -4.134058E+00 LY 0.92 0.01-0.39
Z -4.131593E+00 ZX 2.547832E-03 C 1.638033E+00 LZ-0.01 1.00 0.01
90028 X 1.120986E+01 XY -5.116858E+00 A 2.345315E+01 LX-0.39 0.92-0.02 -1.516737E+01 1.288174E+01
Y 2.131121E+01 YZ 1.910919E-01 B 9.069369E+00 LY 0.92 0.39 0.01
Z 1.298105E+01 ZX 2.547832E-03 C 1.297959E+01 LZ 0.02-0.02-1.00
90029 X -5.801891E+00 XY 5.002377E+00 A -9.705124E-01 LX 0.72 0.04 0.69 8.360745E+00 1.124266E+01
Y -6.152861E+00 YZ 1.910919E-01 B -1.313789E+01 LY 0.69-0.05-0.72
Z -1.312748E+01 ZX -2.547842E-03 C -1.097383E+01 LZ 0.01 1.00-0.06
90030 X 1.536345E+00 XY 5.002377E+00 A 6.378676E+00 LX 0.72-0.69-0.05 -2.238929E+00 9.062510E+00
Y 1.195284E+00 YZ -1.910919E-01 B -3.641881E+00 LY 0.69 0.72-0.03
Z 3.985157E+00 ZX -2.547842E-03 C 3.979991E+00 LZ-0.06 0.02-1.00
90031 X 1.171584E+01 XY -5.116858E+00 A 2.348970E+01 LX-0.40 0.92 0.03 -1.534583E+01 1.260059E+01
Y 2.126247E+01 YZ -1.910919E-01 B 9.489802E+00 LY 0.92 0.40-0.01
Z 1.305916E+01 ZX -2.547842E-03 C 1.305798E+01 LZ-0.02 0.02-1.00
90032 X 4.514247E+00 XY -5.116858E+00 A 1.643190E+01 LX-0.39-0.01-0.92 -4.943524E+00 1.805928E+01
Y 1.423316E+01 YZ 1.910919E-01 B -3.919224E+00 LY 0.92-0.01-0.39
Z -3.916836E+00 ZX -2.547842E-03 C 2.317893E+00 LZ 0.01 1.00-0.01
Main Index
Appendix A 149
Connectors
Main Index
150 MSC Nastran 2010 Release Guide
Connectors Output
Main Index