Nastran 2019 Doc Release

MSC Nastran 2019
MSC Nastran Release Guide
Release Guide
Corporate Europe, Middle East, Africa
MSC Software Corporation MSC Software GmbH
4675 MacArthur Court, Suite 900 Am Moosfeld 13
Newport Beach, CA 92660 81829 Munich, Germany
Telephone: (714) 540-8900 Telephone: (49) 89 431 98 70
Toll Free Number: 1 855 672 7638 Email: [email protected]
Email: [email protected]
Japan Asia-Pacific
MSC Software Japan Ltd. MSC Software (S) Pte. Ltd.
Shinjuku First West 8F 100 Beach Road
23-7 Nishi Shinjuku #16-05 Shaw Tower
1-Chome, Shinjuku-Ku Singapore 189702
Tokyo 160-0023, JAPAN Telephone: 65-6272-0082
Telephone: (81) (3)-6911-1200 Email: [email protected]
Email: [email protected]
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  2018 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. Additional terms and conditions and/or notices may apply for certain third party software. Such
additional third party software terms and conditions and/or notices may be set forth in documentation and/or at
http://www.mscsoftware.com/thirdpartysoftware (or successor website designated by MSC from time to time).
PCGLSS 8.0, Copyright © 1992-2016, Computational Applications and System Integration Inc. All rights reserved.
PCGLSS 8.0 is licensed from Computational Applications and System Integration Inc.
MSC, Dytran, Marc, MSC Nastran, Patran, the MSC Software corporate logo, e-Xstream, Digimat, and Simulating
Reality are trademarks or registered trademarks of the MSC Software Corporation and/or its subsidiaries in the
United States and/or other countries.
NASTRAN is a registered trademark of NASA. FLEXlm and FlexNet Publisher are trademarks or registered
trademarks of Flexera Software. All other trademarks are the property of their respective owners.
Use, duplicate, or disclosure by the U.S. Government is subjected to restrictions as set forth in FAR 12.212
(Commercial Computer Software) and DFARS 227.7202 (Commercial Computer Software and Commercial
Computer Software Documentation), as applicable.
U.S. Patent 9,361,413

December 21, 2018
NA:V2019:Z:Z:Z:DC-REL-PDF
Main Index
Documentation Feedback
At MSC Software, we strive to produce the highest quality documentation and welcome your feedback.
If you have comments or suggestions about our documentation, write to us at: documentation-
[email protected].
Please include the following information with your feedback:
 Document name
 Release/Version number
 Chapter/Section name
 Topic title (for Online Help)
 Brief description of the content (for example, incomplete/incorrect information, grammatical
errors, information that requires clarification or more details and so on).
 Your suggestions for correcting/improving documentation
You may also provide your feedback about MSC Software documentation by taking a short 5-minute
survey at: http://msc-documentation.questionpro.com.
Note: The above mentioned e-mail address is only for providing documentation specific
feedback. If you have any technical problems, issues, or queries, please contact Technical
Support.
Contents
MSC Nastran 2019 Release Guide
Contents
Preface
Preface to the MSC Nastran 2019.0 Release Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
List of MSC Nastran Books . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Corrected and Fixed Error List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Training and Internet Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
MSC Nastran Documentation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
MSC Nastran Documentation Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Overview of MSC Nastran 2019.0

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Dynamic Analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Advanced Implicit Nonlinear (SOL 400) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Advanced Non linear Explicit (SOL 700) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Numerical Methods and High Performance Computing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Pyramid Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Module Instantiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
2 Dynamic Analysis
Rforce/Grav Loads Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Advantages of new features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Example Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
SOL 128 Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Main Index
2 MSC Nastran 2019 Release Guide
Advantages of new features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Example Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3 Advanced Implicit Nonlinear (SOL 400)

