simcenter nastran 2019.1 release guide - siemens

SIEMENSSIEMENSSIEMENS

Simcenter Nastran2019.1 Release Guide

Contents

Proprietary & Restricted Rights Notice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Simcenter Nastran 2019.1 summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Summary of changes to default settings and inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Total ERP results output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1Support for visualization elements in ERP calculations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3Extrapolation options for TABLED bulk entries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9Random analysis enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-24Frequency-dependent enforced motions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-28Limiting frequency response output to peak responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-34

Acoustics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Frequency-dependent dynamic forces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1Acoustic Transfer Vector (ATV) improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Vibro-Acoustic Transfer Vector (VATV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-15Surface dipole acoustic source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20Finite Element Method Adaptive Order (FEMAO) enhancements . . . . . . . . . . . . . . . . . . . . . 3-24Coupled FEMAO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32Duct modes boundary condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35Fan noise boundary condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47AML support for fluid damping coefficient . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-51Support for visualization elements in structure-acoustic interface . . . . . . . . . . . . . . . . . . . . . 3-52Peak acoustic response output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52Spatially varying fluid properties in acoustic analysis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52Acoustic matrix output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-57

Rotor dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Assigning mass properties to bearing elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Superelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Results recovery for external superelements using the mode acceleration method . . . . . . . . . . 5-1Structural damping in external superelements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

WMODAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-12

Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Quadratic thickness plane stress elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1Support for non-structural mass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Multi-step nonlinear solution 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Simcenter Nastran 2019.1 Release Guide 3

Contents

Transient dynamic subcase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1Restarts in SOL 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-10Support for plasticity and creep in bars and beams . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-13Contact improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-14Output for preload and constant time static subcases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-17Element addition and removal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-18Chocking element improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-30Load control option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-31Bolt preload improvements in SOL 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-32New transverse shear stress formulation for composite shell elements . . . . . . . . . . . . . . . . . 7-32Support for non-structural mass in SOL 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33Support for PCOMP and PCOMPG in SOL 401 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-33Reformulated shell elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-45

K6ROT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-47

Multi-step nonlinear kinematics solution 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Multi-step nonlinear kinematics SOL 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1Kinematic joints in SOL 402 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

SMP parallelization of element matrix assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1RDMODES improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Frequency response performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Bolt preload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Bolt preload improvements for linear solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Design objective improvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1Topology optimization improvements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-6

Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

New VKI element iterative solver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1Open contact stiffness for linear solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Edge loads that vary quadratically . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2Element geometry checks in the .rcf file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Documentation changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Removing documentation for AGGPCH parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Removing documentation for RANCPLX parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Upward compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1

Updated data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1CASECC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1CONTACT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-3DIT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-5DYNAMIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-8

4 Simcenter Nastran 2019.1 Release Guide

Contents

Contents

EPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-15GEOM1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18GEOM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-18GEOM3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-19GEOM4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-20GEOM4705 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22MPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-22OBC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-23OBG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-24OBOLT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-24OCKGAP1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25OCONST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25ODAMGCZD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-25ODAMGCZR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-26ODAMGCZT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-26ODAMGPFD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-26ODAMGPFE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-27ODAMGPFR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-27ODAMGPFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28OEF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28OERR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-28OES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-29OGF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-98OJINT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-99OPG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-99OPRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-99OQG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-100OSLIDE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-100OSPDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-100OTEMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-101OUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-101OUMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-101

New data blocks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-103OACPERF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-103ODMTRCOE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-104ODMTRLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-106OELAR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-107RST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-108VATVMAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-110

Updated modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-111BDRYINFO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-111CONSTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-111CONTOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-112DOPR1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-112DOPR3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-113DSAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-113DSAF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-114DSAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-115EMG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-115


Contents

Contents

FEMAOAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-115FEMAOPRE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-116FEMAOPST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-117FOCOEL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-117FONOTR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-117FRFIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-118FRLG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-118FRLGAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-118FRLGEN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-119GP3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-119GPAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-119GPACAO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-120GPFDR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-120INPUTT4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-121MODACC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-121NLTRD3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-121RANDOM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-123SDR2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-124SSG1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-124TEMPATT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-125TOLAPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-125VDRPC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-125

New modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-126ELAREXTF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-126ELARNOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-126ELART . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-127MODGMC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-127MODGM3LD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-128MODGVATV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-129NUMOP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-129PEAKOUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-130RDTSTEP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-133RSTWRT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-133SPCDFILE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-135TEMPFRIC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-135VATVLOAD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-136VATVMAT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-137

Problem Report (PR) fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Problem Report (PR) fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1

Default and input changes for past releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1

NX Nastran 12 summary of changes to default settings and inputs . . . . . . . . . . . . . . . . . . . . 16-1NX Nastran 11 summary of changes to default settings and inputs . . . . . . . . . . . . . . . . . . . . 16-7NX Nastran 10 summary of changes to default settings and inputs . . . . . . . . . . . . . . . . . . . 16-14


Contents

Proprietary & Restricted Rights Notice

© 2019 Siemens Product Lifecycle Management Software Inc. All Rights Reserved.

This software and related documentation are proprietary to Siemens Product Lifecycle ManagementSoftware Inc. Siemens and the Siemens logo are registered trademarks of Siemens AG. Simcenter3D is a trademark or registered trademark of Siemens Product Lifecycle Management Software Inc.or its subsidiaries in the United States and in other countries.

NASTRAN is a registered trademark of the National Aeronautics and Space Administration.Simcenter Nastran is an enhanced proprietary version developed and maintained by SiemensProduct Lifecycle Management Software Inc.

MSC is a registered trademark of MSC.Software Corporation. MSC.Nastran and MSC.Patran aretrademarks of MSC.Software Corporation.

All other trademarks are the property of their respective owners.

TAUCS Copyright and License

TAUCS Version 2.0, November 29, 2001. Copyright (c) 2001, 2002, 2003 by Sivan Toledo, Tel-AvivUniversity, [email protected]. All Rights Reserved.

TAUCS License:

Your use or distribution of TAUCS or any derivative code implies that you agree to this License.

THIS MATERIAL IS PROVIDED AS IS, WITH ABSOLUTELY NO WARRANTY EXPRESSED ORIMPLIED. ANY USE IS AT YOUR OWN RISK.

Permission is hereby granted to use or copy this program, provided that the Copyright, this License,and the Availability of the original version is retained on all copies. User documentation of any codethat uses this code or any derivative code must cite the Copyright, this License, the Availability note,and "Used by permission." If this code or any derivative code is accessible from within MATLAB, thentyping "help taucs" must cite the Copyright, and "type taucs" must also cite this License and theAvailability note. Permission to modify the code and to distribute modified code is granted, providedthe Copyright, this License, and the Availability note are retained, and a notice that the code wasmodified is included. This software is provided to you free of charge.

Availability (TAUCS)

As of version 2.1, we distribute the code in 4 formats: zip and tarred-gzipped (tgz), with or withoutbinaries for external libraries. The bundled external libraries should allow you to build the testprograms on Linux, Windows, and MacOS X without installing additional software. We recommendthat you download the full distributions, and then perhaps replace the bundled libraries by higherperformance ones (e.g., with a BLAS library that is specifically optimized for your machine). If youwant to conserve bandwidth and you want to install the required libraries yourself, download thelean distributions. The zip and tgz files are identical, except that on Linux, Unix, and MacOS,unpacking the tgz file ensures that the configure script is marked as executable (unpack with tarzxvpf), otherwise you will have to change its permissions manually.



HDF5 (Hierarchical Data Format 5) Software Library and Utilities Copyright 2006-2016 byThe HDF Group

NCSA HDF5 (Hierarchical Data Format 5) Software Library and Utilities Copyright 1998-2006 by theBoard of Trustees of the University of Illinois. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted for anypurpose (including commercial purposes) provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this list of conditions,and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions,and the following disclaimer in the documentation and/or materials provided with the distribution.

3. In addition, redistributions of modified forms of the source or binary code must carry prominentnotices stating that the original code was changed and the date of the change.

4. All publications or advertising materials mentioning features or use of this software are asked,but not required, to acknowledge that it was developed by The HDF Group and by the NationalCenter for Supercomputing Applications at the University of Illinois at Urbana-Champaign andcredit the contributors.

5. Neither the name of The HDF Group, the name of the University, nor the name of any Contributormay be used to endorse or promote products derived from this software without specific priorwritten permission from The HDF Group, the University, or the Contributor, respectively.

DISCLAIMER: THIS SOFTWARE IS PROVIDED BY THE HDF GROUP AND THE CONTRIBUTORS"AS IS" WITH NO WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED.

In no event shall The HDF Group or the Contributors be liable for any damages suffered by the usersarising out of the use of this software, even if advised of the possibility of such damage



Chapter 1: Simcenter Nastran 2019.1 summary of changes

Summary of changes to default settings and inputs

Default setting changes

Note

The following table lists changes to default settings that may produce differences in resultsbetween NX Nastran 12 and Simcenter Nastran 2019.1. Default setting changes thatproduce additional output only are not included in this table.

Input type Default changesKeywords None

Nastran statement

SYSTEM(399)=YES is still the default. However, the default elementiterative solver is changed from the CASI element iterative solver to theVKI element iterative solver. To request the CASI element iterative solver,specify SYSTEM(399)=2.

File managementstatements NoneExecutive controlstatements NoneCase controlcommands None

ParametersFZERO changed from 1.0E-3 to 1.0E-1.

MPCZERO changed from 1.0E-7 to 1.0E-11

Bulk entries The default for the minimum adaptive order number on the ACORDER entrychanged from 1 to 2.

Keyword changes

No changes to keywords.

Nastran statement changes

Systemcell

System cellname System cell description Description of change

399 ELEMITER Controls element iterative solver.

SYSTEM(399)=YES is still the default.However, the default element iterativesolver is changed from the CASIelement iterative solver to the VKIelement iterative solver. To requestthe CASI element iterative solver,specify SYSTEM(399)=2.

Simcenter Nastran 2019.1 Release Guide 1-1


Systemcell


495Determines if a shell elementthickness value of 0.0 causes a fatalerror.

SYSTEM(495) no longer applies toCPLSTS3, CPLSTS4, CPLSTS6, andCPLSTS8 elements.

625 Requests the FRRUD3 method forSOL 111. New system cell

693 Requests the solver for SOLs 108and 111. New system cell

707 Controls element matrix assemblymethod. New system cell

715 Controls transverse shear formulationfor composite shells in SOL 401. New system cell

721

Specifies the extrapolation option thatthe software uses for all TABLEDi (i =1, 2, 3, and 6) bulk entries in the inputfile.

New system cell

File management statement changes

File managementstatement

File management statementdescription Description of change

ASSIGN

Assigns physical file names to DBsetmembers, special FORTRAN files thatare used by other FMS statements orDMAP modules, or HDF5 files.

Added SC_H5 describer for readingof files in HDF5 format.

Executive control statement changes

No changes to executive control statements.

Case control command changes

Case controlcommand Case control command description Description of change

ACCELERATION Requests form and type ofacceleration vector output. Added the SOLUTION describer.

ACTEMPSelects spatially-varying intensiveproperties for the fluid in standardFEM and FEMAO acoustic analysis.

New case control command

ANALYSIS Specifies the type of analysis beingperformed for the current subcase.

Added DYNAMICS for SOL 401.

Added CEIG for SOL 402.

1-2 Simcenter Nastran 2019.1 Release Guide


Simcenter Nastran 2019.1 summary of changes


DESOBJSelects the DRESP1, DRESP2, orDRESP3 entry to be used as thedesign objective.

Describers are added to:

• Resolve any DRESP1 responsetype from static, normal mode, orlinear buckling subcases into asingle value.

• Resolve responses acrossmultiple subcases.

• Resolve responses from multiplegrid points or elements such asdisplacement or stress.

DISPLACEMENT Requests form and type ofdisplacement vector output. Added the SOLUTION describer.

DMTRCOEF Requests the duct modestransmission coefficients. New case control command

DMTRLOSS Requests the duct modestransmission loss output. New case control command

ELAR Selects the element add/removal set. New case control command

ERPRequests equivalent radiated power(ERP) calculation and controls ERPoutput.

ERP totals are now output for panels.

PLOTEL3, PLOTEL4, PLOTEL6, andPLOTEL8 visualization elements arenow supported for ERP calculationsand output.

EXTSEOUTSpecifies the various requirementsfor the creation of an externalsuperelement.

Added the ability to create outputtransformation matrices using themode acceleration method.

PLOTEL, PLOTEL3, PLOTEL4,PLOTEL6, PLOTEL8, PLOTHEX,PLOTTET, PLOTPEN, and PLOTPYRvisualization elements are nowsupported for output.

FLXRESULTS Requests flexible slider joint outputfor SOL 402. New case control command

FLXSLI Selects an external flexible sliders setfor SOL 402. New case control command

GPFORCE Requests grid point force balance atselected grid points. Added the SOLUTION describer.

GRDCON

Requests the form and type ofacoustic contribution output for thegrids of structural panels and for theresidual.

Added the SOLUTION = PEAKOUTdescriber setting.

JCONSET Selects an external kinematic jointconstraint set for SOL 402. New case control command

JRESULTS Requests output for kinematic jointsin SOL 402. New case control command





MODCON Requests the form and type of modalcontribution output for the residual.


PANCONRequests the form and type ofacoustic contribution output forstructural panels and the residual.


PEAKOUTRequests response peak output forSOL 108 and 111 frequency responseanalysis.


PRESSURE Requests the form and type ofpressure output for fluid grid points. Added the SOLUTION describer.

RANDOMSelects the RANDPS and RANDT1bulk entries to be used in randomanalysis.

Removed RANCPLX describer.

Added the RMSINT describer, whichspecifies the interpolation method forthe numerical integration.

RANDPEX bulk entry is supported.

SETMC Defines sets for modal, panel, andgrid contribution results. Added acoustic power RTYPE.

VATVOUTDefines requirements for the creationof a vibro-acoustic transfer vector(VATV).


VELOCITY Requests form and type of velocityvector output. Added the SOLUTION describer.

Parameter changes

Parameter Parameter description Description of change

AGGPCH Requests output of the fluid-structurecoupling matrix. Undocumented

DUCTFMAX Defines the maximum duct modefrequency New parameter

GFLSpecifies the uniform fluid-dampingcoefficient in the formulation ofdynamics problems.

GFL is now supported by the FEMAdaptive Order (FEMAO) method.

K6ROTSpecifies the stiffness to be addedto the normal rotation for some shellelements.

K6ROT can now be used withCQUAD8 and CTRIA6 elementswhen the solution sequence is SOL401 or 402.

RANCPLX Specifies whether the format forrandom output is real or complex. Undocumented

RDQSOL Requests the eigenvalue problemmethod for RDMODES New parameter

WMODAL

Specifies a structural-to-viscousdamping conversion method thatuses the solved modal frequencies asconversion factors.

WMODAL can now be used to convertstructural damping in an externalsuperelement to viscous damping.




Degree-of-freedom set changes

No changes to degree-of-freedom sets.

Bulk entry changes

Bulk entry Bulk entry description Description of changeACDUCT Defines an acoustic duct mode. New bulk entry

ACFAN Defines fan noise for a frequencyresponse analysis. New bulk entry

ACNDUCT Defines an acoustic anechoic endduct. New bulk entry

ACORDER Defines the polynomial order for theFEMAO method.

Updated to reflect the new defaultvalue for the minimum adaptive ordernumber.

ACSPO2Defines a surface dipole from anexternal sc_h5 file in HDF5 format foruse in a frequency response analysis.

New bulk entry

ACTEMP

Retrieves from an external filespatially-varying intensive propertydata for fluids in standard FEM andFEMAO acoustic analysis.

New bulk entry

AMLREG Defines an automatically matchedlayer region for acoustic analysis.

AMLREG is now supported by theFEM Adaptive Order (FEMAO)method.

BCTPARM Contact parametersNew parameters. See descriptions inthe SOL 401 contact improvementssection for details.

CJOINT Defines a kinematic joint connection. New bulk entry

CPLSTS6 Defines a plane stress triangularelement.

Added quadratic thickness variationcapability.

CPLSTS8 Defines a plane stress quadrilateralelement.

Added quadratic thickness variationcapability.

CQUAD8Defines a curved quadrilateral shellor plane strain element with eight gridpoints.

Updated to reflect different elementformulation for SOLs 401 and 402.

CTRIA6Defines a curved triangular shell orplane strain element with six gridpoints.

Updated to reflect different elementformulation for SOLs 401 and 402.

DESCDefines a description for kinematicjoints in SOL 402 and acousticdefinitions in SOL 108.

New bulk entry

DRIVER Defines a driver load or enforceddisplacement on kinematic joints. New bulk entry

DTI,DISTL

The use of this bulk entry by theRLOADEX and RANDPEX bulkentries is temporary. Its use will bereplaced with a new File ManagementSystem (FMS) command, whosedesign is yet to be determined.

New bulk entry




Bulk entry Bulk entry description Description of change

ELAR Defines the addition and removal ofelements. New bulk entry

ELAR2 Defines the addition and removal ofelements. New bulk entry

ELARADDDefines an element add/remove setas a union of ELAR and ELAR2 bulkentries.

New bulk entry

FLXADDDefines a flexible slider set as a unionof single flexible sliders defined onFLXSLI entries.

New bulk entry

FLXSLI Defines a flexible slider. New bulk entry

FREQH Defines harmonics andsub-harmonics for fan noise. New bulk entry

FREQVDefines frequency range of interestfor a vibro-acoustic transfer vector(VATV) response analysis.

New bulk entry

JCON Defines fixation times or liberationtimes for kinematic joints. New bulk entry

JCONADD

Defines a kinematic joint constraintset as a union of single kinematicjoint constraint sets defined on JCONentries.

New bulk entry

NLCNTL Parameters for SOL 401 New parameters. See descriptions inthe SOL 401 sections for details.

NLCNTLG Parameters for SOL 401 and 402 New parameters. See descriptions inthe SOL 401 sections for details.

NSM Defines non-structural mass PCOMPG1 and PPLANE are nowsupported.

NSM1 Defines non-structural mass PCOMPG1 and PPLANE are nowsupported.

NSML Defines lumped non-structural mass PCOMPG1 and PPLANE are nowsupported.

NSML1 Defines lumped non-structural mass PCOMPG1 and PPLANE are nowsupported.

PACDUCT Defines the cross sectional propertiesfor an acoustics duct mode. New bulk entry

PACFAN Defines the properties of fan noisefrequency analysis. New bulk entry

PACSPO2Defines the properties of a surfacedipole for a frequency responseanalysis.

New bulk entry

PBEAR Defines bearing properties for rotordynamic analysis.

Added the ability to assign massproperties to PBEAR elements.

PCOMP Defines the properties of layeredcomposite elements.

PCOMP is now supported in SOL401.

PCOMPGDefines the properties of layeredcomposite elements with global plyIDs.

PCOMPG is now supported in SOL401.





PCOMPG1

Defines the properties of an n-plycomposite material laminate whichincludes global ply IDs for SOLs 401and 402.

MIDs can now reference MAT1,MAT2, MAT8, MAT9, or MAT11 bulkentries.

PEAKOUT

Specifies the criteria that are usedto filter the peak responses from allthe resonances in SOL 108 and 111frequency response analysis results.

New bulk entry

PJOINT Defines properties for kinematic joints. New bulk entry

PJOINT2 Defines spring and/or damperproperties for the kinematic joint. New bulk entry

PLOADE1Defines a surface traction that actsalong the edge of plane stress andplane strain elements.

Added quadratic load distributioncapability.

PSOLID Defines the properties of solidelements.

Added FCTN = PFLUIDEX option toreference an external file that containsthe fluid properties.

RANDPEXReferences a PSD specification froman external sc_h5 file in HDF5 formatfor use in a random analysis.

New bulk entry

RLOAD1Defines a frequency-dependentdynamic load for use in frequencyresponse problems.

SPCF is now supported.

RLOADEXDefines frequency-dependentdynamic forces obtained from a file foruse in frequency response problems.

New bulk entry

SPCF

Defines enforced displacementon structural grid points for afrequency response analysis usingfrequency-dependent displacementresults stored in an .op2 file.

New bulk entry

TABLED1 Defines a tabular function with a realindependent and dependent domains.

Added user-specified table lookup forvalues outside the range of tabulardata.





TABLED6Defines a tabular function with a realindependent domain and a complexdependent domain.


VATVBK

Defines the Fortran unit numberfor the ASSIGN INPUTT2 file thatcontains the vibro-acoustic transfervector (VATV) results to be used in aVATV response analysis.

New bulk entry





VATVFS

Defines the structural surfacesof a pressure boundary for thevibro-acoustic transfer vector (VATV)calculation.

New bulk entry



Chapter 2: Dynamics

Total ERP results outputEquivalent radiated power (ERP) output for panels now includes totals. How the software computessome of the totals depends on the whether the output is SORT1 or SORT2.

The following SORT1 and SORT2 output are from a model where the ERP case control commandspecifies output for three panels and two forcing frequencies.

SORT1

FREQUENCY = 3.000000E+03EQUIVALENT RADIATED POWER

PANEL NAME ERP FRACTION NORMAL AREA ERP DENSITYPANEL3 1.491040E+11 4.901360E-01 3.000000E+04 4.970134E+06PANEL1 1.392054E+11 4.575974E-01 1.250000E+04 1.113644E+07PANEL2 1.590001E+10 5.226666E-02 1.750000E+04 9.085721E+05TOTAL 3.042095E+11 1.000000E+00 6.000000E+04 5.070158E+06



For an individual panel at each frequency, the values are calculated as follows:

• For the FRACTION column, the values are the ERP values for the panels normalized with respectto the total ERP for all the panels listed in the output. For example, the fraction of the total ERP ata frequency of 3000 for Panel 3 is 1.491040 x 1011 / 3.042095 x 1011 = 4.901360 x 10-1.

• For the ERP DENSITY column, the values are the ERP value for the panel normalized withrespect to the normal area value for the panel. For example, the ERP density at a frequency of3000 for Panel 3 is 1.491040 x 1011 / 3.000000 x 104 = 4.970134 x 106.

In the TOTAL row at each frequency, the values are calculated as follows:

• For the ERP, FRACTION, and NORMAL AREA columns, the values are the sums of the valuesin the corresponding column. For example, the total ERP at a frequency of 3000 is 1.491040 x1011 + 1.392054 x 1011 + 1.590001 x 1010 = 3.042095 x 1011.

• For the ERP DENSITY column, the value is the total ERP value normalized with respect to thetotal normal area value. For example, the ERP density at a frequency of 3000 is 3.042095 x 1011/ 6.000000 x 104 = 5.070158 x 106.


Chapter 2: Dynamics

SORT2

PANEL=PANEL3(AREA=3.000000E+04 ERP. MAXIMUM=1.491040E+11)EQUIVALENT RADIATED POWER

FREQUENCY ERP FRACTION ERP DENSITY3.000000E+03 1.491040E+11 8.883273E-01 4.970134E+064.000000E+03 1.874405E+10 1.116727E-01 6.248018E+05





PANEL=TOTAL (AREA=6.000000E+04 ERP. MAXIMUM=1.590001E+10)EQUIVALENT RADIATED POWER


In a section for an individual panel such as the PANEL = PANEL1 section, the values are calculatedas follows:

• For the FRACTION column, the values are the ERP values at a given frequency normalized withrespect to the sum of the ERP values for the panel at all the frequencies listed in the output. Forexample, the fraction value for Panel 3 for a frequency of 3000 is 1.491040 x 1011 / (1.491040 x1011 + 1.874405 x 1010) = 8.883273 x 10-1.

• For the ERP DENSITY column, the values are the ERP values normalized with respect to thecorresponding normal area values. For example, the ERP density at a frequency of 3000 forPanel 3 is 1.491040 x 1011 / 3.000000 x 104 = 4.970134 x 106.

In the "PANEL = TOTAL" section, the values are calculated as follows:

• For the ERP column, the values are the sums of the ERP values for each of the panels listed inthe output at the corresponding frequencies. For example, the total ERP at a frequency of 3000is 1.491040 x 1011 + 1.392054 x 1011 + 1.590001 x 1010 = 3.042095 x 1011.

• For the ERP DENSITY column, the values are the total ERP values normalized with respect tothe total normal area. For example, the ERP density at a frequency of 3000 is 3.042095 x 1011 /6.000000 x 104 = 5.070158 x 106.

• For the FRACTION column, the values are the total ERP values normalized with respect to thesum of the total ERP for each frequency listed in the output. For example, the fraction of thetotal ERP at a frequency of 3000 is 3.042095 x 1011 / (3.042095 x 1011 + 3.850434 x 1010) =8.876487 x 10-1.

For more information, see ERP.


Chapter 2: Dynamics

Dynamics

Support for visualization elements in ERP calculationsThe software now supports PLOTEL3, PLOTEL4, PLOTEL6, and PLOTEL8 visualization elements inequivalent radiated power (ERP) calculations. With this capability, you can obtain ERP results for theexterior surfaces of solid elements by applying a surface coat of visualization elements. Because thevisualization elements do not contribute mass, damping, or stiffness to the model, they inherit theirmotion directly from the underlying solid elements.

For example, suppose that you want to calculate the ERP for an internal combustion engine that ismodeled with solid elements. To do so, you can:

1. Surface coat the exterior surfaces of the engine model with visualization elements.

2. Create panels from the visualization elements.

When you create panels from the visualization elements, you treat them as if they are shellelements.

3. Use the ERP case control command to trigger the ERP calculation.

With the ERP case control command, you can also select the panels for which to output ERP resultsand specify the formatting options for the ERP output.

In previous versions of the software, you are limited to performing ERP calculations for CQUAD4,CQUAD8, CQUADR, CTRIA3, CTRIA6, and CTRIAR shell elements.


Dynamics

Chapter 2: Dynamics

ERP

Requests Equivalent Radiated Power Output

Requests equivalent radiated power output for selected panels and the shell orvisualization elements that comprise the selected panels in frequency responseanalysis, and in the equivalent ANALYSIS=DFREQ or ANALYSIS=MFREQ optionswith SOL 200.

FORMAT:

EXAMPLES:ERP(PRINT,SOLUTION=53,ERPCOEFF=0.75)=55

DESCRIBERS:

Describer Meaning

SORT1 Output equivalent radiated power results as a tabular listing ateach forcing frequency. See Remarks 3 and 4. (Default)

SORT2 Output equivalent radiated power results as a tabular listingfor each panel. See Remarks 3 and 5.

PRINT Write output to the print file. (Default)

PUNCH Write output to the punch file.

PLOT Do not write ERP data to either the print or punch file.

SOLUTION = ALL Calculate equivalent radiated power at all frequenciesspecified by FREQUENCY case control commands. (Default)

SOLUTION = setf Calculate equivalent radiated power at all frequenciesspecified by a SET case control command having theidentification number setf. (Integer > 0)

ERPCOEFF = c Coefficient used to scale the equivalent radiated power. SeeRemark 3. (Real > 0.0; Default = 1.0)


Chapter 2: Dynamics

Dynamics

Describer Meaning

ELEMOUT = YES Output equivalent radiated power by element for elements thatcomprise the selected panels. See Remarks 6, 7, and 8.

ELEMOUT = NO Do not output equivalent radiated power by element forelements that comprise the selected panels. (Default)

ALL Output equivalent radiated power for all panels.

setp Output equivalent radiated power for selected panels.

setp selects the set identification of a previously appearingSET case control command. The SET command lists thenames (character entry) of panels defined on a PANEL bulkentry. The SET command must be specified in the samesubcase as the ERP command or above all subcases. ForERP output requests, the panels defined on the PANEL bulkentry must reference SET3 bulk entries only. (Integer > 0)

NONE Do not output equivalent radiated power.

REMARKS:1. Equivalent radiated power calculation is supported for CQUAD4, CQUAD8,

CQUADR, CTRIA3, CTRIA6, and CTRIAR shell elements, and the PLOTEL3,PLOTEL4, PLOTEL6, and PLOTEL8 visualization elements.

2. ERP output is supported in SOL 108 and 111, and in the equivalentANALYSIS=DFREQ or ANALYSIS=MFREQ options with solution 200. You canrequest ERP output for models that contain structural elements only, or modelsthat include both structural and fluid elements.

3. The equivalent radiated power attributable to the ith element at frequency ωk isgiven by:

where:

c is the scaling coefficient specified with the ERPCOEFF describer, which isusually taken to be the product of density and speed of sound in the fluidmedium.

is the normal velocity as a function of position, , at frequency ωk.

Frequencies ωk are specified by the SOLUTION describer.

is the complex conjugate of .

Si is the surface area of the ith element.


Dynamics

Chapter 2: Dynamics

The equivalent radiated power density for the ith element at frequency ωk isgiven by:

The equivalent radiated power for the jth panel at frequency ωk is the sum of theequivalent radiated power for each element comprising the jth panel at frequencyωk and is given by:

The equivalent radiated power density for the jth panel at frequency ωk and isgiven by:

where Aj is the surface area of the jth panel.

When the SORT1 (default) describer is specified, the values in the "FRACTION"column represent the fraction of the total equivalent radiated power for all selectedpanels that is attributable to the jth panel at frequency ωk. These values arecomputed as follows:

where M is the total number of selected panels.

The output is then grouped according to frequency and sorted by panel indescending order of equivalent radiated power.

For a given frequency, the value for equivalent radiated power density in the"TOTAL" row is the ratio of the total equivalent radiated power for all the selectedpanels at that frequency to the total area of those panels.

When the SORT2 describer is specified, for an individual panel, the values in the"FRACTION" column represent the fraction of the total equivalent radiated powerfor all frequencies that is attributable to the jth panel at frequency ωk. These valuesare computed as follows:

where N is the total number of frequencies specified by the SOLUTION describer.

In the "PANEL=TOTAL" section of the SORT2 results, the values in the"FRACTION" column represent the fraction of the total equivalent radiated powerfor all panels at all frequencies that is attributable to all the panels at frequency ωk.These values are computed as follows:


Chapter 2: Dynamics

Dynamics

4. The following sample of SORT1 output for panels is from a model with threepanels selected for output and two forcing frequencies.





5. The following sample of SORT2 output for panels is from a model with threepanels selected for output and two forcing frequencies.







PANEL=TOTAL (AREA=6.000000E+04 ERP. MAXIMUM=1.590001E+10)EQUIVALENT RADIATED POWER


6. Only absolute equivalent radiated power values are available for element output.


Dynamics

Chapter 2: Dynamics

7. The following sample of SORT1 output for elements is from a model wherethe panels selected for output are constructed from PLOTEL3 and PLOTEL4elements, and there are two forcing frequencies.

FREQUENCY = 3.000000E+03ELEMENT EQUIVALENT RADIATED POWER (PLOTEL3)

ELEMENT ID ERP ERP DENSITY5 2.196778E+10 1.757423E+076 3.317672E+10 2.654138E+0729 3.317672E+10 2.654138E+07


ELEMENT ID ERP ERP DENSITY2 8.997186E+09 3.598874E+0614 7.782757E+06 3.113103E+0325 3.932071E+06 1.572828E+0328 3.932071E+06 1.572828E+03


ELEMENT ID ERP ERP DENSITY5 2.744031E+09 2.195225E+066 4.020963E+09 3.216771E+0629 4.020963E+09 3.216771E+06


ELEMENT ID ERP ERP DENSITY2 1.214752E+09 4.859006E+0514 6.009078E+05 2.403631E+0225 2.783943E+06 1.113577E+0328 2.783943E+06 1.113577E+03

8. The following sample of SORT2 output for elements is from a model wherethe panels selected for output are constructed from PLOTEL3 and PLOTEL4elements, and there are two forcing frequencies.

ELEMENT ID = 5ELEMENT EQUIVALENT RADIATED POWER (PLOTEL3)

FREQUENCY ERP ERP DENSITY3.000000E+03 2.196778E+10 1.757423E+074.000000E+03 2.744031E+09 2.195225E+06






Chapter 2: Dynamics

Dynamics









Extrapolation options for TABLED bulk entriesWhen specifying dynamic loads with the TABLED1, TABLED2, TABLED3, and TABLED6 bulk entries,you can now specify the values that the software uses for the table lookup when the lookup pointlies outside the range of tabular data.

In previous versions, the table lookup for points outside the range of tabular data is limited to thefollowing two options:

• Linearly extrapolating the two starting and two ending data points for the table lookup.

• Using the values for the dependent variable at the starting and ending data points as the valuesfor the table lookup.

To use the new extrapolation option with the TABLED1, TABLED2, or TABLED3 bulk entry, do thefollowing:

• Specify EXTRAP = 2.

• In the LOEXT field, specify the table lookup when the lookup point lies below the range of tabulardata.

• In the HIEXT field, specify the table lookup when the lookup point lies above the range of tabulardata.

The procedure to use the new extrapolation option with the TABLED6 bulk entry is the same exceptthat you must specify both parts of the complex dependent variable. Thus, you do the following:

• Specify EXTRAP = 2.


Dynamics

Chapter 2: Dynamics

• In the ULOEXT and VLOEXT fields, specify the table lookup when the lookup point lies belowthe range of tabular data.

o If TYPE = RI, ULOEXT is the real part and VLOEXT is the imaginary part of the complextable lookup.

o If TYPE = MP, ULOEXT is the magnitude and VLOEXT is the phase of the complex tablelookup.

• In the UHIEXT and VHIEXT fields, specify the table lookup when the lookup point lies abovethe range of tabular data.

o If TYPE = RI, UHIEXT is the real part and VHIEXT is the imaginary part of the complextable lookup.

o If TYPE = MP, UHIEXT is the magnitude and VHIEXT is the phase of the complex tablelookup.

The default for the LOEXT, HIEXT, ULOEXT, VLOEXT, UHIEXT, and VHIEXT fields is 0.0. Thus,if you specify EXTRAP = 2 and leave one of these fields blank, the software uses 0.0 as the tablelookup for the field you left blank.

For models that contain multiple TABLEDi (i = 1, 2, 3, and 6) bulk entries, you can now use systemcell 721 to override the individual extrapolation option settings.

• To set the extrapolation option for all of the TABLEDi (i = 1, 2, 3, and 6) bulk entries to EXTRAP= 1, specifying SYSTEM(721) = 1.

• To set the extrapolation option for all of the TABLEDi (i = 1, 2, 3, and 6) bulk entries to EXTRAP= 2, specifying SYSTEM(721) = 2.


Chapter 2: Dynamics

Dynamics

TABLED1

Dynamic Load Tabular Function, Form 1

Defines a tabular function for use in generating frequency-dependent andtime-dependent dynamic loads.

FORMAT:

1 2 3 4 5 6 7 8 9 10TABLED1 TID XAXIS YAXIS EXTRAP LOEXT HIEXT

x1 y1 x2 y2 x3 y3 -etc.- “ENDT”

EXAMPLE:

TABLED1 32 1

-3.0 6.9 2.0 5.6 3.0 5.6 ENDT

FIELDS:

Field Contents

TID Table identification number. (Integer > 0)

XAXIS,YAXIS

Specifies whether the interpolation is linear in Cartesian, semi-log, orlog-log space. See Remark 9. (Character: “LINEAR” or “LOG”; Default =“LINEAR”)

For interpolation in Cartesian space, specify XAXIS = LINEAR andYAXIS = LINEAR.

For interpolation in semi-log space, specify XAXIS = LINEAR andYAXIS = LOG, or XAXIS = LOG and YAXIS = LINEAR. See Remark7.

For interpolation in log-log space, specify XAXIS = LOG and YAXIS= LOG. See Remark 8.

EXTRAP Extrapolation option. (Integer: 0, 1, or 2; Default = 0)

If EXTRAP = 0, obtain table lookup values for x < xmin andx > xmax by applying the interpolation formula to the two starting andtwo ending data points. See Figure 2-1 and Remark 9.

If EXTRAP = 1, use the value of the table field at xmin for the tablelookup when x < xmin and use the value of the table field at xmax forthe table lookup when x > xmax.

If EXTRAP = 2, use LOEXT for the table lookup when x < xmin anduse HIEXT for the table lookup when x > xmax.

LOEXT For EXTRAP = 2, table lookup value when x < xmin. (Real; Default = 0.0)


Dynamics

Chapter 2: Dynamics

Field Contents

HIEXT For EXTRAP = 2, table lookup value when x > xmax. (Real; Default = 0.0)

xi Tabular values of the independent domain. See Remarks 2 and 5.(Real; No default)

yi Tabular values of the dependent domain. See Remark 5. (Real; Default= 0.0)

“ENDT” Flag indicating the end of the table.

REMARKS:1. No warning messages are issued if tabular data is input incorrectly.

2. The values for xi must be listed in either ascending or descending order accordingto algebraic size. Thus, the values at the starting and ending data points are eitherxmin and xmax, respectively, or xmax and xmin, respectively.

3. Discontinuities may be specified at any point except the end points. For example,in Figure 2-1, a discontinuity is not allowed between points x7 and x8. In Figure2-1, if YAXIS = LINEAR, the table lookup value at x3 is:

If YAXIS = LOG, the table lookup value at x3 is:

Figure 2-1. Example of Table Extrapolation and Discontinuity


Chapter 2: Dynamics

Dynamics

If in Figure 2-1 the discontinuity is at x2, x3, and EXTRAP = 0, the software usesdata points (x1,y1) and (x2,y2) to calculate the linear extrapolation formula.

4. At least one continuation must be specified.

5. Any data point, (xi,yi), may be ignored by placing the character string “SKIP” ineither the xi or yi field.

6. The end of the table is indicated by the existence of the character string “ENDT”in either of the two fields following the last entry. An error is detected if anycontinuations follow the entry containing the end-of-table flag “ENDT”.

7. Specify XAXIS = LINEAR and YAXIS = LOG if the tabular data approximates afunction of the form y = bemx. Because such a function plots as a straight line insemi-log space with XAXIS = LINEAR and YAXIS = LOG, fewer data points areneeded to obtain accurate interpolations.

8. Specify XAXIS = LOG and YAXIS = LOG if the tabular data approximates afunction of the form y = bxm. Because such a function plots as a straight line inlog-log space, fewer data points are needed to obtain accurate interpolations.

9. The table lookup at x returns yT(x). The formula that the software uses tointerpolate, and if EXTRAP = 0, extrapolate the tabular data for the table lookupat x depends on how the XAXIS and YAXIS fields are specified, as indicatedin Table 2-1.

Table 2-1. Interpolation formula

XAXIS YAXIS yT(x)

LINEAR LINEAR

LOG LINEAR

LINEAR LOG

LOG LOG

(xi,yi) and (xj,yj) are adjacent data points and, xi < x < xj or xi > x > xj.

10. Extrapolation is not used for Fourier transform methods. The function is zerooutside the range of the table.

11. For frequency-dependent loads, xi is measured in cycles per unit time.


Dynamics

Chapter 2: Dynamics

12. Values for xi must be positive if XAXIS = LOG, and values for yi must be positive ifYAXIS = LOG. Otherwise, the software issues a fatal message.

13. TABLED1 can be used for designed frequency-dependent properties in SOL 200 ifXAXIS = LINEAR and YAXIS = LINEAR. For frequency-dependent properties thatare not associated with design variables, TABLED1 can be used with the otheraxis options, or the other TABLEDi can be used.

REMARKSRELATED TO

SOLS 601 AND701:

1. TABLED1 is referenced by the TID field in TLOAD1 entry to model time-dependentloading. xi is therefore the time value and yi is the multiplier factor for the load.TABLED1 can also be used to define a nonlinear spring stiffness propertyreferenced by the PBUSHT, PBUSH1D and PELAST entries.

2. The XAXIS and YAXIS fields are ignored. Both axes are assumed to be "LINEAR".

3. Discontinuities are not allowed.

4. EXTRAP is ignored. When TABLED1 is used to model time-dependent loading, notable extrapolation is done beyond the range of specified xi values. Hence, therange of xi values should at least span the solution start and end times. In mostcases, x1 = 0.0 should be specified since the solution start time is usually 0.0. Thesolution end time depends on the time steps defined on the TSTEP entry.

REMARKSRELATED TO

SOL 402:1. The XAXIS and YAXIS fields are ignored. Both axes are assumed to be "LINEAR".

2. Discontinuities may be specified between any two points except the two startingpoints or two ending points. If a discontinuity is defined at x = X3 (with X3 = X4),the value of y for x = X3 is Y3. The value Y4 is used to compute y over the intervalX4 < x ≤ X5.


Chapter 2: Dynamics

Dynamics

TABLED2


Defines a tabular function for use in generating frequency-dependent andtime-dependent dynamic loads. Also contains parametric data for use with the table.

FORMAT:

1 2 3 4 5 6 7 8 9 10TABLED2 TID X1 EXTRAP LOEXT HIEXT


EXAMPLE:

TABLED2 15 -10.5 2 -5.0 7.0

1.0 -4.5 2.0 -4.2 2.0 2.8 7.0 6.5

SKIP SKIP 9.0 6.5 ENDT

FIELDS:

Field Contents


X1 Table parameter. See Remark 7. (Real)


If EXTRAP = 0, obtain table lookup values for (x - X1) < xmin and(x - X1) > xmax by linearly extrapolating the two starting and twoending data points. See Figure 2-2.

If EXTRAP = 1, use the value of the table field at xmin for thetable lookup when (x - X1) < xmin and use the value of the tablefield at xmax for the table lookup when (x - X1) > xmax.

If EXTRAP = 2, use LOEXT for the table lookup when(x - X1) < xmin and use HIEXT for the table lookup when(x - X1) > xmax.

LOEXT For EXTRAP = 2, table lookup value when (x - X1) < xmin. (Real;Default = 0.0)

HIEXT For EXTRAP = 2, table lookup value when (x - X1) > xmax. (Real;Default = 0.0)


yi Tabular values of the dependent domain. See Remark 5. (Real;Default = 0.0)



Dynamics

Chapter 2: Dynamics



3. Discontinuities may be specified at any point except the end points. For example,in Figure 2-2, a discontinuity is not allowed between points x7 and x8. If y isevaluated at a discontinuity, then the average value of y is used. In Figure 2-2, thevalue of y at x = x3 is:



4. At least one continuation entry must be specified.



7. The table lookup at x returns:


Chapter 2: Dynamics

Dynamics

The formula that the software uses to interpolate the tabular data for the tablelookup at x is:

where (xi,yi) and (xj,yj) are adjacent data points and, xi < (x - X1) < xj orxi > (x - X1) > xj.

If EXTRAP = 0, the formula that the software uses to extrapolate the tabular datafor the table lookup is the same, except that the starting two or ending two datapoints are used for (xi,yi) and (xj,yj).


9. For frequency-dependent loads, xi and X1 are measured in cycles per unit time.

REMARKSRELATED TO

SOLS 601 AND701:

1. TABLED2 is referenced by the TID field in TLOAD1 entry to model time-dependentloading. xi is therefore the time value and yi is the multiplier factor for the load.TABLED2 can also be used to define a nonlinear spring stiffness propertyreferenced by the PBUSHT, PBUSH1D and PELAST entries.

2. X1 is the delay time (or arrival time of the load), i.e., at time < X1, the load is notactive. When using X1 to control the arrival time of an enforced displacement, itis often appropriate to apply it to the deformed configuration. See the DISPOPTparameter on the NXSTRAT bulk entry for information.

3. Discontinuities are not allowed.

4. EXTRAP is ignored. When TABLED2 is used to model time-dependent loading, notable extrapolation is done beyond the range of specified xi values. Hence, therange of xi values should at least span the solution start and end times. In mostcases, x1 = 0.0 should be specified since the solution start time is usually 0.0. Thesolution end time depends on the time steps defined on the TSTEP entry.

REMARKSRELATED TO

SOL 402:1. Discontinuities may be specified between any two points except the two starting

points or two ending points. If a discontinuity is defined for x = X3 (with X3 =X4), the value of y for x = X3 is Y3. The value Y4 is used to compute y over theinterval X4 < x ≤ X5.


Dynamics

Chapter 2: Dynamics

TABLED3


Defines a tabular function for use in generating frequency-dependent andtime-dependent dynamic loads. Also contains parametric data for use with the table.

FORMAT:

1 2 3 4 5 6 7 8 9 10TABLED3 TID X1 X2 EXTRAP LOEXT HIEXT


EXAMPLE:

TABLED3 62 126.9 30.0 1

2.9 2.9 3.6 4.7 5.2 5.7 ENDT

FIELDS:

Field Contents


X1, X2 Table parameters. See Remark 7. (Real; X2 ≠ 0.0)


If EXTRAP = 0, obtain table lookup values for(x - X1) / X2 < xmin and (x - X1) / X2 > xmax by linearlyextrapolating the two starting and two ending data points. SeeFigure 2-3.

If EXTRAP = 1, use the value of the table field at xmin for thetable lookup when (x - X1) / X2 < xmin and use the value of thetable field at xmax for the table lookup when (x - X1) / X2 > xmax.

If EXTRAP = 2, use LOEXT for the table lookup when(x - X1) / X2 < xmin and use HIEXT for the table lookup when(x - X1) / X2 > xmax.

LOEXT For EXTRAP = 2, table lookup value when (x - X1) / X2 < xmin.(Real; Default = 0.0)

HIEXT For EXTRAP = 2, table lookup value when (x - X1) / X2 > xmax.(Real; Default = 0.0)


yi Tabular values of the dependent domain. See Remark 5. (Real;Default = 0.0)



Chapter 2: Dynamics

Dynamics



3. Discontinuities may be specified at any point except the end points. For example,in Figure 2-3, a discontinuity is not allowed between points x7 and x8. If y isevaluated at a discontinuity, then the average value of y is used. In Figure 2-3, thevalue of y at x = x3 is:



4. At least one continuation entry must be present.



7. The table lookup at x returns:


Dynamics

Chapter 2: Dynamics

The formula that the software uses to interpolate the tabular data for the tablelookup at x is:

where (xi,yi) and (xj,yj) are adjacent data points and, xi < (x - X1) / X2 < xj orxi > (x - X1) / X2 > xj.

If EXTRAP = 0, the formula that the software uses to extrapolate the tabular datafor the table lookup is the same, except that the starting two or ending two datapoints are used for (xi,yi) and (xj,yj).


9. For frequency-dependent loads, xi and X1 are measured in cycles per unit time.X2 is dimensionless.

REMARKSRELATED TO

SOL 402:1. Discontinuities may be specified between any two points except the two starting

points or two end points. If a discontinuity is defined for x = X3 (with X3 = X4), thevalue of y for x = X3 is Y3. The value Y4 is used to compute y over the intervalX4 < x ≤ X5.


Chapter 2: Dynamics

Dynamics

TABLED6


Defines a tabular function of the form w(x) = u(x) + iv(x) or w(x) = |u(x)|eiv(x).FORMAT:

1 2 3 4 5 6 7 8 9 10TABLED6 TID TYPE EXTRAP ULOEXT UHIEXT VLOEXT VHIEXT

x1 u1 v1 x2 u2 v2 -etc.- “ENDT”

EXAMPLE:

TABLED6 101 MP 1

10.0 2.9 16.5 20.0 5.2 93.0

30.0 4.9 132.0 40.0 4.1 108.0 ENDT

FIELDS:

Field Contents

TID Unique table identification number. See Remark 2. (Integer > 0)

TYPE Complex format of response data. (Character: RI or MP; Default= RI)

TYPE = RI for real / imaginary

TYPE = MP for magnitude / phase

EXTRAP Extrapolation option. See Remark 5. (Integer = 0, 1, or 2; Default= 0)

If EXTRAP = 0, obtain table lookup values for x < xmin andx > xmax by linearly extrapolating the two starting and twoending data points. See Figure 2-4.

If EXTRAP = 1, use the value of the table field at xmin for thetable lookup when x < xmin and use the value of the table fieldat xmax for the table lookup when x > xmax.

If EXTRAP = 2, use ULOEXT and VLOEXT for the table lookupwhen x < xmin and use UHIEXT and VHIEXT for the tablelookup when x > xmax.

ULOEXT Real part of table lookup value when x < xmin if EXTRAP = 2 andTYPE = RI. (Real; Default = 0.0)

Magnitude of table lookup value when x < xmin if EXTRAP = 2 andTYPE = MP. (Real; Default = 0.0)


Dynamics

Chapter 2: Dynamics

Field Contents

UHIEXT Real part of table lookup value when x > xmax if EXTRAP = 2 andTYPE = RI. (Real; Default = 0.0)

Magnitude of table lookup value when x > xmax if EXTRAP = 2 andTYPE = MP. (Real; Default = 0.0)

VLOEXT Imaginary part of table lookup value when x < xmin if EXTRAP = 2and TYPE = RI. (Real; Default = 0.0)

Phase of table lookup value when x < xmin if EXTRAP = 2 andTYPE = MP. (Real; Default = 0.0)

VHIEXT Imaginary part of table lookup value when x > xmax if EXTRAP = 2and TYPE = RI. (Real; Default = 0.0)

Phase of table lookup value when x > xmax if EXTRAP = 2 andTYPE = MP. (Real; Default = 0.0)


ui Real part of the dependent variable if TYPE = RI. (Real; Default =0.0)

Magnitude of the dependent variable if TYPE = MP. (Real ≥ 0.0;Default = 0.0)

vi Imaginary part of the dependent variable if TYPE = RI. (Real;Default = 0.0)

Phase of the dependent variable in degrees if TYPE = MP. (Real;Default = 0.0)



2. The TID must be unique for all TABLEDi bulk entries.


4. Discontinuities are not allowed. See Figure 2-4.


Chapter 2: Dynamics

Dynamics


5. When EXTRAP = 0, the two starting and two ending data points are linearlyextrapolated to obtain table lookup values for x < xmin and x > xmax. See Figure 2-4.

6. At least one continuation entry must be present.

7. Any (xi,ui,vi) combination may be ignored by placing the character string “SKIP” inone of the three fields.


9. TABLED6 interpolates the tabular data as follows:

a. If TYPE = RI, the tabular data is converted to magnitude and phase.

b. The magnitudes are linearly interpolated to obtain the lookup value.

c. The phase angles are linearly interpolated to obtain the lookup value. Forthis calculation the software uses the smallest subtended angle between thephase angles that are used in the interpolation calculation.

For example, suppose a TABLED6 bulk entry is defined as follows:

TABLED6 100 MP 1 +10.0 2.9 16.5 20.0 5.2 93.0 +30.0 4.9 132.0 40.0 4.1 326.0 ENDT

The lookup value for the magnitude at x = 27.5 is:


Dynamics

Chapter 2: Dynamics

The lookup value for the phase angle at x = 27.5 is:

The lookup value for the magnitude at x = 35.0 is:

At x = 35.0, the smallest subtended angle between 132.0° and 326° is 166.0°.Thus, the lookup value for the phase at x = 35.0 is:

10. For frequency-dependent loads, xi is measured in cycles per unit time.

Random analysis enhancementsThe following changes are made to the random analysis capability:

• The RANDPEX bulk entry is introduced. It allows you to reference a PSD specification from anexternal sc_h5 file in HDF5 format.

For more information, see Frequency-dependent dynamic forces.

• The RANDOM case control command is changed as follows:

o The RANCPLX describer is removed.

Random analysis in Simcenter Nastran generates real results. In previous versions, you canuse the RANCPLX describer or the RANCPLX parameter to add a zero imaginary part to thereal results. Because post-processors of Simcenter Nastran random analysis results do notsupport complex random results, adding the imaginary part is a waste of storage space. Thus,the RANCPLX capability is removed from the software, the RANCPLX describer is removedfrom the RANDOM case control command, and the RANCPLX parameter is undocumented.

o The RMSINT describer is added.

The RMSINT describer allows you to specify the interpolation method that the software usesfor numerical integration when computing the RMS value of the response and the zero-meancrossing for the RMS von Mises stress.

For more information, see RANDOM.


Chapter 2: Dynamics

Dynamics

RANDOM

Random Analysis Set Selection

Selects the RANDPS, RANDPEX, and RANDT1 bulk entries to be used in randomanalysis.

FORMAT:RANDOM[(RPOSTS1 = i,RMSINT = j,RMSSF = r)] = n

EXAMPLES:RANDOM=177RANDOM(RPOSTS1=1,RMSINT=1,RMSSF=2.0)=123

DESCRIBERS:

Describer Meaning

RPOSTS1 = i Specifies the output format for random results. (Integer; Default =0)RPOSTS1 = 0 for SORT2 output format.RPOSTS1 = 1 for SORT1 output format.

RMSINT = j Specifies the interpolation method for numerical integration whencomputing RMS response and the zero-mean crossing for theRMS von Mises stress from PSDF. (Integer; Default = 0)RMSINT = 0 for interpolation in Cartesian space.RMSINT = 1 for interpolation in log-log space.

RMSSF = r Specifies a scaling factor for RMS and CRMS random results.(Real > 0.0; Default = 1.0)

n Set identification number of RANDPS, RANDPEX, and RANDT1bulk entries to be used in random analysis. (Integer>0; No default)

REMARKS:1. RANDOM must select RANDPS or RANDPEX bulk entries to perform random

analysis.

2. If a describer is specified, it takes precedence over the corresponding parameter.

3. If RANDPS or RANDPEX bulk entries are used in a superelement analysis, theRANDOM command may be specified above the subcase level if a condensedsubcase structure (SUPER=ALL) is used. If a condensed subcase structure is notused, then a unique RANDOM selection of a unique RANDPS entry must bespecified within each of the desired superelement subcases.

4. How you organize subcases for a random analysis depends on whether youinclude ANALSIS = RANDOM in the subcases that contain the RANDOMcommand. For example, suppose that a structure is excited by two loads, and youwant to evaluate the random response of the structure for two PSD functionsusing SOL 111.

Subcase organization using ANALYSIS = RANDOM


Dynamics

Chapter 2: Dynamics

When using ANALYSIS = RANDOM in a subcase, place the subcase that containsthe ANALSIS = RANDOM and RANDOM commands after the subcases thatcalculate the frequency responses.

SUBCASE 1$$ Subcase 1 calculates the normal modes$ANALYSIS=MODESDISP=ALL$SUBCASE 2$$ Subcase 2 calculates the frequency response of the$ structure to the loading specified by DLOAD 111 at$ the frequencies specified by FREQUENCY set 13$FREQUENCY=13DLOAD=111$SUBCASE 3$$ Subcase 3 calculates the frequency response of the$ structure to the loading specified by DLOAD 211 at$ the frequencies specified by FREQUENCY set 13$FREQUENCY=13DLOAD=211$SUBCASE 4$$ Subcase 4 uses the frequency responses from Subcases$ 2 and 3 to calculate the random response of the$ structure for the PSD function specified by RANDOM 100.$ RANDOM 100 references RANDPS and RANDPEX bulk entries$ with SID 100.$ANALYSIS=RANDOMRANDOM=100$SUBCASE 5$$ Subcase 5 uses the frequency responses from Subcases$ 2 and 3 to calculate the random response of the$ structure for the PSD function specified by RANDOM 200.$ RANDOM 200 references RANDPS and RANDPEX bulk entries$ with SID 200.$ANALYSIS=RANDOMRANDOM=200

Subcase organization without using ANALYSIS = RANDOM

When not using ANALYSIS = RANDOM in a subcase, place the subcase thatcontains the RANDOM command in the first subcase that calculates a frequencyresponse. Each random spectrum requires a unique frequency identification


Chapter 2: Dynamics

Dynamics

number, even if you want to evaluate the random response over the same set offrequencies. Thus, in this example, FREQUENCY=13 and FREQUENCY=23reference FREQi bulk entries that contain the same set of frequencies.

SUBCASE 1$$ Subcase 1 calculates the normal modes$ANALYSIS=MODESDISP=ALL$SUBCASE 2$$ Subcase 2 calculates the frequency response of the$ structure to the loading specified by DLOAD 111 at$ the frequencies specified by FREQUENCY set 13 and$ requests the software calculate the random response$ of the structure for the PSD function specified by$ RANDOM 100. RANDOM 100 references RANDPS and RANDPEX$ bulk entries with SID 100.$RANDOM=100FREQUENCY=13DLOAD=111$SUBCASE 3$$ Subcase 3 calculates the frequency response of the$ structure to the loading specified by DLOAD 211 at$ the frequencies specified by FREQUENCY set 13$FREQUENCY=13DLOAD=211$SUBCASE 4$$ Subcase 4 recalculates the frequency response of the$ structure to the loading specified by DLOAD 111 at$ the frequencies specified by FREQUENCY set 23 and$ requests the software calculate the random response$ of the structure for the PSD function specified by$ RANDOM 200. RANDOM 200 references RANDPS and RANDPEX$ bulk entries with SID 200.$RANDOM=200FREQUENCY=23DLOAD=111$SUBCASE 5$$ Subcase 5 recalculates the frequency response of the$ structure to the loading specified by DLOAD 211 at$ the frequencies specified by FREQUENCY set 23$FREQUENCY=23DLOAD=211


Dynamics

Chapter 2: Dynamics

Notice that in this subcase organization, the software must recalculate thefrequency responses for each PSD function. Thus, to minimize the number ofcalculations that the software must perform, use the subcase organization thatincludes ANALYSIS = RANDOM.

Frequency-dependent enforced motionsYou can now apply a large number of frequency-dependent enforced motions on structural gridpoints. For the enforced motions, you use displacement results from an OUTPUT2 (.op2) file that wasgenerated from a previous frequency response analysis. Typically, enforced motion is used whenmotion is specified instead of, or in conjunction, with applied loads.

The displacement coordinate systems of the grids in the referenced OP2 file and grids in your currentmodel must be identical, and the subcases in the referenced OP2 file and subcases in the currentsolution must match.

This new capability is supported by SOL 108 and SOL 111 solutions with standard (fixed low-order)FEM or FEM Adaptive Order (FEMAO) method, which is a higher-order polynomial method.

Workflow for load extraction and enforced motion application:

1. Use the ASSIGN file management statement to select the OUTPUT2 file that contains thedisplacement results from a previous frequency response analysis.

2. Use the new SPCF bulk entry to specify the following:

• Identification number of the SPCF bulk entry.

• Identification number of a SET1 bulk entry that contains a list of structural grid points at whichthe loads are to be extracted and applied to for all DOFs of grids.

Note

When SET1ID is blank, the software will distribute the displacement results to allstructural grids contained in the OUTPUT2 file and apply enforced motions.

• Subcase number of displacement results in OUTPUT2 file.

Note

When OUTPUT2 file only contains one subcase, you can leave the SUBC fieldblank.

• Logical unit number that was assigned by the ASSIGN statement to the OUTPUT2 file.

3. Use the updated RLOAD1 bulk entry to reference the SPCF bulk entry.

For more information, see the new SPCF bulk entry and updated RLOAD1 bulk entry.


Chapter 2: Dynamics

Dynamics

SPCF

Enforced Displacement, File Input

Defines enforced displacement on structural grid points for a frequency responseanalysis using frequency-dependent displacement results stored in an OUTPUT2(.op2) file.

FORMAT:

1 2 3 4 5 6 7 8 9 10

SPCF SID SET1ID SUBC UNITNO

EXAMPLES:

SPCF 100 10 2 12

FIELDS:

Field Contents

SID Set identification number of the SPCF bulk entry. (Integer > 0; Nodefault) See Remark 2.

SET1ID Identification number of a SET1 bulk entry that defines a list ofstructural grids at which the loads are to be extracted and applied tofor all degrees of freedom (DOFs) of the grid. A value of 0 implies thatall structural grids contained in the OUTPUT2 file will have enforcedmotion applied. You must define corresponding SPCs in the BulkData section. (Integer ≥ 0; Default = 0) See Remark 6.

SUBC Subcase number of displacements in OUGV1 data blocks inOUTPUT2 file to be used for enforced displacements on structuralDOF. A value of 0 requests the first subcase to be used. (Integer≥ 0; Default = 0) See Remark 4.

UNITNO Logical unit number of an OUTPUT2 file that contains thefrequency-dependent OUGV1 data blocks. These data blocks will beused to define the enforced displacements on structural DOF. (Integer> 0; No default) See Remarks 3, 4, and 5.

REMARKS:1. SPCF is only supported in SOL 108 and SOL 111 with standard (fixed low-order)

FEM or FEM Adaptive Order method.

2. The SID must be unique with respect to all other SPCF, SPC, or SPCD bulkentries. The selection of SID is determined by the presence of the LOADSETrequest in the Case Control section as follows:

• If LOADSET is not present, SID is selected by the EXCITEIDID of an RLOAD1bulk entry that has enforced displacement specified in its TYPE field.


Dynamics

Chapter 2: Dynamics

• If LOADSET is present, SID is selected by LID in the selected LSEQ entriesthat correspond to the EXCITEID entry of an RLOAD1 bulk entry that hasenforced displacement specified in its TYPE field.

Note that only enforced displacements are supported; enforced velocities andenforced accelerations will be ignored.

3. An appropriate ASSIGN OUTPUT2 statement must be present in the FileManagement Section (FMS) for the value of UNITNO.

4. More than one OUGV1 data block on the OUTPUT2 file can exist and eachOUGV1 data block can contain multiple subcases. SUBC refers to the subcase IDcontained in one of these OUGV1 data blocks. If the subcase defined by SUBCcannot be found, an error will occur. If SUBC = 0, the first subcase encountered inthe first OUGV1 data block found will be used.

5. You must ensure that the enforced displacements defined in the OUGV1 datablock on the OUTPUT2 file are in the same nodal displacement coordinatesystems as the grids defined in your model.

6. The use of the SPCF bulk entry requires the use of the SPC bulk entry in the sameway as required with the use of the SPCD bulk entry.

7. Enforced displacement values contained in the selected OUGV1 data block willoverride the values specified on an SPCD bulk entry if the SID is selected asindicated above.

8. The direct method of specifying enforced displacements is more accurate, efficient,and refined than the large mass or Lagrange multiplier method.

9. Rotational DOFs are in radians.

10. If the solution frequencies are within the frequency range of the displacementsin the selected OUGV1 data block but do not match the frequencies, the solverperforms linear interpolation. If the solution frequencies are below or above thefrequency range of the displacements in the selected OUGV1 data block, thedisplacement values outside the range are assumed to be zero, and the solverdoes not extrapolate.


Chapter 2: Dynamics

Dynamics

RLOAD1

Frequency Response Dynamic Excitation, Form 1

Defines a frequency-dependent dynamic load of the form:

for use in frequency response problems.FORMAT:

1 2 3 4 5 6 7 8 9 10

RLOAD1 SID EXCITEID DELAY DPHASE TC TD TYPE

EXAMPLES:

RLOAD1 5 3 100 30.0 1

RLOAD1 5 3 0.025 4 1 10

FIELDS:

Field Contents

SID Load set identification number. (Integer > 0)

EXCITEID Identification number of the DAREA, SPCD, SPCF, SELOAD bulkentries, static load set, or thermal load set (for heat transfer analysis)that lists each degree of freedom to apply the excitation and thecorresponding scale factor, A, for the excitation. See Remarks 7 and8. (Integer > 0)

DELAY Time delay, τ. (Real or Integer ≥ 0 or blank; for default behavior, seeRemark 2)

If real entry, value of τ for all degrees of freedom in EXCITEID entry.

If integer entry, identification number of a DELAY entry that containsvalues of τ for all degrees of freedom in EXCITEID entry. See Remark3.

DPHASE Phase angle, θ, in degrees. See Remark 10. (Real or Integer ≥ 0 orblank; for default behavior, see Remark 2)

If real entry, value of θ for all degrees of freedom in EXCITEID entry.

If integer entry, identification number of a DPHASE entry that containsvalues of θ for all degrees of freedom in EXCITEID entry. See Remark3.

TC C(f) (Real or Integer ≥ 0 or blank; for default behavior, see Remark 2)


Dynamics

Chapter 2: Dynamics

Field Contents

If real entry, value of C(f) used over all frequencies for all degreesof freedom in EXCITEID entry.

If integer entry, identification number of a TABLEDi entry that definesC(f) for all degrees of freedom in EXCITEID entry.

TD D(f) (Real or Integer ≥ 0 or blank; for default behavior, see Remark 2)

If real entry, value of D(f) used over all frequencies for all degreesof freedom in EXCITEID entry.

If integer entry, identification number of a TABLEDi entry that definesD(f) for all degrees of freedom in EXCITEID entry.

TYPE Defines the type of the dynamic excitation. See Remarks 7 and 8.(Integer, character or blank; Default = 0)

REMARKS:1. Dynamic excitation sets must be selected with DLOAD = SID in the case control

section.

2. If any of DELAY, DPHASE, TC, and TD fields are blank or zero (either integer zeroor real zero), the corresponding value for τ, θ, C(f), and D(f) used by the softwareis real zero.

3. For degrees of freedom in the EXCITEID entry that are not specified on the DELAYentry, the software uses real zero as the value for τ. For degrees of freedom inthe EXCITEID entry that are not specified on the DPHASE entry, the softwareuses real zero as the value for θ.

4. RLOAD1 excitations may be combined with RLOAD2 or RLOADEX excitationsusing a DLOAD bulk entry.

5. SID must be unique for all RLOAD1, RLOAD2, RLOADEX, TLOAD1, TLOAD2,ACSRCE, and SELOAD entries.

6. If ACSRCE and RLOADi entries are combined with a DLOAD bulk entry, theidentification numbers of the TABLEDi selected with the TP field on the ACSRCEentries must be different from the identification numbers of the TABLEDi selectedwith the TC and TD fields on RLOAD1 entries, and the TB and TP fields onRLOAD2 entries.

7. The type of the dynamic excitation is specified by TYPE (field 8) according tothe following table:

TYPE TYPE of Dynamic Excitation

0, L, LO, LOA, or LOAD Applied load (force or moment) (Default)


Chapter 2: Dynamics

Dynamics

TYPE TYPE of Dynamic Excitation

1, D, DI, DIS, or DISP Enforced displacement using SPC, SPCD, SPCFdata

2, V, VE, VEL, or VELO Enforced velocity using SPC or SPCD data

3, A, AC, ACC, or ACCE Enforced acceleration SPC or SPCD data

8. TYPE determines the manner in which EXCITEID is used by the software.

• TYPE = 0: Applied load excitation.

EXCITEID may reference DAREA, FORCEi, MOMENTi, RFORCEi, PLOAD,PLOAD1, QHBDY, QBDYi, QVECT, QVOL, and SELOAD entries.

• TYPE = 1, 2, or 3: Enforced motion excitation.

o If EXCITEID references SPC, SPCD, or SPCF bulk entries, the softwarewill use the SPCD method of enforced motion. You directly specify:

■ Displacements, velocities, or accelerations with SPC or SPCD bulkentries.

■ Only displacements (TYPE = 1) with SPCF bulk entries. For SPCF,the entire dynamic load equation is defined in the file referenced bythe SPCF and any TC, TD, DELAY, and DPHASE values are ignored.

o If EXCITEID references a load entry (DAREA, FORCEi, MOMENTi,RFORCEi, PLOAD, and PLOAD1 entries), the software will use the largemass method of enforced motion. You create a large mass and load atthe grid and degree of freedom where the enforced motion is desired.The software then computes the enforced motion the same for TYPE =1, 2, and 3.

Type = 1, Enforced displacement = Dynamic load input / Large massType = 2, Enforced velocity = Dynamic load input / Large massType = 3, Enforced acceleration = Dynamic load input / Large mass

See the “Enforced Motion” chapter of the Simcenter Nastran Basic DynamicAnalysis User’s Guide for details on both the SPCD and large mass methodsof enforced motion.

9. The legacy method of selecting a DAREA, FORCEi, MOMENTi, RFORCEi,PLOAD, and PLOAD1 entry for a dynamic loading required the LOADSET casecontrol command which selected the LSEQ bulk entry, which in turn selected theload entry. Because the DAREA, FORCEi, MOMENTi, PLOAD, PLOAD1, andSPCD entries are now selected directly with the EXCITEID on the dynamic loadentries DLOADi, TLOADi, and RLOADi, the LOADSET case control and LSEQbulk entry are no longer required. The legacy method is still supported, and isdescribed on the LSEQ entry remarks.

10. The software converts the phase angle, θ, to radians.


Dynamics

Chapter 2: Dynamics

Limiting frequency response output to peak responsesIn a SOL 108 or SOL 111 structural, acoustic, or vibro-acoustic frequency response analysis, you canlimit the output to frequencies where peak responses occur. This capability is called peakout.

To obtain these frequencies, you must specify the following:

• The subset of DOF that you want the software to filter to identify the peak responses.

• The filtering criteria.

In previous versions of the software, two solves are required for you to perform an equivalentanalysis. The first solve calculates the frequency responses. From the frequency responses, youmanually identify the frequencies where peak responses occur. You then edit the input file so that thesecond solve occurs at those frequencies only.

Because peakout requires only one solve and no input file editing, it can save you time and reducethe chances for error.

When you use the peakout capability, the software does the following:

1. Calculates the frequency response for all the DOF identified by the output request where thePEAKOUT describer is specified.

2. Filters the frequency responses for each DOF listed on the PEAKOUT bulk entries. Eachfrequency response that satisfies the filtering criteria is a peak response.

You specify the filtering criteria for each DOF on the PEAKOUT bulk entries.

3. For all the DOF identified by the output request where SOLUTION = PEAKOUT is specified,outputs frequency response results at only the frequencies where the peak responses occur.

When multiple output requests with SOLUTION = PEAKOUT specified are present, the softwareoutputs the frequency response results for each output request at the frequencies of the peakresponses. For an output request that does not have SOLUTION = PEAKOUT specified, the softwareoutputs the frequency response results for that output request at all the frequencies if SOLUTION =ALL, or at a subset of the frequencies if SOLUTION = setf.

The filtering criteria that you can use to identify the peak responses, in the order that the softwareapplies them, are as follows:

1. Frequency range of interest — The response at frequencies outside the range of interest isexcluded from the peak response search.

2. Response cutoff — The response within the frequency range of interest, but below the responsecutoff, is excluded from the peak response search.

3. Response proximity — Responses within the frequency range of interest and above the responsecutoff, but in close proximity to other responses with higher magnitude, are excluded from thepeak response search.

4. Requested number of peaks — Of the responses that remain after the software applies thefirst three criteria, the requested number of responses with the highest magnitude responsesare the peak responses. The other responses are not considered peak responses unless theysatisfy the outlier recovery criterion.


Chapter 2: Dynamics

Dynamics

If the number of responses that remain after applying the first three criteria is less than therequested number of peaks, only the responses that satisfy the first three criteria are peakresponses.

5. Outlier recovery — The outlier recovery criterion identifies as peak responses those responsesthat were eliminated because of the requested number of peaks criterion, but are at muchdifferent frequencies than the peak responses that the software identified after it applied the firstfour criteria. Thus, it is possible to have more peak responses than the number you requested.

Implementing the peakout capability

To use the peakout capability, at a minimum, add the following to the input file for a frequencyresponse analysis: a PEAKOUT case control command, an output request that supports thePEAKOUT describer, and a PEAKOUT bulk entry.

• PEAKOUT case control command

Include PEAKOUT case control commands to trigger the software to generate a set of frequenciesat which peak responses occur for the DOF that you specify. You can place a single PEAKOUTcase control command above the subcases and in each subcase.

When you place a PEAKOUT case control command above the subcases, it is applied toall the subcases. However, when you place a PEAKOUT case control command above thesubcases and inside subcases, the PEAKOUT case control commands inside the subcasestake precedence.

A single PEAKOUT case control command can reference multiple PEAKOUT bulk entriesthat have the same identification number. When this occurs, the set of frequencies at whichpeak responses occur for a given DOF is the union of the peak responses identified by eachPEAKOUT bulk entry separately for the DOF. For example, suppose that a PEAKOUT casecontrol command references two PEAKOUT bulk entries. If 100 Hz, 145 Hz, 176 Hz, and 232 Hzsatisfy the criteria for one PEAKOUT bulk entry, and 85 Hz, 133 Hz, 176 Hz, and 210 Hz satisfythe criteria for the other PEAKOUT bulk entry, the set of frequencies at which peak responsesoccur is 85 Hz, 100 Hz, 133 Hz, 145 Hz, 176 Hz, 210 Hz, and 232 Hz.

• Output requests

On the output requests, specify the new SOLUTION = PEAKOUT describer. The output requeststhat support the peakout capability are as follows:

o For structural frequency response analysis: DISPLACEMENT, VELOCITY, ACCELERATION,GPFORCE, MODCON (SOL 111 only).

o For acoustic frequency response analysis: PRESSURE, MODCON (SOL 111 only).

o For vibro-acoustic frequency response analysis: DISPLACEMENT, VELOCITY,ACCELERATION, GPFORCE, PRESSURE, MODCON (SOL 111 only), PANCON, GRDCON.


Dynamics

Chapter 2: Dynamics

Note

The types of responses on the PEAKOUT bulk entries specify the types of frequencyresponse results that the software uses when it identifies the peak responses. Theoutput request specifies the type of frequency response results to output at thefrequencies for the peak responses.

• PEAKOUT bulk entries

Use one or more PEAKOUT bulk entries to specify the following:

o The DOF for which the software retrieves frequency responses that it filters to identify thepeak responses.

Use the GIDi and CIDi fields to specify these DOF.

o The type of frequency response results to filter for each DOF.

Use the TYPE field to specify the response type. Valid types are displacement,acceleration, velocity, and pressure results. You can include multiple response types on asingle PEAKOUT bulk entry. You can also include the same DOF after multiple responsetypes on a single PEAKOUT bulk entry. When you do so, the software creates the set offrequencies at which peak responses occur for the DOF from the union of the sets offrequencies at which peak responses occur for the DOF for each response type.

o The response cutoff for each DOF.

Use the CUTOFFi field to specify the response cutoff for each DOF. Use real input tospecify a single cutoff value that the software applies across the frequency range ofinterest. Use integer input to reference a TABLED1, TABLED2, TABLED3, or TABLED4bulk entry that defines the cutoff as a tabular function of frequency.

o The frequency range of interest.

Use the LFREQ and HFREQ fields to specify the frequency range of interest.

o The response proximity frequency difference.

Use the NEAR field to specify the minimum allowable frequency difference betweenadjacent peak responses.

o The requested number of peaks.

Use the NPEAK field to specify the desired number of peak responses.

o The outlier recovery criterion.

Use the FAR field to specify frequency bands about each response that is retained afterthe NPEAK criterion is applied. If a response is excluded based on the NPEAK criterionand it lies outside these frequency bands, it is included in the peak responses.

In the frequency response input file, on the FREQi bulk entry, define enough solution frequencies toensure that you do not miss any peak responses. If you include an OFREQ case control command,


Chapter 2: Dynamics

Dynamics

the results for all frequencies specified by the OFREQ command that satisfy the PEAKOUT filteringcriteria are output.

For more information, see the new PEAKOUT case control command and the new PEAKOUT bulkentry, as well as, the updated DISPLACEMENT, VELOCITY, ACCELERATION, PRESSURE,GPFORCE, MODCON, PANCON, and GRDCON case control commands.


Dynamics

Chapter 2: Dynamics

PEAKOUT

Peak Response Frequency Set

Generates a set of frequencies where response peaks occur from SOL 108 and 111frequency response analysis results.

FORMAT:

EXAMPLES:PEAKOUT=100

DESCRIBERS:

Describer Meaning

n Set identification number of PEAKOUT bulk entries. (Integer> 0)

REMARKS:1. A single PEAKOUT case control command can be placed above the subcases

and a single PEAKOUT case control command can be placed in each frequencyresponse subcase.

2. When a PEAKOUT case control command is placed above the subcases, itis applied to all the subcases. When a PEAKOUT case control command isplaced above the subcases and PEAKOUT case control commands are placedinside subcases, the PEAKOUT case control commands inside the subcasestake precedence.

3. A PEAKOUT case control command can reference multiple PEAKOUT bulk entriesthat have the same identification number. When this occurs, the set of frequenciesat which peak responses occur for a DOF is the union of the peak responses thatare identified by each PEAKOUT bulk entry for the DOF.

For example, suppose that a PEAKOUT case control command references twoPEAKOUT bulk entries. If 100 Hz, 145 Hz, 176 Hz, and 232 Hz satisfy the criteriaof one PEAKOUT bulk entry for a given DOF, and 85 Hz, 133 Hz, 176 Hz, and210 Hz satisfy the criteria of the other PEAKOUT bulk entry for the same DOF,the set of frequencies at which peak responses occur for the DOF is 85 Hz, 100Hz, 133 Hz, 145 Hz, 176 Hz, 210 Hz, and 232 Hz.


Chapter 2: Dynamics

Dynamics

PEAKOUT

Peak Response Filtering Criteria

Specifies the filtering criteria and the DOF whose frequency responses are filtered toobtain the set of frequencies at which the peak responses occur.

FORMAT:

1 2 3 4 5 6 7 8 9 10PEAKOUT ID NPEAK NEAR FAR LFREQ HFREQ DBREF

TYPE GID1 CID1 CUTOFF1 GID2 CID2 CUTOFF2

GID3 CID3 CUTOFF3 ...... ...... ......

EXAMPLES:

PEAKOUT 101 3 3.0 25.0 10.0 200.0

DISP 1023 2 2.3E-2 2033 1 1011

PEAKOUT 1003 5 3.0 25.0 10.0 200.0

DISP 1023 2 2.3E-2 2033 1 1011

PRESDBA 8001 1 2001 8002 1 2002

FIELDS:

Field Contents

ID Identification number. See Remark 1. (Integer > 0; No default)

NPEAK Number of peak responses to select from the responses that remainafter the LFREQ, HFREQ, CUTOFFi, and NEAR criteria are appliedto the frequency response results. (Integer > 0; Default = 5)

NEAR Minimum allowable frequency difference between adjacent peakresponses in cycles per unit time. See Remark 2. (Real ≥ 0.0; Default= 0.0)

FAR Frequency difference used to retain responses that are eliminated bythe NPEAK criterion, but are at much different frequencies than thepeak responses that are retained after applying the LFREQ, HFREQ,CUTOFFi, NEAR, and NPEAK criteria in cycles per unit time. SeeRemark 3. (Real > NEAR; Default = 1.0E6)

LFREQ Frequency below which the frequency response results are excludedfrom the set of frequencies at which peak responses occur in cyclesper unit time. See Remark 4. (Real ≥ 0.0; Default = 0.0)

HFREQ Frequency above which the frequency response results are excludedfrom the set of frequencies at which peak responses occur in cyclesper unit time. See Remark 4. (Real > LFREQ; Default = 1.0E6)


Dynamics

Chapter 2: Dynamics

Field Contents

DBREF Reference value for dB calculations. See Remark 5. (Real > 0.0;Default = 1.0E-20)

TYPE Response type. See Remark 1. (Character = "DISP", "VELO","ACCE", "PRES", "PRESDB", "PRESDBA"; No default)

= "DISP" for displacement response.

= "VELO" for velocity response.

= "ACCE" for acceleration response.

= "PRES" for pressure response.

= "PRESDB" for pressure response in dB. See Remark 5.

= "PRESDBA" for pressure response in dBA. See Remark 5.

GIDi Grid point identification number. (Integer > 0; No default)

CIDi Component identification number. (Integer: 1 thru 6 for structural gridpoints, 1 for fluid grid points and scalar points; No default)

CUTOFFi Response magnitude below which frequency response results areexcluded from the set of frequencies at which peak responses occur.(Real > 0.0 or integer > 0; No default)

Real input defines a constant value for the cutoff.

Integer input specifies the identification number of a TABLED1,TABLED2, TABLED3, or TABLED4 bulk entry that defines afrequency-dependent cutoff.

REMARKS:1. A PEAKOUT bulk entry can contain multiple types. When this occurs, the set

of frequencies at which peak responses occur for each DOF is the union of thefrequencies identified for each type for the DOF.

For example, suppose that a PEAKOUT case control command has two types. If100 Hz, 145 Hz, 176 Hz, and 232 Hz satisfy the criteria for one type for a givenDOF, and 85 Hz, 133 Hz, 176 Hz, and 210 Hz satisfy the criteria for the other typefor the same DOF, the set of frequencies at which peak responses occur for theDOF is 85 Hz, 100 Hz, 133 Hz, 145 Hz, 176 Hz, 210 Hz, and 232 Hz.

Multiple PEAKOUT bulk entries with the same ID are also allowed. When thisoccurs, the set of frequencies at which peak responses occur for a given DOF isthe union of the peak responses identified by each PEAKOUT bulk entry for theDOF.

For example, suppose that a second PEAKOUT bulk entry with the same ID ispresent. If 125 Hz, 182 Hz, and 258 Hz satisfy the criteria for this PEAKOUT


Chapter 2: Dynamics

Dynamics

bulk entry for the same DOF, the set of frequencies at which peak responsesoccur for the DOF is 85 Hz, 100 Hz, 125 Hz, 133 Hz, 145 Hz, 176 Hz, 182 Hz,210 Hz, 232 Hz, and 258 Hz.

2. Use the NEAR criterion to retain only the peak response when multiple responsesare clustered over a small frequency range. The software applies the NEARcriterion after it applies the LFREQ, HFREQ, and CUTOFFi criteria to thefrequency response as follows:

a. The software identifies the lowest frequency response from those retainedafter the LFREQ, HFREQ, and CUTOFFi criteria are applied. Let f1 be thefrequency at which this response occurs.

b. The software identifies the next lowest frequency response. Let f2 be thefrequency at which this response occurs.

c. If f1 + ΔfNEAR < f2, where ΔfNEAR is the frequency difference defined by thevalue in the NEAR field, both responses are retained. Then the softwarerepeats the process by comparing the response at f2 to the next lowestfrequency response which occurs at f3.

d. If f2 ≤ f1 + ΔfNEAR, the software excludes whichever of the two responses hasthe smaller magnitude response. Then the software repeats the process bycomparing the response that it retains to the next lowest frequency responsewhich occurs at f3.

e. The software continues the process until all the responses that are retainedafter applying the LFREQ, HFREQ, and CUTOFFi criteria are evaluated.

3. Use the FAR criterion to retain as peak responses those responses that areat much different frequencies than the peak responses that are retained afterapplying the NPEAK criterion. The software applies the FAR criterion as follows:

a. The software creates frequency bands about each peak response that areretained after applying the NPEAK criterion. The range of the band about theith peak response is fi - ΔfFAR < f < fi + ΔfFAR, where ΔfFAR is the frequencydifference defined by the value in the FAR field.

b. The software retains as peak responses any responses that are eliminatedbecause of the NPEAK criterion that lie outside the frequency bands, but arewithin LFREQ ≤ f ≤ HFREQ. Thus, it is possible to have more frequencies inthe set of frequencies at which peak responses occur for a given DOF thanthe number of peak responses specified in the NPEAK field.

4. If the slope of the frequency response curve is descending at LFREQ, the softwaretreats the response at LFREQ as a possible peak response, even though ittypically does not coincide with a peak in the frequency response. If the slope ofthe frequency response curve is ascending at HFREQ, the software treats theresponse at HFREQ as a possible peak response, even though it typically doesnot coincide with a peak in the frequency response. Thus, they are retained aspeak responses if they satisfy the CUTOFFi, NEAR, and NPEAK criteria, or theFAR criterion.


Dynamics

Chapter 2: Dynamics

5. The dB and dBA values are calculated as follows:

where P is the sound pressure level and Pref is the sound pressure reference levelgiven by the value in the DBREF field. The A-weighting function is given as follows:

where f is the frequency in Hz. Thus, the unit of time must be seconds in order forthe A-weighted results to be correct.


Chapter 2: Dynamics

Dynamics

DISPLACEMENT

Displacement Output Request

Requests the form and type of displacement vector output.

FORMAT:

EXAMPLES:DISPLACEMENT=5DISPLACEMENT(REAL)=ALLDISPLACEMENT(SORT2, PUNCH, REAL)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Output a tabular listing of grid points for each load, frequency,eigenvalue, or time, depending on the solution sequence.(Default)

SORT2 Output a tabular listing of load, frequency or time for eachgrid point.

PRINT The printer is the output medium. (Default)

PUNCH The punch file is the output medium.

PLOT Generate, but do not print, displacement results.

REAL or IMAG Requests real/imaginary format for complex output. Specifyeither REAL or IMAG. (Default)

PHASE Requests magnitude/phase format for complex output. Phaseoutput is in degrees.

ABS For enforced motion dynamic analysis, displacement resultsare output as absolute displacement. (Default)

REL For enforced motion dynamic analysis, displacement resultsare output relative to the enforced motion input.


Dynamics

Chapter 2: Dynamics

Describer Meaning

PSDF Requests power spectral density function be calculated forrandom analysis post-processing. The request must be madeabove the subcase level and RANDOM must be selected inthe Case Control. See Remark 8.

ATOC Requests autocorrelation function be calculated for randomanalysis post-processing. The request must be made abovethe subcase level and RANDOM must be selected in the CaseControl. See Remark 8.

CRMS Requests cumulative root mean square function be calculatedfor random analysis post-processing. Request must be madeabove the subcase level and RANDOM must be selected inthe Case Control. See Remark 8.

RMS Requests root mean square and zero crossing functions becalculated for random analysis post-processing. Request mustbe made above the subcase level and RANDOM must beselected in the Case Control. See Remark 8. (Default)

RALL Requests all of PSDF, ATOC, RMS, and CRMS be calculatedfor random analysis post-processing. The request mustbe made above the subcase level and RANDOM must beselected in the Case Control. See Remark 8.

RPRINT Writes random analysis results to the print file. See Remark8. (Default)

NORPRINT Disables the writing of random analysis results to the print file.See Remark 8.

RPUNCH Writes random analysis results to the punch file. See Remark8.

SOLUTION =ALL

Output displacement for all frequencies. See Remark 13.(Default)

SOLUTION = setf Output displacement only for the frequencies listed ona previously appearing SET command with setf as theidentification number. See Remark 13. (Integer > 0)

SOLUTION =PEAKOUT

Output displacement only for frequencies identified with thePEAKOUT command. See Remark 13.

ALL Output displacement for all points.

n Output displacement only for the points listed on a previouslyappearing SET command with n as the identification number.(Integer > 0)


Chapter 2: Dynamics

Dynamics

Describer Meaning

NONE Do not output displacement for any points. (Default)

REMARKS:1. Both PRINT and PUNCH can be requested.

2. The defaults for SORT1 and SORT2 depend on the analysis type:

• SORT1 is the default in static analysis, frequency response, steady state heattransfer analysis, real and complex eigenvalue analysis, flutter analysis, andbuckling analysis. If SORT2 is selected in a frequency response solution forone or more of the commands ACCE, DISP, FORC, GPFO, MPCF, OLOA,SPCF, STRA, STRE, and VELO then the remaining commands are alsooutput in SORT2 format.

• SORT2 is the default in transient response analysis (structural and heattransfer). SORT2 is not available for real eigenvalue (including buckling),complex eigenvalue, or flutter analysis. If SORT1 is selected in a transientsolution for one or more of the commands ACCE, DISP, ENTH, FORC, GPFO,HDOT, MPCF, OLOA, SPCF, STRA, STRE, and VELO then the remainingcommands are also output in SORT1 format.

• XY plot requests force SORT2 format, thus overriding SORT1 format requests.

3. By default, the PRESSURE case control command requests pressure output atfluid grid points only and the DISPLACEMENT case control command requestsdisplacement at structural grid points only. In versions prior to NX Nastran12, thePRESSURE and DISPLACEMENT case control commands are interchangeable.Use SYSTEM(640) to revert to the pre-NX Nastran12 behavior.

4. DISPLACEMENT = NONE overrides an overall output request.

5. The PLOT option is used when curve plots are desired in the magnitude/phaserepresentation and no printer output request is present for the magnitude/phaserepresentation.

6. The units of translation are the same as the units of length of the model. Rotationsare in units of radians.

7. Displacement results are printed and/or punched in the global coordinate system(see field CD on the GRID bulk data entry). The coordinate system for plotteddisplacement output depends on the PARAM,POST setting. See the parameterPOST.

8. The following applies to random solutions:

• By default, frequency response results are not output. If in addition to randomoutput, frequency response output is desired, specify SYSTEM(524)=1 orRANFRF=1 in the input file. The PRINT, PUNCH, PLOT describers control the


Dynamics

Chapter 2: Dynamics

frequency response output. The RPRINT, NORPRINT, RPUNCH describerscontrol the random output.

• The SORT1 and SORT2 describers only control the output format for thefrequency response output. The output format for random results is controlledusing the RPOSTS1 describer on the RANDOM case control command orthe parameter RPOSTS1, except for RMS results, which are only availablein SORT1 format.

• Any combination of the PSDF, ATOC, RMS, and CRMS describers can beselected. The RALL describer selects all four.

• Autocorrelation (ATOC) calculations require the RANDT1 bulk entry.

9. When doing enforced motion dynamic analysis and relative output is requested(using the REL describer), the output is relative to the input as described by theequation:

where uf is absolute displacement, yf is relative displacement, and us is enforcedmotion.

10. During a SOL 108 or 111 frequency-dependent external superelement creationrun, on the SET case control command that is referenced by the DISPLACEMENTcase control command, include any points at which you want to recover resultsduring the system run.

11. The SOLUTION describer is only valid in a SOL 108 or 111 frequency responseanalysis.

12. When an OFREQ case control command is present, the SOLUTION describer isused as follows:

• If SOLUTION=ALL, output results for all frequencies specified by the OFREQcommand.

• If SOLUTION=setf, output results for all frequencies specified by the OFREQcommand that are listed on a previously appearing SET command with setfas the identification number.

• If SOLUTION=PEAKOUT and a PEAKOUT case control command is alsopresent in the input file, output results for all frequencies specified by theOFREQ command that satisfy the PEAKOUT filtering criteria.

13. The SOLUTION describer is not valid for superelements or frequency-dependentcomponents.


Chapter 2: Dynamics

Dynamics

REMARKSRELATED TO

SOLS 601 AND701:

1. Output is restricted to REAL format. IMAG, PHASE, PSDF, ATOC, RMS, andRALL are ignored.

2. Displacements, velocities and accelerations must be output for the same set of gridpoints if requested. Output requested for set n in this command will be combinedwith the sets requested in the VELOCITY and ACCELERATION commands, anddisplacements will be output at the grid points of the combined set.

REMARKSRELATED TO

SOL 402:1. Output is restricted to REAL and SORT1 format. SORT2, IMAG, PHASE, ABS,

REL, PSDF, ATOC, CRMS, RMS, RALL, NOPRINT and RPUNCH are ignored.


Dynamics

Chapter 2: Dynamics

VELOCITY

Velocity Output Request

Requests the form and type of velocity vector output.FORMAT:

EXAMPLES:VELOCITY=5VELOCITY(SORT2,PHASE,PUNCH)=ALL

DESCRIBERS:

Describer Meaning


SORT2 Output a tabular listing of frequency or time for each grid point.



PLOT Generate, but do not print, velocity results.



ABS For enforced motion dynamic analysis, velocity results areoutput as absolute velocity. (Default)

REL For enforced motion dynamic analysis, velocity results areoutput relative to the enforced motion input.


Chapter 2: Dynamics

Dynamics

Describer Meaning









SOLUTION =ALL

Output velocity for all frequencies. See Remark 12. (Default)

SOLUTION = setf Output velocity only for the frequencies listed on a previouslyappearing SET command with setf as the identificationnumber. See Remark 12. (Integer > 0)

SOLUTION =PEAKOUT

Output velocity only for frequencies identified with thePEAKOUT command. See Remark 12.

ALL Output velocity for all points.

n Output velocity only for the points listed on a previouslyappearing SET command with n as the identification number.(Integer > 0)


Dynamics

Chapter 2: Dynamics

Describer Meaning

NONE Do not output velocity for any points. (Default)


2. Velocity output is only available for transient and frequency response problems.





4. VELOCITY=NONE overrides an overall output request.

5. The PLOT option is used when curve plots are desired in the magnitude/phaserepresentation and no printer request is present for magnitude/phaserepresentation.

6. Velocity results are printed and/or punched in the global coordinate system (seefield CD on the GRID bulk data entry). The coordinate system for plotted velocityoutput depends on the PARAM,POST setting. See the parameter POST.


• By default, frequency response results are not output. If in addition to randomoutput, frequency response output is desired, specify SYSTEM(524)=1 orRANFRF=1 in the input file. The PRINT, PUNCH, PLOT describers control thefrequency response output. The RPRINT, NORPRINT, RPUNCH describerscontrol the random output.



Chapter 2: Dynamics

Dynamics





9. During a SOL 108 or 111 frequency-dependent external superelement creationrun, on the SET case control command that is referenced by the VELOCITYcase control command, include any points at which you want to recover resultsduring the system run.







REMARKSRELATED TO

SOLS 601 AND701:


2. Displacements, velocities and accelerations must be output for the same setof grid points if requested. Output requested for set n in this command will becombined with the sets requested in the DISPLACEMENT and ACCELERATIONcommands, and velocities will be output at the grid points of the combined set.


Dynamics

Chapter 2: Dynamics

REMARKSREALTED TO


REL, PSDF, ATOC, CRMS, RMS, RALL, NORPRINT, and RPUNCH are ignored.


Chapter 2: Dynamics

Dynamics

ACCELERATION

Acceleration Output Request

Requests form and type of acceleration vector output.FORMAT:

EXAMPLES:ACCELERATION=5ACCELERATION(SORT2, PHASE)=ALLACCELERATION(SORT1, PRINT, PUNCH, PHASE)=17

DESCRIBERS:

Describer Meaning


SORT2 Output a tabular listing of frequency or time for each grid point.



PLOT Generate, but do not print, acceleration results.



ABS For enforced motion dynamic analysis, acceleration results areoutput as absolute acceleration. (Default)

REL For enforced motion dynamic analysis, acceleration results areoutput relative to the enforced motion input.


Dynamics

Chapter 2: Dynamics

Describer Meaning

PSDF Requests power spectral density function be calculated forrandom analysis post-processing. The request must be madeabove the subcase level and RANDOM must be selected in theCase Control. See Remark 7.


CRMS Requests cumulative root mean square function be calculatedfor random analysis post-processing. Request must be madeabove the subcase level and RANDOM must be selected in theCase Control. See Remark 7.


RALL Requests all of PSDF, ATOC, RMS, and CRMS be calculatedfor random analysis post-processing. The request must bemade above the subcase level and RANDOM must be selectedin the Case Control. See Remark 7.



RPUNCH Writes random analysis results to the punch file. See Remark 7.

SOLUTION =ALL

Output acceleration for all frequencies. See Remark 12.(Default)

SOLUTION =setf

Output acceleration only for the frequencies listed ona previously appearing SET command with setf as theidentification number. See Remark 12. (Integer > 0)

SOLUTION =PEAKOUT

Output acceleration only for frequencies identified with thePEAKOUT command. See Remark 12.

ALL Output acceleration for all points.

n Output acceleration only for the points listed on a previouslyappearing SET command with n as the identification number.(Integer > 0)

NONE Do not output acceleration for any points. (Default)


Chapter 2: Dynamics

Dynamics


2. Acceleration output is only available for transient and frequency responseproblems.





4. ACCELERATION = NONE allows overriding an overall output request.

5. The PLOT option is used when curve plots are desired in the magnitude/phaserepresentation and no printer request is present for magnitude/phaserepresentation.

6. Acceleration results are printed and/or punched in the global coordinate system(see field CD on the GRID bulk data entry). The coordinate system for plottedacceleration output depends on the PARAM,POST setting. See the parameterPOST.


• By default, frequency response results are not output. If in addition to randomoutput, frequency response output is desired, specify SYSTEM(524)=1 orRANFRF=1 in the input file. The PRINT, PUNCH, PLOT describers control thefrequency response output. The RPRINT, NORPRINT, RPUNCH describerscontrol the random output.




Dynamics

Chapter 2: Dynamics




9. During a SOL 108 or 111 frequency-dependent external superelement creationrun, on the SET case control command that is referenced by the ACCELERATIONcase control command, include any points at which you want to recover resultsduring the system run.







REMARKSRELATED TO

SOLS 601 AND701:


2. Displacements, velocities and accelerations must be output for the same set of gridpoints if requested. Output requested for set n in this command will be combinedwith the sets requested in the VELOCITY and DISPLACEMENT commands, andaccelerations will be output at the grid points of the combined set.

REMARKSRELATED TO


REL, PSDF, ATOC, CRMS, RMS, RALL, NOPRINT and RPUNCH are ignored.


Chapter 2: Dynamics

Dynamics

PRESSURE

Pressure Output Request for Fluid Grid Points

Requests the form and type of pressure output for fluid grid points.

FORMAT:

EXAMPLES:PRESSURE=5PRESSURE(REAL)=ALLPRESSURE(SORT2,PUNCH,REAL)=ALL

DESCRIBERS:

Describer Meaning


SORT2 Output a tabular listing of load, frequency or time for eachgrid point.



PLOT Generate, but do not print, pressure results.



TOTAL Output total pressure for the incident-scattered formulation.(Default)

SCATR Output scattered pressure for the incident-scatteredformulation.


Dynamics

Chapter 2: Dynamics

Describer Meaning









SOLUTION =ALL

Output acoustic pressure for all frequencies. See Remark 9.(Default)

SOLUTION = setf Output acoustic pressure only for the frequencies listedon a previously appearing SET command with setf as theidentification number. See Remark 9. (Integer > 0)

SOLUTION =PEAKOUT orPEAK

Output acoustic pressure only for frequencies identified withthe PEAKOUT command. See Remark 9.

ALL Output acoustic pressure for all points.


Chapter 2: Dynamics

Dynamics

Describer Meaning

n Output acoustic pressure only for the points listed on apreviously appearing SET command with n as the identificationnumber. (Integer > 0)

NONE Do not output acoustic pressure for any points. (Default)


2. By default, the PRESSURE case control command requests pressure output atfluid grid points only and the DISPLACEMENT case control command requestsdisplacement at structural grid points only. In versions prior to NX Nastran 12, thePRESSURE and DISPLACEMENT case control commands are interchangeable.Use SYSTEM(640) to revert to the pre-NX Nastran 12 behavior.

3. PRESSURE = NONE overrides an overall output request.


• By default, frequency response results are not output. If you want both randomoutput and frequency response output, specify SYSTEM(524) = 1 or RANFRF= 1 in the input file. The PRINT, PUNCH, and PLOT describers controlthe frequency response output. The RPRINT, NORPRINT, and RPUNCHdescribers control the random output.

• The SORT1 and SORT2 describers control the output format for the frequencyresponse output only. The output format for random results is controlledusing the RPOSTS1 describer on the RANDOM case control command orthe parameter RPOSTS1, except for RMS results, which are only availablein SORT1 format.

• You can select any combination of the PSDF, ATOC, RMS, and CRMSdescribers. The RALL describer selects all four.


5. Any structural points that you include in SET = n are ignored.

6. During a SOL 108 or SOL 111 frequency-dependent external superelementcreation run, on the SET case control command that is referenced by thePRESSURE case control command, include any points at which you want torecover results during the system run.




Dynamics

Chapter 2: Dynamics





10. To obtain pressure results at microphone points, reference the fluid grid IDattached to the microphone points.


Chapter 2: Dynamics

Dynamics

GPFORCE

Grid Point Force Output Request

Requests grid point force balance at selected grid points.FORMAT:

EXAMPLES:GPFORCE=ALLGPFORCE=17GPFORCE(SORT2,PRINT,PUNCH,PHASE) = 123

DESCRIBERS:

Describer Meaning

SORT1 Output a tabular listing of grid points for each load, frequency,eigenvalue, or time depending on solution sequence. (Default)

SORT2 Output a tabular listing of load, frequency, eigenvalue, or time foreach grid point.



NOPRINT Generate, but do not print, grid point force balance results.

REAL orIMAG

Requests real/imaginary format for complex output. Specify eitherREAL or IMAG. (Default)


SOLUTION =ALL

Output grid point force balance for all frequencies. See Remark13. (Default)

SOLUTION =setf

Output grid point force balance only for the frequencies listed on apreviously appearing SET command with setf as the identificationnumber. See Remark 13. (Integer > 0)

SOLUTION =PEAKOUT

Output grid point force balance only for frequencies identified withthe PEAKOUT command. See Remark 13.

ALL Output grid point force balance for all grid points.


Dynamics

Chapter 2: Dynamics

Describer Meaning

n Output grid point force balance only for the grid points listed on apreviously appearing SET command with n as the identificationnumber. (Integer > 0)

NONE Do not output grid point force balance for any grid points.


2. PARAM,DDRMM,-1 is required in the modal solution sequences 111, 112, 146,and 200.

3. The printing of grid point forces is suppressed when PARAM,NOGPF,-1 appearsin the Bulk Data.

4. The Bulk Data entry PARAM,NOELOF,+1 causes the output of grid point forcesto be aligned with the edges of the two-dimensional elements. The default valueof -1 suppresses this output.

5. The Bulk Data entry PARAM,NOELOP,+1 causes the output of the sum ofthe forces parallel to the edges of adjacent elements. The default value of -1suppresses this output.

6. The output of grid point forces that are aligned with the edges of elements isavailable for the following elements: CBAR, CROD, CBEAM, CSHEAR, CONROD,CTRIA3

The positive direction for grid point forces aligned with the edges of elements isfrom the reference point to the load point as indicated on the printed output.

7. Grid point force balance is computed from linear and nonlinear elements, the sumof applied and thermal loads, and MPC and SPC forces. Effects not accountedfor include those from mass elements in dynamic analysis (inertia loads), generalelements, DMIG entries, and boundary loads from upstream superelements.These effects can lead to an apparent lack of equilibrium at the grid point level. Thefollowing table summarizes those effects that are considered and those effects thatare ignored in the calculation of grid point forces in the global coordinate system:

Contributions Included Contributions Ignored

Applied Loads GENEL Forces

SPC Forces DMIG and DMI Forces

Element Elastic Forces Boundary Loads from UpstreamSuperelements

Thermal Loads

MPC and Element Forces


Chapter 2: Dynamics

Dynamics

8. Only the element elastic forces are included when the grid point forces are alignedwith the edges of elements.

9. In inertia relief analysis, the GPFORCE output related to SPC forces and appliedloads is interpreted differently for SOLs 101 and 200. In SOLs 101 and 200, theSPC force and applied load output includes both the effect of inertial loads andapplied loads.

10. GPFORCE is supported in a nonlinear static analysis (SOLs 106 and 601). Itis not supported in SOLs 129 or 701. PARAM,NOELOF and PARAM,NOELOPare not supported in nonlinear static analysis. Thus, Remarks 4, 5, 6, and 8 donot apply to SOL 106.






13. The SOLUTION describer is not valid for external superelements and direct-input,frequency-dependent components.

14. When frequency-dependent elements are present in a frequency responseanalysis or nonlinear bearing elements are present in a rotor dynamic analysis, thegrid point force results are based on the nominal values for stiffness and damping.


Dynamics

Chapter 2: Dynamics

MODCON

Modal Contribution Output Request

Requests the form and type of modal contribution output for the residual.FORMAT:

EXAMPLES:MODCON=123MODCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPS=5)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Output a tabular listing of modal DOF for each frequency or time.(Default)

SORT2 Output a tabular listing of frequency or time for each modal DOF.This option is not available for SOL 110.

REAL orIMAG



PRINT Write modal contribution output to the print (.f06) file. (Default)

PUNCH Write modal contribution output to the standard punch (.pch) file.

NOPRINT Generate, but do not print, modal contribution results.

ABS Output modal contributions in absolute terms. (Default)

NORM Output modal contributions in normalized terms.

BOTH Output modal contributions in both absolute and normalized terms.


Chapter 2: Dynamics

Dynamics

Describer Meaning

TOPS (orTOP) = ps

The number of structural modes to list in the output that have thegreatest contribution to the response at each frequency or time. Ifps > 1, the output is sorted in descending order from the structuralmode that has the greatest contribution. If ps = 0, no structuralmode contributions are output, only totals. See Remark 1. (Integer≥ 0; Default ps = 5)

TOPF = pf The number of fluid modes to list in the output that have the greatestcontribution to the response at each frequency or time. If pf > 1, theoutput is sorted in descending order from the fluid mode havingthe greatest contribution. If pf = 0, no fluid mode contributions areoutput, only totals. See Remark 1. (Integer ≥ 0; Default pf = 5)

SOLUTION= ALL

Perform the modal contribution calculations at all frequencies ortimes that are defined by the FREQUENCY or TSTEP case controlcommands, respectively. See Remark 12. (Default)

SOLUTION= setout

Perform the modal contribution calculations at the frequencies ortimes listed on a previously appearing SET case control commandwith setout as the identification number. See Remark 12. (Integer> 0)

SOLUTION= PEAKOUT

Perform the modal contribution calculations only at the frequenciesidentified with the PEAKOUT command. See Remark 12.

PANELMC =NONE

Requests that no modal contributions are calculated for panels.See Remarks 1 and 9. (Default)

PANELMC =setp

Requests that modal contributions are calculated for the panelslisted on a previously appearing SET case control command withsetp as the identification number. See Remarks 1 and 9. (Integer> 0)

PANELMC =ALL

Requests that modal contributions be calculated for all panelsdefined by PANEL bulk entries. See Remarks 1 and 9.

n Calculate modal contributions for the responses listed on apreviously appearing SETMC case control command with n as theidentification number. (Integer > 0)

ALL Calculate modal contributions for all the responses listed on theSETMC case control commands specified in and above the currentsubcase.

NONE Do not calculate modal contributions.

REMARKS:1. SOL 108, 110, 111, 112, and SOL 146 are supported.

• For SOL 108 and SOL 111, MODCON is supported by the FEM AdaptiveOrder (FEMAO) method with the following exceptions:


Dynamics

Chapter 2: Dynamics

o The number of structural modes (TOPS describer) is not supported.

o The modal pressure contributions are computed on all panels. You cannotspecify a subset of panels.

• For SOL 110, modal contributions for superelements are not supported.

• The TOPF and PANELMC describers are only supported for SOL 111.

• The SOLUTION describer is only supported for SOL 111, 112, and 146.

2. Both PRINT and PUNCH can be requested.

3. MODCON = NONE overrides an overall output request. Thus, to turn offcontribution output for a specific subcase, place MODCON = NONE in the subcase.

4. MODCON supports results for microphone points.

5. Results for SPC forces do not include the effect of any enforced motion applied atthe DOF.

6. The parameters LFREQ, LFREQFL, HFREQ, HFREQFL, LMODES, andLMODESFL are supported.

7. The SOLUTION and PANELMC describers can be abbreviated to SOLU andPANE, respectively.

8. The SET case control command referenced by SOLUTION = setout must containreal values for frequencies or times. Using integer values may lead to erroneousresults.

9. The PANELMC describer applies to acoustic responses and the contributionsfrom structural modes.




• If SOLUTION=setout, output results for all frequencies specified by theOFREQ command that are listed on a previously appearing SET commandwith setf as the identification number.




Chapter 2: Dynamics

Dynamics

PANCON

Acoustic Contribution Output Request for Panels

Requests the form and type of acoustic contribution output for structural panels andthe residual.

FORMAT:

EXAMPLES:PANCON=123PANCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPP=5)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Output a tabular listing of panels for each frequency.

SORT2 Output a tabular listing of frequency for each panel. (Default)

REAL orIMAG



PRINT Write acoustic panel contribution output to the print (.f06) file.(Default)

NOPRINT Do not print the acoustic panel contribution results.

PUNCH Write acoustic panel contribution output to the standard punch(.pch) file.

ABS Output acoustic panel contributions in absolute terms. (Default)

NORM Output acoustic panel contributions in normalized terms.

BOTH Output acoustic panel contributions in both absolute and normalizedterms.

TOPP = ALL List all of the structural panels in the output. Sort the output indescending order from the structural panel that has the greatestcontribution. See Remark 2.


Dynamics

Chapter 2: Dynamics

Describer Meaning

TOPP = pp The number of structural panels to list in the output that have thegreatest contribution to the response at each frequency. If pp > 1,the output is sorted in descending order from the structural panelthat has the greatest contribution. If pp = 0, no structural modecontributions are output, only totals. See Remark 2. (Integer ≥ 0;Default pp = 5)

SOLUTION= ALL

Perform the contribution calculations at all frequencies defined byFREQUENCY case control commands. See Remark 12. (Default)

SOLUTION= setf

Perform the contribution calculations only at the frequencies listedon a previously appearing SET case control command with setf asthe identification number. See Remark 12. (Integer > 0)

SOLUTION= PEAKOUT

Perform the contribution calculations only at the frequenciesidentified with the PEAKOUT command. See Remark 12.

PANEL =ALL

Output contributions for all panels defined by PANEL bulk entries.(Default)

PANEL =setp

Output contributions for the panels listed on a previously appearingSET case control command with setp as the identification number.(Integer > 0)

n Calculate panel contributions for the responses listed on a previouslyappearing SETMC case control command with n as the identificationnumber. Any response listed in this SETMC case control commandthat is not an acoustic response is ignored. (Integer > 0)

ALL Calculate panel contributions for all the responses listed on theSETMC case control commands specified in and above the currentsubcase. Any response listed in these SETMC case controlcommands that is not an acoustic response is ignored. (Default)

NONE Do not calculate panel contributions.

REMARKS:1. SOL 108 and 111 are supported.

2. For SOL 108 and SOL 111, MODCON is supported by the FEM Adaptive Order(FEMAO) method with the exception of the number of structural panels (TOPPdescriber).


4. PANCON = NONE overrides an overall output request. Thus, to turn offcontribution output for a specific subcase, place PANCON = NONE in the subcase.

5. PANCON supports results for microphone points.


Chapter 2: Dynamics

Dynamics


7. The SOLUTION and PANEL describers can be abbreviated to SOLU and PANE,respectively.

8. The SET case control command referenced by SOLUTION = setf must containreal values for frequencies. Using integer values may lead to unintended results.

9. The SET case control command referenced by PANEL = setp must contain thealphanumeric name of panels defined by PANEL bulk entries.








Dynamics

Chapter 2: Dynamics

GRDCON

Acoustic Contribution Output Request for Grids

Requests the form and type of acoustic contribution output for the grids of structuralpanels and for the residual.

FORMAT:

EXAMPLES:GRDCON=123GRDCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPG=5)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Output a tabular listing of grids for each frequency. (Default)

SORT2 Output a tabular listing of frequency for each grid.

REAL orIMAG



PRINT Write acoustic grid contribution output to the print (.f06) file. (Default)

NOPRINT Do not print the acoustic grid contribution results.

PUNCH Write acoustic grid contribution output to the standard punch (.pch)file.

ABS Output acoustic grid contributions in absolute terms. (Default)

NORM Output acoustic grid contributions in normalized terms.

BOTH Output acoustic grid contributions in both absolute and normalizedterms.


Chapter 2: Dynamics

Dynamics

Describer Meaning

TOPG = pg

The number of structural grids to list in the output that have thegreatest contribution to the response at each frequency. If pg >1, the output is sorted in descending order from the structural gridthat has the greatest contribution. If pg = 0, no structural gridcontributions are output, only totals. (Integer ≥ 0)

TOPG = ALL List all of the structural grids in the output. Sort the output indescending order from the structural grid that has the greatestcontribution. (Default)

SOLUTION= ALL


SOLUTION= setf


SOLUTION= PEAKOUT


GRID = ALL Output contributions for all structural grids that are part of theacoustic coupling matrix. (Default)

GRID = setg

Output contributions for the grids listed on a previously appearingSET case control command with setg as the identification number.Any grid in the set that is not part of the coupling matrix is ignored.(Integer > 0)

n Calculate grid contributions for the responses listed on a previouslyappearing SETMC case control command with n as the identificationnumber. Any response listed in this SETMC case control commandthat is not an acoustic response is ignored. (Integer > 0)

ALL Calculate grid contributions for all the responses listed on theSETMC case control commands specified in and above the currentsubcase. Any response listed in these SETMC case controlcommands that is not an acoustic response is ignored. (Default)

NONE Do not calculate grid contributions.


2. GRDCON = NONE overrides an overall output request. Thus, to turn offcontribution output for a specific subcase, place GRDCON = NONE in the subcase.

3. SOL 108 and 111 are supported.



Dynamics

Chapter 2: Dynamics

5. The SOLUTION describer can be abbreviated to SOLU.


7. GRDCON supports results for microphone points.








Chapter 2: Dynamics

Chapter 3: Acoustics

Frequency-dependent dynamic forcesYou can now read frequency-dependent dynamic forces for a frequency response analysis or PowerSpectral Density (PSD) data for a random response analysis from an external file that is in theopen-source HDF5 format and commonly has a *.sc_h5 extension. This allows you to more efficientlysolve vibro-acoustic problems. Typically, these loads are spatially and time-varying computationalfluid dynamics, acoustic, force loads, or stochastic pressure loads that were transformed to SimcenterNastran loads and stored in the external file by a pre/post software, such as Simcenter 3D Pre/Post.

For example, you may want to transform deterministic aerodynamic forces from Simcenter Star-CCM+that cause an automotive side window to vibrate and use these loads in a vibro-acoustic solution toexamine the acoustic response at specific locations to the structural excitation.

This new capability is supported by SOL 108 and SOL 111 solutions with standard (fixed low-order)FEM or FEM Adaptive Order (FEMAO) method (FEMAO), which is a higher-order polynomial method.

In a random response run:

1. Use the ASSIGN file management statement to select the .sc_h5 file that contains the SimcenterNastran loads.

2. Use the new RLOADEX bulk entry to define frequency-dependent dynamic forces obtainedfrom a file of the form:

3. Use the new RANDPEX bulk entry to reference a PSD specification that is a simple PSD acrossall degrees of freedom for use in a random analysis.

4. Use the DLOAD case control command to apply the dynamic forces to the response problem.

5. Use the DLOAD bulk entry to define a dynamic loading condition for the RLOADEX bulk entry.

6. Use the new DTI,DISTL bulk entry for the load description of the RLOADEX and RANDPEXbulk entries

7. Use the RANDOM case control command to select the identification number of a RANDPEXbulk entry.

8. Depending on the organization of your subcases for a random analysis, you may need to includeANALSIS = RANDOM in the subcases that contain the RANDOM case control command.

For more information, see the updated ASSIGN case control command, the new RANDPEX,RLOADEX, and DTI,DISTL bulk entries.

For more information on ANALYSIS = RANDOM, see the RANDOM case control command.



ASSIGN

Assigns Physical File

Assigns physical file names to DBset members, special FORTRAN files that are usedby other FMS statements or DMAP modules, or HDF5 files.

FORMAT:

Format 1

Assign a DBset member name

ASSIGN log-name=’filename1’ [ TEMP DELETE SYS=’sys-spec’ ]

Format 2

Assign a FORTRAN file

Format 3

Assign an HDF5 filename



Acoustics

EXAMPLES:1. Assign the DBALL DBset:

ASSIGN DB1=’filename of member DB1’

INIT DBALL LOGI=(DB1)

2. Assign FORTRAN file 12 to the OUTPUT4 module using the ASCII option:

ASSIGN OUTPUT4=’filename of FORTRAN file’,

UNIT=12, FORM=FORMATTED

3. Assign HDF5 file to unit number 101:

ASSIGN SC_H5=’filename of HDF5 file .sc_h5 extension typical’,

UNIT=101, DEFER

DESCRIBERS:

Describer Meaning

log-name The name of a DBset member name. log-name is alsoreferenced on an INIT statement after the LOGICAL keyword.

filenamei The physical filename assigned to the DBset member.

TEMP Requests that filenamei is deleted at the end of the run.

DELETE Requests that filenamei, if it exists before the start of the run, isto be deleted.

logical-key Specifies defaults for STATUS, UNIT, and FORM of FORTRANfiles for other FMS statements, DMAP modules, punching andplotting operations.

filename2 The physical file name assigned to the FORTRAN file.

filename3 The physical file name assigned to the HDF5 file with commonlya .sc_h5 extension.

STATUS Specifies whether the FORTRAN file is being created(STATUS=NEW) or has been created prior to therun (STATUS=OLD). If its status is not known, thenSTATUS=UNKNOWN is specified.

UNlT=u u is the unit number of the file. See Remark 9.

FORM Indicates whether the FORTRAN file is written in ASCII(FORM=FORMATTED), binary (FORM=UNFORMATTED), orlittle endian binary (LITTLEENDIAN).

DEFER The specified file will not be opened/created during initialization.The file must be opened by the module or DMAP accessingthe file.


Acoustics


Describer Meaning

sys-spec System specific or machine-dependent controls. See Remark 1 .

REMARKS:1. The ASSIGN statement and its applications are discussed further in “Introduction

to Database Concepts” in the Simcenter Nastran User’s Guide.

2. The logical-key names and their default attributes that may be assigned by theuser are as follows:

logical-key Name Default Status Default Unit Default Form ApplicationDBC NEW 40 UNFORMATTED DBC module —

PARAM,POST,0INPUTT2 OLD none UNFORMATTED INPUTT2 module

INPUTT4 OLD none UNFORMATTED INPUTT4 module

OUTPUT2 NEW none UNFORMATTED OUTPUT2 module

OUTPUT4 NEW none UNFORMATTED OUTPUT4 module

DBUNLOAD NEW 50 UNFORMATTED DBUNLOAD FMS statement

DBLOAD OLD 51 UNFORMATTED DBLOAD FMS statement

USERFILE none none none User-defined

HDF NEW 52 UNFORMATTED HDF5 output file withcommonly a .hdf extension

SC_H5 OLD none UNFORMATTED HDF5 output file withcommonly a .sc_h5extension. DEFER mustalways be included. Thislogical-key relates to theRANDPEX and RLOADEXbulk entries.

The defaults may be overridden on the ASSIGN statement.

3. Certain reserved names may not be used for log-names or logical-key names:SEMTRN, LNKSWH, MESHFL, LOGFL, INPUT, PRINT, INCLD1, and CNTFL. Ifthey are used, then a fatal message is issued. Also, unit numbers 1 through 10,14 and 16 should not be assigned. PUNCH and PLOT may be used but are notrecommended.

4. If one of the logical-key names indicated in Remarks 2. and 3. is not specifiedon this statement, then it is assumed to be a DBset member log-name as shownin Format 1.

5. The logical-key names DBUNLOAD and DBLOAD may be assigned only once inthe FMS section. The others may be assigned as many times as needed for theapplication. However, in all logical-key assignments, the unit number u must beunique. If it is necessary to execute the INPUTT4 and OUTPUT4 modules on thesame unit, then specify ASSIGN OUTPUT4 only. The same is recommended forthe INPUTT2 and OUTPUT2 modules.

6. STATUS, UNIT, and FORM are ignored if assigning a log-name (DBset membername).



Acoustics

7. FORM=FORMATTED must be specified for a unit when:

• Ascii output is desired on the INPUTT4 and OUTPUT4 DMAP modules thatprocess the unit. See the Simcenter Nastran DMAP Programmer’s Guide.

• FORMAT=NEUTRAL is selected on the DBUNLOAD and DBLOAD FMSstatements that process the unit. See “Database Archival and Retrieval” inthe Simcenter Nastran User’s Guide.

• The neutral file format is desired for the INPUTT2 and OUTPUT2 modules.

8. See the Simcenter Nastran Installation and Operations Guide for furtherinformation on machine-dependent aspects of the ASSIGN statement.

9. The following unit numbers are reserved for specific tasks. Only use thesenumbers when performing the associated task. For example, UNIT=7 is usedfor punch files.

ASSIGN PUNCH='results_output.pch',NEW,UNIT=7

UNIT NO DESCRIPTION1 Default UNIT for SCR.F012 Default UNIT for SCR.F023 Mesh file SCR.F034 Log file (typically standard out)5 Input (deck) file6 Print file (f06 file)7 Punch file8 Node-locked license file9 Include files10 Control file or the ASG file11 INPUTT2 unit12 OP2 file14 Plot file15 Mesh file16 Assembly file18 Acoustics coupling file - 119 Acoustics coupling file - 220 Data base migration files21 Adina input file22 Adina output file - 123 Adina output file - 224–29 BCS linear solver24–33 BCS eigensolver31–35 Reserved for AMLS files40 DBC (xdb) File141 Reserved for SML (SAMCEF Material Library)42 Reserved for SML (SAMCEF Material Library)


Acoustics


43 Reserved for SML (SAMCEF Material Library)44 Reserved for SML (SAMCEF Material Library)45 Reserved for SML (SAMCEF Material Library)46 Reserved for AMLS files50 DBC (xdb) File251 DBC (xdb) File352 HDF File (hdf)56 Print file (f56 file)66 Linear contact refinement file70 Reserved for Akusmod files71-80 Reserved for BUN files (TEMPEX and DTEMPEX)81-90 Reserved for SML (SAMCEF Material Library)

101-110 Reserved for HDF5 files (commonly .sc_h5), but they arenot mandatory.

151–154 Solution monitor files



Acoustics

RANDPEX

Power Spectral Density (PSD) Specification from an External File

References a PSD specification from an external sc_h5 file in HDF5 format for use in arandom analysis.

FORMAT:

1 2 3 4 5 6 7 8 9 10

RANDPEX SID LUNF LDID FAXIS PAXIS

EXAMPLE:

RANDPEX 5 101 7

FIELDS:

Field Contents

SID Random analysis set identification number. (Integer > 0) See Remark 2.

LUNF Logical unit number for HDF5 file containing PSD specification. (Integer> 0; No default)

LDID Identification number of a loading description contained in the HDF5 filereferenced by LUNF. (Integer > 0; No default) See Remark 5.

FAXIS Specifies a linear or logarithmic interpolation for the frequency axis.(Character; “LINEAR” or “LOG”; Default = ”LINEAR”)

PAXIS Specifies a linear or logarithmic interpolation for the PSD data axis.(Character; “LINEAR” or “LOG”; Default = ”LINEAR”)

REMARKS:1. RANDPEX is only supported in SOL 108 and SOL 111.

2. The set identification numbers must be selected with the case control commandRANDOM = SID. SID must be unique with respect to all other RANDPS andRANDPEX bulk entries. In other words, a RANDOM case control commandcannot reference both RANDPEX and RANDPS bulk entries; it can only referenceone or the other.

3. An entire diagonal PSD matrix will be referenced. This matrix will contain onePSD function for each subcase. Only auto spectral density calculations willbe performed and the subcases in the referenced PSD matrix must conform tothe subcases of the force response calculations performed prior to the randomanalysis.

4. For a discussion of random analysis, see the Advanced Dynamic Analysis User’sGuide.


Acoustics


5. The LDID entry references a DTI, DISTL bulk entry that contains the descriptionstring of the required PSD matrix specification in the HDF5 file referenced by LUNF.



Acoustics

RLOADEX

Frequency Response Dynamic Excitation, File Input

Defines frequency-dependent dynamic forces obtained from a file of the form:

for use in frequency response problems.

FORMAT:

1 2 3 4 5 6 7 8 9 10

RLOADEX SID DELAY DPHASE A LUNF LDID LCID SET1ID

EXAMPLES:

RLOADEX 5 90.0 2.0 102 3 12 2

FIELDS:

Field Contents

SID Load set identification number. (Integer > 0; No default) See Remark6.

DELAY Time delay, τ. (Real or blank; for default behavior, see Remark 3)Value of τ for all degrees of freedom (DOFs) defined on the LUNF file.

DPHASE Phase angle, θ, in degrees. (Real or blank; for default behavior, seeRemark 3) Value of θ for all DOFs defined on the LUNF file.

A Scale factor. (Real or blank; Default = 1.0)

LUNF Logical unit number of an HDF5 file that contains frequency-dependentforce excitations. (0 < Integer ≤ 9999; No default) See Remark 6.

LDID Applied load descriptor identification number of a loading descriptioncontained in the HDF5 file referenced by LUNF. (0 < Integer ≤ 9999;No default) See Remark 6.

LCID Load case identification number of a specific loading in the loadingdescription (Integer>0; No default) See Remark 6.

SET1ID Identification number of a SET1 bulk entry that defines a list ofstructural grids at which the loads are to be extracted and appliedto for all DOFs of the grid. A value of 0 implies that all structuralgrids contained in the HDF5 file will have loads applied. (Integer ≥0; Default = 0)

REMARKS:1. RLOADEX is only supported in SOL 108 and SOL 111.


Acoustics


2. RLOADEX bulk entries must be selected with DLOAD = SID in the case controlsection.

3. If DELAY or DPHASE fields are blank, the corresponding value for τ or θ used bythe software is real zero. The software converts the phase angle to radians.

4. RLOADEX excitations may be combined with RLOAD1 and RLOAD2 excitationsusing a DLOAD bulk entry.

5. The SID must be unique for all RLOADEX, RLOAD1, RLOAD2, TLOAD1,TLOAD2, ACSRCE, and SELOAD entries.

6. The logical unit number LUNF must reference an existing ASSIGN SC_H5 FileManagement System (FMS) statement. The frequency-dependent force excitationdescription referenced by LDID must be contained in this file that also includes theDOF and frequencies at which the excitations are applied.

If the frequencies of the force excitation matrix do not match the solutionfrequencies, linear interpolation will be used to obtain the applied forces at thesolution frequency. No extrapolation will be performed if the solution frequency isless than or greater than the frequency range of the force excitation matrix, and thevalues of the force excitation matrix at the corresponding end point will be used.

A DTI, DISTL bulk entry will be used to define the loading description referencedby LDID. The LCID identifier must correspond to a specific loading within thedescriptor LDID.



Acoustics

DTI,DISTL

Load description

Defines a load description identification number and loading description contained inan HDF5 file.

FORMAT:

1 2 3 4 5 6 7 8 9 10

DTI DISTL LIDID LDID DESCRIPTDESCRIPT(cont.)DESCRIPT(cont.)

DESCRIPT(cont.)

DESCRIPT(cont.)

-etc.- “ENDREC”

EXAMPLE:

DTI DISTL 3 3 LOADING AT ENGIN ENACELL E ON POR T WING

ENDREC

FIELDS:

Field Contents

LDID Load description identification number. This appears in both fields 3and 4 and must be the same value. (Integer > 0; No default) SeeRemark 2.

DESCRIPT Alphanumeric description of the loading. The description continuesuntil ENDREC is encountered in a field. (Character; 1024 charactersmaximum; No default) See Remark 3.

REMARKS:1. DTI,DISTL is only supported in SOL 108 and SOL 111.

2. DTI,DISTL is referenced by an RLOADEX or RANDPEX bulk entry when youaccess loading data from an HDF5 file. LDID must be unique with respect to allother DTI,DISTL bulk entries.

3. DESCRIPT is the loading description contained in the HDF5 file referenced by anRLOADEX or RANDPEX bulk entry. The loading description (that is, the datasetname) defined in the HDF5 file must be in all uppercase letters.


Acoustics


RANDOM

Random Analysis Set Selection

Selects the RANDPS, RANDPEX, and RANDT1 bulk entries to be used in randomanalysis.

FORMAT:RANDOM[(RPOSTS1 = i,RMSINT = j,RMSSF = r)] = n

EXAMPLES:RANDOM=177RANDOM(RPOSTS1=1,RMSINT=1,RMSSF=2.0)=123

DESCRIBERS:

Describer Meaning

RPOSTS1 = i Specifies the output format for random results. (Integer; Default =0)RPOSTS1 = 0 for SORT2 output format.RPOSTS1 = 1 for SORT1 output format.

RMSINT = j Specifies the interpolation method for numerical integration whencomputing RMS response and the zero-mean crossing for theRMS von Mises stress from PSDF. (Integer; Default = 0)RMSINT = 0 for interpolation in Cartesian space.RMSINT = 1 for interpolation in log-log space.

RMSSF = r Specifies a scaling factor for RMS and CRMS random results.(Real > 0.0; Default = 1.0)

n Set identification number of RANDPS, RANDPEX, and RANDT1bulk entries to be used in random analysis. (Integer>0; No default)

REMARKS:1. RANDOM must select RANDPS or RANDPEX bulk entries to perform random

analysis.

2. If a describer is specified, it takes precedence over the corresponding parameter.

3. If RANDPS or RANDPEX bulk entries are used in a superelement analysis, theRANDOM command may be specified above the subcase level if a condensedsubcase structure (SUPER=ALL) is used. If a condensed subcase structure is notused, then a unique RANDOM selection of a unique RANDPS entry must bespecified within each of the desired superelement subcases.

4. How you organize subcases for a random analysis depends on whether youinclude ANALSIS = RANDOM in the subcases that contain the RANDOMcommand. For example, suppose that a structure is excited by two loads, and youwant to evaluate the random response of the structure for two PSD functionsusing SOL 111.

Subcase organization using ANALYSIS = RANDOM



Acoustics

When using ANALYSIS = RANDOM in a subcase, place the subcase that containsthe ANALSIS = RANDOM and RANDOM commands after the subcases thatcalculate the frequency responses.

SUBCASE 1$$ Subcase 1 calculates the normal modes$ANALYSIS=MODESDISP=ALL$SUBCASE 2$$ Subcase 2 calculates the frequency response of the$ structure to the loading specified by DLOAD 111 at$ the frequencies specified by FREQUENCY set 13$FREQUENCY=13DLOAD=111$SUBCASE 3$$ Subcase 3 calculates the frequency response of the$ structure to the loading specified by DLOAD 211 at$ the frequencies specified by FREQUENCY set 13$FREQUENCY=13DLOAD=211$SUBCASE 4$$ Subcase 4 uses the frequency responses from Subcases$ 2 and 3 to calculate the random response of the$ structure for the PSD function specified by RANDOM 100.$ RANDOM 100 references RANDPS and RANDPEX bulk entries$ with SID 100.$ANALYSIS=RANDOMRANDOM=100$SUBCASE 5$$ Subcase 5 uses the frequency responses from Subcases$ 2 and 3 to calculate the random response of the$ structure for the PSD function specified by RANDOM 200.$ RANDOM 200 references RANDPS and RANDPEX bulk entries$ with SID 200.$ANALYSIS=RANDOMRANDOM=200

Subcase organization without using ANALYSIS = RANDOM

When not using ANALYSIS = RANDOM in a subcase, place the subcase thatcontains the RANDOM command in the first subcase that calculates a frequencyresponse. Each random spectrum requires a unique frequency identification


Acoustics


number, even if you want to evaluate the random response over the same set offrequencies. Thus, in this example, FREQUENCY=13 and FREQUENCY=23reference FREQi bulk entries that contain the same set of frequencies.

SUBCASE 1$$ Subcase 1 calculates the normal modes$ANALYSIS=MODESDISP=ALL$SUBCASE 2$$ Subcase 2 calculates the frequency response of the$ structure to the loading specified by DLOAD 111 at$ the frequencies specified by FREQUENCY set 13 and$ requests the software calculate the random response$ of the structure for the PSD function specified by$ RANDOM 100. RANDOM 100 references RANDPS and RANDPEX$ bulk entries with SID 100.$RANDOM=100FREQUENCY=13DLOAD=111$SUBCASE 3$$ Subcase 3 calculates the frequency response of the$ structure to the loading specified by DLOAD 211 at$ the frequencies specified by FREQUENCY set 13$FREQUENCY=13DLOAD=211$SUBCASE 4$$ Subcase 4 recalculates the frequency response of the$ structure to the loading specified by DLOAD 111 at$ the frequencies specified by FREQUENCY set 23 and$ requests the software calculate the random response$ of the structure for the PSD function specified by$ RANDOM 200. RANDOM 200 references RANDPS and RANDPEX$ bulk entries with SID 200.$RANDOM=200FREQUENCY=23DLOAD=111$SUBCASE 5$$ Subcase 5 recalculates the frequency response of the$ structure to the loading specified by DLOAD 211 at$ the frequencies specified by FREQUENCY set 23$FREQUENCY=23DLOAD=211



Acoustics

Notice that in this subcase organization, the software must recalculate thefrequency responses for each PSD function. Thus, to minimize the number ofcalculations that the software must perform, use the subcase organization thatincludes ANALYSIS = RANDOM.

Acoustic Transfer Vector (ATV) improvementIn NX Nastran 12, the acoustic transfer vector (ATV) capability was introduced. An ATV is a simplifiedrepresentation of an acoustic fluid and reduces computational effort. To use the ATV capability in yourvibro-acoustic analyses, an ATV computation run with SOL 108 and a response run with SOL 108 orSOL 111 are required, and the A-set cannot be empty. For example, the A-set is empty when youconstrain the structure in all degrees of freedom. With an empty A-set, the NX Nastran 12 solver exitsthe ATV computation. Now, the software ignores an empty A-set, finishes the ATV computation, andproceeds with a SOL 108 ATV response run.

Note

A SOL 111 ATV response run does not support an empty A-set.

ATV response runs are supported by SOL 108 and SOL 111 solutions with standard (fixed low-order)FEM or FEM Adaptive Order (FEMAO) method, which is a higher-order polynomial method.

Vibro-Acoustic Transfer Vector (VATV)The Vibro-acoustic transfer vectors (VATVs) let you efficiently compute vibro-acoustic pressure dueto aerodynamic or acoustic loads on flexible structures in the context of two-way (strong) coupledvibro-acoustic problems. VATVs contain matrices that link the structural grids of a flexible structurewith microphone points or 2D microphone elements.

The VATVs are independent of the loading and you can reuse them for various loads in multiplevibro-acoustic problems as long the structure, acoustic fluid, and the location of microphones remainthe same.

For example, suppose you want to examine how the acoustic response at specific locations tostructural excitation varies with respect to loads. Rather than solving the entire acoustics problemrepeatedly, you can solve the vibro-acoustics problem once to create a VATV, and then use the VATVrepeatedly to examine how the response varies.

Using a VATV in your vibro-acoustic problems involves two runs:

1. The solver computes the VATV using SOL 108 or SOL 111. During this run, Simcenter Nastranwrites the VATV matrices, which stores the results in pressure format for fluid grid pointsreferenced by microphone elements and normal nodal force format for structural grids, to aname_vatv.op2 file.

2. You use the computed VATV in a frequency response or random analysis. During this run,the solver retrieves and uses the matrix representation of the VATV to calculate the acousticresponse at microphone points and elements to the excitation of the structural portion of themodel. The VATV response analysis can be only SOL 108 and can use one VATV only.


Acoustics


In the VATV computation run:

• Use the VATVOUT case control command to trigger the creation of the VATV. The commandreferences a VATVFS bulk entry and specifies the Fortran unit number for the .op2 file to whichthe VATV results are written.

• Use the VATVFS bulk entry to specify the BSURF or BSURFS bulk entries that define thestructural element faces of a pressure boundary. The structural element faces describe thefree surface region.

• Use an ACMODL bulk entry to specify the coupling interface parameters.

• Use a FREQi bulk entry to specify a frequency range at which the software calculates the matrixrepresentation of the VATV.

Note

During the VATV response run, the software derives the exact frequencies from theVATV matrix computed frequencies in the specified frequency range.

In the VATV response run:

• Use the VATVBK bulk entry to select the .op2 file that contains the matrix representation ofthe VATV.

• Use the FREQV bulk entry to specify a frequency range of interest.

• Use the PRESSURE case control command to request acoustic pressure at microphone points.

• Use the ACPOWER case control command to request acoustic power at 2D microphoneelements.

• Use the PANCON case control command to request the acoustic pressure or power atmicrophone points that are attributable to the vibration of selected structural panels.

o Use PANEL bulk entries to define the structural panels.

o Use SETMC case control commands to specify the microphone points and response type.

Specify RTYPE = PRES for acoustic pressure.

• Use the GRDCON case control command to request the response at microphone points tovibration at grids in structural panels.

When you use a VATV, acoustic particle velocity and acoustic intensity results cannot be computed,and the ACINTENSITY and ACVELOCITY case control commands are ignored if they are specified.

For more information, see the new VATVOUT case control command, and the new VATVFS, FREQV,and VATVBK bulk entries.



Acoustics

VATVOUT

VATV Creation Specification

Defines requirements for the creation of a Vibro-Acoustic Transfer Vector (VATV).FORMAT:

EXAMPLES:VATVOUT(VATVOP2=33,VATVFS=110)=200

DESCRIBERS:

Describer Meaning

VATVOP2 =unit

unit (integer > 0) is the Fortran unit number for the .op2 file towhich the VATV results are written. See Remark 2.

VATVFS = id id (integer > 0) is the identification number of the VATVFS bulkentry that defines the set of structural element faces that will beused to apply pressure.

ALL Output VATV results for all microphone elements. See Remark5. (Default)

n n (integer > 0) is the identification number of a previouslyappearing SET case control command that contains microphoneelement identification numbers at which to output the VATVresults. See Remark 5.

REMARKS:1. VATVOUT is valid for SOL 108 and SOL 111 only. If VATVOUT is included in the

input file for any other solution, the software issues a user fatal message.

2. For specifying VATVOP2 = unit, an appropriate ASSIGN OUTPUT2 statement mustbe present in the File Management Section (FMS) for the absolute value of unit.

3. VATVOUT can only be specified above subcases. If VATVOUT is included in asubcase, it is ignored.

4. Only one VATVOUT can be included in an input file.

5. VATV matrix output is controlled by the specification of ALL or n only. Any otheroutput-related case control commands like DISPLACEMENT or PRESSURE areignored.


Acoustics


VATVFS

Structural surface definition for VATV calculation

Defines the structural surfaces of a pressure boundary for the Vibro-Acoustic TransferVector (VATV) calculation.

FORMAT:

1 2 3 4 5 6 7 8 9 10

VATVFS ID SID1 SID2

EXAMPLE:

VATVFS 100 201 202

FIELDS:

Field Contents

ID Identification number of a set of free surfaces (Integer > 0). SeeRemark 1.

SID1 Free surface identification number for 3D structural elements. (Integer> 0). The SID1 references a BSURFS bulk entry to define thestructural element faces used to describe the free surface region. Theelement faces on the BSURFS bulk entry must all be on structuralelements.

SID2 Free surface identification number for 2D structural elements. (Integer> 0). The SID2 references a BSURF bulk entry to define the structuralelement faces used to describe the free surface region. The elementfaces on the BSURF bulk entry must all be on structural elements.

REMARKS:1. ID can be referenced by the VATVFS describer specification on the VATVOUT

case control command.



Acoustics

FREQV

Frequency range for VATV response analysis

Defines frequency range of interest for a Vibro-Acoustic Transfer Vector (VATV)response analysis. The exact frequencies are derived from the VATV matrix computedfrequencies in the specified frequency range.

FORMAT:

1 2 3 4 5 6 7 8 9 10FREQV SID FMIN FMAX

EXAMPLE:

FREQV 6 10. 600.

FIELDS:

Field Contents

SID Set identification number. (Integer > 0)

FMIN Lower bound of frequency range in cycles per unit time. (Real ≥ 0.0;Default = 0.0)

FMAX Upper bound of frequency range in cycles per unit time. (Real > 0.0;FMAX > FMIN; Default = 1.0E20)

REMARKS:1. VATV response analysis will only use frequencies specified by the FREQV card.

All other FREQi bulk entries will be ignored.


Acoustics


VATVBK

VATV response analysis specification

Defines the Fortran unit number for the ASSIGN INPUTT2 file that contains theVibro-Acoustic Transfer Vector (VATV) results to be used in a VATV response analysis.

FORMAT:

1 2 3 4 5 6 7 8 9 10

VATVBK UNITNO

EXAMPLE:

VATVBK 33

FIELDS:

Field Contents

UNITNO Fortran unit number for the INPUTT2 file that contains the VATVresults. See Remark 1. (Integer > 0; No default)

REMARKS:1. For specifying UNITNO, an appropriate ASSIGN INPUTT2 statement must be

present in the File Management Section (FMS) for the absolute value of UNITNO.

Surface dipole acoustic sourceFor aeroacoustic analyses, you can now create an equivalent surface dipole acoustic source asa boundary condition. A surface dipole is an acoustic source that you use to model the soundgenerated by rigid surfaces located in a low-speed flow field application. In Simcenter Nastran,surface dipoles are based on the Neumann formulation, which assumes that the mass density andspeed of sound around the rigid surfaces are uniform.

To model the sound generated by the interaction of a compressible or incompressible flow with a rigidsurface, define the surface dipole boundary condition with fluid pressures.

The aerodynamic or hydrodynamic fluid pressures are typically computed by computational fluiddynamics (CFD) software, such as Simcenter Star-CCM+, and processed by a pre/post software forlater use by Simcenter Nastran. A pre/post software may read, map, Fourier transform, time-segment,and write the dynamic fluid pressures to an sc_h5 file (*.sc_h5) in HDF5 format.

For example, you may want to examine sound generated by the interaction of low-speed flow withsurrounding surfaces, such as HVAC duct walls, or an automotive side mirror. In contrast to solvingthe entire acoustics problem with volumetric flow information and generating an equivalent pointsource for each CFD cell, you use a surface dipole source on, for example, a side mirror surface as aboundary condition in your analysis. This reduces the data transfer from the CFD software to thepre/post software, and consequently the computational effort by Simcenter Nastran.

This new capability is supported in the following solutions and requires the FEM Adaptive Order(FEMAO) method:



Acoustics

• SOL 108 for uncoupled acoustic and coupled vibro-acoustic analyses.

• SOL 111 for coupled vibro-acoustic analyses.

Note

The coupling can be weak or strong.

Surface dipole workflow:

1. Use the ASSIGN file management statement to select the .sc_h5 file that contains the processeddynamic fluid pressures.

2. Use the new ACSPO2 bulk entry to define a surface dipole for the frequency response analysis.

3. Use the new PACSPO2 bulk entry to define the parameters of the surface dipole for thefrequency response analysis.

4. Use the ALOAD case control command to apply the dynamic loads to the response problem.

5. Use the ALOAD bulk entry to define a dynamic loading condition for the ACSPO2 bulk entry.

6. Use the new DTI,DISTL bulk entry for the load description of the ACSPO2 bulk entry.

For more information, see the new ACSPO2 and PACSPO2 bulk entries.


Acoustics


ACSPO2

Surface Dipole

Defines a surface dipole from an external sc_h5 file in HDF5 format for use in afrequency response analysis.

FORMAT:

1 2 3 4 5 6 7 8 9 10

ACSPO2 SID PID SET1ID LUNF LDID LCID

EXAMPLE:

ACSPO2 200 111 2 25 100 3

FIELDS:

Field Contents

SID Load set identification number. (Integer > 0; No default)

PID Parameter set identification number of PACSPO2. (Integer > 0; Nodefault)

SET1ID Identification number of a SET1 bulk entry that defines a list of elementfaces at which the loads are to be applied. See Remark 2.

LUNF Logical unit number for HDF5 file containing frequency-dependent forceexcitations. (0 < Integer ≤ 9999; No default) See Remark 3.

LDID Applied load descriptor identification number of a loading descriptioncontained in the HDF5 file referenced by LUNF. (0 < Integer ≤ 9999;No default) See Remark 3.

LCID Load case identification number of a specific loading in the loadingdescription. (Integer>0) See Remark 3.

REMARKS:1. ACSPO2 is supported in the following solutions and requires the FEM Adaptive

Order (FEMAO) method:

• SOL 108 for uncoupled acoustic and coupled vibro-acoustic analyses .

• SOL 111 for coupled vibro-acoustic analyses.

2. The SET1ID references a SET1 bulk entry to define the fluid element faces.The element faces on the BSURFS bulk entry must all be on fluid elements. Ifthe SET1ID = BLANK, the solver will use the face definition in the file specifiedby LUNF.

3. The logical unit number LUNF must reference an existing ASSIGN SC_H5 FileManagement System (FMS) statement. The frequency-dependent force excitation



Acoustics

description referenced by LDID must be contained in this file that also includes theDOF and frequencies at which the excitations are applied.

If the frequencies of the force excitation matrix do not match the solutionfrequencies, interpolation will be used to obtain the applied forces at the solutionfrequency. No extrapolation will be performed if the solution frequency is less thanor greater than the frequency range of the force excitation matrix, and the valuesof the force excitation matrix at the corresponding end point will be used.

A DTI, DISTL bulk entry will be used to define the loading description referencedby LDID. The LCID identifier must correspond to a specific loading within thedescriptor LDID.


Acoustics


PACSPO2

Surface Dipole Property

Defines the properties of a surface dipole for a frequency response analysis.FORMAT:

1 2 3 4 5 6 7 8 9 10

PACSPO2 PID TYPE EDGE

EXAMPLE:

PACSPO2 200 INCOMP

FIELDS:

Field Contents

PID A property identification number that matches the identificationnumber of the corresponding ACSPO2 bulk entry. (Integer > 0; Nodefault)

TYPE Scattering flow type. (Character; Default = "INCOMP")

If TYPE = "COMP", define dipole sources and scattering incompressible flow.

If TYPE = "INCOMP", define dipole sources and scattering inincompressible flow.

EDGE Edge correction. (Character; Default = "NO")

If EDGE = "YES", use edge correction.

If EDGE = "NO", do not use edge correction.

REMARKS:1. ACSPO2 in combination with PACSPO2 requires the FEM Adaptive Order

(FEMAO) method.

Finite Element Method Adaptive Order (FEMAO) enhancementsIn NX Nastran 12, the FEMAO method was introduced for SOL 108. FEMAO is a higher-orderpolynomial method for acoustic and vibro-acoustic analyses. It provides more accurate results andfaster solve times by adapting the computational effort to the complexity of the analysis.

Now, several FEMAO enhancements are available:

• FEMAO with SOL 111 modal frequency response is supported.

• With the exception of the number of structural modes (TOPS describer), SOL 108 and SOL 111support modal pressure contributions. The modal pressure contributions are computed on allpanels. You cannot specify a subset of panels.



Acoustics

• With the exception of the number of structural panels (TOPP describer), SOL 108 and SOL 111support panel pressure contributions.

• The solver writes performance indicators, such as computation time (in seconds) and memory(in GB) per frequency per subcase to the .log file and .op2 file for post-processing in a pre/postsoftware.

• For quality assessment, element order per element results from an acoustic analysis will bewritten to the .op2 file.

• Some acoustic analyses require pressure gradient (spatial derivative of the pressure) next topressure computation. On the surface of a first order element mesh, where the mesh representsa set of combined elements in a pre/post processor, only the computed pressure field iscontinuous. The pressure gradient field, which is associated with acoustic particle velocity, ispiecewise constant with abrupt changes between the element faces. However, for a surface withfree second order element faces, also the pressure gradient is continuous. Thus, the use ofsecond order element faces results in increased computational accuracy.

Incident acoustic pressure loads from monopole sources, for example, outside of the FEMdomain, are also more accurately captured with second order elements.

For this reason, the default value for the minimum adaptive order number in the ACORDER bulkentry is changed from 1 to 2, but the software lets you still override the default value with anumber from 1 through 10.

For more information, see the updated MODCON and PANCON case control commands, andACORDER bulk entry.


Acoustics


MODCON

Modal Contribution Output Request

Requests the form and type of modal contribution output for the residual.FORMAT:

EXAMPLES:MODCON=123MODCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPS=5)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Output a tabular listing of modal DOF for each frequency or time.(Default)

SORT2 Output a tabular listing of frequency or time for each modal DOF.This option is not available for SOL 110.

REAL orIMAG



PRINT Write modal contribution output to the print (.f06) file. (Default)

PUNCH Write modal contribution output to the standard punch (.pch) file.

NOPRINT Generate, but do not print, modal contribution results.

ABS Output modal contributions in absolute terms. (Default)

NORM Output modal contributions in normalized terms.

BOTH Output modal contributions in both absolute and normalized terms.



Acoustics

Describer Meaning

TOPS (orTOP) = ps

The number of structural modes to list in the output that have thegreatest contribution to the response at each frequency or time. Ifps > 1, the output is sorted in descending order from the structuralmode that has the greatest contribution. If ps = 0, no structuralmode contributions are output, only totals. See Remark 1. (Integer≥ 0; Default ps = 5)

TOPF = pf The number of fluid modes to list in the output that have the greatestcontribution to the response at each frequency or time. If pf > 1, theoutput is sorted in descending order from the fluid mode havingthe greatest contribution. If pf = 0, no fluid mode contributions areoutput, only totals. See Remark 1. (Integer ≥ 0; Default pf = 5)

SOLUTION= ALL

Perform the modal contribution calculations at all frequencies ortimes that are defined by the FREQUENCY or TSTEP case controlcommands, respectively. See Remark 12. (Default)

SOLUTION= setout

Perform the modal contribution calculations at the frequencies ortimes listed on a previously appearing SET case control commandwith setout as the identification number. See Remark 12. (Integer> 0)

SOLUTION= PEAKOUT

Perform the modal contribution calculations only at the frequenciesidentified with the PEAKOUT command. See Remark 12.

PANELMC =NONE

Requests that no modal contributions are calculated for panels.See Remarks 1 and 9. (Default)

PANELMC =setp

Requests that modal contributions are calculated for the panelslisted on a previously appearing SET case control command withsetp as the identification number. See Remarks 1 and 9. (Integer> 0)

PANELMC =ALL

Requests that modal contributions be calculated for all panelsdefined by PANEL bulk entries. See Remarks 1 and 9.

n Calculate modal contributions for the responses listed on apreviously appearing SETMC case control command with n as theidentification number. (Integer > 0)

ALL Calculate modal contributions for all the responses listed on theSETMC case control commands specified in and above the currentsubcase.

NONE Do not calculate modal contributions.

REMARKS:1. SOL 108, 110, 111, 112, and SOL 146 are supported.

• For SOL 108 and SOL 111, MODCON is supported by the FEM AdaptiveOrder (FEMAO) method with the following exceptions:


Acoustics


o The number of structural modes (TOPS describer) is not supported.

o The modal pressure contributions are computed on all panels. You cannotspecify a subset of panels.

• For SOL 110, modal contributions for superelements are not supported.

• The TOPF and PANELMC describers are only supported for SOL 111.

• The SOLUTION describer is only supported for SOL 111, 112, and 146.


3. MODCON = NONE overrides an overall output request. Thus, to turn offcontribution output for a specific subcase, place MODCON = NONE in the subcase.

4. MODCON supports results for microphone points.

5. Results for SPC forces do not include the effect of any enforced motion applied atthe DOF.


7. The SOLUTION and PANELMC describers can be abbreviated to SOLU andPANE, respectively.

8. The SET case control command referenced by SOLUTION = setout must containreal values for frequencies or times. Using integer values may lead to erroneousresults.

9. The PANELMC describer applies to acoustic responses and the contributionsfrom structural modes.




• If SOLUTION=setout, output results for all frequencies specified by theOFREQ command that are listed on a previously appearing SET commandwith setf as the identification number.





Acoustics

PANCON

Acoustic Contribution Output Request for Panels

Requests the form and type of acoustic contribution output for structural panels andthe residual.

FORMAT:

EXAMPLES:PANCON=123PANCON(SORT1,PHASE,PRINT,PUNCH,BOTH,TOPP=5)=ALL

DESCRIBERS:

Describer Meaning

SORT1 Output a tabular listing of panels for each frequency.

SORT2 Output a tabular listing of frequency for each panel. (Default)

REAL orIMAG



PRINT Write acoustic panel contribution output to the print (.f06) file.(Default)

NOPRINT Do not print the acoustic panel contribution results.

PUNCH Write acoustic panel contribution output to the standard punch(.pch) file.

ABS Output acoustic panel contributions in absolute terms. (Default)

NORM Output acoustic panel contributions in normalized terms.

BOTH Output acoustic panel contributions in both absolute and normalizedterms.

TOPP = ALL List all of the structural panels in the output. Sort the output indescending order from the structural panel that has the greatestcontribution. See Remark 2.


Acoustics


Describer Meaning

TOPP = pp The number of structural panels to list in the output that have thegreatest contribution to the response at each frequency. If pp > 1,the output is sorted in descending order from the structural panelthat has the greatest contribution. If pp = 0, no structural modecontributions are output, only totals. See Remark 2. (Integer ≥ 0;Default pp = 5)

SOLUTION= ALL


SOLUTION= setf


SOLUTION= PEAKOUT


PANEL =ALL

Output contributions for all panels defined by PANEL bulk entries.(Default)

PANEL =setp

Output contributions for the panels listed on a previously appearingSET case control command with setp as the identification number.(Integer > 0)

n Calculate panel contributions for the responses listed on a previouslyappearing SETMC case control command with n as the identificationnumber. Any response listed in this SETMC case control commandthat is not an acoustic response is ignored. (Integer > 0)

ALL Calculate panel contributions for all the responses listed on theSETMC case control commands specified in and above the currentsubcase. Any response listed in these SETMC case controlcommands that is not an acoustic response is ignored. (Default)

NONE Do not calculate panel contributions.

REMARKS:1. SOL 108 and 111 are supported.

2. For SOL 108 and SOL 111, MODCON is supported by the FEM Adaptive Order(FEMAO) method with the exception of the number of structural panels (TOPPdescriber).


4. PANCON = NONE overrides an overall output request. Thus, to turn offcontribution output for a specific subcase, place PANCON = NONE in the subcase.

5. PANCON supports results for microphone points.



Acoustics


7. The SOLUTION and PANEL describers can be abbreviated to SOLU and PANE,respectively.


9. The SET case control command referenced by PANEL = setp must contain thealphanumeric name of panels defined by PANEL bulk entries.








Acoustics


ACORDER

Order for Acoustics FEM Adaptive Order (FEMAO) Method

Defines the polynomial order for the FEMAO method.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACORDER ORDER NUMBER

EXAMPLES:

ACORDER MINIMUM 2

ACORDER MAXIMUM 8

FIELDS:

Field Contents

ORDER Type of adaptive order. (Character = "MINIMUM" or "MAXIMUM").See Remark 3.

NUMBER Adaptive order number. (1 ≤ Integer ≤ 10)

If ORDER = "MINIMUM", the default value for NUMBER = 2.

If ORDER = "MAXIMUM", the default value for NUMBER = 10.

REMARKS:1. ACORDER is supported in SOL 108 and SOL 111 with FEMAO for both uncoupled

acoustics and coupled vibro-acoustic analyses.

2. The specified order is applied to the entire model.

3. If ACORDER has no arguments or does not exist, the software uses all of thefollowing arguments:

a. ORDER = "MINIMUM" and NUMBER = 2.

b. ORDER = "MAXIMUM" and NUMBER = 10.

Coupled FEMAOYou can define coupling of a structure to an acoustic fluid in a vibro-acoustic FEMAO solution.

You can couple a structure to a fluid in a FEMAO (FEM Adaptive Order) solution. A FEMAO solutionis a higher-order polynomial method for acoustic and vibro-acoustic analyses. It provides moreaccurate results and faster solution times by adapting the computational effort to the complexity ofthe analysis. By using a FEMAO solution, the fluid elements can be relatively large, yet result inaccurate results at high frequencies.



Acoustics

In a vibro-acoustic simulation, the structure is expressed in modal DOFs and the acoustic fluid inphysical DOFs.

For FEMAO, SOL 108 Direct Frequency Response has been enhanced, and SOL 111 ModalFrequency Response is a new solution. The enhanced functionality can be used in SimcenterNastran FEM vibro-acoustics solutions, such as:

• An engine in a vehicle engine compartment radiating sound both inside the engine bay andoutside the vehicle.

This type of solution could be used to model an automotive engine in a vehicle, surrounded byan acoustic fluid which incorporates the geometric features of other structures, such as thebody-in-white and the passenger compartment acoustic cavity. You can excite the engine, whichradiates sound into the fluid, and capture the sound response both inside the engine bay, andoutside of the vehicle where it contributes to pass-by noise.

• A panel transmission loss simulation, using modal coordinates for the structure and fluid mesheswith AML (AMLREG) in physical coordinates to represent reverberant and anechoic side on thefront and back of the panel.

Fluid-structure interaction

You can now couple structural FEMs to acoustic fluids as component FEMs in an assembly FEM,and solve the solution using FEMAO.

Structural FEMs:

• Can be coupled to acoustic fluids as component FEMs in an assembly FEM and solved usingFEMAO.

• Can now be solved with fluids for acoustics and vibro-acoustics in both FEM and FEMAOsolutions SOL 108 and SOL 111.

SOL 111 FEMAO now supports:

• Two-way (strong) fluid-structure coupling.

• One-way (weak) fluid-structure coupling with only force excitation of the structure

You define the minimum and maximum order for the elements in the entire model.

Examples:

ACADAPT FINE

ACORDER MAXIMUM 10

ACORDER MINIMUM 2

You set the FEMAO options in the Bulk Data.

You define the adaption rule with the ACADAPT bulk entry.

You define the element order with the ACORDER bulk entry.


Acoustics


ACORDER

Order for Acoustics FEM Adaptive Order (FEMAO) Method

Defines the polynomial order for the FEMAO method.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACORDER ORDER NUMBER

EXAMPLES:

ACORDER MINIMUM 2

ACORDER MAXIMUM 8

FIELDS:

Field Contents

ORDER Type of adaptive order. (Character = "MINIMUM" or "MAXIMUM").See Remark 3.

NUMBER Adaptive order number. (1 ≤ Integer ≤ 10)

If ORDER = "MINIMUM", the default value for NUMBER = 2.

If ORDER = "MAXIMUM", the default value for NUMBER = 10.

REMARKS:1. ACORDER is supported in SOL 108 and SOL 111 with FEMAO for both uncoupled


2. The specified order is applied to the entire model.

3. If ACORDER has no arguments or does not exist, the software uses all of thefollowing arguments:

a. ORDER = "MINIMUM" and NUMBER = 2.

b. ORDER = "MAXIMUM" and NUMBER = 10.



Acoustics

ACADAPT

Order Adaptation Rule for Acoustics FEM Adaptive Order Solution (FEMAO) Method

Invokes the FEMAO method for both uncoupled acoustic and coupled vibro-acousticanalyses.

FORMAT:

1 2 3 4 5 6 7 8 9 10

ACADAPT RULE

EXAMPLE:

ACADAPT COARSE

FIELDS:

Field Contents

RULE Type of adaptation rule. (Character; "COARSE", "STANDARD", or"FINE"; Default = "STANDARD")

REMARKS:1. ACADAPT is supported in SOL 108 and SOL 111 with FEMAO for both uncoupled


Duct modes boundary conditionYou can now apply a rectangular, cylindrical or annular duct modes boundary at the inlet of a ductmodeled with fluid elements. Duct modes are supported in an uncoupled acoustics solution runningSimcenter Nastran Direct Frequency Response (SOL108) with FEMAO.

A duct mode definition is similar to an acoustic load since it results in a propagating acoustic wave.In duct acoustics, duct modes are important in applications such as HVAC and automotive exhaustsystems. Generally, applications in which exhaust noise reduction is important.

In long ducts, each acoustic mode can be expressed as the product of standing waves with apropagating component. A specific duct mode is characterized by the mode orders and the amplitude.

The general solution for a duct mode progagating in a duct with an infinite length (z-direction)is expressed as:

where,


Acoustics


describes the standing wave in x and y,

describes the propagating wave on the duct axis (z-direction),

is the amplitude,

are the mode orders relative to the two directions in the duct cross section,

are dimensions of the duct cross section, and

is the wave number.

Each duct mode has a characteristic cut-on frequency. As a result, specific duct modes propagateonly from a certain frequency onwards. This is demonstrated in the amplitude response plot belowwhere ω1, ω2, and ω3 correspond to the cut-on frequencies of three duct modes, each with theirown mode orders (m,n).

The software considers the boundaries you apply duct modes on as reflection-less. That is, wavecomponents that are reflected back to the duct mode boundary are completely absorbed.

There are two options to define duct modes on an inlet boundary:

• You can define a specific duct mode with given phase and amplitude.

The specific duct mode option is useful when you understand the amplitude and the frequencyrange associated with the incoming noise. For example, you could know the amplitude of theincident modes from previous experiments. You can define specific duct modes that have acorresponding cut-on frequency within this range.

• You can request the distributed option.



Acoustics

The distributed duct mode option is useful when your noise source encompasses a broadband offrequencies or you do not have experimental data for the incoming noise source.

With the distributed option, instead of defining a specific mode, you define the acoustic amplitudewhich is applied to all modes. For each solution frequency, the software applies all possiblecut-on modes as incoherent sources with equal acoustic power. The software computes theresponse of each mode separately, then sums them to compute the total response.

Multiple duct modes boundary conditions can be defined in the same model, but only one definitioncan exist at a specific fluid boundary. For example, you could model a system of ducts which includesmultiple inlets. A unique duct mode boundary condition could be defined on each inlet.

Duct outlet boundary

To allow the acoustic waves to exit a duct system without reflections, you have two options.

• You can define the new Anechoic End Duct (AED) boundary on the outlet. The AED is areflectionless boundary on a duct outlet. You can use this option when you are only interested inresults within the duct system, and not exterior acoustic radiation.

• You can define the Automatically Matched Layer (AML) at the outlet. When the AML is defined,the acoustic energy at the outlet can radiate to exterior microphone locations. You can use thisoption when you are interested in results within the duct system, and exterior acoustic radiation.

Inputs

• You model a system of ducts with a 3D fluid mesh. The duct inlet and outlet locations in whichyou plan to define either a duct mode or an anechoic end duct should be modeled rectangular,cylindrical or annular.

• The new PACDUCT bulk entry defines the cross sectional properties for the duct mode and theanechoic end duct (AED) boundaries.

o You enter the ID of a BSURFS bulk entry in the BID field. The BSURFS entry selects the fluidelement faces where the duct section boundary is applied.

o You specify that your cross section is a circular, annular, or rectangular with the GTYPE field,and enter the dimension of your cross section with the DIMi fields.

o Relative to the coordinate system you select in the CID field, you define the crosssection origin with the XLOC,YLOC,ZDOC fields, and the duct axis direction with theXVEC,YVEC,ZVEC fields.

o You can optionally offset the location of the axial position of the duct origin using the OFFSETfield.

• You define a duct mode with the new ACDUCT bulk entry.

o You reference the ID of a PACDUCT entry with the PID field.

o You specify that your boundary is either a specific duct mode, or distributed duct modeswith the WTYPE field.

o You define the units of the duct mode amplitude as pressure, intensity, or power using theMTYPE field.


Acoustics


o When you are defining a specific duct mode, you will define the mode number pair (m,n)using the MODX1, MODY1 fields.

o For both the specific duct mode and the distributed duct modes, you will define the amplitudeas a complex data pair. You designate the form of this data pair, (real and imaginary) or(magnitude and phase), with the FORM field.

• You reference the ID of your duct mode defined with the ACDUCT bulk entry from the casecontrol with the ALOAD case control command.

• You define your solution frequencies with the FREQi bulk entries. You select these solutionfrequencies from the case control with the FREQUENCY case control command.

• You define an anechoic end duct (AED) boundary with the new ACNDUCT bulk entry. Youreference the ID of a PACDUCT entry with the PID field.

• The new DUCTFMAX parameter is available to define the maximum duct mode frequency usingthe product (DUCTFMAX * maximum excitation frequency). This value determines the truncationof the duct modes wavebasis. It is typically defined slightly over the maximum frequency ofinterest. The DUCTFMAX default is 1.2.

Duct mode output

Two new output options are available when a duct modes boundary condition is defined on a ductinlet, and either an anechoic end duct boundary or an AML is defined on a duct outlet.

• The new DMTRLOSS case control command is available to request the duct modes transmissionloss output.

Transmission loss is computed as the power introduced by the duct mode boundary conditionsdivided by the sum of the modal transmitted power coefficients at the anechoic end duct boundaryor the power at the AML radiation surface. Mathematically it is written as:

• The new DMTRCOEF case control command is available to request the duct modes transmissioncoefficients.

Transmission Coefficients represent the amplitude of the output modes expressed in terms ofpressure, intensity, or power.

Input file example:...$Case Control...***Solution frequency selectionFREQUENCY = 100

***Duct tranmission loss output requestDMTRLOSS(PRINT) = YES

SUBCASE 1



Acoustics

***ALOAD command selects the duct mode with a set ID of 2.ALOAD = 2

BEGIN BULK***These parameters request FEMAOACADAPT STANDARDACORDER MINIMUM 1ACORDER MAXIMUM 1

***Solution frequency definitionFREQ1 100100.00005.000000 180

***Anechoic end duct definitionACNDUCT 1 2

***Anechoic end duct cross sectional propertiesPACDUCT 2 2 CIRCULAR 28.5956 1 0++ 5171.33603.8923 1003.400.4762721.7123-40.879298

***Description referenced by the anechoic end ductDESC 1Duct Outlet

***Fluid element face selection for anechoic end duct boundaryBSURFS 2 332342 91799 88669 91798++ 332418 88688 91799 91800 332464 91797 88671 91796++ 332623 91796 91795 91814 337443 91795 88671 88672++ 337444 91801 91821 91822 337797 88687 88688 91800

***Duct mode definitionACDUCT 2 4SPECIFIC PRESS REAL ++ 0 1 1000.00 0.0000

***Duct mode cross sectional propertiesPACDUCT 4 4 0.0000CIRCULAR 25.3987 2 0++ 1823.95-167.270 1357.170.9493285.4486-50.314286

***Description referenced by the duct modeDESC 2Duct Inlet

***Fluid element face selection for duct mode boundaryBSURFS 4 155804 98888 98889 98906++ 156115 103130 98882 98884 157499 103364 98885 98883++ 157502 102356 98884 98901 157503 102401 98884 102356++ 157661 98883 98902 98882 158279 98887 98888 98906++ 158293 98903 98883 98885 158894 98886 103409 98887++ 158897 98902 98883 98903 159463 98904 98906 98905...


Acoustics


ACDUCT

Duct Mode Definition

Defines duct modes for a frequency response analysis.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACDUCT SID PID WTYPE MTYPE FORM

MODX1 MODY1 X1 Y1

EXAMPLES:

ACDUCT 200 300 PHASE1 2 0.1 60.0

FIELDS:

Field Contents

SID Load set identification number reference by either the ALOAD casecommand or the ALOAD bulk entry. (Integer > 0; No default)

PID Property ID reference by the PID field PACDUCT bulk entry. (Integer> 0; No default)

WTYPE Type of duct modes. (Character; Default=SPECIFIC)

If WTYPE=SPECIFIC, specific duct modes are defined.

If WTYPE=DISTRIB, distributed duct modes are defined.

MTYPE Defines the units of the duct mode amplitude. (Character;Default=PRESS)

If MTYPE=PRESS, duct mode amplitude is a pressure unit.

If MTYPE=INTENS, duct mode amplitude is an intensity unit.

If MTYPE=POWER, duct mode amplitude is a power unit.

FORM Defines the complex data format for the duct mode. (Character;Default=REAL)

If FORM=REAL, the data is in rectangular format (real and imaginary).

If FORM=PHASE, the data is in polar format (magnitude and phase).



Acoustics

Field Contents

MODX1 Mode number relative to the first section coordinate. (Integer)

The section coordinates depend on how GTYPE is defined on theassociated PACDUCT bulk entry.

IF GTYPE=RECTANG, MODX1 is relative to the X direction.

IF GTYPE=CIRCULAR, MODX1 is relative to the Azimuthal direction.

IF GTYPE=ANNULAR, MODX1 is relative to the Azimuthal direction.

MODY1 Mode number relative to the second section coordinate. (Integer)

The section coordinates depend on how GTYPE is defined on theassociated PACDUCT bulk entry.

IF GTYPE=RECTANG, MODY1 is relative to the Y direction.

IF GTYPE=CIRCULAR, MODY1 is relative to the radial direction.

IF GTYPE=ANNULAR, MODY1 is relative to the radial direction.

X1, Y1 Defines the complex data parts for a duct mode. (Real or Integer;Default=0.0)

If FORM=REAL, X1 defines the real part and Y1 defines the imaginarypart.

If FORM=PHASE, X1 defines the magnitude and Y1 defines thephase.

For X1 or Y1 and either FORM value, if an integer is defined, it is theidentification number of a TABLEDi bulk entry which defines valuesas a function of frequency. If a real value is defined for X1 or Y1, thevalue remains constant as the solution frequency changes.

REMARKS:1. SID is referenced in a subcase by the ALOAD case control command, or by the

ALOAD bulk entry when combining multiple loads.

2. MODX1, MODY1 only apply to WTYPE= SPECIFIC.


Acoustics


ACNDUCT

Anechoic End Duct Definition

Defines an anechoic end duct for a frequency response analysis.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACNDUCT ID PID

EXAMPLES:

ACNDUCT 200 300

FIELDS:

Field Contents

SID The identification number of anechoic end duct. (Integer > 0; Nodefault)

PID Property ID reference to the PID field PACDUCT bulk entry. (Integer >0; No default)

REMARKS:1. Only available in a FEMAO SOL108 duct modes analysis.



Acoustics

PACDUCT

Properties of a Duct Section

Defines the geometric properties of a duct section.FORMAT:

1 2 3 4 5 6 7 8 9 10

PACDUCT PID BID OFFSET GTYPE DIM1 DIM2 DID CID

XLOC YLOC ZLOC XVEC YVEC ZVEC

EXAMPLES:

PACDUCT 200 300 RECTANG 10.0 10.0

10.0 0.0 0.0 1.0 0.0 0.0

FIELDS:

Field Contents

PID Property identification number. (Integer > 0)

BID ID of a BSURFS bulk entry which selects the fluid element faceswhere the duct section boundary is applied. (Integer > 0)

OFFSET Offset of the duct section location. (Real; Default = 0.0)

GTYPE Boundary shape of the duct section. The options are CIRCULAR,ANNULAR, or RECTANG which define a circular, annular, orrectangular boundary, respectively. (Character; Default=CIRCULAR)

DIM1,DIM2

Defines the duct section dimensions. (Real; No Default)

If GTYPE= RECTANG, DIM1 is the width and DIM2 is the height.

If GTYPE = CIRCULAR, DIM1 is the radius and DIM2 is ignored.

If GTYPE = ANNULAR, DIM1 is the external radius and DIM2 is theinternal radius.

DID Identification number of a DESC bulk entry for your description ofthe duct boundary. (Integer >0)

CID Local coordinate ID to define the origin and transverse axis of theduct section. (Integer; Default=0)

XLOC,YLOC,ZLOC

Origin of the duct section relative to the coordinate system selectedin the CID field.

XVEC,YVEC,XVEC

Coordinates of a vector defining the transverse direction (that is, theduct axis) relative to the coordinate system selected in the CID field.(Real, Default=0.0)


Acoustics


REMARKS:1. PID must be unique with respect to all other PACDUCT property identification

numbers.



Acoustics

DMTRLOSS

Duct modes transmission loss output request

Requests output of duct modes transmission loss.FORMAT:

EXAMPLES:DMTRLOSS(PRINT)

DESCRIBERS:

Describer Meaning

PRINT Transmission loss is written to the print (.f06) file. (Default)

NOPRINT Transmission loss is not written to the print (.f06) file.

PUNCH Transmission loss is written to the standard punch (.pch) file.

YES Describer settings are honored. Transmission loss is computedand output.

NO Describer settings are ignored. Transmission loss is notcomputed or output. See Remark 4.

REMARKS:1. Duct modes are only available in a FEMAO SOL108 analysis.

2. The DMTRLOSS command can only be used to request transmission loss formodels with duct modes defined. To request transmission loss for acoustic modelswithout duct modes, you should use the TRLOSS command. The TRLOSScommand is not supported when duct modes are defined.

3. DMTRLOSS results are always real values.

4. Only SORT2 output format is available for the frequency response

5. DMTRLOSS=NO can be defined in a subcase to override a DMTRLOSS that isdefined globally (above the subcase level).

6. Computed transmission loss results are written to the .op2 file.

7. PRINT output occurs by default when the DMTRCOEF command is defined,except when PUNCH output is requested. To request both PRINT and PUNCHoutput, you must explicitly define both PRINT and PUNCH. For example,

DMTRLOSS(PRINT,PUNCH)


Acoustics


DMTRCOEF

Duct modes transmission coefficient output request

Requests output of duct modes transmission coefficients.FORMAT:

EXAMPLES:DMTRCOEF(PRINT,PHASE)

DESCRIBERS:

Describer Meaning

PRINT Transmission coefficients are written to the print (.f06) file.(Default)

NOPRINT Transmission coefficients are not written to the print (.f06) file.

PUNCH Transmission coefficients are written to the standard punch (.pch)file.

REAL or IMAG Complex output is written in rectangular format (real andimaginary). REAL or IMAG results in the same output. (Default)

PHASE Complex output is written in polar format (magnitude and phase).Phase output is in degrees.

YES Describer settings are honored. Transmission coefficients arecomputed and output.

NO Describer settings are ignored. Transmission coefficients are notcomputed or output. See Remark 3.

REMARKS:1. Duct modes are only available in a FEMAO SOL108 analysis.

2. Output is always written in SORT1 format.

3. DMTRCOEF=NO can be defined in a subcase to override a DMTRCOEF that isdefined globally (above the subcase level).

4. Computed transmission coefficient results are written to the .op2 file.

5. PRINT output occurs by default when the DMTRCOEF command is defined,except when PUNCH output is requested. To request both PRINT and PUNCHoutput, you must explicitly define both PRINT and PUNCH. For example,

DMTRCOEF(PRINT,PUNCH)



Acoustics

Fan noise boundary conditionYou can define a fan noise inside an acoustic domain. These aeroacoustic simulations for subsonicfluid excitations, such as from a rotating fan or propeller, are solved using a FEM Adaptive Order(FEMAO) acoustic solution. The method can be used to solve a variety of aeroacoustic simulations,such as marine propeller sound propagation, cooling fan noise, or HVAC blower and duct acousticinteraction.

You can solve for the acoustic response using aeroacoustic excitations. Previously solved CFDsimulation surface pressures as a function of time are imported from a CGNS (CFD General NotationSystem) file, converted to a blade force excitation, and are then applied as a fan blade force usingequivalent rotating acoustic forces.

You read transient or frequency-dependent dynamic forces from spatially and time varyingcomputational fluid dynamics, acoustic, force loads, or stochastic pressure loads that weretransformed to Simcenter Nastran loads and stored in the external *.sc_h5 file by a pre/post software,such as Simcenter 3D Pre/Post.

You create a SOL108 FEMAO Acoustics solution and then include single or multiple fan noisesources in your simulation. The rotation speed (RPM) for all fans must be identical.

A fan noise can have a single blade, for which all blade forces will be assumed to be periodicallyidentical. If the fan noise has multiple blades, then blade forces can be unique for every blade. Fannoises must be located on or inside the acoustic fluid boundary.

Fan excitation can be:

• Tonal Noise, which only includes blade passing frequencies and noise.

Note

If the imported CFD fan pressures are defined for only a single blade, you can onlyapply Tonal Noise.

• If you have imported CFD fan pressures with varying forces on several blades, then you can applyTonal and Broadband noise, which includes blade passing frequencies and broadband noise.

You use a fan noise load to excite the acoustic fluid around your structure.

In the solution Case Control, you specify the forcing frequencies as harmonics and sub-harmonicsto set the solution frequencies. Harmonics include only the fan. Subharmonics are available forboth the fan and shaft.

You create a fan noise load with the new ACFAN bulk entry.

You define the fan noise properties with the new PACFAN bulk entry.

You define fan noise harmonics with the new FREQH bulk entry

Input file example:...$* FILE MANAGEMENTASSIGN SC_H5='D:\WorkDir\Project\nx13_LMS1306 Fan Noise\generated_fan_s,egments.sc_h5' UNIT=201ASSIGN SC_H5='D:\WorkDir\Project\nx13_LMS1306 Fan Noise\generated_fan_s,egments.sc_h5' UNIT=202


Acoustics


SOL 108CEND$* CASE CONTROLSUBCASE 1LABEL = Subcase - Direct Frequency 1ALOAD = 1FREQUENCY = 101

SUBCASE 2LABEL = Subcase - Direct Frequency 2ALOAD = 2FREQUENCY = 102

$* BULK DATABEGIN BULK

$REQH SID TYPE HTYPE PID STARTFREQH 101 SINGLE SHAFT 101 1$ACFAN PID TYPE RPM NBLADESPACFAN 101 TONAL 2000.00 1

$REQH SID TYPE HTYPE PID START END STEP NSUBFREQH 102 LSUB BLADE 102 10 50 4 2$ACFAN PID TYPE RPM NBLADESPACFAN 102 TONAL 2166.67 1

$* Load: Fan Noise(1)$CFAN SID PID LUNF LDID LCID WINDOWACFAN 1 101 201 1 1 HANNING$TI NAME LDID LDID DESCRIPT "ENDREC"DTI DISTL 1 1 Fan1/Forces ENDREC

$* Load: Fan Noise(2)$CFAN SID PID LUNF LDID LCID WINDOWACFAN 2 102 202 2 2 RECTANG$TI NAME LDID LDID DESCRIPT "ENDREC"DTI DISTL 2 2 Fan1/Forces ENDREC



Acoustics

ACFAN

Fan Noise Definition

Defines fan noise for a frequency response analysis.FORMAT:

1 2 3 4 5 6 7 8 9 10

ACFAN SID PID LUNF LDID LCID WINDOW

EXAMPLES:

ACFAN 200 111 25 3 2 RECTANG

FIELDS:

Field Contents

SID Load set identification number reference by either the ALOAD casecommand or the ALOAD bulk entry. (Integer > 0; No default)

PID Property ID referenced by the PID field on the PACFAN bulk entry.(Integer > 0; No default)

LUNF Logical unit number for HDF5 file containing frequency-dependentforce excitations. (Integer>0) See Remark 1.

LDID ID of the load description contained in the HDF5 file referenced byLUNF. (Integer>0) See Remark 1.

LCID Load case ID of a specific loading in the loading description(Integer>0). See Remark 1.

WINDOW Window method of Fourier transfer. (character; default = RECTANG)

=HANNING

=RECTANG

REMARKS:1. The logical unit number LUNF must reference an existing ASSIGN SC_H5 File

Management System (FMS) statement. The transient force excitation descriptionreferenced by LDID must be contained in this file including the degrees of freedomand time-steps at which the excitations are applied.


Acoustics


PACFAN

Properties of a fan noise

Defines the properties of fan noise frequency analysis.FORMAT:

1 2 3 4 5 6 7 8 9 10

PACFAN PID TYPE RPM nBlades

EXAMPLES:

PACFAN 200 TONAL 200 2

FIELDS:

Field Contents

PID Property identification number. (Integer > 0)

TYPE FAN noise type (Character; Default=TONAL)

If TYPE=TONAL, all fan blades have the same force. Define tonalcomponents only.

If TYPE=TBROAD, define tonal and broadband components. Fanblades may have different forces.

RPMID Fan rotational speed in revolutions per minute. (Real >0.0; Default= 0.0).

nBlades Apply the same forces for each fan blade. (Integer>0; Default=1)See Remark 2.

REMARKS:



Acoustics

FREQH

Harmonics for fan noise

Defines harmonics and sub-harmonics for fan noise.FORMAT:

1 2 3 4 5 6 7 8 9 10FREQH SID TYPE HTYPE PID START END STEP NSUB

EXAMPLE:

FREQH 200 SINGLE SHAFT 200 2

FIELDS:

Field Contents

SID Set identification number. (Integer > 0)

TYPE Harmonic or sub-harmonic type (Character; Default=SINGLE)

If TYPE=SINGLE, single step.

If TYPE=LINEAR, linear step.

IF TYPE = LSUB, linear step with sub-harmonics.

HTYPE The type of harmonic passing definition: SHAFT or BLADE(Character; Default=SHAFT)

PID Identification number of PACFAN bulk entry. (Integer>0; No default)

START The start harmonic number. (Integer > 0; Default = 1)

END The end harmonic number. Only applies when TYPE = LINEAR orLSUB. (Integer>1; No default)

STEP The harmonic increment. Only applies when TYPE = LINEAR orLSUB. (Integer>0; Default = 1)

nSub The number of sub-harmonics between the harmonics. Only applieswhen TYPE = LSUB. (Integer>0; Default= 1)

REMARKS:

AML support for fluid damping coefficientThe software now supports the definition of a user-specified, uniform fluid damping coefficient withthe GFL parameter, even when an automatically matched layer (AML) is present in SOL 108 andSOL 111 solutions.

In a coupled vibro-acoustic analysis, you apply GFL to the fluid portion of a model.


Acoustics


You can use the standard (fixed low-order) FEM or FEM Adaptive Order (FEMAO) method withthese supported solutions.

For more information on the GFL parameter, see G - Parameters.

Support for visualization elements in structure-acoustic interfaceSET3 bulk entries now support PLOTEL3, PLOTEL4, PLOTEL6, and PLOTEL8 visualizationelements. With this extended support, you can also use 2D PLOTEL elements in the ACMODL bulkentry to model a structure-acoustic interface.

Peak acoustic response outputWhen performing a frequency response analysis, you can now in a single solve identify thefrequencies at which the resonances occur and filter the resonances so that only those resonancesthat meet criteria that you specify are output. This capability is applicable to SOL 108 and SOL 111vibro-acoustic analysis and pure acoustic analysis.

For more information, see Limiting frequency response output to peak responses.

Spatially varying fluid properties in acoustic analysisYou can now use results from a computational fluid dynamics (CFD) general notation system (CGNS)file to define the fluid properties in acoustic radiation and propagation problems. By doing so, you canaccount for spatial variation in the properties of the fluid across the mesh. This allows you to moreaccurately model acoustic applications where significant thermal gradients exist. HVAC systems,exhaust systems, and gas turbines are examples of such applications.

The new capability is applicable to SOL 108 and 111 acoustic analysis with standard FE and FEMadaptive-order (FEMAO) meshes.

When you use the results from a CGNS file to define the fluid properties for an acoustic analysis, thesoftware does the following:

1. Reads the property data from a CGNS format file.

The CGNS format file is typically generated from a CFD mean flow simulation, and the results inthe CGNS file are given at either the grid point locations or element centroid locations of the CFDmesh. The software can read the following results from the CGNS file:

• Temperature only

• Speed of sound only

• Temperature and mass density

• Temperature and pressure

• Speed of sound and mass density

• Speed of sound and pressure



Acoustics

When the software reads a single property from the CGNS file, such as temperature only, it usesa constant value for the pressure that you must specify.

2. Using a maximum distance algorithm, maps the property data in the CGNS file to the grid pointsof the acoustic mesh. The mapped property data is stored in a SCH5 file.

Note

You cannot modify the parameters that control the maximum distance algorithm fromwithin Simcenter Nastran.

3. If necessary, converts the property data at the grid point locations to speed of sound and massdensity values.

4. Using the shape functions for the elements in the acoustic mesh, interpolates the values forspeed of sound and mass density at the grid points to the Gauss points of the elements.

During the acoustic analysis solve, the software uses the mapped fluid properties. Thus, when thesoftware performs the integrations to obtain the element matrices during the acoustic analysis solve,it accounts for spatial variation in the fluid properties across each element.

When using earlier versions of the software, you are limited to accounting for spatially varying fluidproperties on an element-by-element basis, where each element references different materialproperties.

Converting properties to speed of sound and mass density

The software uses speed of sound and mass density values when it calculates the element matrices.Thus, if the software reads temperature or pressure data from the CGNS file, the data must beconverted to speed of sound and mass density data.

The software uses the following equation to convert temperature data to speed of sound data:

where c is the speed of sound, γ is the isentropic expansion factor, R is the gas constant, and T isthe (absolute) temperature.

The software uses the following equation to convert pressure data to mass density data:

where ρ is the mass density, γ is the isentropic expansion factor, p is the (absolute) pressure, and c isthe speed of sound.

Input file requirements

You use the data in a CGNS file to define the fluid properties for an acoustic analysis by adding thenew ACTEMP case control command and bulk entry to the SOL 108 or 111 input file. Because anACTEMP case control command and bulk entry are present, the software uses the material propertiesit obtains from the ACTEMP bulk entry specification.


Acoustics


• Use the ACTEMP case control command to select the ACTEMP bulk entry from which thesoftware accesses the fluid property data. The ACTEMP case control command must be placedabove the subcases.

• Use the ACTEMP bulk entry to specify the following:

o The gas constant and isentropic expansion factor for the fluid, and, if applicable, the constantpressure.

o The combination of properties to retrieve from the CGNS file, such as temperature andpressure, speed of sound and mass density, and so on.

o The unit number of the SCH5 file.

The SCH5 file stores the CFD results that are mapped to the acoustic mesh.

o The IDs of the data tables in the CGNS file that you want to access.

• On the PSOLID bulk entry that the acoustic elements reference, in the FCTN field, specifyPFLUIDEX.

• In the File Management section, use an ASSIGN statement to associate the SCH5 file withthe unit number.

For more information, see the new ACTEMP case control command and the new ACTEMP bulk entry.



Acoustics

ACTEMP

Acoustic Fluid Property Selection

Selects spatially varying fluid property data for acoustic analysis with standard FEMand FEMAO.

FORMAT:

EXAMPLES:ACTEMP=5

DESCRIBERS:

Describer Meaning

n Set identification number of ACTEMP bulk entry. (Integer > 0)

REMARKS:1. A single ACTEMP case control command can be placed above the subcases. If

an ACTEMP case control command is placed in a subcase, a fatal error occurs.

2. An ACTEMP case control command can reference a single ACTEMP bulk entryonly.


Acoustics


ACTEMP

Properties of Acoustic Fluids

Retrieves from a SCH5 file spatially varying fluid property data for acoustic analysiswith standard FEM or FEMAO meshes.

FORMAT:

1 2 3 4 5 6 7 8 9 10ACTEMP ID R GAMMA PRESSURE UNIT DATACODE TID1 TID2

EXAMPLES:

ACTEMP 50 8.313E3 1.38 89 SS&P 100 101

ACTEMP 75 8.313E3 1.4 1.2E-2 99 T&CP 200

FIELDS:

Field Contents

ID Identification number. See Remark 1. (Integer > 0; No default)

R Gas constant for the fluid. See Remark 2. (Real > 0.0; No default)

GAMMA Isentropic expansion factor for the fluid. See Remark 2. (Real > 0.0;No default)

PRESSURE Constant pressure. See Remark 3. (Real > 0.0; No default)

UNIT Unit number of the SCH5 file. See Remark 4. (Integer > 0; No default)

DATACODE Fluid property combination to retrieve. (Character = "T&MD", "T&P","T&CP", "SS&MD", "SS&P", "SS&CP"; No default)

= "T&MD" for temperature and mass density.

= "T&P" for temperature and pressure.

= "T&CP" for temperature and constant pressure.

= "SS&MD" for speed of sound and mass density.

= "SS&P" for speed of sound and pressure.

= "SS&CP" for speed of sound and constant pressure.

TID1 Identification number of the table in the SCH5 file specified by theUNIT field that contains the data for the first property listed in theDATACODE specification. See Remark 3. (Integer > 0; No default)



Acoustics

Field Contents

TID2 Identification number of the table in the SCH5 file specified by theUNIT field that contains the data for the second property listed in theDATACODE specification. See Remark 3. (Integer > 0; No default)

REMARKS:1. If multiple ACTEMP bulk entries are present, each one must have a unique ID.

2. The R and GAMMA fields must be specified.

3. The DATACODE field specification determines which two of the TID1, TID2, andPRESSURE fields need to be specified.

• If the DATACODE specification is "T&CP" or "SS&CP":

o Use the PRESSURE field to specify the constant pressure.

o Use the TID1 field to retrieve the temperature or speed of sound data,whichever is applicable.

The software ignores the TID2 field.

• If the DATACODE specification is "T&MD", "T&P", "SS&MD", or "SS&P":

o Use the TID1 field to retrieve the temperature or speed of sound data,whichever is applicable.

o Use the TID2 field to retrieve the mass density or pressure data, whicheveris applicable.

The software ignores the PRESSURE field.

4. In the File Management section, use an ASSIGN statement to assign the data fileto the unit number specified in the UNIT field.

Acoustic matrix outputIn a SOL 108 or SOL 111 vibro-acoustic analysis, when the SKINOUT = STOP describer setting isspecified on the FLSTCNT case control command, the software now outputs the acoustic matrixbefore the run terminates. This allows you to validate the acoustic coupling between the fluid andstructure prior to proceeding with the more computationally-intensive portions of the run.

In previous versions, the software does not output the acoustic matrix when the SKINOUT = STOPdescriber setting is specified on the FLSTCNT case control command.


Acoustics

Chapter 4: Rotor dynamics

Assigning mass properties to bearing elementsYou can now assign mass properties to bearing elements modeled with PBEAR bulk entries. Withthis capability, you can account for forces in bearing elements that are proportional to linear andangular accelerations.

When you assign mass properties to PBEAR elements, you can model the mass in the following ways:

• As a constant

• As a function of rotor speed

• As a function of rotor speed and relative displacement.

• As a function of rotor speed and relative force

For more information, see the updated PBEAR bulk entry.



PBEAR

Bearing Property Definition

Defines stiffness, viscous damping, and mass matrices for bearing connection.Applicable to all rotor dynamics solution types (SOLs 101, 107, 108, 109, 110, 111,112).

FORMAT:

1 2 3 4 5 6 7 8 9 10PBEAR PID TYPE TXX TXY TYX TYY NOMVAL1

CONTINUATIONLINE

FORMATS:

1 2 3 4 5 6 7 8 9 10

“COM” C1 C1Z D1O

TYPEZ TXZ TYZ TZX TZY TZZ NOMVAL2

“COMZ” C2 C2Z D2O

TYPER TRXRX TRXRY TRYRX TRYRY NOMVAL3

“COMR” C3 C3Z D3O

The ordering of continuation lines is arbitrary.EXAMPLES:

PBEAR 5 K 1001 1002 25.0 27.5

B 2001 2002 2003 2004

PBEAR 5 KD 1001 1002 25.0 27.5 1.0E-1BD 4001 4002 4002 4001

COM 1.0 0.0 1.0E-3

KDZ 2001 2002 2001 2002 2003 2.0E-1

BDZ 5001 5002 5001 5002 5003

COMZ 0.0 1.0 0.0

KDR 3001 3002 3002 1.0E5 1.0E-2

BDR 6001 6002 6002 1.0E2

COMR 1.0 0.0 0.0

FIELDS:

Field Contents

PID Property identification number which is referenced by a CBEAR entry.(Integer > 0)



Rotor dynamics

Field Contents

TYPE Type of data in the TXX, TXY, TYX, and TYY fields on the same line.(Character: “K”, “B”, “M”, “KD”, “KF”, “BD”, “BF”, “MD”, “MF”)

• If TYPE = “K”, specifies constant stiffness or stiffness that is afunction of rotor speed.

• If TYPE = “B”, specifies constant viscous damping or viscousdamping that is a function of rotor speed.

• If TYPE = “M”, specifies constant mass or mass that is a functionof rotor speed.

• If TYPE = “KD”, specifies constant stiffness or stiffness that is afunction of rotor speed and relative displacement.

• If TYPE = “KF”, specifies constant stiffness or stiffness that is afunction of rotor speed and relative force.

• If TYPE = “BD”, specifies constant viscous damping orviscous damping that is a function of rotor speed and relativedisplacement.

• If TYPE = “BF”, specifies constant viscous damping or viscousdamping that is a function of rotor speed and relative force.

• If TYPE = “MD”, specifies constant mass or mass that is afunction of rotor speed and relative displacement.

• If TYPE = “MF”, specifies constant mass or mass that is afunction of rotor speed and relative force.

If TYPE = “KD”, “KF”, “BD”, “BF”, “MD”, “MF”, see Remark 1.

TXX, TXY,TYX, TYY

Stiffness, viscous damping, or mass matrix entry. See Remark 3.(Real or Integer ≥ 0 or blank; for default behavior, see Remark 4)

If TYPE = “K”, “B”, “M”

• If real entry, value of stiffness, viscous damping, or mass matrixentry used for all rotor speeds.

• If integer entry, identification number of a TABLEDi bulk entry thatdefines the stiffness, viscous damping, or mass matrix entry asa function of rotor speed. See Remark 5.

If TYPE = “KD”, “KF”, “BD”, “BF”, “MD”, “MF”:


Rotor dynamics


Field Contents

• If real entry, value of stiffness, viscous damping, or mass matrixentry used for all rotor speeds and relative displacements or rotorspeeds and relative forces.

• If integer entry, identification number of a TABLEST bulk entrythat defines the stiffness, viscous damping, or mass matrix entryas a function of rotor speed and relative displacement or rotorspeed and relative force. The TABLEST bulk entry referencesa series of TABLEDi bulk entries. The TABLEDi bulk entriescontain tabular data of stiffness, viscous damping, or mass vs.rotor speed at constant values of relative displacement or relativeforce. See Remark 5 and Remark 8.

NOMVAL1 Valid if TYPE = “KD”, “KF”, “BD”, “BF”, “MD”, “MF”. Field is ignored ifTYPE = “K”, “B”, “M”. See Remark 6. (Real ≥ 0.0; Default = 0.0)

• For SOLs 101, 108, 109, 111, and 112, defines the relativedisplacement or relative force that is used to either directlycompute the bearing stiffness, viscous damping, or mass, orinitiate iteration for the bearing stiffness, viscous damping, ormass. See Remark 7.

• For SOLs 107, 110, defines the relative displacement or relativeforce that is used to directly compute the bearing stiffness,viscous damping, or mass.

“COM” COM flag. Indicates that coefficients for composite relativedisplacement radial equation or composite relative force radialequation follow. (Character)

C1, C1Z,D1O

Coefficients for composite relative displacement radial equation orcomposite relative force radial equation. See Remark 9 and Remark10. (Real; Defaults are C1 = 1.0, C1Z = 0.0, D1O = 0.0)

TYPEZ Type of data in the TXZ, TYZ, TZX, TZY, and TZZ fields on the sameline. (Character: “KZ”, “BZ”, “MZ”, “KDZ”, “KFZ”, “BDZ”, “BFZ”,“MDZ”, “MFZ”)

• If TYPE = “KZ”, specifies constant stiffness or stiffness that is afunction of rotor speed.

• If TYPE = “BZ”, specifies constant viscous damping or viscousdamping that is a function of rotor speed.

• If TYPE = “MZ”, specifies constant mass or mass that is afunction of rotor speed.

• If TYPE = “KDZ”, specifies constant stiffness or stiffness that is afunction of rotor speed and relative displacement.



Rotor dynamics

Field Contents

• If TYPE = “KFZ”, specifies constant stiffness or stiffness that is afunction of rotor speed and relative force.

• If TYPE = “BDZ”, specifies constant viscous damping orviscous damping that is a function of rotor speed and relativedisplacement.

• If TYPE = “BFZ”, specifies constant viscous damping or viscousdamping that is a function of rotor speed and relative force.

• If TYPE = “MDZ”, specifies constant mass or mass that is afunction of rotor speed and relative displacement.

• If TYPE = “MFZ”, specifies constant mass or mass that is afunction of rotor speed and relative force.

If TYPE = “KDZ”, “KFZ”, “BDZ”, “BFZ”, “MDZ”, “MFZ”, see Remark 1.

TXZ, TYZ,TZX, TZY,TZZ

Stiffness, viscous damping, or mass matrix entry. See Remark 3.(Real or Integer ≥ 0 or blank; for default behavior, see Remark 4)

If TYPE = “KZ”, “BZ”, “MZ”:



If TYPE = “KDZ”, “KFZ”, “BDZ”, “BFZ”, “MDZ”, “MFZ”:


• If integer entry, identification number of a TABLEST bulk entrythat defines the stiffness, viscous damping, or mass matrix entryas a function of rotor speed and relative displacement or rotorspeed and relative force. The TABLEST bulk entry referencesa series of TABLEDi bulk entries. The TABLEDi bulk entriescontain tabular data of stiffness, viscous damping, or mass vs.rotor speed at constant values of relative displacement or relativeforce. See Remark 5 and Remark 8.


Rotor dynamics


Field Contents

NOMVAL2 Valid if TYPE = “KDZ”, “KFZ”, “BDZ”, “BFZ”, “MDZ”, “MFZ”. Fieldis ignored if TYPE = “KZ”, “BZ”, “MZ”. See Remark 6. (Real ≥ 0.0;Default = 0.0)



“COMZ” COMZ flag. Indicates that coefficients for composite relativedisplacement axial equation or composite relative force axial equationfollow. (Character)

C2, C2Z,D2O

Coefficients for composite relative displacement axial equation orcomposite relative force axial equation. See Remark 9 and Remark10. (Real; Defaults are C2 = 0.0, C2Z = 1.0, D2O = 0.0)

TYPER Type of data in the TRXRX, TRXRY, TRYRX, and TRYRY fields onthe same line. (Character: “KR”, “BR”, "MR", “KDR”, “KFR”, “BDR”,“BFR”, “MDR”, “MFR”)

• If TYPE = “KR”, specifies constant stiffness or stiffness that is afunction of rotor speed.

• If TYPE = “BR”, specifies constant viscous damping or viscousdamping that is a function of rotor speed.

• If TYPE = “MR”, specifies constant mass or mass that is afunction of rotor speed.

• If TYPE = “KDR”, specifies constant stiffness or stiffness that is afunction of rotor speed and relative displacement.

• If TYPE = “KFR”, specifies constant stiffness or stiffness that is afunction of rotor speed and relative force.

• If TYPE = “BDR”, specifies constant viscous damping orviscous damping that is a function of rotor speed and relativedisplacement.

• If TYPE = “BFR”, specifies constant viscous damping or viscousdamping that is a function of rotor speed and relative force.



Rotor dynamics

Field Contents

• If TYPE = “MDR”, specifies constant mass or mass that is afunction of rotor speed and relative displacement.

• If TYPE = “MFR”, specifies constant mass or mass that is afunction of rotor speed and relative force.

If TYPE = “KDR”, “KFR”, “BDR”, “BFR”, “MDR”, “MFR”, see Remark 1.

TRXRX,TRXRY,TRYRX,TRYRY

Stiffness or viscous damping matrix entry. See Remark 3. (Real orInteger ≥ 0 or blank; for default behavior, see Remark 4)

If TYPE = “KR”, “BR”, “MR”:



If TYPE = “KDR”, “KFR”, “BDR”, “BFR”, “MDR”, “MFR”:


• If integer entry, identification number of a TABLEST bulk entrythat defines the stiffness, viscous damping, or mass matrix entryas a function of rotor speed and relative displacement or rotorspeed and relative force. The TABLEST bulk entry referencesa series of TABLEDi bulk entries. The TABLEDi bulk entriescontain tabular data of stiffness, viscous damping, or mass vs.rotor speed at constant values of relative displacement or relativeforce. See Remark 8.

NOMVAL3 Valid if TYPE = “KDR”, “KFR”, “BDR”, “BFR”, “MDR”, “MFR”. Fieldis ignored if TYPE = “KR”, “BR”, “MR”. See Remark 6. (Real ≥ 0.0;Default = 0.0)




Rotor dynamics


Field Contents

“COMR” COMR flag. Indicates that coefficients for composite relativedisplacement rotational equation or composite relative force rotationalequation follow. (Character)

C3, C3Z,D3O

Coefficients for composite relative displacement rotational equationor composite relative force rotational equation. See Remark 9 andRemark 10. (Real; Defaults are C3 = 1.0, C3Z = 0.0, D3O = 0.0)

REMARKS:1. Relative displacement is the displacement between the two coincident grids used

to define the CBEAR connection. Relative force is the force carried through theCBEAR connection. The relative force is calculated from the relative displacement.

2. Define speed-dependent bearing properties in the same units for speed that arespecified in the RUNIT field of the ROTORD bulk entry.

3. “X”, “Y”, and “Z”, in TXX, TXY, TYX, TYY, TXZ, TYZ, TZX, TZY, and TZZ, refer tothe X, Y, and Z-axes of the coordinate system referenced in the RCORDi field ofthe ROTORD bulk entry. “RX” and “RY” in TRXRX, TRXRY, TRYRX, and TRYRYrefer to rotation about the X-axis and rotation about the Y-axis of the coordinatesystem referenced in the RCORDi field of the ROTORD bulk entry. In a rotordynamic analysis, a rotor’s axis of rotation must be aligned with the Z-axis of thecoordinate system referenced in the RCORDi field of the ROTORD bulk entry.

4. If any of TXX, TXY, TYX, TYY, TXZ, TYZ, TZX, TZY, TZZ, TRXRX, TRXRY,TRYRX, or TRYRY fields are blank or zero (either integer zero or real zero), thesoftware uses real zero as the value for the corresponding field.

5. In TABLEDi bulk entries, enter the rotor speed data in the units that are specifiedin the RUNIT field of the ROTORD bulk entry.

6. If a NOMVALi is defined in both a stiffness, damping, and mass row, the value inthe stiffness row is used.

7. When TYPE = “KD”, “KF”, “BD”, “BF”, “MD”, “MF”, “KDZ”, “KFZ”, “BDZ”, “BFZ”,“MDZ”, “MFZ”, “KDR”, “KFR”, “BDR”, “BFR”, “MDR”, or “MFR” for SOL 101, 108,and 111, the method used to determine the stiffness, viscous damping, or mass forCBEAR elements depends on the value of MAXITER.

• If MAXITER = 0, the value specified in the NOMVALi field is used to directlycompute the bearing stiffness, viscous damping, and mass.

• If MAXITER ≠ 0, the value specified in the NOMVALi field is used to initiateiteration over relative displacement or relative force. Consecutive iterationsuse the relative displacement and relative force from the previous iterationto update the bearing stiffness, viscous damping, and mass. The relativedisplacement or relative force magnitude on the CBEAR element at eachiteration is compared with the value from the previous iteration to evaluate



Rotor dynamics

convergence. When iterating over relative displacement, convergence isreached when:

|(Disp (old) - Disp (new)) / Disp (old)| < THRSHOLD

When iterating over relative force, convergence is reached when:

|(Force (old) - Force (new)) / Force (old)| < THRSHOLD

Iterating stops when either convergence is met, or the number of iterationsexceeds MAXITER.

MAXITER and THRSHOLD are specified on the ROTORD bulk entry.

8. On a TABLEST bulk entry referenced by a PBEAR bulk entry, the values forrelative displacement or relative force that correspond to the TABLEDi bulk entriesmust be consistently defined for all TABLEDi bulk entries. For example, a validentry is as follows:

PBEAR 789 KD 6891 6892 6893 6894$$ TABLEST tables for PBEAR$TABLEST 6891

0.0 7891 0.1 8891 0.3 9891 ENDTTABLEST 6892

0.0 7892 0.1 8892 0.3 9892 ENDTTABLEST 6893

0.0 7893 0.1 8893 0.3 9893 ENDTTABLEST 6894

0.0 7894 0.1 8894 0.3 9894 ENDT

The following entry is invalid:PBEAR 789 KD 6891 6892 6893 6894$$ TABLEST tables for PBEAR$TABLEST 6891

0.0 7891 0.1 8891 0.3 9891 ENDTTABLEST 6892

0.0 7892 0.1 8892 0.4 9892 ENDTTABLEST 6893

0.0 7893 0.1 8893 0.3 9893 ENDTTABLEST 6894

0.0 7894 0.1 8894 0.3 9894 ENDT

The following entry is also invalid:PBEAR 789 KD 6891 6892 6893 6894$$ TABLEST tables for PBEAR$TABLEST 6891

0.0 7891 0.1 8891 0.3 9891 ENDTTABLEST 6892

0.0 7892 0.1 8892 0.3 9892 ENDT


Rotor dynamics


TABLEST 68930.0 7893 0.1 8893 ENDT

TABLEST 68940.0 7894 0.1 8894 0.3 9894 ENDT

However, the tabular data entered on the TABLEDi bulk entries that are referencedby a TABLEST bulk entry do not need to have the same range.

9. Composite relative displacements are linear combinations of radial andaxial relative displacements. The software calculates the composite relativedisplacements from the following equations:

Δ1 = C1 Δr + C1Z Δz + D1OΔ2 = C2 Δr + C2Z Δz + D2OΔ3 = C3 Δr + C3Z Δz + D3O

where Δ1 is the composite radial relative displacement, Δ2 is the composite axialrelative displacement, Δ3 is the composite rotational relative displacement, Δr isthe radial relative displacement, and Δz is the axial relative displacement. TheD1O, D2O, and D3O coefficients represent preload displacements.

The software calculates Δr as follows:

Δr = (Δx2 + Δy2) 1/2

where Δx is the relative displacement in the x-direction and Δy is the relativedisplacement in the y-direction.

The software calculates Δz as follows:

Δz = ΔGB – ΔGAwhere ΔGA and ΔGB are the axial displacements of the grids listed on the CBEARbulk entry.

For bearing properties that are speed and displacement-dependent, the softwareuses the composite relative displacements to look up values for bearing stiffness,viscous damping, and mass. The matrix for bearing stiffness, viscous damping,or mass is as follows:

where Tij(Δi, Ω) are stiffness, viscous damping, or mass matrix entries as afunction of composite relative displacement and angular speed of the rotor,Ω. If the matrix entries represent viscous damping, Δx, Δy, and Δz representtranslational velocities, and Δrx and Δry represent angular velocities. If the matrixentries represent mass, Δx, Δy, and Δz represent translational accelerations, andΔrx and Δry represent angular accelerations.



Rotor dynamics

If the calculated relative displacement is less than zero, the software automaticallyresets it to zero when it looks up values for bearing stiffness, viscous damping,and mass.

10. Composite relative forces are linear combinations of radial and axial relative forces.The software calculates the composite relative forces from the following equations:

F1 = C1 Fr + C1Z Fz + D1OF2 = C2 Fr + C2Z Fz + D2OF3 = C3 Fr + C3Z Fz + D3O

where F1 is the composite radial relative force, F2 is the composite axial relativeforce, F3 is the composite rotational relative force, Fr is the radial relative force,and Fz is the axial relative force. The D1O, D2O, and D3O coefficients representpreload forces.

The software calculates Fr as follows:

Fr = (Fx2 + Fy2) 1/2

where Fx is the relative force in the x-direction and Fy is the relative force in they-direction.

For bearing properties that are speed and force-dependent, the software uses thecomposite relative forces to look up values for bearing stiffness, viscous damping,and mass. The matrix for bearing stiffness, viscous damping, or mass is as follows:

where Tij(Fi, Ω) are stiffness, viscous damping, or mass matrix entries as afunction of composite relative force and angular speed of the rotor, Ω. If thematrix entries represent viscous damping, Δx, Δy, and Δz represent translationalvelocities, and Δrx and Δry represent angular velocities. If the matrix entriesrepresent mass, Δx, Δy, and Δz represent translational accelerations, and Δrx andΔry represent angular accelerations.

If the calculated relative force is less than zero, the software automatically resets itto zero when it looks up values for bearing stiffness, viscous damping, and mass.


Rotor dynamics

Chapter 5: Superelements

Results recovery for external superelements using the modeacceleration methodYou can now use the mode acceleration method to obtain the output transformation matrices (OTMs)that the software uses to recover results for external superelements that are dynamically reducedusing component mode synthesis. When you use the mode acceleration method, the software canrecover displacement, velocity, acceleration, SPC force, MPC force, element force, grid point forcebalance, stress, strain, composite stress, and composite strain results for the external superelement.

During the system run, the software automatically detects when you specify the mode accelerationmethod in the external superelement creation run. During results recovery for the system run, thesoftware uses the boundary and modal displacements that it calculates during the system run,and the OTMs that it retrieves from the external superelement creation run to calculate results forthe interior DOF of the external superelement.

In earlier versions of the software, you are limited to using the mode displacement method to obtainthe OTMs for results recovery. Like the mode displacement method, the mode acceleration method isapplicable to external superelements that include differential stiffness.

To use the mode acceleration method, in the input file for the external superelement creation run,on the EXTSEOUT case control command, specify the new MODACC describer. The softwarecreates the boundary matrices for the superelement, and the mode acceleration method OTMs forthe superelement. If you do not specify the MODACC describer, the software creates the modedisplacement method OTMs.

The MODACC describer is only applicable when the external superelement is dynamically reducedusing component mode synthesis. When you use any other reduction method, such as Guyanreduction, the software issues a fatal error.

Mode acceleration method formulation

During the system run, the software recovers the results for the interior DOF of the superelementfrom the following equation:

where the subscript ‘o’ refers to interior DOF of the external superelement, the subscript ‘b’ refers tothe boundary DOF for the external superelement, and the subscript ‘q’ refers to the modal coordinatesfor the external superelement. The OTM3 matrix is required for local viscous damping forces, andthe OTM4 matrix is required when internal forces that act on the external superelement are carriedinto the system run.

The equations that the software uses to calculate the OTMs are result specific. For example, torecover displacements, the software calculates OTM1, OTM2, OTM3, and OTM4 from the followingequations:



The following table lists the data blocks that contain the OTMs for the other result types.

Result OTM1 data block OTM2 data block OTM3 data block OTM4 data blockDisplacement DTM1 DTM2 DTM3 DTM4SPC force SPC1 SPC2 SPC3 SPC4MPC force MPC1 MPC2 MPC3 MPC4Element force ELF1 ELF2 ELF3 ELF4Grid point forcebalance GPFB1 GPFB2 GPFB3 GPFB4

Stress STR1 STR2 STR3 STR4Strain STA1 STA2 STA3 STA4Composite stress STRC1 STRC2 STRC3 STRC4Composite strain STAC1 STAC2 STAC3 STAC4

The software calculates velocity and acceleration results for the interior DOF of the externalsuperelement directly from the recovered displacement results. For example, in frequency responseanalysis, because the formulation assumes harmonic motion, velocity and acceleration results arecalculated as follows:



Superelements

EXTSEOUT

External Superelement Creation Specification

Specify the various requirements for the creation of an external superelement.FORMAT:

EXAMPLES:EXTSEOUTEXTSEOUT(ASMBULK,EXTID=100)EXTSEOUT(ASMBULK,EXTBULK,EXTID=200)EXTSEOUT(EXTBULK,EXTID=300)EXTSEOUT(DMIGDB)EXTSEOUT(ASMBULK,EXTID=400,DMIGOP2=21)EXTSEOUT(EXTID=500,DMIGPCH)EXTSEOUT(ASMBULK,EXTBULK,EXTID=500,DMIGSFIX=XSE500,DMIGPCH)EXTSEOUT(ASMBULK,EXTBULK,EXTID=500,DMIGSFIX=EXTID,DMIGPCH)EXTSEOUT(STIF,MASS,DAMP,EXTID=600,ASMBULK,EXTBULK,MATDB)EXTSEOUT(STIF,MASS,DAMP,GEOM,EXTID=600)

DESCRIBERS:

Describer Meaning

STIFFNESS Store the boundary stiffness matrix. See Remarks 1 and 2.

MASS Store the boundary mass matrix. See Remark 1.

DAMPING Store the boundary viscous damping matrix. See Remarks 1and 2.

K4DAMP Store the boundary structural damping matrix. See Remarks 1and 2.

LOADS Store the loads matrix and associated DTI,SELOAD entries.See Remarks 1, 2, and 21.

GEOM Store geometry. See Remark 20.


Superelements


Describer Meaning

MODACC Create the external superelement output transformation matricesusing the mode acceleration method. See Remarks 25 and 26.

FSCOUP Create the a-set acoustic area matrix. See Remark 27.

ASMBULK Generate bulk entries related to the subsequent superelementassembly process and store them on the assembly punch file(.asm). This data is to be included in the main bulk portion of thesubsequent assembly solution. See Remarks 4 and 13.

EXTBULK Generate and store bulk entries for the external superelementon the standard punch file (.pch) when used in combinationwith one of either MATDB, DMIGDB, or DMIGOP2. This datais used in the BEGIN SUPER portion of the bulk section of thesubsequent assembly solution. EXTBULK is ignored if eitherDMIGPCH or MATOP4 is specified. If EXTBULK is not specified,the subsequent assembly solution retrieves the required datafor the external superelement from the medium on which theboundary matrices are stored. See Remarks 5 and 6.

EXTID = seid seid (integer>0) is the superelement ID to be used in theSEBULK and SECONCT bulk entries stored on the assemblypunch file (.asm) if ASMBULK is specified and in the BEGINSUPER bulk entry stored on the standard punch file (.pch) ifDMIGPCH or MATOP4 is specified. See Remarks 3, 4, 5, and 7.

DMIGSFIX =cccccc

cccccc is the suffix (up to six characters and must not = anyEXTSEOUT keyword) that is to be employed in the names ofthe DMIG matrices stored on the standard punch file (.pch) if theDMIGPCH keyword is specified. See Remarks 8 through 11.

DMIGSFIX =EXTID

The seid defined by the EXTID keyword is the suffix that is tobe employed in the names of the DMIG matrices stored on thestandard punch file (.pch) if the DMIGPCH keyword is specified.See Remarks 8 through 11.

MATDB (orMATRIXDB)

Store the boundary matrices and other information on thedatabase (default).

DMIGDB Similar to MATDB (or MATRIXDB) except that the boundarymatrices are stored as DMIG bulk entries on the database.

DMIGOP2 =unit

Store the boundary matrices as DMIG bulk entries on anOUTPUT2 file whose Fortran unit number if given by unit(integer>0). See Remark 14.

DMIGPCH Store the boundary matrices as DMIG bulk entries on thestandard punch file (.pch). See Remarks 6 through 13.



Superelements

Describer Meaning

MATOP4 = unit(or MATRIXOP4= unit)

Store the boundary matrices on an OP4 file whose Fortran unitnumber is given by unit. (Integer ≠ 0)

If unit > 0, matrices are written to the OP4 file in sparse format.

If unit < 0, matrices are written to the OP4 file in full matrixformat.

See Remarks 3, 5, 6, 13, 14, and 23.

REMARKS:1. If none of the describers STIFFNESS, MASS, DAMPING, K4DAMP, and LOADS

are specified, then all of the boundary matrices are stored by default. If any subsetof the describers STIFFNESS, MASS, DAMPING, K4DAMP, and LOADS arespecified, then only the boundary matrices specified are stored.

2. STIFFNESS, DAMPING, K4DAMP, and LOADS may be abbreviated to STIF,DAMP, K4DA, and LOAD, respectively.

3. EXTID and an seid value must be specified if one or more of ASMBULK,EXTBULK, DMIGPCH, or MATOP4 are specified. If the DMIGSFIX=EXTID formis employed along with the DMIGPCH keyword, the value seid may not exceed999999, since this value becomes part of the names given to the DMIG matricesgenerated on the standard punch file (.pch). See Remark 11.

4. If ASMBULK is specified, the following bulk entries are generated and stored onthe assembly punch file (.asm):

SEBULK seid …

SECONCT seid …

GRID entries for the boundary points

CORD2x entries associated with the above GRID entries

5. If DMIGPCH is not specified, but MATOP4 or EXTBULK (in combination withMATDB, DMIGDB, or DMIGOP2) is specified, the following bulk entries aregenerated and stored on the standard punch file (.pch):

BEGIN SUPER seid


GRID entries for the interior points referenced by PLOTEL entries


EXTRN

ASET/ASET1


Superelements


QSET/QSET1

SPOINT

PLOTEL

6. If DMIGPCH or MATOP4 is specified, then EXTBULK is ignored even if it isspecified.

7. If DMIGPCH is specified, the following bulk entries are generated and stored onthe standard punch file (.pch):

BEGIN SUPER seid



ASET/ASET1

SPOINT

DMIG entries for the requested boundary matrices

8. The DMIGSFIX keyword is ignored if DMIGPCH is not specified.

9. If DMIGPCH is specified without the DMIGSFIX keyword, then the boundaryDMIG matrices generated and stored on the standard punch file (.pch) will havenames of the following form:

KAAX (boundary stiffness matrix)

MAAX (boundary mass matrix)

BAAX (boundary viscous damping matrix)

K4AAX (boundary structural damping matrix)

PAX (boundary load matrix)

10. If the DMIGSFIX = cccccc form is employed along with the DMIGPCH keyword,then the boundary DMIG matrices generated and stored on the standard punchfile (.pch) will have names of the following form:

Kcccccc (boundary stiffness matrix)

Mcccccc (boundary mass matrix)

Bcccccc (boundary viscous damping matrix)

K4cccccc (boundary structural damping matrix)

Pcccccc (boundary load matrix)



Superelements

11. If the DMIGSFIX = EXTID form is employed along with the DMIGPCH keyword,then the boundary DMIG matrices generated and stored on the standard punchfile (.pch) will have names of the following form:

Kseid (boundary stiffness matrix)

Mseid (boundary mass matrix)

Bseid (boundary viscous damping matrix)

K4seid (boundary structural damping matrix)

Pseid (boundary load matrix)

12. If the DMIGPCH option is specified, the boundary DMIG matrices generated andstored on the standard punch file (.pch) may not be as accurate as the boundarymatrices resulting from other options (MATDB/MATRIXDB or DMIGOP2 orMATOP4/MATRIXOP4). Accordingly, this may result in decreased accuracy fromthe subsequent assembly job utilizing these DMIG matrices.

13. The punch output resulting from EXTSEOUT usage is determined by ASMBULK,EXTBULK, DMIGPCH, and MATOP4 as follows:

• No ASMBULK, EXTBULK, DMIGPCH, or MATOP4 results in no punch output.

• ASMBULK, but no DMIGPCH, MATOP4, or EXTBULK (in combination withMATDB, DMIGDB, or DMIGOP2) results in punch output being generated andstored on the assembly punch file (.asm). See Remark 4.

• No ASMBULK, but DMIGPCH, MATOP4, or EXTBULK (in combination withMATDB, DMIGDB, or DMIGOP2) results in punch output being generated andstored on the standard punch file (.pch). See Remarks 5 or 7, as appropriate.

• ASMBULK and DMIGPCH, MATOP4, or EXTBULK (in combination withMATDB, DMIGDB, or DMIGOP2) results in punch output consisting of twodistinct and separate parts. One part is generated and stored on the assemblypunch file (.asm) as indicated in Remark 4. The other part is generated andstored on the standard punch file (.pch) as indicated in Remark 5 or 7, asappropriate.

14. If DMIGOP2=unit or MATOP4=unit is specified, an appropriate ASSIGN OUTPUT2or ASSIGN OUTPUT4 statement must be present in the File Management Section(FMS) for the absolute value of unit. An OUTPUT2 file created during a LP-64Nastran executable superelement creation run cannot be used in an ILP-64Nastran executable system run and vice versa. Use the SEOP2CV parameterto control the binary format of the OUTPUT2 file. Note that beginning in NXNastran12, only the ILP-64 executable is available.

15. The creation of an external superelement using EXTSEOUT involves running aSimcenter Nastran job with the following additional data:


Superelements


• The data for the creation of the external superelement is specified by theEXTSEOUT case control command, which must appear above the subcaselevel.

• The boundary points of the external superelement are specified byASET/ASET1 bulk entries.

• If the creation involves component mode reduction, the required generalizedcoordinates are specified using QSET/QSET1 bulk entries. The boundarydata for the component mode reduction may be specified using theBNDFIX/BNDFIX1 and BNDFREE/BNDFREE1 bulk entries (or their equivalentBSET/BSET1 and CSET/CSET1 bulk entries). (The default scenario assumesthat all boundary points are fixed for the component mode reduction.)

• The output for the external superelement is generated in the assembly job.This output consists of displacements, velocities, accelerations, SPC forces,MPC forces, grid point force balances, stresses, strains, and element forces.However, in order for this output to be generated in the assembly job, theoutput requests must be specified in the external superelement creation run.Normally, the only output requests for the external superelement that arehonored in the assembly job are those that are specified in the creation run.There is, however, one important exception to this: the displacement, velocity,acceleration, SPC forces, and MPC forces output for the boundary gridpoints as well as for all grid points associated with the PLOTEL, PLOTEL3,PLOTEL4, PLOTEL6, PLOTEL8, PLOTHEX, PLOTTET, PLOTPEN, andPLOTPYR bulk entries can be obtained in the assembly job even if there is nooutput request specified for these points in the creation run.

• If the assembly job involves the use of PARAM bulk entries, then the followingpoints should be noted:

o PARAM entries specified in the main bulk portion of the input data applyonly to the residual and not to the external superelement.

o PARAM entries specified in the BEGIN SUPER portion of the bulk sectionfor an external superelement apply only to the superelement.

o The most convenient way of ensuring that PARAM entries apply not onlyto the residual but also to all external superelements is to specify suchPARAM entries in Case Control, not in the main bulk section. This isparticularly relevant for such PARAMs as POST.

16. Output transformation matrices are generated for the following outputs requestedin the in external superelement run with EXTSEOUT:

• DISPLACEMENT

• VELOCITY

• ACCELERATION

• SPCFORCE



Superelements

• MPCFORCES

• GPFORCE

• STRESS

• STRAIN

• FORCE

Only these external superelement results can be output in the system analysisrun. PARAM,OMID,YES is not applicable to the output transformation matrices.

17. If a PARAM,EXTOUT or PARAM,EXTUNIT also exist, they will be ignored. Theexistence of the EXTSEOUT case control command takes precedence overPARAM,EXTOUT and PARAM,EXTUNIT.

18. This capability is enabled in SOLs 101, 103, 107-112, 129, 144-146, 159, and 187.In general, it is not supported for thermal analysis, however, in SOL 101 withGuyan reduction, thermal loads can be transferred to a system model via theo-set output transformation matrices. Grid-based results such as displacementsare correct, but element-based results such as stress, strain, and forces are notcorrect because the software cannot remove thermal strain from the modal-basedoutput transformation matrices for these quantities. Fluid and acoustic elementssuch as absorbers are not supported in an external superelement, althoughthey can be included as part of the residual in a system run. For SOL 103, thiscapability creates the external superelement and also creates the componentresults and data blocks that are written to an .op2 file if requested. For the othersolution sequences, this capability only creates the external superelement and noother analysis is performed. Superelement results can be recovered in the secondstep (i.e. superelement assembly, analysis, and data recovery) for SOLs 101, 103,105, 107-112, and 144-146.

19. The run creating the external superelement using this capability is not asuperelement run. No superelement designations are allowed (i.e. SUPER,SEALL, SESET, BEGIN SUPER, etc.).

20. The GEOM describer will output geometry data blocks GEOM1EXA, GEOM2EXA,and GEOM4EXA containing all of the external superelement geometry to supportpost-processing. This describer only works for the MATDB (or MATRIXDB),DMIGDB, and DMIGOP2 storage options. By default, the full geometry will not beexported; the GEOM describer must be explicitly defined to have these geometrydata blocks written.

21. The LOADS describer will output load information in the [Pa] matrix along withassociated DTI,SELOAD bulk entries for each load represented in the [Pa] matrix.DTI,SELOAD bulk entries will not be output for the DMIGPCH option; the use ofthe DMIGPCH option requires the use of the P2G case control command in thesystem analysis in order to access the load information defined in the [Pa] matrixthat is stored in DMIG format. Thermal loads and enforced motion loads using theSPCD bulk data definition method are not supported. The load information and


Superelements


DTI,SELOAD bulk entries that are output depend on the method in which loadsare defined and referenced.

Static solutions. For example, SOL 101:

• In a creation run, the LOAD = n case control command will create a singleload. The [Pa] matrix will have a single column that contains the load valuesreferenced by n. The corresponding LIDSE and EXCSE values on theDTI,SELOAD bulk entry will be the value n.

To select this load in a system run, the LIDSE field on the SELOAD bulk entryshould equal the value of n from the creation run.

• In a creation run, the LOADSET = n case control command is generally usedto create multiple loads. Each definition of an LSEQ bulk entry will create acolumn in the [Pa] matrix regardless of whether or not the LSEQ is referencedby the LOADSET = n case control command. However, an unreferencedLSEQ will generate a null column in the [Pa] matrix. The corresponding LIDSEand EXCSE on an DTI,SELOAD bulk entry will be the value of LID andEXCITEID, respectively, on an LSEQ bulk entry.

To select these loads in a system run, the LIDSE field on the SELOAD bulkentry should equal the value of an EXCITEID from the creation run.

• If both LOADSET and LOAD appear in the case control, LOADSET takesprecedence.

Dynamic solutions. For example, SOL 103:

• In a creation run, a column in the [Pa] matrix is created for each load (notenforced motion) defined on RLOADi and TLOADi bulk entries whether ornot they are referenced in the case control. The corresponding LIDSE andEXCSE on the DTI,SELOAD bulk entries will both be the value of EXCITEIDon the RLOADi or TLOADi bulk entry.

To select these loads in a system run, the LIDSE field on the SELOAD entryshould equal the value of an EXCITEID from the creation run.

• In a creation run, the LOADSET = n case control command can be usedto create multiple loads. Each definition of an LSEQ bulk entry will createa column in the [Pa] matrix. A LSEQ bulk entry must be referenced by aLOADSET case control command in order to generate a column in the [Pa]matrix. The corresponding LIDSE and EXCSE on an DTI,SELOAD bulk entrywill be the value of LID and EXCITEID, respectively, on an LSEQ bulk entry.

To select these loads in a system run, the LIDSE field on the SELOAD entryshould equal the value of an EXCITEID from the creation run.

22. To include differential stiffness in the definition of an external superelement, twosubcases are required in the creation run. The first subcase is a static subcase.The second subcase performs the analysis and generation of the externalsuperelement. To obtain the displacement field used to generate the differentialstiffness effects, include a STATSUB case control command in the second subcase



Superelements

that references the first subcase. Always include the EXTSEOUT case controlcommand above the subcase level. An example of the required setup is as follows:

…SOL 112CENDTITLE = …EXTSEOUT(…)$SUBCASE 1

$ STATIC SUBCASELOAD = 11

$SUBCASE 2

$ DYNAMIC SUBCASETSTEP = 100STATSUB = 1METHOD = 10DLOAD = 20

BEGIN BULK…

For accuracy and consistency, the loads used to generate differential stiffnessfor the external superelement during the creation run should be the same loadsused in the system run without any scaling. If the loads are scaled by a non-unityscaling factor from a case control command like P2G or a bulk entry like LOAD,the differential stiffness portion of the external superelement stiffness matrix will nolonger be consistent with the applied loads.

The ability to generate an external superelement including differential stiffnesseffects is available for SOLs 103, 107-112, and 187. For SOL 112, theIC(STATSUB,DIFFK) or IC(TZERO,DIFFK) case control commands can be usedto generate differential stiffness effects instead of the STATSUB case controlcommand.

23. For the MATOP4 (or MATRIXOP4) option, the number of digits of precision formatrix data is controlled by the DIGITS parameter.

24. See Parameters and Superelements for considerations regarding parameterdefinitions in a system solution which includes external superelements.

25. The MODACC describer generates all the output transformation matricesdiscussed in Remarks 15 and 16 using the mode acceleration method. TheMODACC describer is only applicable when the external superelement isdynamically reduced using component mode synthesis. When any other reductionmethod such as Guyan reduction is used, the software issues a fatal error.

26. When the MODACC and MATOP4 (or MATRIXOP4) describers are both specified,the OUTPUT4 matrices are written in dense format and residual vectors areautomatically turned off.

27. The FSCOUP describer reduces the g-set acoustic area matrix, AGG, to theuser-defined a-set DOF. The FSCOUP describer is valid only when the DMIGPCH


Superelements


describer is specified. When any other output media is specified, the FSCOUPdescriber is ignored.

28. Specifying PARAM,WMODAL,YES causes hysteretic damping to be convertedto viscous damping, which is useful when the external superelement is used ina system transient analysis.

Structural damping in external superelementsYou can now use the WMODAL parameter to convert structural damping to viscous damping duringthe creation run for an external superelement. This capability is useful when you intend to use thesuperelement in a SOL 112 transient analysis system run. The capability is applicable to externalsuperelements that use either the mode displacement method or mode acceleration method forresults recovery.

In earlier versions of the software, the software ignores a WMODAL parameter specification in theinput file of an external superelement creation run.

To convert structural damping in an external superelement to viscous damping, in the input file for theexternal superelement, specify PARAM,WMODAL,YES.

For more information, see WMODAL.

WMODAL

Default = NO

WMODAL specifies a structural-to-viscous damping conversion method that uses the solved modalfrequencies as conversion factors.

When one or both of the W3 and W4 parameters are also specified (see the W3, W4, W3FL, W4FLparameter), the structural-to-viscous damping conversion is calculated as follows:

where [Bdd] is the resulting viscous damping matrix expressed in modal space, ωi are the modalfrequencies in radians per unit time, and [B1dd] and [B2dd] represent viscous damping contributionsfrom damping elements (CVISC, CDAMPi) and DMIG entry of viscous damping, respectively. Theremaining terms represent structural damping. G[K1dd] results from PARAM,G specification. [K4dd]results from GE on MATi entry and DMIG entry of structural damping.

For rigid body modes, the corresponding diagonal entries are partitioned out of the calculation. TheFZERO parameter is used to identify rigid body modes (see the FZERO parameter).

[Bqq] can be used directly in a modal transient response analysis (SOL 112). It can also be usedin a multi-body dynamics or control system simulation when a normal modes analysis (SOL 103),modal frequency response analysis (SOL 111), or modal transient response analysis (SOL 112) input



Superelements

file contains either the ADAMSMNF or MBDEXPORT case control commands. For a multi-bodydynamics simulation, the damping matrix written to the interface file contains only the values alongthe diagonal of [Bqq]. For a control system simulation, the state-space representation written to theinterface file uses all of [Bqq].

The WMODAL parameter is valid for converting structural damping to viscous damping in the residualstructure and external superelements.


Superelements

Chapter 6: Elements

Quadratic thickness plane stress elementsYou can now specify a quadratic thickness variation along the edges of CPLSTS6 and CPLSTS8plane stress elements by specifying the thickness at mid-side grid points. With this capability, youcan more accurately model the geometry in applications of CPLSTS6 and CPLSTS8 plane stresselements where the thickness variation is nonlinear. Such applications include axisymmetric modelsof gas turbines where plane stress elements model compressor blades, turbine blades, and bolts.

In previous versions of the software, you were limited to specifying these elements with constantthickness or with a linear thickness variation along the element edges.

When you specify CPLSTS6 and CPLSTS8 plane stress elements with quadratic thickness along theedges, the software supports the following capabilities:

• Calculation of element matrices such as mass, stiffness, differential stiffness, and so on instructural analysis.

• Calculation of element matrices such as capacitance, conductivity, and so on in thermal analysis.

• Creation of adaptive-order meshes in acoustic analysis.

• Contact.

To use the new capability, specify the thickness of the elements at the mid-side grid points in the newTMi fields for the CPLSTS6 and CPLSTS8 bulk entries.

For more information, see CPLSTS6 and CPLSTS8.


Chapter 6: Elements

CPLSTS6

Plane Stress Triangular Element Connection

Defines a plane stress triangular element for use in linear or nonlinear analysis.FORMAT:

1 2 3 4 5 6 7 8 9 10CPLSTS6 EID PID G1 G2 G3 G4 G5 G6

THETA TFLAG T1 T2 T3

TM4 TM5 TM6

EXAMPLE:

CPLSTS6 302 3 31 33 71 32 51 52

25.0 1 0.1 0.2 0.3

0.15 0.25 0.2

FIELDS:

Field Contents

EID Element identification number. (Integer > 0)

PID Property identification number of a PPLANE or PLPLANE entry.(Integer > 0; Default = EID)

Gi Grid point identification number of connected points. (Unique integers> 0; No default)

THETA Material property orientation angle in degrees. See Remark 13.THETA is ignored for hyperelastic elements. (Real; Default = 0.0)

TFLAG Flag that specifies whether Ti and TMi are thicknesses that overridethe thickness specified on the PPLANE or PLPLANE entry (TFLAG =0) or are factors that scale the thickness specified on the PPLANE orPLPLANE entry (TFLAG = 1). (Integer 0 or 1; Default = 0)

T1,T2,T3 Thickness override or thickness scaling factor at corner grid points.See Remark 3.

If TFLAG = 0, Ti overrides the thickness specified on the PPLANEor PLPLANE entry at the corresponding corner grid point. (Real ≥0.0; Default = thickness specified on the PPLANE or PLPLANEentry; if thickness is not specified on the PPLANE or PLPLANEentry and the Ti field is blank, a fatal error occurs)

If TFLAG = 1, Ti scales the thickness specified on the PPLANEor PLPLANE entry at the corresponding corner grid point. SeeRemark 4. (Real ≥ 0.0; Default = 1.0; if thickness is not specified


Chapter 6: Elements

Elements

Field Contentson the PPLANE or PLPLANE entry and the Ti field is blank, afatal error occurs)

TM4,TM5,TM6

Thickness override or thickness scaling factor at mid-side grid points.See Remarks 3 and 5.

If TFLAG = 0, TMi overrides the thickness specified on thePPLANE or PLPLANE entry at the corresponding mid-side gridpoint. (Real ≥ 0.0; Default = thickness linearly interpolated fromthe thicknesses at the corner grid points of the same elementedge)

If TFLAG = 1, TMi scales the thickness specified on the PPLANEor PLPLANE entry at the corresponding mid-side grid point. SeeRemark 4. (Real ≥ 0.0; Default = thickness linearly interpolatedfrom the thicknesses at the corner grid points of the same elementedge)

REMARKS:1. Element identification numbers should be unique with respect to all other element

identification numbers.

2. The grid points of all axisymmetric elements (CTRAX3, CQUADX4, CTRAX6,CQUADX8, CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8), plane stresselements (CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8), and plane strain elements(CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8) must all lie in either the XZ-plane,or all in the XY-plane of the basic coordinate system. The software automaticallydetermines the orientation.

3. At least one grid point must have a non-zero thickness. Otherwise, a fatal erroroccurs.

4. If TFLAG = 1, the thicknesses that the software uses at the grid points arecalculated as follows:

where:

t1, t2, t3, t4, t5, t6 Thicknesses at G1, G2, G3, G4, G5, and G6, respectively.

T1, T2, T3, TM4,TM5, TM6

Values in the T1, T2, T3, TM4, TM5, and TM6 fields,respectively.


Elements

Chapter 6: Elements

T Thickness specified on the PPLANE or PLPLANE entry.

5. If a TMi field is specified, along the corresponding element edge, the software usesthe TMi value and the thicknesses at the corner grid points on the same elementedge to create a quadratic representation of the thickness along the element edge.

6. Grid points G1 through G6 must be ordered as shown in Figures 1 and 2.

7. The element coordinate system is the basic coordinate system.

8. The reference coordinate system for the output of linear stress/strain is thematerial coordinate system.

9. The element behaves linearly if used in a SOL 106 or SOL 129 analysis.

10. The cyclic solution types (SOLs 114,115,116,118) and the aeroelastic solutiontypes (SOLs 144,145,146) are not supported.

11. GPSTRESS and GPSTRAIN output are not supported.

12. For any grid point (Gi) selected on axisymmetric, plane stress, or plane stainelements, if you select a displacement coordinate system with the CD field on theGRID entry, you must orient the system according to the following rules:

• If the elements are defined on the XY-plane of the basic coordinate system,the Z-axis is the out-of-plane direction. In this case, you must orient the Z-axis(φ-axis for a spherical system) of the displacement coordinate system to beparallel with the Z-axis of the basic coordinate system.

• If the elements are defined on the XZ-plane of the basic coordinate system,the Y-axis is the out-of-plane direction. In this case, you must orient theY-axis (θ-axis for the cylindrical and spherical systems) of the displacementcoordinate system to be parallel with the Y-axis of the basic coordinate system.

13. For orthotropic materials, the THETA angle orients the principal materialcoordinates of the element relative to the basic coordinates. Figures 1 and 2show the positive sense of the THETA angle when the element is defined on theXZ-plane and XY-plane, respectively.


Chapter 6: Elements

Elements

Figure 6-1. CPLSTS6 Element Geometry and Coordinate Systems, XZ-Plane

Figure 6-2. CPLSTS6 Element Geometry and Coordinate Systems, XY-PlaneREMARKS

RELATED TOSOL 601:

1. The reference coordinate system for the output of linear stress/strain is thematerial coordinate system except when MAT1 is assigned to the element. Thenthe material coordinate system is ignored and the linear stress/strain is output inthe basic coordinate system.

2. The reference coordinate system for the output of nonlinear stress/strain is theundeformed element coordinate system, which is the same as the basic coordinatesystem.

3. The reference coordinate system for the output of hyperelastic stress/strain isthe basic coordinate system.


Elements

Chapter 6: Elements

4. 6-node triangular elements may be converted to 7-node triangular elements (with1 additional node at the centroid of the element) by specifying ELCV=1 in theNXSTRAT entry.

5. If THETA is defined, the positive element normal direction, which is defined by G1,G2, and G3 connectivity using the right-hand-rule, must be consistent with thenegative Y-direction (if in XZ-plane) or the positive Z-direction (if in XY-plane) ofthe basic system.

6. The TM4, TM5, and TM6 fields are ignored. Thus, the thickness along the elementedges can be constant or can vary linearly only.

REMARKSRELATED TO

SOL 402:1. The grid points must be defined in the XY-plane of the global coordinate system.

2. The SPCFORCES output results are always in force unit using the thickness(es)of the element or the thickness defined in the PPLANE bulk entry.

3. The TM4, TM5, and TM6 fields are ignored. Thus, the thickness along the elementedges can be constant or can vary linearly only.


Chapter 6: Elements

Elements

CPLSTS8

Plane Stress Quadrilateral Element Connection

Defines a plane stress quadrilateral element for use in linear or nonlinear analysis.FORMAT:

1 2 3 4 5 6 7 8 9 10CPLSTS8 EID PID G1 G2 G3 G4 G5 G6

G7 G8 THETA TFLAG T1 T2 T3 T4

TM5 TM6 TM7 TM8

EXAMPLE:

CPLSTS8 207 3 31 33 73 71 32 51

53 72 70.0 1 0.5 0.5 0.5 0.5

0.5 0.75 0.75 0.6

FIELDS:

Field Contents


PID Property identification number of a PPLANE or PLPLANE entry.(Integer > 0; Default = EID)

Gi Grid point identification number of connected points. (Unique integers> 0; No default)

THETA Material property orientation angle in degrees. See Remark 13.THETA is ignored for hyperelastic elements. (Real; Default = 0.0)

TFLAG Flag that specifies whether Ti and TMi are thicknesses that overridethe thickness specified on the PPLANE or PLPLANE entry (TFLAG =0) or are factors that scale the thickness specified on the PPLANE orPLPLANE entry (TFLAG = 1). (Integer 0 or 1; Default = 0)

T1,T2,T3,T4 Thickness override or thickness scaling factor at corner grid points.See Remark 3.

If TFLAG = 0, Ti overrides the thickness specified on the PPLANEor PLPLANE entry at the corresponding corner grid point. (Real ≥0.0; Default = thickness specified on the PPLANE or PLPLANEentry; if thickness is not specified on the PPLANE or PLPLANEentry and the Ti field is blank, a fatal error occurs)

If TFLAG = 1, Ti scales the thickness specified on the PPLANEor PLPLANE entry at the corresponding corner grid point. SeeRemark 4. (Real ≥ 0.0; Default = 1.0; if thickness is not specified


Elements

Chapter 6: Elements

Field Contentson the PPLANE or PLPLANE entry and the Ti field is blank, afatal error occurs)

TM5,TM6,TM7,TM8

Thickness override or thickness scaling factor at mid-side grid points.See Remarks 3 and 5.

If TFLAG = 0, TMi overrides the thickness specified on thePPLANE or PLPLANE entry at the corresponding mid-side gridpoint. (Real ≥ 0.0; Default = thickness linearly interpolated fromthe thicknesses at the corner grid points of the same elementedge)

If TFLAG = 1, TMi scales the thickness specified on the PPLANEor PLPLANE entry at the corresponding mid-side grid point. SeeRemark 4. (Real ≥ 0.0; Default = thickness linearly interpolatedfrom the thicknesses at the corner grid points of the same elementedge)

REMARKS:1. Element identification numbers should be unique with respect to all other element

identification numbers.

2. The grid points of all axisymmetric elements (CTRAX3, CQUADX4, CTRAX6,CQUADX8, CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8), plane stresselements (CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8), and plane strain elements(CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8) must all lie in either the XZ-plane,or all in the XY-plane of the basic coordinate system. The software automaticallydetermines the orientation.

3. At least one grid point must have a non-zero thickness. Otherwise, a fatal erroroccurs.

4. If TFLAG = 1, the thicknesses that the software uses at the grid points arecalculated as follows:

where:


Chapter 6: Elements

Elements

t1, t2, t3, t4, t5, t6, t7,t8

Thicknesses at G1, G2, G3, G4, G5, G6, G7, and G8,respectively.

T1, T2, T3, T4, TM5,TM6, TM7, TM8

Values in the T1, T2, T3, T4, TM5, TM6, TM7, TM8 fields,respectively.

T Thickness specified on the PPLANE or PLPLANE entry.

5. If a TMi field is specified, along the corresponding element edge, the software usesthe TMi value and the thicknesses at the corner grid points on the same elementedge to create a quadratic representation of the thickness along the element edge.

6. Grid points G1 through G8 must be ordered as shown in Figures 3 and 4.

7. The element coordinate system is the basic coordinate system.

8. The reference coordinate system for the output of linear stress/strain is thematerial coordinate system.

9. The element behaves linearly if used in a SOL 106 or SOL 129 analysis.

10. The cyclic solution types (SOLs 114,115,116,118) and the aeroelastic solutiontypes (SOLs 144,145,146) are not supported.

11. GPSTRESS and GPSTRAIN output are not supported.

12. For any grid point (Gi) selected on axisymmetric, plane stress, or plane stainelements, if you select a displacement coordinate system with the CD field on theGRID entry, you must orient the system according to the following rules:

• If the elements are defined on the XY-plane of the basic coordinate system,the Z-axis is the out-of-plane direction. In this case, you must orient the Z-axis(φ-axis for a spherical system) of the displacement coordinate system to beparallel with the Z-axis of the basic coordinate system.

• If the elements are defined on the XZ-plane of the basic coordinate system,the Y-axis is the out-of-plane direction. In this case, you must orient theY-axis (θ-axis for the cylindrical and spherical systems) of the displacementcoordinate system to be parallel with the Y-axis of the basic coordinate system.

13. For orthotropic materials, the THETA angle orients the principal materialcoordinates of the element relative to the basic coordinates. Figures 3 and 4show the positive sense of the THETA angle when the element is defined on theXZ-plane and XY-plane, respectively.


Elements

Chapter 6: Elements

Figure 6-3. CPLSTS8 Element Geometry and Coordinate Systems, XZ-Plane

Figure 6-4. CPLSTS8 Element Geometry and Coordinate Systems, XY-PlaneREMARKS

RELATED TOSOL 601:

1. The reference coordinate system for the output of linear stress/strain is thematerial coordinate system except when MAT1 is assigned to the element. Thenthe material coordinate system is ignored and the linear stress/strain is output inthe basic coordinate system.

2. The reference coordinate system for the output of nonlinear stress/strain is theundeformed element coordinate system, which is the same as the basic coordinatesystem.

3. The reference coordinate system for the output of hyperelastic stress/strain isthe basic coordinate system.

4. 8-node elements may be converted to 9-node elements (with 1 additional node atthe centroid of the element) by specifying ELCV=1 in the NXSTRAT entry.


Chapter 6: Elements

Elements

5. When THETA is defined, the positive element normal direction, which is defined byG1, G2, and G3 connectivity using the right-hand-rule, must be consistent with thenegative Y-direction (if in XZ-plane) or the positive Z-direction (if in XY-plane) ofthe basic system.

6. The TM5, TM6, TM7, and TM8 fields are ignored. Thus, the thickness along theelement edges can be constant or can vary linearly only.

REMARKSRELATED TO

SOL 402:1. The grid points must be defined in the XY-plane of the global coordinate system.

2. The SPCFORCES output results are always in force unit using the thickness(es)of the element or the thickness defined in the PPLANE bulk entry.

3. The TM5, TM6, TM7, and TM8 fields are ignored. Thus, the thickness along theelement edges can be constant or can vary linearly only.

Support for non-structural massSupport for using NSM, NSM1, NSML, and NSML1 bulk entries to define non-structural mass isexpanded. You can now use NSM, NSM1, NSML, and NSML1 bulk entries to specify non-structuralmass in elements that reference the following properties in the indicated solution types:

• PSHELL bulk entries in SOL 401.

• PCOMPG1 bulk entries in SOL 401.

• PPLANE bulk entries in all solutions.

In previous versions of the software, you can apply non-structural mass to elements that referencethese properties from the NSM fields on the property entries for the indicated solutions.

To add non-structural mass using NSM, NSM1, NSML, and NSML1 bulk entries, you must includea NSM case control command in your input file that selects the NSM, NSM1, NSML, NSML1, orNSMADD bulk entry. The NSMADD bulk entry allows you to use combinations of NSM, NSM1,NSML, and NSML1 bulk entries.

For more information, see NSM, NSM1, NSML, and NSML1.


Elements

Chapter 6: Elements

NSM

Define Non-Structural Mass

Defines a set of non-structural mass by ID.FORMAT:

1 2 3 4 5 6 7 8 9 10

NSM SID TYPE ID VALUE ID VALUE ID VALUE

ID VALUE ID VALUE etc.

EXAMPLE:

NSM 11 PSHELL 16 0.25

FIELDS:

Field Contents

SID Non-structural mass set identification number. (Integer > 0)

TYPE Set points to either property entries or element entries. Properties are:PBAR, PBARL, PBEAM, PBEAML, PBCOMP, PCOMP, PCOMPG,PCOMPG1, PPLANE, PROD, CONROD, PBEND, PSHEAR,PSHELL, PTUBE, and PRAC2D. ELEMENT list of individual elementIDs of element that can have NSM. (Character)

ID Property or Element ID. (Integer > 0)

VALUE Non-structural mass per unit area for 2D elements, or non-structuralmass per unit length for 1D elements. (Real)

REMARKS:1. Non-structural mass sets must be selected with Case Control command NSM =

SID.

2. The ELSUM Case Control command will give a summary of both structural andnon-structural mass by element or property type.

3. If you specify non-structural mass on a property entry and also specify it on aNSM bulk entry (or a NSMADD bulk entry that lists the NSM bulk entry) thatreferences the property entry, the software sums the non-structural mass value onthe property entry and the non-structural mass value on the NSM bulk entry.


Chapter 6: Elements

Elements

NSM1

Define Non-Structural Mass

Alternate form for NSM entry. Defines non-structural mass entries by VALUE, ID list.FORMAT:

1 2 3 4 5 6 7 8 9 10

NSM1 SID TYPE VALUE ID ID ID ID ID

ID ID ID etc.

EXAMPLE:

NSM1 11 ELEMENT 0.46 1243 1532

ALTERNATEFORMS:

NSM1 SID TYPE VALUE ID THRU ID

NSM1 SID TYPE VALUE ALL

NSM1 SID TYPE VALUE ID THRU ID BY N

FIELDS:

Field Contents



ID Property or Element ID. (Integer > 0 or “ALL” or “THRU” or “BY” or N(the BY increment))

VALUE Non-structural mass per unit area for 2D elements, or nonstructuralmass per unit length for 1D elements. (Real)

REMARKS:1. Non-structural mass sets must be selected with Case Control command NSM =

SID.

2. Defining TYPE = PSHELL, PCOMP, PCOMPG, PCOMPG1, or PPLANE appliesmass to all of these types.Defining TYPE = PBEAM, PBEAML, or PBCOMP applies mass to all of thesetypes.Defining TYPE = PBAR or PBARL applies mass to both of these types.


Elements

Chapter 6: Elements

For example, the input “NSML1,12,PSHELL,12.5, ALL” will apply non-structuralmass to the elements associated to all PSHELL, all PCOMP, all PCOMPG, allPCOMPG1, and all PPLANE properties.

3. The ELSUM Case Control command will give a summary of both structural andnon-structural mass by element or property type.

4. If you specify non-structural mass on a property entry and also specify it on aNSM1 bulk entry (or a NSMADD bulk entry that lists the NSM1 bulk entry) thatreferences the property entry, the software sums the non-structural mass value onthe property entry and the non-structural mass value on the NSM1 bulk entry.


Chapter 6: Elements

Elements

NSML

Define Lumped Non-Structural Mass

Defines a set of lumped non-structural mass by ID.FORMAT:

1 2 3 4 5 6 7 8 9 10

NSML SID TYPE ID VALUE ID VALUE ID VALUE

ID VALUE ID VALUE etc.

EXAMPLE:

NSML 23 PSHELL 6 0.22

FIELDS:

Field Contents



ID Property or Element ID. (Integer > 0)

VALUE A lumped mass value to be distributed. See Remark 2. (Real)

REMARKS:1. If TYPE = ELEMENT is used, line element (CBAR, CBEAM, CBEND, CROD,

CTUBE, and CONROD) IDs cannot be mixed with area element (CQUAD4,CQUAD8, CQUADR, CTRIA3, CTRIA6, CTRIAR, CSHEAR, and CRAC2D) IDs.

2. VALUE is the total non-structural mass to be distributed across all IDs.

• Area element calculation (for example, CQUAD4):Mass for a particular element = (Element area) x (VALUE / ∑Element area forall IDs)

• Line element calculation (for example, CBEAM):Mass for a particular element = (Element length) x (VALUE / ∑Element lengthfor all IDs)

3. Non-structural mass sets must be selected with the case control command NSM =SID.

4. The ELSUM case control command will give a summary of both structural andnon-structural mass by element or property type.


Elements

Chapter 6: Elements

5. If you specify non-structural mass on a property entry and also specify it on anNSML bulk entry (or an NSMADD bulk entry that lists the NSML bulk entry) thatreferences the property entry, the software sums the non-structural mass value onthe property entry and the non-structural mass value on the NSML bulk entry.


Chapter 6: Elements

Elements

NSML1

Define Lumped Non-Structural Mass

Alternate form for NSML entry. Defines lumped non-structural mass entries by VALUE,ID list.

FORMAT:

1 2 3 4 5 6 7 8 9 10

NSML1 SID TYPE VALUE ID ID ID ID ID

ID ID ID etc.

EXAMPLE:

NSML1 13 ELEMENT 0.72 156 286

ALTERNATEFORMS:

1 2 3 4 5 6 7 8 9 10

NSML1 SID TYPE VALUE ID1 THRU ID2

1 2 3 4 5 6 7 8 9 10

NSML1 SID TYPE VALUE ALL

1 2 3 4 5 6 7 8 9 10

NSML1 SID TYPE VALUE ID1 THRU ID2 BY N

FIELDS:

Field Contents



ID Property or Element ID. (Integer > 0 or “ALL” or “THRU” (ID1 < ID2 for“THRU” option) or “BY” or N (N > 0))

VALUE A lumped mass value to be distributed. See Remark 2. (Real)

REMARKS:1. If TYPE = ELEMENT is used, line element (CBAR, CBEAM, CBEND, CROD,

CTUBE, and CONROD) IDs cannot be mixed with area element (CQUAD4,CQUAD8, CQUADR, CTRIA3, CTRIA6, CTRIAR, CSHEAR, and CRAC2D) IDs.


Elements

Chapter 6: Elements

2. VALUE is the total non-structural mass to be distributed across all IDs.

• Area element calculation (for example, CQUAD4):Mass for a particular element = (Element area) x (VALUE / ∑Element area forall IDs)

• Line element calculation (for example, CBEAM):Mass for a particular element = (Element length) x (VALUE / ∑Element lengthfor all IDs)

3. Alternate input forms using THRU, BY, and N can be included on differentcontinuation lines except for ALL. ALL can only be used on a single line input.

4. Non-structural mass sets must be selected with the case control command NSM =SID.

5. Defining TYPE = PSHELL, PCOMP, PCOMPG, PCOMPG1, or PPLANE appliesmass to all of these types.Defining TYPE = PBEAM, PBEAML, or PBCOMP applies mass to all of thesetypes.Defining TYPE = PBAR or PBARL applies mass to both of these types.

For example, the input “NSML1,12,PSHELL,12.5, ALL” will apply non-structuralmass to the elements associated to all PSHELL, all PCOMP, all PCOMPG, allPCOMPG1, and all PPLANE properties.

6. The ELSUM case control command will give a summary of both structural andnon-structural mass by element or property type.

7. If you specify non-structural mass on a property entry and also specify it on aNSML1 bulk entry (or a NSMADD bulk entry that lists the NSML1 bulk entry) thatreferences the property entry, the software sums the non-structural mass value onthe property entry and the non-structural mass value on the NSML1 bulk entry.


Chapter 6: Elements

Chapter 7: Multi-step nonlinear solution 401

Transient dynamic subcaseSolution 401 now supports a transient dynamic subcase type to request a direct transient responseanalysis. You designate the transient dynamic subcase by including the ANALYSIS=DYNAMICScase control setting in the subcase.

A transient response analysis computes the behavior of a structure subjected to a time-varyingexcitation. The equation of motion for the dynamic subcase includes the stiffness, damping, and massterms with the option to output displacement, velocity, and acceleration at each degree-of-freedom.

Similar to the other SOL 401 subcase types, the transient dynamic subcase can optionally includegeometry nonlinear effects when PARAM,LGDISP,1 is defined, and it can include the materialnonlinear effects when plasticity, creep, and viscoelasticity are defined. A linear dynamic analysisoccurs when no nonlinear conditions are present.

You use the same inputs to define time assigned and time unassigned mechanical and thermal loadsfor dynamic and static subcases. The difference is that for the dynamic subcase, the software usestime explicitly. For the static subcase, the software uses time to scale loads. See Loads in theMulti-Step Nonlinear User’s Guide.

Mass inputs

In the equation of motion for dynamic and modal subcases, the mass matrix is used in the inertia

force term . For the dynamic and static subcases, mass is also used to compute grid pointforces from the body loads such as gravity, angular velocity, and angular acceleration.

You can use the following inputs to define the mass properties for SOL 401:

• The mass matrix is automatically computed when mass density (ρ) is specified on the MATientries associated with the finite elements.

• Nonstructural mass per unit length can be defined on the PBAR and PBEAM entries. In addition,nonstructural mass per unit area can be defined on the PSHELL entries.

• The CONM1 entry allows you to input a fully coupled 6x6 mass matrix. You can also define halfof the terms on the CONM1 entry for a symmetric matrix.

• The CONM2 entry defines concentrated mass and inertia terms at a grid point.

• The CMASSi bulk entries can be used to define mass at a single degree-of-freedom (DOF) whenonly one DOF is referenced, or it can be used to define coupling between two DOF.

The following parameters are related to the specification of mass properties.



• PARAM,COUPMASS,1 – Requests that the coupled mass option be used rather than thelumped mass option for the elements that support the coupled mass option. By default, with thelumped mass option, the mass of an element is divided and distributed to the grid points. Withthe coupled mass option, the distributed mass is replaced by a non-diagonal mass matrix thatcouples the connected grid points. The coupled mass option is sometimes more accurate,but it uses more computation time.

Note that COUPMASS controls the type of mass matrix used for the inertia term in the dynamicequation of motion. Although, SOL 401 always computes body forces using the consistent massmatrix independent of the PARAM,COUPMASS specification.

• PARAM,WTMASS,value – Specifies a factor by which to multiply the mass of the structure toobtain dimensionally correct mass. For example, if the ft-lb-sec system is used, and the massinput unit is pounds, then value = 1/32.174 = .031081. This factor operates on all mass terms.

Damping

All damping definitions for the SOL 401 transient subcase are applied to the viscous damping force

term in the equation of motion, where is the velocity, and is the total viscousdamping matrix. The total viscous damping is the sum of three types of optional damping inputs:

where,

• is viscous damping explicitly defined with the CDAMPi, CVISC, CBUSH, or CBUSH1Dbulk entries.

• is damping proportional to the mass and stiffness matrices. The parameter ALPHA1 definesdamping proportional to the mass matrix, and the parameter ALPHA2 defines damping that is

proportional to the stiffness matrix. The proportional damping is computed as

• is structural damping, which is converted to viscous damping. The GE field on the MATientry defines the structural damping for the elements that reference the material entry. Theparameter G defines a global structural damping, which is applied to the entire stiffness matrix. Gand GE are converted to viscous damping using the parameters W3 and W4 as follows.

Where:

G is the overall structural damping coefficient (PARAM,G).

W3 is a frequency in radians per unit time (PARAM,W3) for the conversion of the overall structuraldamping into viscous damping.

[K] is the global stiffness matrix.



Multi-step nonlinear solution 401

GE is the element structural damping coefficient defined using the GE field on the material entries.

W4 is a frequency in radians per unit time (PARAM,W4) for the conversion of element structuraldamping into viscous damping.

[KE] is an element stiffness matrix.

Note that GE and G by themselves are dimensionless multipliers of the stiffness. Although,the viscous damping explicitly defined with the CDAMPi, CVISC, CBUSH, or CBUSH1D bulkentries have damping units.

Loads and constraints

The dynamic subcase supports the same loads and constraints as the static subcase. Specifically,both subcases support the definition of the LOAD and the DLOAD case control commands, whichreference time-unassigned and time-assigned loads, respectively. When the time unassigned loadsare defined, the parameter LVAR on the NLCNTL bulk entry is available to optionally ramp the loadsby the number of increments defined on the TSTEP1 bulk entry.

Time unassigned and time assigned temperature loads are also supported for both the dynamic andstatic subcases. The time unassigned temperature load is requested with the TEMP(LOAD) casecontrol command, and the time assigned temperature load is requested with the DTEMP case controlcommand. When the time unassigned temperature loads are defined, the parameter TVAR on theNLCNTL bulk entry is available to optionally ramp the temperature loads by the number of incrementsdefined on the TSTEP1 bulk entry.

You use the same inputs to define time assigned and time unassigned loads for dynamic and staticsubcases. The difference is that for the dynamic subcase, the software uses time explicitly.

Note that a time unassigned load is not specifically defined with a time function. Although, when youapply a time unassigned load and choose the ramp option, it behaves similar to a time assigned load.

See Loads in the Multi-Step Nonlinear User’s Guide.

Initial conditions

You can request initial displacement and velocity conditions for a dynamic subcase with the IC=ncase control command. The integer n on the IC case control references a TIC bulk entry. Only thePHYSICAL option (default) on the IC command is available, which is the option for defining initialconditions on grid points.

The IC command can be defined either in a dynamic subcase, or if all subcases includeANALYSIS=DYNAMICS, you can define the IC command above the subcase level (globally). Foreither definition, the software will only apply an initial condition to a dynamic subcase that is eitherthe first subcase, or if it is not the first, it must be non-sequentially dependent (SEQDEP=NO). Thesoftware ignores an initial condition when a dynamic subcase does not satisfy these rules, andinstead starts from the state of displacement, velocity, and acceleration from the previous preload,static, or dynamic subcase.

Subcase sequencing

The new dynamic subcase can be combined with any of the other subcase types (STATICS,PRELOAD, MODES, CYCMODES, FOURIER). Below are some example scenarios.

Note that a sequentially dependent (SEQDEP=YES) modes subcase cannot follow a dynamicsubcase. Doing so will result in a fatal error.




Note that if you are incrementing time across sequentially dependent static and dynamic subcases,your time steps must continue from one subcase to next.

• A non-sequentially dependent (SEQDEP=NO) dynamic subcase can be defined at any location inthe case control. For this case, the dynamic subcase begins from time=0.0, and with any initialvelocity or acceleration conditions you have defined for the model.

Example:

SUBCASE 1ANALYSIS=STATICSNLARCL=1....SUBCASE 2ANALYSIS=DYNAMICSSEQDEP=NO....

• A sequentially dependent (SEQDEP=YES) dynamic subcase can be defined at any location inthe case control. It can be defined before or after any of the other subcase types (STATICS,PRELOAD, MODES, CYCMODES, FOURIER) except for a static subcase, which requests anonlinear buckling analysis with the NLARCL=ID case control command. For all other cases, thedynamic subcase will start from the last converged configuration and state variables from the endof the prior static, preload, or dynamic subcase.

Example:

SUBCASE 1ANALYSIS=PRELOAD....SUBCASE 2ANALYSIS=STATICSSEQDEP=YES....SUBCASE 3ANALYSIS=DYNAMICSSEQDEP=YES....SUBCASE 4ANALYSIS=STATICSSEQDEP=YES....SUBCASE 5ANALYSIS=PRELOADSEQDEP=YES....SUBCASE 6ANALYSIS=DYNAMICSSEQDEP=YES....

• Any non-sequentially dependent (SEQDEP=NO) subcase type can follow a dynamic subcase.

Example:

SUBCASE 1




ANALYSIS=DYNAMICS....SUBCASE 2ANALYSIS=STATICSSEQDEP=NO....SUBCASE 3ANALYSIS=DYNAMICSSEQDEP=YES....SUBCASE 4ANALYSIS=DYNAMICSSEQDEP=NO....

• A dynamic subcase can be included with a cyclic symmetry model. The cyclic symmetry requestis defined above the subcases (globally) and applies to all subcases. When either a static ordynamic subcase is included in a cyclic symmetry model, the solution is only performed forthe 0th harmonic.

Example:

CYCSET=100....SUBCASE 1ANALYSIS=STATICS....SUBCASE 2ANALYSIS=DYNAMICSSEQDEP=YES/NO....

Automatic time stepping

You can use the existing AUTOTIM parameter on the NLCNTL bulk entry to deactivate automatic timestepping. Automatic time stepping is on by default.

Output summary

The dynamic subcase supports the same output requests as the static subcase. In addition, you canalso request velocity and acceleration for the dynamic subcase. All output for SOL 401 is in SORT1format, including the dynamic subcase. SORT2 output is not supported by SOL 401.

See Supported output in the Multi-Step Nonlinear User’s Guide for the complete list of supportedoutput.

Time integration methods

Two types of analysis can be performed with the dynamic subcase:

• When the dynamic analysis includes the stiffness, damping, and inertia terms, the generalequation of motion is as follows.




• You can optionally turn the inertial effects off for a dynamic subcase by setting the parameterINERTIA=NO on the NLCNTL bulk entry. The general equation of motion for this analysis isas follows.

At each time step, a set of linear or nonlinear equations is solved. A full or modified Newton-Raphsonstrategy can be used.

The new TINTMTH parameter is available on the NLCNTL bulk entry to select the time integrationmethod. In addition, the new parameters; BETA, GAMA, ALFA, and TETA are available on theNLCNTL bulk entry to define constant terms referenced in the following integration methoddescriptions.

• Newmark Method

Velocity is obtained from acceleration using a generalized single step integration operator as

Equation 7-1.

A similar integration operator is used to obtain displacement as

β and γ correspond to the parameters BETA and GAMA on the NLCNTL bulk entry.

o β= 1/4 and γ= 1/2 correspond to the assumption of average constant acceleration over thetime step. This set of values provides the Newmark unconditional scheme with maximumaccuracy.

o β= 1/6 and γ= 1/2 correspond to the assumption of linear acceleration over the time step.

Using a central difference operator for integrating velocity implies , so that we have




Equation 7-2.

From Equation 7-2, accelerations in terms of current displacements and state at t are derived as:

Equation 7-3.

Then using Equation 7-1 and the chain rule, fc can be derived as . Likewise velocitiesin terms of current displacements and state at t are obtained as:

Equation 7-4.

Note that the terms within square brackets in Equations 7-3 and 7-4 only depend ondisplacements, velocities and accelerations at t, and terms that contribute to the integrationoperator. Therefore, the former quantities should be stored as state variables (at nodes).

Finally the corresponding residual is computed as:

The residual and Jacobian for the Newmark operator are summarized in the following figure.




Figure 7-1. Newmark operator

• Hilber-Hughes-Taylor (HHT) Method

The HHT integrator generalizes the Newmark operator, and in doing so, introduces a smallamount of numerical damping by weighting the residual between previous and current time step.This is done by modifying the (residual) equilibrium equations as

where α corresponds to the parameter ALFA parameter on the NLCNTL bulk entry.

Note that we can simply retain the definitions and most expressions from the Newmark operator,and summarize the HHT operator in the following figure.

Figure 7-2. HHT operator

This procedure includes numerical damping in the high frequency spectrum. This numericaldamping has a stabilizing effect on the time integration procedure while guaranteeing very goodaccuracy of integration of the low frequency range (including rigid body motion in particular).The particular value α= 0 generates zero numerical damping (and corresponds to the classicalNewmark scheme with β= 1/4 and γ = 1/2) while α= 1/3 generates maximum damping. It isgenerally recommended to use an intermediate value (α= 0.05 or α= 0.1).

• Generalized Theta Method




The Generalized Theta Method modifies the Hilber-Hughes-Taylor method by rewriting theequilibrium expression at time tn+1, then applying the time integration described with Newmark'smethod:

where θ corresponds to the parameter TETA parameter on the NLCNTL bulk entry.

The Newmark parameters are obtained by:

This procedure allows to introduce some numerical damping in the high frequency spectrumof the system under consideration. This numerical damping has a stabilizing effect on thetime integration procedure while guaranteeing very good accuracy of integration of the lowfrequency range (including rigid body motion in particular). To obtain maximum damping inthe high frequencies and minimum damping in the low frequencies α and θ have to satisfy thefollowing relationship:

and θ has to satisfy .

• Modified Generalized Theta Method

The Modified Generalized Theta Method is obtained using a vector a of acceleration-like variablesin the Newmark integration formula.

Those additional variables are related to the accelerations by the following equation:

where,




are optimal algorithmic parameters for second-order ODEs.

This procedure allows to introduce some numerical damping in the high frequency spectrum ofthe system under consideration. This numerical damping has a stabilizing effect on the timeintegration procedure while guaranteeing very good accuracy of integration of the low frequencyrange (including rigid body motion in particular). Compare to Hilber-Hughes-Taylor method andGeneralized Theta Method, this scheme enforces exactly equilibrium at every time step, whichguaranties second-order accuracy also for the accelerations and less sensitivity to variabletime steps

Damping is controlled by the spectral radius at infinity ρ∞: an undamped scheme is characterizedby ρ∞= 1, while ρ∞= 0 provides asymptotic annihilation of the high frequency response.

Restarts in SOL 401You can now perform a restart solution with SOL 401. A restart solution is a method of continuingfrom a previous run without having to start from the beginning. For example, an initial run could be apre-stressed condition which includes a bolt preload subcase and multiple static subcases. You canthen use the restart file created from the initial run in repeated restart solutions.

The restart solution is also useful when a solution fails to converge. The software saves thecompleted solution points up to the failed time point. When restarting, you can reduce the size of yoursolution increments or perhaps adjust the nonlinear control parameters to help convergence.

For the restart run, you can change load, SPC, MPC, element birth/death, contact, and subcasedefined nonlinear control parameters. By default, you cannot create new grid points or elements,change grid point locations, change glue conditions, or modify materials. See Model check.

Initial run

The initial solution input file can include any combination of static, dynamic, and preload subcasetypes. The modal, cyclic, Fourier subcase types, and nonlinear buckling are not supported in theinitial run.

For the initial run, when you include the new parameter definition RSTGEN=YES on the NLCNTLGbulk entry, the software writes restart data to the same .op2 file in which results are written. The .op2file produced from the initial run will include saved restart solution points from the end of each static,dynamic, and preload subcase. In addition, if convergence fails in a static or dynamic subcase, arestart point is written from the last converged time step. If a preload subcase fails to converge, norestart point is written for that subcase. A preload subcase must complete for a restart point tobe written.

For example, the following input file structure includes the parameter definition RSTGEN=YES onthe NLCNTLG bulk entry to request restart data. If all three subcases complete, restart data willbe written to the .op2 file at the end of each.

....LGDISP=1SUBCASE 1ANALYSIS=PRELOADSUBCASE 2ANALYSIS=STATICS




SUBCASE 3ANALYSIS=STATICS....BULK DATANLCNTLG,RSTGEN,YES....

When you request an initial solution with RSTGEN = YES, the .op2 file is always written as 64-bit,and the parameter OP2FMT is ignored.

Restart run

In your restart input file, you will include an ASSIGN statement that references the .op2 file createdfrom the initial solution. The ASSIGN statement must include a unit number of 161 or larger. Inaddition, if the unit number on your ASSIGN statement is not 161, you must define the new parameterRSTUNIT=unit number on the NLCNTLG bulk entry.

Example one:ASSIGN INPUTT2='OUTDIR:restart_op2_filename.op2' UNIT=161....BULK DATA***NLCNTLG,RSTUNIT is not required for this example since UNIT=161**....

Example two:ASSIGN INPUTT2='OUTDIR:restart_op2_filename.op2' UNIT=201....BULK DATANLCNTLG,RSTUNIT,201***NLCNTLG,RSTUNIT is required for this example since UNIT>161**....

If your restart run input file has the same name as your initial run input file, you should rename the.op2 file created from the initial run if you want to preserve it. Otherwise, it will be overwritten duringthe restart solution. Your ASSIGN statement should also refect the new .op2 file name.

The .op2 file created from the initial run can include saved restart solution points from multiplesubcases. For the restart run, you use the new parameter RSTFROM=n on the NLCNTLG bulkentry to select which initial subcase ID to restart from. Since the RSTFROM=n parameter has nodefault, it is required.

The start time for a restart solution is always the end or final time of the solution point you arerestarting from. For example, let us assume your initial solution included a subcase 1 with time goingfrom 0.0 to 10.0 seconds, a subcase 2 with time going from 10.0 to 30.0 seconds, and all time stepsconverged successfully for each subcase. If you restart from subcase 2, the start time will be 30.0seconds. If your first subcase in the restart input file includes a TSTEP1 bulk entry with an end time of40 seconds, and a number of increments of 5, the time steps for this restart subcase will be 32.0,34.0, 36.0, 38.0, and 40.0 seconds.

The number of subcases and their IDs in the restart input file can be the same as those used in theinitial run, or they can be completely different. You use the new parameter EXEFROM=n on theNLCNTLG bulk entry to select a subcase ID in the restart run input file in which to begin the restartsolution. Since the EXEFROM=n parameter has no default, it is required. The software automaticallymakes the subcase you select with EXEFROM=n sequentially dependent on the subcase you selectwith RSTFROM=n, even if SEQDEP=NO is defined in the subcase selected by EXEFROM=n.




For example, suppose your initial run included three subcases with IDs 1, 2, and 3, all threecompleted, and you have decided to restart from the initial subcase 2 by defining the parameterRSTFROM=2 in your restart input file. In addition, your restart input file has the subcase IDs 1, 3, 5,and 7 and you would like to begin the restart solution with subcase 5. As a result, you will also defineEXEFROM=5 in your restart input file. See Special case: EXEFROM=RSTFROM below.

You can request restart data from a restart run by including the parameter definition RSTGEN=YESon the NLCNTLG bulk entry in the restart run input file. This is useful when convergence problemsare occuring. With each consecutive restart, you are saving the solution progress.

You can define any of the subcase types in the restart input file. Although, if the subcase youselect with RSTFROM is a dynamics subcase, the subcase you select with EXEFROM cannot bea modal, cyclic, or Fourier.

In all restart runs, the software copies the results from the initial run .op2 file into the .op2 file createdin the restart run. As a result, the restart .op2 will include both the initial run subcase results and therestart run subcase results. The software automatically relabels any subcase IDs if a conflict occursbetween the initial run subcase IDs and the restart run subcase IDs.

If you are unsure of the resulting subcase IDs and the time steps in a restart .op2 file, you can loadthe .op2 file into Simcenter 3D post processing. The Post Processing Navigator organizes theresults according to subcase ID and time step.

Special case: EXEFROM = RSTFROM

The purpose of this special case is to continue a non-converged subcase. Only the solution controlparameters on the NLCNTL bulk entry and the time step intervals on the TSTEP1 bulk entry canchange from the initial run to the restart run.

Specifically:

• The TSTEP1 entry defined for the first subcase in the restart input file must have the same endtime as the end time defined for the non-converging subcase in the initial run. The Ninc and Noutfields that define the time step intervals and output are applied from the start time to Tend.

• Any new or modified solution control parameters defined on the NLCNTL entry in the restartinput file apply only from the start time to Tend.

• To keep compatibility with the initial run, the general solution parameters LVAR, TVAR, THRMST,and LOADOFF that are related to loading cannot change.

Model check

By default, during the restart solution, a model check occurs that compares the model data in therestart input file with the model data stored from the initial run .op2 file. A fatal error will occur if modeldifferences are found. There are exceptions where the model may need to be modified. For example,you may need to add a spring element to help a failing solution complete. The new parameterMDLVAL on the NLCNTLG bulk entry is available to turn the model check off.

You can remove all model data from the restart input file and the model validation will be skipped. Forthis case, the software uses the model data in the initial run .op2 file.

Restart parameter summary:




RSTGEN For the initial run, requests that restart data will be saved forstatic, dynamic, and preload subcases. SOL 401 saves therestart data in the output OP2 file. (Character; Default = NO).

YES = Restart data is saved.

NO = Restart data is not saved.

RSTUNIT=n For the restart run, defines the unit number of the external restartfile. The unit number must also be specified on an ASSIGNstatement that references the physical filename of the .op2.(Integer≥161; Default=161)

RSTFROM =n For the restart run, defines the subcase ID from which torestart. This subcase ID was defined in the initial run input file.RSTFROM has no default and must be defined. (Integer>0; Nodefault).

EXEFROM = n For the restart run, defines the subcase ID from which to execute.This subcase ID is defined in the restart run input file. EXEFROMhas no default and must be defined. (Integer>0; No default)

MDLVAL For the restart run, allows the option to turn off the modelvalidation check (Character; Default = “YES”).

YES = Request model validation.

NO = Do not request model validation.

Support for plasticity and creep in bars and beamsBeginning with NX Nastran 12, solution 401 began supporting the CBAR and CBEAM elements.The CBAR and CBEAM elements supported large displacements and rotations when you definedPARAM,LGDISP,1.

Now the CBAR and CBEAM elements also support plasticity and creep nonlinear materials. Youdefine a plastic material by referencing both the MAT1 and MATS1 bulk entries in the regions whereyou expect plasticity to occur. You define a creep material by referencing both the MAT1 andMATCRP bulk entries in the regions where you expect creep to occur. For the nonlinear materialbehavior to be included in the solution, you must reference the nonlinear materials from the PBARLand PBEAML property entries that define one of the following cross section types: TUBE, L (PBEAMLonly), I, CHAN, T, BOX, BAR, I1, CHAN1, Z, and ROD.

The CBAR and CBEAM elements in SOL 401 do not use a plastic hinge approach, which is used bythe CBEAM elements in SOL106. As a result, they are not limited to elastic-perfectly plastic materials(H=0.0) defined with the MATS1 bulk entry. For the CBAR and CBEAM elements in SOL 401, youcan use the same plastic materials on the MATS1 entry which are supported for solid and shellelements, such as H≠0.0 or stress-strain data.

The cross section types on the PBARL and PBEAML that are not listed above and the PBAR andPBEAM entries are supported by SOL 401 if you reference a linear material entry. If you reference anonlinear material for these properties or cross section types, the solution will end with a fatal error.




You can optionally define a different cross-section at ends A and B, and the software will computea linear variation. Cross section definitions at intermediate stations are ignored when a nonlinearmaterial is applied.

See Plasticity analysis.

See Creep analysis.

Contact improvementsThe following contact improvements are available for SOL 401.

• Contact conditions are supported in the new SOL 401 transient dynamics subcase.

• Contact conditions are supported with the new SOL 401 restart capability.

• A new adaptive contact stiffness option is available. You can use the new PENADAPT parameteron the BCTPARM bulk entry to select the new option.

PENADAPT: Option to adaptively modify the contact stiffness between iterations. (Integer;Default=0)

0 – Penalty factor is not adaptively modified by the program.

1 – Penalty factor is adaptively modified.

• A new contact contact algorithm option is available. You can use the new METHOD parameter onthe BCTPARM bulk entry to select the new option.

METHOD: Selects the contact algorithm. (Integer; Default=2)1 - Pure Penalty Method.

2 - Augmented Lagrangian Method.

• An option is now available for the software to remove initial separation by moving grid points sothey are coincident. You use the new ADJUST parameter on the BCTPARM bulk entry to selectthe option.

ADJUST: Request for the software to remove initial separation by moving grid points. (Real;No default)

The software uses an adjustment tolerance to move the source grid points onto the target faceswhen the absolute value of the initial separation distance is below the adjustment tolerance. Theadjustment tolerance is computed as ADJUST * characteristic length.

If ADJUST = 0.0, only the grid points that are initially over-closed are adjusted as long as theover-closure is below the characteristic length.

If ADJUST > 0.0, the adjustment is applied to grid points that are initially open with a gap smallerthan the value of ADJUST * characteristic length.

Note: ADJUST works from the grid point locations and INIPENE works from the Gauss pointlocations. If both are defined, ADJUST is first applied, then INIPENE.

• The existing GUPDATE parameter on the BCTPARM bulk entry can now be defined as a localparameter. Previously, it could only be defined as a global parameter.




For example, if you have ten contact pairs in different regions of your model, each contact pairwill be defined with a unique BCTSET entry each with a unique ID, and these pairs (their IDs)are combined into a single contact set using a BCTADD entry. You can define ten unique setsof parameters for each of your contact pairs. These unique parameter settings defined on tenBCTPARM entries are local parameters. You can also define global parameter settings if youdefine a BCTPARM entry with the same ID as your BCTADD entry. A local parameter definitionoverrides a global definition.

• When the existing PENTYP=1 (default) is defined on the BCTPARM bulk entry, the contactstiffness calculation uses the modulus values defined on your MATi entries in the computation.

Now this computation also uses temperature dependent material properties defined with theMATTi entries.

• The new OFFSET parameter on the BCTPARM bulk entry is available to add a constant offsetdistance for a contact pair.

OFFSET: Constant offset distance for a contact pair. (Real; Default = 0.0)

This value overwrites an offset defined for a region on the BCRPARA entry.

If you define both the OFFSET and INIPENE parameters, the software adds the offset after itevaluates any gaps or penetrations as a result of the INIPENE setting.

• The new TZPENE parameter on the BCTPARM bulk entry is available to ramp the removalof initial penetrations.

TZPENE: End time when initial penetrations will be eliminated. (Real≥0.0; Default = 0.0)TZPENE ramps the removal of initial penetrations. For example, if a subcase start time is 5.0,end time is 10.0, and TZPENE=7.2, the initial penetrations will be eliminated starting from thebeginning of the subcase (5.0) until time=7.2. Ramping the removal of initial penetrations canhelp convergence.

If TZPENE=0.0, the initial penetrations are eliminated in the first subcase.

• The new DISP parameter on the BCTPARM bulk entry is available to select the sliding formulation.

DISP: Selects the sliding contact formulation. (Integer; Default=0)0 – Contact pairing is automatically detemined by the software based on the amount of relativesliding in the pair.

1 – Small sliding formulation. Contact pairing is not updated with sliding displacements and isbased on the initial geometry.

2 – Large sliding formulation. Contact pairing is updated with sliding displacements.

Note: When DISP=1, GUPDATE is internally set to 0 (no pairing update).

When DISP=2, GUPDATE is set to 4 (update every iteration).

When DISP=0 (AUTO), GUDPATE is internally set to 3 for small displacement solutions (LGDISP= -1), and is set to 2 for large displacement solutions (LGDISP = 1).

• If you request stabilization damping with the CTDAMP parameter on the BCTPARM bulk entry,the CTDAMPN and CTDAMPT parameters are available to either scale the damping value, whichthe software automatically computes, or to define the normal damping value explicitly.




Now the CTDAMPN and CTDAMPT parameters can be assigned an integer value that selectsa TABLEDi entry defining a normal damping coefficient as a function of the normal penetrationdistance. The table ordinate unit is Pressure/Velocity, and the abscissa unit is Length.

• The existing FRICMOD parameter on the BCTPARM bulk entry includes the following newfriction models.

FRICMOD=2: Friction is computed using the following product, which optionally depends ontime, velocity or temperature:

μ(t,T,v)= FPARA1 * CFVE(v) * CFTE(T) * CFNF(t)

FPARA1, CFNF, CFTE, and CFVE are all parameters defined on the BCTPARM entry. FRICion the BCTSET entry is ignored.

FPARA1 defines a constant friction value, and CFNF, CFTE, CFVE are integer inputs thatreference TABLEDi entries defining friction as a function of time, temperature, and velocity,respectively. If any of CFNF, CFTE, or CFVE are undefined, their contribution is ignored.FRICMOD=3: Two different friction coefficients are used depending on the sliding velocity.

This friction model uses the parameters VCRIT, FPARA1, and FPARA2 on the BCTPARM entry.FRICi on the BCTSET entry is ignored.

VCRIT defines the critical sliding velocity, FPARA1 (1 in the image below) defines the frictioncoefficient when the sliding velocity < VCRIT, and FPARA2 (2 in the image below) defines thefriction coefficient when the sliding velocity > VCRIT.

FRICMOD=4: Friction coefficient varies linearly with the sliding velocity.

This friction model uses the parameters FPARA1, VCRIT, and FPARA2 on the BCTPARM entry.FRICi on the BCTSET entry is ignored.

FPARA1 defines the friction coefficient at zero velocity, VCRIT defines the critical sliding velocity,and FPARA2 defines the friction coefficient at the critical sliding velocity. The friction varieslinearly between FPARA1 (1 in the image below) and FPARA2 (2 in the image below), up to thecritical sliding velocity VCRIT after which it remains constant.




Output for preload and constant time static subcasesA constant time subcase has a TSTEP1 bulk entry defined with a Tend which is the same as thestart time for that subcase. All bolt preload subcases have a constant time. Statics subcases can bedefined with a constant time if they are before all other subcases, and as a result, have Tend=0.0.

You can use the Ninc field on the TSTEP1 and on the BOLTSEQ entries to increment the loads,temperatures, and contact offsets for a constant time subcase or a bolt preload sequence.Incrementing a load can help convergence when a solution has difficulty.

For example, for a preload subcase which includes a bolt sequence, you can define the numberof increments (Ninc) for each sequence on the BOLTSEQ bulk entry. The Ninc defined for a boltsequence on the BOLTSEQ entry overrides the value defined on the TSTEP1 entry.

Previously, you could only request output at the end time for a constant-time subcase.

Now by default (Nout = YES), the software outputs results for the intermediate load incrementsdefined by Ninc. This also occurs for the incremental load steps in a bolt preload sequence. You canselect the previous behavior for a constant time subcase by defining Nout=END on the TSTEP1 entrydefined for that subcase, and output will only occur for the final load increment.

The following table summarizes the Nout field options for both constant time and non-constanttime subcases.

Nout Output frequency

YES (Default)

Output occurs at all user defined increments defined on the TSTEP1 andBOLTSEQ entries. User defined increments includes the incrementsresulting from Ninc>1 for a constant time subcase. Output does not occur forany software created increments as a result of subincrements or bisection.

END Output occurs at the end time.

ALLOutput occurs at all user defined increments on the TSTEP1 and BOLTSEQentry (same output as Nout=YES), plus any software created increments asa result of subincrements or bisection.

Integer = 0 No output occurs.

Integer > 0 Output is computed at every Nout user defined increment specified on theTSTEP1 or BOLTSEQ entries.

CPLD Output occurs only at coupling times. This option can only be defined by theSimcenter 3D Multiphysics environment.

For a constant time subcase, the output as a result of the Ninc>1 on the TSTEP1 entry is labeled“Load Factor” in the output.




For a non-constant time subcase, the output as a result of the time steps defined on the TSTEP1,and any additional software increments created from automatic time stepping are labeled “TimeStep” in the output.

Element addition and removalSOL 401 now supports the capability to add or remove elements during a solution at pre-definedtime points. For example, you can represent a material removal process while the model is ina loaded state.

The software adds or removes the associated mass and stiffness from the solution. Damping isnot added or removed.

In addition, SOL 401 now also supports the capability to remove elements based on a state of strainat the element integration points. This is useful to represent a rupture condition. You can define theremoval strain state using an inelastic strain (plasticity and creep), or using the total mechanical strain(elastic+inelastic mechanical strain).

The new ELAR case control command is available to select the element add/removal set. The ELARcommand can be defined globally (above the subcases), or in a static or dynamic subcase. SeeSubcase rules.

You define the add and removal of elements with the new ELAR and ELAR2 bulk entries. The ELARentry selects the GRPID bulk entry which is useful when you have a large number of elements toadd or remove. The ELAR2 entry lists elements directly for add or removal, so it is useful when youhave fewer elements. The ELARADD bulk entry is also available to combine multiple ELAR andELAR2 bulk entries into a single add/removal set.

ELAR and ELAR2 bulk entry summary

• The TYPE field defines the addition/removal criteria type. See the ELAR and ELAR2 entriesfor the format of each type.

TYPE = TIME: Element Addition/Removal based on time.

TYPE = RINELE: Element removal (rupture) based on the effective inelastic strain.

TYPE = RMECHE: Element removal (rupture) based on the effective mechanical strain.

• For TYPE=TIME, AC and RC define the addition time and removal time, respectively.

If the time defined for AC or RC is in the time range for a subcase, but not precisely a solutiontime defined by the TSTEP1 bulk entry, a new solution time will be created for the elementaddition or removal. You can optionally request output for all time steps, including time stepscreated for the element addition or removal, by defining NOUT=ALL on the TSTEP1 bulk entry.

If you define the ELAR case control command above the subcase level (global definition), youmust define AC or RC in the time range of one of the subcases. Otherwise, the software willnot add or remove the associated elements.

If you define the ELAR case control command in a subcase, it is recommended that you defineAC or RC in the time range for the subcase. Although, if AC or RC fall outside the range ofthe subcase time, the additions and removal will occur at the end time for the subcase. Anexception is if both AC and RC are defined for the same element in the same subcase. In this




case, the addition will occur at the end time for the subcase, the removal will be ignored, anda warning will occur.

• The addition delta time (AD field) and removal delta time (RD field) are time intervals used to addor remove the element mass and stiffness. The delta time options slow the transition of adding orremoving elements which helps to prevent convergence problems.

If the delta time is greater than the time remaining in the subcase, the software adjusts it to equalthe remaining time in the subcase.

If you define -1 in the AD or RD fields, the software will ramp the element addition or removalover the remaining subcase time.

When the AD and RD fields are undefined, an element addition or removal occurs instantly.

• For TYPE = RINELE, you enter the effective inelastic strain in the RC field in which the elementwill be removed. The strain value you define includes strain contributions from both plasticityand creep materials if both are defined on an element. Plastic and creep strain output can berequested with the PLSTRN and CRSTRN case control commands, respectively.

• For TYPE = RMECHE, you enter the effective mechanical strain in the RC field in which theelement will be removed. The strain value you define includes the elastic and inelastic strains.Elastic strain output can be requested with the ELSTRN case control command. For example, ifan element has both plastic and creep strain, the effective mechanical strain is the sum of theeffective elastic, effective plastic, and effective creep strains. If the material is a user definedmaterial (UMAT), the effective mechanical strain is the equivalent mechanical strain computedfrom mechanical strain components.

Additional information

• For TYPE=TIME, the following elements are supported:

The 3D solid elements CTETRA, CHEXA, CPENTA, CPYRAM with properties defined with thePSOLID or PCOMPS entry.

The axisymmetric elements CQUADX4, CQUADX8, CTRAX3, CTRAX6.

The plane strain elements CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8 including when definedas a generalized plane strain element.

The plane stress elements CPLSTS3, CPLSTS4, CPLSTS6, CPLSTS8.

The chocking elements CCHOCK3, CCHOCK4, CCHOCK6, CCHOCK8.

The bar and beam elements CBAR, CBEAM.

The shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, CTRIA3 with propertiesdefined with the PSHELL, PCOMP, or PCOMPG entries.

The spring elements CELAS1, CELAS2, CBUSH1D, CBUSH.

• For TYPE=RINELE, the following elements are supported:

The 3D solid elements CTETRA, CHEXA, CPENTA, CPYRAM defined with the PSOLID entry.








The shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, CTRIA3 with propertiesdefined with the PSHELL entry.

• For TYPE=RMECHE, the following elements are supported:

The 3D solid elements CTETRA, CHEXA, CPENTA, CPYRAM defined with the PSOLID orPCOMPS entry.





The shell elements CTRIAR, CQUADR, CTRIA6, CQUAD8, CQUAD4, CTRIA3 with propertiesdefined with the PSHELL, PCOMP, or PCOMPG entries.

• The elements CMASSi, CONMi, and cohesive elements are not supported for adding andremoving.

• The software automatically adds or removes from the solution any loads, boundary conditions, orunconnected grid points that are referenced by elements that are added or removed.

Exceptions:

- Contact and glue conditions are not supported on elements being added or removed.

- MPCs or rigid elements cannot be defined on the same grid points of elements being added orremoved.

- A distributed load defined with the FORCDST bulk entry is not supported with the elementaddition or removal.

• When you reference elements by an element addition/removal set to be added at a solution timepoint, the software considers those elements as inactive at the start of the solution. The softwareconsiders all other elements as active at the start of the solution.

Relative to a sequence of sequentially dependent (SD) subcases, elements can only be addedone time, and elements can only be removed one time. As a result, elements that are removedcannot be readded.

For example, you can remove an element that was active at the start of the solution, or you canremove an element that became active at a solution time point during the solution.

• You can define only one removal criteria for an element. For example, for the same element, youcannot define both a removal based on a strain state and a removal based on time.

• Subcase rules




o Element addition and removal can occur in a statics or dynamics subcase. The staticssubcase in which nonlinear buckling is requested with the NLARCL=ID case controlcommand is not supported.

Element addition and removal can not occur in a preload, modal, cyclic, or Fourier subcase.Although, the add/remove status is retained for these subcases if they are sequentiallydependent. For example, if an element is added in a static subcase and the next subcaseis a sequentially dependent modal subcase, the added element will be active in the modalsubcase.

o You can define a global definition of an element add/remove set by placing the ELAR casecontrol command above the subcase level. The global definition is the most flexible and leastrestrictive option. You can define element addition or removal for times, or for strain state,across all static and dynamic subcases with a global definition.

o You can define a specific subcase definition of an element add/remove set by includingthe ELAR case control command in a static or dynamic subcase. For element addition,the specific subcase definition is restricted to only the first static or dynamic subcase in asequence of sequentially dependent subcases. For element removal, you can include theELAR case control command in any static or dynamic subcase.

o If you include a non-sequentially dependent (NSD) subcase, the state of the solution is resetto the initial state, including the element add and remove status and the solution time, whichis reset back to 0.0. When you define an NSD subcase, you are restarting the solution.




ELAR

Element Add/Remove Set Selection

Selects an element add/remove set (SOL 401)FORMAT:

ELAR=nEXAMPLES:

ELAR=5

DESCRIBERS:

Describer Meaning

n Element add/remove set identification of an ELAR, ELAR2, orELARADD bulk entry. (Integer>0)

REMARKS:1. The ELAR case control command can be specified above the subcase level

(global) or in a static or dynamic subcase.




ELAROUT

Element Add/Remove Status Output

Element Add/Remove status output (SOL 401)FORMAT:

EXAMPLES:ELAROUT=YES

DESCRIBERS:

Describer Meaning

PRINT Output is written to the .f06 file and the .op2 file. (Default)

PUNCH Output is written to the .pch file and the .op2 file.

PLOT Output is written to the .op2 file.

YES Request output.

NO No output requested. (Default)

REMARKS:1. The ELAROUT command outputs a status of 0 for elements that have not been

added yet, and a status of 1 for elements that are removed. No status is writtenfor elements that are active.

2. To request output to only the .op2 file, include only PLOT without PRINT orPUNCH.




ELAR

Element Add/Remove Set Definition (SOL 401)

Defines element addition and removal for elements selected in a group.GENERALFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR ESID TYPE AC AD RC RD

GRPID

TYPE=TIMEFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR ESID TIME AC AD RC RD

GRPID

TYPE=RINELEFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR ESID RINELE RC RD

GRPID

TYPE=RMECHEFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR ESID RMECHE RC RD

GRPID

EXAMPLES:

ELAR 100 TIME 0.0 0.1 0.6 0.1

101

ELAR 100 RINELE 0.03 -1

101

ELAR 100 RMECHE 0.03 0.0

101

FIELDS:

Field Contents

ESID Element add/remove set identification number. (Integer > 0)




Field Contents

TYPE Addition/Removal criteria type. (Character)


TYPE = RINELE: Element removal based on inelastic strain.

TYPE = RMECHE: Element removal based on mechanical strain.

GRPID Identification of a GROUP bulk entry, which selects the elements foradding or removing. The referenced GROUP bulk entry must haveTYPEi = ELEM. (Integer > 0)

Fields for TYPE=TIME:

AC Addition time. (Real ≥ 0.0 or blank)

AD Addition delta time. (Integer = -1 or Real ≥ 0.0; Default = 0.0)

RC Removal time. (Real > AC+AD or blank)

RD Removal delta time. (Integer = -1 or Real ≥ 0.0; Default = 0.0)

Fields for TYPE=RINELE or RMECHE:

AC Ignored.

AD Ignored.

RC Removal strain (Effective strain). (Real > 0.0 or blank)

RD Removal delta time. (Integer = -1 or Real ≥ 0.0; Default = 0.0)

REMARKS:1. ESID is selected either by the ELAR case control command or the ELARADD

bulk entry.

2. For TYPE=TIME, AC and RC define the addition time and removal time,respectively.

If the time defined for AC or RC is in the time range for a subcase, but not preciselya solution time defined by the TSTEP1 bulk entry, a new solution time will becreated for the element addition or removal.

If you define the ELAR case control command above the subcase level (globaldefinition), you must define AC or RC in the time range of one of the subcases.Otherwise, the software will not add or remove the associated elements.

If you define the ELAR case control command in a subcase, it is recommendedthat you define AC or RC in the time range for the subcase. Although, if AC or RCfall outside the range of the subcase time, the additions and removal will occur atthe end time for the subcase. An exception is if both AC and RC are defined forthe same element in the same subcase. In this case, the addition will occur at theend time for the subcase, the removal will be ignored, and a warning will occur.




3. The addition delta time (AD field) and removal delta time (RD field) are timeintervals used to add or remove the element mass and stiffness. The delta timeoptions slow the transition of adding or removing elements which helps to preventconvergence problems.

If the delta time is greater than the time remaining in the subcase, it will beadjusted to equal the remaining time in the subcase.

If you define -1 in the AD or RD fields, the software will ramp the element additionor removal over the remaining subcase time.

When the AD and RD fields are undefined, an element addition or removal occursinstantly.

4. For TYPE = RINELE, you enter the effective inelastic strain in the RC field inwhich the element will be removed. The strain value you define includes straincontributions from both plasticity and creep materials if both are defined on anelement. Plastic and creep strain output can be requested with the PLSTRN andCRSTRN case control commands, respectively.

5. For TYPE = RMECHE, you enter the effective mechanical strain in the RC field inwhich the element will be removed. The strain value you define includes the elasticand inelastic strains. Elastic strain output can be requested with the ELSTRNcase control command. For example, if an element has both plastic and creepstrain, the effective mechanical strain would be the sum of the effective elastic,effective plastic, and effective creep strains. If the material is a user definedmaterial (UMAT), the effective mechanical strain is the equivalent mechanicalstrain computed from mechanical strain components.




ELAR2

Alternative Element Add/Remove Set Definition (SOL 401)

Defines element addition and removal for the elements listed.GENERALFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR2 ESID TYPE

EID1 AC1 AD1 RC1 RD1


… … … … …

EIDi ACi ADi RCi RDi

TYPE=TIMEFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR2 ESID TIME



… … … … …

EIDi ACi ADi RCi RDi

TYPE=RINELEFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR2 ESID RINELE

EID1 RC1 RD1

EID2 RC2 RD2

… … …

EIDi RCi RDi

TYPE=RMECHEFORMAT:

1 2 3 4 5 6 7 8 9 10

ELAR2 ESID RMECHE

EID1 RC1 RD1

EID2 RC2 RD2

… … …

EIDi RCi RDi

EXAMPLES:

ELAR2 100 TIME

101 0.0 0.1 0.6 0.1




102 0.0 0.1 0.5 0.1

103 0.0 0.1 0.4 0.1

ELAR2 100 RINELE

101 0.03 -1

102 0.03 0.0

103 0.03 -1

ELAR2 100 RMECHE

101 0.03 -1

102 0.03 0.0

103 0.03 -1

FIELDS:

Field Contents


TYPE Addition/Removal criteria type. (Character)


TYPE = RINELE: Element removal based on inelastic strain.

TYPE = RMECHE: Element removal based on mechanical strain.

EIDi Element ID. (Integer>0)

Fields for TYPE=TIME:

AC Addition time. (Real ≥ 0.0 or blank)

AD Addition delta time. (Integer = -1 or Real ≥ 0.0; Default=0.0)

RC Removal time. (Real > AC+AD or blank)

RD Removal delta time. (Integer = -1 or Real≥ 0.0; Default=0.0)

Fields for TYPE=RINELE or RMECHE:

AC Ignored.

AD Ignored.

RC Removal strain (Effective strain). (Real > 0.0 or blank)

RD Removal delta time. (Integer = -1 or Real ≥0.0; Default=0.0)

REMARKS:1. ESID is selected either by the ELAR case control command or the ELARADD

bulk entry.




2. For TYPE=TIME, AC and RC define the addition time and removal time,respectively.

If the time defined for AC or RC is in the time range for a subcase, but not preciselya solution time defined by the TSTEP1 bulk entry, a new solution time will becreated for the element addition or removal.

If you define the ELAR case control command above the subcase level (globaldefinition), you must define AC or RC in the time range of one of the subcases.Otherwise, the software will not add or remove the associated elements.

If you define the ELAR case control command in a subcase, it is recommendedthat you define AC or RC in the time range for the subcase. Although, if AC or RCfall outside the range of the subcase time, the additions and removal will occur atthe end time for the subcase. An exception is if both AC and RC are defined forthe same element in the same subcase. In this case, the addition will occur at theend time for the subcase, the removal will be ignored, and a warning will occur.

3. The addition delta time (AD field) and removal delta time (RD field) are timeintervals used to add or remove the element mass and stiffness. The delta timeoptions slow the transition of adding or removing elements which helps to preventconvergence problems.

If the delta time is greater than the time remaining in the subcase, it will beadjusted to equal the remaining time in the subcase.

If you define -1 in the AD or RD fields, the software will ramp the element additionor removal over the remaining subcase time.

When the AD and RD fields are undefined, an element addition or removal occursinstantly.

4. For TYPE = RINELE, you enter the effective inelastic strain in the RC field inwhich the element will be removed. The strain value you define includes straincontributions from both plasticity and creep materials if both are defined on anelement. Plastic and creep strain output can be requested with the PLSTRN andCRSTRN case control commands, respectively.

5. For TYPE = RMECHE, you enter the effective mechanical strain in the RC field inwhich the element will be removed. The strain value you define includes the elasticand inelastic strains. Elastic strain output can be requested with the ELSTRNcase control command. For example, if an element has both plastic and creepstrain, the effective mechanical strain would be the sum of the effective elastic,effective plastic, and effective creep strains. If the material is a user definedmaterial (UMAT), the effective mechanical strain is the equivalent mechanicalstrain computed from mechanical strain components.




ELARADD

Defines a union of element add/remove sets (SOL 401)

Defines an element add/remove set as a union of ELAR and ELAR2 bulk entries.FORMAT:

1 2 3 4 5 6 7 8 9 10

ELARADD ESID S1 S2 S3 ... Si

EXAMPLE:

1 2 3 4 5 6 7 8 9 10

ELARADD 101 1 2 3 4

FIELDS:

Field Contents


Si Identification numbers of element add/remove sets defined with ELAR/ ELAR2 entries. (Integer > 0)

REMARKS:1. ESID can be selected by the ELAR case control command.

Chocking element improvementChocking elements are a special type of axisymmetric element that are used to model regions thatcan carry a compressive hoop stress, but cannot carry a tensile hoop stress. You use chockingelements to model regions where the axisymmetric geometry is violated by regularly-spaced featureslike holes or keyways.

Chocking elements can switch between an axisymmetric stiffness when chocked and a plane stressstiffness when unchocked. The software uses an expression to compute the gap status at eachGauss point to determine if a location is chocked or unchocked.

See Chocking elements (SOL 401) in the Multi-Step Nonlinear User’s Guide for the details of thiscomputation.

Previously, when large displacements were not enabled (LGDISP = -1), a solution would occur for thefirst time step to determine the gap status at each Gauss point. The software then used this chockedor unchocked status to recompute the stiffness. The resulting stiffness was used for the rest of thesolution, and the gap status was not reevaluated.

Now when large displacements are not enabled, you can use the new CHOCK parameter on theNLCNTLG bulk entry to control the frequency of gap status updates.

When CHOCK=YES (default), the software computes an updated gap status at the end of every timestep. The software uses this updated chocked or unchocked status to recompute the stiffness. Theresulting stiffness can change from one time step to the next based on the changing gap status.




When CHOCK=NO, the software behavior is the same as the previous release. Specifically, asolution occurs for the first time step to determine the gap status at each Gauss point. The softwareuses this chocked or unchocked status to recompute the stiffness. The resulting stiffness is then usedfor the rest of the solution, and the gap status is not reevaluated.

The CHOCK=YES option allows you to update the stiffness based on the chocking status, but withoutthe computation expense of running a large displacement analysis. This option is only appropriatewhen the changing geometry and stiffness updates which occur with LGDISP=1 are not significant.

PARAM,LGDISP,-1 is the default value for the LGDISP parameter.

When large displacements are enabled, the software behavior in regard to chocking elements hasnot changed. Specifically, the software computes an updated gap status at the end of each timestep. The resulting stiffness can then change from one time step to the next based on the changinggap status and the deformed state of the model.

Load control optionThe new LOADOFF parameter is available on the NLCNTL bulk entry to turn ON or OFF categoriesof mechanical loads. The NLCNTL entry can be defined in the global subcase level and in individualsubcases.

The LOADOFF options are as follows.

LOADOFF value ResultLOADOFF=NONE(Default) No loads are turned off.

LOADOFF=BODY Turns off body loads defined with the GRAV, RFORCE, RFORCE1,ACCEL, and ACCEL1 bulk entries.

LOADOFF=BOUNDRYTurns off boundary loads defined with the PLOAD, PLOAD1, PLOAD2,PLOAD4, PLOADE1, PLOADX1, FORCDST, FORCE, FORCE1,FORCE2, MOMENT, MOMENT1, MOMENT2, and SLOAD bulk entrires.

LOADOFF=BOTH

Turns off both the BODY and BOUNDRY loads listed above.

When LOADOFF=BOTH is defined, the loads which remain on includetemperature loads, initial stress/strain, strains computed from a boltpreload subcase, enforced displacements, and loads as a result ofcontact conditions.

Note

When running SOL 401 in a Simcenter thermal-structural multiphysics analysis, somemechanical loads such as RFORCE1 are used by both the structural and thermal solutions.It's important to understand that the LOADOFF parameter is only turning loads on or off forthe Simcenter Nastran structural solution, and not the thermal solution. In addition, thethermal solution can compute pressure loads which are then applied in the structuralsolution. These pressure loads are applied using the PLOADi entries, and as a result, theywill be turned off from the structural solution when LOADOFF=BOUNDRY is defined.




Bolt preload improvements in SOL 401In the previous release, the SOL 401 bolt preload capability supported bolts modeled with 3D solidelements and 2D plane stress elements.

Now you can also model 1D bolts with CBAR and CBEAM elements. The 1D bolt definition for SOL401 is consistent with the definition for linear solutions.

• You use the ETYPE=1 option on the BOLT bulk entry when defining the 1D bolt.

• If you model the bolt with multiple CBAR and CBEAM elements, you list only one of the elementsin the EID1 field on the BOLT entry.

• The same case control commands and bulk entries supported by the 3D and 2D bolts are alsosuppported for the 1D bolts. This includes the BOLTLD and BOLTRESULTS case controlcommands and the BOLT, BOLTLD, BOLTFRC and BOLTSEQ bulk entries.

• You can use the LOAD and DISP in the TYPE field on the BOLTFRC bulk entry to define apreload as a force or a displacement, respectively.

• Sequential loading of 1D bolts is supported.

• You can define the BOLTRESULTS case control command to request the output of bolt axialforce, shear forces, bending moments and strains for the 1D bolts.

• SOL 401 requires that all of the BOLT bulk entries have the same ETYPE. Specifically, they mustall be ETYPE=1, ETYPE=2, or ETYPE=3. A fatal error will occur if BOLT entries with differentETYPES are referenced.

New transverse shear stress formulation for composite shellelementsIn SOL 401, you can now use composite shell elements whose transverse shear stress formulationproduces results that are independent of the choice of material coordinate system. In SOL 401,composite shell elements are CQUADR, CQUAD4, CQUAD8, CTRIAR, CTRIA3, and CTRIA6elements that reference PCOMP, PCOMPG, or PCOMPG1 property entries.

Note

In SOL 401, the software automatically converts CQUAD4 and CTRIA3 elements toequivalent CQUADR and CTRIAR elements, respectively.

The new formulation is independent of the material coordinate system because it accounts for allthree moments, Mx, My, and Mxy, in Figure 3. The legacy formulation ignores Mxy. Thus, dependingon the stress state and the choice of material coordinate system, this omission can lead to results thatare less accurate than those obtained from the new formulation.

The disadvantage of the new formulation is that it requires additional computational effort.

The legacy formulation remains the default formulation. To use the new formulation, specifySYSTEM(715) = 1.




Figure 7-3. Moments acting on a laminate that lies in the XY-plane

Support for non-structural mass in SOL 401You can now use NSM, NSM1, NSML, and NSML1 bulk entries to specify non-structural mass inelements that reference PSHELL, PCOMPG1, and PPLANE bulk entries in SOL 401.

For more information, see Support for non-structural mass.

Support for PCOMP and PCOMPG in SOL 401PCOMP and PCOMPG bulk entries are now supported in SOL 401. This enhancement improvesbackward compatibility so that you can now more easily adapt laminate models that were created fornon-SOL 401 solution sequences to SOL 401.

In a SOL 401 solve, when the software encounters a PCOMP or PCOMPG bulk entry in the input file,it internally converts it into a PCOMPG1 bulk entry. Because the PCOMPG1 bulk entry does not havea LAM field, the software ignores the LAM field specification on the PCOMP or PCOMPG bulk entrywhen it performs the conversion. This can result in a loss of laminate definition if the LAM field on thePCOMP or PCOMPG bulk entry that the software is converting is not blank.




PCOMP

Layered Composite Element Property

Defines the properties of an n-ply composite material laminate.FORMAT:

1 2 3 4 5 6 7 8 9 10PCOMP PID Z0 NSM SB FT TREF GE LAM

MID1 T1 THETA1 SOUT1 MID2 T2 THETA2 SOUT2

MID3 T3 THETA3 SOUT3 -etc.-

EXAMPLE:

PCOMP 181 -0.224 7.45 10000.0 HOFF

171 0.056 0.0 YES 45.0

-45.0 90.0

FIELDS:

Field Contents

PID Property identification number. (0 < Integer < 10000000)

Z0 Distance from the reference plane to the bottom surface. See Remark14. (Real; Default = -0.5 times the element thickness.)

NSM Nonstructural mass per unit area. (Real)

SB Allowable shear stress of the bonding material (allowable interlaminarshear stress). Required if FT is specified. (Real > 0.0) See Remarks12 and 21.

FT Failure theory. The following theories are allowed (Character or blank. Ifblank, then no failure calculation will be performed):

“HILL” for the Hill theory.

“HOFF” for the Hoffman theory.

“TSAI” for the Tsai-Wu theory.

“STRN” for the Maximum Strain theory.

See the Laminates chapter in the Simcenter Nastran User's Guide for adetailed explanation of each theory.

TREF Reference temperature. See Remark 5. (Real; Default = 0.0)

GE Structural damping coefficient (dimensionless). See Remark 6. (Real;Default = 0.0)




Field Contents

LAM Laminate Options. (Character or blank, Default = blank). See Remarks 4and 16.

“Blank” All plies must be specified and all stiffness terms aredeveloped.

“SYM” Only plies on one side of the laminate centerline arespecified. The plies are numbered starting with 1 for thebottom ply. If the laminate contains an odd number of plies,then model the center ply as half the thickness of the actualcenter ply.

“MEM” All plies must be specified, but only membrane terms (MID1on the derived PSHELL entry) are computed.

“BEND” All plies must be specified, but only bending terms (MID2 onthe derived PSHELL entry) are computed.

“SMEAR” All plies must be specified, stacking sequence is ignored,MID1=MID2 on the derived PSHELL entry and MID3, MID4and TS/T and 12I/T**3 terms are set to zero.

“SMCORE” Face plies on one side of the laminate and the core arespecified to define a laminate that is symmetric about themidplane of the core. The core is specified last. Whencalculating face sheet stiffness, stacking sequence of theface sheets is ignored.

MIDi Material ID of the various plies. The plies are identified by seriallynumbering them from 1 at the bottom layer. The MIDs can refer to MAT1,MAT2, MAT8, MATSMA (SOL 601 only) or MATVE (SOL 601 only) bulkentries. See Remark 2 and SOL 601 Remark 4. (0 < Integer < 99999999or blank, except MID1 must be specified.)

Ti Thicknesses of the various plies. See Remark 2. (Real or blank, exceptT1 must be specified.)

THETAi Orientation angle of the longitudinal direction of each ply with the materialaxis of the element. (If the material angle on the element connectionentry is 0.0, the material axis and side 1-2 of the element coincide.) Theplies are to be numbered serially starting with 1 at the bottom layer. Thebottom layer is defined as the surface with the largest -Z value in theelement coordinate system. (Real; Default = 0.0)

SOUTi Controls individual ply stress and strain print or punch output. SeeRemarks 7 and 8. (Character: “YES” or “NO”; Default = “NO”)

REMARKS:1. PID must be unique with respect to all PCOMP, PCOMPG, and PSHELL entries.




2. The default for MIDi+1, ..., MIDn is the last defined MIDi. In the example above,MID(PLY1) is the default for MID(PLY2), MID(PLY3), and MID(PLY4). The samelogic applies to Ti.

3. Composite shell elements do not support nonlinear elastic materials defined withthe MATS1 bulk entry.

4. At least one of the four values (MIDi, Ti, THETAi, SOUTi) must be present for a plyto exist. The minimum number of plies is one.

5. A temperature-dependent material defined with the combined MATi and MATTientries can be referenced for a ply material (MIDi field on the PCOMP entry).For linear solutions, when computing the equivalent PSHELL and MAT2 entriesfrom the PCOMP definition, the software uses TREF defined on the PCOMPentry to evaluate any temperature-dependent material properties for the plies.TREF defaults to 0.0 if undefined. The TEMPERATURE(INIT) case controlcommand is not used in this phase of the solution, although it must be defined.Otherwise, the software will ignore the temperature-dependent material propertiesand use the properties on the referenced MATi entry. After the software createsthe equivalent PSHELL and MAT2 entries, if a thermal load was defined withthe TEMPERATURE(LOAD) case control command, the software will use theTEMPERATURE(INIT) command to compute thermal strains as described in theremarks on the TEMPERATURE case control command.

By default, SOL 106 behaves as described above. Although, if PARAM,COMPMATT, YES is defined, SOL 106 will use the temperatures selected with theTEMPERATURE(LOAD) command to evaluate temperature-dependent materialproperties for the plies when computing the equivalent PSHELL and MAT2 entries.A unique TEMPERATURE(LOAD) command in each subcase will result in therecomputing of the equivalent PSHELL and MAT2 entries. As described abovefor the linear solutions, the TEMPERATURE(INIT) case control command is alsorequired in SOL 106 in order for the software to use the temperature-dependentmaterial properties when computing the equivalent PSHELL and MAT2 entries.

6. GE given on the PCOMP entry will be used for the element and the valuessupplied on material entries for individual plies are ignored. You are responsiblefor supplying the equivalent damping value on the PCOMP entry. GE is ignored ina transient analysis if PARAM,W4 is not specified. See the parameter W4.

7. The parameter NOCOMPS determines whether stress and/or strain recovery is atthe composite ply layers (default), on the equivalent PSHELL, or both. See theparameter NOCOMPS. The STRESS and/or STRAIN case control commands arerequired for any of these recovery options. When ply results are requested, stressand/or strain are computed at the middle of each ply. To print the ply stress and/orstrain results, the case control command request must include the “PRINT” option(default). To punch these results, the case control command request must includethe “PUNCH” option. SOUTi=YES should then be defined on any ply definitions inwhich you would like print or punch output. The SOUTi entry is not used in thecomputing or printing of failure indices. See Remark 9.




8. Stress and strain output for individual plies are available in all superelementstatic and normal modes analysis and requested by the STRESS and STRAINcase control commands.

9. To compute STRESS failure index, the following must be present:

a. STRESS case control command.

b. The parameter NOCOMPS set to 1 (default) or 0.

c. SB and FT (= to HILL, HOFF or TSAI) on the PCOMP bulk entry.

d. Stress allowables Xt, Xc, Yt, Yc, and S on all referenced MAT8 bulk entries.

e. Stress allowables ST, SC, and SS on all referenced MAT1 bulk entries.

To compute STRAIN failure index, the following must be present:



c. SB and FT (= STRN) on the PCOMP bulk entry.

d. Strain allowables Xt, Xc, Yt, Yc, S, and STRN=1.0 on all referenced MAT8bulk entries.

By default, failure index output prints in the f06 file even when using the PLOT orPUNCH describers on the STRESS and STRAIN case control commands. Theparameter entry PARAM,NOFISR,1 can be used to turn off the printing of thefailure index output. See the parameter NOFISR.

10. To output strength ratio, the failure index output conditions listed in Remark 9must exist, and the parameter SRCOMPS must equal “YES”. See the parameterSRCOMPS.

11. Stress resultant output can be requested with the FORCE case control command.

12. The failure index of the bonding material is calculated by:FIbonding = (max(τ1z, τ2z)/ allowable bonding stress).The allowable bonding stress is defined on the SB field. The strength ratio for thebonding material is:SRbonding = (1 / FIbonding).

13. The software automatically creates equivalent PSHELL and MATi entries from aPCOMP definition. You can optionally include a sorted echo request to print thederived PSHELL and MATi entries in User Information Message 4379, or to thepunch file. The parameter NOCOMPS controls if stress and strain are computedfor the composite elements, the equivalent homogeneous element, or both. Seethe parameter NOCOMPS. The software designates the equivalent homogeneouselements with a MID1 or MID2 ID greater than or equal to 108 on the PSHELLentry. Homogenous stresses are based upon a smeared representation of the




laminate’s properties and in general will be significantly different than the moreaccurate lamina stresses available from PCOMP-based elements.

14. If the value specified for Z0 is not equal to -0.5 times the thickness of the elementand PARAM,NOCOMPS,-1 is specified, then the homogeneous element stressesare incorrect, while lamina stresses and element forces and strains are correct.For correct homogeneous stresses, use ZOFFS on the corresponding connectionentry.

15. An unsymmetrical layup or the use of Z0 to specify an unsymmetrical layup, is notrecommended in buckling analysis or the calculation of differential stiffness. Also,Z0 should not be used to specify an unsymmetrical layup.

16. The SYM option for the LAM option computes the complete stiffness propertieswhile specifying half the plies. The MEM, BEND, SMEAR and SMCORE optionsprovide the following special purpose stiffness calculations: MEM option onlyconsiders membrane effects, BEND option only considers bending effects,SMEAR ignores stacking sequence and is intended for cases where the sequenceis not yet known, SMCORE allows simplified modeling of a sandwich panel withequal face sheets and a central core.

17. Element output for the SMEAR and SMCORE options are produced using thePARAM NOCOMPS -1 methodology that suppresses ply stress/strain results andprints results for the equivalent homogeneous element.

18. When the PCOMP or PCOMPG bulk entries are included in a distributed parallelmethod, the gpart keyword used for selecting the partitioning method must begpart=1.

19. PCOMP is supported in all solutions except SOL 153 or 159 heat transfer analysis,and 701.

20. For elements referencing a PCOMP/PCOMPG, stress and strain output for theindividual lamina is supported in solutions 101, 103, 105, 106, 108, 109, 111, 112,114, 129, 144, 200, 401, 402 and 601. For SOLs 106 and 129, individual laminastress and strain are only output when a linear analysis is run (LGDISP = -1). Inother solutions (including 106 and 129), stress and strain can only be recoveredfor the equivalent PSHELL that the software creates for the laminate.

21. Interlaminar failure is computed using the out-of-plane normal and the shearstresses. For the solid elements, all of the interlaminar stress components existwhile only the shear stresses exist for the shell elements (due to the plane stresshypothesis in shell theories). For this reason, only the SB field is available on thePCOMP, PCOMPG, and PCOMPG1 bulk entries, but both the SB and NB fieldsare available on the PCOMPS entry.

REMARKSRELATED TO

SOL 401:1. LAM is ignored.




2. PID must be unique with respect to all PCOMP, PCOMPG, PCOMPG1, andPSHELL bulk entries.

3. The software automatically creates an equivalent PCOMPG1 bulk entry for eachPCOMP bulk entry. Thus, all the behaviors are aligned with the PCOMPG1 bulkentry. For example, only ply stress and strain results are computed for stress andstrain output requests.

REMARKSRELATED TO

SOL 402:1. GE and SOUTi are ignored.

2. TREF is ignored. Instead, the TREF of the material bulk entry of each ply is takeninto account.

3. Z0 is added to the offset introduced on the element bulk entry (ZOFFS). If elementforces are required, bending moments are given with respect to the updatedneutral plane.

4. LAM must be equal to SYM in SOL 402. Other choices for LAM will lead to an error.

REMARKSRELATED TO

SOL 601:1. Z0, NSM, SB, FT, TREF, GE, LAM and SOUTi are ignored.

2. When the STRESS and/or STRAIN case control commands are defined, resultsat the composite ply layers are computed. Stress and strain components arecomputed at the center of each ply. Inter-laminar results, failure indices, andstrength ratios are not computed. Stress resultant output is not supported.

3. Large strain formulation is not available for multi-layered shell elements.

4. Elasto-plastic material model is supported, but not nonlinear elastic materialmodel. That is, a MATS1 entry with TYPE=PLASTIC is supported, but notTYPE=NLELAST.




PCOMPG

Layered Composite Element Property with global ply IDs

Defines the properties of an n-ply composite material laminate that includes global plyIDs.

FORMAT:

1 2 3 4 5 6 7 8 9 10

PCOMPG PID Z0 NSM SB FT TREF GE LAM

GPLYIDi MIDi Ti THETAi SOUTi

EXAMPLE:

PCOMPG 73 –2.E-4 0.0 8.E+7 TSAI

101 1 1.E-4 0. YES

102 1.E-4 0. YES

103 1.E-4 0. YES

104 1.E-4 0. YES

FIELDS:

Field Contents

PID Property identification number. (0 < Integer < 10000000)

Z0 Distance from the reference plane to the bottom surface. See Remark14. (Real; Default = -0.5 times the element thickness.)

NSM Nonstructural mass per unit area. (Real)

SB Allowable shear stress of the bonding material (allowable interlaminarshear stress). Required if FT is specified. (Real > 0.0) See Remarks12 and 21.

FT Failure theory. The following theories are allowed (Character or blank. Ifblank, no failure calculation will be performed):

“HILL” for the Hill theory

“HOFF” for the Hoffman theory

“TSAI” for the Tsai-Wu theory

“STRN” for the Maximum Strain theory

See the Laminates chapter in the Simcenter Nastran User's Guide for adetailed explanation of each theory.

TREF Reference temperature. See Remark 5. (Real; Default = 0.0)




Field Contents

GE Structural damping coefficient (dimensionless). See Remark 7. (Real;Default = 0.0)

LAM Laminate Options. (Character or blank, Default = blank). See Remark 16.

“Blank” All plies must be specified and all stiffness terms aredeveloped.

“MEM” All plies must be specified, but only membrane terms (MID1on the derived PSHELL entry) are computed.

“BEND” All plies must be specified, but only bending terms (MID2 onthe derived PSHELL entry) are computed.

“SMEAR” All plies must be specified, stacking sequence is ignored,MID1=MID2 on the derived PSHELL entry and MID3, MID4and TS/T and 12I/T**3 terms are set to zero.

“SMCORE” Face plies on one side of the laminate and the core arespecified to define a laminate that is symmetric about themidplane of the core. The core is specified last. Whencalculating face sheet stiffness, stacking sequence of theface sheets is ignored.

GPLYIDi Global ply IDs. See Remark 2. (Integer > 0)

MIDi Material ID of the various plies. The plies are identified by seriallynumbering them from 1 at the bottom layer. The MIDs must refer toMAT1, MAT2, MAT8, MAT11 (Sol 402 only), MATSMA (SOL 601 only)or MATVE (SOL 601 only) bulk entries. See Remark 4. (0 < Integer <99999999 or blank, except MID1 must be specified.)

Ti Thicknesses of the various plies. See Remark 4. (Real or blank, exceptT1 must be specified.)

THETAi Orientation angle of the longitudinal direction of each ply with the materialaxis of the element. (If the material angle on the element connectionentry is 0.0, the material axis and side 1-2 of the element coincide.) Theplies are to be numbered serially starting with the first listed at the bottomlayer. The bottom layer is defined as the surface with the largest -Z valuein the element coordinate system. (Real; Default = 0.0)

SOUTi Controls individual ply stress and strain print or punch output. SeeRemarks 8 and 9. (Character: “YES” or “NO”; Default = “NO”)

REMARKS:1. PID must be unique with respect to all PCOMP, PCOMPG, and PSHELL entries.

2. Each global ply identification number GPLYIDi in a single PCOMPG entry shouldbe unique.




The global ply identification numbers (GPLYIDi) are reused across differentPCOMPG bulk entires in order to post-process relative ply layers with commonGPLYIDi.

3. Composite shell elements do not support nonlinear elastic materials defined withthe MATS1 bulk entry.

4. The default for MIDi+1, ..., MIDn is the last defined MIDi. In the example above,MID(PLY1) is the default for MID(PLY2), MID(PLY3), and MID(PLY4). The samelogic applies to Ti.

5. A temperature dependent material defined with the combined MATi and MATTientries can be referenced for a ply material (MIDi field on the PCOMPG entry).For linear solutions, when computing the equivalent PSHELL and MAT2 entriesfrom the PCOMPG definition, the software uses TREF defined on the PCOMPGentry to evaluate any temperature dependent material properties for the plies.TREF defaults to 0.0 if undefined. The TEMPERATURE(INIT) case controlcommand is not used in this phase of the solution, although it must be defined,otherwise the software will ignore the temperature dependent material propertiesand use the properties on the referenced MATi entry. After the software createsthe equivalent PSHELL and MAT2 entries, if a thermal load was defined withthe TEMPERATURE(LOAD) case control command, the software will use theTEMPERATURE(INIT) command to compute thermal strains as described in theremarks on the TEMPERATURE case control command.

By default, SOL 106 behaves as described above. Although, if PARAM,COMPMATT, YES is defined, SOL 106 will use the temperatures selected with theTEMPERATURE(LOAD) command to evaluate temperature dependent materialproperties for the plies when computing the equivalent PSHELL and MAT2 entries.A unique TEMPERATURE(LOAD) command in each subcase will result in therecomputing of the equivalent PSHELL and MAT2 entries. As described abovefor the linear solutions, the TEMPERATURE(INIT) case control command is alsorequired in SOL 106 in order for the software to use the temperature dependentmaterial properties when computing the equivalent PSHELL and MAT2 entries.

6. At least one of the four values (MIDi, Ti, THETAi, SOUTi) must be present for a plyto exist. The minimum number of plies is one.

7. GE given on the PCOMPG entry will be used for the element and the valuessupplied on material entries for individual plies are ignored. You are responsiblefor supplying the equivalent damping value on the PCOMPG entry. GE is ignoredin a transient analysis if PARAM,W4 is not specified. See the parameter W4.

8. The parameter NOCOMPS determines if stress and/or strain recovery is at thecomposite ply layers (default), on the equivalent PSHELL, or both. See theparameter NOCOMPS. The STRESS and/or STRAIN case control commands arerequired for any of these recovery options. When ply results are requested, stressand/or strain are computed at the middle of each ply. To print the ply stress and/orstrain results, the case control command request must include the “PRINT” option(default). To punch these results, the case control command request must includethe “PUNCH” option. SOUTi=YES should then be defined on any ply definitions in




which you would like print or punch output. The SOUTi entry is not used in thecomputing or printing of failure indices. See Remark 10.

9. Stress and strain output for individual plies are available in all superelementstatic and normal modes analysis and requested by the STRESS and STRAINcase control commands.

10. To output STRESS failure index, the following must be present:



c. SB and FT (= to HILL, HOFF or TSAI) on the PCOMPG Bulk Data entry.

d. Stress allowables Xt, Xc, Yt, Yc, and S on all referenced MAT8 Bulk Dataentries.

e. Stress allowables ST, SC, and SS on all referenced MAT1 Bulk Data entries.

To output STRAIN failure index, the following must be present:



c. SB and FT (= STRN) on the PCOMPG Bulk Data entry.

d. Strain allowables Xt, Xc, Yt, Yc, S, and STRN=1.0 on all referenced MAT8Bulk Data entries.

By default, failure index output prints in the f06 file even when using the PLOT orPUNCH describers on the STRESS and STRAIN case control commands. Theparameter entry PARAM,NOFISR,1 can be used to turn off the printing of thefailure index output. See the parameter NOFISR.

11. To output strength ratio, the failure index output conditions listed in Remark 10must exist, and the parameter SRCOMPS must equal “YES”. See the parameterSRCOMPS.

12. The failure index of the bonding material is calculated by:FIbonding = (max(τ1z, τ2z)/ allowable bonding stress).The allowable bonding stress is defined on the SB field. The strength ratio for thebonding material is:SRbonding = (1 / FIbonding).

13. The software automatically creates equivalent PSHELL and MATi entries from aPCOMPG definition. You can optionally include a sorted echo request to print thederived PSHELL and MATi entries in User Information Message 4379, or to thepunch file. The parameter NOCOMPS controls if stress and strain are computedfor the composite elements, the equivalent homogeneous element, or both. Seethe parameter NOCOMPS. The software designates the equivalent homogeneouselements with a MID1 or MID2 ID greater than or equal to 108 on the PSHELL




entry. Homogenous stresses are based upon a smeared representation of thelaminate’s properties and in general will be significantly different than the moreaccurate lamina stresses available from PCOMP-based elements.

14. If the value specified for Z0 is not equal to -0.5 times the thickness of the elementand PARAM,NOCOMPS,-1 is specified, then the homogeneous element stressesare incorrect, while lamina stresses and element forces and strains are correct.For correct homogeneous stresses, use ZOFFS on the corresponding connectionentry.

15. An unsymmetrical layup or the use of Z0 to specify an unsymmetrical layup, is notrecommended in buckling analysis or the calculation of differential stiffness. Also,Z0 should not be used to specify an unsymmetrical layup.

16. The MEM, BEND, SMEAR and SMCORE options provide the following specialpurpose stiffness calculations: MEM option only considers membrane effects,BEND option only considers bending effects, SMEAR ignores stacking sequenceand is intended for cases where the sequence is not yet known, SMCORE allowssimplified modeling of a sandwich panel with equal face sheets and a central core.

17. Element output for the SMEAR and SMCORE options are produced using thePARAM NOCOMPS -1 methodology that suppresses ply stress/strain results andprints results for the equivalent homogeneous element.

18. When the PCOMP or PCOMPG bulk entries are included in a distributed parallelmethod (DMP), the gpart keyword used for selecting the partitioning methodmust be gpart=1.

19. PCOMPG is supported in all solutions except SOL 153 or 159 heat transferanalysis, 601 and 701.

20. For elements referencing a PCOMP/PCOMPG, stress and strain output for theindividual lamina is supported in solutions 101, 103, 105, 106, 108, 109, 111, 112,114, 129, 144, 200, 401, 402 and 601. For SOLs 106 and 129, individual laminastress and strain are only output when a linear analysis is run (LGDISP = -1). Inother solutions (including 106 and 129), stress and strain can only be recoveredfor the equivalent laminate. That is, output on the equivalent PSHELL created bythe software.

21. Interlaminar failure is computed using the out-of-plane normal and the shearstresses. For the solid elements, all of the interlaminar stress components existwhile only the shear stresses exist for the shell elements (due to the plane stresshypothesis in shell theories). For this reason, only the SB field is available on thePCOMP, PCOMPG, and PCOMPG1 bulk entries, but both the SB and NB fieldsare available on the PCOMPS entry.

REMARKSRELATED TO

SOL 401:1. LAM is ignored.




2. PID must be unique with respect to all PCOMP, PCOMPG, PCOMPG1, andPSHELL bulk entries.

3. The software automatically creates an equivalent PCOMPG1 bulk entry for eachPCOMPG bulk entry. Thus, all the behaviors are aligned with the PCOMPG1 bulkentry. For example, only ply stress and strain results are computed for stress andstrain output requests.

REMARKSRELATED TO

SOL 402:1. GE, LAM and SOUTi are ignored.

2. TREF is ignored. Instead, the TREF of the material bulk entry of each ply is takeninto account.

3. Z0 is added to the offset introduced on the element bulk entry (ZOFFS). If elementforces are required, bending moments are given with respect to the updatedneutral plane.

REMARKSRELATED TO

SOL 601:1. Z0, NSM, SB, FT, TREF, GE, LAM, and SOUTi are ignored.

2. When the STRESS and/or STRAIN case control commands are defined, resultsat the composite ply layers are computed. Stress and strain components arecomputed at the center of each ply. Inter-laminar results, failure indices, andstrength ratios are not computed. Stress resultant output is not supported.

3. Large strain formulation is not available for multi-layered shell elements.

4. Elasto-plastic material model is supported, but not the nonlinear elastic materialmodel. That is, a MATS1 entry with TYPE=PLASTIC is supported, but notTYPE=NLELAST.

Reformulated shell elementsWhen using SOLs 401 and 402, a heterosis formulation for the CQUAD8 element and a reformulatedCTRIA6 element are the default formulations.

You can use the new formulations for the CQUAD8 and CTRIA6 elements to model the followingmono-layer and laminate plane stress behaviors:

• Membrane stiffness (SOL 402 only)

• Membrane and bending stiffness (SOL 401 only)

• Membrane, bending, and transverse shear stiffness

• Membrane, bending, transverse shear, and coupled membrane-bending stiffness

The new formulations for the CQUAD8 and CTRIA6 elements do not support the following behaviors:




• Plane strain.

• Bending stiffness only.

• Bending and transverse shear stiffness only.

The new element formulations have several advantages:

• The new formulations allow for higher aspect ratio of length to thickness before shear lockingoccurs.

• For the CQUAD8 element, the heterosis formulation uses 8-noded serendipity shape functionsfor the translational DOF, and 9-noded Lagrange shape functions for the rotational DOF. Theenriched shape functions lead to better results although at some computational cost.

Because a ninth grid point is required for Lagrange shape functions and only eight actual gridpoints exist, the software creates internal DOF at the centroid of the element. The internal DOFfunctions as the ninth grid point for the element. After calculating the element matrices, thesoftware condenses the internal DOF prior to assembly into the global matrices.

• For the CQUAD8 and CTRIA6 elements, the new formulations use the K6ROT parameter tosuppress grid point singularities by adding stiffness to the out-of-plane rotational DOF.

For a listing of when you can use the K6ROT parameter to add stiffness to the out-of-planerotational DOF, see K6ROT.

• When viewed normal to the reference plane of the element, the X- and Y-axes of the materialcoordinate system are consistent across the element. In the element formulations that are usedin previous versions of the software, the X- and Y-axes of the material coordinate system varyacross the element.

CQUAD8 heterosis formulation

The heterosis formulation uses eight-noded serendipity shape functions for the translational DOF,and nine-noded Lagrange shape functions for the rotational DOF.

By default, four Gauss points (2 x 2 integration) are used to integrate the membrane and transverseshear stiffness, and nine Gauss points (3 x 3 integration) are used to integrate the bending andcoupled membrane-bending stiffness.

CTRIA6 reformulation

The heterosis formulation uses six-noded serendipity shape functions for the translational androtational DOF.

By default, three Gauss points are used to integrate the membrane, bending, transverse shear, andcoupled membrane-bending stiffness.

Out-of-plane rotational stiffness

When the software computes the element stiffness matrix for CQUAD8 and CTRIA6 shell elements, itadds rotational stiffness directly into the element stiffness matrix for the out-of-plane rotational DOF.The rotational stiffness that the software adds is given by the following equation:




where K6ROT is the value of the K6ROT parameter, and D44 and D55 are entries in the constitutiverelation of the shell element. For example, the constitutive relation for a shell element whosegeometry and material properties are symmetric about its midplane has the following form:

where:

Nx, Ny, Nxy In-plane forces

Mx, My, Mxy In-plane moments

εxo, εyo, γxyo Midplane strains

κx, κy, κxy Midplane curvatures

K6ROT

Default = 100.0

K6ROT may be used in the calculation of the stiffness for the out-of-plane rotational DOF forCQUAD4, CQUAD8, CTRIA3, and CTRIA6 elements. K6ROT is always ignored for CQUADR andCTRIAR elements.

Specifying a value between 1.0 and 100.0 for K6ROT is recommended. A large value for K6ROTmay be required in nonlinear analysis and eigenvalue analysis. K6ROT is forced to 0.0 for elementsthat have membrane stiffness only.

K6ROT is applicable in all solution sequences except SOLs 116, 601, and 701. In solution sequenceswhere it is applicable, depending on the element type, its usage is as follows:

• Linear solutions and SOLs 106 and 129

CQUAD4 and CTRIA3: K6ROT is used.

CQUAD8 and CTRIA6: K6ROT is ignored.

• SOLs 401 and 402

CQUAD4 and CTRIA3: K6ROT is ignored.

CQUAD8 and CTRIA6: K6ROT is used.



Chapter 8: Multi-step nonlinear kinematics solution 402

Multi-step nonlinear kinematics SOL 402Simcenter Nastran SOL 402 is a multi-step, structural solution that supports a combination ofsubcase types (static linear, static nonlinear, nonlinear dynamic, preload, modal, Fourier, buckling)and large rotation kinematics.

New features in Simcenter Nastran 2019.1 SOL 402 solutionSubcase analysis typeBoundary conditionsMechanical loadsSupport of kinematic jointsProperties supportMaterial supportGlue supportContact supportNonlinear parametersStress-strain measuresTime stepping strategyRestartSolver supportSupported outputInput summarySolution monitorMiscellaneous

Subcase analysis type

SOL 402 now allows the extraction of complex eigenvalues in an ANALYSIS=CEIG analysis.

A complex modes analysis can help to evaluate the stability of a model, typically for rotating oraeroelastic systems, by analyzing the real part of complex eigenvalues. For example, you can use acomplex modes analysis for a rotating system such as a shaft that is supported by bearings wherethe bearings are idealized by stiffness and damping coefficients.

You use the CMETHOD case control command to select the EIGC bulk entry set identifier to process.

The EIGC bulk entry defines all the data that are required for the complex eigenvalues extraction.



Constraints

SOL 402 now supports constraints defined with the SPC, SPCD, and MPC entries.

Mechanical loads

The LOAD bulk entry can be used to define a driver on kinematic joints.

Support of kinematic joints

You can use kinematic joints and flexible sliders.

Kinematic joints allow structural analysis of an assembly containing moving parts.

With flexible sliders, you drive the displacement of parts along a line of beams that models a track.

For more information, see Kinematic joints (SOL 402) in the Multi-Step Nonlinear User's Guide.

Properties support

SOL 402 adds support for the following properties:

• Beams elements with a cross-section of the TYPE="BAR", "BOX", "CHAN", "CHAN1", "I", "I1","L", "T", "TUBE", and "Z" (PBEAML or PBARL bulk entries) can be used with a nonlinear material(i.e., plastic or temperature-dependent). If a plastic material is used (MATS1 bulk entry withTYPE="PLASTIC"), the behavior is not limited to elastic-perfectly plastic.

The material behavior is calculated by numerical integration in the central section of the element.It is supposed to be constant for the whole element.

• Beams offsets are now taken into account.

• A rod can now reference a nonlinear MATS1 material (MID parameter of the PROD bulk entry).

• For CBAR, CBEAM, and CROD elements, you can use the PARAM,SNORM parameter to definea tangent vector at grid point.

Material support

SOL 402 adds support for the following materials:

• User-defined materials (MUMAT).

• MATSR strain rate dependence.

• MATG gasket materials. For more information, see Gasket material (SOL 402) in the Multi-StepNonlinear User's Guide.

SOL 402 adds support for the following material properties and laws:

• TABLEM5 tabular function for progressive ply failure. For more information, see Ply failuretheories (SOL 402) in the Multi-Step Nonlinear User's Guide.

• Strain hardening, Norton and generalized Garofalo creep laws in the MATCRP bulk entry.

Glue support

You can now define edge-to-edge glue conditions for shells, axisymmetric elements, plane strain, orplane stress elements.



Multi-step nonlinear kinematics solution 402

Contact support

You can now use the NPENAL2 parameter of the BCTPAR2 bulk entry to describe the relationshipbetween the normal distance and the contact pressure.

For more information, see Contact overview, Contact element, and Contact convergence in theMulti-Step Nonlinear User's Guide.

Nonlinear parameters

On the NLCNTL2 bulk entry:

• You can now define parameters to control the analysis, like the maximum allowed displacementor rotation, specify whether time-unassigned loads are ramped or stepped, or take inertia intoaccount in nonlinear dynamic subcases.

• You can now set options to control plasticity and creep conditions.

• You can now define the CRINFAC integration factor used to calculate incremental creep strain.

• You can now use several options to better control automatic time stepping, such as the control ofnegative or zero pivots, the control of the viscous material integration schema, or the error controlparameters for the Newmark, Hilber-Hughes-Taylor, Generalized midpoint, and Generalized-αintegration schemes.

• You can define the restart option.

For more information, see Nonlinear Parameters in SOL 402: NLCNTL2 entry in the Multi-StepNonlinear User's Guide.

Stress-strain measures and hardening law conversion

In SOL 402, the combination of the STRMEAS parameter of the NLCNTLG bulk entry with thePARAM,LGSTRN value will induce specific hardening laws conversions.

For more information, see Stress-strain measures (SOL 402) in theMulti-Step Nonlinear User's Guide.

Time stepping strategy

Automatic time stepping strategy is turned on by default and can be controlled using the AUTOTIM,DTINIT, DTMIN, DTMAX, EQMFMX, and EQMFMIN parameters of the NLCNTL2 bulk entry.

Disabling the automatic time stepping strategy (AUTOTIM='OFF') will now disable all the errorscontrol parameters related to the selected integration scheme.

Restart

In SOL 402, you can now restart your solutions in the following ways:

• You can set up an internal restart.

In an internal restart, you start the solve of a subcase with the computation state (displacements,velocities, stresses, state variables, and so on) of a preload, static, or dynamic previous subcaseduring the same solve. For example, you might want to start several non-sequentially dependent(NSD) subcases with the results of a bolt preload subcase. Similarly, you can start other NSDsubcases with the results of a dynamics subcase.




Although these subcases restart with the computation state of the subcase you specify, they donot restart with the end time of the specified subcase. Time continues to increment for eachsubcase.

You can use the RSUB parameter of the NLCNTL2 bulk entry to select the subcase you wantto restart from.

• You can set up an external restart.

In an external restart, you start a new nonlinear solve with results from a previous solve. Forexample, you can start a new solution using the computed pre-stress of your model. Or, you canstart a new solution from the last converged step within a static or dynamic subcase.

SOL 402 supports external restarts from the end of a subcase or from the last converged timestep. They do not support restarting from other time steps within a subcase. The restart point canbe a static subcase, dynamic subcase, or the end of a preload subcase. Your restart solution canbe a clone of your initial run solution, or it can be a new solution.

You control the external restart options with the NLCNTLG bulk entry.

Note

When you create the restart run, you cannot change any of the contact options that youpreviously defined on the BCTPAR2 bulk entry.

For more information, see Restart in the Multi-Step Nonlinear User's Guide.

Solver support

SOL 402 supports the sparse direct solver (default) or the parallel solver. The element iterativesolver is not supported.

• The Nastran MPI402 keyword specifies the maximum number of CPU selected fordistributed-memory parallel (DMP) processing. The NASTRAN command PARALLEL sets thenumber of MKL threads for shared-memory parallel (SMP) processing.

Supported case control output requests

SOL 402 supports only SORT1 data. SORT2 is not supported.

Case control DescriptionACCELERATION Requests accelerationsBCRESULTS Requests contact resultsBGRESULTS Requests glue resultsBOLTRESULTS Requests bolt resultsCRSTRN Requests creep strain at grid pointsCZRESULT Requests results output for cohesive elementsDISPLACEMENT Requests displacement outputELSTRN Requests elastic strain output at grid points on elementsEKE Requests element kinetic energy outputELSUM Requests output of an element property summaryESE Requests the output of the strain energy




FLXRESULTS Requests outputs for flexible slidersFORCE Requests element force outputGKRESULTS Gasket resultsGPFORCE Requests grid point force balance at selected grid pointsHOUPUT Requests harmonic output for cyclic symmetry and axisymmetric modelsJRESULTS Requests outputs for kinematic jointsMEFFMASS Requests modal effective mass output in a modal subcaseMONVAR Selects degree-of-freedom for a displacement monitor plotMPCFORCES Requests the form and type of multipoint force of constraint vector outputOLOAD Requests the form and type of applied load vector outputOMODES Requests a set of modes for outputOTEMP Requests temperature outputPFRESULTS Requests progressive failure results output for composite solid elementsPLSTRN Requests plastic strain at grid pointsSET Defines a set of element or grid point numbers to be plottedSETMC Set definitions for modal, panel, and grid contribution resultsSETMCNAME Specifies the title of a displacement monitor plotSHELLTHK Requests shell thickness outputSPCFORCES Requests single-point force of constraint vector outputSTATVAR Requests output of state variablesSTRAIN Requests element strain outputSTRESS Requests element stress outputTHSTRN Requests thermal strain at grid points on elementsVELOCITY Requests the form and type of velocity vector output

Input summary

You can use the following parameters with SOL 402.

ALPHA1 K6ROT MATNL SNORMALPHA2 LGDISP NLAYERS UNITSYSF56 LGSTRN POST

You can use the following case control commands with SOL 402.

ACCELERATION DTEMP LABEL SHELLTHKANALYSIS EKE LOAD SPCBCRESULTS ELSTRN MEFFMASS SPCFORCESBCSET ELSUM METHOD STATVARBGRESULTS ESE MONVAR STRAINBGSET FLXRESULTS MPC STRESSBOLTLD FLXSLI MPCFORCES SUBCASEBOLTRESULTS FORCE NLCNTL SUBTITLECMETHOD GKRESULTS OLOAD TEMPERATURECRSTRN GPFORCE OTEMP THSTRN




CYCFORCES HARMONICS PFRESULTS TITLECYCSET HOUTPUT PLSTRN TSTEPCZRESULTS IC SEQDEP VELOCITYDISPLACEMENT JCONSET SETDLOAD JRESULTS SETMC

You can use the following bulk entries with SOL 402.

BCPROP CPLSTS3 MAT1 PELASTBCPROPS CPLSTS4 MAT11 PGAPBCRPARA CPLSTS6 MAT2 PJOINTBCTADD CPLSTS8 MAT3 PJOINT2BCTPAR2 CPYRAM MAT8 PLOADBCTSET CQUAD MAT9 PLOAD1BEDGE CQUAD4 MATCID PLOAD2BGADD CQUAD8 MATCRP PLOAD4BGPARM CQUADR MATCZ PLOADE1BGSET CQUADX4 MATDMG PLOADX1BOLFRC CQUADX8 MATFT PLPLANEBOLT CREEP MATG PLSOLIDBOLTFOR CROD MATHE PMASSBOLTLD CTETRA MATHEM PPLANEBSURF CTRAX3 MATHEV PRODBSURFS CTRAX6 MATS1 PSHELLCBAR CTRIA3 MATSR PSHL3DCBEAM CTRIA6 MATT1 PSOLCZCBUSH CTRIAR MATT11 PSOLIDCBUSH1D CYCADD MATT2 RBARCDAMP1 CYCAXIS MATT3 RBE2CDAMP2 CYCSET MATT8 RBE3CELAS1 DESC MATT9 RFORCECELAS2 DLOAD MATTC RFORCE1CGAP DRIVER MOMENT SPCCHEXA DTEMP MOMENT1 SPC1CHEXZ ECHOOFF MOMENT2 SPCADDCJOINT ECHOON MPC SPCDCMASS1 EIGB MPCADD TABLED1CMASS2 EIGC MUMAT TABLED2CONM1 EIGR NLCNTL2 TABLED3CONM2 EIGRL NLCNTLG TABLED4CONROD ENDDATA PBAR TABLEM1CORD1C FLXADD PBARL TABLEM2CORD1R FLXSLI PBEAM TABLEM3




CORD1S FORCE PBEAML TABLEM4CORD2C FORCE1 PBUSH TABLEM5CORD2R FORCE2 PBUSH1D TABLES1CORD2S GRAV PBUSHT TABLESTCPENTA GRID PCOMP TEMPCPENTCZ GROUP PCOMPG TEMPDCPLSTN3 INCLUDE PCOMPG1 TICCPLSTN4 JCON PCOMPS TLOAD1CPLSTN6 JCONADD PDAMP TSTEPCPLSTN8 LOAD PELAS TSTEP1

You can use the following NASTRAN system cells in SOL 402:

57 400 525 67481 401 587 675107 413 592 683143 442 593 699

Solution monitor

To aid you in assessing the status of your solve, the Solution Monitor provides plots for contact andmaterial status, convergence, and energy results.

To help you decide whether a solve should continue, you can interact with the solve by viewingprogress on the SOL 402 tab, or by viewing the graphs as they update.

If you see that the solution cannot converge, you can stop it in the Solution Monitor and thendisplay the intermediate results in post-processing.

For more information, see Solution Monitor in the Simcenter 3D help.

Miscellaneous

• You can now define GROUP of grid points.

• SOL 402 will only run on long-word computers.

Kinematic joints in SOL 402In the Simcenter Nastran SOL 402 solution sequence, you can define kinematic joints and flexiblesliders.

Kinematics joints allow the structural analysis of an assembly that contains moving parts.

With flexible sliders, you will drive the displacement of parts along a line of beams that models a track.

Kinematic joint typesJoint topologyJoint description




Joint propertiesAdditional joint propertiesKinematic driversJoint time constraintOutput requests on jointsFlexible sliderOther bulk entriesOther case control commands

Kinematic joint types

The joint connects two nodes N1 and N2.

Some joints can have an optional third node N3 to support spring or damper additional properties,or driver loads.

You can define the following types of joints.

Joint type Description Third nodeallowed

REVOLUTE The two nodes are coincident. The joint constrains them torotate relative to each other along an axis that you define. Yes

INLINE This joint constrains the second node N2 to slide along avector that is attached to first node N1. Yes

SLIDERThis joint constrains the second node N2 to slide along thestraight line that joints both nodes, but fixes the relativerotation between the nodes.

Yes

SPHERE This joint allows the relative rotation between the two nodes,but fixes their relative translation. -

CYLDRThis joint constrains the second node N2 to slide along thestraight line that joints both nodes and allows a relativerotation between the nodes along that axis.

Yes

SLIUNV

This joint constrains the second node N2 to slide along avector that is attached to first node N1.

An universal joint relation is introduced between therotations of the two nodes.

Yes

FIXEDThis joint defines rigid links between the two nodes. Thelinks can be activated or released per DOF at a given time.For more information, see Joint time constraint.

-

SCREWThis joint acts as CYLDR joint but the relative rotationaround and translation along the straight line that joints bothnodes are related by the pitch property of the screw.

Yes

UNIVSL The two nodes are coincident. This joint acts as twocombined REVOLUTE joints and designs a cardan shaft. -

CONVEL

The two nodes are coincident. This joint introduces onekinematic condition on the relative rotation of the twonodes. The translational constrains on the two nodes DOFsare imposed either by Boolean identification or Lagrangemultipliers.

-




Joint topology

In the CJOINT bulk entry, you define:

• The joint topology and optionally the joint axis.

• The property identification number of the PJOINT and (optional) PJOINT2 bulk entries.

• (Optional) the description identification number of the DESC bulk entry.

Joint description

In the DESC bulk entry, you can optionally add a description (text) for the joint.

Joint properties

In the PJOINT bulk entry you define the joint type.

Optionally, you can also define:

• Stiffness and friction data.

• Specific properties, such the characteristic lengths for the REVOLUTE or the SLIDER, or thePITCH for the screw.

Additional joint properties

In the PJOINT2 bulk entry, you can add a spring and/or damper behavior to the joint.

This applies to a REVOLUTE, INLINE, SLIDER, CYLDR, SLIUNV, or SCREW joint.

You define stiffness ar damping data that can be constant or defined using table fields.

Kinematic drivers

You can use the DRIVER bulk entry to define loads on the joints.

You can define displacements or forces on INLINE, SLIDER, CYLDR, SLIUNV, or SCREW joints.

You can define rotations or torques on REVOLUTE, CYLDR or SCREW joints.

No load can be defined on FIXED, UNIVSL or CONVEL joints.

Joint time constraint

In the JCON bulk entry, you can define time constraints. At a given time, you can:

• Fix or release a REVOLUTE, INLINE, SLIDER, CYLDR, SLIUNV, or SCREW joint.

• Release specific translation and/or rotation DOFs for a FIXED joint.

Output requests on joints

In the JRESULTS case control command, you can set output requests on joints. You can request:

• Force and moment vector in basic coordinates.

• The relative position and rotation between the kinematic joint node definition in basic coordinates.

• The relative velocity and angular velocity between the kinematic joint node definition in basiccoordinates.




Flexible slider

The FLXSLI bulk entry lets you define flexible sliders: you set a list of nodes to follow a track madeof beams.

You define the slider type that will link each node to a beam:

Slider Conditions on the rotation of the moving nodeFLEX The rotations of the node are free.

CYLF The rotations of the node around the beam axis re free, the two other rotations(around the transverse axes) are identical to the ones of the beam.

PRIF The rotations of the node are identical to the rotations of the beam.

TWIFThe rotations of the node around the beam axis are identical the beam rotationaround that axis, but the two other rotations (around the transverse axes) arefree.

Optionally, you can also add:

• Friction data.

• A driver:

o You can define a force or displacement driver that will load the flexible slider with a constantvalue or values using in table fields.

o You can define a simple sensor to retrieve results.

When you define a driver, you can also request to output the relative displacement along thecurvilinear abscissa of the track in the FLXRESULTS case control command.

Other bulk entries

You can also define the following additional bulk entries:

Bulk entry Description

JCONADD Define a set of JCON constraints. That JCONADD entry can be referenced ina JCONSET case control command.

FLXADD Define a set of FLXSLI flexible sliders. That FLXADD entry can be referencedin a FLXSLI case control command.

Other case control commands

You can also define the following additional case control commands:

Case Control DescriptionJCONSET Select a single JCON constraint or a JCONADD bulk entry.

FLXSLI Select a single flexible slider or a FLXADD bulk entry. This case controlcommand is global and cannot vary from one subcase to another.



Chapter 9: Performance

SMP parallelization of element matrix assemblyTo enhance system performance when you specify the PARALLEL execution keyword, the softwarenow uses open multi-processing (OpenMP) to parallelize element matrix assembly (EMA). By usingOpenMP, the open core is optimized for best threaded performance.

In previous versions, EMA is a serial process. When matrix decomposition is parallelized at theshared memory parallel (SMP) level, serial EMA can become a bottleneck that limits performance.

To revert to serial EMA, specify SYSTEM(707)=1.

RDMODES improvementsRecursive Domain Normal Modes (RDMODES) is a parallel capability that uses substructuringtechnology for large scale normal modes analysis.

The RDMODES performance has been improved for Simcenter Nastran 2019.1. One improvementis in the Lanczos method for the reduced eigenvalue computation in the RDMODES method. It isparticularly beneficial when you are requesting a large number of modes.

In addition, we introduced an alternative in-core dense eigensolver for the reduced eigenvalueproblem. The in-core option is more efficient than the Lanczos method for denser problems such asmodels that include external superelements. Both improvements produce reduced solution times,and results that are consistent with NX Nastran 12.

The new RDQSOL parameter is available to request the eigensolver for the reduced eigenvalueproblem in the RDMODES method. The choices are LANC(ZOS), and INCO(RE). The default,RDQSOL=LANC, selects the Lanczos method and is suitable for most models. RDQSOL=INCOselects the in-core method, and is the best choice for dense models.

The following table summarizes the performance improvement for a variety of models. Theimprovements become more significant for larger numbers of modes. All of these runs wereperformed with DMP=4, SMP=6, and RDQSOL=LANC (default).

Structure DOF(Millions)

StructureModes

Percentage Decreasein CPU Time

Model 1 13.4 4,100 2Model 2 11.5 12,000 16Model 3 22.2 16,700 31

The following table shows a notable improvement for a fully coupled fluid-structure vibro-acousticmodel that includes an external superelement. The size of the model is moderate, but the number ofmodes is large. The run was performed with SMP=16, and RDQSOL= INCO.



Structure DOF(Millions)

StructureModes

Percentage Decreasein CPU Time compared

to LanczosModel 4 0.23 29,000 70

RDMODES can run in either DMP, serial, or SMP configurations. The DMP, serial, and SMP runs willall benefit.

You activate RDMODES by entering the Nastran keyword ‘nrec’ on the command line. To specifythe desired parallel functionality, you can also enter the Nastran keywords ‘dmp’ or ‘smp’. Samplecommand line entries include:

DMP: NASTRAN nrec = m dmp = p

Serial: NASTRAN nrec = m

SMP: NASTRAN nrec = m smp = p

SMP and DMP: NASTRAN nrec = m smp = p dmp = p

where m is the number of external partitions and p is the number of processors.

See the Parallel Processing Guide for information on all parallel options.

Frequency response performanceThe following new performance options are available for the frequency response solutions (SOLs 108and 111).

• When you run SOL 111 with SYSTEM 462=1 (default), the software automatically selects thesolution method. The software selects the in-core FRRDRU method when:

o The model does not include frequency-dependent properties or materials.

o The model does not include unsymmetric damping.

o The mode does not consist of only fluid elements.

o The number of modes > 500 (default).

o There is enough memory to solve in-core.

The in-core FRRDRU method has been improved. You will see the best improvements if yourmodel is requesting a large number of modes (both structure and fluid, > 10,000), and a largenumber of solution frequencies (> 100).

The following table summarizes the performance improvements for four models comparing runsfrom NX Nastran 12, with runs from Simcenter Nastran 2019.1. All of the runs used SMP=24.

ApproximateStructure DOF

(Millions)

Structureand FluidModes

(Thousands)

Structure(K4) Damping(Thousands)

Percentimprovement inelapsed time

Model 1 12 12 1 12



Performance


(Millions)

Structureand FluidModes

(Thousands)

Structure(K4) Damping(Thousands)

Percentimprovement inelapsed time

Model 2 15 10 4 55Model 3 4 14 3 58Model 4 30 28 15 66

• The new Pardiso solver is available for both SOLs 108 and 111. The new solver is especiallyuseful for frequency-dependent problems.

The new solver is automatically selected for SOL 111 based on the density of the resulting inputmatrices (Sparsity<10%).

You can explicitly request the new solver for SOL 108 or 111 by defining the new system cellsetting SYS693=1. The default value of the system cell 693 is 0.

You can explicitly request the previous Sparse solver for SOL 108 or 111 by defining the newsystem cell setting SYS693=-1.

The following table summarizes two models that are used to demonstrate the improvement.Results for two SOL 111 runs for each model are summarized below the table.


(Millions)

ApproximateFluid DOF(Millions)

Structure Modes(Thousands)

Number ofSolution

FrequenciesModel 1 2 0.75 0.5 1000Model 2 0.5 0.5 3 150

Model 1 elapsed time improvement::

RUN 1 SMP=8 66% ImprovementRUN 2 DMP=4 and SMP=7 69% Improvement

Model 2 elapsed time improvement::

RUN 1 SMP=8 73% ImprovementRUN 2 SMP=16 80% Improvement

• The new FRRUD3 solution method is available for SOL 111 to reduce your solve time when yourmodel includes a large fluid-structure coupling, you are solving for a large number of fluid modes(> 3000), and your number of solution frequencies is >100.

You can request the new method by defining the new system cell setting SYS625=1, and you areusing the default setting for the system cell 462 (SYS462=1).

By default, SYS625=0, and the previous FRRUD1 method is used.

The new FRRUD3 solution method reduces the elapsed time for the model described below by31%. This reduced time is relative to the NX Nastran 12 FRRUD1 method.

o The model included a fluid-structure coupling.


Performance


o It requested 11K structure modes and 3K fluid modes.

o A response was computed for 200 solution frequencies.



Chapter 10: Bolt preload

Bolt preload improvements for linear solutionsBolt preload defined as a displacement

In the previous release, you could define a bolt preload only as a force for the linear solutions 101,103, 105, 107 through 112. You could define the preload force with either the BOLTFOR bulk entry orwith the BOLTFRC bulk entry with TYPE=LOAD.

You can now also define the bolt preload as a displacement for the linear solutions using theBOLTFRC bulk entry with TYPE=DISP. The displacement that you define on the BOLTFRC entryrepresents the resulting shortening of the bolt from the preload. The software uses the bolt length toconvert the preload displacement to an equivalent axial bolt strain.

The STRAIN preload option on the BOLTFRC bulk entry is not supported for the linear solutionsand will cause a fatal error if defined.

Also see Bolt preload improvements for SOL 401.


Chapter 11: Optimization

Design objective improvementThe design objective is the single overall goal of the optimization. You define the single objective withthe DESOBJ case control command, which selects a design response such as weight, displacement,or compliance. The objectives to minimize weight or volume are computed independent of anysubcase and defined globally. However, when an objective references a response computed acrosssubcases that can also include multiple grid points or elements, you must use a method that resolvesthe multiple responses into a single value.

For example, the objective to minimize the x-displacement of multiple grid points could be definedin a specific subcase. In this case, you must decide how the software will resolve the multipledisplacement values. If this same objective was defined globally (above the subcases), you mustdecide A) how the software will resolve the multiple displacement values in each subcase, and B)how it will resolve each value found in A) for the multiple subcases.

In the previous release, you were required to resolve multiple responses by using either the DRSPANor BETA methods. In addition, an alternative DESOBJ case control command first became availablein the NX Nastran maintenance package 12.0.0 MP1 to resolve compliance subcase responses in atopology optimization run. This capability is described in the NX Nastran 12.0.1 Release Guide.

Now the DESOBJ command includes describers to resolve any DRESP1 response type from static,normal mode, or linear buckling subcases into a single value. The updated DESOBJ format issupported for all SOL 200 runs including Topology Optimization.

The format for a global definition now includes the SCSET and SCFUNC options to resolve responsesacross multiple subcases (selected using SCSET), and it includes the ENFUNC option to resolveresponses from multiple grid points or elements such as displacement or stress. The DESOBJ formatfor a global definition is as follows.

The format for the specific subcase definition now includes the ENFUNC option described above.The DESOBJ format for a subcase definition is as follows.


https://docs.plm.automation.siemens.com/docs/nastran/12.0.1/en_US/release_guide.pdf


For both formats, the existing MIN or MAX selection still requests that the objective is to be minimizedor maximized, and n still refers to a response ID, although, when using the new format (that is,ENFUNC, SCSET, or SCFUNC are defined), n can only refer to a DRESP1 response type fromstatic, normal mode, or linear buckling subcases.

To resolve responses for subcases other than static, normal mode, or linear buckling, you must usethe DRSPAN or BETA methods. See Resolving Multiple Design Responses in the Design Sensitivityand Optimization User's Guide for a description of these methods.

See DESOBJ for a description of both new and existing describers.



Optimization

DESOBJ

Design Objective

Selects the DRESP1, DRESP2, or DRESP3 entry to be used as the design objective.FORMATS:

Format for global definition:

Format for subcase definition:

EXAMPLES:DESOBJ=10DESO=25DESOBJ(MIN,SCSET=ALL,SCFUNC=MAX)=10

DESCRIBERS:

Describer Meaning

General Describers

MIN Specifies that the objective is to be minimized.

MAX Specifies that the objective is to be maximized.

n ID number of a DRESP1, DRESP2, or DRESP3 bulk entry. TheDRESP2 and DRESP3 options are valid only for the simplerDESOBJ command (see Remark 11). (Integer>0)

SCSET Describers


Optimization


Describer Meaning

FIRST The objective response is computed only for the first subcase(legacy behavior).

ALL Spans the objective response across all compatible subcases(Default).

m Spans the objective response across the subcases listed in SETm.

SCFUNC and ENFUNC Describers

MAX Combine the responses from the different subcases/entities bytaking the maximum value (Default, see remarks 13 and 14).

MIN Combine the responses from the different subcases/entities bytaking the minimum value (See remarks 13 and 14).

SUM Combine the responses from the different subcases/entities bycomputing the sum.

AVG Combine the responses from the different subcases/entities bycomputing the average.

SSQ Combine the responses from the different subcases/entities bycomputing the sum of the squares.

RSS Combine the responses from the different subcases/entities bycomputing square root of the sum of the squares.

ENFUNC only Describers

NONE No combination is made across entities listed on the response(legacy behavior).

REMARKS:1. A DESOBJ command is required for a design optimization task and is optional for

a sensitivity task. No more than one DESOBJ may appear in Case Control.

2. If the DESOBJ command is specified within a SUBCASE, the identified DRESPiBulk Data entry uses a response only from that subcase. If DESOBJ appearsabove all SUBCASE commands and there are multiple subcases, it uses a globalresponse (See also Remarks 4, 5, 9, 10, 11 and 12).

3. The minimization or maximization is on the algebraic value of the objectivefunction. Thus, be careful if you expect negative values or if there is a possibility forthe objective function to change sign during optimization. For example, to minimizethe absolute value of a displacement component, the absolute value or the squareof the relevant response may need to be specified with a DRESP2 responsethat references the DRESP1 for that particular displacement component. If it ispossible for the objective function to change sign, as in the case of a displacementcomponent, the change of sign can cause the objective function to move in anundesirable direction. When such a possibility exists, it is best to place appropriateconstraints on the value of the response that is used for the objective function.



Optimization

4. A global response, as mentioned in Remark 2, may be either asubcase-independent response or a subcase-dependent response (see remarks9, 10, 11 and 12) or one that includes a combination of DRESP1 responses frommore than one subcase (see also DRSPAN Case Control command, and theRemarks for DESGLB).

5. When the global response includes a combination of DRESP1 responses frommore than one subcase, each such DRESP1 response must have been assignedto a particular subcase using the DRSPAN Case Control command. A DESOBJreferencing such a global response is output for the last analyzed subcaseassociated with the second level response in question.

6. When the design is infeasible due to violated constraints, the objective functionmay move in the direction opposite to that desired in an attempt to reach thefeasible region.

7. The best design found is not necessarily the one in the last design cycle or the onewith the lowest value of the objective function. If there are one or more feasibledesigns (very small positive within specified or default tolerance, or negativemaximum normalized constraint values), the best design is the feasible designwith the lowest value of the objective function. If there are no feasible designs(all positive non-trivial values of the maximum normalized constraint), the bestinfeasible design found is that with the smallest value of the maximum normalizedconstraint, without regard for the value of the objective function. However, fortopology optimization, see also Remark 8.

8. For topology optimization jobs, if there are no maximum size, casting or additivemanufacturing constraint, the determination of the best design follows the logicdescribed in Remark 7. Otherwise, the comparisons for the best design selectionis based only on those design cycles where manufacturing constraints have beenactivated (see also Parameter BDMNCON).

9. SCSET, SCFUNC and ENFUNC options can only be used if n refers tosubcase-dependent DRESP1 responses. Furthermore, they do not apply toresponses related to frequency (DFREQ and MFREQ), transient (MTRAN) andaeroelasticity (SAERO and FLUTTER) subcases types. For instance, they are notapplicable to DRESP1 such as WEIGHT, VOLUME, FRDISP or TSTRESS and toDRESP2 or DRESP3 responses.

10. The SCSET, SCFUNC and ENFUNC options are not supported withsuperelements.

11. SCFUNC can be used such that the objective function is evaluated for each of theselected (SCSET) and relevant subcases. The values resulting from each subcaseare then combined using the operator specified after SCFUNC to compute theobjective value. This option can only be used when DESOBJ card is placed atglobal level and not inside a subcase.

12. ENFUNC applies to DRESP1, which can reference several entities (for example,a displacement component over a number of grid points, stress over several


Optimization


elements). These operators allow combining all the listed entities onto the designobjective.

13. The default for SCFUNC and ENFUNC option is MAX. However, to preserve theconsistency of the optimization problem, this default is switched to MIN in case theobjective is requested to be maximized (for example, DESOBJ(MAX)=n).

14. MAX and MIN operators (SCFUNC and ENFUNC) consider response algebraicvalues (with their sign) alike corresponding DRESP2 integrated functions. Hence,if the objective response corresponds to both positive and negative values acrossselected subcases and/or entities, MAX always selects the positive value with thelargest magnitude and MIN selects the negative value with the largest absolutevalue.

Topology optimization improvements

Manufacturing constraint improvements

Manufacturing constraints are optional restrictions that you can include in your topology optimizationsolution to guide the design towards meeting your production criteria. The cyclic symmetry,extrusion, and minimum size manufacturing constraints have been improved, and as a result, arenow more robust and reliable. These improvements have corrected issues with constraint violations,performance issues, or oscillations of the design process.

The inputs to define these constraints have not changed, and are described on the DMNCON bulkentry.

The specific improvements are described below.

• Cyclic symmetry and extrusion constraint

A new formulation has been implemented for the cyclic symmetry and extrusion constraints. Thenew formulation, based on design variable linking, automatically defines the links between designvariables that should be equal according to the defined constraints.

With the new formulation, the constraint is exact when the mesh conforms to the constraint(meaning that the mesh is cyclically symmetric or extruded). In the general case of a free(or unstructured) mesh, these constraints are approximate because the link between designvariables involves a distance tolerance. Mesh refinement will improve this approximation.

The updated formulation also enables a better processing of combinations of planar symmetry,cyclic symmetry and extrusion constraint.

The following manufacturing constraint combinations are supported:

o Up to 3 planar symmetry with planes orthogonal to each other.

o 1 cyclic symmetry + 1 planar symmetry with planar symmetry plane orthogonal to cyclicsymmetry rotation axis.

o 1 cyclic symmetry + 1 extrusion, with extrusion vector collinear to cyclic symmetry rotationaxis.



Optimization

o 1 extrusion + 1 or 2 planar symmetries, with planes parallel to the extrusion direction andnormal to each other.

• Minimum size constraint

The formulation of the minimum size constraint has been redesigned. As a consequence, it isnow implicitly integrated into the optimization problem definition, which improves convergence ofthe optimization process and result quality.

Stress sensitivity performance improvement

For topology and topometry optimization problems, the adjoint loads method is now available andautomatically used for sensitivity analysis of static stress responses. Considering the large amount ofdesign variables these optimization problem usually involve, the adjoint load method has a significantadvantage in terms of solution time and memory requirements over the pseudo-load method that wasformerly used for stress response.

See Use of Adjoint Loads in Design Sensitivity Analysis in the Design Sensitivity and OptimizationUser's Guide for a description of the method.

Output improvement for topology optimization

The parameter NASPRT defines the frequency in which the solution performs data recovery andwrites output.

Previously, the option PARAM, NASPRT, 0 would output the best design cycle to the .op2 file, whilethe last design cycle was written to the .f06 file. Note that the best design cycle and the last designcycle are not necessarily the same.

To improve output consistency, the PARAM, NASPRT, 0 request will now output the best designcycle to both the .op2 and .f06 files.

The NASPRT parameter includes the following options for topology optimization.

• NASPRT = 0 (Default): Output occurs for the 0th and the best design cycle.

• NASPRT = N where N>0: Output occurs for the 0th cycle and for every Nth increment.

• NASPRT = -1: No output occurs.

• NASPRT = -2: Output occurs for every improved design cycle.

Note that for topology optimization, none of the NASPRT settings specifically requests output for thelast design cycle. As a result, the result for the last design cycle is output only when the last designcycle coincides with one of the NASPRT requests described above.


Optimization


DMNCON

Manufacturing Constraint for Topology Optimization

Defines a manufacturing constraint for topology optimization.ADDITIVE

MANUFACTURING(ADDM)

FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID ADDM

ANGLE MIND X Y Z N1 N2 N3

CASTING DIEDIRECTION(S)

(CDID)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID CDID

X Y Z N1 N2 N3

D1 D2 D3 D21 D22 D23

CHECKER-BOARDINGCONTROL

(CHBC)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID CHBC

OFF-FLAG

CYCLICSYMMETRY

(SYMC)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID SYMC

X Y Z N1 N2 N3

M1 M2 M3 NSECT

EXTRUSIONALONG ASTRAIGHT

LINE (EXTC)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID EXTC

N1 N2 N3



Optimization

MINIMUMSIZE (MINS)

FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID MINS

Size

MAXIMUMSIZE (MAXS)

FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID MAXS

Size

PLANARSYMMETRY

(SYMP)FORMAT:

1 2 3 4 5 6 7 8 9 10

DMNCON ID SYMP

X Y Z N1 N2 N3

EXAMPLES:

DMNCON 500 SYMP

0.0 1.0 0.0 0.7071 0.7071 1.0

DMNCON 200 EXTC

1.0 0.0 0.0

FIELDS:

Field Contents

General Fields:

ID Identification number. (Integer>0)

TYPE Type of manufacturing constraint. (TYPE examples: ADDM, CHBC,EXTC) See Remark 4. (Character; No default)

Fields for Additive Manufacturing (ADDM):

Note that either ANGLE or MIND can be blank, indicating there is no such constraint.

ANGLE Maximum angle from the normal that points away from the baseplate, for overhangs, in degrees. (Real)

MIND Minimum allowed size. (Real).


Optimization


Field Contents

X,Y,Z Coordinates of a point on a plane for the base plate. (Real)

Ni Components of a vector normal to the base plate in the direction ofmaterial addition. (Real)

Fields for Casting die direction(s) (CDID):

X,Y,Z Coordinates of a point on the casting plane. (Real)

Ni Components of a vector normal to the casting plane. (Real)

Di Components of a vector that defines the first direction of moldremoval. (Real)

D2i Components of an optional vector that defines a second direction ofmold removal. If these components D2i are all 0.0 or blank, then onlythe first direction is used. (Real: default=0.0,0.0,0.0)

Fields for Checker-boarding control (CHBC):

OFF-FLAG This field is used only to turn off the default checker-boarding control,achieved by entering a negative real number in this field. (Real)

The checker-boarding control manufacturing constraint is on bydefault, even when you have not defined the DMNCON bulk entry.To disable checker-boarding control, you must define the DMNCONbulk entry with TYPE= CHBC and a negative real number in theOFF-FLAG field. Any other choices for the OFF-FLAG field will resultin the checker-boarding control remaining on by default.

Fields for Cyclic symmetry (SYMC):

X,Y,Z Coordinates of a point on the rotation axis. (Real)

Ni Components of a vector defining the axis of rotation. (Real)

Mi Components of a vector perpendicular to the axis of rotation, definingthe first boundary of the first symmetry sector. The software willsweep this vector counter clockwise by the angle = 360/NSECT todetermine the boundaries of the consecutive symmetry sectors.(Real)

NSECT The number of sectors that would fill the 360 degrees. (Positive ornegative integer)

When NSECT is a positive integer, the symmetry is that of repeatedsectors. When NSECT is a negative integer, the symmetry is thatof reflected sectors.



Optimization

Field Contents

Fields for Extrusion along a straight line (EXTC):

Ni Components of a vector defining the extrusion direction. (Real)

Fields for Min and Max size (MINS or MAXS):

Size Minimum or maximum member size. (Real)

Fields for Planar symmetry (SYMP):

X,Y,Z Coordinates of a point on the symmetry plane. (Real)

Ni Components of a vector normal to the symmetry plane. (Real)

REMARKS:1. Multiple DMNCON bulk entries are supported if you would like to define a variety of

manufacturing conditions. For example, you can have multiple DMNCON entrieswith TYPE=SYMP, and could also add another DMNCON entry with TYPE=MAXS.

2. The manufacturing conditions currently apply to all of the active elements selectedfor topology optimization.

3. Except for TYPE=SYMP, the parameter BDMNCON defines the design cycle atwhich the software will start application of the manufacturing constraints duringthe SOL 200 topology optimization solution. The resulting delay has been foundto improve the quality of results in topology optimization with manufacturingconstraints. The BDMNCON parameter default is the smaller of 10 cycles, or thevalue of the DESMAX parameter minus 3, but not smaller than 2. The DESMAXparameter defines the maximum number of design cycles allowed, and is definedon the DOPTPRM bulk entry. SYMP is applied from the beginning.

4.

TYPE Description

Additive (ADDM)

Additive manufacturing builds material layer by layer. Theprevious layers in a build-up must be sufficient to supportconsecutive layers. When building up overhanging geometry,if the overhang is built in an aggressive angle, there is apossibility that the structure can collapse as a result ofcantilevered material. You define a maximum overhang angleand/or a minimum size applicable to any slender members,as well as the manufacturing direction.

Overhang angles are measured relative to the positivemanufacturing direction vector.


Optimization


TYPE Description

Casting diedirection (CDID)

Parts that are cast should not have any pockets that cannotbe formed or protrusions that would interfere with the moldpieces from parting, or with the part coming out of the mold.You define the coordinates of a point on the casting plane,a vector normal to the casting plane, a vector along whichone part of the mold travels when separating, and another,optional, vector along which the other part of the mold, if itexists, travels when separating.

Checker-boardingcontrol (CHBC)

Checker-boarding is a condition where the software removesmaterial in an alternating pattern similar to a checker board,when simpler finite elements are used. It is undesirablebecause it does not represent an optimal distribution ofmaterial and the results are difficult to manufacture. Thechecker-boarding control constraint can be used to helpprevent this condition from occurring.

OFF-FLAG < 0.0, the checker-boarding control is turned off.

OFF-FLAG ≥ 0.0, the checker-boarding control is left on.

* Note: The software applies the checker-boarding control bydefault even when you have not defined a DMNCON bulkentry. If you want to disable the checker-boarding control,you must define the DMNCON bulk entry with TYPE=CHBCand a negative real number in the OFF-FLAG field.

Cyclic symmetry(SYMC)

You provide a full circular model that has repeated cyclicsymmetry sectors. The mesh on each sector does notneed to match. The software will work to symmetrize thenormalized mass density (NMD) values on each sector. Youdefine the axis of rotation, the number of sectors (NSECT)within 360 degrees, and relative to a 0-degree symmetryplane, you define a point on that symmetry plane and aradial vector perpendicular to the axis of rotation along oneof the edges of the symmetry plane. The software sweepsthe 0-degree symmetry plane counter clockwise by the angle= 360 / | NSECT | to determine the consecutive symmetryplanes.

When NSECT is a positive integer, the software treats yourmodel as having repeated sectors. When NSECT is anegative integer, the software treats your model as havingreflected sectors. With repeated symmetry, each sector issimilar to every other sector. With reflected symmetry, everysector is the mirror image of the previous sector. You can usereflected symmetry only with an even number of sectors.

Extrusion along astraight line (EXTC)

Extruded parts must have material continuity in the extrusiondirection. You define the straight line extrusion direction.

Min size (MINS)This allows you to control the minimum member size forcreated “slender” members. You define the minimumcross-sectional "thickness" size.



Optimization

TYPE Description

Max size (MAXS)

This allows you to control the maximum member size. Forexample, if you define the maximum member size, trussmembers created by the optimization process will not be any"thicker" than the specified size.

Planar symmetry(SYMP)

With this condition, your model must be meshed on bothsides of the symmetry plane. The mesh on each side of thesymmetry plane does not need to match. The software worksto symmetrize the NMD values on both sides of a givensymmetry plane. You define a point on the symmetry planeand a vector normal to the symmetry plane.


Optimization

Chapter 12: Miscellaneous

New VKI element iterative solverThe new VKI element iterative solver is available for SOL 101 and SOL 401 and is used by defaultwhen the element iterative solver is requested. The previous CASI element iterative solver is alsoavailable. The input requirements to request either of the element iterative solvers is summarizedbelow.

The element iterative solvers support all element types, although, the best performance is seenwith models composed of mostly solid elements.

• SOL 101 inputs:To request the VKI element iterative solver in SOL 101, you define ITER = YES and ELEMITER =YES on the NASTRAN statement.

To request the CASI element iterative solver in SOL 101, you define ITER = YES andSYSTEM(399) = 2 on the NASTRAN statement.

• SOL 401 inputs:To request the VKI element iterative solver in SOL 401, you define SOLVER = ELEMITER on theNLCNTL entry.

To request the CASI element iterative solver in SOL 401, you define SOLVER = ELEMITER onthe NLCNTL entry, and you define SYSTEM(399) = 2 on the NASTRAN statement.

The VKI element iterative solver and the CASI element iterative solver have the following restrictions.

SOL 101 Restrictions:• Superelements are not supported.

• The CQUAD8, CTRIA6, and RBE2 elements are only supported if the parameter settingELITASPC=YES is defined.

• The CQUAD4 and CTRIA3 elements are supported only if the parameter K6ROT is defined(results obtained will be the same as if the parameter SNORM = 0.0 was entered).

• Inertia relief is not supported.

• DMIG is not supported.

• Differential stiffness is not supported.

• The combination of a bolt preload in which the bolt is meshed with solid elements, contactconditions, and the element iterative solver is not supported.

• If you define the BOLT bulk entry using the ETYPE=2 bolt, instead of the glue based approach,the software will revert to an MPC approach.



• GROUNDCHECK and WEIGHTCHECK case control requests are not supported.

• The DMP parallel solution options are not supported. The SMP parallel solution option issupported.

SOL 401 Restrictions:• The combination of a bolt preload in which the bolt is meshed with solid elements and contact

conditions is not supported.

• GROUNDCHECK and WEIGHTCHECK case control requests are not supported.

• The DMP parallel solution options are not supported. The SMP parallel solution option issupported.

Open contact stiffness for linear solutionsThe new OPNSTF parameter is available on the BCTPARM bulk entry to change the open contactstiffness. The open contact stiffness is computed as OPNSTF * Closed Contact Stiffness. TheSOL 101 default is OPNSTF=1.0 and the open and closed contact stiffness are the same. Thisis the same behavior as in previous releases.

You can optionally define OPNSTF<1.0 to decrease the open contact stiffness. For example, formodels with large initial gaps at the contact interface, all contact elements may be initially open. Inthis situation, you may need enough contact stiffness to prevent a singularity, but not too muchopen stiffness to prevent contact from becoming established. When many contact elements remainopen by the second iteration, they can become inactive which can cause a singularity or contactconvergence issues.

The previous solution to this problem was to reduce the overall contact element stiffness using theAUTOSCAL parameter. The problem with this approach is that the closed contact condition canbecome very soft producing excessive penetrations in the final converged solution. This is becauseAUTOSCAL reduces the stiffness for all subsequent iterations.

Now, you can soften the open initial contact stiffness by defining a small value, such asOPNSTF=1.0E-6, allowing your contact elements to become well established in the initial iterations.After the gaps have closed, the software applies the closed contact stiffness which ensures smallpenetrations and an accurate final contact condition.

Note that the new OPNSTF parameter is also used by SOL 401. The SOL 401 default isOPNSTF=1.0E-6.

Edge loads that vary quadraticallyFor CPLSTS6 and CPLSTS8 plane stress elements, you can now use the PLOADE1 bulk entryto create surface tractions:

• Whose magnitude varies quadratically along the element edge.

• Whose direction is always measured relative to the normal to the element edge.

With this capability, you can more accurately model surface tractions:



Miscellaneous

• That have magnitude that varies nonlinearly.

• That are applied to curved element edges.

For example, in gas turbines, large nonlinear pressure gradients occur at the leading and trailingedges of compressor and turbine blades. In axisymmetric models of gas turbines, the blades areoften modeled with plane stress elements. If the plane stress elements are CPLSTS6 and CPLSTS8,you can use PLOADE1 bulk entries to model the pressure distribution along the edges of the bladeswith a piecewise continuous function that varies quadratically along the edge of each element. Inthis way, you can more accurately model the pressure distribution as compared to modeling it with alinear representation along the edge of each element.

To create surface tractions that vary quadratically, on the PLOADE1 bulk entry, specify the magnitudeof the surface traction in the following locations:

• At the end grid points of the element edge

• At the mid-side grid point on the element edge

To specify the angle at which the surface traction acts relative to the inward normal at all points alongthe element edge, specify a value in the THETA field of the PLOADE1 bulk entry.

For more information, see PLOADE1.


Miscellaneous


PLOADE1

Edge Load on Plane Strain and Plane Stress Elements

Defines a surface traction that acts along the edge of CPLSTN3, CPLSTN4, CPLSTN6,CPLSTN8, CPLSTS3, CPLSTS4, CPLSTS6, or CPLSTS8 elements. The magnitudeof the surface traction can be constant or vary linearly along the edge of CPLSTN3,CPLSTN4, CPLSTN6, CPLSTN8, CPLSTS3, and CPLSTS4 elements. The magnitudeof the surface traction can be constant or vary linearly or quadratically along the edgeof CPLSTS6 and CPLSTS8 elements.

FORMAT:

1 2 3 4 5 6 7 8 9 10PLOADE1 SID EID PA PB GA GB THETA PM

EXAMPLE:

PLOADE1 200 35 3.5 10.5 10 30 20.

FIELDS:

Field Contents

SID Load set identification number. See Remark 1. (Integer > 0)


PA Magnitude of the surface traction at grid point GA in force per unitarea. (Real; No default)

PB Magnitude of the surface traction at grid point GB in force per unitarea. (Real; Default = PA)

GA, GB Corner grid points. GA and GB are any two adjacent corner gridpoints of the element. (Integer > 0; No default)

THETA Angle between the direction of the surface traction and inward normalto the element edge in degrees. See Remarks 2, 3, and 4. (Real;Default = 0.0)

PM Magnitude of the surface traction at the mid-side grid point betweenGA and GB in force per unit area. (Real; For default behavior, seeRemark 5)

REMARKS:1. In static solution sequences, the load set ID (SID) is selected by the LOAD case

control command. In dynamic solution sequences, SID must be referenced inthe LID field of an LSEQ entry, which in turn must be selected by the LOADSETcase control command.

2. THETA is measured relative to the inward normal to the element edge thatconnects GA and GB as shown in Figures 12-1, 12-2, and 12-3. The positive sense



Miscellaneous

of rotation for THETA is about the negative Y-axis when the element lies in theXZ-plane, and is about the negative Z-axis when the element lies in the XY-plane.

Figure 12-1. Surface Traction on Linear Plane Stress (CPLSTS3, CPLSTS4) andPlane Strain (CPLSTN3, CPLSTS4) Element Edges

Figure 12-2. Surface Traction on Quadratic Plane Stress (CPLSTS6, CPLSTS8)Element Edges


Miscellaneous


Figure 12-3. Surface Traction on Quadratic Plane Strain (CPLSTN6, CPLSTN8)Element Edges

3. Because THETA is a constant, the normal and the tangential components of thesurface traction are a fixed ratio.

4. The direction in which the surface traction acts depends on THETA and the signof the surface traction magnitude. For example, if -90.0 < THETA < 90.0, thenormal component of the surface traction is directed inward when the magnitudeof the surface traction is positive, and is directed outward when the magnitude ofthe surface traction is negative. If 90.0 < THETA < 270.0, the normal componentof the surface traction is directed outward when the magnitude of the surfacetraction is positive, and is directed inward when the magnitude of the surfacetraction is negative.

5. The software obtains the equation that represents how the magnitude of thesurface traction is distributed as follows:

• For CPLSTN3, CPLSTN4, CPLSTN6, CPLSTN8, CPLSTS3, and CPLSTS4elements, the software ignores the PM field and fits a linear equation throughthe surface traction magnitudes at GA and GB.

• CPLSTS6 and CPLSTS8 elements, the software fits a quadratic equationthrough the surface traction magnitudes at GA, GB, and the mid-side nodebetween GA and GB. If the PM field is undefined, the software fits a linearequation through the surface traction magnitudes at GA and GB.

6. Table 12-1 shows the default follower force behavior for each analysis type.

Table 12-1. Follower Effects Default Behavior

Analysis Type Follower Force Follower Stiffness

SOLs 103, 105, 107,108, 109, 110, 111, and112 without STATSUB

Excluded Excluded



Miscellaneous

Table 12-1. Follower Effects Default Behavior

Analysis Type Follower Force Follower Stiffness

SOLs 103, 105, 107,108, 109, 110, 111, and112 with STATSUB

Excluded Included(1)

SOL 401 with ANALYSIS= MODES, CYCMODES,or FOURIER

Excluded Included(2)

SOL 401 smalldisplacement(PARAM,LGDISP,-1)

Excluded Excluded

SOL 401 largedisplacement(PARAM,LGDISP,1)

Included Excluded(2)

(1) To exclude follower stiffness, specify PARAM,FOLLOWK,NO.(2) To override the default behavior, use the FOLLOWK parameter on theNLCNTL bulk entry.

REMARKSRELATED TO

SOL 601:1. To define a surface traction as time-independent, use LOAD = SID in the case

control.

2. To define a surface traction as time-dependent, reference the SID in the EXCITEIDfield of a TLOAD1 entry and include a DLOAD case control command thatreferences the TLOAD1 entry.

3. In large deformation analysis, the direction of the surface traction follows thedeformation of the element by default. The use of LOADOPT = 0 in an NXSTRATentry causes the surface tractions to act in their original direction throughout theanalysis.

4. PM is ignored.

REMARKSRELATED TO

SOL 402:1. To define a surface traction as time-independent, use LOAD = SID in the case

control.

2. To define a surface traction as time-dependent, reference the SID in the EXCITEIDfield of a TLOAD1 entry and include a DLOAD case control command thatreferences the TLOAD1 entry.

3. THETA is ignored.


Miscellaneous


4. PM is ignored.

Element geometry checks in the .rcf fileYou can include element geometry checks in the run-time configuration (.rcf) file. For example,suppose that your input file includes the following element geometry checks:

GEOMCHECK HEX_AR=10.0,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK HEX_EPLR=1.5,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK HEX_WARP=1.7,MSGLIMIT=100,MSGTYPE=FATAL

Rather than including these geometry checks in the input file, you can include them in the .rcf fileas follows:

NASTRAN HEX_AR=10.0NASTRAN HEX_EPLR=1.5NASTRAN HEX_WARP=1.7NASTRAN MSGLIMIT=100NASTRAN MSGTYPE=FATAL

By including element geometry checks in the .rcf file, you can:

• Save time preparing an input file when you use the same element geometry checks repeatedly.

• Standardize element geometry checks across a company or within specific analysis groups.

However, by including element geometry checks in the .rcf file, you are limited to having a singlemessage limit specification and a single message type specification. Thus, on an individual elementgeometry check basis, you lose the ability to specify the following:

• The number of elements that must fail the element geometry check before the software issues awarning message or terminates the run.

• Whether the software issues a warning message or terminates the run.

When you include element geometry checks in both the input file and the .rcf file, the elementgeometry checks that the software uses are the union of those in the input file and the .rcf file. Ifthe same element geometry check is present in both the input file and the .rcf file, the input filespecification for the element geometry check takes precedence. For example, suppose that yourinput file includes the following element geometry checks:

GEOMCHECK HEX_AR=10.0,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK HEX_EPLR=1.5,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK HEX_WARP=1.7,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK TET_AR=8.0,MSGLIMIT=100,MSGTYPE=INFORM

and the .rcf file includes the following element geometry checks:

NASTRAN TET_AR=10.0NASTRAN TET_EPLR=1.5NASTRAN MSGLIMIT=50NASTRAN MSGTYPE=FATAL

The software processes the combined element geometry checks the same as it would the followinginput file specification:



Miscellaneous

GEOMCHECK HEX_AR=10.0,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK HEX_EPLR=1.5,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK HEX_WARP=1.7,MSGLIMIT=100,MSGTYPE=FATALGEOMCHECK TET_AR=8.0,MSGLIMIT=100,MSGTYPE=INFORMGEOMCHECK TET_EPLR=1.5,MSGLIMIT=50,MSGTYPE=FATAL


Miscellaneous

Chapter 13: Documentation changes

Removing documentation for AGGPCH parameterYou can access the functionality of the AGGPCH parameter by specifying the AGGPCH describeron the FLSTCNT case control command or the new FSCOUP describer on the EXTSEOUT casecontrol command. Because of this capability, the AGGPCH parameter is no longer needed andis removed from the documentation.

Removing documentation for RANCPLX parameterBecause the RANCPLX capability is removed from the software, the RANCPLX parameter isremoved from the documentation.

For more information, see Random analysis enhancements.


Chapter 14: Upward compatibility

Updated data blocks

CASECC

Updated Record - REPEAT

Word Name Type Description

...... ...... ...... ......

623 RMSINT I Random RMSINT parameter

624 XSEMODAC I External superelement MODACC parameter

625 XSEFSCOU I External superelement FSCOUP parameter

626 SCSET I Optimization static subcase set identificationnumber (DESOBJ)

627 SCFUNC I Optimization static subcase function option(DESOBJ)

628 ELAR I Element add/remove set identification number

629 ELAROFLG I Element status output flag: 1=yes, 0=no(ELAROUT)

630 DMTRSET I 1=yes (default), 0=no

631 DMTRMEDIA I bit(1)=1 (default), bit(1)=0 noprint; bit(2)=1punch, bit(2)=0 nopunch (default); bit(3)=1 plot

632 DMTRFMT I 0=real/imaginary (default),1=magnitude/phase

633 DMTRTYPE I Unused

634 PEAKOUT I PEAKOUT bulk entry selection

635 ELAROMDA I Element status output, output media(ELAROUT)

636 FLXSLI I Flexible slider identification number

637 JCONSET I Joint constraint set identification number




638 JRESSET I Kinematic joints output set (JRESULTS)

639 JRESMEDIA I Kinematic joints output media (JRESULTS)

640 JRESFMT I Kinematic joints output code: 1=force,2=moment, 4=position, 8=rotation, 16=speed,32=rotation speed (JRESULTS)

641 FLXRSET I Flexible slider output set (FLXRESULTS)

642 FLXRMEDIA I Flexible slider output media (FLXRESULTS)

643 FLXRFMT I Flexible slider output code: 64-curvdisp(FLXRESULTS)

644 ACTEMP I ACTEMP bulk entry selection

645 DMTRLSET I 1=yes (default), 0=no

646 DMTRLSMEDIA I bit(1)=1 print (default), bit(1)=0 noprint;bit(2)=1 punch, bit(2)=0 nopunch (default);bit(3)=1 plot

647 DMTRLSFMT I Unused

648 ENFUNC I Optimization entity response function option(DESOBJ)

649 GPFSOL I GPFORCE output frequency selection value

650 CSMSET I Co-simulation (wetted) region set identificationnumber

651 DISPSOL I DISPLACEMENT output frequency selectionvalue

652 VELOSOL I VELOCITY output frequency selection value

653 ACCESOL I ACCELERATION output frequency selectionvalue

654 PRESSOL I PRESSURE output frequency selection value

655 UNDEF(545) None

...... ...... ...... ......



Upward compatibility

CONTACT

Updated Record – ATVFS(6571,65,657)


1 SID I ATVFS identification number

2 OPTION I 0 = set, 1 = ALL

3 BID I BSURFS identification number

Word 3 repeats until -1 occurs

New Record – CSMADD(6700,67,670)


1 ID I Co-simulation (wetted) region set combinationidentification number

2 CID I Identification numbers of CSM entries


New Record – CSMSET(6590,62,659)


1 CSID I Co-simulation (wetted) identification number

2 BID I Identification number of BSURF, BSURFS, orBEDGE entry

3 DESCID I Co-simulation description identification number

New Record – FLXADD (9201,92,694)


1 ID I Identification number

2-n Gi I Grid point identification numbers

n+1 -1 I Delimiter

New Record – FLXSLI(9101,91,693)


1 FID I Flexible slider identification number





2 TYPE CHAR4 Slider type

3 NGRPID I Grid GROUP identification number

4 BGRPID I Beam element GROUP identification number

5 SGID I Sensor grid identification number

6 PROJ I Projection option: 0=no, 1=yes

7 NLIM I Number of beams to use

8 NALG I Lagrange and topology option

9 DTYPE I Driver type: 0=blank,1=FORC, 2=DISP, 3=SENS

10 DGID I Driver grid identification number

11 DVAL RS Driver constant value

12 DTID I Table identification number for time-dependent drivervalue

13 FOP I Friction option: 0=NO, 2=INFINTE, 3=VELO,4=DISP

14 CF RS Friction coefficient

15 TOL RS Critical velocity

16 KCF RS Pre-sliding stiffness

17 UNDEF(8) None

New Record – VATVFS(6801,68,680)


1 SID I VATVFS identification number

2 UNDEF None

3 BID3 I BSURFS identification number

4 BID2 I BSURF identification number

5 UNDEF(4) None




DIT

Updated Record - TABLED1(1105,11,133)


1 ID I Table identification number

2 CODEX I Type of interpolation for the x-axis

3 CODEY I Type of interpolation for the y-axis

4 FLAG I Extrapolation on/off flag

5 LOCUT RS Low cutoff value

6 HICUT RS High cutoff value

7 UNDEF(2) None

9 X RS X tabular value

10 Y RS Y tabular value

Words 9 through 10 repeat until (-1,-1) occurs

Updated Record – TABLED2(1205,12,134)



2 X1 RS X-axis shift




6 UNDEF(3) None

9 X RS X value

10 Y RS Y value










3 X2 RS X-axis normalization




7 UNDEF(2) None

9 X RS X value

10 Y RS Y value





2 TYPE I Type of table data: =0 for real/imaginary; =1 formagnitude/phase


4 LOCUT1 RS Real/magnitude part of low cutoff value

5 HICUT1 RS Real/magnitude part of high cutoff value

6 LOCUT2 RS Imaginary/phase part of low cutoff value

7 HICUT2 RS Imaginary/phase part of high cutoff value

8 UNDEF(1) None

9 X RS X value (frequency in Hz)

10 YR RS Y real or magnitude value

11 YI RS Y imaginary or phase value (phase in degrees)

Words 9 through 11 repeat until (-1,-1,-1) occurs




Updated Record – TABLEM1(105,1,93)



2 CODEX I Type of interpolation for the x-axis

3 CODEY I Type of interpolation for the y-axis


5 UNDEF(4) None

9 X RS X tabular value

10 Y RS Y tabular value







4 UNDEF(5) None

9 X RS X value

10 Y RS Y value






3 X2 RS X-axis normalization


5 UNDEF(4) None

9 X RS X value





10 Y RS Y value


DYNAMIC

New Record – ACANDUCT(6890,68,689)

Anechoic duct mode


1 SID I Load set identification number

2 PID I PACDUCT SID

3 UNDEF(3) None

New Record – ACDUCT(6780,60,678)

Acoustic duct mode



2 PID I PACDUCT SID

3 WTYPE I =0 for specific, =1 for distributed

4 MTYPE I =0 for pressure, =1 for intensity, =2 for power

5 FORM I = 0 for real part or magnitude, =1 for imaginary partor phase

6 MODXX I Mode number in the X-direction

7 MODYY I Mode number in the Y-direction

8 X1 RS Real part or magnitude of duct mode amplitude

9 TX1 I Table ID for real part or magnitude of duct modeamplitude

10 Y1 RS Imaginary part or phase of duct mode amplitude

11 TY1 RS Table ID for imaginary part or phase of duct modeamplitude

12 UNDEF(4) None




New Record – ACFAN(6810,61,681)

Acoustic fan noise



2 PID I Parameter set identification number

3 LUNF I Logical unit number for HDF5 file

4 LDID I Applied load descriptor identification number of aloading

5 LCID I Load case identification number of a specificloading

6 WINDOW I =0 for RECTANG, =1 for HANNING

7 UNDEF(4) None

New Record – ACSPO2 (6820,63,682)

Acoustic surface dipole




3 SIDSET1 I SET1 identification number


5 LDID I Applied load descriptor identification number of aloading

6 LCID I Load case identification number of a specificloading

7 UNDEF(4) None

New Record – FREQH(6830,64,683)



2 TYPE I =0 for SINGLE, =1 for LINEAR, =2 for LSUB

3 PID I PACFAN bulk ID





4 START I Number of the starting harmonic

5 END I Number of the ending harmonic

6 STEP I Steps of harmonic

7 NSUB I Sub-harmonic between harmonics

8 HTYPE I =0 for shaft, =1 for blade

9 UNDEF(2) None

New Record – FREQV(6990,69,699)



2 FMIN RS Minimum frequency

3 FMAX RS Maximum frequency

4 UNDEF(2) None

New Record – PACDUCT(6880,67,688)

Property of duct mode



2 BID I BSURFS identification number

3 OFFSET RS Offset

4 DID I Description identification number

5 GTYPE I = 0 for circular, =1 for annular, =2 for rectangular

6 LENGTH RS Length or external radius

7 WIDTH RS Width or inner radius

8 CID I Local coordinate identification number

9 XLOC RS Location of the origin in the X-direction

10 YLOC RS Location of the origin in the Y-direction

11 ZLOC RS Location of the origin in the Z-direction





12 XVECT1 RS X-direction of the duct vector 1

13 YVECT1 RS Y-direction of the duct vector 1

14 ZVECT1 RS Z-direction of the duct vector 1

15 UNDEF(11) None

New Record – PACFAN(7000,70,700)

Parameters for acoustic fan noise



2 TYPE I =0 INCOM, =1 COMP

3 RPM RS Rotational speed

4 NBLADES I Same force for each of NBLADES

5 UNUSED(6) I

New Record – PACSPO2 (7010,74,701)

Parameter acoustic surface dipole



2 UNDEF None

3 TYPE I = 0 INCOMP

= 1 COMP

4 EDGE I = 0 No edge correction

= 1 Edge correction

5 UNDEF(6) None

New Record –PEAKOUT(1102,12,80)


1 ID I Identification number for PEAKOUT





2 NPEAK I Desired number of peak responses

3 NEAR RS Minimum allowable frequency difference betweentwo peak responses

4 FAR RS Maximum allowable frequency difference betweentwo peak responses

5 LFREQ RS Starting frequency for peak response identification

6 HFREQ RS Ending frequency for peak response identification

7 DBREF RS Reference value for dB calculation

8 UNDEF None

9 TYPE I Output type: 1=displacement, 2=velocity,3=acceleration, 4=pressure, 5=pressure in dB,6=pressure in dBA

10 GI I Grid ID of response location (row)

11 CI I Component (0-6) of response location (row)

12 CUTTAB I Integer values for table, <0 for real value

13 CUTVALI RS Real value for cutoff, 0.0 for table



New Record – RANDPEX(2307,23,250)


1 SID I Set identification number


3 LDID I Identification number of descriptor on LUNF

4 FAXIS I Type of interpolation for the frequency axis

5 PAXIS I Type of interpolation for the PSD axis

6 UNDEF(2) None




New Record – RLOADEX(5007,50,242)



2 DELAYI RS DELAY bulk entry identification number

3 DPHASEI RS DPHASE bulk entry identification number

4 A RS Scale factor


6 LDID I Applied load descriptor Identification number onLUNF

7 LCID I Identification number of load case contained withinLDID

8 SET1ID I Identification number of SET1ID for grid list, 0 forall grids

9 DELAYR RS Constant value for tau if DELAYI=0

10 DPHASER RS Constant value for phase if DPHASEI=0

11 UNDEF(2) None

New Record – RPM(6870,65,687)

Rotational speed of fan



2 SPEED RS Rotational speed of fan

3 TIDSPEED I Table ID for rotational speed

4 UNDEF(3) None

Updated Record – PBEAR(9110,91,570)

PBEAR definition.


...... ...... ...... ......

70 TYPE3(2) CHAR4 Inertia type (M, MD, or MF)





71 ITXX3 I Integer table ID for XX values

72 ITXY3 I Integer table ID for XY values

73 ITYX3 I Integer table ID for YX values

74 ITYY3 I Integer table ID for YY values

75 ITXZ3 I Integer table ID for XZ values

76 ITYZ3 I Integer table ID for YZ values

77 ITZX3 I Integer table ID for ZX values

78 ITZY3 I Integer table ID for ZY values

79 ITZZ3 I Integer table ID for ZZ values

80 IRXRX3 I Integer table ID for RXRX values

81 IRXRY3 I Integer table ID for RXRY values

82 IRYRX3 I Integer table ID for RYRX values

83 IRYRY3 I Integer table ID for RYRY values

84 RTXX3 RS Real constant XX value

85 RTXY3 RS Real constant XY value

86 RTYX3 RS Real constant YX value

87 RTYY3 RS Real constant YY value

88 RTXZ3 RS Real constant XZ value

89 RTYZ3 RS Real constant YZ value

90 RTZX3 RS Real constant ZX value

91 RTZY3 RS Real constant ZY value

92 RTZZ3 RS Real constant ZZ value

93 RRXRX3 RS Real constant RXRX value

94 RRXRY3 RS Real constant RXRY value

95 RRYRX3 RS Real constant RYRX value

96 RRYRY3 RS Real constant RYRY value




EPT

New RECORD – DESC(9801,98,698)



2 NWORDS I Number of words for the description string

3 DESC CHAR4 Description

Words 3 repeats NWORDS times

New RECORD – ELAR(9300,93,684)



2 TYPE I Type: 1=TIME, 2=RINELE, 3=RMECHE

3 AC RS Element activation time

4 ACTFLG I Activation time flag

ACTFLG=1

5 AD I Ramp over the remaining subcase time

ACTFLG=2

5 AD RS Activation delta time

6 RC RS Element removal time or removal strain

7 REMFLG I Removal time flag

REMFLG=1

8 RD I Ramp over the remaining subcase time

REMFLG=2

8 RD RS Removal delta time

9 UNDEF(2) None

11 GRPID I GROUP identification number

12 UNDEF(7) RS Stress recovery location at point D in elementz-axis




New RECORD – ELAR2(9400,94,685)



2 TYPE I Type: 1=TIME, 2=RINELE, 3=RMECHE

3 UNDEF(6) None

9 EID I Element identification number

10 AC RS Element activation time

11 ACTFLG I Activation time flag

ACTFLG=1

12 AD I Ramp over the remaining subcase time

ACTFLG=2

12 AD RS Activation delta time

13 RC RS Element removal time or removal strain

14 REMFLG I Removal time flag

REMFLG=1

15 RD I Ramp over the remaining subcase time

REMFLG=2

15 RD RS Removal delta time

16 UNDEF(3) None


New RECORD – ELARADD(9500,95,686)


1 ID I Element add/remove set identification number

2 G1 I Identification number of element add/remove setthat are defined with ELAR and ELAR2 entries





New RECORD – PJOINT(9601,96,691)


1 PID I Property identification number

2 TYPE(2) CHAR4 Joint type: HINGE, SLIDER, PRISM, SPHERE,CYLDR, TWIST, REMLINK, SCREW, UNIVSL,CONVEL

4 KT RS Translational stiffness

5 KR RS Rotational stiffness

6 CF RS Friction coefficient

7 FR0 RS Tightening force for friction computation

8 TOL RS Regularization velocity

9 KCF RS Regularization stiffness

10 LR RS Characteristic length radius

11 LX RS Characteristic length X

12 LY RS Characteristic length Y

13 LZ RS Characteristic length Z

14 LIBL RS Liberation length

15 PITCH RS Screw pitch

16 OPT I Option number

17 UNDEF(9) None

New RECORD – PJOINT2(9701,97,692)



2 TYPE(2) CHAR4 Spring or damper type

4 X1 RS Constant value

5 X1TID I Table identification number for non-linear springor damper

6 SX1TID I Table identification number for time-dependentscaling factor





Words 2 through 6 repeat until -1 occurs

GEOM1

New Record – VATVBULK(6791,67,679)


1 UNIT I FORTRAN unit identification number for ATV OP2 file

2 UNDEF(9) None

GEOM2

Updated RECORD – CPLSTS6(1801,18,986)




3 G(6) I Grid point identification numbers of connectionpoints

9 UNDEF(2) None

11 THETA RS Material property orientation angle or coordinatesystem ID

12 TFLAG I Flag signifying meaning of T(3) values

13 TC(3) RS Membrane thickness of element at corner gridpoints

16 UNDEF(5) None

21 TM(3) RS Membrane thickness of element at mid-side gridpoints

24 UNDEF None

Updated RECORD – CPLSTS8(3601,36,987)








3 G(8) I Grid point identification numbers of connectionpoints

11 THETA RS Material property orientation angle or coordinatesystem ID

12 TFLAG I Flag signifying meaning of T(4) values

13 TC(4) RS Membrane thickness of element at corner gridpoints

17 UNDEF(4) None

21 TM(4) RS Membrane thickness of element at mid-side gridpoints

New RECORD – CJOINT(9301,93,690)




3 G(4) I Grid point identification numbers

7 CID1 I Element coordinate system 1 identificationnumber

8 CID2 I Element coordinate system 2 identificationnumber


10 UNDEF(7) None

GEOM3

Updated Record – PLOADE1(6701,67,978)




3 PA RS Surface traction at grid point GA





4 PB RS Surface traction at grid point GB

5 G(2) I Corner grid point identification numbers

7 THETA RS Angle between surface traction and inward normal

8 PM RS Surface traction at mid-side grid point between GAand GB

New Record – DRIVER(9801,98,695)


1 DID I Driver load identification number


3 TYPE(2) CHAR4 Driver type: FORC, TORQ, DISP, or ROT

5 P RS Driver constant value

6 PTID I Table ID for time-dependent driver value

7 UNDEF(3) None

GEOM4

Updated Record – SPCF(5301,53,35)

The record ID changes from (9401,94,9028)



2 SET1ID I Set identification number of SET1 bulk entry (0 =all grids)

3 SUBC I Subcase number of OUGV1 data (0 = first subcase)

4 UNITNO I Unit number of OUTPUT2 file

5 UNDEF(4) None

New Record – JCON(12101,121,696)


1 JCID I Joint constraint identification number





2 EID I Joint element identification number

3 JNTFLAG I Joint flag

JNTFLAG=1

4 TF RS Fixation time

JNTFLAG=2

4 TL RS Liberation time

JNTFLAG=3

4 TT(3) RS Removable link liberation times in transition

JNTFLAG=4

4 TR(3) RS Removable link liberation times in rotation

JNTFLAG=5

4 T6(6) RS Removable link liberation times in transition androtation

End JNTFLAG

New Record – JCONADD(12201,122,697)



2 JCID I Joint constraint identification number

Word 2 repeats until End of Record

Removed Records

The following obsolete records are removed:

SPCDE(8701,87,9021)

SPCDF(8901,89,9023)

SPCDG(9701,97,9030)

SPCE(9301,93,9027)

SPCEB(9101,91,9025)




SPCFB(9201,92,9026)

SPCGB(9601,96,9029)

SPCGRID(8601,86,9031)

GEOM4705

Updated Record – SPCF(5301,53,35)

The record ID changes from (9401,94,9028)



2 SET1ID I Set identification number of SET1 bulk entry (0 =all grids)

3 SUBC I Subcase number of OUGV1 data (0 = first subcase)

4 UNITNO I Unit number of OUTPUT2 file

5 UNDEF(4) None

Removed Records

The following obsolete records are removed:

SPCDE(8701,87,9021)

SPCDF(8901,89,9023)

SPCDG(9701,97,9030)

SPCE(9301,93,9027)

SPCEB(9101,91,9025)

SPCFB(9201,92,9026)

SPCGB(9601,96,9029)

SPCGRID(8601,86,9031)

MPT

New Record – ACTEMP(9203,92,89)


1 ID I Identification number for ACTEMP





2 R RS Gas constant

3 GAMMA RS Isentropic expansion factor

4 PRESSURE RS Constant pressure

5 UNIT I Unit number of file that contains node-basedacoustic fluid parameters

6 DATACODE I Specifies the data to read from the file

7 TID1 I Table ID on input unit for first acoustic property

8 TID2 I Table ID on input unit for second acoustic property

Removed Records

The following records are removed:

NLARCL(1308,13,663)

NLCNTL(1203,12,617)

TSTEP1(17500,175,618)

OBC

Updated Record – IDENT


...... ...... ...... ......

12 PID I Physical property

13 UNDEF(15) None

28 BLTSEQID I Bolt sequence number for SOL 401 preloadedbolts

29 UNDEF(22) None

51 TITLE(32) CHAR4 Title

...... ...... ...... ......




OBG



...... ...... ...... ......


13 UNDEF(15) None


29 UNDEF(22) None


...... ...... ...... ......

OBOLT



...... ...... ...... ......

19 UNDEF(9) None


29 UNDEF(22) None

...... ...... ...... ......

Updated Record – DATA


1 EKEY I Device code + 10 * bolt element identificationnumber

NUMWDE = 7 3D solid element or 1D beam/bar element

2 AX RS Axial force in bolt coordinate system

...... ...... ...... ......




OCKGAP1



...... ...... ....... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

OCONST



...... ...... ...... ......


13 UNDEF(15) None


29 UNDEF(22) None


...... ...... ...... ......

ODAMGCZD

Updated Record - IDENT


...... ...... ...... ......

8 UNDEF(20) None

28 BLTSEQID I Bolt sequence number for SOL 401preloaded bolts





29 UNDEF(22) None

...... ...... ...... ......

ODAMGCZR



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

ODAMGCZT



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

ODAMGPFD

Table of damage values for ply failure for SOL 401

Damage values at corner grids on middle, and the values are unitless.



...... ...... ...... ......





11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

ODAMGPFE



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

ODAMGPFR



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......




ODAMGPFS



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

OEF



...... ...... ...... ......


29 UNDEF(22) None

...... ...... ...... ......

OERR



...... ...... ...... ......

13 UNDEF(15) None


29 UNDEF(22) None

...... ...... ...... ......




OES



...... ...... ...... ......


29 UNDEF(23) None

...... ...... ...... ......

Updated Record - DATA

Note

For the following element types, complex stress and strain are added.

ELTYPE =300 HEXA element (CHEXA)

SCODE,6=0 Strain

TCODE,7=0 Real

2 CID I Coordinate System

3 CTYPE CHAR4 Grid or Gauss

4 GRID I Corner grid ID

5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z

8 EXY RS Strain in XY

9 EYZ RS Strain in YZ

10 EZX RS Strain in ZX

11 EVM RS Von Mises strain

Words 4 through 11 repeat 8 times.

TCODE,7=1 Real/Imaginary






4 GRID I External grid ID

5 EXR RS Strain in X

6 EYR RS Strain in Y

7 EZR RS Strain in Z

8 ETXYR RS Strain in XY

9 ETYZR RS Strain in YZ

10 ETZXR RS Strain in ZX

11 EXI RS Strain in X

12 EYI RS Strain in Y

13 EZI RS Strain in Z

14 ETXYI RS Strain in XY

15 ETYZI RS Strain in YZ

16 ETZXI RS Strain in ZX



End TCODE,7

SCODE,6=1 Stress

TCODE,7=0 Real




5 SX RS Stress in X

6 SY RS Stress in Y

7 SZ RS Stress in Z

8 SXY RS Stress in XY

9 SYZ RS Stress in YZ

10 SZX RS Stress in ZX




11 SVM RS Von Mises stress






5 SXR RS Stress in X

6 SYR RS Stress in Y

7 SZR RS Stress in Z

8 TXYR RS Stress in XY

9 TYZR RS Stress in YZ

10 TZXR RS Stress in ZX

11 SXI RS Stress in X

12 SYI RS Stress in Y

13 SZI RS Stress in Z

14 TXYI RS Stress in XY

15 TYZI RS Stress in YZ

16 TZXI RS Stress in ZX



End TCODE,7

End SCODE,6

ELTYPE =301 PENTA element (CPENTA )

SCODE,6=0 Strain

TCODE,7=0 Real







5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z
























End TCODE,7




SCODE,6=1 Stress

TCODE,7=0 Real




5 SX RS Stress in X

6 SY RS Stress in Y

7 SZ RS Stress in Z



























End TCODE,7

End SCODE,6

ELTYPE =302 TETRA element (CTETRA)

SCODE,6=0 Strain

TCODE,7=0 Real




5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z



























End TCODE,7

SCODE,6=1 Stress

TCODE,7=0 Real




5 SX RS Stress in X

6 SY RS Stress in Y

7 SZ RS Stress in Z



























End TCODE,7

End SCODE,6

ELTYPE =303 PYRAM element (CPYRAM)

SCODE,6=0 Strain

TCODE,7=0 Real




5 EX RS Strain in X

6 EY RS Strain in Y

7 EZ RS Strain in Z



























End TCODE,7

SCODE,6=1 Stress

TCODE,7=0 Real




5 SX RS Stress in X




6 SY RS Stress in Y

7 SZ RS Stress in Z
























End TCODE,7

End SCODE,6




ELTYPE =306 Nonlinear composite HEXA element (CHEXALN)

SCODE,6=0 Strain

TCODE,7=0 Real

1 PLY I Lamina number

2 FLOC CHAR4 Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID (center=0)

4 EX1 RS Normal strain in the 1-direction

5 EY1 RS Normal strain in the 2-direction

6 EZ1 RS Normal strain in the 3-direction

7 ET1 RS Shear strain in the 12-plane

8 EL2 RS Shear strain in the 23-plane


10 ETMAX1 RS von Mises strain

For each fiber location requested (PLSLOC), words 3 through 10 repeat 4 times.



2 FLOC I Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID

4 EX1R RS Normal strain in the 1-direction

5 EY1R RS Normal strain in the 2-direction

6 EZ1R RS Normal strain in the 3-direction

7 ET1R RS Shear strain in the 12-plane

8 EL2R RS Shear strain in the 23-plane


10 EX1I RS Normal strain in the 1-direction

11 EY1I RS Normal strain in the 2-direction

12 EZ1I RS Normal strain in the 3-direction




13 ET1I RS Shear strain in the 12-plane

14 EL2I RS Shear strain in the 23-plane




End TCODE,7

SCODE,6=1 Stress

TCODE,7=0 Real




4 SX1 RS Normal stress in the 1-direction

5 SY1 RS Normal stress in the 2-direction

6 SZ1 RS Normal stress in the 3-direction

7 ST1 RS Shear stress in the 12-plane

8 SL2 RS Shear stress in the 23-plane


10 STMAX1 RS von Mises stress



4 SX1R RS Normal stress in the 1-direction

5 SY1R RS Normal stress in the 2-direction

6 SZ1R RS Normal stress in the 3-direction

7 ST1R RS Shear stress in the 12-plane

8 SL2R RS Shear stress in the 23-plane





10 SX1I RS Normal stress in the 1-direction

11 SY1I RS Normal stress in the 2-direction

12 SZ1I RS Normal stress in the 3-direction

13 ST1I RS Shear stress in the 12-plane

14 SL2I RS Shear stress in the 23-plane




End TCODE,7

End SCODE,6

ELTYPE =307 Nonlinear composite PENTA element (CPENTALN)

SCODE,6=0 Strain

TCODE,7=0 Real




4 EX1 RS Normal strain in the 1-direction

5 EY1 RS Normal strain in the 2-direction

6 EZ1 RS Normal strain in the 3-direction

7 ET1 RS Shear strain in the 12-plane










2 FLOC I Fiber location (BOT, MID, TOP)

3 GRID I Edge grid ID

4 EX1R RS Normal strain in the 1-direction

5 EY1R RS Normal strain in the 2-direction

6 EZ1R RS Normal strain in the 3-direction

7 ET1R RS Shear strain in the 12-plane



10 EX1I RS Normal strain in the 1-direction

11 EY1I RS Normal strain in the 2-direction

12 EZ1I RS Normal strain in the 3-direction

13 ET1I RS Shear strain in the 12-plane





End TCODE,7

SCODE,6=1 Stress

TCODE,7=0 Real




4 SX1 RS Normal stress in the 1-direction

5 SY1 RS Normal stress in the 2-direction

6 SZ1 RS Normal stress in the 3-direction

7 ST1 RS Shear stress in the 12-plane









4 SX1R RS Normal stress in the 1-direction

5 SY1R RS Normal stress in the 2-direction

6 SZ1R RS Normal stress in the 3-direction

7 ST1R RS Shear stress in the 12-plane



10 SX1I RS Normal stress in the 1-direction

11 SY1I RS Normal stress in the 2-direction

12 SZ1I RS Normal stress in the 3-direction

13 ST1I RS Shear stress in the 12-plane





End TCODE,7

End SCODE,6

ELTYPE =312 Axisymmetric tria element (TRAX3)

SCODE,6=0 Strain

TCODE,7=0 Real

1 THETA RS Material orientation angle






4 EX RS Normal strain in the X-direction

5 EY RS Normal strain in the Y-direction

6 EZ RS Normal strain in the Z-direction

7 EXY RS Shear strain in the XY-plane

8 EYZ RS Shear strain in the YZ-plane

9 EZX RS Shear strain in the ZX-plane

10 EVM RS von Mises strain






4 EXR RS Normal strain in the X-direction

5 EYR RS Normal strain in the Y-direction

6 EZR RS Normal strain in the Z-direction

7 ETXYR RS Shear strain in the XY-plane

8 ETYZR RS Shear strain in the YZ-plane

9 ETZXR RS Shear strain in the ZX-plane

10 EXI RS Normal strain in the X-direction

11 EYI RS Normal strain in the Y-direction

12 EZI RS Normal strain in the Z-direction

13 ETXYI RS Shear strain in the XY-plane

14 ETYZI RS Shear strain in the YZ-plane

15 ETZXI RS Shear strain in the ZX-plane



End TCODE,7




SCODE,6=1 Stress

TCODE,7=0 Real




4 SX RS Normal stress in the X-direction

5 SY RS Normal stress in the Y-direction

6 SZ RS Normal stress in the Z-direction

7 SXY RS Shear stress in the XY-plane

8 SYZ RS Shear stress in the YZ-plane

9 SZX RS Shear stress in the ZX-plane

10 SVM RS von Mises stress






4 SXR RS Normal stress in the X-direction

5 SYR RS Normal stress in the Y-direction

6 SZR RS Normal stress in the Z-direction

7 TXYR RS Shear stress in the XY-plane

8 TYZR RS Shear stress in the YZ-plane

9 TZXR RS Shear stress in the ZX-plane

10 SXI RS Normal stress in the X-direction

11 SYI RS Normal stress in the Y-direction

12 SZI RS Normal stress in the Z-direction

13 TXYI RS Shear stress in the XY-plane

14 TYZI RS Shear stress in the YZ-plane




15 TZXI RS Shear stress in the ZX-plane



End TCODE,7

End SCODE,6

ELTYPE =313 Axisymmetric quad element (QUADX4)

SCODE,6=0 Strain

TCODE,7=0 Real

































End TCODE,7

SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =314 Axisymmetric tria element (TRAX6)

SCODE,6=0 Strain

TCODE,7=0 Real

































End TCODE,7

SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7




End SCODE,6

ELTYPE =315 Axisymmetric quad element (QUADX8)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =316 Plane strain tria element (PLSTN3)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =317 Plane strain quad element (PLSTN4)

SCODE,6=0 Strain

TCODE,7=0 Real





SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =318 Plane strain tria element (PLSTN6)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =319 Plane strain quad element (PLSTN8)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6




ELTYPE =320 Plane stress tria element (PLSTS3)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =321 Plane stress quad element (PLSTS4)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =322 Plane stress tria element (PLSTS6)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress




TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =323 Plane stress quad element (PLSTS8)

SCODE,6=0 Strain

TCODE,7=0 Real

































SCODE,6=1 Stress

TCODE,7=0 Real

































End TCODE,7

End SCODE,6

ELTYPE =343 Shell triangular element (TRIA6)

SCODE,6=0 Strain

TCODE,7=0 Real

1 THETA RS



4 FD1 RS Fiber distance at z1

5 EX1 RS Normal strain in the X-direction

6 EY1 RS Normal strain in the Y-direction

7 EZ1 RS Normal strain in the Z-direction

8 EXY1 RS Shear strain in the XY-plane




9 EYZ1 RS Shear strain in the YZ-plane

10 EZX1 RS Shear strain in the ZX-plane

11 EVM1 RS von Mises strain











1 THETA RS




5 EX1R RS Normal strain in the X-direction

6 EY1R RS Normal strain in the Y-direction

7 EZ1R RS Normal strain in the Z-direction

8 ETXY1R RS Shear strain in the XY-plane

9 ETYZ1R RS Shear strain in the YZ-plane

10 ETZX1R RS Shear strain in the ZX-plane

11 EX1I RS Normal strain in the X-direction

12 EY1I RS Normal strain in the Y-direction

13 EZ1I RS Normal strain in the Z-direction

14 ETXY1I RS Shear strain in the XY-plane

15 ETYZ1I RS Shear strain in the YZ-plane




16 ETZX1I RS Shear strain in the ZX-plane

















SCODE,6=1 Stress

TCODE,7=0 Real



5 SX1 RS Normal stress in the X-direction

6 SY1 RS Normal stress in the Y-direction

7 SZ1 RS Normal stress in the Z-direction

8 SXY1 RS Shear stress in the XY-plane

9 SYZ1 RS Shear stress in the YZ-plane

10 SZX1 RS Shear stress in the ZX-plane

11 SVM1 RS von Mises stress














1 THETA RS




5 SX1R RS Normal stress in the X-direction

6 SY1R RS Normal stress in the Y-direction

7 SZ1R RS Normal stress in the Z-direction

8 TXY1R RS Shear stressin the XY-plane

9 TYZ1R RS Shear stress in the YZ-plane

10 TZX1R RS Shear stress in the ZX-plane

11 SX1I RS Normal stress in the X-direction

12 SY1I RS Normal stress in the Y-direction

13 SZ1I RS Normal stress in the Z-direction

14 TXY1I RS Shear stress in the XY-plane

15 TYZ1I RS Shear stress in the YZ-plane

16 TZX1I RS Shear stress in the ZX-plane









22 TXY2R RS Shear stress in the XY-plane











End TCODE,7

End SCODE,6

ELTYPE =344 Shell quad element (QUAD8)

SCODE,6=0 Strain

TCODE,7=0 Real

1 THETA RS
























1 THETA RS



































SCODE,6=1 Stress

TCODE,7=0 Real























1 THETA RS



































End TCODE,7

End SCODE,6

ELTYPE =345 Shell quad element (QUADR)

SCODE,6=0 Strain

TCODE,7=0 Real

1 THETA RS
























1 THETA RS



































SCODE,6=1 Stress

TCODE,7=0 Real























1 THETA RS



































End TCODE,7

End SCODE,6

ELTYPE =346 Shell triangular element (TRIAR)

SCODE,6=0 Strain

TCODE,7=0 Real

1 THETA RS
























1 THETA RS



































SCODE,6=1 Stress

TCODE,7=0 Real























1 THETA RS



































End TCODE,7

End SCODE,6


ELTYPE =355 Composite triangular shell element (CTRIA6)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1





6 EY1 RS Normal -2

7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z

11 ETMAX1 RS von Mises

Words 4 through 11 repeat 3 times

TCODE,7 =1 Real/Imaginary




5 EX1R RS Normal -1

6 EY1R RS Normal -2

7 EZ1R RS Normal -3

8 ET1R RS Shear-12

9 EL2R RS Shear-2Z

10 EL1R RS Shear-1Z

11 EX1I RS Normal -1

12 EY1I RS Normal -2

13 EZ1I RS Normal -3

14 ET1I RS Shear-12

15 EL2I RS Shear-2Z

16 EL1I RS Shear-1Z



SCODE,6=1 Stress

TCODE,7 =0 Real








5 SX1 RS Normal -1

6 SY1 RS Normal -2

7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z

10 SL1 RS Shear-1Z

11 TMAX1 RS von Mises






5 SX1R RS Normal -1

6 SY1R RS Normal -2

7 SZ1R RS Normal -3

8 ST1R RS Shear-12

9 SL2R RS Shear-2Z

10 SL1R RS Shear-1Z

11 SX1I RS Normal -1

12 SY1I RS Normal -2

13 SZ1I RS Normal -3

14 ST1I RS Shear-12

15 SL2I RS Shear-2Z

16 SL1I RS Shear-1Z







End TCODE,7

End SCODE,6


ELTYPE =356 Composite quadrilateral shell element (CQUAD8)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1

6 EY1 RS Normal -2

7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z







5 EX1R RS Normal -1

6 EY1R RS Normal -2

7 EZ1R RS Normal -3





8 ET1R RS Shear-12

9 EL2R RS Shear-2Z

10 EL1R RS Shear-1Z




14 ET1I RS Shear-12

15 EL2I RS Shear-2Z

16 EL1I RS Shear-1Z



SCODE,6=1 Stress

TCODE,7 =0 Real




5 SX1 RS Normal -1

6 SY1 RS Normal -2

7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z

10 SL1 RS Shear-1Z











5 SX1R RS Normal -1

6 SY1R RS Normal -2

7 SZ1R RS Normal -3

8 ST1R RS Shear-12

9 SL2R RS Shear-2Z

10 SL1R RS Shear-1Z




14 ST1I RS Shear-12

15 SL2I RS Shear-2Z

16 SL1I RS Shear-1Z



End TCODE,7

End SCODE,6


ELTYPE =357 Composite triangular shell element (CTRIAR)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1

6 EY1 RS Normal -2





7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z







5 EX1R RS Normal -1

6 EY1R RS Normal -2

7 EZ1R RS Normal -3

8 ET1R RS Shear-12

9 EL2R RS Shear-2Z

10 EL1R RS Shear-1Z




14 ET1I RS Shear-12

15 EL2I RS Shear-2Z

16 EL1I RS Shear-1Z



SCODE,6=1 Stress

TCODE,7 =0 Real








5 SX1 RS Normal -1

6 SY1 RS Normal -2

7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z

10 SL1 RS Shear-1Z







5 SX1R RS Normal -1

6 SY1R RS Normal -2

7 SZ1R RS Normal -3

8 ST1R RS Shear-12

9 SL2R RS Shear-2Z

10 SL1R RS Shear-1Z




14 ST1I RS Shear-12

15 SL2I RS Shear-2Z

16 SL1I RS Shear-1Z







End TCODE,7

End SCODE,6


ELTYPE =358 Composite quadrilateral shell element (CQUADR)

SCODE,6=0 Strain

TCODE,7 =0 Real




5 EX1 RS Normal -1

6 EY1 RS Normal -2

7 EZ1 RS Normal -3

8 ET1 RS Shear-12

9 EL2 RS Shear-2Z

10 EL1 RS Shear-1Z







5 EX1R RS Normal -1

6 EY1R RS Normal -2

7 EZ1R RS Normal -3

8 ET1R RS Shear-12





9 EL2R RS Shear-2Z

10 EL1R RS Shear-1Z




14 ET1I RS Shear-12

15 EL2I RS Shear-2Z

16 EL1I RS Shear-1Z



SCODE,6=1 Stress

TCODE,7 =0 Real




5 SX1 RS Normal -1

6 SY1 RS Normal -2

7 SZ1 RS Normal -3

8 ST1 RS Shear-12

9 SL2 RS Shear-2Z

10 SL1 RS Shear-1Z











5 SX1R RS Normal -1

6 SY1R RS Normal -2

7 SZ1R RS Normal -3

8 ST1R RS Shear-12

9 SL2R RS Shear-2Z

10 SL1R RS Shear-1Z




14 ST1I RS Shear-12

15 SL2I RS Shear-2Z

16 SL1I RS Shear-1Z



End TCODE,7

End SCODE,6

OGF



...... ...... ...... ......


31 UNDEF(20) None

...... ...... ...... ......




OJINT



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

OPG



...... ...... ...... ......

24 UNDEF(4 ) None


29 UNDEF(22) None

...... ...... ...... ......

OPRESS



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ....... ...... ......




OQG



...... ...... ...... ......


29 UNDEF(22) None

...... ...... ...... ......

OSLIDE



...... ...... ...... ......

13 UNDEF(15) None


29 UNDEF(22) None

...... ...... ...... ......

OSPDS



...... ...... ...... ......

13 UNDEF(15) None


29 UNDEF(22) None

...... ...... ...... ......




OTEMP



...... ...... ...... ......

11 UNDEF(17) None


29 UNDEF(22) None

...... ...... ...... ......

OUG



...... ...... ...... ......


29 UNDEF(22) None

...... ...... ...... ......

OUMAT



...... ...... ...... ......

12 UNDEF(16) None


29 UNDEF(22) None

...... ...... ...... ......




Updated Record – DATA

Support for CBEAM element


ELTYPE = 2 CBEAM

2 EID I Element ID

3 MATID I Material ID

4 NVPG I Number of values per grid

5 GRID I Grid point

6 SVIC I State variable index at point C

7 SVVC RS State variable value at point C

Words 6 and 7 repeat until (-1,-1) occurs

8 SVID I State variable index at point D

9 SVVD RS State variable value at point D


10 SVIE I State variable index at point E

11 SVVE RS State variable value at point E


12 SVIF I State variable index at point F

13 SVVF RS State variable value at point F



Support for CBAR element


ELTYPE = 34 CBAR

2 EID I Element ID

3 MATID I Material ID

4 NVPG I Number of values per grid





5 GRID I Grid point

6 SVIC I State variable index at point C

7 SVVC RS State variable value at point C


8 SVID I State variable index at point D

9 SVVD RS State variable value at point D


10 SVIE I State variable index at point E

11 SVVE RS State variable value at point E


12 SVIF I State variable index at point F

13 SVVF RS State variable value at point F



New data blocks

OACPERF

Performance data that indicates computation time in seconds and memory consumed in GB perfrequency per subcase for FEMAO analysis.

Record - HEADER


1 NAME(2) CHAR4 Data block name

3 Word I No Def or Month, Year, One, One





Record - IDENT


1 UNDEF(50) None

51 TITLE(32) CHAR4 Title character string (TITLE)

83 SUBTITLE(32) CHAR4 Subtitle character string (SUBTITLE)

115 LABEL(32) CHAR4 LABEL character string (LABEL)

Record - DATA


1 NFREQ I Number of frequencies

2 FREQ RS Frequency

3 TIME I Computation time per frequency in seconds

4 MEMORY RS Memory per frequency in GB


Record - TRAILER


1 NUMREC I Number of records

2 UNDEF(5) None

ODMTRCOE

Acoustic duct mode transmission loss

Record - HEADER



Record - IDENT


1 ACODE(C) I Device code + 10*Approach code





2 TCODE(C) I Table code = 95

3 UNDEF None

4 SUBCAS I Subcase identification number

5 FREQ RS Frequency (Hz)

6 ID I Identification number of PACDUCT

7 DID I DID of DESC

8 UNUSED None

9 FCODE(C) I Format code

10 NUMWDE(C) I Number of words per entry in DATA record= 6

11 UNDEF(40) None




Record - DATA


1 MODX I Mode number in X-direction

2 MODY I Mode number in X-direction

3 PRESR RS Real part of transmission coefficient in pressure

4 PRESI RS Imaginary part of transmission coefficient inpressure

5 INTEN RS Transmission coefficient in intensity

6 POWER RS Transmission coefficient in power

Record - TRAILER







2 UNDEF(5) None

ODMTRLS

Acoustic duct mode transmission loss in SORT 1 and SORT 2 format

Record - HEADER



Record - IDENT



2 TCODE(C) I Table code = 96

3 UNDEF None

4 SUBCAS I Subcase identification number

TCODE,1=1 SORT 1


TCODE,1=2 SORT 2

5 ISID I Identification number for duct modetransmission loss

End TCODE,1

6 UNUSED(3) None


10 NUMWDE(C) I Number of words per entry in DATA record= 6

11 UNDEF(40) None







Record - DATA


TCODE,1=1 SORT 1

1 ISID I FACES/GROUP identification number forincident power

TCODE,1=2 SORT 2


End TCODE,1

2 TRLOS RS Transmission loss

Record - TRAILER



2 UNDEF(5) None

OELAR

Element status (active or inactive)

Record - HEADER





Record - IDENT



2 TCODE(C) I Table code

3 UNDEF None

4 SUBCAS I Subcase or random identification number





5 TIME RS Current solution time

6 UNUSED(3) None


10 NUMWDE(C) I Number of words per entry in DATA record

11 UNDEF(40) None




Record - DATA


1 EID I Element identification number*10+devicecode

2 FLGAR I Flag of pre-born or removed element:0=pre-born, 1=removed

3 DTIM RS Activate time for pre-born element ordeactivate time for removed element

Record - TRAILER


1 UNDEF(6) None

RST

Table of restart subcase and time step for SOL 401 and 402 when performing STATICS, DYNAMIC,and PRELOAD analysis types. MODES, CYCMODES, and FOURIER are not supported.

Record - HEADER









Record - IDENT


1 SOLTYPE I 401 or 402

2 OFSTFLG I Offset flag for 401

3 MASSNEWM I MASS matrix update flag for 401

4 BLTNUM I Bolt type number; 0 for no bolt

5 BLTSEQID I Bolt sequence identification number

6 PBCONV I Parameter for preload bolt

7 ANAL(2) CHAR4 ANALYSIS card

8 DLDPREV I DLOAD of previous run

9 LDPREV I LOAD of previous run

10 CNTLOOP I Parameter for CONTACT loop

11 CNTUPDT I Parameter for CONTACT update

12 NEWBCSET I Parameter for new CONTACT set

13 MSCHG I Parameter for preload

14 UNDEF(132) None

Record - CHECKPT


1 SUBCASE I Subcase identification number

2 NSTEP I Current time step position for subcase

3 TIME RS Time step that can be used for restart

4 DESCRP(128) CHAR4 Description






Record - TRAILER


1 UNDEF(6) None

VATVMAP

VATV matrix row and column mapping vector.

Record 0 – HEADER



Record 1 – ROWMAP


1 EXID I Microphone point external ID


Record 2 – COLMAP


1 EXID I Structural grid external ID


Record 5 – TRAILER


1 NROW I Number of rows in VATV matrix

2 NCOL I Number of columns in VATV matrix

3 UNDEF(4) None




Updated modules

BDRYINFO

Updated Format:

BDRYINFO CASECC,GEOM1,GEOM2,BGPDT,GPDT,USET,EQEXIN,GPECT,EST,ECT,KDICT,MDICT,BDICT/GEOM1EX,GEOM2EX,GEOM4EX,CASEX,USETX,EQEXINX,BGPDTX,GPECTX,ESTX,ECTX,KDICTX,MDICTX,BDICTX/NOQSET/NOMATK/NOMATM/NOMATB/NOMATKY/NOMATA/NOMATP/DMIGSFIX $

New Parameter:

NOMATA Input-integer-default= -1. Acoustic area matrix existence flag.

-1 Does not exist

0 Empty

1 Exists

CONSTF

Updated Format:

CONSTF CNELM,BGPDT,CSTM,UGCB,ECSTAT,TLAMDA,UGCD,PLAMDA,ELSLIP,OFFSETP,DLAMDA,ADJUST,DITS,CNTRSTP,NODTEMPI/KELMC,KDICTC,ECSTAT,TLAMDA,ELAMDA,DLAMDA/GSIZE/LGDISP/IOPT/CNTNINC/DELTIME/CITO/SCINIT/SCENDT/RSTIME/CNTNSUB/CNTSTPS/ANAI/CITI/GEOMUPDT/AUGLOOP/ISOLVER $

New Input Data Blocks:

ADJUST Contact region adjustment data block

DITS Table of TABLEij bulk entry images

CNTRSTP Restart data

NODTEMPI Nodal temperatures for variation of friction coefficient with respect to temperature

New Output Data Blocks:

ECSTAT Contact status

TLAMDA Total tractions

ELAMDA Not used




DLAMDA Augmented component of the tractions

New Parameters:

CITI Input-integer-no default. Contact iteration identification number

GEOMUPDT Input-integer-no default. Geometry update flag

AUGLOOP Input-integer-no default. Augmentation loop identification number

ISOLVER Input-integer-default=1. ISOLVER=1 for direct solvers. ISOLVER=2 for elementiterative solvers.

CONTOUT

Updated Format:

CONTOUT CNELM,ECDISP,CASESX2H,ECSTAT,ECDISD,BGPDT,CNTPENTR,UGC,ISLIP,TFSLIP/OSPDS1,OSLIDE1,OCONST1/NVEC/DMAPNO/RSTIME/LGDISP/ANAI/LDFACAL/ARCLNTH/BLTSEQID $

New Parameter:

BLTSEQID Input-integer-default=0. Bolt sequence identification number used to populateoutput data blocks for SOL 401 bolt sequence workflows

DOPR1

Updated Format:

DOPR1EDOM,EPT,DEQATN,DEQIND,GEOM2,MPT,CASEXX,DIT,EDT,CONELS,ECT,BGPDT/DESTAB,XZ,DXDXI,DTB,DVPTAB*,EPTTAB*,CONSBL*,DPLDXI*,PLIST2*,XINIT,PROPI*,DSCREN,DTOS2J*,OPTPRM,CONS1T,DBMLIB,BCON0,BCONXI,DMATCK,DISTAB,CASETM,SPAN23,MFRDEP,DESVUP,EDOMNU,GEOM2N,ECTNU,EPTNU,CONTEL,MPTNU,DLKCON/S,N,MODEPT/S,N,MODGEOM2/S,N,MODMPT/DPEPS/S,N,PROTYP/S,N,DISVAR/S,N,IDVTRL/NASPRT/INREL $

New Parameter:

INREL Input-integer-no default. Parameter controlling the calculation of inertia relief.For more information, see the INREL parameter in the Simcenter NastranQuick Reference Guide.




DOPR3

Updated Format:

DOPR3 CASE,EDOMS,DTB,ECT,EPT,DESTAB,EDT,FRLF,DEQIND,DEQATN,DESGID,DVPTAB,VIEWTB,OINT,PELSET,DFRFNC,TSPAN23,DIT,EDOM/OBJTAB,CONTAB,R1TAB,RESP12,RSP1CT,FRQRSP,CASEDS,OINTDS,PELSETDS,DESELM,RESP3,TNSPAN23,SPAN1RG,FRLTMP/DMRESD/S,N,DESGLB/S,N,DESOBJ/S,N,R1CNT/S,N,R2CNT/S,N,CNCNT/SOLAPP/SEID/S,N,EIGNFREQ/PROTYP/DSNOKD/SHAPES/S,N,R3CNT/PRESENS3/INREL $

New Parameter:

INREL Input-integer-no default. Parameter controlling the calculation of inertia relief.For more information, see the INREL parameter in the Simcenter Nastran QuickReference Guide.

DSAD

Updated Format:

DSAD RSPCSC,R1TCSC,R12CSC,OBJCSC,CONCSC,BLAMA,LAMA,CLAMA,DIVTAB,AUXTAB,STBTAB,FLUTAB,OUG1DS,OES1DS,OSTR1DS,OEF1DS,OEFITDS,OES1CDS,OSTR1CDS,OQG1DS,DSCREN,XINIT,COORDN,OL,FRQRSP,CASEER,CASERS,UGX,OPTPRM,DVPTAB*,PROPI*,BGPDT,DNODEL,WGTM,ONRGYDS,GLBTABDS,GLBRSPDS,R3CSC,RMSTAB,RMSVAL,SPAN1RG,OUGPSD1,DYNAMICS,SABFIL,OERP200,OERPEL0,ERPFIL*,EST,CSTM,PCOMPT,GPSNT,DIT,DITID,MPT/R1VAL,R2VAL,RSP2R,R2VALR,CVAL,CVALR,OBJTBR,CNTABR,R1TABR,R1VALR,DRSTBL,FRQRPR,UGX1,AUG1,R1MAPR,R2MAPR,CASDSN,CASDSX,DRDUG,DRDUTB,CASADJ,LCDVEC,RR2IDR,R3VAL,R3VALR,RESP3R,RMSTABR,RMSVALR,SPANSV,SPANSVG/WGTS/VOLS/S,N,OBJVAL/S,N,NR1OFFST/S,N,NR2OFFST/S,N,NCNOFFST/APP/DMRESD/SEID/DESITER/EIGNFREQ/S,N,ADJFLG/PEXIST/MBCFLG/RGSENS/PROTYP/AUTOADJ/FSDCYC/S,N,NR3OFFST/INREL/K6ROT/S,N,ADJSTR $


EST Element summary table.




CSTM Table of coordinate system transformation matrices.

PCOMPT Table containing LAM option input and expanded information from the PCOMPbulk entry.

GPSNT Grid point shell normal table.

DIT Table of TABLEij bulk entry images.

DITID Table of identification numbers in DIT.

MPT Table of bulk entry images related to material properties.

New Parameters:

K6ROT Input-real-default=0.0. Specifies the stiffness to be added to the normal rotationfor CQUAD4 and CTRIA3 elements.

ADJSTR Output-integer-default=0. Indicates which load method is used for stress

=0 for the legacy psuedo-load method

=1 for the adjoint load method

DSAF

Updated Format:

DSAF R1TABR,EST,ESTDV2,TABEV2,ETT,MIDLIS,KELM,KDICT,PTELEM,KELMDS,KDICTDS,PTELMDSX,ECT,VELEM,VELEMN/ESTDCN,TABECN,ETTDCN,KELMDCN,KDICTDCN,PTELMDCN,VELEMDCN,ESTDCNA,TABECNA/NDVTOT/PESE $


ESTDCNA Same as ESTDCN, but without unperturbed elements. For use with adjoint loadsfor stresses. Exists based on ADJSTR (see the DSAD module)

TABECNA Same as TABECN, but without unperturbed elements. For use with adjoint loadsfor stresses. Exists based on ADJSTR (see the DSAD module)




DSAL

Updated Format:

DSAL DRSTBL,DELWS,DELVS,DELB1,DELF1,COGRID,COELEM,OUGDSN,OESDSN,OSTRDSN,OEFDSN,OEFITDSN,OESCDSN,OSTRCDSN,R1VALR,OQGDSN,ONRGYDSN,TABDEQ,OL,DSDIV,DELX,DELS,DELFL,DELCE,FRQRPR,DELBSH,DRDUTB,ADELX,R1TABR,DRMSVL,TABECNA/DSCM/NDVTOT/DELTAB/EIGNFREQ/ADJFLG/SEID $

New Output Data Block:

TABECNA Table of relationship between internal identification numbers of constraints inESTDCNA (see DSAF module) and elements and responses in R1TABR, butwithout unperturbed elements. For use with adjoint loads for stresses. Existsbased on ADJSTR (see DSAD module)

EMG

Updated Format:

EMG EST,CSTM,MPT,DIT,CASECC,UG,ETT,EDT,DEQATN,DEQIND,BGPDT,GPSNT,ECTA,EPTA,EHTA,DITID,EBOLT,COMPEST,EFILL,PCOMPT,EPT,CMPGEST,ELAREST/KELM,KDICT,MELM,MDICT,BELM,BDICT,ELMMOD,CONFAC2/S,N,NOKGG/S,N,NOMGG/S,N,NOBGG/S,N,NOK4GG/S,N,NONLHT/COUPMASS/TEMPSID/DEFRMSID/PENFAC/IGAPS/LUMPD/LUMPM/MATCPX/KDGEN/TABS/SIGMA/K6ROT/LANGLE/NOBKGG/ALTSHAPE/PEXIST/FREQTYP/FREQVAL/FREQWA/UNSYMF/S,N,BADMESH/DMGCHK/BOLTFACT/REDMAS/TORSIN/SHLDAMP/SHLDMP/BSHDMP/LMSTAT/LMDYN/STFOPTN/MODOPTN/HINDEX/HOOPDOF/ISPCSTR $

New Input Data Block:

ELAREST Element add/remove information summary table

FEMAOAC

Updated Format:

FEMAOAC BGPDTS,CASEALL,CONTACT,CSTMS,DITS,DLT,DYNAMIC,ECTS,EDTS,EPT,EQEXINS,FRL,FOL,GEOM4S,FEMAOMAT,,,,,,,,MPT,PDFTAB,SILS,USETD,UDFTAB,SYSVEC,DOFASET,DOFSTR,UGSTAB,PGSTAB/UGFAO,VELAO,INTAO,XACPWRT2,XACPWRI2,XACPWR2,XACTRLS2,UDSAO,XDMTRCOL1,XDMTRLS1,XUGPC1,,,OACPERF,OUXY,XUGMC1,PTMIC,VATV,VECNORM/IERR/ATVUSE $





XDMTRCOL1 Data block of duct modes transmission coefficients in SORT1 format

XDMTRLS1 Data block of duct modes transmission loss in SORT1 format

XUGPC1 Data block of panel contribution coefficients in SORT1 format

OACPERF Performance data indicating computation time per frequency in seconds andmemory consumed in GB per frequency in FEMAO analysis

OUXY SDISPLACEMENT output

XUGMC1 Data block of modal contribution coefficients in SORT1 format

PTMIC Table of the property of VATV microphone points

VATV VATV matrix

VECNORM Table of vector norm of VATV structural grids

New Parameter:

ATVUSE Input-integer-default=0. ATVUSE flag. If ATVUSE=2, VATV matrix is computed

FEMAOPRE

Updated Format for Strongly-Coupled Vibro-Acoustic SOL 108 FEMAO Solution:

FEMAOPRE BGPDTS,CASEF,EQEXINS,DOFVEC,FOL,UDF,PDF,UGS,PGS,CKDD,CMDD,CBDD,CK4DD,SCALEFAC,VGFS/DOFASET,DOFSTR,SYSVEC,UDFTAB,PDFTAB,UGSTAB,PGSTAB,FEMAOMAT/IERR/NOASET/NOGSET//FREQDEP/YSFLAG $

Updated Format for Weakly-Coupled SOL 108 FEMAO Solution:

FEMAOPRE BGPDTS,CASEF,EQEXINS,DOFVEC,FOL,UDF,PDF,UGS,PGS,,,,,,,VGFS/DOFASET,DOFSTR,SYSVEC,UDFTAB,PDFTAB,UGSTAB,PGSTAB,/IERR/NOASET/NOGSET//FREQDEP/YSFLAG $


VGFS Fluid/structure partitioning vector




FEMAOPST

Updated Format:

FEMAOPST CASEF,UGFAO,VELAO,INTAO,UNUSED,XACPWRT2,XACPWRI2,XACPWR2,XACTRLS2,XDMTRCO1,XDMTRLS1,XUGPC1,,XUGMC1,/OUGF1,OACVELO1,OACINT1,UNUSED,OACPWRT2,OACPWRI2,OACPWR2,OACTRLS2,ODMTRCO1,ODMTRLS1,OUGPC1,,OUGMC1,/IERR/NOASET/NOSORTPC//NOSORTMC $


VGFS Fluid/structure partitioning vector

FOCOEL

Updated Format:

FOCOEL CASECC,BGPDT,CSTM,GEOM2,EST,MPT,CONTACT,SIL,GPSNTC,UGCB,GEOM4,FEPEN,UGCP,ELMMOD/CNELM,GPECTC,SPCCY/NSKIP/OPTION/NLHEAT/GSIZE/S,N,REFOPT/S,N,CNTSET/S,N,NCELS/S,N,MAXO/S,N,MAXI/CNTS/S,N,AITK/S,N,MPLI/S,N,RESET/S,N,FRICTM////S,N,CTOL/CNTLOOP/LGDISP/S,N,NSEGCYC/S,N,CYCAXID/FSYMTOL/NEWBCSET $

New Parameter:

NEWBCSET Input-real-default=0.

= -1 contact set has NOT changed – 1st subcase 1st pass

= 0 contact set has NOT changed

= 1 contact set has changed

FONOTR

Updated Format:

FONOTR CNELM,ECSTAT,ELAMDA,CASESX/OQGCFF1,OBC1,CONFON,ELTRCT/NROW/NVEC/DMAPNO/RSTIME/LGDISP/FLAG/ANAI/LDFACAL/ARCLNTH/BLTSEQID $

New Parameter:

BLTSEQID Input-integer-dafault=0. Bolt sequence number




FRFIN

Updated Format:

FRFIN DYNAMIC,EQEXIN,DIT/O1,O2,O3,O4/FREQVAL/P2/FRFID/P4/P5/P6/P7/P8/P9/S,N,FOUND/PHSOPT $

New Parameter:

PHSOPT Input-integer-default=0. Phase interpolation option: 0 for shortest arc length; 1for forward phase.

FRLG

Updated Format:

FRLG CASECC,USETD,DLT,FRL,GMD,GOD,DIT,PHDH,DISTL,BGPDT,CSTM,EDT/PPF,PSF,PDF,FOL,PHF,YPF/SOLTYP/OPT/S,N,FOURIER/S,N,APP/UNITS $


DISTL DTI,DISTL description table

BGPDT Basic grid point definition table

CSTM Coordinate system transformation matrices

EDT Element data table

Updated Parameter:

APP Output-character-default=‘FREQ’. Dynamic load type. Set to ‘FREQ‘, if RLOAD1,RLOAD2, or RLOADEX entries are referenced. Set to ‘TRAN‘, if TLOAD1 orTLOAD2 entries are referenced.

New Parameter:

UNITS Input-character-default=' '. Units string.

FRLGAC

Updated Format:

FRLGAC CASECC,USETD,FRL,MICLOC,DIT,FOL,CONTACT/PGFAC,PIGFAC,PTMIC $





CONTACT Table of bulk entries related to surface contact

FRLGEN

Updated Format:

FRLGEN DYNAMIC,LAMAS,LAMAF,FOL/FRL,FRL1,DFFDNF/S,N,NOFRL/S,N,NOOPT/DFREQ/ATVUSE $


FOL Frequency response frequency output list from VATV computation analysis

New Parameter:

ATVUSE Input-integer-default=0. ATV/VATV analysis flag. If ATVUSE =2, only the FREQVcard and FOL input data block are used

GP3

Updated Format:

GP3 GEOM3,EQEXIN,GEOM2,EDT,UGH,ESTH,BGPDTH,CASEHEAT,CASECC,EPT,GEOM5,CSTMS,DYNAMIC,DISTL/SLT,ETT,CASECCN/S,N,NOLOAD/S,N,NOGRAV/S,N,NOTEMP $


DYNAMIC Table of Bulk Data entry images related to dynamics

DISTL Table of DTI,DISTL Bulk Data entry images

GPAC

Updated Format:

GPAC EQEXIN,BGPDT,GEOM1,SIL,EPT,ECT,MPT,CONTACT,VGF,GPL,GPDT,DIT,CSTM,DYNAMIC,GEOM4,PVT,DISTL,CASECC/VGFO,SILO,EQEXINO,BGPDTO,GPLO,GPDTO,VGFDAML,VGFCG,VGFP,/LUSET/S,N,AMLDOF/SEID/REENTRY//GFL $





DYNAMIC Table of Bulk Data entry images related to dynamics

GEOM4 Table of Bulk Data entry images related to constraints

PVT Sets parameter values

DISTL Direct table input table for RS; Contains the load set labels on DTI Bulk Dataentries

CASECC Table of Case Control images

GPACAO

Updated Format:

GPACAO BGPDT,CSTM,SIL,ECT,EQEXIN,EDT,GEOM2,CASECC,DYNAMIC,EPT,DIT,CONTACT,SYSARR,FRL,GEOM4,MPT,PVT,DISTL,SETMC/OEFMXORD,,OACCQ,,,,,,,/S,N,LUSET/S,N,MATCH/S,N,CTYPE $



DISTL Direct table input table for RS. Contains the load set labels on DTI bulk entries

SETMC Table of SETMC case control commands

GPFDR

Updated Format:

GPFDR CASECC,UG,KELM,KDICT,ECT,EQEXIN,GPECT,PG,QG,BGPDT,{LAMA or FOL or TOL or OLF},CSTM,VELEM,PTELEM,QMG,NFDICT,FENL,MELM,MDICT,BELM,BDICT,MDLIST,LDFACAL,CUMMAL,MFCASE/ONRGY1,OGPFB1,OEKE1,OEDE1/APP/TINY/XFLAG/CYCLIC/WTMASS/S,N,NOSORT2/HINDEX/SCFLAG/CYC_SUBCAS $


MFCASE Frequency-based partitioning matrix for PEAKOUT results




INPUTT4

Updated Format:

INPUTT4 /M1,M2,M3,M4,M5/NMAT/IUNIT/ITAPE/ORGNAM/BIGMAT $

Updated Parameter:

ORGNAM Output-character-no default. Original name of first data block (M1).

MODACC

Updated Parameter Options:

IOPT Input-integer-default=0. Processing options:

0=process OFREQ or OTIME or OMODES.

1=process SOLUTION = set number descriptor for MODCON.

2=process SOLUTION = set number descriptor for PANCON.

3=process SOLUTION = set number descriptor for ERP.

4=process MDLIST. Only valid if APP=‘REIGEN’.

5=process OMODES as a request for pairs of modes rather than individualmodes. Only valid for Fourier modes with a harmonic index > 0 and cyclicmodes with 0 < harmonic index < N/2, where N is the number or repetitionsin the cyclic geometry.

6=process SOLUTION = set number descriptor for GRDCON.

NLTRD3

Updated Format:

NLTRD3CASESX2H,PDT,YS,ELDATAH,KELMNL,KDDL,GMNL,MPTS,DITS,KBDD,DLT1,CSTMS,BGPDT,SILS,USETD,BRDD,MDDDYN,NLFT,KFSNL,MJJ,UNUSED,GPSNTS,DITID,DEQIND,DEQATN,ELGNST,GLUESEQ,COMPEST,KDICTUP,EPT,ECTS,EDT,RGNL,EQEXINS,SLT,KELMUP,GEOM3,GEOM5,ETT,FBSIN,CNELM,ECSTAT,ELSLIP,TLAMDA,UNUSED,EST,GPECT,INITGAUS,UGCP,YS1I,ECDISPG,DLT,KDICTNL,CONFAC2,GEOM1,GEOM2,PVT0,SETMC,OFFSETP,RFRCEI,UNUSED,DLT2,PGT,INOFFGA,CMPGEST,PGBOLT1,SBDATA,ELAREST,ADJUST,LMDD,UMDD,NODTEMPI/ULNTH,IFSH,ESTNLH,IFDH,OES1,PNLH,TELH,MULNT,MESTNL,MESTNL2,UNUSED,PBDATA,OSTR1,OSTR1EL,OSTR1TH,OSTR1PL,OSTR1CR,OES1G,OSTR1G,OSTR1ELG,OSTR1THG,OSTR1PLG,OSTR1CRG,OTEMP1,OES1C,OSTR1C,OSTR1ELC,OSTR1THC,OQGGF1,OBG1,PLPG,FENLR,PLFG,UGLAST,




FBSOUT,TLAMUP,ADGPECT,ADEST,ADSTRES,OERRES,OERREP,OERRSS,OERRSP,CNELMUP,OJINT,ORMN,ELAMUP,YS2F,UDLAST,ESTNLINI,CSDATA,PBDATA,OJINE,CNTPENTR,UMATINL,STATVAR2,OUMAT,OUMATG,ODAMGPFD,ODAMGPFE,ODAMGPFS,ODAMGCZT,ODAMGCZR,ODAMGCZD,OCKGAP1,OCKGAP1G,OBOLT1,UGGPO,OSLIDEG1,DLAMDA,OSTR1PLC,RFRCEF,ECSTATUP,TSLIP,PLPG2,GESTNL,GESTNL2,ESTNLG,ODAMGPFR,OEF1,TRMBD,UNUSED,ELSLIPUP,LDFACAL,ALCUMM,OBCKL,OEFIT,OESRT,OQGCF1,OBC1X,OSPDS1X,OSLIDE1,OCONST1,PSLIP,PLAMDA,BLTSCLDB,PDBT1_OUT,OELAR,CNTRSTP/KRATIO/S,N,CONV/S,N,RSTIME/S,N,NEWP/S,N,NEWDT/S,N,OLDDT/S,N,NSTEP/LGDISP/S,N,ANAL/S,N,ITERID/ITIME/S,N,KTIME/S,N,LASTUPD/S,N,NOGONL/S,N,NBIS/MAXLP/TSTATIC/LANGLE/NDAMP/TABS/S,N,LDFACAL/MATNL/S,N,ARCLNTH/ITERMP/BLTSEQID/GLUE/GPFORCE/BCSET/S,N,CITO/S,N,CITI/S,N,AUGLOOP/S,N,CNVO/S,N,CNTPUPDT/S,N,CONFLAG/S,N,CNTNINC/S,N,BISFLAG/S,N,DTLAST/S,N,CPLFLG/S,N,PBCONV/S,N,CNTUPDT/NCELS/S,N,CRPFLAG/ETYPE/S,N,MESTFLG/RSTMPREV/ENDTIME/S,N,CNTNDIV/K6ROT/S,N,OFSTFLG/MASSNEWM/S,N,LOOPSEQ1/S,N,RSTTIME/INITACCN/STEQSTP/ILSTSBCS/RSTFLAG $


BRDD D-set damping matrix used in ANALYSIS=DYNAMICS

MDDDYN D-set mass matrix used in ANALYSIS=DYNAMICS

KFSNL FS partition of stiffness matrix, used to compute force exerted by applied enforceddisplacements in the first iteration of a time step

MJJ Consistent mass matrix for the g-set

ELAREST Element add/remove information summary table

ADJUST Contact regions adjustment data

LMDD Nonstandard lower triangular factor (L) and diagonal matrix (D) or Cholesky factorfor mass matrix MDDDYN. Generated and used for ANALYSIS=DYNAMICS only

UMDD Upper triangular factor for mass matrix MDDDYN. Generated and used forANALYSIS=DYNAMICS only

NODTEMPI Nodal temperatures used by contact algorithm for variation of friction coefficientwith respect to temperature


ORMN Table of removed nodes by element add/remove

BLTSCLDB Initial strain values from previous bolt iterations within subcase

PDBT1_OUT Initial strain values of all bolts currently previously tightened

OELAR Inactive element status and addition/removal time




CNTRSTP Contact data needed for restart purposes

New Parameters:

BLTSEQID Output-integer-default =0. Bolt sequence identification number. Populates outputdata blocks for SOL 401 bolt sequence workflows

LOOPSEQ1 Input/output-integer-default=0. Count of the bolt sequence index within subcase

RSTTIME Output-real-no default. Converged time used for restart with unconvergedsubcase

INITACCN Input-integer-default=0. Flag to signal whether initial acceleration needs to becomputed in the current ANALYSIS=DYNAMICS subcase (initial accelerationcomputed if INITACCN=1)

STEQSTP Input-integer-default=0. Flag to indicate if a static equilibrium step needs to beperformed in a STATICS/preload subcase following a DYNAMICS subcase.

LSTSBCS Input-character-no default. Set to STAT if the current subcase follows a STATICSsubcase in a sequentially dependent analysis; set to PREL if the current subcasefollows a PRELOAD subcase in a sequentially dependent analysis; set to DYNAif the current subcase follows a DYNAMICS subcase in a sequentially dependentanalysis

RSTFLAG Input/output-integer-no default. Parameter used for restart of UMAT, indicatingthe status of restart run

RANDOM

Updated Format:

RANDOM XYCDB,DIT,PSDL,OUG2,OPG2,OQG2,OES2,OEF2,CASECC,OSTR2,OQMG2,RCROSSL,OFMPF2M,OSMPF2M,OLMPF2M,OPMPF2M,OGPMPF2M,OUGF2,OACPWR2,OACPWRI2,OACPWRT2,DISTL/PSDF,AUTO,OUGPSD2,OUGATO2,OUGRMS2,OUGNO2,OUGCRM2,OPGPSD2,OPGATO2,OPGRMS2,OPGNO2,OPGCRM2,OQGPSD2,OQGATO2,OQGRMS2,OQGNO2,OGGCRM2,OESPSD2,OESATO2,OESRMS2,OESNO2,OESCRM2,OEFPSD2,OEFATO2,OEFRMS2,OEFNO2,OEFCRM2,OEEPSD2,OEEATO2,OEERMS2,OEENO2,OEECRM2,OQMPSD2,OQMATO2,OQMRMS2,OQMNO2,OGMCRM2,OUGFPSD2,OUGFATO2,OUGFRMS2,OOGFNO2,OUGFCRM2,OAPPSD2,OIPPSD2,OTPPSD2,OCPSDF,OCCORF,SABFIL/S,N,NORAND/RMSINT/UNUSED/SSFLAG/RMSSF/CMPFLAG/RANDSC $


DISTL Table of DTI,DISTL Bulk Data images




Updated Parameter:

UNUSED Input-integer-default = 0. Unused.

SDR2

Updated Format:

SDR2 CASECC,CSTM,MPT,DIT,EQEXIN,SILD,ETT,{OL or EDT},BGPDT,PG,QG,UG,EST,XYCDB,OINT,PELSET,VIEWTB,GPSNT,DEQATN,DEQIND,DITID,PCOMPT,GPKE,BOLTFOR,MDLIST,COMPEST,EPT,DYNAMIC,EDT,CBRROT,LDFACAL,CUMMAL,CMPGEST,MFCASE/OPG1,OQG1,OUG1,OES1,OEF1,PUG,OGPKE1,OEFIIP,OEFIIS,OESRIP,OESRIS,OEFIT,OESRT/APP/S,N,NOSORT2/NOCOMP/ACOUSTIC/METRIK/ISOFLG/GPF/ACOUT/PREFDB/TABS/SIGMA/ADPTINDX/ADPTEXIT/BSKIP/FREQW/BTBRS/LANGLE/OMID/SRCOMPS/APP1/GSPF/RPM/SWPANGLE/STFOPTN/RUNIT/HINDEX/HOOPDOF/SCFLAG/CYCAXID/NACEXTRA/K6ROT $


MFCASE Frequency-based partitioning matrix for PEAKOUT results

New Parameter:

K6ROT Input-real-default=-1.0. Normal rotational stiffness factor for CQUAD8 and CTRIA6elements with new formulation

SSG1

Updated Format:

SSG1 SLT,BGPDT,CSTM,MEDGE,EST,MPT,ETT,EDT,MGG,CASECC,DIT,UG,DEQATN,DEQIND,GPSNT,CSTMO,SCSTM,GEOM4,EPT,PCOMPT,COMPEST,FORCDSTT/{PG or AG},PTELEM,SLTH/LUSET/NSKIP/DSENS/APP/ALTSHAPE/TABS/SEID/LMFACT/LOADOFFU/K6ROT $

New Parameters:

LOADOFFU Input–integer–default =0. NLCNTL LOADOFF use flag.

= 0 for not active

= 1 for active




K6ROT Input-real-default=-1.0. Normal rotational stiffness factor for CQUAD8 andCTRIA6 elements with new formulation.

TEMPATT

Updated Format:

TEMPATT CASECC,GEOM3,GEOM5,ETTORIG/TSETATT/S,N,ERRTEMPATT/RSTIME/TEMPOPT/S,N,NEWTSETID/S,N,TIMEDEP/S,N,TIMEINDT/TEMPINIT/TEMPLOAD/DTEMP/RAMPFLG/TINIT/TEND $

New Parameters:

RAMPFLG Input-integer-no default. Time unassigned temperature loads are ramped orstepped

TINIT Input-real-no default. Start time of the subcase

TEND Input-real-no default. End time in TSTEP1

TOLAPP

Updated Format:

Format for nonlinear transient analysis (TOLAPPF=0):

TOLAPP CASEXX,MPT,TEL/TOL,,TOL1/TOLAPPF/NSOUT/RSTEXIS/RSTTIME $


RSTEXIS Input-logical-default=FALSE. Restart run flag. Set to TRUE if a restart run.

RSTTIME Input-real-default=0.0. Start time for restart run.

VDRPC

Updated Format:

VDRPC CASEG,SETMC,APC,NPC,MAG,FOL,BGPDT,PNLLST or SLGRIDS/OUTFLE/APP/S,N,NOSORT2/S,N,NOSOUT/IRTYPE/DATTYP/VATVFLG $

New Parameter:

VATVFLG Input-integer-default =0. Data type. VATV analysis flag. Set to 1 if it is VATV analysis




New modules

ELAREXTF

Update external forces for element add/remove.

Format:

ELAREXTF SLT0,GPECT,ELAREST,BGPDT,MESTNL2,GEOM3/SLT/S,N,REEXTF $

Input Data Blocks:

SLT0 Old table of static and thermal loads

GPECT Grid point element connection table

ELAREST Element add/remove table


MESTNL2 Element summary table for nonlinear elements

GEOM3 Table of bulk entry images related to static and thermal loads

Output Data Block:

SLT New table of static and thermal loads based on added or removed elements

Parameters:

REEXTF Output-integer-no default. Recompute external force flag.

=0 to not recompute external force

>0 to recompute external force

=1 to recompute mass when one of GRAV, RFORCE, ACCEL, ACCEL1 orRFORCE1 bulk entry exists

ELARNOUT

Remove the nodal results such as displacement, SPC force, and so on that are associated withthe inactive regions for element add/remove.

Format:

ELARNOUT ORMN,OUGV1,,/ $




Input Data Blocks:

ORMN Table of removed nodes

OUGV1 Table of nodal results

ELART

Creates an element addition/removal information list.

Format:

ELART CASECC1,EPT,EDT,ECTS/ELAREST/RSTIME/TEND/SUBID1/SUBID2 $

Input Data Blocks:

CASECC1 Case control for current subcase with SEQDEP updated

EPT Element property table

EDT Element data table for iterative solver

ECTS Element connectivity table output by GP2

Output Data Block:

ELAREST Element addition/removal information list

Parameters:

RSTIME Input-real-no default. Start time of current subcase

TEND Input-real-no default. End time of current subcase

SUBID1 Input-integer-no default. Current subcase identification number

SUBID2 Input-integer-no default. Previous subcase identification number

MODGMC

Modifies the GEOM1 table to reflect the changes in nodal coordinates as a results of contact regionadjustment. Also, when Lagrange multipliers are used with contact, it expands the GEOM2 table toreflect the extra DOF that are added to the model.

Format:

MODGMC GEOM1,ADJUST,GEOM2/MGEOM1,MGEOM2/NUMLMC $




Input Data Blocks:

GEOM1 Data block that contains grid geometry

ADJUST Contact nodal adjusted coordinates table

GEOM2 Data block that contains element connectivity

Output Data Blocks:

MGEOM1 Modified grid geometry data block with the nodal coordinates on the targetregions adjusted

MGEOM2 Modified GEOM2 data block to reflect the additional Lagrange multiplier DOF

Parameter:

NUMLMC Input-integer-default=0. Number of Lagrange multiplier DOF

MODGM3LD

Modifies the GEOM3 data blocks and creates the GEOM3LD data block based on the LOADOFFPdefinition.

Format:

MODGM3LD GEOM3/GEOM3LD/S,N,ERRMODG3/LOADOFFP $

Input Data Block:

GEOM3 Table of static and thermal loads

Output Data Block:

GEOM3LD Modified statics and thermal loads table

Parameters:

ERRMODG3 Output-logical-no default. MODGM3LD module error return flag. Set to TRUE ifan error is found.




LOADOFFP Input-character-default=NONE. NLCNTL LOADOFF value defined

= NONE to include body and boundary loads in the output GEOM3LD.

= BODY to exclude body loads. That is, no body load in GEOM3LD.

= BOUNDRY to exclude surface loads. That is, no surface load inGEOM3LD. (This excludes any load not part of body load, including MPpressures from thermal.)

= BOTH to exclude both body and surface loads

MODGVATV

Check and update geometry and element tables for VATV analysis.

Format:

MODGVATV GEOM1,PVT,GEOM1ATV,PVTATV,GEOM2/OGEOM1,ATVMIC,VATVSGRD/ $

Input Data Blocks:

GEOM1 Table of bulk entry images related to geometry


GEOM1ATV Table of bulk entry images related to geometry from VATV computation

PVTATV Sets parameter values from VATV computation

GEOM2 Table of bulk entry images related to element connectivity

Output Data Blocks:

OGEOM1 Updated table of Bulk Data entry images related to geometry

ATVMIC Microphone element identification numbers of VATV in VATV analysis

VATVSGRD Structural grids list in the VATV

NUMOP2

Outputs the total number of data blocks from an OP2 file.

Format:

NUMOP2 //UNITNUM/S,N,IRET $




Parameters:

UNITNUM Input-integer-no default. FORTRAN unit number of the OP2 file

IRET Output-integer-no default. Total number of data blocks in the OP2 file.

PEAKOUT

Processes the data required to determine the frequencies at which peak responses occur for a set ofPEAKOUT filtering criteria.

Format:

PEAKOUT I1,I2,I3,I4/O1/P1/P2 $

Input Data Blocks:

Ii Input data blocks that depend on the value P1

Output Data Block:

O1 Output data block that depends on the value P1

Parameters:

P1 Input-integer-no default. Option selection described in the table that follows

P2 Input-character-no default. Parameter used with P1 = 4 Option only.

Summary of Options:

P1 Option Description

P1 = 1 Reads PEAKOUT bulk entries and formats the PEAKOUT data using SIL numbersinstead of grid and component numbers.

P1 = 2 Creates a G-sized partition vector of all DOF required by the total number ofPEAKOUT case control commands. This vector is used to create an RGAPEAKtransformation matrix which is used in the peak response search.

P1 = 3 For each subcase, identifies any requested PEAKOUT case control commands,searches for the requested peak responses, and outputs a matrix of partition vectorsthat identify the frequencies that correspond to the peak responses.

P1 = 4 For each subcase, creates a partition vector that identifies the frequencies thatare output.




Option P1 = 1

Reads PEAKOUT bulk entries and formats the PEAKOUT data using SIL numbers instead of grid andcomponent numbers.

Format:

PEAKOUT DYNAMIC,BGPDT,,,/TABPKOUT/1 $

Input Data Blocks:

DYNAMIC Table of bulk entry images related to dynamics that contains PEAKOUT bulkentry data


Output Data Block:

TABPKOUT Table that contains PEAKOUT data from GEOMi and SIL numbers

Option P1 = 2

Creates a G-sized partition vector of all DOF required by the total number of PEAKOUT case controlcommands. This vector is used to create an RGAPEAK transformation matrix which is used inthe peak response search.

Format:

PEAKOUT TABPKOUT,CASES,,,/VGPKOUT/2 $

Input Data Blocks:

TABPKOUT Table output from Option P1 = 1

CASES Table of case control command images

Output Data Block:

VGPKOUT G-sized partitioning vector that identifies all DOF required for the peak responsesearch

Option P1 = 3

For each subcase, identifies any requested PEAKOUT case control commands, searches for therequested peak responses, and outputs a matrix of partition vectors that identify the frequencies thatcorrespond to the peak responses.




Format:

PEAKOUT TABPKOUT,CASES,UGFPEAK,FOL,DIT/MFPKOUT/3 $

Input Data Blocks:

TABPKOUT Table output from Option 1


UGFPEAK G-size matrix of responses with values needed for the peak output search. Thematrix is sparse with only terms needed for the peak response search.

FOL Frequency response frequency output list

DIT Direct input tables

Output Data Block:

MFPKOUT Matrix of frequency partitioning vectors that identify the output frequencies thatcorrespond to the peak responses. A matrix of frequency partitioning vectors isoutput for each subcase.

Option P1 = 4

For each subcase, creates a partition vector that identifies the frequencies that are output.

Format:

PEAKOUT CASES,FOL,MFPKOUT,,/MFCASE/4/XXXX $

Input Data Blocks:


FOL Frequency response frequency output list

MFPKOUT Matrix of frequency partitioning vectors that identify the output frequencies thatcorrespond to the peak responses. A matrix of frequency partitioning vectors isoutput for each subcase.

Output Data Block:

MFCASE Matrix of frequency partitioning vectors that identify the output frequencies fromSOLUTION = PEAKOUT or SOLUTION = SET.




Parameter:

XXXX Input-character-no default. Case control command to search.

'GPFO' for the GPFORCE case control command'DISP' for the DISPLACEMENT case control command'VELO' for the VELOCITY case control command'ACCE' for the ACCELERATION case control command'PRES' for the PRESSURE case control command'GRDC' for the GRIDCON case control command'PANC' for the PANCON case control command'MODC' for the MODCON case control command

RDTSTEP

Read parameters in TSTEP1 from the NLSAM data block.

Format:

RDTSTEP CASECC,NLSAM//OPTN/S,N,OUTVAL

Input Data Blocks:

CASECC Table of case control command images

NLSAM Table of bulk entry images related to SAMCEF

Parameters:

OPTN Input-integer-no default. Input option

=-1 TEND (first line)

=1 TEND (last line)

=2 NINC (not currently supported)

=3 NOUT (not currently supported)

OUTVAL Output-real-no default. Output value

RSTWRT

Write out RST data block.

Format:

RSTWRT CASESX2H/RST/RSTTIME/SBCNO/NSTEP/OFSTFLG/MASSNEWM/BLTNUM/BLTSEQP/PBCONVP/ANAL/DLDPREV/LDPREV/CNTLOOP/CNTUPDT/NEWBCSET/MSCHG $




Input Data Block:

CASESX2H Table of case control values

Output Data Block:

RST Table of restart information

Parameters:

RSTTIME Input-real-no default. Restart time

SBCNO Input-integer-no default. Subcase identification number

NSTEP Input-integer-no default. Current time step position for subcase

OFSTFLG Input-integer-no default. Offset flag for 401

MASSNEWM Input-integer-no default. MASS matrix update flag for 401

BLTNUM Input-integer-no default. Bolt type number; 0 for no bolt

BLTSEQP Input-integer-no default. Bolt sequence identification number

PBCONVP Input-integer-no default. Bolt convergence flag

=0 for either bolt not present or bolt preload update is not needed

=1 for bolt has converged

=2 for bolt has not converged and bolt preload needs to be updated

ANAL Input-integer-no default. Flag that indicates the analysis type

=1 for ANALYSIS = STATICS

=2 for ANALYSIS = MODES

=3 for ANALYSIS = PRELOAD

DLDPREV Input-integer-no default. DLOAD of previous run

LDPREV Input-integer-no default. LOAD of previous run

CNTLOOP Input-integer-no default. Parameter for CONTACT loop

CNTUPDT Input-integer-no default. Parameter for CONTACT update

NEWBCSET Input-integer-no default. Parameter for new CONTACT set

MSCHG Input-integer-no default. Parameter for preload




SPCDFILE

Generates frequency-dependent enforced displacement matrix from frequency response resultsin an OUGV1 data block on an OUTPUT2 file.

Format:

SPCDFILE USET,CASECC,GEOM4,DYNAMIC,EQEXIN,FOL/YGFX,YGX/IREC/S,N,NOSPCF $

Input Data Blocks:

USET DOF set membership table for the g-set

CASECC Table of case control command images for a given solution pass

GEOM4 Table of bulk entry images related to constraints

DYNAMIC Table of bulk entry images related to dynamics

EQEXIN Table of equivalence external to internal grid/scalar numbering

FOL Table of output frequencies

Output Data Blocks:

YGFX Frequency-dependent enforced displacement matrix

YGX Unitary enforced displacement matrix

Parameters:

IREC Input-integer-no default. Record number of CASECC to use for case controlvalues

NOSPCF Output-integer-no default. SPCF selection flag

0 = No SPCF selected for this subcase

1 = Selected SPCF found for this subcase

TEMPFRIC

Compute the nodal temperatures for the current time step.

Format:

TEMPFRIC GEOM3,NODTEMPL/NODTEMPI/TEMPINIT/TEMPLOAD/SCINIT/SCENDT/RSTIME/NGRID $




Input Data Blocks:

GEOM3 Static and thermal load information

NODTEMPL Nodal temperatures from prior subcase

Output Data Block:

NODTEMPI Nodal temperatures corresponding to current time step.

Parameters:

TEMPINIT Input-integer-default=0. Initial temperature set identification number

TEMPLOAD Input-integer-default=0. Temperature load set identification number

SCINIT Input-real-no default. Subcase start time

SCENDT Input-real-no default. Subcase end time

RSTIME Input-real-no default. Current time

NGRID Input-integer-no default. Number of grids in the model

VATVLOAD

Creates partition vector or normal loading matrix from loading matrix.

Format:

VATVLOAD PS3,NORMVCT,,/PSNORM/IFPART/S,N,NNODES $

Input Data Blocks:

PS3 Structural load matrix

NORMVCT Table of nodal normal vector

Output Data Block:

PSNORM Partition vector or normal nodal loading matrix

Parameters:

IFPART Input-integer-default=0. If Set to 1, create the partition vector

NNODES Output-integer-default=0. The number of structural nodes in the normal nodalloading matrix




VATVMAT

Create VATV matrix from sysnoise table.

Format:

VATVMAT VATVSSN,FOL/VATV/IFREQ $

Input Data Blocks:

VATVSSN Table of VATV from sysnoise

FOL Frequency response frequency output list from VATV computation analysis

Output Data Block:

VATV VATV matrix

Parameter:

IFREQ Input-integer-default=1. The ith frequency in the FOL data block



Chapter 15: Problem Report (PR) fixes

Problem Report (PR) fixesThe following list summarizes the problems that are fixed in Simcenter Nastran 2019.1.

PR# Problem Description8381589 SOL 109 direct transient analysis results are incorrect.8385552 An INIPINE error occurs.8394541 A problem arises when translating a CSYS from the Bolt dialog box in SOL402.8395987 Output is missing form the .pch file in SOL402.8553161 A question about access violation errors.9018012 Output vectors are missing in SOL 106.9084228 A LOADOFF failure occurs in multiphysics coupled solutions.9103518 A problem with output of acoustic power.

9123410 Incorrect results occur in SOL601 when 3D Elements, 3D orthotropic material,and MATCID are used.

9148966 Equivalent nodal forces are incorrect when PLOADE1 is applied to a CPLSTS6element with non-uniform thickness.

9160835 Using inertia relief (PARAM INREL -2) produces incorrect results.9164856 A problem arises when using SOL101 preload and SPCD.9191110 Linear Statics displacement results problem.9198592 Nonlinear modal analysis problem.9204883 Avoiding contact omission in SOL401 contact analysis.9204905 Poor convergence occurs when LGDISP is used with SOL 401 and bolt preload.

9206617 The dynamic response is incorrect for SOL 112 in Simcenter Nastran 12 withresidual vectors and NODYNRSP.

9208221 Specifying PARAM,OMID,YES triggers unrealistic values on the corner nodesof CQUAD4.

9212740 SOL 401 restart is unable to find clearly existing subcase to use in the restart.

9212776 Restart solution is unable to find or misidentifies the .op2 file from the restart-fromsolution.

9212854 Error message does not contain sufficient information.9220497 Contact is not working.9222147 Large error in stress occurs.9223053 F-OF-MPC is not shown in the .f06 file.9228273 A problem exists with the Campbell diagram output from rotor093.dat.9229441 SYSTEM FATAL MESSAGE 4276 occurs when defining a subcase in SOL159.9230130 Strange bolt preload results occur when modeled with solid elements.9230261 A problem exists with the Campbell diagram output from rotor094.dat.9233421 In SOL 103, CQUAD8 and CTRIA6 elements are grounded on DOF 6.9239504 Using TF and NOLIN1 loads too small but MSC appears correct.



9248947 In SOL 111, MEFFMASS case control command and PARAM,DDRMM,-1 maycause modes to be missing.

9252088 KHH does not have damping when a superelement is included.9252309 Results differ from those in the Simcenter Nastran Rotor Dynamics User's Guide.9262672 Convergence problems occur in SOL402.9269160 Incorrect order of operations occurs in CONATTM SUBDMAP.9279164 A null pivot problem arises in SOL 402 when no such problem arises in SOL 101.9282440 FREQ card limitation.

9287268 A problem arises when calculating acoustic modes in a vibro-acoustic FEMmodel.

9293817 PBARL design variables corrupt sensitivities for other design variables.



Chapter 16: Default and input changes for past releases

NX Nastran 12 summary of changes to default settings and inputs


Note

The following table lists changes to default settings that may produce differences inresults between NX Nastran 11 and NX Nastran 12. Default setting changes that produceadditional output only are not included in this table.

Input type Default changeKeywords NoneNastran statement NoneFile managementstatements NoneExecutive controlstatements NoneCase controlcommands

The default for the interface file request describer on the MBDEXPORT casecontrol command has changed from RECURDYN to SCMOTION.

Parameters The default for the MPCZERO parameter has changed from 1.0E-11 to1.0E-7.

Bulk entries The default for the AUTO parameter on the NXSTRAT entry has changedfrom 0 to 1.

Keyword changes

Keyword Keyword description Description of change

krylov Activates the Padé via Lanczosmethod in SOL 108. New keyword


Systemcell


205Defines the number of rows that aresimultaneously updated during asparse symmetric decomposition.

Update of the computer-dependentdefault rank value



Systemcell


627

In SOL 401, defines the outputcoordinate system for the 3Dsolids elements CTETRA, CHEXA,CPENTA and CPYRAM elements,the plane strain elements CPLSTN3,CPLSTN4, CPLSTN6, CPLSTN8, andthe plane stress elements CPLSTS3,CPLSTS4, CPLSTS6, CPLSTS8.

New system cell

640 PRESOUTDetermines the case controlcommand to be used for acousticpressure output at fluid grids.

New system cell

649 Controls whether the GDSTAT parallelsolution is used in SOL 401. New system cell

653

Controls whether the results arewritten to an HDF5 format output filein addition to an OP2 format outputfile.

New system cell

665 BSHDCPL

Turns off the computation of theCBUSH coupling moments which arecomputed when the connecting gridpoints are not coincident. Applies toall solutions except for SOLs 402,601, and 701.

New system cell

679 KRYLOV Activates the Pade via Lanczosmethod in SOL 108. New system cell

687Specifies the modulus of elasticity thatis used for rigid Lagrange elementsin a model.

New system cell

698

Controls the number of warning orerror messages from temperatureprocessing from the GP3 moduleprinted to the .f06 file.

New system cell


No changes to file management statements.





ACCELERATION Acceleration output requestAdded remark on results recoveryfor points on frequency-dependentexternal superelements.

ACINTENSITY Acoustic intensity output Added SORT2 option.



Default and input changes for past releases


ACPOWER Acoustic power output Added options for random analysisresults.

ACVELOCITY Acoustic velocity output Added SORT2 option.ALOAD Acoustic load set selection New case control command

ATVOUT Acoustic transfer vector (ATV)creation specification New case control command

DISPLACEMENT Displacement output request

Added remark on results recoveryfor points on frequency-dependentexternal superelements.

Added remark that pressure resultsare separated from the displacementresults.

FRFIN Frequency-dependent frequencyresponse function matrix input New case control command

FRFOUT Frequency-dependent externalsuperelement creation specification New case control command

GRDCON Acoustic grid contribution request New case control command

IMPERF Selects grid point imperfections inSOL 401 New case control command

INITS Selects an initial stress or strain set oran offset strain set for SOL 401 New case control command

INPOWER Incident acoustic power output New case control command

MBDEXPORTCreates interface file for multibodyand control system software during aSOL 103, 111, or 112 run.

The Simcenter Motion solver isnow supported and the default forthe interface file request describerhas changed from RECURDYN toSCMOTION.

MONITOR Print selection for monitor data New case control command

NLARCL Requests nonlinear buckling in SOL401 New case control command

OTMFORC OTM force and moment output New case control command

PANCON Acoustic panel contribution request Eliminated the ability to request gridcontributions.

PRESSURE Pressure output request

By default, DISPLACEMENT casecontrol command can no longeroutput pressure results. The modifiedPRESSURE case control commandneeds to be used.

SETMC Modal contribution set definition Added PRESSURE response type.

TRLOSS Acoustic power transmission lossoutput New case control command

TRPOWER Transmitted acoustic power output New case control commandVECTOR Displacement output request Undocumented

VELOCITY Velocity output requestAdded remark on results recoveryfor points on frequency-dependentexternal superelements.




Parameter changes


BDMNCON

For SOL 200 topology optimization,defines the number of design cyclesin which the software will delay theapplication of any manufacturingconstraints.

New parameter

BRSYMFAC

Controls whether the stiffness anddamping that the software uses forCBEAR elements is the stiffness anddamping defined on PBEAR bulkentries or symmetrized versions ofthe stiffness and damping defined onPBEAR bulk entries.

New parameter

FLEXINVSelects the inversion method thatthe software uses when it invertsFRFFLEX bulk entry data.

New parameter

OPTION Used in conjunction with theSCRSPEC parameter. Corrected documentation

RESVALT

Determines whether the contributionof the residual vector modes tothe dynamic physical response isconsidered.

Undocumented

SCRSPECControls how the structural responseis calculated for response spectrainput in normal modes analysis.

Corrected documentation



Bulk entry changes


ACADAPTUser specified order adaptation rulefor acoustics FEM adaptive ordersolution

New bulk entry

ACORDER User specified order for acousticsFEM adaptive order solution New bulk entry

ACPLNW Acoustic plane wave source New bulk entryACPNVEL Acoustic panel normal velocity New bulk entryACPOLE1 Acoustic monopole source New bulk entryACPOLE2 Acoustic dipole source New bulk entryACPRESS Enforced pressure value on grids New bulk entryACTRAD Acoustic transfer admittance New bulk entry

ALOAD Acoustic load combination with unitscale factors New bulk entry

ATVBULK Selects acoustic transfer vector (ATV)results for an ATV system run New bulk entry





ATVFS Coupling interface definition for anacoustic transfer vector (ATV) New bulk entry

BCTPARM Control parameters for the contactalgorithm

The following new parameters havebeen added to the BCTPARM bulkentry for SOL 401: IPENRAMP,INTRFC, CTDAMP, CTDAMPN,CTDAMPT, and GAPVAL.

CHACAB Acoustic absorber element connection UndocumentedCHACBR Acoustic barrier element connection Undocumented

DMNCON Defines a manufacturing condition forSOL 200 topology optimization. New bulk entry

DMRLAW Defines a lattice type for SOL 200topology optimization. New bulk entry

DRESP1

Defines a set of structural responsesthat are used for the objective and/ordesign constraints, or for sensitivityanalysis purposes

For topology optimization, theDRESP1 now includes a complianceresponse type. It is defined byincluding CMPLNCE in the RTYPEfield.

DVTREL1 Selects the elements to be included ina SOL 200 topology optimization. New bulk entry

FRFFLEX Direct input of frequency-dependentdynamic flexibility matrix at points New bulk entry

FRFOMAP Assigns output type to FRFOTMresults New bulk entry

FRFOTMDirect input of frequency-dependentdynamic output transformation matrixat points

New bulk entry

FRFSTIF Direct input of frequency-dependentdynamic stiffness matrix at points New bulk entry

IMPERF Defines grid point imperfections inSOL 401 New bulk entry

IMPRADD Combines multiple IMPERF bulkentries in SOL 401 New bulk entry

MATPOR Defines material properties for porousmaterials used as acoustic absorbers

The defaults for the RHO, C, GAMMA,PR, MU, RES, POR, L1, and L2 fieldschange from "0.0" to "no default". Thedefault for the TORT field changesfrom "0.0" to "1.0".

The input for the RHO, C, GAMMA,PR, MU, L1, and L2 fields changefrom "REAL" to "REAL > 0.0". Theinput for the RES field changes from"REAL" to "REAL ≥ 0.0". The input forthe TORT field changes from "REAL"to "REAL ≥ 1.0". The input for thePOR field changes from "REAL" to"0.0 < REAL ≤ 1.0".





MAT10C

Defines constant or nominal materialproperties for fluid or absorberelements in coupled fluid-structuralanalysis

New bulk entry

MATF10CDefines tabular material properties forfluid or absorber elements in coupledfluid-structural analysis

New bulk entry

MONPNT2 Integrated load monitor point -element monitor output results item New bulk entry

MONPNT3 Integrated load monitor point - sumsgrid point forces New bulk entry

NLARCL Defines control parameters for SOL401 nonlinear buckling New bulk entry

NLCNTL Defines solution control parametersfor SOL 401

For SOL 401, the following newparameters have been added to theNLCNTL bulk entry: MSTAB, MSFAC

NXSTRATDefines parameters for solutioncontrol and strategy in advancednonlinear structural analysis

The following new parametershave been added to the NXSTRATbulk entry: ATSNSUB, ATSMASS,TETINT, DIAGSOL, BOLTDAMP,TFSHIFT

PAABSF1 Acoustic Impedance/AdmittanceElement Property New bulk entry

PACABS Acoustic absorber property UndocumentedPACBAR Acoustic barrier property Undocumented

PACTRAD Property of acoustic transferadmittance New bulk entry

PCOMPG1

Property entry to define a compositeproperty which allows for a differentfailure theory for each layer. SOLs401 and 402 only

New bulk entry

PLOTEL3 Triangular visualization element withthree grid points New bulk entry

PLOTEL4 Quadrilateral visualization elementwith four grid points New bulk entry

PLOTEL6 Triangular visualization element withsix grid points New bulk entry

PLOTEL8 Quadrilateral visualization elementwith eight grid points New bulk entry

PLOTHEXSix-sided hexahedron visualizationelement with eight to twenty gridpoints

New bulk entry

PLOTPEN Five-sided pentahedron visualizationelement with six to fifteen grid points New bulk entry

PLOTPYRFive-sided pyramid visualizationelement with five to thirteen gridpoints

New bulk entry

PLOTTET Four-sided tetrahedron visualizationelement with four to ten grid points New bulk entry




Bulk entry Bulk entry description Description of changeSEBULK Partitional superelement connection Added the TYPE = "FRFOP2" option

TABLEM5

For progressive ply failure with the UDdamage model in SOL 401, TABLEM5is optionally used to define a nonlinearfunction relating the shear damage(d12) to the thermodynamic force (Y)

New bulk entry



Note

The following table lists changes to default settings that may produce differences inresults between NX Nastran 10 and NX Nastran 11. Default setting changes that produceadditional output only are not included in this table.

Input type Default changeKeywords None

Nastran statement The nastran.exe and nastranw.exe commands run the ILP-64 executablerather than the LP-64 executable


Parameters The default for WRTMAT has changed to 1The default for PRGPST has changed to NO

Bulk entries The default for CONV1 on the DOPTPRM bulk entry has changed from0.001 to 0.0001The default for CRCERAT on the NLCNTL bulk entry has changed from0.1 to 0.4The default for CRTECO on the NLCNTL bulk entry has changed from 0.01to 1.0E-4


Systemcell


462 - - - Methods for SOL 111. Automatic selection of performancemethods.

617 ACFORM Reverts to previous acousticsbehavior. New system cell




Systemcell


635 Q8T6_ANG

Controls the maximum allowableangle between normals to corner gridsfor CQUAD8 and CTRIA6 elements.USER WARNING MESSAGE 5276is issued if the maximum allowableangle is exceeded.

New system cell

636 TET_EPIA GEOMCHECK check value forCTETRA – edge point included angle. New system cell

637 HEX_EPIA GEOMCHECK check value forCHEXA – edge point included angle. New system cell

638 PEN_EPIA GEOMCHECK check value forCPENTA – edge point included angle. New system cell

639 PYR_EPIAGEOMCHECK check value forCPYRAM – edge point includedangle.

New system cell




Executive controlstatement

Executive control statementdescription Description of change

GEOMCHECKSpecifies tolerance values for(optional) finite element geometrytests.

Added edge-point-included-angle(EPIA) geometry tests for CTETRA,CHEXA, CPENTA, CPYRAM,CHEXCZ, and CPENTCZ elementswith midside grids.

Added cohesive elements CHEXCZand CPENTCZ, and chockingelements CCHOCK3, CCHOCK4,CCHOCK6, and CCHOCK8 to thetable of test keywords.



ACINTENSITY Requests acoustic intensity output atmicrophone points. New case control command

ACPOWER Requests acoustic power output forAMLREGs. New case control command

ACVELOCITY Requests acoustic velocity output atmicrophone points. New case control command





ANALYSIS Specifies the type of analysis beingperformed for the current subcase.

Cyclic normal modes subcase isavailable in SOL 401 for modelswhich include axisymmetric elements.The subcase is designated with theANALYSIS=CYCMODES.

Fourier normal modes subcase isavailable in SOL 401 for modelswhich include axisymmetric elements.The subcase is designated with theANALYSIS=FOURIER.

A bolt preload subcaserequires ANALYSIS=PRELOADand BOLTLD=n commands.(ANALYSIS=STATICS does no longersupport bolt preload subcases.)

Random analysis subcase isavailable in SOLs 108 and 111.The subcase is designated with theANALYSIS=RANDOM case controlcommand in the subcase.

BCSET Selects the contact set for SOLs 101,103, 105, 111, 112, 401, 601 and 701.

BCSET can now be defined in a staticsubcase for SOL 401 only.

BCRESULTSContact Result Output Request(SOLs 101, 103, 111, 112, 401, 601,and 701).

SEPDIS describer is now supportedby SOLs 601 and 701.

BGRESULTS Glue Result Output Request (SOLs101, 103, 105, 401, and 601).

Added new SEPDIS describer torequest slide distance output.

Added support for Sol 601.

BOLTRESULTS Requests bolt results output in SOL401. New case control command

CKGAP Requests gap result output forchocking elements in SOL 401. New case control command

CYCFORCES

Requests MPC force output atthe grid points selected for theautomatic coupling in a SOL 401cyclic symmetry analysis.


CYCSET Selects a cyclic symmetric boundarycoupling in SOL 401. New case control command

CZRESULTS Requests results output for cohesiveelements in SOL 401. New case control command

DTEMP

Selects a time-assigned temperatureset to be used for temperaturedependent material properties andthermal loading.

Added support for SOLs 601 and 701.





FLSTCNT Miscellaneous control parameters forfluid-structure interaction.

Describer SKINOUT has beenenhanced to write out coupling datato OACCQ output data block in an.op2 file.

HARMONICS

Requests the solution harmonics forcyclic symmetry and axisymmetricmodels in solutions 114, 115, 116,118, and 401.

Case control has been enhanced tosupport SOL 401.

Describer h and NONE have beenremoved.

HOUTPUT

Requests harmonic output for cyclicsymmetry and axisymmetric modelsin solutions 114, 115, 116, 118, and401.

Case control has been enhanced tosupport SOL 401.

INITS Selects an initial stress or strain set. New case control command

MODCON Requests modal contribution resultsfor the residual.

Case control has been enhancedto support results for MICPNTmicrophone points (0D microphoneelements).

MONVARSelects degree-of-freedom for adisplacement monitor plot in a SOL401 run with Simcenter Multiphysics.


OLOAD Requests the form and type of appliedload vector output. Added support for SOLs 601 and 701.

OSTNINI Requests initial strain output in SOL401. New case control command

PANCON Requests acoustic panel contributionresults for the residual.

Case control has been enhancedto support results for MICPNTmicrophone points (0D microphoneelements).

PFRESULTSRequests progressive failure resultsoutput for composite solid elementsin SOL 401.


SETMCNAMESpecifies the title of a displacementmonitor plot in a SOL 401 run withSimcenter Multiphysics.


STATVAR Requests output of state variableswith SOL 401. New case control command

Parameter changes


AFZERO

Frequency threshold in units of hertzused by the SOL 401 cyclic andFourier subcase types to determine ifa mode is a rigid body mode when AFnormalization is requested.

New parameter

FRUMINAllows frequency-dependentelements to be connected to o-setdegrees-of-freedom.

New parameter





MODTRKSpecifies mode tracking algorithm forcomplex eigenvalue rotor dynamicanalysis.

Added MODTRK = 4 option.

ODSRequests an efficient RDMODESrestart method which reduces theamount of eigenvector restart data.

New parameter

RLOOPNEW

For complex eigenvalue andfrequency response rotor dynamicanalysis, includes gyroscopic andcirculation terms in mass, damping,and stiffness matrices when theanalysis is performed in the fixedreference system.

New parameter

SEOP2CV

Overrides the effect ofPARAM,OP2FMT when the .op2file is created by the EXTSEOUT casecontrol command on ILP64.

New parameter

SPCSTR

Constrains structural DOFs in theanalysis set, but only after thestructural excitation is transferredover to the fluid.

New parameter

Item code changes

No changes to item codes.



Bulk entry changes


ACMODLDefines modeling parameters for theinterface between the fluid and thestructure.

Added option for turning on strong orweak acoustic coupling.

AMLREG Defines automatically matched layerregion for acoustics analysis. New bulk entry

BCRPARA Defines parameters for a contact faceor edge region.

For subcases which have a constanttime, the software automaticallyincrements the contact offset usingthe number of increments. Thenumber of increments is defined witheither the Ninc field on the TSTEP1entry, or with the Ninc field on theBOLTSEQ entry.

BCTPARMSurface-to-Surface ContactParameters (SOLs 101, 103,111, 112, and 401).

Added option to delay contactfriction to help alleviate convergenceproblems.





BGPARM Control parameters for the gluealgorithm.

Added SLIDE parameter for slidingglue.

BOLTFRCDefines bolt preload force,displacement, or strain in SOL401.

New bulk entry

BOLTSEQ Specifies a bolt preload sequence inSOL 401. New bulk entry

CCHOCK3Defines a 2D chocking triangularelement connection. Valid for SOL401 axisymmetric analysis only.

New bulk entry

CCHOCK4Defines a 2D chocking quadrilateralelement connection. Valid for SOL401 axisymmetric analysis only.

New bulk entry

CCHOCK6Defines a 2D chocking triangularelement connection. Valid for SOL401 axisymmetric analysis only.

New bulk entry

CCHOCK8Defines a 2D chocking quadrilateralelement connection. Valid for SOL401 axisymmetric analysis only.

New bulk entry

CHEXA Six-Sided Solid Element Connection. Added PMIC to the PID list.

CHEXCZ

Defines the connections of thesix-sided cohesive element with eightto twenty grid points. Valid for SOL401 only.

New bulk entry

CPENTA Five-Sided Solid Element Connection. Added PMIC to the PID list.

CPENTCZ

Defines the connections of thefive-sided cohesive element with sixto fifteen grid points. Valid for SOL401 only.

New bulk entry

CPYRAM Five-Sided Solid Element Connection. Added PMIC to the PID list.

CQUAD4 Quadrilateral Plate ElementConnection. Added PMIC to the PID list.

CROD Defines atension-compression-torsion element. Added PMIC to the PID list.

CTETRA Four-Sided Solid ElementConnection. Added PMIC to the PID list.

CTRIA3 Triangular Plate Element Connection. Added PMIC to the PID list.

CYCSET Defines pairs for cyclic symmetry inSOL 401. New bulk entry

CYCADD Combines cyclic symmetry sets inSOL 401. New bulk entry

CYCAXIS Default cylindrical coordinate systemfor a SOL 401 cyclic model. New bulk entry

DOPTPRMOverrides default values ofparameters used in designoptimization.

Added new EDVOUT parameter.

DVEREL1 Automatic shell element thicknessdesign variable. New bulk entry





DTEMP Defines a time dependent temperatureset. Added support for SOLs 601 and 701.

INITADD Combines multiple initial stress orinitial strain sets in SOL 401. New bulk entry

INITS Defines initial stress or strain state inSOL 401. New bulk entry

IPLANE Defines infinite plane for acousticsanalysis. New bulk entry

MAT3

Defines linear orthotropic materialsfor the axisymmetric elementsCQUADX4, CQUADX8, CTRAX3,CTRAX6; the plane strain elementsCPLSTN3, CPLSTN4, CPLSTN6,CPLSTN8; and the plane stresselements CPLSTS3, CPLSTS4,CPLSTS6, CPLSTS8.

Added note that except foraxisymmetric models in SOL601, 701, the use of MAT11 isrecommended for defining orthotropicmaterials for axisymmetric elementsand 2D solid elements.

The MAT3 bulk entry is scheduled tobe undocumented in the next versionof NX Nastran.

MAT11

Defines the orthotropic materialproperties for axisymmetric elements,2D solid elements, 3D solid elements,and 3D solid composite elements.

Added support for axisymmetricelements, 2D solid elements, and 3Dsolid composite elements.

MATCZDefines damage model and materialproperties for cohesive elements.Valid for SOL 401 only.

New bulk entry

MATDMG

Defines damage-related materialproperties for progressive ply failurein composite solid elements. Valid forSOL 401 only.

New bulk entry

MATPOR Defines material properties for porousmaterials used as acoustic absorbers. New bulk entry

MICPNT Defines microphone point for acousticanalysis. New bulk entry

MUMATDefines the material properties for theuser defined material subroutine inSOL 401.

New bulk entry

NLCNTL Defines solution control parametersfor SOL 401.

Added new parameters:

AUTOTIM, CNTMDIV, EQMFMIN,EQMFMX, FRICDLY, FSYMTOL,KSYM, KSYMTOL, LVAR, MISFBLT,MSGLVLB, MSGLVLC, TSCEQ,TSCUMAT, UMFMIN, UMFMX,USOLVER, and ZERBOLT.

PCHOCK Defines properties for CCHOCKielements. Valid for SOL 401 only. New bulk entry

PCOMPSDefines the properties of an n-plycomposite material laminate forCHEXA and CPENTA solid elements.

Added progressive ply failure option.





PGPLSNDefines the properties of generalizedplane strain elements. Valid for SOL401 only.

Added capability to definetime-varying added stiffness.

PMICDefines dummy property formicrophone elements for acousticanalysis.

New bulk entry

PSOLCZ Defines the properties of cohesiveelements. Valid for SOL 401 only. New bulk entry

RCROSSC

Defines a pair of response quantitiesfor computing the cross-powerspectral density and cross-correlationfunctions in random analysis forlaminate composites.

New bulk entry

RFORCEDefines a static loading conditiondue to an angular velocity and/oracceleration.

Describer RACC is supported bySOLs 601 and 701.

RFORCE1Defines a static loading conditiondue to an angular velocity and/oracceleration.

Describer RACC is supported bySOLs 601 and 701.

RFORCE2

Defines a static loading condition dueto an angular velocity and/or angularacceleration for maneuver load rotordynamic analysis. Valid for SOL 101only.

New bulk entry

ROTORD Defines rotor dynamics solutionoptions.

Added option for selectingsynchronous modes only in aSOL 107 or SOL 110 complexeigenvalue rotor dynamic analysis.

ROTPARMDefines solution control parametersfor complex eigenvalue and frequencyresponse rotor dynamic analysis.

New bulk entry

ROTSE

Defines the modal reduction typeand additional a-set grids for a rotorsuperelement. Valid for SOLs 107,108, and 109.

Expanded solution support forsuperelement style reduction of rotorsto include SOL 108 direct frequencyresponse rotor dynamic analysisand SOL 109 direct transient rotordynamic analysis.



Note

The following table lists changes to default settings that may produce differences in resultsbetween NX Nastran 9 and NX Nastran 10. Default setting changes that produce additionaloutput only are not included in this table.




Input type Default changeKeywords None

Nastran statement

For CTRAX3, CQUADX4, CTRAX6, CQUADX8, CTRIAX, and CQUADXelements, the default input and output changes from being on a per unitradian basis to being on a per 2π radian basis. This change does not applyto SOLs 153, 159, 601, and 701.


Parameters None

Bulk entries

For the ROTORD bulk entry, the default for MAXITER changes from “0”to “10”.

For the SWLDPRM bulk entry, the default for DISPRT changes from “0”to “2”.


Systemcell


370 QRMETH Selects the formulation used byQUADR and TRIAR elements.

When SYSTEM(370) = 1, complexstresses and strains are not computedfor QUADR and TRIAR elements thatare used to model laminates.

579 FREQVM

Determines whether the von Misesstress and strain are computed fora deterministic frequency responseanalysis in SOL 108 or SOL 111.

New system cell

587 –

In solution sequences other thanSOLs 153, 159, 601, and 701,controls whether axisymmetric inputand output for CTRAX3, CQUADX4,CTRAX6, CQUADX8, CTRIAX, andCQUADX elements is on a per unitradian basis or a per 2π radian basis.

New system cell

589 – Controls the CQUADR and CTRIARelement R6 stiffness. New system cell










ADAMSMNFGenerates ADAMS Modal NeutralFile (MNF) during a SOL 103, 111, or112 run.

Added NONCUP describer whichcontrols whether off-diagonal termsin the modal viscous damping matrixare written to ADAMS MNF files.

ADAPTERR Controls the computation and outputof error estimates. New case control command

CRSTRN Requests creep strain at grid pointsin SOL 401. New case control command

DTEMP Selects a time-assigned temperatureset in SOL 401. New case control command

GCRSTRN Requests creep strain at Gauss pointsin SOL 401. New case control command

GPLSTRN Requests plastic strain at Gausspoints in SOL 401. New case control command

JINTEGControls the computation and outputof the j-integral for crack simulation inSOL 401.


MBDEXPORT

Generates interface file for third-partymulti-body dynamics and controlsystem software during a SOL 103,111, or 112 run.

Added NONCUP describer whichcontrols whether off-diagonal terms inthe modal viscous damping matrix arewritten to ADAMS MNF files, standardor state-space MATLAB files, andstandard and state-space OP4 files.

OPRESS Requests solution set pressure outputin SOL 401. New case control command

PLSTRN Requests plastic strain at grid pointsin SOL 401. New case control command

RIGIDSelects the rigid element processingmethod for RBAR, RBE1, RBE2,RBE3, RROD, and RTRPLT elements.

Added AUTO and STIFF describerswhich select the rigid elementbehavior for RBE2 and RBARelements in SOL 401.

Parameter changes


COLPHEXA Allows collapsed CHEXA elementsfor crack simulation. New parameter

MATNL Globally turns on material nonlinearcapabilities in SOL 401. New parameter

NONCUP

Selects whether coupled or uncoupledmodal equations are used in SOLs111 and 112 runs, or are exported tointerface files for use with multibodydynamics or control system software.

Capability is now supported for modalviscous damping matrices exported tostandard or state-space MATLAB andOP4 files.




Parameter Parameter description Description of changePHIBGNPHIDEL

PHINUM

Defines the range of azimuth angleover which the equations of motionwith time-dependent coupling termsare solved during a rotor dynamicanalysis.

New parameters

POSTSpecifies the set of data blocksthat are written to output files forpost-processing.

Output data blocks that contain modaland panel contribution results cannow written to the OP2 file when eitherPARAM,POST,-1 or PARAM,POST,-2is specified.

Output data blocks that contain vonMises results from SOLs 108 and 111frequency response analyses cannow written to the OP2 file when eitherPARAM,POST,-1 or PARAM,POST,-2is specified.

POSTOPT

In the context of the NX Multiphysicsenvironment, controls if NX Nastranwrites the requested results aftereach time step in which output wasrequested, or at the end of thesubcase for the time steps in whichoutput was requested.

New parameter

QSETREMControls whether unused q-setDOF are retained with an externalsuperelement.

New parameter

RGBEAMARGBEAMERGLCRIT

RGSPRGK

Used in SOL 401 when the softwareinternally replaces the RBE2 andRBAR elements with either a stiffbeam element or a stiff springelement. This is done to computelarge displacement effects andthermal expansion.

New parameters

ROTCMRF

Specifies the reference rotor speedthat is used to compute the reducedmodal basis in a SOL 107 rotordynamic solve with complex modalreduction.

ROTCMRF is supported, butundocumented in NX Nastran 9.

ROTCOUPSpecifies the coupling grid points in aSOL 107, 108, or 109 rotor dynamicanalysis.

New parameter

SWPANGLE

Specifies the angular increment indegrees at which failure indices andstrength ratios are computed andoutput for laminates in SOL 108 and111.

New parameter




Item code changes

Element code Element code description Description of change

95, 96, 97, 98, 232, 233CQUAD4, CQUAD8, CTRIA3,CTRIA6, CQUADR, and CTRIARcomposite shell elements

Added item codes for complexstresses and strains.

269, 270 CHEXA and CPENTA composite solidelements

Added item codes for real andcomplex stresses and strains.

280 CBEAR elements Added item codes for real andcomplex moments.



Bulk entry changes


BCTPARM Controls parameters forsurface-to-surface contact algorithm.

Added PTOL, CNTCONV, OPNSTF,OPNTOL, GAPTOL, NOSEP,GUPDATE, GUPTOL, DISCAL,DISTOL, and KSTAB parameters tocontrol SOL 401 surface-to-surfacecontact algorithm.

BFLUIDDefines a fluid boundary byreferencing BSURFS, BCPROPS, orBEDGE bulk entries for SOL 601,106.

New bulk entry

BOLT Selects the elements to be included inthe bolt preload calculation.

Added the SOL 401 bolt preloadcapability.

CHEXA Six-sided solid element connection. Added alternate formats to supportcollapsed CHEXA element definition.

CRAKTP Specifies information related to acrack tip in SOL 401. New bulk entry

DTEMP Defines a time dependent temperatureset in SOL 401. New bulk entry

DTEMPEX Defines a time dependent temperatureset using a .bun file in SOL 401. New bulk entry

MATCRP Defines coefficients for Bailey-Nortoncreep model in SOLs 401 and 601. New bulk entry

MATOVR Overrides plasticity and/or creep forselected elements in SOL 401. New bulk entry

MATS1 Defines stress-dependent materialproperties.

Updated to support plasticity analysisin SOL 401. Added TYPE =“PLSTRN” to support stress versusplastic strain tabular data entry.

MATSR

Specifies strain-rate dependentproperties for use with MATS1 entrywith the same MID in SOLs 601 and701.

New bulk entry





NLCNTL Defines solution control parametersfor SOL 401.

Added the CREEP parameter todeselect creep effects in subcases.Added the CRCERAT, CRCINC,CRICOFF, CRINFAC, CRINTS,CRMFMN, CRMFMX, CRSBCDT,CRTEABS, CRTECO, CRTEREL,CRTSC, CRTSMN, and CRTSMXparameters to control adaptive timestepping in creep analysis.

Added the PLASTIC parameter todeselect plasticity effects in subcases.

Added the EPSBOLT and ITRBOLTparameters to control bolt preloadcalculations.

PBEAR Defines stiffness and viscous dampingmatrices for bearing connection.

Added continuation lines that allowyou to define additional stiffness andviscous damping terms for CBEARelements.

Speed and displacement-dependent,and speed and force-dependentCBEAR stiffness and viscousdamping are now supported in SOLs108, 109, 111, and 112 in addition tothe previously supported SOL 101.

Added continuation lines that allowyou to define composite relativedisplacements and composite relativeforces. The software now uses thecomposite relative displacementsand composite relative forces to lookup stiffness and viscous dampingvalues when the stiffness andviscous damping are speed anddisplacement-dependent, or speedand force-dependent, respectively.

PCOMP Defines the properties of an n-plycomposite material laminate.

Added support for stress and strainoutput for individual lamina in SOLs108 and 111 to existing remark.

PCOMPGDefines the properties of an n-plycomposite material laminate whichincludes global ply IDs.


Added support for PCOMPG in SOL601.

PCOMPSDefines the properties of an n-plycomposite material laminate forCHEXA and CPENTA solid elements.






PGPLSN Defines the properties of generalizedplane strain elements. New bulk entry

PSHL3D Defines the properties of 3D shellelements for SOLs 601 and 701. New bulk entry

ROTORD Defines rotor dynamic solutionoptions.

Removed the limit of ten on MAXITERand changed the default for MAXITERfrom “0” to “10”.

ROTSE Supplemental rotor superelementdefinition. New bulk entry

SWLDPRM Defines parameters forCWELD/CFAST connectors.

The default for DISPRT waspreviously “0” and is now ”2”. As aresult, GA/GB displacements are notoutput by default. The default changeimproves performance.

TEMPEX Time independent temperature setdefined in a .bun file for SOL 401. New bulk entry

VCEV Defines virtual crack tip extensionvectors in SOL 401. New bulk entry



Siemens Industry Software

HeadquartersGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 972 987 3000

AmericasGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024USA+1 314 264 8499

EuropeStephenson HouseSir William Siemens SquareFrimley, CamberleySurrey, GU16 8QD+44 (0) 1276 413200

Asia-PacificSuites 4301-4302, 43/FAIA Kowloon Tower, Landmark East100 How Ming StreetKwun Tong, KowloonHong Kong+852 2230 3308

About Siemens PLM Software

Siemens PLM Software, a business unit of the SiemensIndustry Automation Division, is a leading global providerof product lifecycle management (PLM) software andservices with 7 million licensed seats and 71,000 customersworldwide. Headquartered in Plano, Texas, SiemensPLM Software works collaboratively with companiesto deliver open solutions that help them turn moreideas into successful products. For more informationon Siemens PLM Software products and services, visitwww.siemens.com/plm.

© 2018 Siemens Product Lifecycle ManagementSoftware Inc. Siemens and the Siemens logo areregistered trademarks of Siemens AG. D-Cubed,Femap, Geolus, GO PLM, I-deas, Insight, JT, NX,Parasolid, Solid Edge, Teamcenter, Tecnomatix andVelocity Series are trademarks or registered trademarksof Siemens Product Lifecycle Management SoftwareInc. or its subsidiaries in the United States and in othercountries. All other trademarks, registered trademarksor service marks belong to their respective holders.

simcenter nastran 2019.1 release guide - siemens

Documents