Contact Model Check (2019) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Guidelines and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Output of Advanced Composite in Nastran Traditional Format of Layer Composite . . . . . . . . . . . . . . . . 33
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Monitor Points with SOL 400 NLSTAT and NLTRAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Guidelines and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Examples (/tpl/mpt400/mon400_1.dat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
4 Advanced Nonlinear Explicit (SOL 700)

Articulated Total Body (ATB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
ATB Input Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Nastran SOL700 Input Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Termination Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Viscoelastic Material - MATVE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Initial Metric Method (IMM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
IMM Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Air bag fabric material model (MATFAB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Main Index
Contents 3
SCA User Defined Services (UDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Localized cohesive friction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
DMP for the auto coupling approach. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Simulating flow through failed shells with the auto coupling approach. . . . . . . . . . . . . . . . . . . . . . . . . . 53
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
5 Numerical Methods and High Performance Computing

New Features of SOLVE=AUTO in MSC Nastran 2019.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Enhancements to SOL 200 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Enhancements to SOL 111 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
New FASTFR with SMP parallelization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Technical Discussion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Improved Parallel Performance for Acoustic Coupling Matrix Reduction Using ACMS . . . . . . . . . . . . . . 60
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Improved Performance for the RANDOM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
New DMP Implementation of Modal Participation Factor Calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Test Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Change to Default Parallel Scheduling for ACMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Test Case . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Main Index
Improved performance for large Adams mnf file generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
6 Pyramid Elements
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Feature Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
User Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Guidelines and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7 Module Instantiation
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Classic Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Enhanced Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Loading and Boundary Conditions in Secondary Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Secondary Module's Bulk Data Section . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Module Definition Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Guidelines and Limitations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Flat Plate Model with One Primary and Three Secondary Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
8 User Interface
The Nastran HDF5 Result Database (NH5RDB) Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Benefits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
Test Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
9 Platform Support
Supported Hardware and Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Software Development Kit (SDK) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112
Main Index
Preface
Preface
 Preface to the MSC Nastran 2019.0 Release Guide 6


List of MSC Nastran Books 6

Technical Support 7
 Training and Internet Resources 7

MSC Nastran Documentation 8
Main Index
Preface to the MSC Nastran 2019.0 Release Guide

This Release Guide contains descriptions for the MSC Nastran 2019.0 version and supersedes the MSC
Nastran 2018.0 Release Guide.
List of MSC Nastran Books

A list of some of the MSC Nastran documents is as follows:
Installation and Release Guides

 Installation and Operations Guide
 Release Guide
Reference Guides
 Quick Reference Guide
 DMAP Programmer’s Guide
 Reference Guide
 Utilities Guide
Demonstration Guides
 Linear Analysis
 Implicit Nonlinear (SOL 400)
 Explicit Nonlinear (Dytran based SOL 700)
User’s Guides
 Getting Started
 Linear Static Analysis
 Dynamic Analysis
 Embedded Fatigue
 Embedded Vibration Fatigue
 Thermal Analysis
 Superelements
 Design Sensitivity and Optimization
 Rotordynamics
 Implicit Nonlinear (SOL 400)
 Explicit Nonlinear (SOL 700)
 Aeroelastic Analysis
 User Defined Services
Main Index
7
Preface
 Non Linear (SOL 400)

 High Performance Computing
 DEMATD
You may find any of these documents from MSC Software at:
http://simcompanion.mscsoftware.com/infocenter/index?page=home
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)
The SimCompanion link above gives you access to the wealth of resources for MSC Software products. Here
you will find product and support contact information, product documentations, knowledge base articles,
product error list, knowledge base articles and SimAcademy Webinars. It is a searchable database which
allows you to find articles relevant to your inquiry. Valid MSC customer entitlement and login is required to
access the database and documents. It is a single sign-on that gives you access to product documentation for
complete list of products from MSC Software, allows you to manage your support cases, and participate in
our discussion forums.
Corrected and Fixed Error List

For a list of corrected defects in the MSC Nastran 2019.0 release, please visit our Simcompanion site and see:
https://simcompanion.mscsoftware.com/infocenter/index?page=content&id=KI8008006
Training and Internet Resources

MSC Software (www.mscsoftware.com)
The MSC Software corporate site with information on the latest events, products, and services for the
CAD/CAE/CAM marketplace.
http://simcompanion.mscsoftware.com
The SimCompanion link above gives you access to the wealth of resources for MSC Software products. Here
you will find product and support contact information, product documentations, knowledge base articles,
product error list, knowledge base articles and SimAcademy Webinars. It is a searchable database which
allows you to find articles relevant to your inquiry. Valid MSC customer entitlement and login is required to
access the database and documents. It is a single sign-on that gives you access to product documentation for
complete list of products from MSC Software, allows you to manage your support cases, and participate in
our discussion forums.
http://www.mscsoftware.com/msc-training
Main Index
The MSC-Training link above will point you to schedule and description of MSC Seminars. Following
courses are recommended for beginning MSC Nastran users.
NAS101A - Linear Static and Normal Modes Analysis using MSC Nastran
This course serves as an introduction to finite element analysis. It includes discussion of basic features
available in MSC Nastran for solving structural engineering problems. In this course, all finite element
models will be created and edited using a text editor, not a graphical pre-processor. Proper data structure of
the MSC Nastran input file is covered. At the conclusion of seminar, the student will be familiar with
fundamental usage of MSC Nastran.
NAS101B - Advanced Linear Analysis using MSC Nastran
This course is a continuation of NAS101A - Linear Static and Normal Modes Analysis using MSC Nastran.
In this class, you will learn: Theory of buckling analysis and how to perform a buckling analysis About rigid
elements - MPC, RBAR,RBE2, and RBE3 Modeling with interface element CINTC and connectors
Lamination theory and composite materials MSC Nastran composite theory Failure theories Linear contact
and permanent glued contact Different model checks Modeling tips and tricks
NAS120 - Linear Static Analysis using MSC Nastran and Patran
This seminar introduces basic finite element analysis techniques for linear static, normal modes, and buckling
analysis of structures using MSC Nastran and Patran. MSC Nastran data structure, the element library,
modeling practices, model validation, and guidelines for efficient solutions are discussed and illustrated with
examples and workshops. Patran will be an integral part of the examples and workshops and will be used to
generate and verify illustrative MSC Nastran models, manage analysis submission requests, and visualize
results. This seminar provides the foundation required for intermediate and advanced MSC Nastran
applications.
MSC Nastran Documentation

For quick access to the full set of MSC Nastran Documentation on Windows, do the following:
1. Go to your MSCNastran_Installation_DIR\20190\doc\pdf_nastran\folder.
2. Right-click on nastran_library.pdf to create a shortcut to the Windows Desktop.
3. Click Send to --> Desktop
This creates a shortcut to your Windows Desktop.
Main Index
9
Preface
MSC Nastran Documentation Requirements

The following browsers are recommended to view and navigate through the PDF based MSC Nastran
documentation:
Desktop
Vendor Environment Browser Browser Version
Linux (64-bit) KDE Konqueror 4.3.4 or higher
Linux (64-bit) Gnome Evince 2.28.2 or higher
Microsoft (64-bit) Windows 7 Adobe Reader 10.1.4 or higher
Windows 10
Note: Adobe has dropped support for Reader on Linux. The browsers in the above table have been
tested and work with the current version of the MSC Nastran Documentation.
Utilities
The MSC utilities including MultiOpt described in this release guide have been moved from the Installation
and Operators Guide to their own manual labeled MSC Nastran Utilities Guide.
Main Index
Main Index
Chapter 1: Overview of MSC Nastran 2019.0
Overview of MSC Nastran

1 2019.0

Introduction 12
MSC Nastran Implicit Nonlinear (SOL 600) User’s GuideMSC Nastran 2019 Release Guide
Main Index
Introduction
Introduction
MSC Software is pleased to introduce you to the exciting new technologies in MSC Nastran 2019.0.—the
premier and trusted CAE solution for aerospace, automotive, defense, and manufacturing industries
worldwide. This release includes new features and enhancements in following topics:
Dynamic Analysis
 Rforce/Grav Loads Enhancements, 16
 SOL 128 Enhancements, 19
Advanced Implicit Nonlinear (SOL 400)

 Contact Model Check (2019), 28
 Output of Advanced Composite in Nastran Traditional Format of Layer Composite, 33
 Monitor Points with SOL 400 NLSTAT and NLTRAN, 36
Advanced Non linear Explicit (SOL 700)

 Articulated Total Body (ATB), 43
 Viscoelastic Material - MATVE, 45
 Initial Metric Method (IMM), 45
 Air bag fabric material model (MATFAB), 46
 SCA User Defined Services (UDS), 47
 Localized cohesive friction, 50
 DMP for the auto coupling approach, 52
 Simulating flow through failed shells with the auto coupling approach, 53
Numerical Methods and High Performance Computing

 New Features of SOLVE=AUTO in MSC Nastran 2019.0, 55
 New FASTFR with SMP parallelization, 57
 Improved Parallel Performance for Acoustic Coupling Matrix Reduction Using ACMS, 60
 Improved Performance for the RANDOM Module, 61
 New DMP Implementation of Modal Participation Factor Calculations, 62
 Change to Default Parallel Scheduling for ACMS, 63
 Improved performance for large Adams mnf file generation, 66
Pyramid Elements
 Pyramid Elements, 68
Main Index
CHAPTER 1 13
Overview of MSC Nastran 2019.0
Module Instantiation
 Module Instantiation, 82
User Interface
 The Nastran HDF5 Result Database (NH5RDB) Enhancement, 98
Platform Support
 Supported Hardware and Operating Systems, 112
Main Index
Introduction
Main Index
Chapter 2: Dynamic Analysis
2 Dynamic Analysis

Rforce/Grav Loads Enhancements 16
 SOL 128 Enhancements 19
Main Index
Rforce/Grav Loads Enhancements
Introduction
Current Nastran implementation allows user to apply GRAV and RFORCE loads to the complete model. However, in
certain application, there is a need to apply these forces only to certain portion of the model and not to the complete model.
In this release, an option is created such that user can apply gravity loading (GRAV) and rotational force (RFORCE) to just
a portion of the structure.
Advantages of new features

The new feature gives the user more flexibility to reproduce realistic loading conditions. For example, in case of a rotating
structure mounted on a support structure, the RFORCE may only need to be applied to rotor grids only.
User Interface
GRAVSET
Default = 0
A PARAM, GRAVSET, n where n is a Bulk Data SET1 entry, allows the user to apply gravity loading (GRAV) to just a
portion of the structure. GRAVSET like GRAV loading is global and is computed once at the beginning of the analysis.
The Bulk Data SET1 n defines the GRIDS to which the gravity loading is to be applied. GRAVSET can appear in either
the Bulk Data or ABOVE or IN the 1st Subcase. A GRAVSET appearing in any other Subcase will be ignored and may
cause incorrect results. A GRAVSET appearing in or above the first subcase takes precedence over a GRAVSET appearing
in Bulk Data. See also the companion RFORSET entry. If there is no GRAV loading called out, then PARAM, GRAVSET,
n needs to be removed from the run.
RFORSET
Default = 0
A PARAM, RFORSET, n where n is a Bulk Data SET1 entry, allows the user to apply rotational force loading (RFORCE)
to just a portion of the structure. RFORSET like RFORCE loading is global and is computed once at the beginning of the
analysis. The Bulk Data SET1 n defines the GRIDS to which the rotational force loading is to be applied. RFORSET can
appear in either the Bulk Data or ABOVE or IN the 1st Subcase. A RFORSET appearing in any other Subcase will be
ignored and may cause incorrect results. A RFORSET appearing in or above the first subcase takes precedence over a
RFORSET appearing in Bulk Data. See also the companion GRAVSET entry. If there is no RFORCE loading called out,
then PARAM, RFORSET, n needs to be removed from the run.
Example
Rectangular Plate
A rectangular plate model is used to demonstrate the application of new feature for gravity loading.
Main Index
CHAPTER 2 17
Dynamic Analysis
The portion where gravity loads need to be applied is highlighted in the figure above. This portion can be defined as part
of a set using following line:
SET1 99 20 21 41 42 62 63 83
84 104 105
In order to apply loads only to the grids selected in above set entry following line is included in case control or bulk data
section:
PARAM,GRAVSET,99
Load Output
a. With PARAM,GRAVSET,99
Main Index
b. Without GRAVSET
Example Summary
All the test cases analyzed for testing are available in "../tpl/s128_v19/" folder. Here is a brief description for all the test
cases:
Different combination of RFORSET and GRAVSET for the plate model
grav_rfor_e1
grav_rfor_e2
grav_rfor_e3
grav_rfor_e4
grav_rfor_e5
grav_rfor_e6
grav_rfor_e7
grav_rfor_e8
grav_rfor_e9
grav_rfor_fat1
grav_rfor_fat2
Main Index
CHAPTER 2 19
Dynamic Analysis
SOL 128 Enhancements

SOL 128, also known as nonlinear harmonic response or SOL SENLHARM, was a pre-release at MSC Nastran version
2008 (around the time of MD R3), but was validated for use at version 2010. It allows the inclusion of discrete
nonlinearities to be added to a harmonic response analysis via NOLINi, NLRGAP or NLRSFD type entries. The frequency
domain problem is solved as a time domain problem using Fourier series and Newton iteration. As long as the nonlinearities
remain relatively light, several types of problems may be solved without needing to resort to fully blown nonlinear transient
analysis. The theory of the harmonic balance method and its implementation in MSC Nastran is based mainly on reference
[1].
In this release, goal is to address the limitations observed in SOL 128 and make the analysis more robust to avoid
convergence failures. The key requirements identified for this project are
1. Resetting initial conditions for a run with non-converged frequencies
2. Produce NLLOAD output
3. Output nonlinear loads and displacement for harmonics > 0
4. Implement continuation procedure
Advantages of new features

1. Resetting initial conditions for a run of non-converged frequencies
SOL 128 works well when the solution converges. However, handling of situations of non-convergence needs
improvement.
Non-convergence can occur when the problem has simply become too nonlinear to be handled by the assumptions
of the harmonic balance method programmed in SOL 128. However, it is often the case that the region of
instability only persists for a small frequency interval. The current capability uses the solution at the previously
converged frequency as the initial conditions for the problem at the current excitation frequency. If the solution
at the current frequency does not converge, the response at this frequency is set to zero and the code moves to the
next frequency to be analyzed, retaining the solution at the previously converged frequency as the initial conditions.
This may or may not allow solutions at subsequent frequencies to be found. If no solution is found at the next
frequency, the logic repeats and will do so until all excitation frequencies have been tried.
It is desirable to be able to force the initial conditions for a particular excitation frequency to zero after a certain
number of non-converged frequencies. A new user defined parameter will be introduced to determine number of
frequency steps after which the initial conditions are reset.
2. NLLOAD output
There is no NLLOAD output for SOL 128, so loads defined on the NOLINi, NLRGAP or NLRSFD entries
cannot be output to the f06/op2 files. The goal for this task is to produce nonlinear harmonic loads for each
harmonic selected for the analysis.
3. Output of harmonics > 0
Output responses for the harmonics other than the fundamental.
The responses for harmonics other than the fundamental are computed, but they are not made available to the user.
Part of the problem is a loop to output the responses and a format in which to post the results once they are
Main Index
obtained. A similar issue persists for cyclic symmetry. A convenient method of outputting the harmonic data in
concise, well labelled format is needed.
For frequency dependent output, displacements will be produced for each harmonic selected for analysis. For
transient output, one final set of non-linear displacements will be presented.
4. Continuation Procedure
For certain non-linear problems, use of continuation procedure can result in more robust analysis and can capture
nonlinear response accurately which cannot be done with conventional analysis. In continuation procedure,
excitation frequency is treated as a dependent variable along with rest of the harmonic state variables. Thus, the
problem size is increased by one and an additional equation is required to solve the equation
User Interface
A new entry NHRMPRM is introduced in this version to specify all the nonlinear frequency response analysis parameters
in one place.
NHRMPRM Parameters for Nonlinear frequency response analysis (SOL 128)
1 2 3 4 5 6 7 8 9 10
NHRMPRM PARAM1 VAL1 PARAM2 VAL2
Var Name Type/ Default Description

NLHRED I = -1 Use reduction for nonlinear analysis.
NHPLUS I = 20 Number of extra points to avoid aliasing.
NLHTOL R = 1.0E-5 Tolerance for convergence.
NLHTWK R = 1.1 Push-off factor for line search in case convergence fails.
MXICODE0 I=5 If solution fails to converge for mxicode0 steps, new trial displacement
is used.
TICPNCH I=0 Write a tic card for each DOF to start transient run.
MNCSF I = 1000 Max number of non-converged sequential frequencies for RESET.
MFRINT R = 10. Maximum frequency interval for RESET.
NLHDIAG I = 0,1 Output additional diagnostic messages.
CONTP I=0 Continuation procedure.
Feature Description
Reset Initial Conditions
Two options are provided in the analysis to reset initial conditions:
Main Index
CHAPTER 2 21
Dynamic Analysis
1. The number of sequential non-converged solutions exceeds some maximum value defined by the user (default is
1000).
Use NHRMPRM entry to specify MNCSF=N to define the Maximum Number of non-Converged Sequential
Frequencies. N is a positive integer.
2. The frequency interval between the current excitation frequency and the previously converged solution exceeds
some maximum value defined by the user (default is 0.5 Hz).
Use NHRMPRM entry to specify MFRINT=M to define the Maximum FRequency INTerval. M is a positive real
number defining the number cycles (Hz) between the current excitation frequency and the previously converged
solution.
If both parameters are defined, the smaller interval will take precedence
Continuation Procedure
Current Harmonic Balance equation being solved
This equation has (2*NHARM+1)*NDOF unknown variables.

{u}OLD = (uR( ω 0 ), uR( ω 1 ), uI( ω 1 ), uR( ω 2 ), uI( ω 2 )…. uR( ω NHARM ), uI( ω NHARM )).
Also, [G] matrix above has size of (2*NHARM+1)*NDOF and R{u} has size (2*NHARM+1)*NDOF.
For continuation procedure, rotor speed is added as the new variable. Thus, the new state vector is given by:
{u}NEW = ((uR( ω 0 ), uR( ω 1 , uI( ω 1 , uR( ω 2 , uI( ω 2 …. uR( ω NHARM , uI( ω NHARM ), ω )
The equations are now solved using the approximate Moore-Penrose method. In this method, the tangent direction for the
solution curve is also solved iteratively. The approximate method is simplified version of the actual Moore-Penrose method
since it avoids computing a null vector needed for iteration. The iteration procedure is modified as shown in equation
below:
 u   R u { u } i
–1
u  R { u }i 
  =   – T  
ω
 i + 1  ω i  { T i }   0 
where; { T i } denotes the tangent vector for the current iteration step.
∂R ∂R
Ru { u }i = ------ -------
∂u ∂ω
The first term of the Jacobian  ∂-----R- is already determined.

∂u
Main Index
∂R { u } ∂{ F n ( { u } ) } nl
---------------- = [ G ] + ----------------------------------
-
∂{ u } ∂{ u }
∂R
The most complicated term in the Jacobian is the ------
- term which is important to determine for the usage of continuation
∂ω
process. From the definition of residual vector, its partial derivative with respect to frequency can be written as:
∂R {u, ω} ∂[ G ( ω ) ] ∂{ F n ( u ,ω ) } nl ∂{ P ( ω ) }
--------------------- = ---------------------- { u } + ---------------------------------- – -----------------------
∂ω ∂ω ∂{ u } ∂ω
∂R
For determining ------
- , two different cases are considered based on the problem type.
∂ω
Frequency Independent Analysis

For simpler problems where the nonlinear force, linear force and system matrices are independent of frequency, it is possible
∂R
to obtain a simpler analytical solution for ------
- term. In this case,
∂ω
∂G ( ω )
---------------- = ( -2n 2 ω ) [ M ] + in [ B ]
∂ω
Many problems described in literature can be solved using these expressions. The V2019.0 release only supports frequency
independent analysis with continuation procedure.
Frequency Dependent Case
The rotordynamics problems will fall under this category. For the general case, the ∂---------------------
[G(ω)]
- term can be written as:
∂ω
∂[ G ( ω ) ] ∂[ M ( ω ) ] ∂[ B ( ω ) ] ∂[ K ( ω ) ]
---------------------- = - ( nω ) 2 ---------------------- + in ω --------------------- + --------------------- + ( -2n 2 ω ) [ M ] + in [ B ]
∂ω ∂ω ∂ω ∂ω
The tangent vector is determined using following steps:
 R u ( { u } i – 1 )  0 
–1
W =  T   
 { Ti – 1 }   1 
and
W
{ T i } = --------
W
This implies that the tangent vector satisfies following linear system of equations:
R u ( { u } i )W = 0
T
{ Ti – 1 } W = 1
Thus, in Moore-Penrose correction approach, each correction occurs in plane orthogonal to the kernel of R u ( { u } i ) and the
tangent is in the same direction as the previous tangent vector. The second equation above prevents the continuation
procedure from turning back which can occur in case of constant arc-length method.
In Moore-Penrose method, the initial prediction for solution at the (K+1)th frequency step is given by:
Main Index
CHAPTER 2 23
Dynamic Analysis
u u
  =   + h { T } 0,K
 ω 1, K + 1  ω 0,K
where; { T } 0,K is the tangent vector obtained at the Kth step.
Examples
Reset Initial Condition
a. Using maximum number of frequency step failures
NHRMPRM MNCSF2 NLHDIAG 1
Input File: s128_mncsf.dat
b. Using maximum frequency interval
NHRMPRM MFRINT 0.0002 1
Reference case: s128_ori.dat
Output for Multiple Harmonics

Example: r1d128nhrm.dat
NLHARM 60, 2, 3, 20
Main Index
NLLOAD Output
Main Index
CHAPTER 2 25
Dynamic Analysis
Continuation Procedure
Example: s128_contp1.dat
Example: s128_contp2.dat
Main Index
Example Summary
All the test cases analyzed for testing are available in "../tpl/s128_v19/" folder. Here is a brief description for all the test
cases:
Output for multiple harmonics and NLLOAD r1d128nhrm
Continuation procedure for 2 DOF system S128_contp1
Continuation procedure for 1 DOF system S128_contp2
FATAL message when NHARM < SUBFAC in NLHARM entry S128_fat1
Reset of initial condition when frequency interval limit is reached S128_mfr
Reset of initial condition when frequency steps limit is reached S128_mncsf
Original test case without the reset option S128_ori
Main Index
Chapter 3: Advanced Implicit Nonlinear (SOL 400)
Advanced Implicit Nonlinear

3 (SOL 400)

Contact Model Check (2019) 28
 Output of Advanced Composite in Nastran Traditional Format of Layer Composite
33

Monitor Points with SOL 400 NLSTAT and NLTRAN 36
Main Index
Contact Model Check (2019)
Introduction
When using segment-to-segment method for contact analysis, it is necessary and help for users to review and check if
contact model is set up correctly, because in the numerical analysis, complicated structure with many parts, contact,
sometimes, is unavoidable. It becomes very challenging and tough for users to determine and review if the contact status in
the initial stage is reasonable, even with the help of GUI. Therefore, The Phase II of the contact model check project is
helpful and necessary to provide the user as more information of the contact status with Segment-to-Segment method for
contact analysis, as possible, then, user may do pre-check for the contact issues, for example, potential adjustment of the
geometry induced by initial stress free request, and so on.
In this release, the enhanced features include:
Contact Model Check:

a. Adding contact model check during analysis.
b. Enabling contact model check in segment-to-segment method.
c. Supporting all the contact types for SOL 400 and SOL 101, as well permanent glued contact for other linear
solutions: SOL 103, 105, 109, 112, and 200.
Output Geometry Adjustment of Initial Stress Free

a. Supporting all the contact types including permanent glued contact, general glued contact, as well touching
contact.
b. Improving initial stress free in segment-to-segment method by adjusting geometry same as node-to-segment
method.
c. Supporting all the contact types for SOL 400 and SOL 101, as well permanent glued contact for other linear
solutions: SOL 103, 105, 109, 112, and 200.
Add SEGANGL on BCPARA (and BCAUTOP)

a. Allow user input minimum angle between segments on BCPARA; before this release contact analysis uses 120
degree as minimum angle.
b. SEGANGL only applies to segment-to-segment method and is ignored by node-to-segment method.
c. Supporting all the contact types including permanent glued contact, general glued contact, as well touching
contact.
Add N3DSUM on NLOPRM, NLDBG

a. Simplified debug output of N3DADV with summary of the contact information of all the contact pairs.
b. Supporting all the contact types and both node-to-segment method and segment-to-segment method.
Main Index
CHAPTER 3 29
Benefits
In the numerical analysis of a complicated structure with many parts, contact, in most cases, is unavoidable. It becomes
very challenging and tough for users to determine and review if the contact status in the initial stage is reasonable, even with
the help of GUI. Therefore, it is helpful and necessary to provide the as more information of the contact status as possible,
then, user may do pre-check for the contact issues.
It is also very helpful for users to monitor the contact status during the analysis, in particular if job can't be completed.
Contact summary for debug is to help user to save much space for contact information by means of providing brief
summary.
Example
Figure 3-1 Contact Check, Distance Plot of seg-to-seg method
Main Index
Fig 2(a) Contact Check Vector without Initial Stress Free Fig 2(b) Initial Stress Free Adjustment Vector & Fringe
Vector plot shows both magnitude and direction of distance between contact pairs. Figure 2 exemplifies that the Initial
Stress Free Adjustment is capable of clearing the gap/penetration reported by Contact Check.
In this release, segment-to-segment can adjust geometry same as node-to-segment when Initial Stress Free requested.
Figure 3-2 Contact Check, Distance Vector and Contact Stress, Normal Fringe at 100% Load
Contact Check is also available during analysis (both node-to-seg and seg-to-seg), see Figure 3-2
Contact Check vectors are all in the normal direction of master surface, and the magnitude are numerical zeroes, which
means gap/penetrations can be neglected at 100% load.
Main Index
CHAPTER 3 31
Sample debug output of NLOPRM,NLDBG=N3DSUM
N3DSUM
4 segments of body 1 are touching body 2 at 4 segments
4 segments of body 2 are touching body 3 at 4 segments
N3DADV
body 1 segment 13 is touching body 2 segment 2
touching segment is defined by nodes 48 47 50 51
touched segment is defined by nodes 2 3 6 5
this generates contact polygon 1 with polygon points 1 to 9
Main Index
Guidelines and Limitations

In seg-to-seg contact, old method treats initial stress free as pre-stress in the equation, instead of adjusting geometry. Turn
on SYSTEM(758)=8 if no geometry adjustment is desired when initial stress free requested.
Main Index
CHAPTER 3 33
Output of Advanced Composite in Nastran Traditional Format of

Layer Composite
Introduction
SOL 400 supports both traditional layered composite and advanced composite elements, however, they output stresses and
strains in different formats. It may be inconvenient for users to process the composite output. This enhanced capability
provides an option for users to output stresses and strains of advanced composite elements in the format of Nastran
conventional elements, so that users may have the unique output format with both Nastran traditional/conventional
composite elements and advanced nonlinear composite elements.
Benefits
The option provides a consistent format for both traditional and advanced composite elements.
In the old format, advanced composite element stresses have two blocks in f06, one is for stresses and strains for plies and
another shows interlaminar stresses, shown as below
:
With the enhanced capability, the output of stress/strain of advanced composite element including both Solid Layer
Composite elements and Shell layer Composite elements may adapt the same format as the Nastran
traditional/conventional layer composite, as shown
Main Index
Output of Advanced Composite in Nastran Traditional Format of Layer Composite
Besides f06, Nastran HDF5 result file provides a similar format and Patran is able to show the stresses and strains on one
plot for the same plies even some elements are traditional and others are advanced elements.
User Interface
The format can be turned on by MDLPRM, COMPN1, YES, default is NO.
Example
Some examples are under tpl/advcomp in MSC Nastran Documentation Installation directory.
Here we pick up tpl/advcomp/advcomp_shlsld.dat.
In the input file, CQUAD4 from 1 to 24 are traditional layered composite elements, CQUAD4 from 25 to 28 and all
CHEXA elements are advanced composite elements, all of them have plies 401 and 402.
Run Nastran with the input file, one will have its HDF5 result file named advcomp_shlsld.h5, attach it to Patran. Below
figure shows the stresses of ply 402 for all the elements in one plot, this is impossible in the old format.
Main Index
CHAPTER 3 35
Limitations
Interlaminar shear strains are fixed to zero, and no format change in failure indices.
Main Index
Monitor Points with SOL 400 NLSTAT and NLTRAN
Introduction
The concept of monitor points was first introduced in MSC.Nastran 2001 using the MONPNT1 entry. This capability
allows users to sum forces over certain regions of aerodynamic or structural mesh about chosen points in a defined
coordinate system. Subsequent releases of MSC Nastran further expanded this integrated load feature to various monitor
responses including a MONPNT2 that selects a specific element response for output, a MONPNT3 that sums grid point
forces at a selected integration point, and a MONDSP1 that provides averaged displacement at a user specified location.
The weighted summation of existing monitor results can be computed through MONSUM, MONSUM1, and
MONSUMT entries.
This release extends current capability of monitor points from the available linear solution sequences (SOLs 101, 103, 108,
109, 111, 112, 144, 146 and 200) to SOL 400 with analysis types NLSTAT and NLTRAN. Supported monitor point
entries include MONPNT1, MONPNT3, MONSUM, MONSUM1, and MONSUMT.
Benefits
Monitor Points functionality provides a convenient tool for critical loads survey in aerodynamic analysis. It is widely used
by aerospace engineers to drive load mapping applications and to assess the performance of aircrafts.
MONPNT1 enables the extraction of the applied loading for a specified region, while MONPNT3 provides a summation
of the internal loads to facilitate computing resultant forces at a cut in the structure. The feature of scaling and combining
monitor data by MONSUM, MONSUM1 and MONSUMT offers an efficient method for loads manipulations. This
capability is useful to convert units or to obtain a response that is not directly available. Although Monitor Points were
originally designed for aeroelastic simulations, they can also be applied in any type of analysis.
The implementation of Monitor Points capability with SOL 400 NLSTAT and NLTRAN allows users to calculate
integrated loads in nonlinear analysis. This functionality provides a more general nonlinear analysis, thus fills the gap in the
ability to model monitor points and enhances MSC NASTRAN by supporting consistent linear and nonlinear capabilities.
Input
There is no change to the input required to specify the monitor points, except that a new 'C' option allowing the exclusion
of contact forces is added to the exclusion flag (XFLAG) of MONPNT3 entry.
The MONITOR Case Control command controls the printing of the monitor point results. This command must be placed
above the subcase level or in the first subcase (above the step level for SOL 400) and applies to all subcases and steps.
MONITOR commands in subcases subsequent to the first one or in any steps for SOL 400 are ignored.
Monitor Points are specified by the following two Bulk Data entries:
 MONPNT1 - External integrated loads at a user specified point.
 MONPNT3 - Sum of selected grid point forces for the user defined set of nodes and elements.
The monitor quantities can be scaled and/or combined using the following Bulk Data entries:
 MONSUM - Linear combinations of existing monitor points.
 MONSUM1 - Linear combination of existing monitor points at a user specified location.
Main Index
CHAPTER 3 37
 MONSUMT - Linear combination of existing monitor points with moment transfer.

The MSC Nastran Quick Reference Guide provides detail descriptions of the above command and entries. Users can
understand the Monitor Points capability better through reading the numerous remarks of this guide.
Output
For nonlinear static analysis with SOL 400 NLSTAT, the monitor quantities are integrated at each load step that has an
output request. For nonlinear transient analysis with SOL 400 NLTRAN, monitor responses are calculated at each user
requested output time step for each user specified component. Output formats are similar to current output formats of
monitor points. SORT1 format is used for nonlinear static analysis; while SORT2 format is applied to nonlinear transient
analysis.
Examples of MONPNT1 and MONPNT3 results for nonlinear static analysis with analysis type NLSTAT are shown
below.
MONPNT1 Results of SOL 400 NLSTAT

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)
MONITOR POINT NAME = APPLD COMPONENT = APPLD CLASS = GENERAL SUBCASE 1 STEP 10
LABEL = TEST APPLIED LOADS LOAD STEP = 1.00000E+00
CP = 0 X = 1.00000E+01 Y = 0.00000E+00 Z = 0.00000E+00 CD = 0
AXIS RIGID APPLIED

---- -------------
CX 4.000000E+05
CY 0.000000E+00
CZ 0.000000E+00
CMX 0.000000E+00
CMY 2.000000E+05
CMZ -2.000000E+05
MONPNT3 Results of SOL 400 NLSTAT

S T R U C T U R A L I N T E G R A T E D F R E E B O D Y M O N I T O R P O I N T L O A D S (MONPNT3)
MONITOR POINT NAME = G1_4 SUBCASE 10 STEP 101

LABEL = A SIMPLE TEST OF MONPNT3 LOAD STEP = 5.00000E-01
CP = 0 X = 0.00000E+00 Y = 0.00000E+00 Z = 0.00000E+00 CD = 0
AXIS REST. APPLIED

---- -------------
CX -4.159707E-01
CY -9.350353E-02
CZ 7.000781E+00
CMX 3.503802E+00
CMY -2.802110E+01
CMZ 6.924776E-02
Lists of MONPNT1 and MONPNT3 results for nonlinear transient analysis with analysis type NLTRAN are shown next
Main Index
MONPNT1 Results of SOL 400 NLTRAN (Component CX)

MONITOR POINT NAME = FORCE1 COMPONENT = CX GENERAL SUBCASE NO. 1

LABEL = FORCES AT GRID 11
CP = 0 X = 9.000000E+01 Y = 0.000000E+00 Z = 0.000000E+00 CD = 0
TIME STEP INERTIAL EXTERNAL TOTAL

------------ ------------ ------------ ------------
0.000000E+00 0.000000E+00 0.000000E+00 0.000000E+00
1.000000E-02 -2.857143E-01 1.000000E+00 7.142857E-01
2.000000E-02 5.306122E-01 1.000000E+00 1.530612E+00
3.000000E-02 -1.690962E-01 1.000000E+00 8.309038E-01
4.000000E-02 -3.856726E-01 1.000000E+00 6.143274E-01
5.000000E-02 4.996728E-01 1.000000E+00 1.499673E+00
6.000000E-02 -4.261830E-02 1.000000E+00 9.573817E-01
7.000000E-02 -4.631428E-01 1.000000E+00 5.368572E-01
8.000000E-02 4.395978E-01 1.000000E+00 1.439598E+00
9.000000E-02 8.634465E-02 1.000000E+00 1.086345E+00
1.000000E-01 -5.136075E-01 1.000000E+00 4.863925E-01
MONPNT3 Results of SOL 400 NLTRAN (Component CZ)
MONITOR POINT NAME = FORCSM2 COMPONENT = CZ SUBCASE NO. 1

LABEL = SUMMATION OF FORCES AT GRID 2
CP = 0 X = 1.000000E+01 Y = 1.000000E+00 Z = 0.000000E+00 CD = 0
TIME STEP RESULTANT
------------ ------------
0.000000E+00 0.000000E+00
2.800000E-01 0.000000E+00
5.600000E-01 3.007433E-01

1. Monitor Points with SOL 400 apply to structural meshes only.
2. The existing mini-EMA (element matrix assembly) method implemented for MONPNT3 in linear solution
sequences cannot be applied in nonlinear analysis. Instead, MONPNT3 must post-process grid point force results
to obtain point information. This limitation may impact the performance of nonlinear transient analysis because of
excessive CPU cost to process GPFORCE data.
3. Since nonlinear MONPNT3 must use grid point force methodology, accuracy of nonlinear MONPNT3 results
depends on the robustness of nonlinear GPFORCE capability for nonlinear static analysis. It also relies on the
robustness of nonlinear transient element nodal force, nonlinear transient contact force, nonlinear inertia force and
nonlinear damping force calculations.
4. Thermal loads are not considered in MONPNT1.
5. Nonlinear MONPNT3 results will not be exported to a CSV file.
6. Nonlinear MONPNT3 data may not be used on a MONSUM, MONSUM1 or MONSUMT entry.
7. For external superelements, Monitor Points results cannot be retrieved at the assembly run (second step). The third
step must be run to get the Monitor Points results.
8. The monitor point data from nonlinear transient analysis can be voluminous since the results are printed for each
component at each user specified output time step.
Main Index
CHAPTER 3 39
Examples (/tpl/mpt400/mon400_1.dat)
Test cases of Monitor Points capability with SOL 400 NLSTAT and NLTRAN are available in the directory /tpl/mpt400.
These tpl files demonstrate the usages of supported monitor types with various combinations.
Example problem mon400_1.dat demonstrates the specification of MONPNT1 and MONPNT3 in nonlinear static
analysis. This is a latch model with touching rigid to shell contact shown in Figure 3-3.
Figure 3-3 TPL example mon400_1.dat
The MONITOR Case Control Command is defined to request monitor point results. Note that a GPFORCE command
is also specified to compare MONPNT3 results and grid point forces output. A partial list of Executive Control statements
and Case Control commands is shown as follows:
SOL 400
CEND
ECHO = NONE
set 3=381
MONITOR=ALL
SUBCASE 1
STEP 1
SUBTITLE = Default
SPC = 9
LOAD = 10
BCONTACT = 1
ANALYSIS = NLSTAT
NLSTEP = 2
GPFORCE(PRINT,PLOT) =3
In this example, two MONPNT1 entries are created to specify integration load points, one on structure and the other on
a rigid surface. These integrations occur over the grids associated with the SET1 entries referenced on the AECOMP entries
MONPNT1 FLoads Loads on structure
123456 CEN 1 0. 0. 0. 1
AECOMP CEN SET1 4
SET1 4 711 712 713 714 715 716 717
718 719 720
MONPNT1 RLoads Loads on Rigid

123456 CENR 1 0. 0. 0. 1
Main Index
AECOMP CENR SET1 5

SET1 5 10001
This model also contains six MONPNT3 entries that sum grid point forces over a set of nodes and elements defined on
the GRIDSET and ELEMSET fields of MONPNT3.
MONPNT3 BEND1 Bottom bend force
123456 50 70 1 0. 0. 0. SMADC
SET1,50,344,357,358,359,360,361,362,333
SET1,70,211,217,216,215,214,213,212,204,205,206,207,208,209,210
MONPNT3 BEND2 Top bend force

123456 52 72 1 0. 0. 0. SMADC
SET1,52,945 ,986 ,995 ,996 ,997 ,998 ,999 ,1000,987 ,958
SET1,72,685,710,709,708,707,706,705,704,688,686,697,698,699,700,701,
702,703,687
MONPNT3 BEND2B Top bend force at one grid
123456 53 73 1 0. 0. 0. SMADC
SET1,53,945
SET1,73,685,686
MONPNT3 CONTC Botom contact edge excluding SMAD

123456 54 74 1 0. 0. 0. SMAD
MONPNT3 CONTNC Botom contact edge excluding contact

123456 54 74 1 0. 0. 0. SMADC
MONPNT3 CONTB Botom contact edge excluding blank

123456 54 74 1 0. 0. 0.
SET1,54,381
SET1,74,230,289 PSHELL 1 1 0.4 1 1
The MONPNT1 results at the last load increment (load step = 1.0) are shown in the following table:
MONITOR POINT NAME = FLOADS COMPONENT = CEN CLASS = GENERAL SUBCASE 1 STEP 1
LABEL = LOADS ON STRUCTURE LOAD STEP = 1.00000E+00
CP = 1 X = 0.00000E+00 Y = 0.00000E+00 Z = 0.00000E+00 CD = 1
AXIS RIGID APPLIED

---- -------------
CX -1.000000E+01
CY 0.000000E+00
CZ 0.000000E+00
CMX 0.000000E+00
CMY -5.500010E+00
CMZ 6.017217E+01
MONITOR POINT NAME = RLOADS COMPONENT = CENR CLASS = GENERAL SUBCASE 1 STEP 1
LABEL = LOADS ON RIGID LOAD STEP = 1.00000E+00
CP = 1 X = 0.00000E+00 Y = 0.00000E+00 Z = 0.00000E+00 CD = 1
AXIS RIGID APPLIED

---- -------------
CX -1.000000E+00
CY 0.000000E+00
CZ 0.000000E+00
CMX 0.000000E+00
CMY -3.450000E+00
CMZ 3.729800E+00
Main Index
CHAPTER 3 41
To demonstrate the effect of excluding contact forces on MONPNT3, the grid points forces output for grid ID = 381 is
listed first in the following table.
SUBCASE 1 STEP 1
LOAD STEP = 1.00000E+00
G R I D P O I N T F O R C E B A L A N C E
POINT-ID ELEMENT-ID SOURCE T1 T2 T3 R1 R2 R3

381 F-OF-CNT -3.287752E-01 6.018190E-01 0.0 0.0 0.0 0.0
381 230 QUAD4 2.677896E-01 -5.799091E-01 -5.000710E-02 1.348574E-04 7.995402E-05 9.605388E-03
381 289 QUAD4 6.099666E-02 -2.190803E-02 5.000904E-02 -1.348493E-04 -7.987675E-05 -9.605460E-03
381 *TOTALS* 1.100395E-05 1.880501E-06 1.946208E-06 8.098842E-09 7.727520E-08 -7.200248E-08
A set of MONPNT3 results for the bottom contact edge with or without contact force exclusion (XFLAG = blank, SMAD
or SMADC) is shown as in the following table.
MONITOR POINT NAME = CONTB SUBCASE 1 STEP 1

LABEL = BOTOM CONTACT EDGE EXCLUDING BLANK LOAD STEP = 1.00000E+00
CP = 1 X = 0.00000E+00 Y = 0.00000E+00 Z = 0.00000E+00 CD = 1
AXIS REST. APPLIED

---- -------------
CX 1.100395E-05
CY 1.880501E-06
CZ 1.946208E-06
CMX 2.875793E-06
CMY -1.413075E-05
CMZ -2.557746E-06
MONITOR POINT NAME = CONTC SUBCASE 1 STEP 1

LABEL = BOTOM CONTACT EDGE EXCLUDING SMAD LOAD STEP = 1.00000E+00
CP = 1 X = 0.00000E+00 Y = 0.00000E+00 Z = 0.00000E+00 CD = 1
AXIS REST. APPLIED

---- -------------
CX 1.100395E-05
CY 1.880501E-06
CZ 1.946208E-06
CMX 2.875793E-06
CMY -1.413075E-05
CMZ -2.557746E-06
MONITOR POINT NAME = CONTNC SUBCASE 1 STEP 1

LABEL = BOTOM CONTACT EDGE EXCLUDING CONTACT LOAD STEP = 1.00000E+00
CP = 1 X = 0.00000E+00 Y = 0.00000E+00 Z = 0.00000E+00 CD = 1
AXIS REST. APPLIED

---- -------------
CX 3.287862E-01
CY -6.018171E-01
CZ 1.946208E-06
CMX -8.274982E-01
CMY -4.520800E-01
CMZ 2.375924E-01
Since contact force is the only force type applied to node 381, it is seen that only adding the C option in the XFALG of
MONPNT3 can obtain different results of MONPNT3.
Main Index
Chapter 4: Advanced Nonlinear Explicit (SOL 700)
Advanced Nonlinear Explicit

4 (SOL 700)

Articulated Total Body (ATB) 43

Viscoelastic Material - MATVE 45
 Initial Metric Method (IMM) 45

Air bag fabric material model (MATFAB) 46

SCA User Defined Services (UDS) 47
 Localized cohesive friction 50

DMP for the auto coupling approach 52

Simulating flow through failed shells with the auto coupling approach 53
Main Index
CHAPTER 4 43
Advanced Nonlinear Explicit (SOL 700)
Articulated Total Body (ATB)

In order to perform analyses of occupant interaction with structures, the occupant modeling program ATB (Version 5.3.1)
is included in Nastran SOL 700 (References 1.,2., 3., and 4.). This is not just a procedure for running one program,
transferring results, and then running the other program. Nastran SOL700 and ATB run concurrently, exchanging data as
the analysis proceeds. ATB is built as standard in Nastran and is activated only when required.
ATB Input Specification

The input specification for ATB (Reference 3.) does not change. The ATB-input file name (with standard extension .ain or
extension .lin) must be specified by the user. This is done on the command line of the Nastran SOL700 script by using one
of the keywords (atb =, ain = or lin =) followed by the ATB-input filename (without an extension). Both methods command
Nastran SOL700 to activate ATB.
Some useful options have been added to the ATB input file:
 If a nonzero value is set in the NSJF field (I4) right after the I3 field on entry G.1.a, initial joint forces are
subtracted from internal forces. Thus, it is possible to create an initial equilibrium after positioning the dummy.
Care should be taken when using this option.
 Nastran SOL700 can control the timesteps of output generated by ATB. This achieved by changing flags on the
ATB output generation card (Card A5) in the ATB input file:
• Field 3: Frequency of output written to main ATB print-file. If the value is set to -1, the output is controlled
by the Nastran SOL700 parameter DYPARAM,ATBAOUT,xxx. The default for this parameter is 10
milliseconds.
• Field 26: Frequency of output written to time-history files (H-cards and LU-numbers). If the value is set to -
1, the output is controlled by the Nastran SOL700 parameter DYPARAM,ATBTOUT,xxx. The default for
this parameter is 1 millisecond.
 If extra output files of ATB are requested, the starting LU number of the ASCII time history files has been
increased from 21 (which is the ATB standard) to 41 in order to avoid mixing with output files of Nastran
SOL700.
Despite above-mentioned additions, any original ATB-input file is still valid.
Moreover, positioning of the dummy can be handled by Nastran SOL700. For a description, see the Bulk Data entries
ATBJNT, ATBSEG, and the DYPARAM entry ATBSEGCREATE.
Nastran SOL700 Input Specification

Each segment contact ellipsoid used in the occupant model must be defined in the Nastran SOL700 input file with the
RELEX entry. The names of these ellipsoids must be the same as the segment names as defined in the ATB-input file on
the B.2 entry. The use of the RELEX entry is described in the Bulk Data section.
Only the RELEX entry should be used.
The interaction between the ATB ellipsoids and the structural parts of the Nastran SOL700 model is achieved through
METHOD=RELLIPS in BCTABLE or BCONPRG. This interaction applies to all structural elements: quadrilateral and
triangular shells, membrane elements, Lagrangian solids, and rigid bodies.
Main Index
Articulated Total Body (ATB)
Termination Conditions
All termination conditions selected in Nastran SOL700 remain valid. If a termination condition occurs, ATB is forced into
an end cycle, and Nastran SOL700 terminates as usual.
ATB-termination conditions cannot be used to stop the analysis.
Example
A detailed example of a model using ATB is available in the Airbags and Occupant Safety (Ch. 10) of MSC Nastran SOL 700
User’s guide. Other examples are in:
 tpl/dfsi700_1/tratbn0
 tpl/dfsi700_1/vem6_3hii
 tpl/dfsi700_1/tabtn008
 tpl/dfsi700_1/velcon002
References
1. Louise A. Obergefell, Thomas R. Gardner, Ints Kaleps, and John T. Fleck, Articulated Total Body Model
Enhancements, Volume 1: "Modifications", (NTIS No. ADA198726).
2. J. T. Fleck, F. E. Butler, and N. J. Deleys, "Validation of the Crash Victim Simulator", Calspan Report Nos. ZS-
5881-V-1 through 4, DOT-HS-806-279 through 282, 1982, Volumes 1 through 4, (NTIS No. PC E99, PB86-
212420).
3. Joseph A. Pellettiere, Huaing Cheng, Annnette L. Rizer, The Development of GEBOD Version V, 2000.
4. S.Tanimura, K.Mimura, and W.H. Zhu, Practical Constitutive Models Covering Wide Ranges of Strain Rates,
Strains and Temperatures, Key Engineering Materials Vols. 177-180,189-200, 2000
Main Index
CHAPTER 4 45
Viscoelastic Material - MATVE

Viscoelastic material is introduced to Nastran SOL 700 that can be used for Lagrangian (structural) solid elements. It is
mostly used for modeling of rubber. Generally, tire companies are using the model to simulate hydroplaning or other events.
The material model defines an isotropic linear viscoelastic shear model where the mechanical analog is a spring, a dashpot,
and a Maxwell element connected in parallel.
Example
 tpl/dfsi700_1/tmatft101
Initial Metric Method (IMM)

The Initial Metric Method is typically useful for air bag modeling. When using out-of-plane folding technique, the
membrane elements can deform quite significantly. The final shape of the deformed bag can be negatively influenced. In
order to overcome this problem, Nastran SOL700 offers a way to initialize strains inside elements such that the final shape
is preserved. It is called the Initial Metric Method, further called the IMM method. Elements can be initialized smaller than
the original state, but also can be initialized larger.
 For elements that are initialized smaller, stresses only start to build up after the original state has been reached.
 Elements that are larger have a positive IMM strain. When growing larger, their Young's modulus is assumed to be
twice as large during one time step. When shrinking, no stresses are applied until the original state is reached.
IMM can also be applied when scaling the model of the air bag such that the model fits inside the inflator housing.
IMM Methods
Three formulations are available. Using the parameter IMM, they are:
 “FULL: While elements are under IMM condition, they carry stresses when under compression. This is the
default.
Main Index
Air bag fabric material model (MATFAB)
 “REDUCED: While elements are under IMM condition, the carry a reduced stress when under compression. The
relative area factor, SMDFER, is used to reduce Young's modulus.
 “ZERO: While elements are under IMM condition, compressive stresses are not carried. They code relies on the
material damping to avoid excessive nodal velocities. It has been shown that IMM formulation ZERO is most
suitable when more that a couple of membrane elements with zero area exist in the initial state of the air bag
model.
It should be noted that when elements are not under the IMM condition anymore (IMM strain tensor components are all
zero), the elements start to behave like a regular membrane elements according to the material model attached.
Usage
The IMM needs two models of the same air bag. One model is called Initial state and the second is called Original or
Reference state.
 The Initial state model has to be part of the main input file. This state can be visualized in output requests.
 The Original state model has to be supplied in a different file. Nastran reads this file and uses the data to initialize
IMM strains on the elements of the Initial state model.
The following line activates the Initial Metric Method:
nastran <nastran_input_file> imm700=<original_input_file>
The Initial Metric Method is also activated when the IMMFILE = (filename) directive is present in the File Management
section.
The Initial Metric Method can be used in combination with ATB and can be used in any contact type. IMM is only used
for triangular membrane elements. The IMM-strains can be visualized in an archive file or time-history file. The variables
are EXXIMM, EYYIMM and EXYIMM. A value of zero denotes that during the run, the original state was reached and
IMM for that particular element is not active anymore.
Example
 tpl/dfsi700_1/vimm1
Air bag fabric material model (MATFAB)

This material model is intended for simulating woven materials as used in airbags. This model can only be referred to by
triangular shell with one Gauss point when used in airbags. For other applications, it may be referred to by elements with
membrane behavior (triangular quadrilateral shell with one Gauss point). Additionally, it can be referred to by the layered
composite element property PBCOMP The model is based on a finite strain formulation and tracks the orientation of the
fabric tows in both warp and weft direction (that is, warp ends and weft picks) as large shear strains occur.
A detailed description of the material is given in the SOL 700 User Guide. It also includes a section how to determine the
various material parameters
Main Index
CHAPTER 4 47
Example
 tpl/dfsi700_1/vfabc4.dat
SCA User Defined Services (UDS)

In this version of Nastran, a number of UDS services have been reintroduced and a couple of new ones have been created.
Below follows a short description of each one. Detailed information is available in the User Defined Services User's Guide.
Subroutine name Description

EOSUDS Calculates the equation of state for Lagrangian and Eulerian solid elements
FAILUDS User defined failure of Lagrangian and Eulerian materials.
FLOWUDS Returns the velocity, pressure, density, and specific internal energy at a
single material Eulerian user defined flow boundary.
TABLUDS User defined table
TICEUDS Defines an initial condition for Eulerian elements and/or grid points at the
beginning of the analysis
PORUDS The user subroutine defines a general porosity model for coupling surfaces
SHRUDS The user subroutine defines the shear modulus, for Lagrangian and
Eulerian elements with shear strength
YLDUDS The user subroutine defines the yield stress for Lagrangian and Eulerian
elements with shear strength
FORCUDS The user subroutine defines the nodal velocities for Lagrangian elements
COMPUDS The user subroutine defines the orthotropic failure criteria including
degradation for Lagrangian shell elements
Examples
EOSUDS
 tpl/s700uds/matexeosn
 tpl/s700uds/t11n11020n_c
 tpl/s700uds/t11n11020n
 tpl/s700uds/usreosexn
 tpl/s700uds/usrn001n_c
 tpl/s700uds/usrn001n
Main Index
SCA User Defined Services (UDS)
FAILUDS
 tpl/s700uds/comt002n_c
 tpl/s700uds/comt002n
FLOWUDS
 tpl/s700uds/badn002n
 tpl/s700uds/bndexfl3tn_c
 tpl/s700uds/bndexfl3tn
 tpl/s700uds/bndexfl3wqn_c
 tpl/s700uds/bndexfl3wqn
 tpl/s700uds/bndexfl3wrn_c
 tpl/s700uds/bndexfl3wrn
 tpl/s700uds/bndexfldn
 tpl/s700uds/bndexflqn
 tpl/s700uds/bndtnkfn_c
 tpl/s700uds/bndtnkfn
 tpl/s700uds/roemaexfn_c
 tpl/s700uds/roemaexfn
 tpl/s700uds/t11n11015mdn_c
 tpl/s700uds/t11n11015mdn
 tpl/s700uds/visposngn_c
 tpl/s700uds/visposngn
 tpl/s700uds/visposnmdn_c
 tpl/s700uds/visposnmdn
 tpl/s700uds/visposnn_c
 tpl/s700uds/visposnn
Main Index
CHAPTER 4 49
 tpl/s700uds/visposnt11mdn_c
 tpl/s700uds/visposnt11mdn
 tpl/s700uds/visposnt11mdn.dat:flowuds,400,myflow,,,1,posy
 tpl/s700uds/visposnt11n_c
 tpl/s700uds/visposnt11n
 tpl/s700uds/visposnt9gn_c
 tpl/s700uds/visposnt9gn
 tpl/s700uds/visposnt9mdn_c
 tpl/s700uds/visposnt9mdn
 tpl/s700uds/visposnt9n_c
 tpl/s700uds/visposnt9n
TABUDS
TICEUDS
 tpl/s700uds/sloexintn_c
 tpl/s700uds/sloexintn
PORUDS
 tpl/s700uds/porn012n_c
 tpl/s700uds/t11n11016mdn_c
 tpl/s700uds/porn012n
 tpl/s700uds/t11n11016mdn
SHRUDS
Main Index
Localized cohesive friction
YLDUDS
FORCUDS
COMPUDS
 tpl/s700uds/usrexcp1
 tpl/s700uds/usrexcp1_c
Localized cohesive friction

In hydroplaning soil can stick to the wheel. This sticking can already be simulating by using DYPARAM, COHESION,
but this PARAM applies to the whole wheel. In practice it can happen that mud sticks to only part of the wheel, while it
slides off other parts. To simulate this, local cohesive friction has been added. It can be activated by using the new entries
COUCOHF and COHFRIC.
The two figures below show an example model. Two wedges (black) are being pulled out of soil (red). The blue represent
air. Here air and soil are modeled by a Euler mesh of 320x1x80 elements. For this model, getting a smooth interface between
air and soil requires a fine Euler mesh.
Main Index
CHAPTER 4 51
Main Index
DMP for the auto coupling approach
Examples
 tpl/dfsi700_2/wedge1.dat
DMP for the auto coupling approach

For simulating fluid-structure interaction Sol 700 provides the fast coupling approach. It is activated by DYPARAM,
FASTCOUP. It requires that the surface defining the interaction is a closed surface. The user has to close the surface by
creating dummy surfaces and this can make the method less user friendly. To provide a user friendly approach, the auto
coupling approach had been introduced in Nastran 2018. It supports interaction surfaces with holes or T-joints and is
activated by DYPARAM, AUTOCOUP. In this release DMP has been enabled for this approach.
CPU timings with dmp are shown for a simple test model. The model consists of a plate with hole. On the left side of the
plate there is high pressure. On the other side there is low pressure. This gives the velocity field shown in the fringe plot
below.
Running the model on 1, 2 and 4 CPUs gives:
Number of CPUs Time Speed-up

1 273 1.0
2 176 1.56
4 135 2.0
Main Index
CHAPTER 4 53
The model uses 136161 Euler element.
Examples
 tpl/dfsi700_2/acsdmp1.dat
Simulating flow through failed shells with the auto coupling

approach
Support of auto coupling to enable flow through failed segments has been added. It is activated by setting the option FAIL
on the DYPARAM, AUTOCOUP entry. An example of a bird strike is shown below.
In the picture below a cylinder models the bird and impacts a shell shown in black. This causes failure of the shell and the
bird flows through the failed segments. Only one Euler domain is needed to model the bird. Without the auto coupling
approach two Euler domains would be needed. Therefore, auto coupling offers a more user friendly simulation method.
Examples
 tpl/dfsi700_2/autocpintf1.dat
Main Index
Chapter 5: Numerical Methods and High Performance Computing
Numerical Methods and

5 High Performance
Computing

New Features of SOLVE=AUTO in MSC Nastran 2019.0 55
 New FASTFR with SMP parallelization 57

Improved Parallel Performance for Acoustic Coupling Matrix Reduction Using ACMS
60

Improved Performance for the RANDOM Module 61
 New DMP Implementation of Modal Participation Factor Calculations 62

Change to Default Parallel Scheduling for ACMS 63

Improved performance for large Adams mnf file generation 66
Main Index
CHAPTER 5 55
New Features of SOLVE=AUTO in MSC Nastran 2019.0
Enhancements to SOL 200

Introduction
As design sensitivity and optimization analysis are computationally intensive due to the nature of several design cycle
iterations with multi-disciplinary analysis, it is critical that we select the best solvers, their parallel implementations and
combinations for multitude of analyses. Starting from MSC Nastran 2019, the command line option "solve=auto" has
improved design to automatically select the best modal solver, direct solver, specific parallel implementations and optimal
DMP and SMP options based on the model characteristics, the analyses performed and the availability of resources.
Benefits
The benefits of "solve=auto" is to achieve the best performance and efficient utilization of resources right out of the box.
This provides the capability to automatically choose the optimal combinations and thus eliminating the need for the user
to understand the complexity of the solvers and their parallel implementations/ options.
Test Cases
There is no new or modified input required for this enhancement. The example jobs presented below are customer models
and are executed with the command line option "solve=auto".
Selected DMP Selected DMP Elapsed time in Elapsed time in

Solvers and SMP in and SMP in MSC Nastran MSC Nastran
Case Analysis chosen 2018.2 2019.0 2018.2 2019.0
MODEL A Modal Distributed 4 DMP and 5 2 DMP and 8 353 182
frequency MSCLDL SMP SMP
response and
Accelerated
ACMS
MODEL B Direct Distributed 4 DMP and 5 2269 1104
frequency MSCLDL SMP
response and Lanczos
Enhancements to SOL 111

Introduction
 SOLVE=AUTO with SOL 111 will now select SMP if sufficient memory is available and NewACMS is selected.
 SOLVE=AUTO with SOL 111 will reduce the default of DMP=4 for large models to DMP=2 if insufficient
memory is available and NewACMS is selected.
Main Index
New Features of SOLVE=AUTO in MSC Nastran 2019.0
Table 5-1 Comparison 2018.2 and 2019

2018.2 2019
Elapsed 2132 1816
DMP 4 2
SMP 4 5
SOLVE=AUTO in 2018.2 sets DMP=4/SMP=4.

SOLVE=AUTO in 2019.0 determined there was insufficient memory for DMP=2/SMP=5.
The RHEL 7.1 system had 20 cores and 256Gb of RAM resulting in a 15% speed up.
Table 5-2 Comparison 2018.2 and 2019

2018.2 2019
Elapsed 9554 8005
DMP 4 2
SMP 2 8
SOLVE=AUTO in 2018.2 sets DMP=4/SMP=2.

SOLVE=AUTO in 2019.0 determined there was insufficient memory for DMP=4.
DMP was reduced to DMP=2, and the processors were given to SMP (SMP=8).
The Win10 system had 16 cores and 128GB of RAM resulting in a 15% speed up.
Main Index
CHAPTER 5 57
New FASTFR with SMP parallelization
Introduction
The frequency response calculation based on the Sherman-Woodbury-Morrison formula is often required for the
simulations in the automotive and aerospace industries. It is a computationally intensive process and requires significant
time and computing power. With the advances in electric car manufacturing and quiet engines, the frequency range that
has to be covered is steadily increasing, which makes this type of calculation exponentially more expensive. In this release
we have added a new FASTFR module that will perform this operation using SMP-parallel kernels. The new module is
aimed at improving performance of SOL 111 models, which require frequency response analysis over a large range of
frequencies or with a large number of load cases.
Benefits
The new module provides significant performance improvement for the models with large number of frequencies, modes
and load cases. The best performance is achieved by using the maximum number of SMP threads and maximum amount
of memory. In case of limited memory, the calculations are done in several passes over the frequency domain. Compared to
the previous MSC Nastran Release 2018.0, the new release should give a speedup anywhere from a factor of 2 to 10 when
we compare different benchmark models.
Technical Discussion
The previous versions of MSC Nastran used to process the frequency response for one frequency at a time by calling SLITX
module and storing multiple temporary matrices on disc in the process. Once the computations are completed, the entire
frequency response matrix had to be re-arranged. The new module reads in all the input matrices and processes all the
frequencies and load cases at once without doing any additional I/O operations. The resulting frequency response matrix
is automatically filled out in the correct order.
In contrast to the previous releases that used DMP parallelization for splitting the frequency domain equally between the
nodes and used SMP parallelization for bottom-level computations, the new module relies solely on the SMP
parallelization. In case of running the new 2019.0 release of Nastran with DMP and SMP using the Master-Slave scenario,
all computations in FASTFR will be performed only on Master process using SMP over the maximum allowed number of
cores/threads.
The new FASTFR module only supports the frequency response analysis for non-frequency dependent materials. For the
frequency-dependent models, best performance is achieved by using a combination of DMP and SMP parallelization.
Main Index
New FASTFR with SMP parallelization
Figure 5-1 Examples of performance improvement in total elapsed time due to new FASTFR
In the Figure 5-1, the red bar is the total elapsed time for the runs with 2018.1 release, normalized to 1. The black bars
represent the total elapsed time for the same models run with the new 2019.0 release including the new FASTFR. The basic
details about the test runs are as follows:
Model A: SOL 111, structure+ fluid, DOF=10 M, number of frequencies: 200, number of loads: 17, mem=128 GB
Model B: SOL 111 structure only, DOF=8 M, number of frequencies: 301, number of loads: 180, mem=128 GB
Main Index
CHAPTER 5 59
Figure 5-2 Examples of performance improvement in total elapsed time for frequency response due to new FASTFR
In Figure 5-2, the red bar is the elapsed time for frequency response for the runs with 2018.1 release, normalized to 1. The
black bars represent the elapsed time within the new FASTFR module for the same models run with the new 2019.0 release
for the same models as in Figure 5-1.
Main Index
Improved Parallel Performance for Acoustic Coupling Matrix Reduction Using ACMS
Improved Parallel Performance for Acoustic Coupling Matrix

Reduction Using ACMS
Introduction
Automated Component Modal Synthesis (ACMS) is an important capability in linear dynamic analysis. Use of ACMS is
the de facto standard method of computing a modal subspace for the analysis of noise and vibration of large models. ACMS
is often used for vibro-acoustic analysis.
Current trends in the automotive industry are driving requirements for acoustic analysis to increasingly higher frequencies.
When coupling structure and fluid models, the cost of reducing the coupling matrix to modal coordinates increases rapidly
with the number of fluid modes. MSC Nastran 2019.0 features improved performance for this operation.
Benefits
A Nastran acoustic analysis featuring a mid- to high-frequency acoustic range in conjunction with ACMS in Version 2019.0
will complete in a shorter time compared to previous Nastran versions. Job throughput will improve on all customer
computer platforms. This leads to greater overall productivity.
The acoustic coupling matrix [A] is reduced to modal coordinates by forming a triple product using structure and fluid
modes. Specifically,
[ φs ]T [ A ] [ φf ] = modal (generalized) fluid – structure coupling matrix
where [A] is known as the Area Matrix in MSC Nastran.
Inputs
There is no new or modified user input associated with this enhancement.
Outputs
There is no new or modified output associated with this enhancement.
Test Cases
Improved performance reducing the acoustic coupling matrix is shown in a Test Case below.
Main Index
CHAPTER 5 61
Improved Performance for the RANDOM Module
Introduction
Random response analysis is an important analysis function, performing power spectral density and auto-correlation
quantities following a frequency response analysis. For a significant amount of data in the analysis, these calculations can
be very time consuming. A significant performance improvement is realized in MSC Nastran 2019.0 for these calculations.
Benefits
Random response analysis in Version 2019.0 will complete in a shorter time compared to previous Nastran versions. Job
throughput will improve on all customer computer platforms. This leads to greater overall productivity.
In MSC Nastran, random response analysis is implemented as a data reduction procedure that is applied to the results of a
frequency response analysis. Normal data reduction procedures are applied to the response results, resulting in sets of output
quantities. Power spectral density and auto-correlation function calculations are then performed in the RANDOM module.
The solution techniques used in the RANDOM module have been updated to modern computing methods for Version
2019. The result is a significant performance improvement for all known use cases.
Inputs
There is no new or modified user input associated with this enhancement.
Outputs
There is no new or modified output associated with this enhancement.
Test Cases
An improvement in RANDOM module performance is shown in a Test Case below.
Main Index
New DMP Implementation of Modal Participation Factor Calculations
New DMP Implementation of Modal Participation Factor

Calculations
Introduction
The computation of modal participation factors can be very time consuming. The time required for these calculations is
due to the large amount of data that is considered: the number of forcing frequencies, and the number of structure and
fluid modes. For any nontrivial frequency range, the time required for participation factor calculation can easily dwarf the
time required for all other tasks in the analysis.
Benefits
The time required for participation factor computations may be reduced by using Distributed Memory Parallel (DMP)
processing in Version 2019.0. The use of DMP will bring the calculation cost more in line with related compute costs in
the analysis.
In MSC Nastran, participation factors are calculated in the PFCALC module. The PFCALC module executes a nested loop:
the outermost loop is over user-defined subcases. For each subcase, the solution loops over each excitation frequency. There
is a third loop over any user-defined panels, executed for each frequency. For Version 2019, DMP parallelization is
implemented over the excitation frequency loop. This is in keeping with frequency domain parallelism used in other MSC
Nastran solution strategies.
Inputs
There is no new or modified user input associated with this enhancement. Case Control commands PFMODE, PFPANEL,
and PFGRID are used to request modal, panel, and grid participation factors. An MSC Nastran V2019 job using DMP
will cause the panel participation calculations to execute in parallel. The parallel speedup is roughly linear, up to at least
DMP=4.
Note that participation factors assocated with PEAKOUT Case Control requests are still computed in serial for this version
of MSC Nastran.
Outputs
There is no new or modified outputs associated with this enhancement.
Test Cases
A demonstration of DMP participation factor calculations is presented in a Test Case below.
Main Index
CHAPTER 5 63
Change to Default Parallel Scheduling for ACMS

Automated Component Modal Synthesis (ACMS) with VERSION=NEW was introduced in MSC Nastran Version
2016.0. It employs Shared Memory Parallelism (SMP) to achieve maximum parallel speedup. The original implementation
of ACMS VERSION=NEW was limited to a static allocation of work to SMP threads. A dynamic parallel scheduling
algorithm was introduced in MSC Nastran 2018.0.
For MSC Nastran Version 2019.0, the default parallel scheduling is changed from STATIC to DYNAMIC. For most cases
using a significant number of parallel threads, DYNAMIC offers greater speedup compared to STATIC. For some cases,
the memory requirement for DYNAMIC scheduling may be slightly higher (about 10%).
The ACMS parallel scheduling algorithm may be selected with the SCHED keyword on the DOMAINSOLVER Executive
System command:
DOMAINSOLVER ACMS ( SCHED={DYNAMIC|STATIC} )
Main Index
Test Case
Test Case
The example presented here is from a customer model. Model and analysis characteristics are described in generic terms.
Performance results comparing Version 2019.0 with Version 2018.2 are shown. Parallel scalability is shown where
applicable.
The test case below was executed using 16 cores (dmp=4 smp=4) and 200 GB memory (memorymax=200 GB).
Machine Characteristics:
OS: Red Hat Enterprise Linux Server release 7.1 (Maipo)
Model: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz
Nsocket: 2
Ncore: 20 ( 2 X 10 )
Cache: 25600 KB
RAM: 256 GB
TEST CASE: Automotive Modal Frequency Response Analysis
Number of DOF 10.4 million
Number of grid points 1.7 million
Number of 2D elements 1.2 million
Number of 3D elements 0.6 million
Number of structure modes 2300
Number of fluid modes 640
Number of load cases 275
Number of forcing frequencies 230
Main Index
CHAPTER 5 65
In the example shown, the speedup for the participation factor calculations (PFCALC) is 3.55. The RANDOM module
improvement is more than 12X. The improvement for the MDHREDX module (acoustic coupling matrix reduction) is
57%. The overall job speedup is 2.5X.
Main Index
Improved performance for large Adams mnf file generation
Improved performance for large Adams mnf file generation

The generation of modal neutral files (.mnf ) for Adams flexible bodies using the case control command ADAMSMNF may
be time consuming for large model with lots of eigenmodes. Changes have been made to improve the usage of core memory,
reduce the I/O during the generation of the .mnf and improve the mass invariant calculation. These changes result in
significant elapsed time reduction for many model. For the model in the example shown below, the speed-up of the
ADMFLEX module, which generates the .mnf file, is more than 5x.
Example: Heavy truck frame with 2.8 M Grids and 272 extracted modes
Figure 5-3 Example of performance improvement in total elapsed time for MNF generation due to improved ADMFLEX
Main Index
CHAPTER 5 67
Main Index
Chapter 6: Pyramid Elements
6 Pyramid Elements
 Introduction 69

Benefits 69

Feature Description 69
 User Interface 70

Examples 73

Guidelines and Limitations 80
Main Index
CHAPTER 6 69
Pyramid Elements
Introduction
Pyramid elements have been added to MSC Nastran. This adds one more topology to the existing standard tetrahedral,
penta (wedge) and hexahedral solid element topologies. The pyramid element is completely supported in all physics and
applications where the other regular solid elements are supported in MSC Nastran.
Benefits
Automated meshers commonly produce mixed meshes - with Hexahedral elements in the core of the geometry, Tetrahedral
elements at the boundaries of the geometry and Pyramid elements acting as transitional elements between the Hexahedral
and Tetrahedral topologies.
MSC Nastran can now directly work on these meshes, thereby increasing the ease of use in various applications such as
cavity acoustics, optimization etc.
Feature Description
The pyramid element enhancement to MSC Nastran supports the following features:
1. All linear solution sequences. This includes SOL 101, SOL 103, SOL 105, SOL 107, SOL 108, SOL 109, SOL
110, SOL 111, SOL 112, SOL 144, SOL 145 and SOL 146. SOL 200 and SOL 400 also support the pyramid
element.
2. All physics already supported by MSC Nastran standard solid elements are also supported for the pyramid element.
This includes:
a. Linear statics
b. Linear dynamics (modal, frequency and transient)
c. Buckling analysis
d. Design Sensitivity and Optimization
e. Fatigue analysis except vibration fatigue
f. Rotor dynamics
g. Acoustics
h. Contact including automated contact generation
i. Material and geometric nonlinearity
j. Linear perturbation analysis
k. Random analysis
l. Coupled analysis
m. Heat transfer
n. Thermo-mechanical coupled analysis
o. Aeroelasticity and flutter
3. All types of loading such as structural point or distributed loads, gravity loads, pressure loads, thermal loads, etc. are
supported for the pyramid element.
Main Index
70 CPYRAM
User Interface
4. Standard features of MSC Nastran such as Super elements, restarts, modules, GEOMCHECK are supported for
the pyramid element.
5. Output in the format of HDF5 is supported for the pyramid element result quantities.
6. The pyramid element is also supported in the ADAMSMNF Tool Kit.
User Interface
A new connection entry is added in the bulk data entry for defining pyramid elements:
CPYRAM Five-Sided Solid Element Connection
Format:
1 2 3 4 5 6 7 8 9 10
CPYRAM EID PID G1 G2 G3 G4 G5 G6
G7 G8 G9 G10 G11 G12 G13
Example:
CPYRAM 7 4 15 16 17 18 40 21
22 23 24 31 32 33 34
Describer Meaning Type Default

EID Element identification number. 0 < Integer < 100,000,000 Required
PID Property identification number of a PSOLID Integer > 0 Required
entry.
Gi Identification numbers of connected grid Integer > 0 or blank Required; G6-G13 are
points. optional
Main Index
CHAPTER 6 71
Pyramid Elements
Figure 6-1 CPYRAM Element Connection
Remarks:
1. Element ID numbers must be unique with respect to all other element ID numbers.
2. The topology of the diagram must be preserved, that is, G1, G2, G3, G4 define the quadrilateral base, G5 defines
the apex, G1, G5, G10 are on the same edge, etc.
3. For a 5 noded CPYRAM element, only G1 - G5 should be provided. For a 13 noded CPYRAM element, G1 - G13
should be provided. Intermediate number of grid points between 5 and 13 are not allowed.
4. The pyramid elements use the basic coordinate system as the element coordinate system. They can use a material
coordinate system defined by the CORDM field of the corresponding PSOLID entry. CORDM = 0, -1, -2 or blank
is the same as the basic coordinate system.
5. For CORDM > 0, the material coordinate system is defined with respect to the initial geometry and is used to input
orthotropic or anisotropic material properties and for stress output. For geometric nonlinear analysis, the material
coordinate system rotates with the element. Component of stresses are output in the material coordinate system
referenced by the CORDM field of PSOLID entry (CORDM > 0).
PSLDN1 Nonlinear Property Extensions for a PSOLID Entry
The PSLDN1 bulk data entry now has two additional keywords C5 and C13 for defining the element structural behaviour
and integration scheme (BEHi and INTi), and element heat behaviour and integration scheme (BEHiH and INTiH).
Main Index
72 PLOAD4
User Interface
Structural Classification of Elements

Element Structural Type BEHi CODE Integration Code Element Type # Nodes
SOLID SOLID L PYR 5
LRIH PYR 5
Q PYR 13
Heat Classification of Elements

Element Heat Type BEHiH CODE Integration Code Element Type # Nodes
SOLID SOLID L PYR 5
Q PYR 13
Integration codes are:
L Linear
LRIH Linear Reduced Integration Hourglass control
Q Quadratic
PLOAD4 Pressure Load on Surface and Faces of Solid Elements
The PLOAD4 bulk data entry can now be used for defining pressure load on faces of pyramid element as well. Any two
diagonal grids on the rectangular face defined by G1 and G3 identify the rectangular face of the pyramid element. For the
triangular face, G1 and G2 defining the adjacent grids on the base of the quadrilateral face sharing a common edge with
the triangle identify the triangular face.
CHBDYE Geometric Surface Element Definition (Element Form)
For the CHBDYE element defining a boundary condition surface element with reference to a heat conduction element the
side convention for the pyramid element is as follows:
Side gp gp gp gp
1 3 2 5
2 1 4 5
3 2 1 5
4 3 5 4
5 4 1 2 3
Main Index
CHAPTER 6 73
Pyramid Elements
GEOMCHECK Specifies Geometry Check Options
The following geometry check options have been added for the CPYRAM entry.
Name Value Type Default Comment

PYR_AR Real > 0.0 100.0 Longest edge to shortest edge aspect ratio.
PYR_EPLR Real > 0.0 0.50 Edge point length ratio.
PYR_EPIA Real > 0.0 150.0 Edge point included angle in degrees.
PYR_DETJ Real 0.0 | J | minimum value.
PYR_WARP Real > 0.0 0.707 Quadrilateral face warp coefficient.
Examples
The delivery contains a number of test cases in TPL/LINPYRA and TPL/NLINPYRA subdirectories in the Nastran
Documentation Installation Directory. The following table contains a brief information on a few of these tests:
Deck Name Feature

npyr_023 Closure of rubber seal using segment-to-segment contact with friction
npyra_95a External acoustics with ACFPMRESULT request
npyra_95b
r3dcpy13f, Rotor dynamics analysis using simple hollow tube model
r3dcpy13r
Example 1: Closure of rubber seal using segment-to-segment contact with friction

This example is based on the demonstration model given in chapter 50 of Demonstration Problems Manual - Implicit
Nonlinear. A deformable rubber seal is placed between two rigid plates, one of which is moved downwards. This example
illustrates the nonlinear analysis of segment-to-segment contact with large sliding and friction.
A region in the rubber seal with a mixed mesh incorporating CHEXA elements in the core, CTETRA elements at the
boundary and CPYRAM elements in the transition region is shown in the figure below:
Main Index
74 GEOMCHECK
Examples
Figure 6-2 Rubber Seal FE model showing Pyramid Elements
Main Index
CHAPTER 6 75
Pyramid Elements
This modified model has been analysed in Marc and MSC Nastran (SOL 400) for comparison and the results show
identical behaviour as shown in figures below:
Figure 6-3 Comparison of behavior in Marc versus MSC Nastran
Main Index
76 GEOMCHECK
Examples
Figure 6-4 Closure of Rubber Seal simulated in MSC Nastran
Example 2: External acoustics with ACFPMRESULT request

This example is derived from the Course notes NAS-115, Workshop 9 titled flat plate exterior acoustics. This involves an
exterior acoustics analysis of a simply supported square plate excited by an acoustic load normal to the plate at its centre as
described in the figure below.
Main Index
CHAPTER 6 77
Pyramid Elements
Figure 6-5 Exterior acoustics flat plate with acoustic excitation
Here, the fluid region is modelled with a combination of both CHEXA and CPYRAM elements. The results for the mixed
mesh are compared with the workshop results with pure CHEXA elements (ACFPMRESULT). The following figures show
the result comparison.
Figure 6-6 ACFPM Results comparison between SOL 400 and SOL 111
Main Index
78 GEOMCHECK
Examples
Figure 6-7 Velocity Results comparison between CHEXA and mixed CHEXA and CPYRAM
Example 3: Rotor dynamics analysis using simple hollow tube model

In order to validate the implementation for Rotordynamics analysis, a simple hollow tube rotor model is considered. The
rotor is constrained at one end, similar to cantilever boundary condition. This particular rotor geometry was modeled using
existing CHEXA elements and also using newly developed CPYRAM elements for comparison of results.
Figure 6-8 Rotordynamics analysis of simple hollow tube
Campbell Diagram obtained using CPYRAM elements in fixed and rotating reference frames is shown below. The results
obtained using CPYRAM elements match very well with those obtained using CHEXA elements.
Main Index
CHAPTER 6 79
Pyramid Elements
Figure 6-9 Results in Rotating reference frame
Figure 6-10 Results in fixed reference frame
Main Index
80 GEOMCHECK

1. The default for the linear (5-node) pyramid element is full integration and this is directly supported using the
PSOLID entry. If reduced integration is desired for 5-node pyramid element then the PSLDN1 bulk data entry C5
line should be used.
2. The linear pyramid element may show excessively stiff behavior for bending dominated test problems. Since the
pyramid elements are mainly used as transition elements, this drawback for first-order elements is not an issue in
most real world applications. It should also be noted that second order pyramid elements behave well for bending
problems without any shear locking issue.
3. Digimat support via MATDIGI material entry is not currently available for pyramid elements.
4. ELSUM does not work for pyramid elements. Also, ELSUM does not work for all elements identified by secondary
properties (PSLDN1, PSHLN1, etc).
5. Spatially dependent/frequency dependent materials are not supported for pyramid elements.
6. Stress recovery in conjunction with thermal loads for pyramid elements is supported for non-linear analysis
(SOL400) and linear analysis (linear solution sequences, SOL400). Limitations in SOL400 with respect to this
feature are relevant to both the pyramid element and other elements identified through secondary properties like
PSLDN1 / PSHLN1:
a. Thermal stresses in a linear perturbation analysis about a non-linear state in SOL400 will not be calculated
properly for these elements.
b. Thermal stresses in a nonlinear step in SOL400 will not be calculated properly for these elements when they are
used in super-elements.
7. Damping (GE / GEij) is supported for pyramid elements through MAT1/ MAT9 entries. Limitations with respect
to this feature are relevant to both the pyramid element and other elements identified through secondary properties
like PSLDN1 / PSHLN1:
a. GE field on MAT2, MAT3, MAT8 materials are not supported for these elements.
b. GEij fields on MAT2 are not supported for these elements.
8. Currently there is no support from Patran for the Pyramid elements.
Main Index
CHAPTER 6 81
Pyramid Elements
Main Index
Chapter 7: Module Instantiation
7 Module Instantiation
 Introduction 83

Benefits 83

Input 83
 Output 85

Guidelines and Limitations 86

Examples 86
Main Index
CHAPTER 7 83
Introduction
In V2018, Modules were introduced as new method of substructuring. Modules are similar to the Part Superelement feature
in which each substructure is defined by a standalone Bulk Data section delimited by the BEGIN MODULE and
ENDMODULE commands. Modules defined in this way are called primary Modules. In V2019, Module instantiation
provides the analyst with the ability to replicate or copy a Module to a new location. In addition to a copy, the analyst is
also able to mirror the Module to a new position. For purposes of the discussion below, a primary Module is the Module
being copied and the resulting copied Module is called a secondary Module. Module 0 refers to the main Bulk Data section.
Benefits
Module instantiation is particularly useful when there are components of the structure that are repeated; for example, gear
teeth, turbine fan blades, RAM chips on a computer board or many components found in an airplane or automobile. The
primary benefit to the analyst is that there are fewer Bulk Data entries to manage. In other words, Module instantiation
greatly enhances user convenience and productivity by eliminating the need to individually model geometrically identical
Modules and contributes to enhanced efficiency for performing the analysis of such assembled configurations.
Input
A secondary Module is first defined by the MDBULK entry by specifying TYPE=”REPEAT”, “MIRROR”, or “MOVE”
and the primary Module ID in the RMODID field:
1 2 3 4 5 6 7 8 9
MDBULK MODID TYPE RMODID METHOD TOL
Describer Meaning
MODID Element identification number.
TYPE Module Type (Character)
PRIMARY Module with its own BEGIN MODULE section (default)
REPEAT Module is identical copy of primary Module RMODID
MIRROR Module is mirror copy of primary Module RMODID
MOVE Module is identical or mirror of primary Module RMODID and the copied
module's repositioning is defined on the MDMOVE entry.
RMODID Identification number of the reference (or primary) Module, used only if TYPE = “REPEAT”,
“MIRROR” or “MOVE”. (Integer>0)
Then the repositioning of the secondary is achieved with one of two user interfaces: Classic and Enhanced. The Classic
interface uses TYPE=”REPEAT” or TYPE=”MIRROR” and the Enhanced interface uses TYPE=”MOVE”. For a given
Module, the interfaces may not be combined.
Main Index
Input
Classic Interface
The Classic interface comprises the MDLOC and MDMPLN Bulk Data entries which are based upon the SELOC and
SEMPLN entries employed in Part Superelement instantiation. MDLOC defines a Module copy by listing three non-
collinear GRIDs or POINTs in the Primary Module and three corresponding GRIDs or POINTs in Module 0. MDMPLN
defines a Module copy/mirror by specifying three noncollinear GRIDs or POINTs in the mirror plane. The GRIDs or
POINTs referenced by MDMPLN are specified in Module 0 only. A secondary Module may be created by both an
MDMPLN and MDLOC entry but the Module will be mirrored first according to the MDMPLN specification and then
repositioned second according to MDLOC. MDLOC and MDMPLN are specified in Module 0 only. Only one MDLOC
and/or MDMPLN may be specified for a given Module.
Enhanced Interface
The Enhanced interface comprises the MDMOVE, MDTRAN, MDROT1, MDROT2, MDMIR1, and MDMIR2
entries. The MDBULK entry has TYPE=”MOVE” which requires an MDMOVE entry identified by the secondary (or
copied) Module's ID.
MDMOVE Defines a Module repositioning sequence. References MDMIRi, MDROTi, and MDTRAN
entries.
Then the MDMOVE entry defines a sequence of move “commands” described on one or more of the following entries:
MDMIR1 Defines a Module mirror plane by three non-collinear GRIDs or POINTs on the mirror plane
MDMIR2 Defines a Module mirror plane by specifying a pair of coordinate system axes defined by a CORDij
entry and a reference GRID or POINT through which the mirror plane will be applied.
MDROT1 Defines a Module rotation by specifying the endpoints (GRIDs or POINTs) of a rotation vector
and a reference GRID or POINT about where the rotation occurs.
MDROT2 Defines a Module rotation by specifying a coordinate system axis defined by a CORDij entry for
the rotation vector and a reference GRID or POINT about where the rotation occurs.
MDTRAN Defines a Module translation by specifying the endpoints (GRIDs or POINTs) of a translation
vector. The default magnitude of translation is the length of the vector.
MDMOVE, MDTRAN, MDROT1, MDROT2, MDMIR1, and MDMIR2 entries; and any GRIDs, POINTs, or
CORDij entries referenced by these entries, are specified in Module 0 only.
Loading and Boundary Conditions in Secondary Modules

It should be noted that the secondary Module has its own basic coordinate system which we call the Module Basic
Coordinate System (MBCS) and, if any rotation or mirroring occurs, the MBCS will not have the same orientation as
Module 0's basic coordinate system which we call the Assembly Basic Coordinate System (ABCS). If repositioning involves
rotating or mirroring the Module, then the MBCS, and any CORDij entries in the primary Module, will also be rotated
or mirrored. Also, in the case of a mirror, the MBCS will be a left-handed coordinate system. Thus, all GRID point loads,
Main Index
CHAPTER 7 85
MPCs, and SPCs go through the same rotation or mirroring as the Module-possibly causing unexpected results if the user
has not planned for this rotation or mirroring. The user is cautioned to check the OLOAD RESULTANTS carefully for
any Modules that are rotated during a repositioning or mirroring operation. Body loads defined by GRAV, RFORCE, and
ACCEL Bulk Data entries will be applied according to the ABCS.
Secondary Module's Bulk Data Section

By default, the secondary Module inherits all of the Bulk Data entries from it's primary or reference Module and therefore
the secondary Module does not require its own Bulk Data section (BDS). If, however the user would like to define, for
example, a new set of loads and/or boundary conditions for the secondary Module then a BDS for the secondary is required
and will contain only the entries for the new loads and/or boundary conditions. Only those entries of the same name in the
primary's BDS will be overridden by the secondary's BDS. For example, a single FORCE entry in the secondary's BDS will
only override all FORCE entries copied from the primary's BDS. If the user just wants to ignore selected entries from the
primary then the EXCLUDE Bulk Data entry in the secondary's BDS may be specified.
It should be noted that any Bulk Data entry coming from the primary's BDS may be replaced or ignored in the secondary's
BDS except for GRID entries and any CORDij entries which affect the Module's geometry.
Output
Module Definition Table

The “MODULE DEFINITION TABLE” has been expanded to include the definition of secondary Modules. The sample
f06 excerpt shows that Module 10 is a primary Module which is being instantiated or copied to secondary Modules 20, 30,
and 40.
MODULE DEFINITION TABLE (SORTED BY MODULE ID)
PRIMARY
MODULE MODULE TYPE LABEL
-------- -------- ----------------------------- --------------------
0 0 MAIN BULK DATA
10 0 PRIMARY (BEGIN MODULE) LOWER LEFT
20 10 COPY (MDBULK) UPPER LEFT
30 10 COPY (MDBULK) LOWER RIGHT
40 10 COPY (MDBULK) UPPER RIGHT
No other changes have been made to the format or contents of the f06, op2, or pch files.
An important point should be noted with respect to interpreting the grid point results of a secondary Module. The grid
point results; e.g., DISPLACEMENTs, SPCForces, OLOADs, etc., are interpreted according to the MBCS as described
above.
Main Index

V2019 has the current limitations:
 “Create a Module copy from another Module copy. In other words, RMODID on the MDBULK Bulk Data
entry must refer to a primary Module.
 “If MDMIR1 or MDMIR2 Bulk Data entry is referenced on MDMOVE entry, then it can only be referenced as
the first movement.
 “Defining a group of Modules is not supported as well as copying the group.
 “Modules embedded within another Module is not supported.
Examples
Flat Plate Model with One Primary and Three Secondary Modules
We will demonstrate the enhanced interface with a very simple flat plate model. The model may be found at
tpl/modules3/modules27.dat. The primary Module 10 has four CQUAD4 elements each measuring 1 cm by 1 cm on the
left below. We will create a copy called Module 30 with three movements by utilizing the Enhanced Interface. To create
Module 30 (indicated by dashed edges), we will first mirror Module 10 about a plane parallel to the assembly basic XZ
plane through GRID 107. The MDMIR1 entry below references three POINTs in Module 0 which define this plane. We
cannot use GRIDs 107 and 108 for P1 and P2 on the MDMIR1 entry because these GRIDs are located in Module 10 and
POINTs referenced by MDMIR1 must be defined in Module 0.
Format:
1 2 3 4 5 6 7 8 9 10
MDMIR1 MVID P1 P2 P3
Describer Meaning
MVID Move identification number to be referenced on an MDMOVE entry. (Integer>0)
Pi GRID or POINT identification numbers of three non-collinear points in Module 0. (Integer>0)
Main Index
CHAPTER 7 87
Note how the MBCS is also mirrored in the figure above. Next, we will translate Module 30 by 2 cm in the assembly's x-
direction using the MDTRAN entry. POINTs 3007 and 3008 (IDS and IDE) define a vector in the assembly x-direction
but its length is only 1 cm so we must specify 2 cm for MAG.
Format:
1 2 3 4 5 6 7 8 9 10
MDTRAN MVID IDS IDE MAG
Describer Meaning
IDS GRID or POINT identification number of translation vector's starting point. (Integer>0)
IDE GRID or POINT identification number of translation vector's end point. (Integer>0)
MAG Magnitude of translation. If blank or zero, then the length of the vector will be used. (Real,
Default=0.0)
Main Index
Examples
Finally, we will rotate Module 30 by 90 degrees (MAG on MDROT1 entry) about a vector normal into the page formed
by POINTs 3000 and 3007 (IDS and IDE). The rotation will occur at POINT 1000 (RID).
Format:
1 2 3 4 5 6 7 8 9 10
MDROT1 MVID RID IDS IDE MAG
Describer Meaning
RID GRID or POINT identification number of a reference point at which rotation will occur. If
blank or 0 then Module will be rotated about rotation vector defined from IDS to IDE.
(Integer≥0, Default=0)
IDS GRID or POINT identification number of rotation vector's starting point. (Integer>0)
IDE GRID or POINT identification number of rotation vector's end point. (Integer>0)
MAG Magnitude of rotation in degrees. (Real≠0.0)
Main Index
CHAPTER 7 89
We will now complete the model with Modules 20 and 40 and leave it to the reader to dissect the movement commands.
Main Index
Examples
The applied loading is indicated by red arrows and constraints by green. The constraints and loads have to applied according
the mirrored and rotated coordinate systems. In BEGIN MODULE=10, GRID 101 is allowed to slide in the y-direction.
In BEGIN MODULE=20, SPC,1,101 is overridden by SPC,1,107. In BEGIN MODULE=20, the SPC in BEGIN
MODULE=10 is ignored and FORCE entries are defined. Note that the force directions are applied in the negative x-
direction because their direction is with respect to the MBCS. Similarly, for BEGIN MODULE=40.
Main Index
CHAPTER 7 91
The next examples are more complex than previous and show how the module copies are created with both the classic and
enhanced interface. All examples below are available in the tpl/modules3 folder.
Main Index
Examples
Main Index
CHAPTER 7 93
Main Index
Examples
Main Index
CHAPTER 7 95
Main Index
Examples
Main Index
Chapter 8: User Interface
8 User Interface

The Nastran HDF5 Result Database (NH5RDB) Enhancement 98
Main Index
98 MSC Nastran 2018.2 Release Guide
The Nastran HDF5 Result Database (NH5RDB) Enhancement
The Nastran HDF5 Result Database (NH5RDB)

Enhancement
Introduction
In this release, the NH5RDB is enhanced to support aerodynamic analysis SOL 144, 145 and 146. In
addition, Nastran module feature and more data types are added.
Benefits
The NH5RDB covers more Nastran solution sequences and data types for post processing.
The supported data types are summarized in the following, please refer to NH5RDB schema file for the
dataset structure definitions
1. Aerodynamic analysis SOL 144, 145 and 146
a. Stability and control derivatives
b. Aerodynamic pressure and force
c. Divergence and flutter table
d. Trim variables
e. Intermediate matrix
2. Modal effective mass
a. Effective mass
b. Mass fraction
c. Participation factor
3. Module feature
a. Module input entries
b. Support in NH5RDB domain definition
4. Contact
a. Contact check and adjustment
b. Global contact body data
5. Debug data block OFDBGDT
6. End load and shear stress
7. Eigen vector for structural and fluid coupled analysis
Main Index
CHAPTER 8 99
User Interface
Test Case
The aeroelastic analysis example nh5_ha144a is listed below, the output datasets in NH5RDB is shown in
figure 1 and 2.
Test model file: nh5_ha144a.dat
$$$$$$$$ HANDBOOK FOR AEROELASTIC ANALYSIS EXAMPLE HA144A $$$$$$$$
$ $
$ MODEL DESCRIPTION 30 DEG FWD SWEPT WING W/CANARD $
$ BEAM MODEL WITH DUMBBELL MASSES $
$ $
$ SOLUTION SYMMETRIC IN-FLIGHT STATIC STABILITY $
$ ANALYSIS USING DOUBLET-LATTICE $
$ METHOD AERODYNAMICS AT MACH NO. 0.9 $
$ AND ZONA51 AERO AT MACH NO. 1.3
$ $
$ OUTPUT PLOTS OF THE STICK MODEL AND AERO $
$ GRID, LISTS OF RESTRAINED AND $
$ UNRESTRAINED SYMMETRIC STATIC $
$ STABILITY DERIVATIVES PLUS THE $
$ AERODYNAMIC FORCES AND PRESSURES $
$ PLUS STRESSES AND DEFLECTIONS FOR $
$ 1G LEVEL FLIGHT. $
$ $
$$$$$$$$ $$$$$$$$
TIME 5 $ CPU TIME IN MINUTES
SOL 144 $ STATIC AERO
CEND
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
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)
OUTPUT(PLOT)
PLOTTER = NASTRAN
SET 1 = ALL
FIND SCALE, ORIGIN 1,SET 1
PLOT SET 1
Main Index
PLOT STATIC DEFORMATION 0, ORIGIN 1, SET 1, OUTLINE

BEGIN BULK
mdlprm,hdf5,1
$*** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ***$
$ $
$ THE ANNOTATIONS IN THIS INPUT SECTION ARE INTENDED TO $
$ EXPLAIN THE DATA ON THE ENTRY IMAGES FOR THIS SPECIFIC $
$ EXAMPLE WITHOUT REFERENCE TO THE VARIOUS MANUALS WHERE $
$ MORE GENERAL DESCRIPTIONS WILL BE FOUND. $
$ $
$*** * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * ***$
$ $
$ * * * STRUCTURAL DATA * * * $
$ $
$ (LB-FT-SEC SYSTEM) $
$ $
$ * * GRID GEOMETRY * * $
$ $
$ GRID 90 - 100 (T3) FUSELAGE POINTS $
$ GRID 110 - 122 (T3) WING POINTS $
$ $
$ * FUSELAGE GRID * $
$ $
$ THE GRID ENTRY DEFINES THE LOCATION OF A STRUCTURAL GRID $
$ POINT. LISTED ARE ITS COORDINATE SYSTEM ID, ITS LOCATION, $
$ THE ID OF THE COORDINATE SYSTEM IN WHICH ITS DISPLACEMENTS $
$ ARE DEFINED, ITS PERMANENT SINGLE-POINT CONSTRAINTS AND $
$ ITS ASSOCIATED SUPERELEMENT ID. $
$ $
$ ID CP X1 X2 X3 CD PS SEID
GRID 90 15. 0. 0.
GRID 97 0. 0. 0.
GRID 98 10. 0. 0.
GRID 99 20. 0. 0.
GRID 100 30. 0. 0.
$ $
$ * WING GRID * $
$ $
$ ID CP X1 X2 X3 CD PS SEID
GRID 111 24.61325 +5. 0.
GRID 110 27.11325 +5. 0.
GRID 112 29.61325 +5. 0.
GRID 121 18.83975+15. 0.
GRID 120 21.33975+15. 0.
GRID 122 23.83975+15. 0.
$ $
$ * * STRUCTURAL STIFFNESS PROPERTIES * * $
$ $
$ * FUSELAGE STRUCTURE * $
$ $
Main Index
CHAPTER 8 101
User Interface
$ THE CBAR ENTRY DEFINES A SIMPLE BEAM ELEMENT. LISTED ARE $

$ ITS PROPERTY ENTRY ID, THE TWO GRID POINTS JOINED BY THE $
$ BEAM AND COMPONENTS OF A VECTOR FROM THE FIRST POINT. $
$ THIS VECTOR DEFINES THE DIRECTION OF THE STRUCTURAL DE- $
$ FLECTION OF THE POINT AND ITS POSITIVE SENSE. $
$ $
$ EID PID GA GB X1,GO X2 X3
CBAR 101 100 97 98 0. 0. 1.
CBAR 102 100 98 90 0. 0. 1.
CBAR 100 100 90 99 0. 0. 1.
CBAR 103 100 99 100 0. 0. 1.
$ $
$ THE PBAR ENTRY DEFINES GEOMETRIC PROPERTIES OF THE BEAM. $
$ LISTED ARE ITS ASSOCIATED MATERIAL ENTRY ID, ITS CROSS SEC- $
$ TIONAL AREA, AREA MOMENTS OF INERTIA, TORSIONAL MOMENT $
$ OF INERTIA AND NON-STRUCTURAL MASS PER UNIT AREA. THE $
$ OPTIONAL CONTINUATION ENTRY CONTAINS STRESS RECOVERY $
$ COEFFICIENTS, I.E., Y,Z COORDINATES WHERE STRESSES ARE $
$ TO BE COMPUTED. K1 AND K2 ARE AREA FACTORS FOR SHEAR $
$ STIFFNESS (DEFAULT IS BLANK; THEN SHEAR STIFFNESS IS $
$ INFINITE, I.E., SHEAR FLEXIBILITY IS ZERO. I12 IS THE $
$ AREA PRODUCT OF INERTIA. $
$ $
$ PID MID A I1 I2 J NSM
PBAR 100 1 2.0 .173611 0.15 0.5 +PB1
$ C1 C2 D1 D2 E1 E2 F1 F2
+PB1 1.0 1.0 1.0 -1.0 -1.0 1.0 -1.0 -1.0 +PB2
$ K1 K2 I12
+PB2 0.0
$ $
$ * WING STRUCTURE * $
$ $
$ EID PID GA GB X1,GO X2 X3
CBAR 110 101 100 110 0. 0. 1.
CBAR 120 101 110 120 0. 0. 1.
$ $
$ THE RBAR ENTRY DEFINES A RIGID BAR. LISTED ARE THE GRID $
$ POINTS AT EACH END AND THE DEPENDENT AND INDEPENDENT DOFS $
$ AT EACH END. THE NUMBER OF INDEPENDENT DOFS AT THE TWO $
$ ENDS MUST EQUAL SIX. BY DEFAULT THOSE NOT DECLARED INDE- $
$ PENDENT ARE MADE DEPENDENT. $
$ $
$ EID GA GB CNA CNB CMA CMB
RBAR 111 110 111 123456
RBAR 112 110 112 123456
RBAR 121 120 121 123456
RBAR 122 120 122 123456
$ $
$ PID MID A I1 I2 J NSM
Main Index
PBAR 101 1 1.5 0.173611+2.0 0.462963 +PB3

$ C1 C2 D1 D2 E1 E2 F1 F2
+PB3 0.5 3.0 0.5 -3.0 -0.5 3.0 -0.5 -3.0 +PB4
$ K1 K2 I12
+PB4 0.0
$ $
$ THE MAT1 ENTRY DEFINES THE MATERIAL PROPERTIES. LISTED $
$ ARE ITS ID, ITS ELASTIC MODULUS, SHEAR MODULUS, POISSONS $
$ RATIO, MASS DENSITY, TEMPERATURE EXPANSION COEFFICIENT, $
$ REFERENCE TEMPERATURE AND A STRUCTURAL DAMPING COEFFICIENT. $
$ $
$ MID E G NU RHO A TREF GE
MAT1 1 1.44+9 5.40+8
$ $
$ * * MASS AND INERTIA PROPERTIES * * $
$ $
$ * FUSELAGE MASSES * $
$ $
$ THE CONM2 ENTRY DEFINES A CONCENTRATED MASS. LISTED ARE $
$ ITS ID, GRID LOCATION, COORDINATE SYSTEM TO LOCATE THE $
$ CENTER OF GRAVITY, THE MASS VALUE AND THE LOCATION OF $
$ THE CENTER OF GRAVITY RELATIVE TO THE GRID LOCATION. $
$ $
$ EID G CID M X1 X2 X3
CONM2 97 97 0 1500.0
CONM2 98 98 0 1500.0
CONM2 99 99 0 1500.0
CONM2 100 100 0 1500.0
$ $
$ * WING MASSES * $
$ $
CONM2 111 111 0 600.0
CONM2 112 112 0 400.0
CONM2 121 121 0 600.0
CONM2 122 122 0 400.0
$ $
$ * * STRUCTURAL PARAMETERS * * $
$ $
$ THE PARAM,GRDPNT,XX ENTRY CAUSES THE GRID POINT WEIGHT $
$ GENERATOR TO BE EXECUTED USING GRID POINT XX AS THE REF- $
$ ERENCE POINT. THEN THE INERTIA MATRIX, THE TRANSFER MATRIX $
$ FROM BASIC TO PRINCIPAL AXES AND OTHER PERTINENT INERTIA $
$ DATA ARE PRINTED. $
$ $
PARAM GRDPNT 90
$ $
$ THE PARAM,WTMASS,GINV CAUSES ALL THE STRUCTURAL MASSES AND $
$ MASS DENSITIES TO BE MULTIPLIED BY GINV (I.E., BY ONE OVER $
$ THE ACCELERATION OF GRAVITY). THE DYNAMIC PRESSURE SUPPLIED $
$ FOR AERODYNAMIC FORCE CALCULATIONS WILL NOT BE MULTIPLIED $
Main Index
CHAPTER 8 103
User Interface
$ BY GINV. $
$ $
PARAM WTMASS .031081
$
$ THE PARAM,AUNITS,GINV PERMITS THE ACCELERATIONS ON THE TRIM
$ ENTRY TO BE SPECIFIED IN UNITS OF LOAD FACTOR (I.E., IN G'S)
$
PARAM AUNITS .031081
$ $
$ * * STRUCTURAL CONSTRAINTS * * $
$ $
$ THE SPC1 ENTRY CONSTRAINS THE LISTED GRID POINTS IN THE $
$ SPECIFIED DOF COMPONENTS. $
$ $
$ SID C G1 G2 G3 G4
SPC1 1 1246 90
SPC1 1 246 97 98 99 100
$ $
$ THE SUPORT ENTRY IDENTIFIES A GRID POINT OR A SCALAR POINT $
$ AND SPECIFIES THE DOF COMPONENTS IN WHICH THE USER DESIRES $
$ REACTIONS TO BE APPLIED TO PREVENT RIGID BODY MOTION. IT $
$ THUS INVOKES THE SOLUTION OF THE BALANCE EQUATIONS TO DETER- $
$ MINE THE REACTIONS. IN THE STATIC AEROELASTIC SOLUTION $
$ THE DOF COMPONENTS MUST BE CONSISTENT WITH THE UNDEFINED $
$ VARIABLES ON THE TRIM ENTRIES. $
$ $
$ ID C
SUPORT 90 35
$ $
$ THE OMIT1 ENTRY IDENTIFIES GRID POINT COMPONENTS TO BE $
$ OMITTED FROM THE REMAINDER OF THE ANALYSIS. $
$ $
$ ID G G
OMIT1 4 110 120
$ $
$ * * * AERODYNAMIC DATA * * * $
$ $
$ (LB-FT-SEC SYSTEM) $
$ $
$ * * ELEMENT GEOMETRY * * $
$ $
$ THE AEROS ENTRY IS UNIQUE TO THE STATIC AEROELASTICITY $
$ SOLUTION, SOL21. ACSID IDENTIFIES THE AERO COORDINATE $
$ SYSTEM, RCSID IDENTIFIES THE REFERENCE COORDINATE SYS- $
$ TEM FOR RIGID BODY MOTION. REFC IS THE REFERENCE CHORD. $
$ REFB IS THE REFERENCE SPAN. REFS IS THE REFERENCE WING $
$ AREA. SYMXZ AND SYMXY ARE SYMMETRY KEYS. $
$ $
$ ACSID RCSID REFC REFB REFS SYMXZ SYMXY
Main Index
AEROS 1 100 10.0 40.0 200.0 1

$ $
$ THIS CORD2R ENTRY DEFINES THE AERO COORDINATE SYSTEM $
$ FLAGGED BY THE AEROS ENTRY. THE ORIGIN IS AT THE CANARD $
$ QUARTER CHORD. LISTED ARE THE ORIGIN, A POINT ALONG THE $
$ Z AXIS AND A POINT IN THE X-Z PLANE, ALL IN THE RID $
$ COORDINATE SYSTEM. $
$ $
$ CID RID A1 A2 A3 B1 B2 B3
CORD2R 1 0 12.5 0. 0. 12.5 0. 10. +CRD1
$ C1 C2 C3
+CRD1 20. 0. 0.
$ $
$ THIS CORD2R ENTRY DEFINES THE NACA COORDINATE SYSTEM TO $
$ WHICH ALL THE STABILITY DERIVATIVES AND TRIM CONDITIONS $
$ WILL BE REFERENCED. $
$ $
$ CID RID A1 A2 A3 B1 B2 B3
CORD2R 100 0 15.0 0.0 0.0 15.0 0.0 -10.0 +CRD100
$ C1 C2 C3
+CRD100 0.0 0.0 0.0
$ $
$ * * SPLINE FIT ON THE LIFTING SURFACES * * $
$ $
$ * BEAM SPLINE FIT ON THE WING * $
$ $
$ THE SPLINE2 ENTRY SPECIFIES A BEAM SPLINE FOR INTERPOLAT- $
$ ION OVER THE REGION OF THE CAERO ENTRY (ID1 AND ID2 ARE $
$ THE FIRST AND LAST BOXES IN THIS REGION). SETG REFERS $
$ TO A SET1 ENTRY WHERE THE STRUCTURAL GRID POINTS ARE $
$ DEFINED. DZ AND DTOR ARE SMOOTHING CONSTANTS FOR LINEAR $
$ ATTACHMENT AND TORSIONAL FLEXIBILITIES. CID IDENTIFIES $
$ THE CORD2R ENTRY THAT DEFINES THE SPLINE AXIS. DTHX AND $
$ DTHY ARE ROTATIONAL ATTACHMENT FLEXIBILITIES (-1. SPECIFIES $
$ NO ATTACHMENT). $
$ $
$ EID CAERO ID1 ID2 SETG DZ DTOR CID
SPLINE2 1601 1100 1100 1131 1100 0. 1. 2 +SPW
$ DTHX DTHY
+SPW -1. -1.
$ $
$ THE CAERO1 ENTRY IS USED FOR DOUBLET-LATTICE AERODYNAMICS. $
$ LISTED ARE ITS PAERO ENTRY ID AND THE COORDINATE SYSTEM $
$ FOR LOCATING THE INBOARD AND OUTBOARD LEADING EDGE POINTS $
$ (1 AND 4). NSPAN AND NCHORD, OR LSPAN AND LCHORD, ARE $
$ USED TO PARTITION THE WING INTO AERODYNAMIC PANELS, $
$ THE FORMER FOR UNIFORMLY SPACED PANELS AND THE LATTER $
$ FOR NON-UNIFORMLY SPACED PANELS. IGID IS THE ID OF ITS $
$ ASSOCIATED INTERFERENCE GROUP. THE CONTINUATION ENTRY $
$ DEFINES POINTS 1 AND 4, THE ROOT CHORD AND TIP CHORD. $
Main Index
CHAPTER 8 105
User Interface
$ THE BOXES FORMED BY THE GRID LINES WILL BE NUMBERED $

$ BEGINNING WITH EID SO CHOOSE A NUMBER THAT IS UNIQUE, $
$ AND IS GREATER THAN ALL STRUCTURAL GRID, SCALAR AND $
$ EXTRA POINT IDS. $
$ $
$ EID PID CP NSPAN NCHORD LSPAN LCHORD IGID
CAERO1 1100 1000 8 4 1 +CAW
$ ( FWD LEFT POINT ) CHORD ( FWD RIGHT POINT ) CHORD
$ X1 Y1 Z1 X12 X4 Y4 Z4 X14
+CAW 25. 0. 0. 10. 13.45299+20. 0. 10.
$ $
$ THE PAERO1 ENTRY IS REQUIRED EVEN THOUGH IT IS NON-FUNCTIONAL $
$ (BECAUSE THERE ARE NO ASSOCIATED BODIES IN THIS EXAMPLE). $
$ $
$ PID B1 B2 B3 B4 B5 B6
PAERO1 1000
$ $
$ THE SET1 ENTRY DEFINES THE SETS OF STRUCTURAL GRID POINTS $
$ TO BE USED BY THE BEAM SPLINE FOR INTERPOLATION. $
$ $
$ SID G1 G2 G3 G4
SET1 1100 99 100 111 112 121 122
$
$ THE CORD2R ENTRY DEFINES THE COORDINATE SYSTEM IN WHICH THE $
$ BEAM SPLINE EXTENDS ALONG THE WING Y-AXIS. IT LISTS THE $
$ ORIGIN, A POINT ALONG THE Z-AXIS AND A POINT IN THE X-Z $
$ PLANE. $
$ $
$ CID CS A1 A2 A3 B1 B2 B3
CORD2R 2 0 30. 0. 0. 30. 0. 10. +CRD2
$ C1 C2 C3
+CRD2 38.66025+5.0 0.
$ $
$ * CONTROL SURFACE DEFINITION * $
$ $
$ THE AESURF ENTRY DEFINES AN AERODYNAMIC CONTROL SURFACE. $
$ LISTED ARE THE ALPHANUMERIC NAME OF THE SURFACE, THE ID $
$ OF A COORDINATE SYSTEM THAT DEFINES THE HINGE LINE AND $
$ THE ID OF AN AELIST ENTRY. $
$ $
$ ID LABEL CID1 ALID1 CID2 ALID2
AESURF 505 ELEV 1 1000
$ $
$ THE AELIST ENTRY LISTS AERODYNAMIC BOXES THAT LIE ON THE $
$ CONTROL SURFACE. $
$ $
$ SID E1 E2 E3 ETC
AELIST 1000 1000 THRU 1007
$ $
Main Index
$ * BEAM SPLINE FIT ON THE CANARD * $

$ $
$ AGRID PANEL (FIRST & LAST BOX)SGRID SPLCS
SPLINE2 1501 1000 1000 1007 1000 0. 1. 1 +SPC
+SPC 1. -1.
$ $
$ PANEL PID CS NSPAN NCHORD IGP
CAERO1 1000 1000 2 4 1 +CAC
$ (FWD LEFT POINT ) CHORD (FWD RIGHT POINT ) CHORD
+CAC 10. 0. 0. 10. 10. 5. 0. 10.
$ $
$ SGRID GRID POINTS
SET1 1000 98 99
$ $
$ $
$ * * * AERODYNAMIC DATA * * * $
$ $
$ * * USER SUPPLIED INPUT DATA * * $
$ $
$ THE DMI ENTRY ACCOMMODATES DIRECT INPUT OF USER SUPPLIED $
$ MATRICES OF DATA. LISTED ARE THE NAME OF THE MATRIX, THE $
$ FORM OF MATRIX (IN THIS CASE DIAGONAL), THE TYPE OF DATA $
$ (IN THIS CASE REAL SINGLE PRECISION), BEING INPUT AND THE $
$ TYPE EXPECTED AT OUTPUT (IN THIS CASE TO BE DETERMINED $
$ INTERNALLY). M IS THE NUMBER OF ROWS AND N IS THE NUMBER $
$ OF COLUMNS. THE DATA IS EXPECTED BY COLUMNS. THE CONTIN- $
$ UATION ENTRY LISTS THE COLUMN NO., THE ROW NO. OF THE FIRST $
$ NON-ZERO ELEMENT AND THE FOLLOWING ELEMENTS IN THAT COLUMN. $
$ $
$ * PRESSURE MODIFIERS (WEIGHTING MATRIX) * $
$ $
$ NAME "0" FORM TIN TOUT M N
DMI WKK 0 3 1 0 80 1
$ NAME J I1 A(I1,J) A(I1+1,J) . . .
DMI WKK 1 1 1.0 THRU 80
$ $
$ * INITIAL DOWNWASHES (E.G., DUE TO INCIDENCE,TWIST OR CAMBER) * $
$ $
DMI W2GJ 0 2 1 0 40 1
DMI W2GJ 1 9 .0017453THRU 40
$ $
$ * PRESSURES (E.G., AT ZERO ANGLE OF ATTACK) * $
$ $
DMI FA2J 0 2 1 0 40 3
DMI FA2J 1 1 0.0 THRU 40
$ $
$ $
$ * * * SOLUTION SPECIFICATIONS * * * $
Main Index
CHAPTER 8 107
User Interface
$ $
$ * * AERODYNAMIC DOFS * * $
$ $
$ THE AESTAT ENTRY LISTS TRIM VARIABLES USED TO SPECIFY $
$ RIGID BODY MOTIONS. THESE AND THE CONTROL SURFACE $
$ ROTATIONS MAKE UP THE VARIABLES IN THE EQUATIONS OF $
$ MOTION. $
$ $
$ ID LABEL
AESTAT 501 ANGLEA
AESTAT 502 PITCH
AESTAT 503 URDD3
AESTAT 504 URDD5
$ $
$ * * TRIM CONDITIONS * * $
$ $
$ THE TRIM ENTRY SPECIFIES CONSTRAINTS FOR THE TRIM VARIABLES $
$ LISTED ON THE AESTAT AND AESURF ENTRIES. LISTED ARE ITS ID, $
$ THE MACH NUMBER, DYNAMIC PRESSURE AND PAIRS OF TRIM VARI- $
$ ABLES AND THEIR CONSTRAINED VALUES. THOSE THAT ARE NOT $
$ HELD FIXED MUST BE CONSTRAINED BY REACTION FORCES STIPU- $
$ LATED ON THE SUPORT ENTRY. SEE SECTION 3.5.3 OF THE THEO- $
$ RETICAL MANUAL FOR MORE DETAILS. $
$ $
$ TRIM CONDITION 1: 1 G LEVEL FLIGHT AT LOW SPEED $
$ $
$ ID MACH Q LABEL1 UX1 LABEL2 UX2 +TRM
TRIM 1 0.9 40.0 PITCH 0.0 URDD3 -1.0 +TR1
$ LABEL3 UX3
+TR1 URDD5 0.0
$ * * * $
$ TRIM CONDITION 2: 1 G LEVEL FLIGHT AT HIGH SUBSONIC SPEED $
$ $
+TR2 URDD5 0.0
$ * * * $
$ TRIM CONDITION 3: 1 G LEVEL FLIGHT AT LOW SUPERSONIC SPEED $
$ $
+TR3 URDD5 0.0
$ * * * $
ENDDATA
Main Index
Figure 8-1 Aerodynamic datasets in NH5RDB
Main Index
CHAPTER 8 109
User Interface
Figure 8-2 Aerodynamic force
Reference
MSC Nastran Quick Reference Guide
NH5RDB Data Schema 2019
Main Index
Main Index
Chapter 9: Platform Support
9 Platform Support

Supported Hardware and Operating Systems 112
Main Index
Supported Hardware and Operating Systems
Supported Hardware and Operating Systems

The MSC Nastran 2019 release is provided and certified on the following hardware/software platforms:
FORTRAN
Vendor OS Hardware Version C Version Default MPI
Linux (64-bit) RHEL 6.7 Intel Xeon Intel Intel 2017.0.5.239 Intel MPI
2017.0.5.239
RHEL 7.1 2017.0.5.249
RHEL 7.3
SuSE 11 SP4
SuSE 12 SP1
Microsoft (64-bit) Windows 7 Intel Xeon Intel Microsoft v4.0.30319 Microsoft v8.1
2017.0.5.239
Windows 10
Note:
1. Windows 10 may require installation/enabling .NET Framework 3.5. See the MSC Nastran 2019.0 Installation and
Operations Guide for details.
2. MSC Nastran 2019 RHEL 7.1 also works on RHEL 7.2 with the exception of customization using SDK.
3. MSC Nastran 2019 RHEL 6.7 does not support customization using SDK.
Software Development Kit (SDK)

The MSC Software Development Kit 2019 is required for users who want to customize MSC Nastran 2019 with features
like User Subroutines, User Defined Modules, OpenFSI, and Beam Libraries. The SDK can be downloaded separately from
the “MSC Software Development Kit” product page.
Main Index

Nastran 2019 Doc Release

Uploaded by

Copyright:

Available Formats

Nastran 2019 Doc Release

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Nastran 2019 Doc Release

Uploaded by

Copyright:

Available Formats

What are some recommended training courses for beginning MSC Nastran users?

What are some recommended training courses for beginning MSC Nastran users?

How can users quickly access the full set of MSC Nastran documentation?

How can users quickly access the full set of MSC Nastran documentation?

MSC Nastran 2019

MSC Nastran Release Guide

U.S. Patent 9,361,413

1 Overview of MSC Nastran 2019.0

Advantages of new features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3 Advanced Implicit Nonlinear (SOL 400)

4 Advanced Nonlinear Explicit (SOL 700)

SCA User Defined Services (UDS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

5 Numerical Methods and High Performance Computing

Improved performance for large Adams mnf file generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

 Preface to the MSC Nastran 2019.0 Release Guide 6

Preface to the MSC Nastran 2019.0 Release Guide

List of MSC Nastran Books

Installation and Release Guides

 Non Linear (SOL 400)

Corrected and Fixed Error List

Training and Internet Resources

MSC Nastran Documentation

MSC Nastran Documentation Requirements

Overview of MSC Nastran

Advanced Implicit Nonlinear (SOL 400)

Advanced Non linear Explicit (SOL 700)

Numerical Methods and High Performance Computing

Rforce/Grav Loads Enhancements

Advantages of new features

Different combination of RFORSET and GRAVSET for the plate model

SOL 128 Enhancements

Advantages of new features

NHRMPRM Parameters for Nonlinear frequency response analysis (SOL 128)

Var Name Type/ Default Description

This equation has (2*NHARM+1)*NDOF unknown variables.

The first term of the Jacobian  ∂-----R- is already determined.

Frequency Independent Analysis

The tangent vector is determined using following steps:

where; { T } 0,K is the tangent vector obtained at the Kth step.

Output for Multiple Harmonics

Advanced Implicit Nonlinear

Contact Model Check (2019)

Contact Model Check:

Output Geometry Adjustment of Initial Stress Free

Add SEGANGL on BCPARA (and BCAUTOP)

Add N3DSUM on NLOPRM, NLDBG

Figure 3-1 Contact Check, Distance Plot of seg-to-seg method

Sample debug output of NLOPRM,NLDBG=N3DSUM

Guidelines and Limitations

Output of Advanced Composite in Nastran Traditional Format of

Monitor Points with SOL 400 NLSTAT and NLTRAN

 MONSUMT - Linear combination of existing monitor points with moment transfer.

MONPNT1 Results of SOL 400 NLSTAT

AXIS RIGID APPLIED

MONPNT3 Results of SOL 400 NLSTAT

MONITOR POINT NAME = G1_4 SUBCASE 10 STEP 101

AXIS REST. APPLIED

MONPNT1 Results of SOL 400 NLTRAN (Component CX)

MONITOR POINT NAME = FORCE1 COMPONENT = CX GENERAL SUBCASE NO. 1

This equation has (2NHARM+1)NDOF unknown variables.